Import of Metadata

The System Operations > Import Metadata option allows you to import metadata from a source company to a destination company. Before importing metadata, the first step is to export metadata from a source company. When you export metadata, a JAR file is created out of the metadata. You can also use the existing JAR file of the metadata, if any.

Note: While importing metadata, only JAR, ZIP, and XML file extensions are allowed. For all other extensions, an error message is displayed.

To import metadata, upload the JAR file that contains the metadata to the destination company. After the JAR file is uploaded, the DataService workflow is initiated. To learn more about the DataService workflow, see Workflow Reference on the TIBCO MDM product documentation page. The DataService workflow uses the metadata in the JAR file to create a repository at the destination company. If a repository of the same name exists in the destination company, the content of the repository will be overwritten. Metadata, namely, attributes, attribute groups, classification scheme, input maps, output maps, and so on, is overwritten.

Note: When repository metadata is imported, if the table name is specified, it will be used to create the repository data table. Else, a system-defined value is used. If the specified table name already exists, an exception is thrown and the repository is not imported.

Similarly, for an attribute, if the database column name is not specified or a duplicate column name is specified, a system generated column name is used.