CODEWITHSUNDEEP
websphereload-balancingwebsphere-9
flipcode
flipcode

Reputation: 661

WebSphere topology.. 2 Nodes, each with their own Cluster and hardware load balancer in front

I have a java application that needs sticky sessions. We have a load balancer sitting in front of 2x WebSphere ND Application Servers Nodes (separate hosts). These are within a single Cluster.

I'm trying to work out, if I have an external load balancer and I must have sticky sessions enabled.. what's the benefit of a single Cluster? This server-to-server connectivity requires quite a bit of firewall activity.

Couldn't we just have..

Load Balancer
   Cell01
      DMgrNode
      Node01
         Cluster01
            ClusterMember01
      Node02
         Cluster02
            ClusterMember02

The load balancer just distributes with sticky sessions, load between Node01 and Node02?

Upvotes: 0

Views: 111

Answers (1)

Kenny
Kenny

Reputation: 316

A cluster must have more than one member. You have two separate clusters with a single member each. You need ONE cluster, with a server on each note. A cluster can cross nodes. The way you have this set up will NOT handle sessions. Clustering provides workload balancing and failover. With only one member of a cluster, you get neither. Here is what you need to do:

  • Delete Cluster02 on Node02.
  • Add a new clustermate for Cluster01 on Node02.

Upvotes: 1

Related Questions