wood burning stoves 2.0*
The moose likes Websphere and the fly likes  load balancing for Application client of IBM WAS Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark " load balancing for Application client of IBM WAS" Watch " load balancing for Application client of IBM WAS" New topic
Author

load balancing for Application client of IBM WAS

Hemant Bhasin
Greenhorn

Joined: Nov 20, 2003
Posts: 6
I have a cluster configuration of IBM WAS 5 (N/w deployent) spread across different host machine. The enterpise application installated on the WAS cluster has only EJB components, there are no web components.
These EJBs are to be accessed by application clients only.
As i understand, application clients can be run from any external machine using lanchclient executable of WAS.
How to setup load balancing for these access from the application client,
so that the load is evenly distributed to all machines in the WAS cluster.
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
You don't have to set up anything. It happens automatically through the client ORBs. When you bind to a stateless session bean in the cluster WebSphere automatically trasmits back to the client the addresses of all the rest of the servers in that cluster and the ORB will load-balance its requests across the cluster members.
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Hemant Bhasin
Greenhorn

Joined: Nov 20, 2003
Posts: 6
Thanks for the direction.
In a 2 server WAS cluster (with each WAS server on a separate physical machine, say ip1 & ip2). The deployment manager is on separate machine (ip3).
As i understand, the application client has to do a JNDI lookup using ip3:2809 and it will get all the cluster information.
Subsequently do the requests directly go to ip1 or ip2 or they still have to go via ip3.
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
After the first "bootstrapping" call, ip3 will no longer be used.
Kyle
Hemant Bhasin
Greenhorn

Joined: Nov 20, 2003
Posts: 6
so in essence, after the jndi lookup has been done.
even if ip3 goes down it would have no effect on the system.
So i should rather do all the JNDI lookup at the very start
so that IP3 redundancy is not required.
For balancing the load on ip1 and ip2, edge components is the s/w part.
However all WAS documentation detail ,its use for load balancing the web requests only.
In my case, the ear deployed in WAS has only EJBs.
How to distribute the load coming from application clients on these 2 (or more ) servers.
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Originally posted by Hemant Bhasin:
so in essence, after the jndi lookup has been done.
even if ip3 goes down it would have no effect on the system.

Yes, that is right.

So i should rather do all the JNDI lookup at the very start
so that IP3 redundancy is not required.
.

Yes, again.


For balancing the load on ip1 and ip2, edge components is the s/w part.
However all WAS documentation detail ,its use for load balancing the web requests only.
In my case, the ear deployed in WAS has only EJBs.
How to distribute the load coming from application clients on these 2 (or more ) servers.

I've said this before. You don't need to do anything else. The load will be automatically distributed across the application servers by the client ORB. You don't need the edge components for this.
[QB]
Kyle
[ March 17, 2004: Message edited by: Kyle Brown ]
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: load balancing for Application client of IBM WAS