Service Layer Load Balancer not behaving as expected by industry standards.

[Pipalia1]

Any load balancer is logically expected to have a single end point. In SAP Business One v10 SQL (1000240), when we create Nodes, they load balance and remain on the same server. But when we create a load balancer on another machine, we end up with two different end points which a developer needs to connect to. This is not how a load balancer works ideally, a developer should have a single end point regardless of how the load is balanced.

--- Steps to Reproduce ---

• Install Service Layer for SAP B1 v10 in one server
• Install Service Layer Component for SAP B1 v10 on another server
• You will now have two different IP addresses and logins for the service layer
• A load balancer should automatically balance the load, without developers worrying about when to connect to which machine

[EunSeok_Bang]

Hello again,

The intended single end point is SL load balancer.

You need to install only load balancer members in the 2nd server.

the load balancer in the 1st server is the only load balancer in the landcape and serve as a single end point.

Regards

EunSeok

[Pipalia1]

That's what we were hoping for, but in the SLD, we are seeing two different end points and a service listed for both end points.

We saw an entry in the Control Center for the SLD for the following:

• VM1:50000; VM1:40000/ServiceLayerController (where the SLD is)
• VM2:50000; VM2:40000/ServiceLayerController (additional server where only Service Layer was installed as described in Admin guide of the documentation)

So it was unclear what the developers are meant to call when a second load balancing server is installed, because it's not clear from documentation that the server will automatically load balance and we are meant to ignore the second end point.

[Pipalia1]

Is there a document or tech note which explains this behavior sir? Thank you for your response.