3 Upgrading to Release 9.1.0 on BEA WebLogic Server

This chapter explains how to upgrade to Oracle Identity Manager release 9.1.0 from release 9.0.1.5 on BEA WebLogic Server. Do not attempt to upgrade to release 9.1.0 from any other previous Oracle Identity Manager release.

Run the contents of the release 9.1.0 upgrade package to a temporary directory on your existing release 9.0.1.5 system.

The following steps (detailed in this chapter) explain how to upgrade from release 9.0.1.5 to release 9.1.0 on BEA WebLogic Server:

1. Creating a Backup of the Existing Deployment

2. Upgrading the Oracle Identity Manager Database

3. Preparing for the Upgrade from Release 9.0.1.5 to Release 9.1.0

   1. Preparing Oracle Identity Manager for Upgrade

   2. Preparing and Upgrading the Design Console

   3. Preparing and Upgrading the Remote Manager

4. Performing the Upgrade from Release 9.0.1.5 to Release 9.1.0

5. Migrating Custom Java Code

6. Postupgrade Configuration

7. Upgrading the Diagnostic Dashboard

3.1 Creating a Backup of the Existing Deployment

The first step for upgrading to release 9.1.0 is to create a backup of your existing release 9.0.1.5 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.1.5 deployment to its original state.

You must create a backup of the following:

• Oracle Identity Manager

  Back up the OIM_HOME directory in which you have installed Oracle Identity Manager.

• Oracle Identity Manager Design Console

  Back up the OIM_DC_HOME directory in which you have installed the Oracle Identity Manager Design Console.

• Back up BEA WebLogic Server

  Back up BEA WebLogic Server domain directory, for example, the C:\bea\user_projects\domains\mydomain directory. Also back up the BEA_HOME/weblogic81/server/lib/ directory.

  Note:

  For a clustered installation, repeat this step on each node of the cluster.

• Oracle Identity Manager Remote Manager

  Back up the OIM_RM_HOME directory in which you have installed the Oracle Identity Manager Remote Manager.

• Database used for release 9.0.1.5

  Follow the standard backup procedure for the database.

3.2 Upgrading the Oracle Identity Manager Database

For details about upgrading the Oracle Identity Manager database, refer to Chapter 5, "Upgrading the Oracle Identity Manager Database".

3.3 Preparing for the Upgrade from Release 9.0.1.5 to Release 9.1.0

Before you upgrade to Oracle Identity Manager release 9.1.0, you must prepare for the upgrade by performing preupgrade configuration tasks on the following:

• Oracle Identity Manager

• Design Console

• Remote Manager

3.3.1 Preparing Oracle Identity Manager for Upgrade

Prepare Oracle Identity Manager for upgrade to release 9.1.0 by updating the release 9.0.1.5 libraries, scripts, and configuration files. To do so:

Note:

If you are upgrading to release 9.1.0 in a WebLogic cluster, then perform the steps in this section on the WebLogic Admin Server computer.

1. For upgrading from release 9.0.1.5, extract the contents of the Oracle Identity Manager release 9.1.0 upgrade package to a temporary directory on the computer in which the Oracle Identity Manager release 9.0.1.5 is installed.

   Note:

   This guide refers to this temporary directory as PATCH.

2. Back up the OIM_HOME directory.

