In the PowerCenter Client, you can export repository objects to an XML file and then import repository objects from the XML file. Use the following client applications to export and import repository objects:
Repository Manager.
You can export and import both Designer and Workflow Manager objects.
Designer.
You can export and import Designer objects.
Workflow Manager.
You can export and import Workflow Manager objects.
pmrep
.
You can export and import both Designer and Workflow Manager objects. You might use
pmrep
to automate exporting objects on a daily or weekly basis.
Exporting and importing an object is similar to copying an object from one folder or repository to another. For example, when you copy an object between folders or export and import that object, you can resolve object name conflicts. However, when you copy objects between folders or repositories, you must be connected to both repositories. When you export an object from one repository and import the object into another repository, you do not need to be connected to both repositories.
Export and import objects between repositories with the same version. Informatica does not support imported objects from a different release.
You can export and import repository objects to accomplish the following tasks:
Deploy metadata into production.
After you test a mapping in a development repository, you can export it to an XML file and then import it from the XML file into a production repository. You might export and import objects to incrementally deploy metadata by exporting and importing part of a composite object.
Archive metadata.
You can export objects to an XML file that you no longer need before removing them from the repository.
Share metadata.
You can share metadata with a third party. For example, you want to send a mapping to someone else for testing or analysis, but you do not want to disclose repository connection information for security reasons. You can export the mapping to an XML file and edit the repository connection information before sending the XML file. The third party can import the mapping from the XML file and analyze the metadata.
Search and replace property names in an entire repository object.
You can search for a property name and replace all occurrences of it with a different name. For example, you have a mapping with an unconnected Lookup transformation. You want to change the name of a port in the unconnected Lookup transformation. Several other transformations call the lookup port through an expression, so you want to make sure you change the port name in all other expressions. You can export the mapping to an XML file and open it in a text editor. Search for the old port name and replace all references to it with the new port name. Then import the mapping into the repository.
Copy metadata between repositories.
You can copy objects between repositories that you cannot connect to from the same client. Export the object and transfer the XML file to the target machine. Then import the object from the XML file into the target repository.
Create mappings.
You can export an existing mapping and use Mapping Architect for Visio to turn the mapping into a mapping template. Once a mapping template is created in Mapping Architect for Visio you can import multiple mappings into the repository.
You can also export and import relational sources and targets to share metadata with other business intelligence and data modeling tools.