Install RAM non-clustered, then change to clustered later?

As far as I know you can't easily change it. First you would need to
have a WAS Network Deploy profile. You probably have just a Basic server
profile.

You can still use the same databases, that's half the work. But you
would need to create a Network Deploy profile instead of a Basic profile
and then go through the Cluster setup of a brand new WAS Network deploy
profile. You can then point to the existing databases and it should pick
them up.

Rich

As far as I know you can't easily change it. First you would need to
have a WAS Network Deploy profile. You probably have just a Basic server
profile.

You can still use the same databases, that's half the work. But you
would need to create a Network Deploy profile instead of a Basic profile
and then go through the Cluster setup of a brand new WAS Network deploy
profile. You can then point to the existing databases and it should pick
them up.

Rich

Actually WAS ND will be installed on the first server and when the second server is delivered with WAS ND a cluster between the two will be created. Should we use the deploy Cluster Setup application in this case or do you advocate a re-install once the cluster is in place.

Hi,

You should reinstall using the deploy Cluster Server Setup. You can use
the same databases. That will take care of the worst of it.

From what I have heard is that the Server Setup has no capability of
changing an already installed RAM from a non-clustered to a clustered.

Rich

Hi,

You should reinstall using the deploy Cluster Server Setup. You can use
the same databases. That will take care of the worst of it.

From what I have heard is that the Server Setup has no capability of
changing an already installed RAM from a non-clustered to a clustered.

Rich

It should be possible to cluster vertically and use the cluster setup. Once the second server arrives we should be able extend the cluster horizontally.

I should point out that this is a non-production system that won't go live until it is properly clustered over 2 servers. I'm looking to get through the install and validate that RAM works correctly while I'm waiting for the other WAS node to become available.

Do you see a problem with this approach in non-production?

On 7/22/2010 11:23 AM, vfertig wrote:

richkulpwrote:
Hi,

You should reinstall using the deploy Cluster Server Setup. You can
use
the same databases. That will take care of the worst of it.

From what I have heard is that the Server Setup has no capability
of
changing an already installed RAM from a non-clustered to a
clustered.

Rich

It should be possible to cluster vertically and use the cluster setup.
Once the second server arrives we should be able extend the cluster
horizontally, unless you see a problem with that.

Once RAM is installed in a cluster you should be able to add another

server to the cluster. Server setup may then need to run to update
certain server specific settings.

I've never actually done it so I'm not sure. I'll ask around.

Rich

My recommendation is

a) create a cluster (even if it has only one application server from a single node, as you said vertical cluster)

b) Get done with install, by choosing that cluster for RAM
c) Note that you will still have to create another application server for RTC (that is not part of any clusters) otherwise install would not proceed.
d) later when you add a new node to the cell, you can edit the cluster and create new members in the cluster and create an application server under the new node.

To do that in WAS 7.0, open admin console

e)click Servers > Clusters > WebSphere application server clusters > cluster_name > Cluster members.

b)click New to create a new cluster member. choose the new node.

for more details

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_member.html

After adding the new cluster, you might have to make sure the webserver plugins are regenerated & propogated

Thanks. I'll go with that recommendation.

We successfully installed using the cluster setup on a vertically clustered (multiple servers on a single WAS node) configuration.