WebSphere Application Server - Re: WebSphere: Question Re: Clustering & Server Names

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > January 2005 > Re: WebSphere: Question Re: Clustering & Server Names





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: WebSphere: Question Re: Clustering & Server Names
Sven-Jürgen Lämke

2005-01-25, 5:53 pm

Hi,

see answers below:

"smethwickman" <smethwickman@yahoo.com> schrieb im Newsbeitrag
news:1106610540.761845.40660@f14g2000cwb.googlegroups.com...
> Good afternoon.
>
> We are in the process of creating a Clustered
> environment for the Epiphany application [version
> 6.5.2] using WebSphere, 5.0.2, and have hit upon
> a possible problem.
>
> During the Cluster "set up process" [i.e. adding
> a node] we see that both of the names for the two
> Application Servers that will form the cluster have
> been assigned, by default, using one Deployment
> Manager [note the default name is "server1"].

Before you can set up a cluster you have to add your 'local'
applicationservers from the two nodes using the addNode-command. By default
all existing applicationservers will be added under cell-control by the
network deployment manager (WAS ND). Each server has a "full qualified name"
which beside the servername (e.g. the default server 'server1') consists of
the hostname. You can see this in the WAS ND-Adminconsole.
>
> Is it possible to use the identical name of
> "server1" and still be successful in our
> clustering efforts? Or, must the server names
> be different and, if so, how/where should this
> be performed during the clustering process? In
> other words, should the server name change/
> assignment be performed before, or after,
> clustering and how?
>

When building the cluster by using the WAS ND-Adminconsole the
clustermembers - which in your case should based on the
server1-configuration - can get completely different names (e.g.
Epiphany_cluster with clustermembers Epi_cm1, Epi_cm2 etc.). To make us of
the clustered appservers, you deploy your application to the cluster
Epiphany_cluster. This automatically deploys the application on all
clustermembers (don't forget updating httpPlugin when having
webressources)). You can now start the cluster or each clustermember
seperately.
When accessing EJBs, you switch from the 'node-view' to the 'cluster-view'.
You can see the ports in the Endpoint-Definition for each clustermember.

Regards

Sven

> Finally, can SKS point me to the definitive
> guide to clustering using 5.0.2, be it an> IBM document, web-site,

off-the-shelf book,
> etc?

See WAS ND Admin guide.

>
> Many thanks,
> David
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com