Weblogic Cluster - Config

[edson santos]

Im new to weblogic. So please excuse my question if its very basic. Im trying to setup a weblogic cluster. I have two physical windows machines and i have installed weblogic on one of the machines and created a domain in that. I have created a server in that domain. Now i want to have another server on the second windows machine and make it part of this domain to make a cluster. So what should i do on the second machine after installing weblogic software on it. I would really appreciate any help regarding this.

Thank You

[Marcos Maia]

Hi,

Using the admin console or a wlst script:

create the cluster
create 2 machines
create the servers

add servers to cluster and each one for it's properly machine.

Then on the second machine after installing weblogic, create a domain using the same directory structure(not required but a good practice) as you did in the first machine, note that the admin server is problably running on you first machine as problably your first managed server.
After doing this, edit and run the script under $DOMAIN_HOME/bin called startManagedWeblogic, that's it.
Other option is use nodemanager and start the server using admin console.

regards.

[edson santos]

Ok Marcos you again... thanks.. a lot...

I�ll do that... actually I�ll try first with NODEMANAGER or I�ll do using SCRIPT.

Thanks.. a lot...

[edson santos]

Marco, actually the things aren�t so simple like that..

Well I just did what you told me to... but there are some errors like this :

<Aug 29, 2008 1:36:08 AM GMT-03:00> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address <second server 172.29.0.79> might be incorrect or another process is using port 8020: java.net.BindExceptio
: Cannot assign requested address: JVM_Bind.>

I got some doubts like :

When you say... after doing this : ok... about STARTMANAGEDSERVER should I start this from the FIRST MACHINE ? Another question, the second machine it must be something running, like, the AdminServer of the second machine, or else, the Manager must be running in manner that the FIRST server which is running the ADMINSERVER and the cluster has been built, can communicate to Second Server, I understood your comments, but I have some doubts about the basics.

I�m stuck here, I know that probably this is basic, but I�m unable to get this working.

Thanks again...

[Marcos Maia]

HI,

Well imagine the configuration:

2 hardwares and a weblogic domain with Admin Server + 2 managed servers. 1 managed server running same hardware as Admin server other in the second hardware, not using node manager.

What you have to do is:

Install weblogic on both hardwares.
Create a domain with same name and directory structure on both hardwares.
Run admin server in hardware 1.
Using admin console create:
1 Cluster
2 Machines

Add Admin Server and Managed server 1 to Machine 1.
Add Managed server 2 to machine 2.
Add both managed servers to cluster(not Admin server).

Make sure you activate your changes.

on hardware 1 edit startManagedWeblogic to place correct Admin url and then run the script to start managed server 1. It's a good thing if you create a boot.properties file for each server under $DOMAIN_HOME/servers/$SERVER_NAME/security as doing so you'll not be required to type password while starting the servers.

Than all you need to do to start managed server 1 is run the startManagedWeblogic script, if you have placed boot.properties and edited startManagedWeblogic correctly all you need to do is run your script with a command like:

    
startManagedWeblogic $MANAGED_SERVER_NAME

replace $MANAGED_SERVER_NAME with the name you gave for managed server 1 while configuring it using the admin console.

Then on the second machine, navigate to where you have created the domain and to the bin directory, edit the startManagedWeblogic script and run it.

If you're using a solaris environment or linux is a good practice send the standard out to nohup and start it in background like:

nohup ./startManagedWeblogic managedServer2 &

regards.

[edson santos]

Thanks Marco...
I�m using Windows,
I�ll follow your orientation, I forgot NodeManager anyway, doesn�t work...

Thanks...

[edson santos]

Ok Marcos, I�ve tried, what you told me to...

Didn�t work...

I�ve created ONE DOMAIN in hardware 1 and the same domain in hardware two.

I�ve started AdminServer on HARDWARE 1 and I�ve created TWO MANAGED SERVERS on it...

After that.. I�ve created two LOGICAL MACHINES on it...

But also, is important to say... I�ve created on HARDWARE 2 one managed server, you have to be aware that I�m not using NODEMANAGER in both nodes ok ?? I would like to start up the servers by the StartManagedWeblogic.cmd scripts.

I�ve added the AdminServer and the ManagedServer on machine 1 which one its Listen Address is like : HARDWARE 1 = localhost

and I�ve added on Logical Machine 2, which has been created on HARDWARE 1 the IP address of the HARDWARE 2 is that correct ??

Ok, I�ve started the AdminServer on machine one, I�ve created the CLUSTER with the CLUSTER ADDRESS containing HARDWARE1 ORT,HARDWARE2 ORT, (ports = ManagedServers ok ?) After that, I�ve started the AdminServer on HARDWARE 1 and by script have started ManagedServer1 on hardware 1 successfully.

Ok, now, I�ve logged on hardware 2 (remember windows S.O. machines) ok,I went ran into %DOMAIN_HOME%\bin and edited STARTMANAGEDWEBLOGIC.cmd and I`ve replaced set ADMIN_URL=http://localhost:8000 to set ADMIN_URL=http://hardware1:8000

Everything is fine, but when I try to start up the MANAGEDSERVER2 on HARDWARE2 (Basically I�m logged on it) I got this error :

<Sep 1, 2008 9:24:43 PM GMT-03:00> <Error> <com.bea.weblogic.kernel> <000000> <[Security:090735]The DBMS connection was
not usable>
<Sep 1, 2008 9:24:43 PM GMT-03:00> <Critical> <Security> <BEA-090403> <Authentication for user Administrator denied>
<Sep 1, 2008 9:24:43 PM GMT-03:00> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.s
ecurity.SecurityInitializationException: Authentication for user Administrator denied

Remember on the HARDWARE 2 on %DOMAIN_HOME%\servers\%SERVER_NAME%\Security is an empty directory.

Sorry boring you, but the OFICIAL BEA SUPPORT doesn�t work, and I don�t know how to get this UP AND RUNNING.

I�d appreciate your help.

Thanks...

[edson santos]

Hey MARCOS to let you know, I�ve made it...
But only with WEBLOGIC SERVER, I forgot to say, this is about WEBLOGIC INTEGRATION, BEA is working on it...

Thanks Marcos...