54.6 Upgrading the Identity Applications

When you run the installation 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, specify Existing Database for the database type.

  • (Conditional) If your existing database runs on Oracle and you instruct the installation program to write a SQL file to update the schema, you must perform additional steps. For more information, see Section 54.7.1, Preparing an Oracle Database for the SQL File.

  • 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 the application server.

  • Do not use case-insensitive collation for your database. Case-insensitive collation is not supported. If you use case-insensitive collation, you might encounter duplicate key errors during migration. If a duplicate key error is encountered, check the collation and correct it, then re-install the identity applications.

  • 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 Section 4.4, Using Self-Service Password Management in Identity Manager.

For more information about installing the identity applications, see Section X, Installing the Identity Applications.