WebSphere Application Server Clustering 6.0.

2 Document

Created by
Sandip Desale

April 2006
 1. Software Needed:

a. WAS 6.0.2
b. WAS Network Deployment Manager 6.0.2 [NDM]
c. IBM HTTP Server V 2.0.47
d. Microsoft’s IIS v5.0
e. SQL Server 2000
f. Data Direct connectJDBC Release 3.5 driver for SQL Server

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 1 of 35

 2. Installations:

WebSphere 6.0.2 Clustering Installation

a. Install WAS6.0.2 Application server on 2 Different machines.

b. Install WASv6.0.2 Network Deployment Manager on one machine. Create a profile DMGR
using profile creator.
c. Install IBM HTTP Server v2.0.47 on the same machine where WASNDM is installed.
d. Install IBM HTTP Server Plug-in on the same machine where WASNDM is installed.
e. Install connectJDBC driver for SQL Server. You can download latest connectJDBC driver
from www.datadirect.com site.

Steps to Configure NDM

1. Create Profile DMGR using profile Creator if not created while installation.

2. Start NDM by giving following command…

<NDM Install Folder>\profile\DMGR\bin startManager

3. After successful start of NDM go to

<NDM Install Folder>\profile\DMGR \logs\SystemOut.log
Read for “SOAP Connector Port” [Default Port: 8879].

4. On Node machines where WAS6.0.2 is installed. [On both machines with WAS6.0.2 setup] and
execute the batch file addNode as explained below…
<WAS6.0.2 Installation Directory>\profiles\default\bin 
addNode <NDM Machine Name> 8879

e.g. addNode PUNITP64411D 8879

Here on PUNITP64411D system WAS-NDM is installed.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 2 of 35

 5. Open NDM Administrative console of NDM. You can check the nodes are added or not.
System AdministrationNodes

6. Administrative console.
a. Click on Servers Clusters New
b. Create New Cluster and Name it as ONSCRVCluster press Next

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 3 of 35

 Fig10

7. Add Servers to Cluster

a. Enter Server Name – ONSCRVServerPUNITP63880
b. Select Node on which you want to create this server
i. Select PUNITP63880DNode01(6.0.2.0) in select Node drop Down box
ii. Keep other settings as default…

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 4 of 35

 Federated Nodes
will list in the
combo

iii. Click on Apply button. Server will get added to the list Displayed in the following
screen.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 5 of 35

 c. Follow the similar steps for adding server for another node PUNITP63974D. After
clicking Apply button the screen looks like as per below…

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 6 of 35

 d. Now click on Next Button. After adding
second node server

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 7 of 35

 e. Click on Finish button. It takes few minutes to create a cluster.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 8 of 35

 f. Click on Save Link to the changed configuration to Master Configuration.

Do not forget the check the check box labeled Synchronize changes with Nodes and click on Save
Button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 9 of 35

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 10 of 35
 g. Click on Ok button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 11 of 35

 h. Now your new cluster is created. You can check the Cluster Topology by clicking on
Cluster Topology Link which is provided under Servers Link.
ServersCluster Topology

8. After adding Servers Nodes to Cluster, stop Manager

StopManager

9. Now Start the Node from the respective WAS6.0.2 servers

<WAS HOME>\bin\startNode

10. Install EAR or WAR as per the WAS6.0.2 Installation Documents.

If you directly installing application WAR or EAR through NDM Admin console then map the
modules to cluster directly rather than mapping the modules to individual servers.

Session Management Using Database

11. Configure Data Source separately for both the WAS6.0.2 Server Nodes
a. Click on ResourcesJDBC Providers

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 12 of 35

 b. Now click on Browse Nodes button and select a node PUNITP63880DNode01 and click on
Ok button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 13 of 35

 c. Now click on Browse Servers button and select ONSCRVServerPUNITP63880 server and
click on Ok button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 14 of 35

 d. Then click on Apply button.

Now you can create a data source for ONSCRVServerPUNITP63880 which is on node
PUNITP63880DNode01.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 15 of 35

 Make different
selection of Node &
Server and then create
a new data source

e. Now Click on New button for creating a data source.

i. Select a Data Base Type in Step 1 drop down box.

ii. As soon as you select the SQL Server in first dropdown, second (Step 2)
dropdown will get enabled.

iii. Then select Provider type as WebSphere embedded ConnectJDBC Driver for
SQL Server.

iv. Then in step 3, select XA Data Source.

Screen will look like as follows…

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 16 of 35

 v. Click on Next Button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 17 of 35

 vi. Click on Ok Button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 18 of 35

 vii. Now click on Link WebSphere embedded ConnectJDBC driver for MS SQL Server (XA) ,
as shown in above figure.

viii. Now click on Data sources (Version 4) link.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 19 of 35

 1. Create a new Data Source. Click on New button.

a. Enter Name as ONSCRVPUNITP63880D

b. Enter JNDI Name as JDBC/ONSSessions
c. Enter Database Name as ONSCRVSessions
d. Enter User ID as sa
e. Enter Password as sa

No Need to change other description and no need to add category.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 20 of 35

 2. Click on Ok button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 21 of 35

 3. Now click on ONSCRVPUNITP63880D Link as shown in above figure.

