20 Upgrading Oracle Identity Manager Highly Available Environments

This chapter describes how to upgrade Oracle Identity Manager highly available environments to 11g Release 2 (11.1.2.3.0) on Oracle WebLogic Server, using the manual upgrade procedure.

Note:

If your existing Oracle Identity and Access Management environment was deployed using the Life Cycle Management (LCM) Tools, you must use the automated upgrade procedure to upgrade to Oracle Identity and Access Management 11g Release 2 (11.1.2.3.0).

For information about automated upgrade procedure, supported starting points and topologies, see Chapter 2, "Understanding the Oracle Identity and Access Management Automated Upgrade".

Note:

Before you proceed, check if your existing Oracle Access Management version is supported for high availability upgrade. For more information on supported starting points for high availability upgrade, see Section 3.3, "Supported Starting Points for Oracle Identity and Access Management Manual Upgrade".

This chapter includes the following sections:

20.1 Upgrade Roadmap

Table 20-1 lists the steps to upgrade Oracle Identity Manager high availability environment illustrated in Figure 20-1 to 11.1.2.3.0.

Table 20-1 Oracle Identity Manager High Availability Upgrade Roadmap

Task No Task For More Information

1

Review the Oracle Identity Manager high availability upgrade topology, and identify OIMHOST1 and OIMHOST2 on your setup.

See, Understanding Oracle Identity Manager High Availability Upgrade Topology

2

Perform the necessary pre-upgrade tasks.

See, Performing the Pre-Upgrade Tasks

3

Upgrade the binaries of Oracle WebLogic Server, Oracle SOA Suite, and Oracle Identity Manager on both OIMHOST1 and OIMHOST2.

See, Upgrading Oracle Home on OIMHOST1 and OIMHOST2

4

Upgrade the Database schemas and create necessary schemas.

See, Upgrading Database Schemas on OIMHOST1

5

Perform the Oracle Identity Manager middle tier upgrade offline on OIMHOST1 by running the middle tier upgrade utility offline.

See, Performing OIM Middle Tier Upgrade Offline on OIMHOST1

6

Replicate the domain configuration on OIMHOST2 by pack the domain on OIMHOST1 and unpacking it on OIMHOST2.

See, Replicating Domain Configuration on OIMHOST2

7

Perform the Oracle Identity Manager middle tier upgrade online on OIMHOST1 by running the middle tier upgrade utility online.

See, Performing OIM Middle Tier Upgrade Online on OIMHOST1

8

Scale out the BI Publisher for high availability setup.

See, Scaling out Oracle BI Publisher

9

Upgrade the Oracle Identity Manager Design Console and the Oracle Identity Manager Remote Manager to 11.1.2.3.0 on OIMHOST1.

See, Upgrading Other OIM Installed Components on OIMHOST1

10

Perform the necessary post-upgrade tasks.

See, Performing Post-Upgrade Tasks

11

Verify the upgrade.

See, Verifying the Upgrade

20.2 Understanding Oracle Identity Manager High Availability Upgrade Topology

Figure 20-1 shows the Oracle Identity Manager cluster set up that can be upgraded to 11.1.2.3.0 by following the procedure described in this chapter.

Figure 20-1 Oracle Identity Manager High Availability Upgrade Topology

Description of Figure 20-1 follows
Description of ''Figure 20-1 Oracle Identity Manager High Availability Upgrade Topology''

On OIMHOST1, the following installations have been performed:

  • An Oracle Identity Manager instance has been installed in the WLS_OIM1 Managed Server and a SOA instance has been installed in the WLS_SOA1 Managed Server.

  • A WebLogic Server Administration Server has been installed. Under normal operations, this is the active Administration Server.

On OIMHOST2, the following installations have been performed:

  • An Oracle Identity Manager instance has been installed in the WLS_OIM2 Managed Server and a SOA instance has been installed in the WLS_SOA2 Managed Server.

  • A WebLogic Server Administration Server has been installed. Under normal operations, this is the passive Administration Server. You make this Administration Server active if the Administration Server on OIMHOST1 becomes unavailable.

The instances in the WLS_OIM1 and WLS_OIM2 Managed Servers on OIMHOST1 and OIMHOST2 are configured as the OIM_CLUSTER cluster.

