Google Search

Sunday, May 11, 2014

OIM 11G Design Console in Cluster Environment

Configuring OIM 11G Design Console in Cluster Environment: 

How To Configure Design Console for OIM 11g Cluster Install?

Below are the steps:

To explain a sample configuration in this article, assuming there are 2 oim_server nodes in the cluster distributed in machine1 and machine2 and both listening on port 8003.

1. To configure OIM Design Console 11g, Oracle Identity Manager 11g Configuration Wizard needs to be started by executing the <IDM_Home>/bin/config.sh script (<IDM_Home>\bin\config.bat on Windows) on the machine where the Administration Server is running. This IDM_Home is the directory where Oracle Identity Manager is installed.

Refer the following documentation for the complete configuration details:

Configuring OIM Design Console


http://download.oracle.com/docs/cd/E14571_01/install.1111/e10033/oidonly.htm#CIHDDJEA

2. Once the OIM Design Console is installed, try accessing the Design Console, it should probably be accessing the node mentioned in the Configuration Wizard. (Say details of machine 1 was provided during the configuration then Design Console is accessing that node of the cluster).

3. Now bring down the node in machine1, check Design Console access and it should fail. This occurs because the Design Console is not configured to access both the nodes of the cluster.

4. To make the Design Console access both the nodes of the cluster:

  • Go to <IDM_HOME>/designconsole/config and take a backup of xlconfig.xml.
  • Open the xlconfig.xml and make the following changes:
    • The <ApplicationURL> tag might have a value like:
      http://machine1:port/xlWebApp/loginWorkflowRenderer.do                                               (referring to the first node)
    • Change the value to point to the loadbalancer URL (Say Oracle HTTP Server is configured as the LoadBalancer then the default URL would be http://ohsmachinehostname:7777)

      http://ohsmachinehostname:7777/xlWebApp/loginWorkflowRenderer.do

    • The <java.naming.provider.url> tag might have a value like:

      t3://machine1:port/oim (referring to the first node)

    • Change the value to point to both the nodes:

      t3://machine1:port,machine2:port (The /oim is not required)

  • Now save the file and run ./xlclient.sh(cmd) from IDM_HOME/designconsole. It should connect to the second node of the cluster.

No comments:

Post a Comment