Highly Available WebSphere Business Integration Solutions

Chapter 5. Implementing the solution 85

򐂰 WebSphere Business Integration Toolset 4.2.2.2 for Windows 2000 (Fix Pack

2)

򐂰 WebSphere Business Integration Message Broker Tooling for Windows 5.0

CSD 3

򐂰 WebSphere Business Integration Adapters for AIX:

– JText 5.4.4

–JDBC 2.4.3

– WebSphere MQ Integrator Broker 2.5.1

򐂰 XML Datahandler 2.5

It is recommended that the latest supported software and code fixes are applied

to your specific Business Integration solution.

5.6 Adding applications to HACMP control

1. Shut down the cluster if it is already running on all nodes of the cluster:

smitty clstop

2. Configure application server:

a. Log on to the AIX console.

b. smitty hacmp

c. Extended Configuration

d. Extended Resource Configuration

e. HACMP Extended Resources Configuration

f. Configure HACMP application server.

g. Add an application server such as WICS422HA.

h. Select the server name.

i. Select the location of the start script such as

$CROSSWORLDS/bin/hascripts/wics_ha_start

j. Select the location of the start script such as

$CROSSWORLDS/bin/hascripts/wics_ha_stop

k. Exit by pressing Enter.

3. Configure the application monitor:

a. smitty hacmp

b. Extended Configuration

c. Extended Resource Configuration

86 Highly Available WebSphere Business Integration Solutions

d. HACMP Extended Resource Configuration

e. Configure the HACMP application monitoring.

f. Configure the custom application monitor.

g. Add the custom application monitor.

h. Select the server name.

i. Stabilization Interval: choose 200 (seconds) to allow the cluster to start the

applications.

j. The restart count is 3.

k. The restart interval is 0.

l. The clean up method is usually the stop script.

m. The restart method is usually the start script.

n. Exit by pressing Enter.

4. Adding application server to the resource group:

a. smitty hacmp

b. Extended Configuration

c. Extended Resource Configuration

d. HACMP Extended Resource Group Configuration

e. Change/show resource attributes for a resource group.

f. Select the resource group.

g. Select the application server.

h. Exit by pressing Enter.

5. Synchronize the cluster:

a. smitty hacmp

b. Extended configuration

c. Extended verification and synchronization

d. Use defaults and press Enter.

Verify the success of the HACMP configuration by checking the log file on

/tmp/hacamp.out. Now start the cluster with:

smitty clstart

choose Reacquire resources after forced down to false.

Execute usr/es/sbin/cluster/utilities/clRGinfo to check whether the

resource group is running.