Weblogic server clustering

Environment

1. Physical machine 2–linux2————Webcenter/Weblogic
2. Physical machine 3–linux3————Webcenter/Weblogic

Versions

1. Weblogic Server —-10.3.3

Directory Structure layout on linux2 & linux3

1. MW_HOME=/u01/oracle
2. WLS_HOME=$MW_HOME/wlserver_10.3
3. Admin Server—–/u01/admin/sample/aserver/sample (Admin Server is only  on linux2)
4. Managed Server—-/u01/mserver/sample/sample

5. Apps —/u01/mserver/sample/apps

Admin & Managed Servers

Admin Server

1. sample_Admin Server —linux2

Managed Servers

1. sserver1 & sserver2—linux2

2.mserver1—linux2

3.mserver2—linux3

Clustering Type : Multicast

Clustered  Name : mserver (mserver1 & mserver2)

Step1 :  Install weblogic server on linux2 & linux3.

WLS Install

Step2.  Create Domain on  linux2.

cd $MW_HOME/wlserver_10.3/common/bin

$ ./config.sh

Select Create a new WebLogic Domain

Select Oracle JRF

Domain Name: sample

Domain location:/u01/admin/sample/aserver

Enter Weblogic Server Administrator username and password

1.Name :weblogic

Select Administration Server, Managed Servers,Clusters and Machines & Deployments

Administration Server

1. Name : Sample_AdminServer

2. Listen Address : All Local Address

3.Listen Port: 10001

Managed Servers

1. mserver1:9003 & sserver1:9005 -linux2.com

2. mserver2:9003 &  sserver2:9005-linux3.com

Clusters

1. mserver : multicast

Assign Servers to Clusters

1. Cluseter: mserver–mserver1 & mserver2

Configuring Machines

1.Server1: Node Manger Listener–linux2.com:5556

2.Server2:Nodemanager Listener–linux3.com:5556

Assign Servers to Machines

Target Deployments to Clusters or Servers

1. Cluster: mserver : select library to include jrf libraries in mserver cluster

Target Services to Cluster or Servers

Configuration Sumamry

Creating Domain

Step 3.   on linux2 : pack the sample domain using pack.sh

cd $MW_HOME/wlserver_10.3/common/bin

./pack.sh -managed=true -domain=/u01/admin/sample/aserver/sample -template=sample.jar -template_name=sample

< read domain from “/u01/admin/sample/aserver/sample”
>>  succeed: read domain from “/u01/admin/sample/aserver/sample”
<< set config option Managed to “true”
>>  succeed: set config option Managed to “true”
<< write template to “/u01/oracle/wlserver_10.3/common/bin/sample.jar”
……………………………………………………………………………………….
>>  succeed: write template to “/u01/oracle/wlserver_10.3/common/bin/sample.jar”
<< close template
>>  succeed: close template

Step 4. on linux2 . unpack the sample domain using unpack.sh

cd $MW_HOME/wlserver_10.3/common/bin

./unpack.sh -domain=/u01/mserver/sample/sample -template=sample.jar -overwrite_domain=true  -app_dir=u01/mserver/sample/apps
<< read template from “/u01/oracle/wlserver_10.3/common/bin/sample.jar”
>>  succeed: read template from “/u01/oracle/wlserver_10.3/common/bin/sample.jar”
<< set config option OverwriteDomain to “true”
>>  succeed: set config option OverwriteDomain to “true”
<< set config option AppDir to “/u01/oracle/wlserver_10.3/common/bin/u01/mserver/sample/apps”
>>  succeed: set config option AppDir to “/u01/oracle/wlserver_10.3/common/bin/u01/mserver/sample/apps”
<< set config option DomainName to “sample”
>>  succeed: set config option DomainName to “sample”
<< write Domain to “/u01/mserver/sample/sample”
…………………………………………………………………………………..
>>  succeed: write Domain to “/u01/mserver/sample/sample”
<< close template
>>  succeed: close template

Step 5. secure copy  the template sample.jar from linux2 to oracle@linux 3:/u01/oracle/wlserver_10.3/common/bin/

Step 6. on linux3. unpack the sample domain using unpack.sh

cd $MW_HOME/wlserver_10.3/common/bin

./unpack.sh -domain=/u01/mserver/sample/sample  -template=sample.jar -app_dir=u01/mserver/sample/apps

./unpack.sh -domain=/u01/mserver/sample/sample  -template=sample.jar -app_dir=u01/mserver/sample/apps
<< read template from “/u01/oracle/wlserver_10.3/common/bin/sample.jar”
>>  succeed: read template from “/u01/oracle/wlserver_10.3/common/bin/sample.jar”
<< set config option AppDir to “/u01/oracle/wlserver_10.3/common/bin/u01/mserver/sample/apps”
>>  succeed: set config option AppDir to “/u01/oracle/wlserver_10.3/common/bin/u01/mserver/sample/apps”
<< set config option DomainName to “sample”
>>  succeed: set config option DomainName to “sample”
<< write Domain to “/u01/mserver/sample/sample”
…………………………………………………………………………………..
>>  succeed: write Domain to “/u01/mserver/sample/sample”
<< close template
>>  succeed: close template

Step 7. on linux2 & linux3 start the node manager.

cd $MW_HOME/wlserver_10.3/server/bin

nohup ./startNodeManager.sh &

Step 8. on linux2. Start the Admin Server

cd /u01/admin/sample/aserver/sample/bin

nohup ./startWebLogic.sh &

Step9  :Access the console of webloigc server http://linux2.com:10001/console and start the Managed Servers

Step 10 . Make sure Node manager on linux3. is reachable

Step 11. Start the Managed Servers on linux2 and linux3.

This slideshow requires JavaScript.

Next : I will try to put more information on Load Balancing Techniques &  proxy configuration

Related Links

1. Weblogic Server Installation

2. Configuring  Oracle Single Sign-on for Weblogic Server

3. Weblogic Server Administrator password

4.  Increasing the Heap Size in Weblogic Server