3. Copy the directories and files listed in the location of the From column to the location listed in the To column in Table 3-1.

   Overwrite the existing files in the To location if necessary.

   Note:

   Delete the release 9.0.1.5 files in the OIM_HOME/documentation/ directory before copying the release 9.1.0 files from PATCH/documentation/.

   Table 3-1 Oracle Identity Manager Preupgrade Files to Copy

   From	To
   PATCH/documentation/	OIM_HOME/documentation/
   PATCH/readme.html	OIM_HOME
   PATCH/xellerate/bin/	OIM_HOME/xellerate/bin/
   PATCH/xellerate/config/	OIM_HOME/xellerate/config/
   PATCH/xellerate/ConnectorDefaultDirectory/	OIM_HOME/xellerate/ConnectorDefaultDirectory/
   PATCH/xellerate/connectorResources/	OIM_HOME/xellerate/connectorResources/
   PATCH/xellerate/customResources/	OIM_HOME/xellerate/customResources/
   PATCH/xellerate/DDTemplates/	OIM_HOME/xellerate/DDTemplates/
   PATCH/xellerate/ext/	OIM_HOME/xellerate/ext/
   PATCH/xellerate/GTC/	OIM_HOME/xellerate/GTC/
   PATCH/xellerate/JavaTasks/	OIM_HOME/xellerate/JavaTasks/
   PATCH/xellerate/lib/	OIM_HOME/xellerate/lib/
   PATCH/xellerate/SPMLWS/	OIM_HOME/xellerate/SPMLWS/
   PATCH/xellerate/webapp/	OIM_HOME/xellerate/webapp/

   
   

   Note:

   While copying the PATCH/xellerate/lib/ directory, do not copy xlAttestationUpgrade.jar. Copy it only before running the UpgradeAttestation script.

4. Copy the following files from the PATCH/xellerate/setup/ directory to the OIM_HOME/xellerate/setup/ directory according to the Oracle Identity Manager installation:

   • setup.xml

   • patch_weblogic.cmd

   • patch_weblogic.sh

   • weblogic-setup.xml

   • setup_wl_server.xml

   • spml_weblogic.sh

   • spml_weblogic.cmd

   • UpgradeAttestation.sh

   • UpgradeAttestation.cmd

5. Update your existing release 9.0.1.5 Oracle Identity Manager xlconfig.xml configuration file in the OIM_HOME/xellerate/config/ directory with the new cache-related setting for release 9.1.0. To do so:

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

   2. After </ProcessDefinition>, add the following:

      <EmailDefinition>
                  <Enable>false</Enable>
                  <ExpireTime>14400</ExpireTime>
      </EmailDefinition>
      

   3. Change:

      <ServerProperties>
                  <Enable>false</Enable>
                  <ExpireTime>14400</ExpireTime>
      </ServerProperties>
      

      To:

      <ServerProperties>
                  <Enable>true</Enable>
                  <ExpireTime>14400</ExpireTime>
      </ServerProperties>
      

   4. After </ColumnMetaData>, add the following:

      <!-- API Data -->
      <API>
                  <Enable>false</Enable>
                  <ExpireTime>14400</ExpireTime>
      </API>
      <CustomResourceBundle>
                  <Enable>true</Enable>
                  <ExpireTime>-1</ExpireTime>
      </CustomResourceBundle>
      <CustomDefaultBundle>
                  <Enable>true</Enable>
                  <ExpireTime>-1</ExpireTime>
      </CustomDefaultBundle>
      <ConnectorResourceBundle>
                  <Enable>true</Enable>
                  <ExpireTime>-1</ExpireTime>
      </ConnectorResourceBundle>
      <LinguisticSort>
                  <Enable>true</Enable>
                  <ExpireTime>-1</ExpireTime>
      </LinguisticSort>
      <GenericConnector>
                  <Enable>true</Enable>
                  <ExpireTime>-1</ExpireTime>
      </GenericConnector>
      
      <GenericConnectorProviders>
                  <Enable>true</Enable>
                  <ExpireTime>-1</ExpireTime>
      </GenericConnectorProviders>
      

   5. After </AttestationTaskMessage>, add the following:

      <AttestationTaskDetailMessage>com.thortech.xl.schedule.jms.attestation.processOfflinedAttestationTaskDetails</AttestationTaskDetailMessage>
      

      Note:

      The aforementioned line of code must be entered as a single line without any line breaks.

   6. Inside:

      <recon_offline_queue>
      

      Replace:

      <queueName>queue/xlQueue</queueName>
      

      With:

      <queueName>queue/xlReconQueue</queueName>
      

   7. Inside:

      <auditor_offline_queue>
      

      Replace:

      <queueName>queue/xlQueue</queueName>
      

      With:

      <queueName>queue/xlAuditQueue</queueName>
      

   8. Inside:

      <attestation_request_queue>
      

      Replace:

      <queueName>queue/xlQueue</queueName>
      

      With:

      <queueName>queue/xlAttestationQueue</queueName>
      

   9. Inside:

      <attestation_task_queue>
      

      Replace:

      <queueName>queue/xlQueue</queueName>
      

      With:

      <queueName>queue/xlAttestationQueue</queueName>
      

   10. Inside:

       <attestation_workflow_task_queue>
       

       Replace:

       <queueName>queue/xlQueue</queueName>
       

       With:

       <queueName>queue/xlAttestationQueue</queueName>
       

   11. Inside:

       <process_offline_queue>
       

       Replace:

       <queueName>queue/xlQueue</queueName>
       

       With:

       <queueName>queue/xlProcessQueue</queueName>
       

   12. Inside:

       <process_task_offline_queue>
       

       Replace:

       <queueName>queue/xlQueue</queueName>
       

       With:

       <queueName>queue/xlProcessQueue</queueName>
       

   13. After </attestation_task_queue> add the following:

       <attestation_task_detail_queue>
                   <queueName>queue/xlAttestationQueue</queueName>
                   <autoAcknowledge>true</autoAcknowledge>
                   <replyTo></replyTo>
                   <persistentFlag>true</persistentFlag>
                   <disableMessageId>true</disableMessageId>
                   <disableTimeStampe>false</disableTimeStampe>
                   <messageEncrypt>false</messageEncrypt>
       </attestation_task_detail_queue>
       

