Migrating the Repository when Domain Names or Encryption Keys Differ
Migrating the Repository when Domain Names or Encryption Keys Differ
When the domain names or encryption keys differ, you must copy the encryption key file from the old domain, rename it, and upgrade the Metadata Manager Service. The upgrade process updates the domain name and encryption key in the new repository.
Before you migrate the repository, create the new Metadata Manager repository database. You must also export users and groups from the old domain and import them into the new domain. You can use the infacmd command line program to export and import users and groups. For more information about infacmd commands, see the
Informatica Command Reference
.
In the old domain, use the mmRepoCmd backupRepository command to back up the repository contents to a binary file.
In the new domain, create the Metadata Manager Service and associate it with the new repository database.
Enable the Metadata Manager Service in the new domain.
The PowerCenter Repository Service and PowerCenter Integration Service must be running to enable the Metadata Manager Service.
Copy the repository back-up file from the back-up directory in the old domain to the back-up directory in the new domain.
The back-up directory for repository back-up files is the following directory:
<Informatica services installation directory>\services\MetadataManagerService\mm_files\<Metadata Manager Service name>\backup
Copy the domain encryption key file, siteKey, from the old domain to the encryption key directory in the new domain and rename the copied file siteKey_old.
Do not overwrite the siteKey file in the new domain.
The encryption key directory in the new domain will contain two encryption key files, siteKey and siteKey_old.
In the new domain, use the mmRepoCmd restoreRepository command to restore the repository contents from the binary file that you copied from the old domain.
In the new domain, recycle the Metadata Manager Service.
The Metadata Manager Service drops and recreates the caches that store model and resource information.
In the new domain, manually create the search index for all resources.