This week's book giveaway is in the Reactive Progamming forum.
We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line!
See this thread for details.
Win a copy of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams this week in the Reactive Progamming forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
  • Knute Snortum
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar

Help Please !! deploying application to a cluster

Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everyone, I have some knowledge on weblogic administration. But I am not expert. So my questions may look very simple for you expertises.
In one of my previous client applications, there was a cluster of 2 weblogic servers server1 and server2. Server1 is admin server. Server2 is managed server. Weblogic version is 6.1.
All application components are deployed to server1 and all of them are targeted to server1 except components comp1, comp2 which are targeted to server2.
Then, inside the application, we are explicitly looking for server2 whenever we do JNDI lookup for comp1 and comp2. I mean for initial context, we are supplying the server name and then we are doing jndi lookup for comp1 and comp2.
I am in dilemma that do we require the cluster setup here. ? What I feel is if we have more than one server, then we definitely need a cluster setup in which one server we have to make admin and remaining servers as managed servers. And we will have to deploy all our application components to the admin server but target these components to server 2, server 3. If we wish we can also target the components to admin server. (I also know that if we target the components to admin server, the performance will be slowed down. But that is different issue).

But in this particular scenario, I am 100% sure that there is no load balancing and failover taken care which will be automatically provided by the cluster if and only if we target all the components to all the servers and pass cluster address for JNDI lookup.
In this case we are manually doing the load balancing by transferring the requests explicitly to server2 regarding comp1 and comp2.
I am requesting the expertise on clusters to tell me if my perception is wrong.
My another BIG question is : When we want to achieve complete load balancing and failover, do we need to deploy the application to each of the servers or do we need to deploy the application only to admin server but target the application to the entire cluster so that the application is available in all the servers ? I may be completely wrong . please clarify my confusion.

I would highly appreciate if you give me elaborated answers and big thanks for you all in advance.
Mo-om! You're embarassing me! Can you just read a tiny ad like a normal person?
Java file APIs (DOC, XLS, PDF, and many more)
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!