3.3.2 Preparing and Upgrading the Design Console

Prepare the Oracle Identity Manager Design Console for upgrade to release 9.1.0 by updating your release 9.0.1.5 Design Console libraries, scripts, and configuration files. To do so:

1. Back up the OIM_DC_HOME directory.

2. Copy the directories and files listed in the location of the From column to the location listed in the To column in Table 3-2.

   Overwrite the existing files in the To location if necessary.

   Note:

   Delete the release 9.0.1.5 files in the OIM_DC_HOME/documentation/ directory before copying the release 9.1.0 files from the PATCH/documentation/ directory.

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

   From	To
   PATCH/xlclient/XLDesktopClient.ear	OIM_DC_HOME/xlclient/
   PATCH/readme.html	OIM_DC_HOME/xlclient/
   PATCH/xlclient/CustomClient.zip	OIM_DC_HOME/xlclient/
   PATCH/xlclient/xlFvcUtil.ear	OIM_DC_HOME/xlclient/
   PATCH/xlclient/lib/	OIM_DC_HOME/xlclient/lib/
   PATCH/documentation/	OIM_DC_HOME/documentation/
   PATCH/xellertate/ext/	OIM_DC_HOME/ext/

   
   

3. Edit the OIM_DC_HOME/xlclient/classpath.bat file and add the following string to the end of CLASSPATH:

   ".\ext\oscache.jar;.\ext\commons-logging.jar;.\ext\javagroups-all.jar"
   

4. Specify the multicast address in the xlconfig.xml file of the Design Console as follows:

   1. Open the OIM_DC_HOME/xlclient/Config/xlconfig.xml file in a text editor.

   2. Add the following lines before the </xl-configuration> tag:

      <!--  Value of MultiCastAddress must be the same as that of Oracle Identity Manager -->
      <Cache>
        <XLCacheProvider>
          <MultiCastAddress>MULTICASTADDRESS_VALUE</MultiCastAddress>
        </XLCacheProvider>
      </Cache>
      

   3. Change MULTICASTADDRESS_VALUE to the value of the multicast address for Oracle Identity Manager.

Note:

