When you run the Upgrade program for the identity applications, ensure that you incorporate the following considerations:
Use the same database that you used for the previous User Application. That is, the installation from which you are migrating. In the installation program, specifyfor the database type.
You can specify a different name for the User Application context.
Specify an installation location that is different from the one for the previous installation.
Point to a supported version of Tomcat.
Do not use case-sensitive collation for your database. Case-sensitive collation is not supported. The case-insensitive collation might cause duplicate key errors during migration. If a duplicate key error is encountered, check the collation and correct it, then re-install the identity applications. The only supported collation is SQL_Latin1_General_CP1_CI_AS.
Understand the differences in the providers for managing passwords. SSPR is the default provider. To use Identity Manager’s legacy provider or an external provider, you must update the configuration of the identity applications after the upgrade. For more information, see Using Self-Service Password Management in Identity Manager.
For more information about upgrading the Identity Applications, see Upgrading Identity Applications and Identity Reporting.