Skip to content

Manage Processes

One may use the Process Manager icon in the upper right to see at a glance whether processes are running and also open their logs.

Obtain an Object Id

For many admin tasks and most REST API calls, it is necessary to know the internal object_id of objects, models, etc.

Steps

  1. Go to MANAGE > System and select Enable in the Debug Logging pull-down.

  2. Navigate to the object page for the object for which you wish to obtain the object_id.

  3. In the Properties area of the object page, see the Model Id and Object Id fields.

    A screenshot of a computer Description automatically generated

The Object Id displayed here is in the context of the model it is in. The universal object_id is the combination of the Model Id and Object Id displayed on the object page.

The universal (repository wide, rather than model specific) object_id that most API calls are looking for is the concatenation of the Model Id and Object Id displayed on the object page. You must separate them with an underscore ("_").

E.g., in this case, the object_id is 37_30.

Be sure to include any negative or minus-signs (e.g., -1_22)

You may remove the debug preference once you have obtained the object_id, as leaving it enabled will greatly increase logging unnecessarilyObtain an Stable Id

MetaKarta also computes a Stable Id. A Stable Id:

  • Is unique to an object within the context of a configuration

  • Is used in the URLs presented at the top of web page results so that one may copy and paste using the Stable Id

  • Is unlike the Object Id in that the Stable Id remains fixed even as new versions of harvested metadata are include (replaced) in the configuration.

  • Stable Ids are preserved in major version upgrades and in the backup/restore operations

Steps

  1. Go to MANAGE > System and select Enable in the Debug Logging pull-down.

  2. Navigate to the object page for the object for which you wish to obtain the Stable Id.

  3. In the Attributes area of the object page, see the Stable Id field.

    A screenshot of a computer Description automatically generated

Logging "Popular" Search Queries

MetaKarta can log the search queries executed into a csv file.

Steps

To enable the logging of search queries:

  1. Create a "search" directory under the "$MM_HOME/data/logs" directory in the installation folders

  2. Restart MetaKarta

The log contains the following search query details: time, user ID, configuration, text.

To disable the logging of search queries:

  1. Delete the "search" directory under the "$MM_HOME/data/logs" directory in the installation folders

  2. Restart MetaKarta

View Links

Most repository objects are inter-related in numerous ways, e.g.,

  • Configuration versions contain versions of models, mappings and glossaries.

  • Mappings have source and target models and glossaries

  • Etc.

In order to see these relationships, one may use the View Links options in the metadata manager UI.

Steps

  1. Go to MANAGE > Repository and the Repository Panel.

  2. Right-click on the object to check select View Links.

A version of a repository model may have different specific links than other versions of that same model and even from the model as a whole. Be sure to Show versions if necessary.

Example

Go to the metadata manager user interface and open the Repository Panel.

Right-click on the Staging DW model and select View Links and note that it is a member of the Published configuration version and is the target of mappings.

A screenshot of a computer Description automatically generated

A screenshot of a computer Description automatically generated

Wait more than one hour.

Right-click on the Data Warehouse folder and select More... > Operations > Purge unused versions. Click Run Operation.

Rebuilding the Search Index

If recommended by the Support Team, it may be necessary to rebuild the indexes used by search and the user interface.

Steps

  1. Stop the application server.

  2. Go to $MM_HOME/data/Search/ and delete the lucene-xxxxxxxx folder (where the xxxxxxxx are hexadecimal digits identifying the particular index)

  3. Restart the application server.

Organize the Repository Tree

You may organize the objects presented in the Repository Tree for the Repository as a while.

Repository organization is very important as you may schedule, assign responsibilities, and perform actions (right-click) by folder.

Steps

  1. Sign in as a user with at least the Metadata Editor capability object role assignment to the configuration you wish to organize.

  2. Go to MANAGE > Repository.

  3. Right-click on the Repository or any folder and select Create > Folder to create folders.

Thus, folders may contain folders.

  1. Drag any object into a folder to organize.

Moving an object in the Repository Tree changes the unique path (ID) used to uniquely identify the object, e.g., in the REST API or in the URLs. In addition, all responsibility object role assignments are cleared and then re-computed based upon inheritance.