Step 7: Upgrade Your Identity Manager Application

To upgrade your Identity Manager application, you might be required to do the following:

• Update Your Database Table Definitions

• Promote the Identity Manager Application

• Import a Subset of update.xml

• Upgrade All Gateway Instances

• Upgrade All PasswordSync Instances

About Data Sources

If you use a JDBC data source defined in your application server as your Identity Manager repository location, be aware that this data source might not work outside the application server. In other words, a JDBC data source provided by an application server might be available for use only by web applications that run in that container.

The Identity Manager product upgrade process runs outside the application server, just like the Identity Manager console. Therefore, in each environment where Identity Manager normally uses a data source, your upgrade procedure might need to include steps to switch to a JDBC DriverManager connection.

You can temporarily replace the ServerRepository.xml file that specifies a data source with another ServerRepository.xml file that specifies a JDBC DriverManager connection. Restore the original ServerRepository.xml file as a subsequent step in your upgrade procedure.

Alternatively, you can expand the Identity Manager application WAR file onto the file system, specify WSHOME as the file system location, and use this “side” environment to perform a manual upgrade process or to perform any step that requires a console, such as importing a subset of update.xml or renaming TaskDefinition objects.

If additional setup is required for your custom integrations in each environment, perform the additional setup as part of this step.

Update Your Database Table Definitions

Verify that your Identity Manager application image includes any SQL scripts needed to update your database table definitions, and that these SQL scripts have been modified to fit your environment.

If your image does not include these SQL scripts, ensure that your upgrade procedure specifically describes the modifications required for each environment.

Promote the Identity Manager Application

Promote the Identity Manager application image into your Test environment. Your application image must include the target Identity Manager product version, your updated configuration, and your customizations.

Import a Subset of update.xml

You must import the update.xml file to update the repository objects that are not managed as part of your Identity Manager application baseline.

Use only one Identity Manager server to import update.xml and have only one Identity Manager server running during the upgrade.

If you start any other Identity Manager servers during the upgrade process, you must stop and restart those servers before making them available again.

Upgrade All Gateway Instances

Upgrade every Sun Identity Manager Gateway installation in your environment. See To Upgrade the Identity Manager Gateway.

Newer versions of Identity Manager server will not work with older versions of the Gateway. All Gateway and Identity Manager Server installations should be updated within the same maintenance window.

Upgrade All PasswordSync Instances

Upgrade every PasswordSync installation in your environment. SeeUpgrade All PasswordSync Instances.

Unless the Release Notes specify otherwise, newly installed versions of the Identity Manager server provide limited, temporary support for older versions of PasswordSync. This support is provided so that Identity Manager can continue to run while you upgrade your PasswordSync instances. All instances of PasswordSync should be updated to the same version as Identity Manager Server as soon as possible.