The load balancer acts to distribute traffic and monitor incoming connections in the enterprises technical landscape. Users unbeknown to them may pass through several firewalls, proxies and loadbalancers upon entering an Enterprise's network. The settings of these loadbalancers can affect the perceived performance of the application for end users and even affect BAU.
In this of blog posting I'm going to go over a number of settings that can affect the performance of SAP Sourcing and even some other applications that users may be passed to after the loadbalancer.
1. The number of simultaneous connections allowed in the proxy configuration can have an affect on performance in Sourcing as a new one is opened each time a user connects.
MaxConnPerIP parameter limit from 64 to 128.
<IfDefine LIMIP>
<Location />
MaxConnPerIP 64 <-- Increase this to 128
</Location>
</IfDefine>
2. The Connection to the sourcing system will sometimes timeout as initially generating the session can take a number of seconds. The suggestion here is to update the Loadbalancer to ignore timestamps when calculating timeouts.
This is the command for a F5 load balancer.
parameter-map type connection TIMEOUTS
set tcp timeout half-closed 30
tcp-options selective-ack allow
tcp-options timestamp allow <-- this one must be removed.
3. For SSL Termination using a Apache as well as the “RequestHeader set X-Original-HTTPS on” parameter the “mod_headers” module must be enabled. In most cases it is already enabled if there are other “RequestHeader” directives in the configuration. If not, there should be a line in the configuration similar to the one below to enable the module.
LoadModule headers_module modules/mod_headers.so
