3 Upgrading to Release 9.0.3 from Release 9.0.2 on WebLogic Application Servers

This chapter explains how to upgrade to Release 9.0.3 from Release 9.0.2 on WebLogic application servers—do not attempt to upgrade to Release 9.0.3 from any other previous Oracle Identity Manager release.

Release 9.0.3 is certified on the WebLogic 8.1 with SP6 application server. You must upgrade to WebLogic 8.1 with SP6 as part of the process for upgrading to Release 9.0.3.

Note:

If you are a new Oracle Identity Manager customer and Release 9.0.3 is your initial deployment of the product, you can skip this chapter and simply run the Release 9.0.3 installer program to deploy Release 9.0.3.

Extract the contents of the Release 9.0.3 upgrade package to a temporary directory on your existing Release 9.0.2 system.

Note:

This document refers to this temporary directory as <PATCH>.

The following is a list of the steps in this section that explain how to upgrade from Release 9.0.2 to Release 9.0.3 on WebLogic:

1. Upgrading the Database for Oracle Identity Manager

   • Upgrading an Existing Database Instance In-Place

   • Creating a New Database Instance for the Upgrade

2. Preparing for the Upgrade

   1. Preparing the Oracle Identity Manager Server for Upgrade

   2. Preparing the Administrative and User Console for Upgrade

   3. Preparing the Design Console for Upgrade

   4. Preparing the Remote Manager for Upgrade

3. Performing the Upgrade

4. Migrating Release 9.0.2 Custom Code

5. Upgrading the Diagnostic Dashboard

6. Post-Upgrade Configuration

Upgrading the Database for Oracle Identity Manager

Choose one of the following approaches to upgrade the database used by your Oracle Identity Manager Release 9.0.2 deployment:

• Perform an in-place upgrade of the existing database configured for Release 9.0.2—refer to Upgrading an Existing Database Instance In-Place.

• Create a new instance of the database for Release 9.0.3, then import the data used by your Release 9.0.2 deployment into that new database and perform the upgrade—refer to Creating a New Database Instance for the Upgrade.

Before you upgrade your database, perform the following steps:

1. Extract the contents of the Oracle Identity Manager Release 9.0.3 upgrade package to a temporary directory on the database machine—this document refers to this temporary directory as <PATCH>.

2. Enable execute permissions on the scripts in the <PATCH> directory.

Upgrading an Existing Database Instance In-Place

This approach upgrades your existing Release 9.0.2 database instance by upgrading the database schema while your database remains in-place.

1. Backup your existing database. As appropriate to your particular database, use the export/backup utilities provided with the Oracle database or SQL Server to perform a complete backup of your production database.

   Production database backup includes, but is not limited to, complete export or backup of the Oracle Identity Manager Release 9.0.2 database instance to ensure that no data is lost during the upgrade process. If the upgrade fails, this backup can be used to restore the database to its original state.

2. Verify your database is properly configured by referring to the database vendor's documentation and the Oracle Identity Manager Installation and Upgrade Guide specific to your application server.

3. Upgrade your database schema from Oracle Identity Manager Release 9.0.2 to Release 9.0.3 by using the one of the following scripts appropriate for your database and operating system. Be sure to run the script on the machine where the database resides.

   Note:

   The oim_db_upg_902_to_903 script also upgrades the required stored procedures for Oracle.

   Oracle on UNIX:

   1. Run the following script on the system where the database for Oracle Identity Manager Release 9.0.2 is installed to upgrade the database schema:

      <PATCH>/db/oracle/Scripts/oim_db_upg_902_to_903.sh
      
      

   2. Enter the appropriate information for the Oracle database when prompted by the oim_db_upg_902_to_903.sh script.

   Oracle on Windows:

   Run the following batch script on the system where the Release 9.0.2 database is installed to upgrade the database schema:

   <PATCH>\db\oracle\Scripts\oim_db_upg_902_to_903.bat
   
   

   The following is the command line usage for the Oracle oim_db_upg_902_to_903.bat script:

   oim_db_upg_902_to_903.bat <ORACLE_SID> <ORACLE_HOME> <ORACLE_XELL_USER> <ORACLE_XELL_USER_PWD> <PATCH> 
   
   

   SQL Server:

   Run the <PATCH>\db\SQLServer\Scripts\upg_902_to_903.bat batch file. Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.

