Customizations Migration
Detailed procedure for migrating from Identity Manager -Software Stack to the IBM Verify Identity Governance - Container.
Configuration and customization
After you migrate your Identity Manager -Software Stack data over to IBM Verify Identity Governance - Container, you can migrate your configurations and customizations.
List of customizations
This section provides detailed instructions to locate the customizations if migration is from -Software Stack and how to do the same in IBM Verify Identity Governance - Container.
The first step is to locate the customizations based on software stack installation path.
There is a possibility that some customizations may not have been made by the customer, and in such cases, they can simply ignore those specific customizations.
Also, customers may have other customizations apart from what is listed in this section, and in that case you need to locate those files on the legacy system and need to use utility program or instructions from Customization section for migrating them to IBM Verify Identity Governance - Container system.
- Feed files
-
Use the loadHRFeed.sh utility program to copy the feed files into the IBM Verify Identity Governance - Container, so that it can be accessed by an HR Feed service. See loadHRFeed topic.
- External Libraries
-
See Customization overview topic for copying the external libraries into the IBM Verify Identity Governance - Container.
- Workflow Extensions
-
workflowextension.xml: This file will have all details like Extension name, servlet class, description, Activity ID, XML etc.
- Updated properties files
-
You can refer the Editing the property files topic for more details about updating the properties files in IBM Verify Identity Governance - Container.
- Identity manager application server certificate
-
Perform these steps for downloading the Identity Manager's certificate chain from the web browser. Enter the Identity Manager Administration Console URL of the old system in the web browser and download the certificate chain. The process may vary slightly depending on the browser you are using. Here are example instructions for Google Chrome web browser:
- Click on the padlock icon in the address bar to view the site information.
- Click on
Connection is secure
text. - Click on
Certificate is valid
or similar text. - Navigate to the "Details" tab.
- Click the individual certificate from certificate hierarchy and export it.
- Edit the config.yaml file. In the server > keystore section, specify the exported certificate chain details.
- Custom files and folders
-
Data directory: Refer the Editing the property files topic for more details about updating the properties files in this directory.
itim_console.war, isim_isc_subform.war, and ui directories: The files from these directories can be modified. Refer the Customization section for detailed instructions.
Next step
This completes a typical migration process.
Optional step: After completing this step, you can proceed to the Production cutover.