Configuring load balancing support for SAP connector
To enable load balancing for the SAP connector, configure several properties for JAVA_OPT_FLAGS and /etc/services file as shown in the following table. The /etc/services file is used to map port numbers to service names, depending on whether you are using the SAP connector through the secure connector or in the appliance or docker.
Procedure
- If you are using the SAP connector through the secure connector, complete the follow steps:
- Edit the secure connector start scripts and add the following properties related to load balancing for the flag JAVA_OPT_FLAGS:
-DsapMessageServerHostname=VALUE -DsapLogonGroup=VALUE -DsapR3Name=VALUE
For example:
set JAVA_OPT_FLAGS= -DsapMessageServerHostname=VALUE -DsapLogonGroup=VALUE -DsapR3Name=VALUE -Xrs -Xmx768m -Xms512m -XX:+UseParallelGC
- Edit the etc/services file as shown in Table 1, the location of this file depends on your host system (Linux, Windows). In Linux, the file is at /etc/services. In Windows, the file is at c:\WINDOWS\system32\drivers\etc\services.
- Restart the secure connector, and then test loadbalancing
- If the preceding steps did not work, add the following extra property (to set the ashost and system number for schema generation and the 3 prop for only runtime):
-DsapASHostForSchemas=true
- Edit the secure connector start scripts and add the following properties related to load balancing for the flag JAVA_OPT_FLAGS:
- If you are using the SAP connector in an appliance or docker, complete the following steps:
Note: Contact IBM support to make these changes in the appliance.
- Have the below properties added in maestro.sh for this flag JAVA_OPT_FLAGS:
-DsapMessageServerHostname=VALUE -DsapLogonGroup=VALUE -DsapR3Name=VALUE
For example:
set JAVA_OPT_FLAGS= -DsapMessageServerHostname=VALUE -DsapLogonGroup=VALUE -DsapR3Name=VALUE -Xrs -Xmx768m -Xms512m -XX:+UseParallelGC
- Edit the /etc/services file as shown in Table 1.
- Restart App Connect, and then test loadbalancing
- If the preceding steps did not work, add the following extra property (to set the ashost and system number for schema generation and the 3 prop for only runtime):
-DsapASHostForSchemas=true
- Have the below properties added in maestro.sh for this flag JAVA_OPT_FLAGS:
Service Type | Port | Service Name |
---|---|---|
sapmsS01 | 3600/tcp | SAP Message Server Port |
sapdp00 | 3200/tcp | SAP System Dispatcher Port Note: The last two
digits of the service type and port, "00", indicate the SAP system
ID. If the SAP system ID is not "00", use the SAP system number.
|
sapdp00s | 4700/tcp | SAP System Dispatcher Security Port Note: The
last two digits of the service type and port, "00", indicate the SAP
system ID. If the SAP system ID is not "00", use the SAP system number.
|
sapgw00 | 3300/tcp | SAP System Gateway Server Port Note: The last
two digits of the service type and port, "00", indicate the SAP system
ID. If the SAP system ID is not "00", use the SAP system number.
|
sapgw00s | 4800/tcp | SAP System Gateway Security Port |
For the sapmsXXX service type, XXX is the SAP System ID. For example, if the SAP System ID is E01, the entry should read as follows:
sapmsE01 35YY/tcp #SAP System Message Port
YY is the SAP System Number.