• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • paul wheaton
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Henry Wong
Saloon Keepers:
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Tim Moores
  • Mikalai Zaikin
Bartenders:
  • Frits Walraven

Weblogic Cluster Installation in 2 hardwares

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi everyone,

I need to setup weblogic cluster in 2 hardware.
I have tried to find existing discussion on this and the closest one is

Weblogic Cluster - Config

However, that thread's conclusion is not very clear to me -- no final conclusion..

Could someone please help explaining to me in clear steps/sequence?
I'm trying to explain this as clearest as possible..

In Hardware #1:
1. setup weblogic
2. create domain mydomain
3. create machine M1
4. create managed server MS1, e.g. will listen to 192.168.0.150:7005

in Hardware #2
5. setup weblogic
6. create domain mydomain
7. create machine M2
8. create managed server MS2, e.g. will listen to 192.168.0.160:7006

back to hardware #1:
9. open admin console for mydomain
10. create cluster ("mycluster"), with address 192.168.0.150:7005,192.168.0.160:7006
11. Question: Should I also creating MS2 again here -- in hardware #2 -- remember that I've created MS2 in hardware #2 in step 7?

back to hardware #2:
12. Question: Should I also duplicate creating cluster here -- in hardware #2 -- remember that I've created mycluster in hardware #1 in step 10.

13. in hardware #1, I start the MS1:
startmanagedserver MS1 http://192.168.0.150:7001

14. Question: Where should I start MS2?
In hardware #1 or in hardware #2?
And where should I point out the Administration URL?
Is it to the Administration URL of MS1 or MS2?

Could you please advise on my question above (and also correcting any
missing/wrong steps), please.. ?
Sorry if some of the questions above are too basic.
I'll appreciate your help and advise very much in advance!!!

Cheers,
Dion
 
Ranch Hand
Posts: 977
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Some points:

You must start Adminserver only in one machine, let's say machine 1(M1)

So your steps will be:

In Hardware #1:
1. setup weblogic
2. create domain mydomain (var/weblogic/domains/mydomain)
3. start adminserver for this domain (startWeblogic.sh under mydomain directory)
4. log on on Adminconsole as domain administrator
5. create machine M1
6. create managed server MS1, e.g. will listen to 192.168.0.150:7005
7. Add server MS1 to machine M1
8. create machine M2(this will be in a different hardware)
9. Create managed server MS2
10. Add MS2 to machine M2
11. Create cluster
12. Add MS1 & MS2 to cluster


All this is done using admin console from domain created in machine M1.

Then go to machine M2

in Hardware #2
5. setup weblogic
6. create domain mydomain in same directory structure(var/weblogic/domains/mydomain)
7. DO NOT start admin server in this hardware, all config is done using admin server from hardware 1.



Than.. with admin server already running only on M1

1. go to M1 and navigate to $DOMAIN_DIR/bin(var/weblogic/domains/mydomain/bin) and use startManagedWeblogic.sh to start server M1
2. go to M2 and navigate to $DOMAIN_DIR/bin and use startManagedWeblogic.sh to start server M2

It's done..
Also consider editing startManagedWeblogic.sh to add the admin server url

Also you'll need a proxy to load balance to your cluster so you can test it, you can use hardware, some httpserver like Apache, sun, IIS or even an weblogic server instance to do this job for you.

Later you should also consider using node manager in both machines to provide further control over your domain.

regards.
 
Dionisius Purba
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Marcos,

I'd like to thank you very very much for such a clear and easy to follow instruction!!!
I've just posted a new thread about my issue on to auto-start managed server , and I'm surely will be thankful if you can share your expertise again if you have time for it.

Thanks so much again Marcos.

Cheers,
Dion
 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am trying to create a cluster with following details

1 managed server + admin server on one machine.
1 managed server on another machine.

First of all I created one domain(Cluster_domain) on First Physical m/c, then with the help of admin server console.

1)Created first m/c M1, then added one managed server MS1 to M1.
2)Created second m/c M2, then added one managed server MS2 to M2.
MS1 is pointing to port 7003 on first physical m/c while MS2 is pointing to port 7005 on second physical m/c

3)Created one Cluster(My_Cluster) and added MS1 and MS2 to that the cluster.

Then I went to second physical m/c created the same domain(Cluster_domain) in the same directory structure.

Then I went to first physical m/c and started the managed server MS1 with the help of managedWebLogic.sh command in bin directory.


Till here it is working fine.

Then I went to second physical m/c and started the managed server MS2 with the help of managedWebLogic.sh command in bin directory.

here I am getting following error....


Feb 4, 2010 1:24:31 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.management.ManagementException: [Management:141223]The server name MS2 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:39)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:459)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:164)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:711)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:482)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:440)
at weblogic.Server.main(Server.java:67)

>
<Feb 4, 2010 1:24:31 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Feb 4, 2010 1:24:31 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Feb 4, 2010 1:24:31 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>


Thanks in advance for your help.
 
Mitesh Lashkari
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have successfully started the second managed server MS2 on second physical machine.

Note: instead of using ./startManagedWebLogic.sh MS2
we shoud use ./startManagedWeblogic.sh MS2 IP of Adminserver:portno on which admin server is running

But now I need to add Node manager.....
Could you please enlighten on this?

Thanks
 
There will be plenty of time to discuss your objections when and if you return. The cargo is this tiny ad:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
reply
    Bookmark Topic Watch Topic
  • New Topic