After the server and Design Console are upgraded, go to Adapter Manager on the Design Console and recompile all the adapters.

3.3.3 Preparing and Upgrading the Remote Manager

To prepare the Oracle Identity Manager Remote Manager for the upgrade to release 9.1.0 by updating your release 9.0.1.5 Remote Manager libraries, scripts, and configuration files. To do so:

1. Create a backup of the OIM_RM_HOME/xlremote/lib/ directory.

2. Copy the contents of the PATCH/xlremote/lib/ directory to the OIM_RM_HOME/xlremote/lib/ directory by overwriting the files if necessary.

3.3.4 Undeploy Applications

You must manually undeploy the applications running on BEA WebLogic Server before upgrading Oracle Identity Manager. To do so:

1. Login to the WebLogic Administrative Console.

2. In the left pane, go to Deployments, Applications, and then to Nexaweb.

3. In the right pane, click the Deploy tab, and then click Stop Application.

4. In the left pane, go to Deployments, Applications, and then to Xellerate.

5. In the right pane, click the Deploy tab, and then click Stop Application.

6. In the left pane, go to Deployment, and then to Applications.

7. Click Delete to delete the Nexaweb application. Click Yes to confirm the deletion.

8. In the left pane, go to Deployments, and then to Applications.

9. Click Delete to delete the Xellerate application. Click Yes to confirm the deletion.

10. Restart BEA WebLogic Server.

    Note:

    For a clustered installation, restart all the application servers including the Admin server after deleting the applications from the WebLogic Administrative Console.

3.3.5 Multiple JMS Queues

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 usage in future Oracle Identity Manager releases

This section provides details that help to create the additional JMS queues.

For a nonclustered installation, implement only the changes mentioned in "Creating JMS Queues for JMS Server (For Noncluster Installation Only)".

For a clustered installation, implement only the changes mentioned in the following sections:

• Creating JMS Queues for JMS Servers (For Clustered Installation Only)

• Creating JMS Distributed Queues (For Clustered Installation Only)

3.3.5.1 Creating JMS Queues for JMS Server (For Noncluster Installation Only)

To create JMS queues for JMS server:

1. Log in to the WebLogic Administrative Console.

2. Navigate to Services, JMS, and then to Servers.

3. Expand the tree for the xlJMSServer.

4. Click Destinations.

5. Click the Clone icon for xlQueue.

6. Enter the values for Name and JNDI name as follows:

   • Name: xlReconQueue

   • JNDI Name: queue/xlReconQueue

7. Click Clone, and then click the Redelivery tab.

8. Select the Error Destination that starts with queue/xlErrorQueue.

9. Repeat steps 4 through 8 with the following Name and JNDI Name values:

   • Name: xlAuditQueue

   • JNDI Name: queue/xlAuditQueue

   • Name: xlAttestationQueue

   • JNDI Name: queue/xlAttestationQueue

   • Name: xlProcessQueue

   • JNDI Name: queue/xlProcessQueue

3.3.5.2 Creating JMS Queues for JMS Servers (For Clustered Installation Only)

To create JMS queues for JMS servers:

1. Log in to the WebLogic Administrative Console.

2. Go to Services, JMS, and then Servers.

3. Expand the tree for the xlJMSServer JMS server that starts with xlJMSServer SERVER_NAME.

4. Click Destinations.

5. Click the Clone icon for xlQueue SERVER_NAME.

6. Enter the values for Name and JNDI Name as follows:

   • Name: xlReconQueue SERVER_NAME

   • JNDI Name: queue/xlReconQueue SERVER_NAME

7. Click the Clone icon, and then click the Redelivery tab.

8. Select the Error Destination that starts with queue/xlErrorQueue SERVER_NAME.

9. Repeat steps 4 through 8 with the following Name and JNDI Name values:

   • Name: xlAuditQueue SERVER_NAME

   • JNDI Name: queue/xlAuditQueue SERVER_NAME

   • Name: xlAttestationQueue SERVER_NAME

   • JNDI Name: queue/xlAttestationQueue SERVER_NAME

   • Name: xlProcessQueue SERVER_NAME

   • JNDI Name: queue/xlProcessQueue SERVER_NAME

