Pages

Ads 468x60px

Sunday 14 October 2012

Cluster Configuration and Deploy Applications


Clusters & Configuration

With Network Deployment, you can use application server clustering to enhance
workload distribution. A cluster is a logical collection of application server processes that provides workload balancing and high availability.

Application servers in a cluster are members of that cluster and must all have
identical application components on them. Other than the applications on them, cluster members do not have to share any other configuration data.

For example, one cluster member might run on a large multi-processor server
while another member of that same cluster might run on a small mobile computer. The server configuration settings for each of these two cluster

members is very different, except the application components that are assigned
to them. In that area of configuration, they are identical. The members of a cluster can be located on a single node (vertical cluster), across multiple nodes (horizontal cluster), or on a combination of the two.

When you install, update, or delete an application, the updates are automatically
distributed to all members in the cluster. In WebSphere Application Server V5, if
you updated an application on a cluster, you had to stop the application on every
Server in the cluster, install the update, and then restart the server. With
WebSphere Application Server V6, the Rollout Update option allows you to
update and restart the application servers on each node, one node at a time.
This provides continuous availability of the application.

CREATION OF CLUSTERS:

            Open the admin console of deployment manager

In left hand side console
à Select the server
            -     Application Servers
            -     WebServers
            -     Generic Servers
-     JMS Servers
-          Clusters
-          Cluster Topology

à Click on: Clusters
n  Click on: New
n  Enter the cluster name: Sumanth (name of the cluster)

à Existing Server
0 : Do not include an existing server in this cluster (in this we can create new servers)
                                                0: Select an existing server to add to this cluster ( in this we can select the servers already which are created)
Note: if you want create the new server the click on : Do not include an existing server in this cluster
n  Click on next
Member name  : server1 (name of the server)
            Click on : apply

If you want to create one more server:  enter the member name again
n  Click on next

è If you want to use the existing server click on : Select an existing server to add to this cluster 
n  Browse for the path the server

D:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\mirdev81Cell01\nodes\mirdev81CellManager01\servers

n  Click on : next

è Summary (it will show all the select components to create the cluster)
è Click on : FINISH
è Click on : SAVE

è Expand + total changes document: 30 (in total it tells about the servers)
è Synchronize changes with Nodes

TO SEE THE PORT NUMBERS:

è Click on selected server
      ex: server2
      à Click on Ports
      à Wc adminhost : in this we can see the port number

TO START THE CLUSTER:

à Select the server
            -     Application Servers
            -     WebServers
            -     Generic Servers
-     JMS Servers
-          Clusters
-     Cluster Topology

è Click on : Clusters
     
      select                     name                status
sumanth                 

è Click on: Start (it will start the cluster and shows in status)
NOTE: if the cluster not started, then start the each server in the cluster)

TO DEPLOY AN APPLICATION ON CLUSTER:

            Open the admin console of deployment manager

In left hand side console
à Select the server
            -     Application Servers
            -     WebServers
            -     Generic Servers
-     JMS Servers
-          Clusters
-          Cluster Topology

è Select the Application server
            à Click on : install new application

è Path of the new application
n  Local file system
n  Remote file system

à click on Local file system : EJB.War   ( Browse for the location the file)

NOTE: select the War File or Ear File
      WAR FILE: Web Arch File
      EAR File : Enterprise Arch

èContext Root : naidu (name of the context root, by this name we will open the browser later)
à Click on : next

è Application security warning
                  à Click on : continue

è Select installed options
                  à Click on : next

è Map modules to server

Select        Modules          URL                Server
                  EJB Client       Client.waR,     WebSphereCell=
WEB-INF/      mirdev30cell01,
WEB.XML     node=mirdev30node01, server=server1

è Cluster and Server: webspherecell=miredv30cell01, cluster=sumanth
NOTE: the above clusters and servers shows,  the clusters and server which are already created and select the required cluster to deploy the application.

è Select the cluster sumanth
                              à Click on : Apply
                              à Click on : next
                              à Click on : next
                  à Click on : Finish

è Save the master configuration            
                  à Click on : save

è select the war file and start

NOTE : after creation of cluster, Go to the browser

                  http://localhost:9081/sumanth

                  sumanth : cluster root name
                  9081 : port number (wc dafault host)

TO SEE THE PORT NUMBER:
                  à servers
n  Application server
Click on required server and click on ports
-- Wc dafault host

0 comments:

Post a Comment