Skip to main content

Harvest several Models from a directory of external metadata files.

It is common for an organization to have a large number of external metadata files, but does not use an external metadata repository. Often, this organization would like to import the files into TDC in batch in an automated fashion. TDC has the ability to support this scenario with the help of a harvesting script.

In this case, the files are stored under a file directory which is accessible to the TDC application server. The script scans the directory and its subdirectories for files of the particular external metadata type and finds matching Models under a particular folder in TDC . The TDC repository folder and model structure will match the structure of files and their directories on the file system. When the necessary Model does not exist the script creates one and imports the file. When the content is present the script will re-import it if the file’s version has not been harvested yet.

One can schedule MM to run the script periodically. It should allow customers to place files under the directory and be assured that TDC will import them automatically. It will work for any single model file-based bridges.

A special model named Settings must also be defined in order to control how the files will be imported (what source tool and what bridge parameters).

Ensure proper permissions

  1. Sign in as a user with at least the Metadata Management capability object role assignment on the Configuration you are in.

Create the configuration (as needed)

Information note

One may create, harvest and analyze metadata (model contents) from the MANAGE > Repository tree . However, generally it is best to create a configuration to work in (and to define the scope of analysis and search) and then go to MANAGE > Configuration and create and harvest there.

Create the TDC folder

  1. Go to the MANAGE > Repository
  2. Right click on a folder in the Repository Tree where you want to place the folder containing the results of the import and select New > Folder .
  3. Name the folder accordingly.

Create the Settings file to control the import of Models:

  1. Right click on that new folder in the Repository Tree and select New > Imported Model .
  2. Select the Overview tab in the Create Model dialog.
  3. Enter “Settings” in the NAME for the model.
  4. Select the correct source format in the IMPORT BRIDGE pull-down.
  5. Click OK .
  6. Select the Import Setup tab.
  7. For each of the Parameter s, complete according to the tool-tips displayed in the right hand panel of the dialog. In particular, for the File parameter
    • Click on the Browse icon and browse for a file inside the directory structure on the file system.
Information note

If you cannot find the location using the Browse function you must configure (as part of the installation) the available paths to present to users. More details may be found in the deployment guide .

  1. Update the File parameter to so that the path only refers to the top level of the directory structure on the file system (i.e., remove the file name and any sub-directory names as well as removing the trailing slash or backslash.
  2. Click SAVE .

Harvest the Models on demand:

  1. Right click the new folder in the Repository Panel and select Operations > Import new model(s) from folder .
  2. Click Run Operation .
  3. The Log Messages dialog then appears and log messages are presented as the import process proceeds.
  4. If you receive the Import Successful result, click Yes to open the Model. If instead you see the Import Failed result, inspect the log messages and correct the source Model file accordingly.
  5. Be sure to include those new models in the configuration.

You may now browse the Models.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!