B SOA Suite 10.1.3.4 HA Setup Using WebSphere Cluster

B.2.3.1 Setting up SOAServer on the First (Primary) Node

Step1: Create a Custom Node "Node A" in MachineA

1. While creating the node, federate the node into the Deployment Manager.

2. Verify that Node A has been federated from the IBM Admin Console's Node page.

3. Start Node Agent for Node A using the startNode command.

Step 2: Under the WAS_SOA10134_Installables/cfg folder, edit the config.properties file, as per the environment

Refer to Step 4 in Step 7: Install and Configure IBM WebSphere Application Server Version 6.1.0.15 for the list of properties in the config.properties file.

1. Ensure that the DEPLOY_ESBDT property is set to "N" in config.properties.

   • DEPLOY_BPELPM=Y

   • DEPLOY_ESBDT=N

   • DEPLOY_ESBRT=Y

   • DEPLOY_RULES=Y

   • DEPLOY_OWSM=Y

   Note:

   If proxy setting is enabled, then the NONPROXYHOSTS property should contain the machine names of all cluster member and deployment manager.

   For example, NONPROXYHOSTS=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|a-host|b-host|c-host

2. Run the following script from WAS_SOA10134_Installables folder at the operating system command prompt:

   For...	Run...
   Windows XP	configureStandAloneServer.bat -secure
   Linux	configureStandAloneServer.sh -secure

   
   

   The configuration scripts mentioned in the table execute in two parts:

   The first part creates all the artifacts required for the SOAServer such as DataSources, ConnectionFactories, and Shared-Libraries on the WebSphere Application Server. (On Linux environments, this part needs to be executed as a 'root' user.) The second part of the script modifies configuration values under SOA_HOME. (On Linux environments, this part needs to be executed as a 'non-root' user.)

   After you execute the script, this script prompts you to enter the WebSphere username and password. If the authentication is successful, then the Deployment Manager artifacts will be installed/configured into WebSphere application server.

   Note:

   • The above scripts can be run without the "-secure" option, if security is disabled in the WebSphere environment.On Linux environments, the above script needs to be executed as a 'root' user. Also, the script will prompt for the SOA username while executing the second phase of the configuration.

3. The script requires JAVA_HOME and WAS_HOME to be set.

4. Check the output.log/output-copy.log files in the WAS_SOA10134_Installables /bin/logs directory.

   This script will configure SOAServer1 on Machine A and add it to a cluster.

5. Log in to the WebSphere Admin Console and verify that the SOACluster and SOAServer1 are created.

B.2.3.2 Adding Subsequent Members to the Cluster (Secondary Nodes)

Step 1: Create a Custom Node "Node B" in MachineB

1. While creating the node, federate the node into the Deployment Manager.

2. From the IBM Admin Console, navigate to the cluster created in the previous step and click the Cluster members.

3. Click New to create a new Cluster member.

4. In the Create Additional Cluster Member page, enter a name for the new server, for example, SOAServer2. Add the new server into the cluster and save the changes.

   Note:

   Ensure that Node B is selected in the Select Node list.

   Now, there will be two servers as cluster member, one each on Node A and Node B.

Step 2

1. Repeat Steps 1 to 4 in Step 2: Under the WAS_SOA10134_Installables/cfg folder, edit the config.properties file, as per the environment.

2. The configuration scripts re-configure SOAServer-1 on Node2 created in the previous steps.

   • Create new SIB Bus, SIB Bus member

   • Update Queue Connection Factories, Queues and Activation Specifications with the new SIB details.

   • Update the shared-libraries.

   • Update the WebSphere variables and JVM properties.

Oracle SOA Suite on WebSphere Cluster is configured for HA.

B.2.3.3 Setting up ESB-DT Outside the Cluster

Step 1: Create a Custom Node "Node C" in MachineC

1. While creating the node, federate the node into the Deployment Manager.

2. Verify that Node C has been federated from the IBM Admin Console's Node page.

3. Start Node agent for Node C using startNode command.

Step 2: Under the WAS_SOA10134_Installables/cfg folder, edit the config.properties as per the environment

1. Ensure that the DEPLOY_ESBDT property is set to "Y" in config.properties.The rest of the DEPLOY properties should be set to N.

   • DEPLOY_BPELPM=N

   • DEPLOY_ESBDT=Y

   • DEPLOY_ESBRT=N

   • DEPLOY_RULES=N

   • DEPLOY_OWSM=N

2. Repeat Steps 2 to 4 in Step 2: Under the WAS_SOA10134_Installables/cfg folder, edit the config.properties file, as per the environment.

   The configuration script will configure ESB-DT Server on MachineC.

3. Log in to the WebSphere Admin Console and verify that the ESB-DT server is created. Modify the DT_OC4J_HOST and DT_OC4J_PORT parameters in the ESB_PARAMETER (oraesb) table with hostName/port value of the ESB-DT server.

   Note:

   For ESB-DT HA, an active-passive cluster needs to be setup separately. ESB_DT needs to run as a single instance and the host/port of this instance should be updated in DT_OC4J_HOST and DT_OC4J_PORT fields of ESB_PARAMETER table in the ORAESB schema.