4. Then Click on Custom Properties link. You will see following screen.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 22 of 35

 a. Then click on serverName Link as displayed in the above figure.

b. Enter the value field for SQL server machine name and click on
Ok button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 23 of 35

 5. Then click on Save Link which is displayed on the screen and then Save
button.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 24 of 35

Create a data base 'ONSCRVSessions' on SQL Server machine named PUNITP63974D.

6. Repeat the same procedure for setting a Data source for another node.
Keep the JNDI name same for both the nodes.

Session Management of the servers…

12. Click on ServersApplication Servers link.

13. Then click on ONSCRVServerPUNITP63880 server link which is displayed on the screen.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 25 of 35

 14. Click on Session Management link as displayed in the above figure.

a. Click the check box of Enable URL rewriting label and click on Ok button.

b. Again Click on Session Management link as displayed in the above figure. Then click on
Distributed environment settings link as displayed in the following figure.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 26 of 35

 c. Then Select Data Base radio button

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 27 of 35

 d. Click on Database link which is provided and shown in the above figure.

i. Enter the Data Source JNDI Name as JDBC/ONSSessions

(This is given while creating Data Source in the above mentioned steps)

ii. Enter User Id as sa

iii. Enter Password as sa

iv. Select DB Row Size as ROW SIZE 32KB

v. Check the check box provided against Use multi row schema label.

Screen will look like as per below…

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 28 of 35

 vi. Click on Ok button.

vii. Then click on Custom tuning parameters link which is displayed on the screen.

viii. Select the tuning level as Low and click on Ok button.

Save all the changes which are made in configuration to master configuration.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 29 of 35

 15. Follow the same steps mentioned in item number 14 for other application server,
ONSCRVServerPUNITP63974 as well.

NOTE:

1. Please check for the System time. All machines should have the same System time.

2. While configuring the Data source try to have different Database Connection pool for different Node
Agents.

3. Cluster Hierarchy

ONSCRVCluster
Nodes
PUNITP63880DNode01 (ND 6.0.2.0)
Cluster members
ONSCRVServerPUNITP63880
punitp63974dNode01 (ND 6.0.2.0)
Cluster members
ONSCRVServerPUNITP63974

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 30 of 35

 Setting plug-in for NDM

Following steps needs to be followed for any type of HTTP Server. E.g. IIS, IBM HTTP
Server, Apache Web Server etc.

Install application WAR or EAR on NDM.

2. While installing select Cluster Name while doing server mapping for
modules of Application WAR or EAR.
Complete the installation of application as per application installation document.
Then Open Command Prompt…
5. Execute the GenPluginCfg.bat batch file from the <WAS-NDM
HOME>\bin folder without giving any parameters…

Copy the Plug-in file from <WAS-NDM-HOME>/profiles/Dmgr\config\cells folder.

7. Paste the same file in WAS a v6.0.2 node (both systems where WAS v6.0.2
is installed)in the following folder path…
<WAS-HOME>/profiles/default/config/cells
8. Open all the Plugin-cfg.xml file and change the path <WAS-NDM-
HOME> to <WAS-HOME> of the respective machines

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 31 of 35

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 32 of 35
Apache HTTP Web Server v 2.0.47 Plug-in configuration

Install the Apache Web Server (HTTP Serve v2.0.47) on Machine where NDM is installed
Install Web Server Plug-in for HTTP Server v2.0 on Machine where NDM is installed.
While installing this it will ask for the HTTP Server installation folder. So install HTTP
Server first then install the plug-in for that HTTP Server.
Start HTTP Server.
Copy the Plug-in file from WAS-NDM-HOME>/profiles/Dmgr\config\cells and paste the same in
following folder…<HTTP PLUGIN INSTALL FOLDER>\config\cells
4. Open the entire Plugin-cfg.xml file and change the path <WAS-NDM-
HOME> to <WAS-PLUGIN-HOME> of the respective machines.
5. Restart the NDM as well as HTTP Server.

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 33 of 35

Microsoft IIS Plug-in Configuration

1. Install the Microsoft IIS v5.0 on Machine where NDM is installed

2. Install Web Server Plug-in for Microsoft IIS on Machine where NDM is installed.
3. Copy the Plug-in file from WAS-NDM-HOME>/profiles/Dmgr\config\cells and paste the same in
following folder…<IIS PLUGIN INSTALL FOLDER>\config\cells
4. Open the entire Plugin-cfg.xml file and change the path <WAS-NDM-HOME> to <IIS-PLUGIN-
HOME> of the respective machines.
5. Open Command Prompt and execute the following command.
configureIIS -install <plug-in file> <virtual directory> <washome> <description>
It will create the Virtual folder for WAS.
e.g. –
IIS Plug-in Home  D:\WASIISPlugin
D:\WASIISPlugin\bin> configureIIS -install iisWASPlugin_http.dll IISWASNDM
D:\WASIISPlugin\bin VirtualFolderforWAS

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 34 of 35

 6. Restart the IIS using IISRESET command from command prompt

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 35 of 35

WAS6.0.2 Clustering Doc Ver.Rev. 1.00 36 of 35