The instances in the WLS_SOA1 and WLS_SOA2 Managed Servers on OIMHOST1 and OIMHOST2 are configured as the SOA_CLUSTER cluster.

20.3 Performing the Pre-Upgrade Tasks

Before you begin with the upgrade process, you must perform necessary pre-upgrade tasks on OIMHOST1. It includes reviewing the features of 11.1.2.3.0, reviewing system requirements and certifications, generating and analyzing the pre-upgrade report, backing up the existing environment, and other specific tasks required for your starting point.

If your starting point is Oracle Identity Manager 11g Release 2 (11.1.2.2.0), 11g Release 2 (11.1.2.1.0), or 11g Release 2 (11.1.2), perform the pre-upgrade tasks described in Section 10.2, "Performing the Required Pre-Upgrade Tasks".

If your starting point is Oracle Identity Manager 11g Release 1 (11.1.1.5.0), perform the pre-upgrade tasks described in Section 14.2, "Performing the Required Pre-Upgrade Tasks".

20.4 Upgrading Oracle Home on OIMHOST1 and OIMHOST2

You must upgrade the Oracle Home on both OIMHOST1 and OIMHOST2 by upgrading the binaries of Oracle WebLogic Server, Oracle SOA Suite, and Oracle Identity Manager to 10.3.6, 11.1.1.9.0, and 11.1.2.3.0 versions respectively.

Note:

If you are using a shared file system, binary upgrade is not required on OIMHOST2.

If your starting point is Oracle Identity Manager 11g Release 2 (11.1.2.2.0), 11g Release 2 (11.1.2.1.0), or 11g Release 2 (11.1.2), follow the instructions described in Section 10.3, "Upgrading Oracle Home" to upgrade Oracle Home.

If your starting point is Oracle Identity Manager 11g Release 1 (11.1.1.5.0), follow the instructions described in Section 14.3, "Upgrading Oracle Home" to upgrade Oracle Home.

20.5 Upgrading Database Schemas on OIMHOST1

After you upgrade the Oracle Home, you must upgrade the Database schemas on OIMHOST1. Also, you must create Oracle BI Publisher (BIP) schemas.

If your starting point is Oracle Identity Manager 11g Release 2 (11.1.2.2.0), 11g Release 2 (11.1.2.1.0), or 11g Release 2 (11.1.2), follow the instructions described in Section 10.4, "Creating Necessary Schemas and Upgrading Existing Schemas" to upgrade Database schemas.

If your starting point is Oracle Identity Manager 11g Release 1 (11.1.1.5.0), follow the instructions described in Section 14.4, "Creating Necessary Schemas and Upgrading the Existing Schemas" to upgrade Database schemas.

20.6 Performing OIM Middle Tier Upgrade Offline on OIMHOST1

After you upgrade Oracle Home and Database schemas, you must perform Oracle Identity Manager middle tier upgrade offline. This is done by running the middle tier offline script.

To perform the Oracle Identity Manager middle tier upgrade offline, complete the following tasks described in Section 24.2.4, "Upgrading Oracle Identity Manager Middle Tier":

  1. Additional Task for Windows 64-Bit Users Before Upgrading Middle Tier

  2. Creating a Truststore for Upgrading SSL Enabled Middleware

  3. Updating the Properties File

  4. Performing Oracle Identity Manager Middle Tier Upgrade Offline

20.7 Replicating Domain Configuration on OIMHOST2

You must replicate the domain configuration on OIMHOST2. This task involves packing the upgraded domain on OIMHOST1 and unpacking it on OIMHOST2.

Note:

Make sure that the Managed Servers are stopped before you perform this step. Do not start the Managed Servers until you complete this task.

