Upgrading a Test environment requires only a subset of the steps that you performed when upgrading your Development environment. For example, you do not have to detect changes or update source control. The updated baseline for your Identity Manager application already contains those changes.
Before upgrading any targeted environments, you must generate an image of your Identity Manager application that is appropriate for that environment. The baseline, and therefore the image, contains the following:
Step 1 is optional, but performing this step is considered a best practice when upgrading the Production environment.
Also, if you perform Step 1 in your Production environment, make it a standard step when upgrading in all of your other environments.
Make a copy of your existing database and Identity Manager file structure.
Always back up the Identity Manager database and file system before applying any Identity Manager patches, service packs, or hotfixes and before going through any major upgrades.
You can use third-party backup software or a backup utility supplied with your system to back up the Identity Manager file system. To back up your database, see your database documentation for recommended backup procedures.
Shutdown or idle Identity Manager.
Use your backup utilities to back up your database and the file system where you installed Identity Manager.
Hotfix class files generally work only with the specific version of the Identity Manager product for which the hotfix was delivered.
You might find it necessary to upgrade a Production environment that contains executing task instances. Unfortunately, upgrading an Identity Manager TaskDefinition object in the repository can corrupt executing task instances that depend on the TaskDefinition object. This possibility is a particularly important consideration in a Production environment where people are depending on those tasks to complete correctly and to perform their business functions.
Although it is easiest to have users complete their tasks or terminate still-executing tasks prior to upgrade, these options are not always feasible.
If your Production environment might contain executing task instances when you upgrade, be sure that your upgrade procedure describes how to address these instances.
From the Identity Manager console, rename the current TaskDefinition to include a time stamp.
Load the new TaskDefinition.
Problems might occur if you change activities or actions.
If the target Identity Manager product version requires platform changes, you must make these changes before upgrading the Identity Manager product.
To upgrade your Identity Manager application, you might be required to do the following:
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.
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 image into your Test environment. Your application image must include the target Identity Manager product version, your updated configuration, and your customizations.
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 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.
Log in to the GlassFish administrator interface.
Choose Applications > Web Applications from the menu bar.
Locate your web application and click the Redeploy link.
Click the button next to the Local Packaged File or Directory That Is Accessible From the Application Server option.
Click the Browse Folders button and select the top-level folder for your installation.
Restart the application server.
Step 9 is optional, but performing this step is considered a best practice when upgrading the Production environment.
Also, if you perform Step 9 in your Production environment, make it a standard step when upgrading all of your other environments.