10. Repeat steps 3 through 9 for all available JMS servers starting with XlJMSServer SERVER_NAME.

3.3.5.3 Creating JMS Distributed Queues (For Clustered Installation Only)

To create JMS distributed queues only for clustered installation:

1. Login in to the WebLogic Administrative Console.

2. Go to Services, JMS, and then to Distributed Destination.

3. Click Configure a new Distributed Queue...

4. Enter the values for Name and JNDI Name as follows:

   • Name: xlReconQueue

   • JNDI Name: queue/xlReconQueue

5. Click Create at the bottom of the page.

6. Click the Members tab, and then click the Configure a new Distributed Queue Member link.

7. Provide the following details:

   • Name: Specify the name as SERVER_NAME_queue_member

   • JMS Queue: Select xlReconQueue SERVER_NAME

8. Repeat steps 6 and 7 for the available servers. For example, for two managed servers (XL_SERVER1, XL_SERVER2) in the cluster, create the distributed queue members as listed in the following table:

   Name	JMS Queue Name
   XL_SERVER1_queue_member	xlReconQueueXL_SERVER1
   XL_SERVER2_queue_member	xlReconQueueXL_SERVER2

   
   

9. Click Configure a new Distributed Queue...

10. Enter the values for Name and JNDI Name as follows:

    • Name: xlAuditQueue

    • JNDI Name: queue/xlAuditQueue

11. Clcik Create at the bottom of the page.

12. Click the Members tab, and then click the Configure a new Distributed Queue Member link.

13. Provide the following details:

    • Name: Specify the name as SERVER_NAME_queue_member

    • JMS Queue: Select xlAuditQueue SERVER_NAME

14. Repeat steps 12 and 13 for the available servers. For example, for two managed servers (XL_SERVER1, XL_SERVER2) in the cluster, create the distributed queue members as listed in the following table:

    Name	JMS Queue Name
    XL_SERVER1_queue_member	xlAuditQueueXL_SERVER1
    XL_SERVER2_queue_member	xlAuditQueueXL_SERVER2

    
    

15. Click Configure a new Distributed Queue...

16. Enter the values for Name and JNDI Name as follows:

    • Name: xlAttestationQueue

    • JNDI Name: queue/xlAttestationQueue

17. Clcik Create at the bottom of the page.

18. Click the Members tab, and then click the Configure a new Distributed Queue Member link.

19. Provide the following details:

    • Name: Specify the name as SERVER_NAME_queue_member

    • JMS Queue: Select xlAttestationQueue SERVER_NAME

20. Repeat steps 18 and 19 for the available servers. For example, for two managed servers (XL_SERVER1, XL_SERVER2) in the cluster, create the distributed queue members as listed in the following table:

    Name	JMS Queue Name
    XL_SERVER1_queue_member	xlAttestationQueueXL_SERVER1
    XL_SERVER2_queue_member	xlAttestationQueueXL_SERVER2

    
    

21. Click Configure a new Distributed Queue...

22. Enter the values for Name and JNDI Name as follows:

    • Name: xlProcessQueue

    • JNDI Name: queue/xlProcessQueue

23. Click Create at the bottom of the page.

24. Click the Members tab, and then click the Configure a new Distributed Queue Member link.

25. Provide the following details:

    • Name: Specify the name as SERVER_NAME_queue_member

    • JMS Queue: Select xlProcessQueue SERVER_NAME

26. Repeat steps 24 and 25 for the available servers. For example, for two managed servers (XL_SERVER1, XL_SERVER2) in the cluster, create the distributed queue members as listed in the following table:

    Name	JMS Queue Name
    XL_SERVER1_queue_member	xlProcessQueueXL_SERVER1
    XL_SERVER2_queue_member	xlProcessQueueXL_SERVER2

    
    

