weblogic clustering
TRANSCRIPT
WEB LOGIC 8.1 SP2 CLUSTERING
FOUR SOFT LIMITED5Q1-A2 & A3, Cyber Towers
HITEC City, Madhapur,Hyderabad – 500033, Andhra Pradesh
INDIA Phone: +91(40) 23100600 / 601, Fax: +91(40) 23100602http://www.four-soft.com
Web Logic Clustering
DOCUMENT CONTROL SHEETDetails Name Designation/Department Date Email IDPrepared By Sastry D Sr Soft Engineer
/Technology04-Aug-05
Reviewed By Purushotham P Asst. Manager technology 05-Aug-
Approved By Mahaboob H General Manager 05-Aug-
A- Add, M- Modify, D- Delete
DOCUMENT AMENDMENT RECORD
Version No. Date Section No.
Page No.
Type of change (A/M/D) *
Brief Description of changes
Reasons for Changes
i
Web Logic Clustering
Table Of Contents 1 Introduction
1.1 Administrator Server
2 Clustering Installations 2.1 Configuring the Managed Server instances 2.2 Configure the Admin Server3 Starting the Admin and managed servers
ii
Web Logic Clustering
Introduction:
A Web Logic Server cluster consists of multiple Web Logic Server instances running simultaneously and working together to provide increased scalability and reliability.
The characteristics of the web logic cluster are:
Consists of Multiple Web logic Server instances to improve reliability.It appears to client as a single instance.Cluster can run on a single machine or on different machines.More instances can be added/removed to an existing clusterAll the server instances in a cluster must run the same version of Web logic Server
Domain
A domain is an interrelated set of Web logic Server instances/resources. Domain is managed as a unit. The web logic instances in the domain can be clustered, nonclustered, combination of clustered & nonclustered. One web logic server instance acts as an Admin Server.
Domain also contains the resources & services required by web logic server instances. The resource includes Machine definition, optional network channels, connectors, startup classes etc.
Any cluster/resources can’t be split in multiple domains
Advantages of Clustering
Scalability
More instances can be added; existing can be removed from the cluster dynamically depending upon the requirements. And this is can be done without interruption of service—the application continues to run without impact to clients and end users.
High Availability
If any instance fails the other instance would take care of the services offered by the failed instance. Thus the application will continue even after the failure of any instance.Failover
Failover is the unavailability of some set of processing task to the instance. A copy of the failed object is maintained & made available to the other instances to complete the task.
3
Web Logic Clustering
Load Balancing
Load balancing is the even distribution of the jobs among the various instances existing in the cluster. To do the load balancing the info about the services & location of all the instances must be available to all other instances, which can only be done through a proper communication between the instances.
Administrator ServerThe administration server is a web logic server instance in a domain that configures and manages the web logic server instances in that domain.
In a single domain there would be a single Admin server. When an admin server starts it loads the config.xml file for the domain. Admin server must be running when the configuration is modified.In a typical production environment that contains an Administration server and multiple web logic servers. When a server instance is started then the admin server is started first. So each & every server contacts the admin server before it starts.
The following fig shows the above discussed production environment.
4
Web Logic Clustering Once the servers in the clusters starts then even if the admin server fails the working doesn’t effected. Load balancing & the Failover remain available.
2 .Clustering Installation:
Installing Weblogic81SP2 on all the machines.
Configuration Steps For Cluster Setup
2.1 Configuring the Managed Server instances
Run the configuration wizardChoose “Create a new web logic configuration” click Next.
5
Machine - 1
Weblogic8.1SP2 Admin Server
Machine - 2
Weblogic8.1SP2 Managed Server 1
Machine - 3
Weblogic8.1SP2 Managed Server 2
Web Logic Clustering
Choose “Basic web logic Server domain” click Next
6
Web Logic Clustering
Choose Custom click Next
7
Web Logic Clustering
Give the values for all the attributes
Name of the managed server say managedserver1Listen address: IP address of the machine of the managedserver1Listen port: Say 7003Click Next
8
Web Logic Clustering
Managed Servers, clusters, and Machine configuration: Chose No and click Next
9
Web Logic Clustering
Database JDBC option: chose No and click Next.
10
Web Logic Clustering
Messaging JMS option: Chose No and click Next.
11
Web Logic Clustering
Configuring Username and Password: Give Username as “web logic” and Password as “web logic” and click Next.
12
Web Logic Clustering
Configuring windows Option: choose the default option and click Next.
13
Web Logic Clustering
Build start Menu entries: choose default options and click Next.
14
Web Logic Clustering
Configure Server Start Mode & JAVA SDK :choose default option and click next .
15
Web Logic Clustering
Create Web Logic Configuration: Give the name of the domain you want to create in configuration name and click Create. Note: The domain name for managed server and admin Server should be the same .
16
Web Logic Clustering
Click Done
Following the above procedure ,configure managedserver2 with the same domain name on another machine .
2.2 Configure The Admin Server:
Run the Configuration Wizard Again to configure the Admin Server.Choose “Create a new web logic Configuration “ and Click Next.
17
Web Logic Clustering
Choose “Basic Web Logic Server Domain “ Click Next .
18
Web Logic Clustering
Choose Custom and Click Next.
19
Web Logic Clustering
Give the Values for all the Attributes
Name of the Admin Server Say adminserver.Listen address:IP address of the machineListen Port : Say 7001Click Next .
20
Web Logic Clustering
Managed Servers, Clusters and Machine Configuration: Choose YES and Click Next.
21
Web Logic Clustering
Configure Managed Servers:
Click AddEnter the name of the managed server as entered below.Enter the IP Address of the machine where above managed server is configured.Enter the Listen PortClick Add for adding another Machine ie managedserver2.Then Repeat above steps.Click Next.
22
Web Logic Clustering
Configure Clusters:Click AddEnter the name of the Cluster Eg : Cluster1Enter the Multicast Port .Its value must be with in the Range of 224.0.0.0 to 239.255.255.255Click Add if another Cluster is required.Click Next
23
Web Logic Clustering
Assign servers to Cluster:Select the Cluster in the Right Window Pane.Select all the managed under this cluster in the left window.Click Arrow pointing to right hand side.Similarly repeat the process for all the Clusters.Click Next.
24
Web Logic Clustering
25
Web Logic Clustering
Configure Machines:Click Add.Enter the name of the machine and their IP Address participating in the cluster.Click Next.
26
Web Logic Clustering
Assign Server Name to Machine :Assign the Server names to the machines following the same procedure as done for Assigning Servers to clusters.
27
Web Logic Clustering
Database JDBC Options :Choose NO and Click Next.
28
Web Logic Clustering
Messaging JMS Options :Choose NO and Click Next.
29
Web Logic Clustering
Configure Username and Password: Give Username as “Web Logic” and Pass Word as you desired. And Click Next.
30
Web Logic Clustering
Configuration Windows Options :Choose Default Value and Click Next.
31
Web Logic Clustering
Build start Menu entries : Choose the Default options and Click Next.
32
Web Logic Clustering
Configure Server Start Mode & JAVA SDK: Choose default Option and Click Next.
33
Web Logic Clustering
Create Web Logic Configuration: Give the name of the domain you want to create in configuration name and click Create. The domain name for managed servers and Admin server should be the same.
34
Web Logic Clustering
Click Done.
3. Starting the Admin and managed servers:
Deployed sample application on the Admin Server and the managed servers.
Start the Admin server on Machine 1 by executing command “StartWeblogic.cmd”.
Start the Managed Server 1 on Machine 2 by executing command “startManagedWebLogic managedserver1 http://adminhost:7001” from the command line where “adminhost” is name of the Admin Server machine.
Start the Managed Server 2 on Machine 3 by executing command “startManagedWebLogic managedserver2 http://adminhost:7001” from the command line where “adminhost” is name of the Admin Server machine.
The resources deployed on the managed server should be accessed successfully for e.g. http://machine2:7003/beabasic/index.jsp and http://machine3:7005/beabasic/index.jsp
35