4. Perform the following steps to recompile the stored procedures for your database:

   Note:

   If you are using an Oracle database, you can skip this step as running the oim_db_upg_902_to_903 script already created the required stored procedures for Oracle.

   SQL Server:

   1. Launch a plain-text editor, then open:

      <PATCH>\db\SQLServer\StoredProcedures\compile_all_XL_SP.bat
      
      

   1. For every stored procedure listed in the Sequential Lists section of compile_all_XL_SP.bat, replace the string @sysuser with the database user name. This is necessary because SQL Server requires functions invoked from a stored procedure to be qualified by the database user name (owner). Be sure you replace the entire @sysuser string, including the @ character

   1. Run the following script:

      <PATCH>\db\SQLServer\StoredProcedures\compile_all_XL_SP.bat
      
      

      Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.

5. Perform the following steps appropriate for your database to upgrade the Oracle Identity Manager Audit and Compliance module:

   Oracle:

   1. Log in to SQL *Plus with the credentials of the Oracle Identity Manager Release 9.0.2 database schema owner.

   1. Run the following script:

      <PATCH>/db/oracle/Scripts/Oracle_Enable_XACM.sql
      
      

   SQL Server:

   Run the following script:

   <PATCH>\db\SQLServer\Scripts\SQLServer_Enable_XACM.bat
   
   

   Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.

6. The user profile auditing feature and the reports feature require that certain metadata be loaded into the database. As appropriate for the operating system on the machine hosting your Oracle Identity Manager server, load Oracle Identity Manager metadata into your database by executing one of the following commands:

   Windows:

   Run the following .bat file:

   <PATCH>\db\Utilities\LoadXML.bat
   
   

   UNIX:

   Run the following script:

   <PATCH>/db/Utilities/LoadXML.sh
   
   

   Refer to Appendix B, "Loading Metadata into the Database" for more information on executing this script.

Creating a New Database Instance for the Upgrade

In this approach, you create a new database instance for Release 9.0.3, then import the data used by your Release 9.0.2 deployment into that new database and perform the upgrade. This method ensures that your current working database remains available if a rollback is required. Use the following steps for creating a new, upgraded database instance:

1. Backup your existing database. As appropriate to your particular database, use the export/backup utilities provided with the Oracle database or SQL Server to perform a complete backup of your production database.

   Production database backup includes, but is not limited to, complete export or backup of the Oracle Identity Manager Release 9.0.2 database instance to ensure that no data is lost during the upgrade process. If the upgrade fails, this backup can be used to restore the database to its original state.

2. Create a new database by referring to the database vendor's documentation and the Oracle Identity Manager Installation and Upgrade Guide specific to your application server.

   Note:

   If you create a new database, be sure to specify the user name and password used by your original database instance as the credentials for your new database.

3. Using the import utility provided by your particular database, import the data you exported from your Release 9.0.2 database into your newly created Release 9.0.3 database. This creates an exact copy of your original database instance.

4. Upgrade your database schema from Oracle Identity Manager Release 9.0.2 to Release 9.0.3 by using the one of the following scripts appropriate for your database and operating system. Be sure to run the script on the machine where the database resides.

   Oracle on UNIX:

   Run the following script on the new Release 9.0.3 database system and enter the appropriate information when prompted to upgrade the database schema:

   <PATCH>/db/oracle/Scripts/oim_db_upg_902_to_903.sh
   

   Note:

   The oim_db_upg_902_to_903 script also upgrades the required stored procedures for Oracle.

   Oracle on Windows:

   Run the following batch script on the new Release 9.0.3 database system to upgrade the database schema:

   <PATCH>\db\oracle\Scripts\oim_db_upg_902_to_903.bat
   
   

   The following is the command line usage for the Oracle oim_db_upg_902_to_903.bat script:

   oim_db_upg_902_to_903.bat <ORACLE_SID> <ORACLE_HOME> <ORACLE_XELL_USER> <ORACLE_XELL_USER_PWD> <PATCH>
   
   

   SQL Server:

   Run the following script:

   <PATCH>\db\SQLServer\Scripts\upg_902_to_903.bat
   
   

   Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.

