Upgrade Guide › WebSphere Version › Provisioning Components Upgrade › Migrate the Provisioning Directory

Migrate the Provisioning Directory

When upgrading to CA Identity Manager r12.5 SP8, you may need to migrate the Provisioning Directory to a new system to accommodate requirements for memory or a 64-bit operating system.

To migrate the Provisioning Directory to a new system

1. Install CA Directory on the new system using the CA Directory component installer.
2. Copy any custom schema files from the existing Provisioning Directory system to the new system. Custom schema files exist in the following situations:
   • The COSX (etrust_cosx.dxc) has been modified.
   • The LDA connector (etrust_lda.dxc) is installed.
   • A custom C++ connector schema has been created.

   Copy the schema files from the local %DXHOME%/config/schema directory to the same directory on the new system.

3. Install the r12.5 SP8 Provisioning Directory on the new system using the same domain name as the existing system.
4. Stop the etrustadmin DSA on the old system and dump the data by running the following command from a command prompt:

   dxdumpdb -O -f filename -p dc=etadb -S DSA_name database_name
   

5. Stop the -main, -co, and -inc DSAs on the new host by running the following commands from a command prompt:

   dxserver stop new_system_name-impd-main
   dxserver stop new_system_name-impd-inc
   dxserver stop new_system_name-impd-co
   

6. Load the data file produced in Step 4 into all the DSAs by running the following commands from a command prompt:

   dxloaddb -s new_system_name-impd-main filename
   dxloaddb -s new_system_name-impd-co filename
   dxloaddb -s new_system_name-impd-inc filename
   

7. Restart the DSAs on the new host by running the following commands from a command prompt:

   dxserver start new_system_name-impd-main
   dxserver start new_system_name-impd-inc
   dxserver start new_system_name-impd-co
   

   The r12.5 SP8 Provisioning Directory is now running on the new system with all the data from the old system. The old Provisioning Directory can now be removed.

8. Uninstall and reinstall any alternate Provisioning Directories.

   Note: For more information, see the Installation Guide.

Note: Be sure to use the new Provisioning Directory hostname when upgrading the Provisioning Servers. The default in the upgrade installer will be set to the old hostname and must be changed.