To do this, complete the following steps:

  1. On OIMHOST1, run the following command from the location $MW_HOME/oracle_common/common/bin to pack the upgraded domain:

    On UNIX:

    sh pack.sh -domain=<Location_of_OIM_domain> -template=<Location_where_domain_configuration_jar_to_be_created> -template_name="OIM Domain" -managed=true

    On Windows:

    pack.cmd -domain=<Location_of_OIM_domain> -template=<Location_where_domain_configuration_jar_needs_to_be_created> -template_name="OIM Domain" -managed=true

  2. Copy the domain configuration jar file created by the pack command on OIMHOST1 to any accessible location on OIMHOST2.

  3. On OIMHOST2, run the following command from the location $MW_HOME/oracle_common/common/bin to unpack the domain:

    On UNIX:

    sh unpack.sh -domain=<Location_of_OIM_domain> -template=<Location_on_OIMHOST2_where _you_copied_jar_file_created_by_pack_command> -overwrite_domain=true

    On Windows:

    unpack.cmd -domain=<Location_of_OIM_domain> -template=<Location_on_OIMHOST2_where _you_copied_jar_file_created_by_pack_command> -overwrite_domain=true

  4. After you unpack the domain, copy the content of the following directory on OIMHOST1 to the same directory on OIMHOST2:

    DOMAIN_HOME/soa/autodeploy

20.8 Performing OIM Middle Tier Upgrade Online on OIMHOST1

After you replicate the domain configuration on OIMHOST2, you must perform the Oracle Identity Manager middle tier upgrade online on OIMHOST1. This is done by running the middle tier online upgrade script.

To perform the Oracle Identity Manager middle tier upgrade online, complete the following tasks described in Section 24.2.4, "Upgrading Oracle Identity Manager Middle Tier":

  1. Starting Administration Server and SOA Managed Server(s) - Start the WebLogic Administration Server and SOA Managed Server(s) on OIMHOST1.

  2. Performing Oracle Identity Manager Middle Tier Upgrade Online

  3. Starting the Oracle Identity Manager Managed Server(s) and the BIP Server - Start the Oracle Identity Manager Managed Server(s) on both OIMHOST1 and OIMHOST2, BIP Managed Server(s) on OIMHOST1, and the SOA Managed Server on OIMHOST2.

  4. Changing the Deployment Order of Oracle Identity Manager EAR - Perform this step only if you are upgrading Oracle Identity Manager 11g Release 1 (11.1.1.5.0) environments.

20.9 Scaling out Oracle BI Publisher

This is an optional step.

After you upgrade the Oracle Identity Manager middle tier, if you wish to scale out the Oracle BI Publisher (BIP), complete the following steps:

  1. Creating a new BIP Server on OIMHOST2

  2. Setting the Location of the Shared BI Publisher Configuration Folder

  3. Setting Scheduler Configuration Options

  4. Configuring JMS for BI Publisher

  5. Verifying the BIP Server Scale Out

20.9.1 Creating a new BIP Server on OIMHOST2

To create a new BIP server on OIMHOST2 and add it to the existing BIP cluster, do the following:

  1. Log in to the WebLogic Administration Server using the following URL:

    http://host:port/console

  2. Create a new BIP Server on OIMHOST2 and add it to the existing BIP cluster by completing the following steps:

    1. Click Lock & Edit next to Change Center on the upper left of the WebLogic Administration Console screen.

    2. Expand Environment under Domain Structure.

    3. Click Servers. The Summary of Servers page is displayed.

    4. Click New.

    5. Specify the server name. For example, bi_server2.

    6. Specify the Server Listen Address and Server Listen Port.

    7. Select Yes for Make this server a member of an existing cluster, and select the BIP cluster.

    8. Click Next, and then click Finish.

    9. Click Activate Changes.

  3. If you wish to start the BIP server on OIMHOST2 using the Node Manager, you must assign a machine to the BIP server. To do this, complete the following steps:

    1. Click Lock & Edit next to Change Center on the upper left of the WebLogic Administration Console screen.

    2. Expand Environment under Domain Structure.

    3. Click Servers. The Summary of Servers page is displayed.

    4. Select the BIP Server that you created on OIMHOST2.

    5. Go to the General tab under Configuration.

    6. Select the Machine name from the Machine drop-down list.

    7. Click Save.

    8. Click Activate Changes.

20.9.2 Setting the Location of the Shared BI Publisher Configuration Folder

After creating a new BIP server on OIMHOST2, you must set the server configuration options for Oracle BI Publisher.

Note:

