Weblogic Cluster spanning multiple machines (WL6.1)

Document ID : KB000031699
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:

Weblogic Cluster spanning multiple machines (WL6.1)

The procedure is being given for Weblogic 6.1. (For other versions the procedure will be similar with slight differences.)

 

Instructions:

Each WebLogic Server domain has one server instance acting as the Administration Server. In a domain, server instances other than the Administration Server are referred to as Managed Servers

1. Use an existing domain like WLS "Examples" with Administration Server and Clustered Managed Servers on the Admin server.

2. On the three different boxes, install the same WL6.1 version along with using the same ports and passwords, Use one of the boxes as the Admin box and 2 others as Managed Servers.

3. Create a new Cluster by clicking on Configure a New Cluster on the Admin server console.

4. Assign a unique name to the cluster and also insert the IP addresses for all Managed Servers participating in cluster configuration in the Cluster Address box and click on Create.

5. Add new Managed Servers to Servers on the console by clicking on Configure a new Server. Under Cluster tab for new servers, select the new cluster and click on Add.

6. You need to deploy whatever component under Deployment that needs to be monitored to the new cluster by clicking on Target and going to Cluster tab and add the new cluster to chosen box and click on Apply.

7. Now go to each Managed Server. Open the bat or shell file for running the webapp. For example, edit startExamplesServer.sh.

8. Add/Modify the following in sh file:

-Dweblogic.Name=clusterServer1

-Dweblogic.management.server=192.168.0.101:6001 

-Dweblogic.management.username=system

-Dweblogic.management.password=systemPassword 

The server instance's cluster configuration is stored by the Administration Server, so you do not need to explicitly include address binding or multicast information in the command line. You do, however, need to specify:

weblogic.Name, to identify the clustered instance you want to start. 

weblogic.management.server, to identify the host and port number of the Administration Server that stores the clustered instance's configuration. 

weblogic.management.username, to specify a username to connect to the Administration Server. 

weblogic.management.password, to specify the user's password. 

9. As the clustered instance boots, monitor the log messages to see that it joins the cluster. The instance begins by binding the multicast address and common port number of the cluster: 

Starting Cluster Service ....

<Jul 25, 2001 6:35:17 PM PDT> <Notice> <WebLogicServer> <ListenThread listening on port 7001, ip address 172.17.13.25>

<Jul 25, 2001 6:35:18 PM PDT> <Notice> <Cluster> <Listening for multicast messages (cluster MyCluster) on port 7001 at address 239.0.0.84>

<Jul 25, 2001 6:35:18 PM PDT> <Notice> <WebLogicServer> <Started WebLogic Managed Server "MyServer-1" for domain "mydomain" running in Production Mode>

10. To verify that all clustered instances are participating in the cluster, open the Administration Console. Select the cluster, click the Monitoring tab, then select Monitor server participation in cluster. If one or more of the started server instances do not appear in the display, verify that the server instances have been configured with the correct multicast address and port number.