The attached doc has instruction to configure WAS for cluster.

Also it’s available in this link –

http://www.ssi-eroom.com/eRoom/MNHM/MinnesotaHealthMatch/0_b0ad

The HM app can be on the same server, but has to be on a different web context name. The only
change we have to do on the app is modifying the contol.js script in WebContext/albion/script
folder. The function getBaseURL hardcoded value needs to correspond with the web context
name you gave above.

function getBaseURL(){
return "/healthmatch/";
}

WebSphere Network Deployment Installation Guide

Prerequisites:
 WebSphere Application Server 5.0 installation CD
 WebSphere Network Deployment installation CD

1. Run WebSphere Application Server (WAS) installation CD.

When prompted for Select a Language, select your language of choice.
From WebSphere Application Server LaunchPad, select Install the product.
When prompted for Select a language…, select your language of choice.
Click Next.
Accept the licensing agreement, and click Next.
Select Full or Custom setup, and click Next.
If you select Custom setup, you will be prompted to select components to install.
For IBM WebSphere Application Server,
specify E:\Program Files\IBM\WebSphere\AppServer.
For IBM HTTP Server,
specify E:\Program Files\IBM\WebSphere\IBMHttpServer.
Click Next.
Uncheck all boxes on running an application as a service, and click Next
Accept default node name and hostname, and click Next.
Verify your selected features for install, and click Next.
The installation process would proceed now.
Click Next and Finish.
From WebSphere Application Server LaunchPad, select Exit.
This completes the WebSphere Application Server installation.
2. Apply any appropriate IBM WAS patches.
3. From Windows application launch bar, select First Steps from WAS menu.
Select Start the Server from the selection list.
Verify for ADMU3000I: Server server1 open for e-business… on the console before
proceeding.
4. To start Administrative Console.
Select Administrative Console from the selection list.
When the Internet browser is launched, enter WAS for user id.
5. To create a web application server template.
Select Server > Application Servers.

pwdpw55 Page 1 10/23/2008

 Click New to create a new server.
For Server name, specify serverTemplate.
Click Next, and click Finish.
Select serverTemplate from the list.
Under Additional Properties, select Web Container.
Under Additional Properties, select HTTP Transports, and delete all the HTTP
Transports on the list.
Click Save from the WAS toolbar (located below WAS banner), and confirm the
saving of the Master Configuration.
This completes the installation and configuration of WAS.
6. From Windows application launch bar, select First Steps from WAS menu.
Select Start the Server from the selection list.
Verify for ADMU3000I: Server server1 open for e-business… on the console before
proceeding.
7. Run WebSphere Network Deployment (ND) installation CD. When prompted for
Select a Language, select your language of choice.
From WebSphere Application Server LaunchPad, select Install the product.
When prompted for Select a language…, select your language of choice.
Click Next.
Accept the licensing agreement, and click Next.
Check box on Reconfigure the product…, and click Next.
Select the ND features required, and click Next.
For IBM WebSphere Application Server Network Deployment,
specify E:\Program Files\IBM\WebSphere\DeploymentManager.
Accept default node name, host name and cell name, and click Next.
Uncheck the box on WAS ND as a service, and click Next
Verify your selected features for install, and click Next.
The installation process would proceed now.
Click Next and Finish.
From WebSphere Application Server LaunchPad, select Exit.
This completes the WebSphere Application Server Network Deployment installation.
8. Apply any appropriate IBM WAS ND patches.
9. From Windows application launch bar, select First Steps from WAS ND menu.
Select Start the Deployment Manager from the selection list.
Verify for ADMU3000I: Server dmgr open for e-business… on the console before
proceeding.
10. To start Administrative Console.
Select Administrative Console from the selection list.
When the Internet browser is launched, enter WAS for user id.
11. To create a new node for the WAS.
Select System Administration > Nodes.
Click Add Node to create a new node.
For Server name, specify the host of the node you want to manage.
Check Include Applications to include all the applications from the new node.
Click OK.

pwdpw55 Page 2 10/23/2008

 Verify that WAS ND has successfully added the node to the WAS ND Manager.
Logout as instructed, and login again. Verify the new server is added.
12. To create a cluster and add two application servers to it.
Select Servers > Clusters.
Click New to create a new cluster.
Specify a name for the cluster.
For Existing server, select Do not include…. Click Next.
Specify clone1 for the server name.
For Select template, select Existing application server and select /serverTemplate.
Click Apply.
Repeat for clone2 server. Click Next and Finish.
13. To add HTTP Transports to the application servers.
Select Servers > Application Servers.
Select clone1.
Under Additional Properties, select Web Container.
Under Additional Properties, select HTTP Transports, and click New.
For Host, specify *, and for Port, specify 9080. Click OK.
Repeat for clone2, but specify 9081 for the port.
Click Save from the WAS ND toolbar (located below WAS ND banner), and confirm
the saving of the Master Configuration.
14. To add host aliases to the virtual host.
Select Environment > Virtual Hosts. Select default_host from the list.
Under Additional Properties, select Host Aliases. Click New.
For Host, specify *, and for Port, specify 80. Click OK.
Repeat for port 9080 and 9081. These ports correspond to ports defined in clone1 and
clone2 application servers.
Note: Port 80 is required to manage load-balancing request from the web server.
Click Save from the WAS ND toolbar (located below WAS ND banner), and confirm
the saving of the Master Configuration.
This completes the cluster configuration of WAS ND.
15. To add an enterprise application to a cluster.
Select Applications > Enterprise Applications. Click Install.
Specify the location of the deployment (.ear) file. Click Next.
Click Next until Step 3: Map modules to applications servers screen.
Check the module(s) to map.
For Clusters and Servers, select …cluster=cluster1. Click Apply.
Click Next, and click Finish.
Click Save from the WAS ND toolbar (located below WAS ND banner), and confirm
the saving of the Master Configuration.
This completes the application installation on a cluster environment.
16. Save Web Server plug-in file.
Select Environment > Update Web Server plugin. Click OK.
This step
17. To start the cluster.
Select Servers > Clusters.

pwdpw55 Page 3 10/23/2008

 Select the cluster to start, and click Start. The cluster will trigger its servers to start.
Verify that the servers and the application are started.
18. Start the application.
Select Applications > Enterprise Applications.
Check the box of the application to start. Click Start.
19. Modify location of the Web Server plug-in file.
Open E:\Program Files\IBM\WebSphere\IBMHttpServer\conf\httpd.conf.
Locate and modify the line as shown below.
WebSpherePluginConfig "E:\Program
Files\IBM\WebSphere\DeploymentManager/config/cells/plugin-cfg.xml"

start the apache.exe available in IBM

http://hmintegration:80/healthmatch/hmlogon/startup.html

MyCluster

Server1 Server2

9081 9082

HealthMatch
Application

pwdpw55 Page 4 10/23/2008