Client guidelines for
deploying a third-party load balancer that is connected directly to SAP Mobile Server client ports.
The load balancer must:
- Balance connections at the TCP/IP level.
- Perform all load balancing on client connections to the
SAP Mobile Server cluster, independent of any other network
device.
- Connect directly to the client ports of each
SAP Mobile Server in the cluster.
- Support client request routing (that is, back-end server affinity)
for nonpersistent HTTP connections, based on
both the
X-SUP-SESSID HTTP cookie and the ml-session-id HTTP
header. See
Reference topic in Developer Guide: REST API Applications,
especially the HTTP Headers and Cookies subtopic.
Note: To allow header inspection, the load balancer must be a
transport-layer
security
(TLS)
endpoint on HTTPS connections from mobile clients.