9 Deploying in a Clustered Oracle Application Server Configuration

This chapter describes how to deploy Oracle Identity Manager in a clustered Oracle Application Server environment and contains the following sections:

• Overview of Deploying in a Clustered Oracle Application Server Configuration

• Installing Oracle Application Server on Cluster Members

• Upgrading Oracle Application Server From Release 10.1.3.1 To Release 10.1.3.3

• Applying Oracle Application Server Patches

• Creating OC4J Instances

• Installing and Configuring a Database for Oracle Identity Manager

• Installing Oracle Identity Manager on Cluster Members

• Configuring Oracle Identity Manager for the Oracle Application Server Cluster

• Accessing the Oracle Identity Manager Administrative and User Console for the Cluster

• Installing and Configuring the Design Console for the Cluster

• Postinstallation Tasks for Clustered Oracle Application Server Installation

9.1 Overview of Deploying in a Clustered Oracle Application Server Configuration

This section describes the steps to deploy Oracle Identity Manager in a Oracle Application Server clustered configuration by using three example cluster members as follows:

• Cluster Node A and Cluster Node B are Oracle Application Servers running Oracle Identity Manager.

• Cluster Node C is an Oracle HTTP Web Server.

9.2 Installing Oracle Application Server on Cluster Members

The first step in deploying Oracle Identity Manager in a clustered Oracle Application Server configuration is to install Oracle Application Server on the cluster members, for example, on Cluster Node A, Cluster Node B, and Cluster Node C.

Perform the following steps on the Oracle Universal Installer to install Oracle Application Server on the cluster members. When you run the Oracle SOA Suite installer, you must choose the Advanced Install option.

• On Cluster Node A:

  • Install Oracle Application Server by selecting the J2EE Server option on the Select Installation Type page.

  • In the Specify Port Configuration Options window that is displayed, Automatic is selected by default. Click Next.

  • Select the Configure this as an Administrator OC4J instance option on the Administration Settings page.

  • Select the Configure this OC4J instance to be part of an Oracle Application Server cluster topology option and specify the host IP address and Port for the discovery address on the Cluster Topology Configuration page.

  Note:

  - Discovery address (Multicast address and port number) for Cluster Node A, Cluster Node B, and Cluster Node C must be the same.

  - The path of ORACLE_HOME has to be same for Node A and Node B.

• On Cluster Node B:

  • Install Oracle Application Server by selecting the J2EE Server option on the Select Installation Type page.

  • In the Specify Port Configuration Options window that is displayed, Automatic is selected by default. Click Next.

  • Do not select the Configure this as an Administrator OC4J instance option on the Administration Settings page.

  • Select the Configure this OC4J instance to be part of an Oracle Application Server cluster topology option and specify the host IP address and Port for the discovery address on the Cluster Topology Configuration page.

• On Cluster Node C:

  • Install the Web server by selecting the Web Server option on the Select Installation Type page.

  • In the Specify Port Configuration Options window that is displayed, Automatic is selected by default. Click Next.

  • Select the Configure this Oracle HTTP Server instance to be part of an Oracle Application Server cluster option and specify the host IP address and Port for the discovery address on the Cluster Topology Configuration page.

9.3 Upgrading Oracle Application Server From Release 10.1.3.1 To Release 10.1.3.3

Ensure that you have upgraded Oracle Application Server from release 10.1.3.1 to release 10.1.3.3. To check the version of Oracle Application Server that you currently use:

1. Ensure that the Oracle Application Server Java binary path is ORACLE_HOME\jdk\bin.

2. Run the following command from ORACLE_HOME\j2ee\OC4J_INSTANCE\java -jar oc4j.jar version.

   The information that appears should be similar to the following example:

   Oracle Containers for J2EE 10g (10.1.3.3.0) (build 070610.1800.23513)

9.4 Applying Oracle Application Server Patches

The following patches may be specific to 10.1.3.3.0 version of Oracle Application Server:

Note:

• If you are running on any other version of Oracle Application Server, then contact Oracle to get the patches for that version of Oracle Application Server.

• If you are installing Oracle Identity Manager in Microsoft Windows Vista, then you must set the environment variable OPATCH_PLATFORM_ID to 207.

1. Install Oracle Application Server patch 2617419.

2. Install Oracle Application Server patch 6685235.

3. Install Oracle Application Server patch 5389650.

4. Install Oracle Application Server patch 6454278.

   Patches and instructions on how to apply those patches can be downloaded from the OracleMetaLink Web site at:

   http://metalink.oracle.com.

   Note:

   All the steps to install Oracle Application Server patches must be repeated for all installations of Oracle Application Server.

9.5 Creating OC4J Instances

After installing Oracle Application Server on the cluster members, create OC4J instances named xlClusterMember1 on Cluster Node A. For this:

1. Log in to the Oracle Enterprise Manager 10g Application Server Control.

2. Click the name of the Cluster Node you want to create the OC4J instance on.

3. Click Create OC4J Instance.

4. Enter xlClusterMember1 as the instance name and select Add to a new group with name and enter xlClusterGroup as the Group Name.

5. Click Create to create and start the xlClusterMember instance.

6. Start the OC4J instances you created on each Cluster Node.

Repeat these steps for creating xlClusterMember2 on Cluster Node B by using appropriate values. Use xlClusterGroup as the Group Name.

9.5.1 Max Server Sockets for OC4J Instance

To avoid OutOfMemory errors during runtime, open ORACLE_HOME/j2ee/OC4J_INSTANCE/config/rmi.xml, and add max-server-sockets="200" as shown:

<rmi-server
...
max-server-sockets="200">

Note:

• This configuration is part of patch 6685235.

• OC4J_INSTANCE is the instance of Oracle Application Server where Oracle Identity Manager is deployed. For a clustered installation of Oracle Identity Manager, this needs to be repeated for xlClusterMember1 and xlClusterMember2.

9.5.2 Setting the RMI Port Number Range

The Oracle Process Manager and Notification server (OPMN) dynamically assigns port numbers to each OC4J instance within your Oracle Application Server instance.

To ensure that you can access the Oracle Identity Manager Design Console and Administrative and User Console on Oracle Application Server, you must set the RMI port number range to be unique in the ORACLE_HOME/opmn/conf/opmn.xml file. Perform the following steps to set a unique RMI port number range in each node:

1. In a text editor, open the ORACLE_HOME/opmn/conf/opmn.xml file.

2. Locate the <port id="rmi" range="12401-12500"/> entry for cluster member xlClusterMember1 in Node A.

3. Choose one of the port for RMI within the range of 12401 and 12500, for example, <port id="rmi" range="12409"/>. Make sure that you use this same RMI port ID for the clustergroup in other nodes.

4. Save and close the opmn.xml file.

   Note:

   Repeat the steps 1 through 4 for the all the other cluster members, such as xlClusterMember2 in Node B.

5. Stop and restart the Oracle Application Servers for the changes to take effect. Verify the change by running the opmnctl status -l command from the ORACLE_HOME/opmn/bin/ directory.

   To restart Oracle Identity Manager, run the following commands:

   To stop Oracle Application Server:

   ORACLE_HOME/opmn/bin/opmnctl stopall
   

   To start Oracle Application Server:

   ORACLE_HOME/opmn/bin/opmnctl startall
   

   See Also:

   The "Setting Environment Variables" section for information about setting environment variables

9.6 Installing and Configuring a Database for Oracle Identity Manager

Refer to Chapter 4, "Installing and Configuring a Database for Oracle Identity Manager" for information.

9.7 Installing Oracle Identity Manager on Cluster Members

After creating OC4J instances, install Oracle Identity Manager on both Cluster Node A and then Cluster Node B with the same database schema information.

Refer to Chapter 5, "Installing Oracle Identity Manager on Microsoft Windows" or Chapter 6, "Installing Oracle Identity Manager Server on UNIX" to install Oracle Identity Manager on both Cluster Node A and Cluster Node B.