5. Perform the following steps to recompile the stored procedures for your database:

   Note:

   If you are using an Oracle database, you can skip this step as running the oim_db_upg_902_to_903 script already created the required stored procedures for Oracle.

   SQL Server:

   1. Launch a plain-text editor and open the following script:

      <PATCH>\db\SQLServer\StoredProcedures\compile_all_XL_SP.bat
      
      

   1. For every stored procedure listed in the Sequential Lists section of compile_all_XL_SP.bat, replace the string @sysuser with the database user name. This is necessary because SQL Server requires functions invoked from a stored procedure to be qualified by the database user name (owner). Be sure you replace the entire @sysuser string, including the @ character.

   1. Run the following script:

      <PATCH>\db\SQLServer\StoredProcedures\compile_all_XL_SP.bat
      
      

      Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.

6. Perform the following steps appropriate for your database to upgrade the Oracle Identity Manager Audit and Compliance module:

   Oracle:

   1. Log in to SQL *Plus with the credentials of the Oracle Identity Manager Release 9.0.2 database schema owner.

   1. Run the following script:

      <PATCH>/db/oracle/Scripts/Oracle_Enable_XACM.sql
      
      

   SQL Server:

   Run the following script:

   <PATCH>\db\SQLServer\Scripts\SQLServer_Enable_XACM.bat
   
   

   Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.

7. The user profile auditing feature and the reports feature require that certain metadata be loaded into the database. As appropriate for the operating system on the machine hosting your Oracle Identity Manager server, load Oracle Identity Manager metadata into your database by executing one of the following commands:

   Windows:

   Run the following script:

   <PATCH>\db\Utilities\LoadXML.bat
   
   

   UNIX:

   Run the following script:

   <PATCH>/db/Utilities/LoadXML.sh
   
   

   Refer to Appendix B, "Loading Metadata into the Database" for more information on executing this script.

Preparing for the Upgrade

Before you upgrade to Oracle Identity Manager Release 9.0.3, you must prepare for the upgrade by performing pre-upgrade configuration tasks on the following components:

• Oracle Identity Manager server

• Administrative and User Console

• Design Console

• Remote Manager

Preparing the Oracle Identity Manager Server for Upgrade

Prepare the Oracle Identity Manager server for upgrade to Release 9.0.3 by updating the Release 9.0.2 libraries, scripts, and configuration files using the information in this section.

Note:

If you are upgrading to Release 9.0.3 in a WebLogic cluster, perform the steps in this section on the Admin Server machine.

1. Extract the contents of the Oracle Identity Manager Release 9.0.3 upgrade package to a temporary directory on the machine where the Oracle Identity Manager Release 9.0.2 server is installed—this document refers to this temporary directory as <PATCH>.

2. Backup the following directories.

   • <XL_HOME>\xellerate\config

   • <XL_HOME>\xellerate\DDTemplates

   • <XL_HOME>\xellerate\lib

   • <XL_HOME>\xellerate\setup

   • <XL_HOME>\xellerate\webapp

   • <XL_HOME>\xellerate\ext

   • <XL_HOME>\xellerate\connectorResources

   • <XL_HOME>\documentation

