Load balancing on the local host only (6.40 Java)

[Former Member]

Hello!

When configuring load balancing for Web AS 6.20 (Java), the property "LocalLoadBalancing" was available in the ServiceManager of the dispatcher. See Note 772561.

This property is not available in Web AS 6.40 (SP14).

How can I now ensure that a dispatcher does not connect to a server process on another physical server?

// Mikael

[Former Member · Accepted solution]

Hi Mikael,

In Web AS 6.40 this property is invalidated by the new <b>instance-based</b> cluster concept. In other words, when installing a Web AS 6.40 system you're installing instances (i.e. one central services instance, one java central instance, and 1-n dialog instances). A Web AS 6.40 instance contains one dispatcher and 1-n servers. The installation software (SAPinst) lets you install an instance on the same physical host only. Therefore, in 6.40 all servers that are behind the J2EE dispatcher are <b>always</b> on the same physical machine => the behavior of the LocalLoadBalancing property.

In 6.20, the installable unit is a dispatcher/server, and you can choose to distribute them to different physical hosts => the need to have the LocalLoadBalancing property to control remote/local LB.

Hope this explains things a bit.

P.S. In case you need more info about the cluster architecture of the Web AS Java 6.40, you can have a look <a href="http://help.sap.com/saphelp_nw04/helpdata/en/2e/611724f410254ca12a3f396ec5ae85/frameset.htm">here</a>.

[Former Member · Accepted solution]

Thank you.

I can now confirm that the cluster setup is correct, but the EP Monitoring workset isn't... But that is another problem!

For those finding this thread later on, here is the documentation: http://help.sap.com/saphelp_nw04/helpdata/en/c8/e86e04987f4cd0af29ae628422ab95/frameset.htm