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

• Installing Oracle Application Server on Cluster Members

• Creating OC4J Instances

• 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

Overview

This chapter describes the steps to deploy Oracle Identity Manager in a Oracle Application Server clustered configuration using three example clusters 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.

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:

• On Cluster Node A:

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

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

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

• On Cluster Node B:

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

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

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

• On Cluster Node C:

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

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

Creating OC4J Instances

After installing Oracle Application Server on the cluster members, create OC4J instances named xlClusterMember on Cluster Node A and on Cluster Node B by using the following steps:

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 xlClusterMember as the instance name and leave all other instance parameters as their default value.

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

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

Repeat these steps until you create xlClusterMember instances on both Cluster Node A and on Cluster Node B.

Installing Oracle Identity Manager on Cluster Members

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

Refer to Chapter 5, "Installing Oracle Identity Manager Server on Windows" or Chapter 6, "Installing Oracle Identity Manager Server on UNIX or Linux" 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, be sure to set the following information when prompted by the Oracle Identity Manager Server Installer:

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

• Enter xlClusterMember as the OC4J instance name.

• 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
  
  

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 <XL_HOME>\xellerate\ext\ directory to the <ORACLE_HOME>\jdk\jre\lib\ext\ directory on both Cluster Node A and Cluster Node B.

2. Increase the Oracle Application Server heap size on both Cluster Node A and Cluster Node B by performing the following steps:

   1. Open the <ORACLE_HOME>\opmn\conf\opmn.xml file in a text editor.

   2. Locate the process-type id="<Instance Name>" entry. If using the instance names in this chapter, Instance Name will be xlClusterMember.

   3. Change -XX:MaxPermSize=128M to be -XX:MaxPermSize=512M

   4. Save and close the <ORACLE_HOME>\opmn\conf\opmn.xml file.

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

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 web server on Node C, which is 7777 by default.

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.

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 <XL_DC_HOME>\xlclient\config\xlconfig.xml using 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.