3. Copy the directories and files listed in the location of the From column in the following table to the location listed in the To column in the following table. Overwrite the existing files in the To location if necessary.

   Table 3-1 Oracle Identity Manager Server Pre-Upgrade Files to Copy

   Copy From....	To
   <PATCH>\xellerate\DDTemplates\	<XL_HOME>\xellerate\DDTemplates\
   <PATCH>\xellerate\lib\	<XL_HOME>\xellerate\lib\
   <PATCH>\xellerate\webapp\	<XL_HOME>\xellerate\webapp\
   <PATCH>\documentation\	<XL_HOME>\documentation
   <PATCH>\xellerate\config\	<XL_HOME>\xellerate\config\
   <PATCH>\xellerate\ext\	<XL_HOME>\xellerate\ext\
   <PATCH>\xellerate\GTC\	<XL_HOME>\xellerate\GTC\
   <PATCH>\xellerate\connectorResources\	<XL_HOME>\xellerate\connectorResources\

   
   

4. Copy the following files from the <PATCH>\xellerate\setup directory to the <XL_HOME>\xellerate\setup directory:

   • setup.xml

   • patch_weblogic.cmd

   • patch_weblogic.sh

   • weblogic-setup.xml

   • setup_wl_server.xml

5. Edit the patch_weblogic script specific to your operating system in the <XL_HOME>/xellerate/setup/ directory (edit patch_weblogic.cmd for Windows or edit patch_weblogic.sh for UNIX). Make the following changes:

   • Replace @bea_home with the path to the WebLogic installation directory

   • Replace @loc with the path to the Oracle Identity Manager server installation directory

6. Update your existing Release 9.0.2 Oracle Identity Manager server xlconfig.xml configuration file in the <XL_HOME>/xellerate/config/ directory with the new cache related setting for Release 9.0.3. Perform the following steps:

   1. Open the <XL_HOME>/xellerate/config/xlconfig.xml file and locate the <xl-configuration>< Cache> parameter.

   2. Add the following XML entry before the </Cache> parameter:

      <LinguisticSort>
               <Enable>true</Enable>
               <ExpireTime>-1</ExpireTime>
      </LinguisticSort>
      
      

Preparing the Administrative and User Console for Upgrade

Several Administrative and User Console files were modified in Release 9.0.3. If you customized your Release 9.0.2 Administrative and User Console, that is, you made changes to the default, stock Administrative and User Console that shipped with Release 9.0.2, you must add your customizations into the new Release 9.0.3 Administrative and User Console files.

Refer to Appendix C, "Upgrading Customized Administrative and User Consoles" if you customized your Release 9.0.2 Administrative and User Console.

If you did not customize your Release 9.0.2 Administrative and User Console, skip this section and continue the upgrade process by referring to Preparing the Design Console for Upgrade.

Preparing the Design Console for Upgrade

Prepare the Oracle Identity Manager Design Console for upgrade to Release 9.0.3 by updating your Release 9.0.2 Design Console libraries, scripts, and configuration files using the following steps:

1. Backup the following files and directories:

   • <XL_DC_HOME>\xlclient\XLDesktopClient.ear

   • <XL_DC_HOME>\xlclient\CustomClient.zip

   • <XL_DC_HOME>\xlclient\xlFvcUtil.ear

   • <XL_DC_HOME>\xlclient\lib

   • <XL_DC_HOME>\xlclient\ext

   • <XL_DC_HOME>\documentation

   • <XL_DC_HOME>\xlclient\fvcutil.cmd

2. Copy the directories and files listed in the location of the From column in the following table to the location listed in the To column in the following table. Overwrite the existing files in the To location if necessary.

   Table 3-2 Oracle Identity Manager Design Console Pre-Upgrade Files to Copy

   Copy From....	To
   <PATCH>\xlclient\XLDesktopClient.ear	<XL_DC_HOME>\xlclient\
   <PATCH>\xlclient\CustomClient.zip	<XL_DC_HOME>\xlclient\
   <PATCH>\xlclient\xlFvcUtil.ear	<XL_DC_HOME>\xlclient\
   <PATCH>\xlclient\lib\	<XL_DC_HOME>\xlclient\lib\
   <PATCH>\xlclient\ext\	<XL_DC_HOME>\xlclient\ext\
   <PATCH>\xlclient\fvcutil.cmd	<XL_DC_HOME>\xlclient\
   <PATCH>\documentation\	<XL_DC_HOME>\documentation\

   
   

Preparing the Remote Manager for Upgrade

