A Configuring BPELPM on WebSphere for Multiple Federated Nodes

This appendix describes the steps to be followed to configure BPELPM 10.1.3.3 in a Multiple Federated Node environment of WebSphere 6.1 ND and preparing the multiple instances of BPELPM as a HA setup.

• Install WebSphere ND 6.1

• BPELPM 10.1.3.3 Configuration on Federated Multi Node environment

A.1 Install WebSphere ND 6.1

The supported topology for HA of OracleSOASuite is by configuring Multiple federated Websphere nodes within a cell with one Deployment Manager. The HA topology for ESB is to have a single ESB-DesignTime (esbservices) and multiple ESB-Runtimes(esbservices-runtime) within the Websphere Cell pointing to the same oraesb database. The ESB DesignTime should be uninstalled from the IBM console, on Websphere Nodes, which need to host only the ESB-Runtime.

Perform the following steps to install WebSphere ND 6.1 on Node01 and Node02:

Node01

1. Launch the WebSphere 6.1 ND Installation wizard.

2. Select Cell (Deployment Manager and a Managed Node) as the environment and complete the installation.

   This creates the following:

   2 Profiles: DMgr01 and AppSrv01

   1 Cell: for example, Cell01

   2 Nodes: CellManager01 and Node01

   By Default in this environment, the Node01 is federated with Cell01

3. Run startManager from DMgr01/bin.

4. Run startNode from AppSrv01/bin.

5. Access IBM Console from http://<hostname>:<port>/ibm/console.

   Note:

   Check for the actual soap connector port from the WC_adminhost attribute in serverindex.xml of CellManager01.

Node02

1. Launch the Profile Management Tool and create a new profile.

2. Select Custom profile as the environment.

3. Select the <hostname> and <soap connector port> of the Deployment Manager with which this new node should be federated.

   Note:

   Check for the actual soap connector port from the SOAP_CONNECTOR_ADDRESS attribute in serverindex.xml of CellManager01.

4. Complete creating the profile.

   This creates the following:

   1 Profile: Custom01

   1 Node: for example, Node02, which is federated to Cell01

5. Run startNode from Custom01/bin.

A.2 BPELPM 10.1.3.3 Configuration on Federated Multi Node environment

The steps to configure BPELPM 10.1.3.3 on WebSphere 6.1 for Federated multi Node environment are by and large the same as for a single single Node environment. The differences are mentioned below:

Ensure that the Deployment Manager and both the NodeAgents (Node01 and Node02) are running. In case of federated multi node environment, the setup scripts should be run individually on each node.

A.2.1 Running the configureSOA.bat/sh for Node01

Select the following values in constants.properties:

• CELL_NAME= Cell01

• NODE_NAME= Node01

• PROFILE_NAME= AppSrv01

• BPEL_HOME= [The directory path in which Oracle BPEL Process Manager is installed on the same host as this Node.]

Other attribute values are unambiguous.

After successful execution of setup.sh/bat, the following would be created:

• OracleSOAServer on Node01 configured to run on port 9700

  This can be verified from IBM admin console under oracleSOAServer -> Ports -> WC_defaulthost.

A.2.2 Running the configureSOA.bat/sh for Node02

Select the following values in constants.properties:

• CELL_NAME= Cell01

• NODE_NAME= Node01

• PROFILE_NAME= Custom01

Other attribute values are unambiguous.

After successful execution of setup.sh/bat, the following would be created:

• OracleSOAServer on Node02 configured to run on port 9700

  If Node02 and Node01 are created on the same host then due to port clash, then both the oracleSOAServers cannot be started together. This port should be changed manually to a different value, for example, 9702.

  This can be modified from IBM admin console under oracleSOAServer -> Ports -> WC_defaulthost.

A.2.3 Virtual Hosts

Also ensure that the new ports are added to the list of Virtual Hosts. This can be done from the IBM admin console under Virtual Hosts -> default_host -> Host Aliases.The IBM Admin console would display the following servers under Application Servers after the above steps.

Table A-1 Server Details

Name	Node	Version
oracleSOAServer	sraghura-pcNode05	ND 6.1.0.3
oracleSOAServer	sraghura-pcNode03	ND 6.1.0.3

A.2.4 Configuring BPELPM on 2 Nodes for HA

Use a software Load Balancer, which maps the 2 BPELPM Node instances to a single Load Balancing URL, as follows:

• http://<hostname>:load_bal_port/

  • http://<hostname>:9700

  • http://<hostname>:9702

Modify the soapCallbackURL to http://<hostname>:load_bal_port/ in <BPEL_HOME>/system/config/collaxa-config.xml.

Then, restart oracleSOAServer on both Node01 and Node02.