RishiBang
asked on
WAS 61 - Adding servers to Cluster
Hi,
I am using WAS 6.1 with Fixpack level 33.
I have a cluster with two members. Now I want add a server which is federated earlier and not been part of any cluster.
So, my reqmt is to add the third server to the existing cluster.
But I am unable to do this from GUI console as the UI from the cluster members page's "Add" option is only for adding servers to the cluster by creating them instead of adding an existing server.
Thanks,
Rishi
I am using WAS 6.1 with Fixpack level 33.
I have a cluster with two members. Now I want add a server which is federated earlier and not been part of any cluster.
So, my reqmt is to add the third server to the existing cluster.
But I am unable to do this from GUI console as the UI from the cluster members page's "Add" option is only for adding servers to the cluster by creating them instead of adding an existing server.
Thanks,
Rishi
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ok, but how many nodes have you got at the moment (I Mean, websphere nodes). goto system administration -> nodes
> It has created two servers but placed only one server (Server4) into to the cluster and left the Server3 outside
Interesting.
Since Server4 should be "just like" Server3, which is a cluster member, I bet that the deployment of applications to Server4 would fail because WebSphere won't allow the same application to be deployed to both a cluster and to a non-cluster because the routing logic would not be able to distinguish between these ambiguous application instances.
I think that your best bet might be to just remove Server4, and create a new cluster member named Server4. The fact that it is a cluster member would mean that all of the resources (e.g., applications) that currently exist on any/all of the existing cluster members will be replicated / copied to new cluster members.
Does that make sense?
Interesting.
Since Server4 should be "just like" Server3, which is a cluster member, I bet that the deployment of applications to Server4 would fail because WebSphere won't allow the same application to be deployed to both a cluster and to a non-cluster because the routing logic would not be able to distinguish between these ambiguous application instances.
I think that your best bet might be to just remove Server4, and create a new cluster member named Server4. The fact that it is a cluster member would mean that all of the resources (e.g., applications) that currently exist on any/all of the existing cluster members will be replicated / copied to new cluster members.
Does that make sense?
ASKER
Hi baranello,
The Ariba application's cluster I have mentioned is with two servers on a single WAS node.
Nodes are not much interest here. The install wizard asks the node name and rightly creating the configuration.
Honogod, as yo mentioned the application deployment is not manual here and after creating the cluster, the wizard deploys the application automatically.
Since in this case it has already deployed for the app first time when creating the cluster for first time, it is not redeploying it again.
The only concern is with modifying the cluster to add two new servers.
Pls let me know if we can modify the cluster using wsadmin script to add the left out server (server3) to an existing cluster.
Thanks,
Rishi
The Ariba application's cluster I have mentioned is with two servers on a single WAS node.
Nodes are not much interest here. The install wizard asks the node name and rightly creating the configuration.
Honogod, as yo mentioned the application deployment is not manual here and after creating the cluster, the wizard deploys the application automatically.
Since in this case it has already deployed for the app first time when creating the cluster for first time, it is not redeploying it again.
The only concern is with modifying the cluster to add two new servers.
Pls let me know if we can modify the cluster using wsadmin script to add the left out server (server3) to an existing cluster.
Thanks,
Rishi
Using a wsadmin script, you can create new cluster members quite easily.
For example, this article "Scripting from scratch: Creating a Jython administrative script for IBM WebSphere Application Server" describes, in great detail, how to create a script to create new cluster members.
http://goo.gl/P5Fz
For example, this article "Scripting from scratch: Creating a Jython administrative script for IBM WebSphere Application Server" describes, in great detail, how to create a script to create new cluster members.
http://goo.gl/P5Fz
ASKER
Hi HonorGod,
I have raised a problem ticket with Ariba Support and waiting for their response.
I will let you know if any changes I will do on WAS side to rectify this.
Thanks,
Rishi
I have raised a problem ticket with Ariba Support and waiting for their response.
I will let you know if any changes I will do on WAS side to rectify this.
Thanks,
Rishi
Sounds good. Thanks for the status update.
ASKER
Thanks to HonorGod & Barnello for their inputs.
Thanks for the grade & points.
Good luck & have a great day.
Good luck & have a great day.
ASKER
Thanks for the info provided.
Let me explain my real requirement.
Our client is using Ariba Application for procurement. It is a J2EE app than can be run on WebSphere or Weblogic
Ariba application has an installation wizard which will create a cluster in WAS using wsadmin scripts.
I have installed WAS and then ran the Ariba installation wizard
The wizard allows us to create only two members in a cluster at a time.
Later client asked me to add additional cluster members to the same cluster.
I have reran the wizard and given new names for members (Say server3 & sever 4)
It has created two servers but placed only one server (Server4) into to the cluster and left the Server3 outside.
I thought it may be a bug with the product's installer and I can manage that from cluster configuration from WAS console by just moving the server left out into the cluster.
But I didn't anticipated that its complex in WAS too.
Thanks,
Rishi