Prepare the Oracle Identity Manager Remote Manager for upgrade to Release 9.0.3 by updating your Release 9.0.2 Remote Manager libraries, scripts, and configuration files using the following steps:

1. Backup the <XL_RM_HOME>\xlremote\lib\ directory.

2. Copy the contents of the <PATCH>\xlremote\lib\ directory to the <XL_RM_HOME>\xlremote\lib\ directory, overwriting files if necessary.

Performing the Upgrade

Upgrading from an existing Oracle Identity Manager Release 9.0.2 deployment to Oracle Identity Manager Release 9.0.3 involves assembling a new enterprise application archive (EAR) file from the latest libraries, then redeploying the EAR.

Use the steps in one of the following sections appropriate to your deployment to upgrade to Release 9.0.3 on WebLogic:

• Upgrading A Single WebLogic Application Server

• Upgrading A WebLogic Cluster

Upgrading A Single WebLogic Application Server

Perform the following steps to upgrade to Release 9.0.3 on a single WebLogic application server:

1. Make sure the WebLogic application server is running.

2. Log in to the WebLogic Admin Console.

3. Click Deployment and then click Applications.

4. Remove the Xellerate and Nexawebb application deployments by clicking the Remove button for each application.

5. Shutdown the WebLogic application server gracefully.

6. Delete all the files in the <BEA_HOME>\user_projects\domains\<Name_of_domain_directory>\XLApplications directory.

7. Upgrade to the WebLogic 8.1 with SP6 application server using the following steps:

   1. Use the WebLogic application server documentation for details on backing up your existing WebLogic deployment and then upgrading to WebLogic 8.1 with SP6.

      Note:

      While upgrading to WebLogic 8.1 SP6 application server you should review the information about the BEA Patch for 2007 Daylight Savings Time Changes for the United States. Go to the Customer Support News section of the BEA eSupport Web site at:

      http://support.bea.com/

   2. After completing the upgrade to WebLogic 8.1 with SP6, open the following files in a text editor and change the JAVA_HOME variable to point to <BEA_HOME>\jdk1.4.2_11:

      Change the JAVA_HOME Variable in These Files
      <BEA_HOME>\weblogic81\common\bin\commEnv.<cmd or sh>
      <BEA_HOME>\weblogic81\server\bin\ant
      <Name_of_domain_directory>\setEnv.<cmd or sh>
      <Name_of_domain_directory>\startWebLogic.<cmd or sh>

      
      

   3. Rename the jdk1.4.2_05 directory used for Release 9.0.2 to something like OLD_jdk1.4.2_05 or LEGACY_jdk1.4.2_05 to avoid confusion when executing and troubleshooting the upgrade scripts.

8. Start the WebLogic application server.

9. If you are using SQL Server as your database, verify the following files have been added to the CLASSPATH:

   • mssqlserver.jar

   • msbase.jar

   • msutil.jar

10. Copy <PATCH>\xellerate\ext\ojdbc14.jar to the <BEA_HOME>\weblogic81\server\lib\ directory and overwrite the existing file if necessary.

11. Run one of the following patch_weblogic scripts on the application server:

    Windows:

    Run <XL_HOME>\xellerate\setup\patch_weblogic.cmd using the WebLogic administrator's password and the Oracle Identity Manager database user's password as command arguments, for example:

    <XL_HOME>\xellerate\setup\patch_weblogic.cmd <WebLogic_admin_password> <database_user_password>
    
    

    UNIX:

    Run <XL_HOME>/xellerate/setup/patch_weblogic.sh using the WebLogic administrator's password and the Oracle Identity Manager database user's password as command arguments, for example:

    $ <XL_HOME>/xellerate/setup/patch_weblogic.sh -<WebLogic_admin_password> -<database_user_password>
    
    

12. Select Security, then select Realms, then select myrealm, then select Providers, and then select Authentication.

13. Delete the XellerateAuthenticator.

14. Shutdown the WebLogic application server gracefully.

