Load balancing and cluster

Question

Please help on this,
Steps I have created
1. Install Portal on node A
2. Create j2ee cluster instance on node B pointing to node A
3. Software load balance both the nodes
Even after load balancing the two portal nodes,if I shutdown Portal node A dispatcher,then the portal node B dispatcher will automatically shutdown, since the portal node B is a j2ee cluster for Portal node A.In this case how the URL will work from node B ? Please explain

Answer 1

I did portal install on server A. I  started dispatcher and I am logging with the URL http://ServerA:52100/irj on server A. And I did install of J2EE cluster on another server called ServerB. I started Server B's dispatcher. When I am starting Server B's dispatcher in Server A I am able to see another time Element joined.The URL for the serverB is http://ServerB:52100/irj. When I created users on Server A, I am able to see the users on Server B.When server B goes down or if dispatcher of B stopped even then Server A is working because it is independent install. But when the Server A goes down which is the main server then the additional J2EE cluster node that is Server B is going down automatically because it is dependent on Server A. But I want to make it as complete high availability of failover,means if Server A goes down it should fail over to Server B and if Server B goes down it should fail over to Server A. I understood we can do software load balancing from windows level or hardware load balancing to get the high availability. But now with my existing installs, I want to make failover to work, please suggest me which is the best way to do without changing any of the existing installs.
My environment is :
Operating system: Windows 2003 Enterprise Edition
Data base: SQL 2000(Already configured as cluster)
Portal: EP6.0 SP2