3.4 Performing the Upgrade from Release 9.0.1.5 to Release 9.1.0

Upgrading from an existing Oracle Identity Manager release 9.0.1.5 deployment to Oracle Identity Manager release 9.1.0 involves assembling a new enterprise application archive (EAR) file from the latest libraries, and then redeploying the EAR file.

Perform the following steps to upgrade to release 9.1.0 on a single BEA WebLogic Server installation and WebLogic cluster:

To upgrade from release 9.0.1.5:

1. Install the JDK version that is supported with Oracle Identity Manager release 9.1.0 for BEA WebLogic Server.

   See Also:

   Oracle Identity Manager Installation and Configuration Guide for BEA Weblogic Server for more information about installing JDK for BEA WebLogic Server

2. Stop BEA WebLogic Server.

3. Navigate to BEA_HOME\user_projects\domains\NAME_OF_DOMAIN_DIRECTORY. For example, C:\bea\user_projects\domains\mydomain.

4. In a text editor, open the WebLogic start script file. The start script is:

   • For Microsoft Windows:

     startWebLogic.cmd
     

   • For UNIX:

     startWebLogic.sh
     

5. JVM memory settings must be changed for production environments and when processing a large volume of data in nonproduction environments. Edit the script to specify memory options as follows:

   For Microsoft Windows, locate the line that starts with the following:

   %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS%
   

   Add either of the following lines just before it:

   • If Sun JVM is used:

     set MEM_ARGS=-Xms1280m -Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m
     

   • If BEA JRockit JVM is used:

     set MEM_ARGS=-Xms1280m -Xmx1280m
     

   For UNIX, locate the line that starts with the following:

   $JAVA_HOME/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}
   

   Add either of the following lines just before it:

   • If Sun JVM is used:

     MEM_ARGS="-Xms1280m -Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m"
     export MEM_ARGS
     

   • If BEA JRockit JVM is used:

     MEM_ARGS="-Xms1280m -Xmx1280m"
     export MEM_ARGS
     

6. If BEA JRockit JVM is being used, add the -XnoOpt option to the existing JAVA_OPTIONS. This option turns off adaptive optimization and is required for stable Oracle Identity Manager operation.

   For Microsoft Windows, locate the line that starts with the following:

   %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS%
   

   Add the following line just before it:

   set JAVA_OPTIONS=%JAVA_OPTIONS% -XnoOpt
   

   For UNIX, locate the line that starts with the following:

   $JAVA_HOME/bin/java ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS}
   

   Add the following line just before it:

   JAVA_OPTIONS="$JAVA_OPTIONS -XnoOpt"
   export JAVA_OPTIONS
   

7. Save and close the file.

8. In a text editor, open the following files and change the JAVA_HOME and JAVA_VENDOR variables to point to the newly installed JDK directory:

   • BEA_HOME/weblogic81/common/bin/commEnv.cmd or commEnv.sh

   • BEA_HOME/weblogic81/server/bin/ant.bat or ant.sh

   • BEA_HOME/user_projects/domains/NAME_OF_DOMAIN_DIRECTORY/setEnv.cmd or setEnv.sh

   • BEA_HOME/user_projects/domains/NAME_OF_DOMAIN_DIRECTORY/startWebLogic.cmd or startWebLogic.sh

   Rename the jdk1.4.2_11 directory used for release 9.0.1.5 to OLD_jdk1.4.2_11 or LEGACY_jdk1.4.2_11 to avoid confusion when running and troubleshooting the upgrade scripts.