15. Copy <XL_HOME>\xellerate\lib\wlXLSecurityProviders.jar to the <BEA_HOME>\weblogic81\server\lib\mbeantypes\ directory.

16. Start the Weblogic application server.

17. Select Security, then select Realms, then select myrealm, then select Providers, then select Authentication, then select Configure a new OIMAuthenticator... and create a OIMAuthenticator with the SUFFICIENT Control Flag.

18. Shutdown the WebLogic application server gracefully.

19. Start the WebLogic application server.

Upgrading A WebLogic Cluster

Perform the following steps to upgrade to Release 9.0.3 on a WebLogic cluster:

1. Log in to the WebLogic Admin Console.

2. Shutdown all Managed Servers gracefully.

3. Click Deployment and then click Applications.

4. Remove the Xellerate and Nexawebb application deployments by clicking the Remove button for each application.

5. Delete all the files in the <BEA_HOME>\user_projects\domains\<Name_of_domain_directory>\XLApplications directory on each node in the cluster.

6. Delete the following folders on each node in the cluster:

   • <BEA_HOME>\weblogic81\common\nodemanager\<Name_of_server_directory>\stage\xellerate

   • <BEA_HOME>\weblogic81\common\nodemanager\<Name_of_server_directory>\stage\Nexaweb

7. Upgrade to the WebLogic 8.1 with SP6 application server using the following steps:

   1. Use the WebLogic application server documentation for details on backing up your existing WebLogic deployment and then upgrading to WebLogic 8.1 with SP6.

      Note:

      While upgrading to WebLogic 8.1 SP6 application server you should review the information about the BEA Patch for 2007 Daylight Savings Time Changes for the United States. Go to the Customer Support News section of the BEA eSupport Web site at:

      http://support.bea.com/

   2. After completing the upgrade to WebLogic 8.1 with SP6, open the following files in a text editor and change the JAVA_HOME variable to point to <BEA_HOME>\jdk1.4.2_11:

      Change the JAVA_HOME Variable in These Files
      <BEA_HOME>\weblogic81\common\bin\commEnv.<cmd or sh>
      <BEA_HOME>\weblogic81\server\bin\ant (on the Admin server only)
      <Name_of_domain_directory>\setEnv.<cmd or sh>
      <Name_of_domain_directory>\startWebLogic.<cmd or sh>

      
      

   3. Rename the jdk1.4.2_05 directory used for Release 9.0.2 to something like OLD_jdk1.4.2_05 or LEGACY_jdk1.4.2_05 to avoid confusion when executing and troubleshooting the upgrade scripts.

8. Start the Admin Server.

9. In the WebLogic Admin Console, ensure the following fields and values are set on the Remote Start tab for all Managed Servers:

   • Java Home: <BEA_HOME>\jdk1.4.2_11

   • Bea Home: <BEA_HOME>

10. Make sure all Managed Servers are running.

11. Ensure the Listen Address field on the Configuration tab for all Managed Servers contains the Host Address.

12. If you are using SQL Server as your database, verify the following files have been added to the Class Path field in the Remote Start tab of all Managed Servers:

    • mssqlserver.jar

    • msbase.jar

    • msutil.jar

13. Copy <PATCH>\xellerate\ext\ojdbc14.jar to the <BEA_HOME>\weblogic81\server\lib\ directory on all cluster participants—including the Admin Server, and overwrite the existing files if necessary.

14. Run one of the following patch_weblogic scripts on the Admin Server:

    Windows:

    Run <XL_HOME>\xellerate\setup\patch_weblogic.cmd using the WebLogic administrator's password and the Oracle Identity Manager database user's password as command arguments, for example:

    <XL_HOME>\xellerate\setup\patch_weblogic.cmd <WebLogic_admin_password> <database_user_password>
    
    

    UNIX:

    Run <XL_HOME>/xellerate/setup/patch_weblogic.sh using the WebLogic administrator's password and the Oracle Identity Manager database user's password as command arguments, for example:

    $ <XL_HOME>/xellerate/setup/patch_weblogic.sh -<WebLogic_admin_password> -<database_user_password>
    
    

