You can migrate one resource or all resources in a repository. If you migrate individual resources, migrate and reload JDBC and data management resources before you migrate and reload other types of resources. If you do not migrate and reload resources in this order, you might lose connection information for business intelligence and data modeling resources.

If you migrate one resource, you can specify a name for the new resource. If you do not specify a name for the new resource or you migrate all resources, rmu generates the new resource names. If you migrate an Embarcadero ERStudio, MicroStrategy, or SAP PowerDesigner resource, rmu creates one new resource for each metadata source file.

rmu takes an XML configuration file as an argument. The configuration file specifies connection information for the original repository database. It also specifies authentication information for the original resource and the new resource.

When you migrate a resource, rmu first creates a new resource configuration file and then creates a new resource from the resource configuration file. If errors occur during the migration process, check the migration log file to determine the cause of the errors, and then rerun rmu. The migration log file is

<Informatica Installation Directory>\services\MetadataManagerService\utilities\rcfmuUtil\resourcemigration.log

.

After you run rmu, you can view the new resource on the

Load

tab or the

Browse

tab.

Metadata Manager displays one of the following statuses for the new resource:

After migration, load the new resource. Then re-create the shortcuts, comments, links, and relationships from the original resource. You must also update any schedule that the original resource is assigned to.

rmu cannot convert Business Objects universe names to universe IDs. Therefore, after you migrate and load a Business Objects resource, you might need to update the universe ID.