If you are upgrading an Oracle Identity Manager, Access Manager, Oracle Adaptive Access Manager integrated environment, where the Administration Server and the Managed Servers have different domain location, follow the instructions described in Steps for Setting Location of the Shared BI Publisher Configuration Folder in Case of an Integrated Environment to set the shared BIP configuration folder location.

To set the server configuration options for Oracle BI Publisher, complete the following steps:

  1. Copy the contents of the DOMAIN_HOME/config/bipublisher/repository directory to the shared configuration folder location.

  2. On APPHOST1, log in to the BI Publisher using administrator's credentials.

  3. Go to the Administration tab.

  4. Select Server Configuration under System Maintenance.

  5. Enter the shared location for the configuration folder in the Path field under Configuration Folder.

  6. Enter the shared location for the BI Publisher Repository in the BI Publisher Repository field under Catalog.

  7. Apply your changes.

  8. Restart the BI Publisher application by doing the following:

    1. Log in to the WebLogic Administration Console using the following URL:

      http://host:port/console

    2. Expand Deployments under Domain Structure.

    3. Click bipublisher(11.1.1.).

    4. Click Stop and then select When work completes or Force Stop Now.

    5. After the application has stopped, click Start and then select servicing all requests.

Steps for Setting Location of the Shared BI Publisher Configuration Folder in Case of an Integrated Environment

If you are upgrading an Oracle Identity Manager, Access Manager, Oracle Adaptive Access Manager integrated environment, where the Administration Server and the Managed Servers have different domain location, complete the following steps to set the location of the shared BIP configuration folder:

  1. Stop the BIP Managed Server(s) on OIMHOST1 and OIMHOST2. For information about stopping the servers, see Section 24.1.9.1, "Stopping the Managed Server(s)".

  2. Copy the contents of the DOMAIN_HOME/config/bipublisher/repository directory to the shared configuration folder location.

  3. Open the xmlp-server-config.xml file available in the Admin domain at the location at DOMAIN_HOME/config/bipublisher/ on OIMHOST1.

  4. Update the file path in the xmlp-server-config.xml file with the shared configuration folder location shown in the following example:

    <?xml version = '1.0' encoding = 'UTF-8'?> 
<xmlpConfig xmlns="http://xmlns.example.com/oxp/xmlp"> 
 <resource> 
  <file path="<shared configuration folder location>/repository"/> 
 </resource> 
 <config> 
  <file path="<shared configuration folder location>/repository"/> 
 </config> 
</xmlpConfig>

  5. Start the BI Managed Server(s) on OIMHOST1 and OIMHOST2.

20.9.3 Setting Scheduler Configuration Options

To set the scheduler configuration options, complete the following steps:

  1. On APPHOST1, log in to the BI Publisher using administrator's credentials.

  2. Go to the Administration tab.

  3. Select Scheduler Configuration under System Maintenance.

  4. Select Quartz Clustering under Scheduler Selection.

  5. Click Apply.

20.9.4 Configuring JMS for BI Publisher

You must configure the location for all persistence stores to a directory that is accessible from both OIMHOST1 and OIMHSOT2. This can be done by changing all persistent stores to use this shared base directory. To do this, complete the following steps:

  1. Log in to the WebLogic Administration Console using the following URL:

    http://host:port/console

  2. Expand Services under Domain Structure.

  3. Click Persistent Stores. The Summary of Persistent Stores page is displayed.

  4. Click Lock & Edit under Change Center.

  5. Click on an existing File Store (for example, BipJmsStore), and verify the target. If the target is bi_server2, then you must target the new File Store that you will be creating in the next step, to bi_server1.

  6. Click New and then click Create File Store.

  7. Enter a name for the new file store (for example, BipJmsStore1), and specify bi_server1 as the Target. Specify the directory that is located in the shared storage which is accessible from both APPHOST1 and APPHOST2.

    ORACLE_BASE/admin/domain_name/bi_cluster/jms". Is this an example of the directory path?

  8. Click OK, and then click Activate Changes.

  9. Go back to the home page of the WebLogic Administration Console, and expand Services under Domain Structure.

  10. Click Messaging, and then select JMS Servers. The Summary of JMS Servers page is displayed.

  11. Click Lock & Edit under Change Center.

  12. Click New.

  13. Enter a name for the JMS Server (for example, BipJmsServer1).

  14. In the Persistent Store drop-down list, select the file store that you just created (for example, BipJmsStore1).

  15. Click Next.

  16. Select bi_server1 as the Target.

  17. Click Finish, and then click Activate Changes.

  18. Go back to the home page of the WebLogic Administration console, and expand Services under Domain Structure.

  19. Click Messaging, and select JMS Modules.

  20. Click Lock & Edit under Change Center.

  21. Click BipJmsResource, and go to the Subdeployments tab.

  22. Select BipJmsSubDeployment under Subdeployments.

  23. Add the newly created JMS Server (BipJmsServer1), as an additional target for the subdeployment.

  24. Click Save, and then click Activate Changes.

