Weblogic Cluster ??

[DannyB]

Hi, anyone experienced in configuring WebLogic Cluster ??

 

[wushutwist]

What do you want to know about WebLogic Clustering?

 

[DannyB]

I'm trying to set it up, on a machine with a fixed ip, and with other ips granted to it (for the "virtual machine&quot.

I wish I had some kind of checklist to run through ....

I set up a domain (wl), with a server inside it. I seem to get them running, but not as a cluster.

Any help would really be appreciated.

 

[wushutwist]

At the bare minimum you will need an Administration Server and two Managed Servers. Your Administration could be the same instance as one of the Managed Servers but I would not recommend it.

- Create each of those and tie them to different IPs or DNS names. WebLogic Clustering uses IP Mulicast and needs each Server instance to have a unique address.
- Once you get each of these created then you will need to start the Admin Server and add the other 2 as part of the Cluster using the WebLogic Console or by directly editing the config.xml (BTW, I am talking about WL 6.x). At this point you will need to choose a Multicast Address. Make sure nothing else on your segment is using this address, especially not any other WebLogic Cluster.
- There are a bunch of optional steps after this such as setting up Replication Groups, skip these for now.
- You should be ready to start the Cluster. Start the Administration Server first, then start the other two Servers as Managed Servers. You will first need to edit the startManagedWebLogic.cmd and put in the appropriate address and password for the Admin Server (otherwise known as the Management Server). Once the changes are made then you should be able to start the managed servers properly.
- Bring up the Console for the Admin Server and select Cluster -> Monitoring -> Monitor Server Participation (or something similar).

This is from memory, I apologize if I left out any steps or I didn't fully explain things. Good Luck.

 

[wushutwist]

At the bare minimum you will need an Administration Server and two Managed Servers. Your Administration could be the same instance as one of the Managed Servers but I would not recommend it.

- Create each of those and tie them to different IPs or DNS names. WebLogic Clustering uses IP Mulicast and needs each Server instance to have a unique address.
- Once you get each of these created then you will need to start the Admin Server and add the other 2 as part of the Cluster using the WebLogic Console or by directly editing the config.xml (BTW, I am talking about WL 6.x). At this point you will need to choose a Multicast Address. Make sure nothing else on your segment is using this address, especially not any other WebLogic Cluster.
- There are a bunch of optional steps after this such as setting up Replication Groups, skip these for now.
- You should be ready to start the Cluster. Start the Administration Server first, then start the other two Servers as Managed Servers. You will first need to edit the startManagedWebLogic.cmd and put in the appropriate address and password for the Admin Server (otherwise known as the Management Server). Once the changes are made then you should be able to start the managed servers properly.
- Bring up the Console for the Admin Server and select Cluster -> Monitoring -> Monitor Server Participation (or something similar).

This is from memory, I apologize if I left out any steps or I didn't fully explain things. Good Luck.

 

[DannyB]

Ok, thanks a lot. We managed (apparently) to get the cluster going (I had forgotten to start up node manager).

I'll running through the checklist u gave me. Right now we have to get confortable with that.

Let me know if I (we) can help u with Java Enterprise.

Thanks once more.