15. Stop the cluster and gracefully shutdown all Managed Servers in the cluster by right-clicking on the name of the cluster, selecting Start/Stop this cluster, and then selecting the Graceful shutdown of all Managed Servers... option in the right pane.

16. Select Security, then select Realms, then select myrealm, then select Providers, and then select Authentication.

17. Delete the XellerateAuthenticator.

18. Shutdown the WebLogic Admin Server gracefully.

19. Copy <XL_HOME>\xellerate\lib\wlXLSecurityProviders.jar to the <BEA_HOME>\weblogic81\server\lib\mbeantypes\ directory on the Admin Server.

20. Start the WebLogic Admin Server.

21. Select Security, then select Realms, then select myrealm, then select Providers, then select Authentication, then select Configure a new OIMAuthenticator... and create a OIMAuthenticator with the SUFFICIENT Control Flag.

22. Shutdown the WebLogic Admin Server gracefully.

23. Start the WebLogic Admin Server.

24. Copy the <XL_HOME> directory from the Admin Server to all Managed Servers while maintaining the same directory structure.

25. Copy <XL_HOME>\xellerate\lib\wlXLSecurityProviders.jar to the <BEA_HOME>\weblogic81\server\lib\mbeantypes\ directory on all Managed Servers in the cluster, overwriting the existing files.

26. Copy <XL_HOME>\xellerate\lib\nexaweb-common.jar to the <BEA_HOME>\weblogic81\server\lib\ directory on all Managed Servers in the cluster, overwriting the existing files.

27. Start the cluster.

Migrating Release 9.0.2 Custom Code

You can recycle custom code used in your Release 9.0.2 environment into your newly upgraded Release 9.0.3 environment.

Note:

Before you migrate custom code from the Release 9.0.2 environment, you must first recompile the custom code using the Oracle Identity Manager Release 9.0.3 libraries.

The following is a list of the customized items you can migrate from your Release 9.0.2 environment and reuse in Release 9.0.3 after recompiling using the Release 9.0.3 libraries:

Note:

For clustered environments, after recompiling the following customized items using the Release 9.0.3 libraries, copy the recompiled code to the remaining participants in the cluster.

• Custom java code recompiled using the integrated development environment (that is, Eclipse, JDeveloper, WASD or command line javac) and Release 9.0.3 libraries.

• Custom java libraries bound to functional Oracle Identity Manager Release 9.0.2 adapters recompiled using Release 9.0.3 libraries. You do not need to recompile the adapters.

• Custom scheduled tasks recompiled using Release 9.0.3 libraries.

• Custom event handlers recompiled using Release 9.0.3 libraries.

• Custom clients that were built using Oracle Identity Manager Release 9.0.2 APIs must be updated to make them compatible with the Oracle Identity Manager Release 9.0.3 APIs.

  For example, certain APIs might have been deprecated and replaced by new APIs. Refer to the Oracle Identity Manager Release 9.0.3 Release Notes for information on API changes between Oracle Identity Manager Release 9.0.2 and Release 9.0.3.

Upgrading the Diagnostic Dashboard

You must remove the existing Release 9.0.2 Diagnostic Dashboard XIMDD application before upgrading to the Release 9.0.3 Diagnostic Dashboard on WebLogic. Use the following steps:

1. Remove the existing XIMDD application using the Admin Console.

2. Install a new instance of the XIMDD application using the Release 9.0.3 XIMDD.war file in the <PATCH>\DiagnosticDashboard directory.

   Refer to the "Installing the Diagnostic Dashboard" section in the "Working with the Diagnostic Dashboard" chapter in the Oracle Identity Manager Administrative and User Console Guide for complete steps on how to install the Diagnostic Dashboard on your application server.

Post-Upgrade Configuration

After completing the upgrade to Release 9.0.3, refer to the Post-Installation Configuration for Oracle Identity Manager and WebLogic chapter in the Oracle Identity Manager Installation Guide for WebLogic to verify your upgraded Release 9.0.3 environment is configured correctly.