To validate the JMS configuration for BI Publisher, complete the steps described in Updating the BI Publisher Scheduler Configuration.

Updating the BI Publisher Scheduler Configuration

This section describes how to update the JMS Shared Temp directory for the BI Publisher Scheduler. Complete the following steps on only one host, either APPHOST1 or APPHOST2:

  1. Log in to BI Publisher using the following URL:

    http://host:port/xmlpserver

    For example:

    http://APPHOST1VHN1:9704/xmlpserver

  2. Go to the Administration tab.

  3. Click Scheduler Configuration under System Maintenance. The Scheduler Configuration screen is displayed.

  4. Update Shared Directory with the directory that is located in the shared storage. This shared storage must be accessible from both APPHOST1 and APPHOST2.

  5. Click Test JMS.

    Note:

    When you click Test JMS, a confirmation message is displayed indicating that the JMS was tested successfully.

    If you do not see a confirmation message for a successful test, verify if the JDNI URL is set to the following:

    cluster:t3://bi_cluster

  6. Click Apply.

  7. Go to the Scheduler Diagnostics tab, and check the Scheduler status.

  8. Restart bi_server1 and bi_server2.

Note:

For more information about scaling out BI Publisher, see "Scaling Out the Oracle Business Intelligence System" in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence for 11g Release 1 (11.1.1.7.0).

20.9.5 Verifying the BIP Server Scale Out

Verify that you have successfully scaled out Oracle BI Publisher by starting the Node Manager, WebLogic Administration Server, SOA Managed Server, OIM Managed Server, and BIP Server on OIMHOST2, and checking the status of the servers in the WebLogic Administration console.

Verify that you can access BIP links on both OIMHOST1 and OIMHOST2 using the following URL:

http://host:port/xmlpserver

20.10 Upgrading Other OIM Installed Components on OIMHOST1

After you complete the middle tier upgrade, you must upgrade the Oracle Identity Manager Design Console and the Oracle Identity Manager Remote Manager to 11.1.2.3.0 on OIMHOST1.

For information about upgrading the Design Console and Remote Manager, see Section 24.2.5, "Upgrading Other Oracle Identity Manager Installed Components".

20.11 Performing Post-Upgrade Tasks

After you upgrade Oracle Identity Manager high availability environments to 11.1.2.3.0, you must perform the necessary post-upgrade tasks described in Section 24.2.6, "Performing Oracle Identity Manager Post-Upgrade Tasks".

20.12 Verifying the Upgrade

This section describes how to verify the upgrade.

If your starting point is Oracle Identity Manager 11g Release 2 (11.1.2.2.0), 11g Release 2 (11.1.2.1.0), or 11g Release 2 (11.1.2), you must complete the steps described in Section 10.8, "Verifying the Oracle Identity Manager Upgrade" to verify the upgrade.

If your starting point is Oracle Identity Manager 11g Release 1 (11.1.1.5.0), you must complete the steps described in Section 14.8, "Verifying the Oracle Identity Manager Upgrade" to verify the upgrade.

20.13 Troubleshooting

For the list of common issues that you might encounter during the Oracle Identity Manager upgrade process, and their workaround, see Section 25.1, "Troubleshooting Oracle Identity Manager Upgrade Issues".

For the list of known issues related to upgrade, and their workaround, see "Upgrade and Migration Issues for Oracle Identity and Access Management" in the Oracle Fusion Middleware Release Notes for Identity Management.