Import of Repositories Metadata with Cross-Repository Relationships

For repositories with cross repository relationships, you need to consider the relationships on the target company and how such relationships (on the Target company) may be affected as a result of an import.

For instance, you have a Customer repository with an associated Address repository, and if you want to import it to a target company which already has a Address repository with more attributes than the source repository of the same name, the target repository attributes will get overwritten by the source repository attributes. To avoid this and in case of such conflict, you can open and edit the response XML as a part of the exported JAR, put it back into the JAR and then perform the import on the target company.

  • When a repository is exported, the related repositories are also exported in the response XML.
  • For a given repository entity within the command object, the response XML would have multiple entities within the same command if the repository entity being exported has related repositories.
  • If a relationship definition has relationship attributes, the relationship attributes and table name corresponding to the attributes is also exported along with the relationship definition.
  • If an attribute is multivalue, the table name for the multivalue attribute is exported along with the attribute.
  • When input maps are defined in a repository, the input maps are also exported along with the repository. When the input maps have related input maps, the related input map is also exported along with the relationship attribute.