Important:

When installing Oracle Identity Manager on both Cluster Node A and Cluster Node B, ensure that you set the following information when prompted by the Oracle Identity Manager Installer:

• Select Yes when prompted as to whether the application server is clustered.

• Enter xlClusterGroup as Cluster Name.

• Enter the appropriate OC4J instance name (xlClusterMember1 or xlClusterMember2).

• Enter xlClusterMember's RMI port number as the RMI port. You can identify the RMI port number by executing the following command from the ORACLE_HOME/opmn/bin/ directory:

  opmnctl status -l
  

9.8 Configuring Oracle Identity Manager for the Oracle Application Server Cluster

After installing Oracle Identity Manager, perform the following steps to configure it for the Oracle Application Server cluster:

1. Copy the Oracle Identity Manager log4j-1.2.8.jar log file from the OIM_HOME/xellerate/ext/ directory to the ORACLE_HOME/jdk/jre/lib/ext/ directory on both Cluster Node A and Cluster Node B.

2. Restart all the cluster members, including Cluster Node A, Cluster Node B, and Cluster Node C.

9.9 Accessing the Oracle Identity Manager Administrative and User Console for the Cluster

After restarting all the cluster members, you can access the Oracle Identity Manager Administrative and User Console for the cluster by going to the following URL:

http://Node_C_host_name:web_server_port/xlWebApp

Note:

Node_C_host_name represents the host name of the Web server and web_server_port represents the port number of the server on Node C, which is 7777 by default.

9.10 Installing and Configuring the Design Console for the Cluster

You can install the Oracle Identity Manager Design Console on any Windows node in the cluster. Refer to Chapter 10, "Installing and Configuring the Oracle Identity Manager Design Console" for Design Console requirements and installation steps.

9.10.1 Configuring the Design Console to be Cluster Aware

You must configure the Design Console to be cluster aware. Perform the following steps to configure the Design Console to be cluster aware:

1. Open OIM_DC_HOME/xlclient/config/xlconfig.xml in a text editor.

2. Modify the java.naming.provider.url attribute to be cluster aware, for example:

   ormi://host name:12408/Xellerate,ormi://host name:12408/Xellerate
   

3. Save and close the xlconfig.xml file.

9.11 Postinstallation Tasks for Clustered Oracle Application Server Installation

Before the postinstallation configuration for a clustered installation of Oracle Application Server, follow the instructions in Chapter 7, "Postinstallation Configuration for Oracle Identity Manager and Oracle Application Server".

Postinstallation configuration for clustered Oracle Application Server installation involves synchronizing the multicast IP for all Oracle Identity Manager installations. To do this:

1. Go to ORACLE_HOME/j2ee/OC4J_INSTANCE/application-deployments/Xellerate/ in the first node.

2. Open orion-application.xml.

3. Search for multicast IP and record the IP address.

4. Go to ORACLE_HOME/j2ee/OC4J_INSTANCE/application-deployments/Xellerate/ in the second node.

5. Open orion-application.xml.

6. Search for multicast IP and change it to the same multicast IP value as the first node.

7. Apply step 6 to all other nodes.

8. Go to OIM_HOME/xellerate/config/ in the second node.

9. Open xlconfig.xml and search for MultiCastAddress and change it to the same multicast IP value as the first node.

   Note:

   There are two instances of MultiCastAddress in xlconfig.xml that are used by Oracle Identity Manager for internal caching and scheduler-related activities. These values must be the same. Also, cluster members xlClusterMember1 and xlClusterMember2 must have the same value for MultiCastAddress in xlconfig.xml.

10. Apply step 9 to all other nodes.

11. Restart all servers.

    Note:

    You must synchronize multicast IP address in orion-application.xml every time after you run the patch_oc4j script. Multicast address in orion-application.xml is used by Oracle Application Server for HTTP session replication and failover.