B SOA Suite 10.1.3.4 HA Setup Using WebLogic Cluster

This appendix describes the configuration steps for installing and configuring clustered Oracle SOA Suite 10.1.3.4 on WebLogic Server 9.2. This appendix contains the following sections:

Sample HA Topology
Steps for Installation and Configuration of the Sample HA Topology
Post Installation Steps

B.1 Sample HA Topology

This is a sample topology with the following chosen as its members.

DOMAIN - Single domain (SOADomain)
CLUSTER - SOA cluster will contain two managed servers (OracleSOAServer1 and OracleSOAServer2)
MACHINES - Two machines each hosting one managed server (Machine1 and Machine2)
ADMIN SERVER - Single admin server will run on Machine1

You can extend the same procedure to configure a cluster with more members as per your requirement. Figure B-1 describes the sample topology diagram.

Figure B-1 Topology Diagram

Figure B-2 describes the flowchart of the script to be executed for the sample topology.

Figure B-2 Scripts Execution Flowchart

B.2 Steps for Installation and Configuration of the Sample HA Topology

This section consists the detailed steps for installation and configuration of the sample HA topology mentioned in Sample HA Topology.

B.2.1 Prerequisites

The following prerequisites should be met for the installation and configuration of the sample HA topology:

Install WebLogic Server 9.2 on both machines (Machine1 and Machine2).
Download the Weblogic_SOA10134_HA.zip file and extract on both the machines.

B.2.2 Installing Database

Common Dehydration Store:

Install Oracle Database 10.2.x on a common machine (either Machine1 or Machine2).
Run IRCA from SOASuite 10.1.3.1 Install Pack/Disk1/Soa_schemas/irca to create ORABPEL/ORAESB/ORAWSM schemas on the above database.
Run the 10.1.3.4 schema upgrade scripts for ORABPEL/ORAESB schemas from SOASuite 10.1.3.4 Install Pack/Disk1/Soa_schemas_upgrade.

B.2.3 SOA Suite 10.1.3.4 (for OC4J) Installation on both Machines

Perform the following steps to install Oracle SOA Suite 10.1.3.1:

Install Oracle SOA Suite 10.1.3.1 for OC4J on both the machines (Machine1 and Machine2).
Choose Basic Installation of SOA Suite 10.1.3.4. For Linux, choose the above-created database during installation. Choose the same path for installation on both machines.
After installation, ensure that the ORACLE_HOME on both machines is pointing to the same location.
Apply PatchSet 4 (Oracle SOASuite 10.1.3.4 for OC4J) on both the installations.
Apply Patch for Oracle SOA Suite 10.1.3.4 on WebLogic 9.2.

Refer to Step 6: Apply Patch for Oracle SOA Suite 10.1.3.4 on WebLogic 9.2 for more information on applying the patch.
Install Oracle SOA Suite 10.1.3.4 for OC4J on both the physical machines (Machine1 and Machine2).

Note:
It is necessary to have Oracle SOA Suite for OC4J installed on both the physical machines in the above scenario.

B.2.4 Steps to Configure HA Setup for SOA 10.1.3.3 on WebLogic 9.2

Perform the following steps to configure HA setup for SOA 10.1.3.3 on WebLogic 9.2.

Note:

All paths in this section are relative to Weblogic_SOA10134_HA unzip location.

Make appropriate entries in the SOADomain.properties file and run setupDomain.bat/sh on Machine1.

The domain wide details such as Domain properties, Admin Server properties, DataSource properties will need to be filled in SOADomain.properties.

This script will prompt for the password to be set for the default 'weblogic' user.
Make appropriate entries in the SOANode.properties file for OracleSOAServer1 and run addNode.bat/sh on Machine1.

Modify the SOANode.properties file entries for OracleSOAServer2 and run the addNode.bat/sh script again on same Machine (Machine1).

This can be repeated further for more managed servers in the cluster. Ensure that for every run of this script the SOANode.properties values are changed for the appropriate managed server.

This script will prompt for the user id and password for connecting to the admin server.
After adding all the required managed servers, run the packDomain.bat/sh script on Machine1.

Ensure that this step is performed only after all the managed servers are added to the domain using the addNode.bat/sh script.
Transfer the SOAManagedServerTemplate.jar from WL_HA_SOA_Installables/template directory of Machine1 to WL_HA_SOA_Installables/template directory of Machine2.

This step can be repeated for more machines if required.
Run the unpackDomain.bat/sh script on Machine2. This step can be repeated for more machines, if required.
Edit the SOANode.properties file and run configNode.bat/sh on Machine1. and Machine2. Ensure that the SOANode.properties file entries are updated for each machine.

This script will prompt for the user id and password for connecting to the admin server.
Run configDomain.bat/sh on Machine1. This needs to be run only on Machine1. The SOA Applications will be deployed to the cluster in this step.

This script will prompt for the user id and password for connecting to the admin server.

B.3 Post Installation Steps

Perform the following post installation steps:

B.3.1 NodeManager Setting

Navigate to the <BEA_HOME>/weblogic92/server/bin directory and edit the startNodemanager script to add following property as part of the JAVA_OPTIONS arguments.On Windows: set JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.security.SSL.ignoreHostnameVerification=true

On Unix:

set JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.SSL.ignoreHostnameVerification=true"

B.3.2 Configure Collaxa-config for BPEL

Update the following properties in SOA_HOME/bpel/system/config/collaxa-config.xml on both the machines to configure HA for BPEL runtime:

bpelPlatform = weblogic_8
soapServerUrl = LoadBalancerHost:port
soapCallbackUrl = LoadBalancerHost:port
enableCluster = true
clusterName = LoadBalancerHost:port

B.3.3 Configure JGroups for BPEL

Update the <SOA_HOME>/bpel/system/config/jgroups-protocol.xml file on both the machines to setup JGroups between the BPEL instances.This is used for BPEL process and adapter state synchronization between BPEL instances.

B.3.4 ESB Design Time (ESB-DT)

It is not recommended to have ESB-DT running in the same HA cluster as ESB Runtime (ESB-RT). Select the option mentioned below:

Run ESB-DT in a separate non-clustered managed server outside the domain of the cluster.

Download and install Oracle SOA Suite 10.1.3.4 for Weblogic 9.2 and complete the setup.

After running the post installation, disable or delete all the deployments except esbservices deployment on the managed server.

Modify the DT_OC4J_HOST and DT_OC4J_PORT parameter in ESB_PARAMETER (oraesb) table with hostName/port of the new managed server.

For ESB-DT HA, an Active-Passive cluster needs to be setup separately for ESB-DT.

ESB_DT needs to run as a singleton 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.

B.3.5 Load Balancer

Perform the following steps to configure external load balancer Apache for WebLogic Cluster setup:

Refer to http://e-docs.bea.com/wls/docs92/plugins/apache.html to install and configure Apache plugin on WebLogic server.
Mention the load balancer hostname and port name in <SOA_HOME>/bpel/utilities/ant-orabpel.properties and <SOA_HOME>/bpel/system/config/collaxa-config.xml files on all machines.

B.3.6 Addresses

The SOA Apps will be available at the following addresses post installation.

Admin Server: http://Machine1: 8001/console
BPEL Console: http://LoadBalancerhost: port/BPELConsole
OWSM: http://LoadBalancer: port/ccore/Login.jsp
WorkList App: http://LoadBalancerhost: port/
RuleAuthor : http://LoadBalancerhost: port/ruleauthor
ESB-DT: http://Machine1: 9700/esb