9. Edit the scripts specific to your operating system in the OIM_HOME/xellerate/setup/ directory as listed in Table 3-3.

   Table 3-3 WebLogic Upgrade Patch Scripts and Parameters to Edit

   Operating System	Script to Edit	Parameter to Edit
   Microsoft Windows	patch_weblogic.cmd	Replace @loc with the path to the Oracle Identity Manager installation directory. Replace @bea_home with the path to the WebLogic installation directory. Replace @java_loc with the path to the Java installation directory.
   	UpgradeAttestation.bat	Replace @java_home with the path to the Java installation directory.
   Linux	patch_weblogic.sh	Replace @loc with the path to the Oracle Identity Manager installation directory. Replace @bea_home with the path to the WebLogic installation directory Replace @java_loc with the path to the Java installation directory.
   	UpgradeAttestation.sh	Replace @java_home with the path to the Java installation directory. Replace @loc with the path to the Oracle Identity Manager installation.

   
   

10. Edit the spml_weblogic script specific to your operating system in the OIM_HOME/xellerate/setup/ directory. Edit spml_weblogic.cmd for Microsoft Windows and spml_weblogic.sh for UNIX.

    For upgrade from release 9.0.1.5:

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

    • Replace @bea_home with the path to the Weblogic Server installation directory.

    • Replace @java_loc with the path to the Java installation directory.

11. Delete the OIM_HOME/xellerate/webapp/precompiled/ directory.

12. Start BEA WebLogic Server.

    Note:

    For a cluster installation, before proceeding, ensure that the following fields and values are set on the Remote Start tab for all Managed Servers:

    • Java Home

    • BEA Home

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

13. Copy the PATCH/xellerate/ext/ojdbc14.jar file to the BEA_HOME/weblogic81/server/lib/ directory. If the file already exists, then overwrite it.

    Note:

    For a clustered installation, copy the ojdbc14.jar file to the BEA_HOME/weblogic81/server/lib/ directory on all cluster participants including the Admin Server, and overwrite the existing files if necessary.

14. For upgrading attestation, see Appendix H, "Attestation Upgrade Utility". This is a mandatory step.

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

    Note:

    Before running the patch scripts, ensure that the application server is in running state.

    Microsoft Windows:

    Run OIM_HOME\xellerate\setup\patch_weblogic.cmd by using the WebLogic administrator password and the Oracle Identity Manager database user password as command arguments, for example:

    OIM_HOME\xellerate\setup\patch_weblogic.cmd WEBLOGIC_ADMIN_PASSWORD OIM DATABASE_USER_PASSWORD
    

    UNIX:

    Run OIM_HOME/xellerate/setup/patch_weblogic.sh by using the WebLogic administrator password and the Oracle Identity Manager database user password as command arguments, for example:

    $ OIM_HOME/xellerate/setup/patch_weblogic.sh -WEBLOGIC_ADMIN_PASSWORD -OIM DATABASE_USER_PASSWORD
    

16. Select Security, Realms, myrealm, Providers, and Authentication in the order specified.

17. Delete the XellerateAuthenticator.

18. Shut down BEA WebLogic Server gracefully.

    Note:

    For a clustered installation, stop the cluster by right-clicking the name of the cluster, and then selecting the Start/Stop this cluster option. Shut down all Managed Servers by selecting the Graceful Shutdown of all Managed Servers option in the right pane.

19. Copy OIM_HOME/xellerate/lib/wlXLSecurityProviders.jar to the BEA_HOME/weblogic81/server/lib/mbeantypes/ directory.

20. Start BEA WebLogic Server.

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

22. Shut down BEA WebLogic Server gracefully.

23. Start BEA WebLogic Server.

    Note:

    For a clustered installation:

    1. Copy the OIM_HOME directory from the WebLogic Admin Server to all Managed Servers by maintaining the same directory structure.

    2. Copy OIM_HOME/xellerate/lib/wlXLSecurityProviders.jar to the BEA_HOME/weblogic81/server/lib/mbeantypes/ directory on all Managed Servers in the cluster. If the file already exists, then overwrite it.

    3. Copy OIM_HOME/xellerate/lib/nexaweb-common.jar to the BEA_HOME/weblogic81/server/lib/ directory on all Managed Servers in the cluster by overwriting the existing files if necessary.

    4. Start the WebLogic Admin server, and then start the Managed Servers.

