| Oracle® Identity Manager Upgrade Guide Release 9.1.0 (9.0.3.2 Upgrade) Part Number E13340-01 |
|
|
View PDF |
| Oracle® Identity Manager Upgrade Guide Release 9.1.0 (9.0.3.2 Upgrade) Part Number E13340-01 |
|
|
View PDF |
This chapter explains how to upgrade to release 9.1.0 from release 9.0.3.2 on IBM WebSphere Application Server. Do not attempt to upgrade to release 9.1.0 from any other previous Oracle Identity Manager release.
Note:
You can only upgrade the existing database and then perform a new installation of Oracle Identity Manager.For information about installing Oracle Identity Manager, refer to Oracle Identity Manager Installation and Configuration Guide for IBM WebSphere Application Server.
Extract the contents of the release 9.1.0 upgrade package to a temporary directory on your existing release 9.0.3.2 system.
The following steps (detailed in this chapter) explain how to upgrade from release 9.0.3.2 to release 9.1.0 on IBM WebSphere Application Server:
The first step for upgrading to release 9.1.0 is to create a backup of your existing release 9.0.3.2 deployment to ensure that no data is lost during the upgrade process. If the upgrade fails, then you can use this backup to restore the release 9.0.3.2 deployment to its original state.
Create a backup of the following:
Oracle Identity Manager
Create a backup of the OIM_HOME directory in which you have installed Oracle Identity Manager.
Oracle Identity Manager Design Console
Create a backup of the OIM_DC_HOME directory in which you have installed the Oracle Identity Manager Design Console.
Oracle Identity Manager Remote Manager
Create a backup of the OIM_RM_HOME directory in which you have installed the Oracle Identity Manager Remote Manager.
Database used for release 9.0.3.2
Follow the procedures in this section to install release 9.1.0 if you are upgrading WebSphere to IBM WebSphere Application Server v6.1.0.9.
For details about upgrading the Oracle Identity Manager Database, refer to Chapter 6, "Upgrading the Oracle Identity Manager Database".
Release 9.1.0 is certified on IBM WebSphere Application Server v6.1.0.9. Install or upgrade to IBM WebSphere Application Server v6.1.0.9 before upgrading to release 9.1.0.
Ensure that you upgrade the WebSphere client also to 6.1.0.9 for the release 9.1.0 Design Console.
Note:
For a clustered installation of IBM WebSphere Application Server, you must upgrade the Network Deployment Manager and all Node Managers to IBM WebSphere Application Server v6.1.0.9.Refer to the WebSphere application server documentation for details on upgrading to WebSphere 6.1.0.9. For setting up WebSphere, refer to the Oracle Identity Manager Installation and Configuration Guide for IBM WebSphere Application Server. Do not install Oracle Identity Manager before upgrading the database as mentioned in the following pages.
Note:
When upgrading to IBM WebSphere Application Server v6.1.0.9, review the information about IBM WebSphere Application Server Daylight Savings Time Changes for the United States. Also ensure that you install the JDK upgrade as appropriate for the 6.1.0.9 release. Note that this is different from the WebSphere 6.1.0.0 to WebSphere 6.1.0.9 upgrade.Go to the IBM Support and downloads Web site at the following URL:
To install release 9.1.0:
Install IBM WebSphere Application Server and upgrade it to release 6.1.0.9.
Install release 9.1.0.
Copy UpgradeAttestation.bat from PATCH/xellerate/setup/ to OIM_HOME/xellerate/setup/.
For upgrading attestation, see Appendix H, "Upgrade Attestation Utility".
This section discusses the steps involved in installing or upgrading Oracle Identity Manager components. It consists of the following topics:
For details on installing Oracle Identity Manager, refer to the Oracle Identity Manager Installation and Configuration Guide for IBM WebSphere Application Server.
Note:
When installing release 9.1.0, ensure that you point to the existing database you upgraded to release 9.1.0 on the Database Server Selection screen in the installer program. Enter the information for the existing database that you upgraded to release 9.1.0 in the following fields on the Database Server Selection screen:Host
Port
Database SID
User Name
Password
When Oracle Identity Manager is installed against an existing database, the .xldatabasekey file from the existing Oracle Identity Manager installation must be copied to the new OIM_HOME/xellerate/config/ directory. Create the /config directory in the new OIM_HOME/xellerate/ path if it does not already exist.
Previously, Oracle Identity Manager used a single JMS queue (named xlQueue) for all asynchronous operations including requests, reconciliation, attestation, and offline tasks. In release 9.1.0, by default, Oracle Identity Manager uses separate JMS queues for specific operations to optimize JMS queue processing. The following is a list of the default JMS queue configuration and their related operations:
xlQueue for request operations
xlReconQueue for reconciliation operations
xlAuditQueue for auditing operations
xlAttestationQueue for Attestation operations
xlProcessQueue for future usage
By default, multiple JMS queues are configured in Oracle Identity Manager release 9.1.0.
Refer to the "Installing and Configuring the Oracle Identity Manager Design Console" section in the Oracle Identity Manager Installation and Configuration Guide for IBM WebSphere Application Server for complete steps on how to install the Design Console on the application server.
Refer to the "Installing and Configuring the Oracle Identity Manager Remote Manager" section of the Oracle Identity Manager Administrative and User Console Guide for complete steps on how to install the Remote Manager on the application server.
Start the server and run the Re-Issue Audit Message Task scheduled task to ensure that all the pending audit messages in the aud_jms table are processed.
Note:
While running the Re-Issue Audit Message Task scheduled task, ensure that the database and server is upgraded. If you are running the scheduled task by using the Design Console, then make sure that the Design Console has also been upgraded.You must perform the following postupgrade configuration procedures:
To set the user profile audit level:
Define a secondary data source for reporting, if required.
See Also:
Oracle Identity Manager Audit Report Developer's Guide for information about defining a secondary data sourceStart the application server on which the Oracle Identity Manager installation is running.
Set the audit level. The permissible values are (in descending order):
Process Task
Resource Form
Resource
Membership
Core
None
To specify an audit level:
Log in to the Design Console as an administrator.
Navigate to the System Configuration form.
Locate XL.UserProfileAuditDataCollection and set its value to Resource Form or the appropriate audit level as listed in step 3 of this procedure.
To collect user profile audit data in the secondary reporting data store:
Log in to the Design Console as an administrator.
Navigate to the System Configuration form.
Locate XL.UserProfileAuditInSecondaryDS and set its value to TRUE.
For detailed information about generating user snapshots, see Appendix E, "Generating User Snapshots".
For detailed information about generating GPA snapshots, see Appendix G, "Generating GPA Snapshots".
To load data for exception-based reporting, run the UPA Form Data Upgrade utility. For information about the UPA Form Data Upgrade utility, see Appendix F, "UPA Form Data Upgrade Utility".
You can migrate the custom Java code from the release 9.0.3.2 environment into the new release 9.1.0 environment. Before you migrate the custom Java code from the release 9.0.3.2 environment, you must first recompile it by using the release 9.1.0 libraries located in the OIM_HOME/xellerate/lib/ directory.
Using the integrated development environment that was originally used compile the release 9.0.3.2 custom Java code, which are Eclipse, JDeveloper, WASD or command-line javac, recompile all custom Java code by using the release 9.1.0 libraries.
The following is a list of the custom items you can migrate from release 9.0.3.2 and reuse in release 9.1.0 after recompiling by using the release 9.1.0 libraries.
Note:
For clustered environments, after recompiling the following items by using the release 9.1.0 libraries, copy them to each participant node of the cluster.Custom Java libraries bound to functional Oracle Identity Manager release 9.0.3.2 adapters recompiled by using release 9.1.0 libraries.
You must copy the recompiled custom Java libraries in the OIM_HOME/xellerate/JavaTasks/ directory of release 9.0.3.2 to the same directory of release 9.1.0. In addition, you must copy the recompiled custom Java libraries in the OIM_RM_HOME/xellerate/JavaTasks/ directory of release 9.0.3.2 to the OIM_RM_HOME/xellerate/JavaTasks/ directory of release 9.1.0.
Custom scheduled tasks recompiled by using release 9.1.0 libraries.
You must copy the recompiled custom scheduled tasks to the OIM_HOME/xellerate/ScheduleTask/ directory of release 9.1.0.
Note:
If you want to display the built-in scheduled task on the Administrative and User Console, then copy the xlScheduler.jar file from the OIM_HOME/lib/ directory to the OIM_HOME/xellerate/ ScheduledTask directory. If the ScheduledTask directory does not exist, then create it.Custom event handlers recompiled by using release 9.1.0 libraries.
You must copy the recompiled custom event handlers to the OIM_HOME/xellerate/EventHandlers/ directory of release 9.1.0.
Connector resource bundles by copying the OIM_HOME/xellerate/connectorResources/ directory of release 9.0.3.2 to the OIM_HOME/xellerate/connectorResources/ directory of release 9.1.0.
Custom resources by copying the OIM_HOME/xellerate/customResources/ directory of release 9.0.3.2 to the OIM_HOME/xellerate/customResources/ directory of release 9.1.0.
Custom Administrative and User Console deployments. Several Administrative and User Console files are modified in release 9.1.0. If you customized your release 9.0.3.2 Administrative and User Console, that is, you made changes to the default Administrative and User Console that shipped with release 9.0.3.2, then you must add your customizations into the new release 9.1.0 Administrative and User Console files.
