3.5 Connecting Web Server to SAP Server

Liquid UI Web Server requires information about the server’s location to establish a connection with a SAP ERP system. Connection strings specify the target SAP ERP system for the RFC user. These strings can directly point to a SAP ERP system or a back-end system through a message server when load-balancing is employed. Connection strings are defined within the config.js file and entered into the SAP Router field when creating an SAP connection. Various formats can be used for connection strings, as outlined below:

 

Note: In all connection strings listed below, the [serverName] value can be an IP address or a system name.

/H/[serverName]

This connection string is used when there is a single server to connect to. The value that replaces the [serverName] can be either a Liquid UI Server or a SAP application Server. If our server is named 'Coffee', the string would appear as follows.

/H/Coffee

/H/[serverName]/G/[groupName]

This format is used when you are connecting to a single server, with multiple user groups. For example, if we are using the 'Roast' group on the 'Coffee' server, the connection string is shown below.

/H/Coffee/G/ROAST

[serverName]:[portNumber]

This format is used when you are connecting to a single server with a specific port. For example, if port 3600 is used on the 'Coffee' server, the connection string is shown below.

Coffee:3600

/H/[serverName]/S/[messageServerName]

This format is used when connecting to a single server through a message server. The connection string is shown below.

/H/Coffee/G/ROAST

/H/[serverName]/S/[messageServerName]/G/[groupName]

This format is used when connecting to a specific server with multiple user groups through a message server. For example, if using 'Decaf' to connect to the 'Coffee' server in the 'Roast' group, the connection string is shown below.

/H/Coffee/S/Decaf/G/Roast

Connection strings can be used to establish a direct connection to a specific SAP ERP system or to point to a back-end system through a message server. Refer to the Load Balancing section within this document for more details on load balancing. 

If you are using the rfcconnect command, you can use this command to directly enter a connection string. A typical rfcconnect string will look as shown in the following example:

rfcconnect = "SYSNR=00 IFDATABASE=TRX LANG=E CLIENT=800 ASHOST=juneau  SYSNR=00 LCHECK=0 USE_SAPGUI=0 USER=ayam PASSWD=x05y9a787q/rmAYe7CqiUmcsXVyK3N427ummcQ04LPs=" ;

 

Note: In this example, we are using an encrypted RFC password. If you are not using an encrypted password, it will be in plain text.

In addition to a single rfcconnect entry, it is also possible to enter an array that contains multiple rfcconnect strings. Such an array would look as in the following example:

rfcconnect = [ "IFDATABASE=GD4 CLIENT=600 ASHOST=HMLUSDA4.SAMPLE.NET SYSNR=00",
"IFDATABASE=GD2 CLIENT=600 ASHOST=SAMPLE4.SAMPLE.NET SYSNR=02",
"IFDATABASE=GT4 CLIENT=600 ASHOST=SAMPLE6.SAMPLE.NET SYSNR=04",
"IFDATABASE=TRX CLIENT=800 ASHOST=SAMPLE1 SYSNR=00",
"IFDATABASE=GT7 CLIENT=600 ASHOST=SAMPLE6.SAMPLE.NET SYSNR=02"];