24. 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 the server are upgraded. If you are running the scheduled task by using the Design Console, then make sure that the Design Console has also been upgraded.

3.4.1 Redeploying SPML Web Service

If you are using SPML Web service in the existing Oracle Identity Manager setup, then you must redeploy the SPML Web service whenever the setup is upgraded.

See Also:

The "SPML Web Service" section in Oracle Identity Manager Tools Reference

3.5 Migrating Custom Java Code

You can migrate the custom Java code from release 9.0.1.5 environment into the new release 9.1.0 environment. Before you migrate the custom Java code from the release 9.0.1.5 environment, you must first recompile the custom code 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 to compile the release 9.0.1.5 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.1.5 and reuse in release 9.1.0 after recompiling.

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.1.5 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.1.5 to the OIM_HOME/xellerate/JavaTasks/ directory of release 9.0.1. In addition, you must copy the recompiled custom Java libraries in the OIM_RM_HOME/xellerate/JavaTasks/ directory of release 9.0.1.5 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 event handlers to the OIM_HOME/xellerate/ScheduleTask/ directory of release 9.1.0.

  Note:

  If you want to see 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 scheduled tasks 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.1.5 to the OIM_HOME/xellerate/connectorResources/ directory release 9.1.0.

• Custom Resources by copying the OIM_HOME/xellerate/customResources/ directory release 9.0.1.5 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.1.5 Administrative and User Console, that is, you made changes to the default Administrative and User Console that shipped with release 9.0.1.5, then you must add your customizations to the new release 9.1.0 Administrative and User Console files.

3.6 Postupgrade Configuration

The following postupgrade configuration procedures are required if you are upgrading from an Oracle Identity Manager release 9.0.1.5 installation without the Oracle Identity Manager Audit and Compliance module to an Oracle Identity Manager release 9.1.0 installation with the Auditing and Compliance module:

• Setting the User Profile Audit Level

• Generating User Snapshots

• Generating GPA Snapshots

• Loading Data for Exception-Based Reporting

3.6.1 Setting the User Profile Audit Level

To set the user profile audit level:

1. Define a secondary data source for reporting, if required.

   Refer to Oracle Identity Manager Audit Report Developer's Guide for more information about defining a secondary data source.

2. Start the application server on which the Oracle Identity Manager installation is running.

3. Set the audit level. The permissible values are (in descending order):

   • Process Task

   • Resource Form

   • Resource

   • Membership

   • Core

   • None

4. To specify an audit level by performing the following steps:

   1. Log on to the Design Console as an administrator.

   2. Navigate to the System Configuration form.

   3. Locate XL.UserProfileAuditDataCollection and set its value to Resource Form or the appropriate audit level as listed in step 3 of this procedure.

5. To collect user profile audit data in the secondary reporting data store, complete the following steps:

   1. Log on to the Design Console as an administrator.

   2. Navigate to the System Configuration form.

   3. Locate XL.UserProfileAuditInSecondaryDS and set its value to TRUE.

3.6.2 Generating User Snapshots

For detailed information about generating user snapshots, see Appendix E, "Generating User Snapshots".

3.6.3 Generating GPA Snapshots

For detailed information about generating GPA snapshots, see Appendix G, "Generating GPA Snapshots".

3.6.4 Loading Data for Exception-Based Reporting

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".

3.7 Upgrading the Diagnostic Dashboard

To upgrade the existing release 9.0.1.5 Diagnostic Dashboard XIMDD application to the release 9.1.0 Diagnostic Dashboard on BEA WebLogic Server:

1. Remove the existing XIMDD application by using the WebLogic Administrative Console.

2. Install a new instance of the XIMDD application by using the Release 9.1.0 (9.0.1.5 Upgrade) XIMDD.war file in the PATCH/DiagnosticDashboard/ directory.

   See Also:

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