Overview
If SAPLogon is installed on the Syniti Replicate server, it usually creates all required entries for the SAP backend systems in your local network. However, if SAPLogon is not installed (or you need to connect to an SAP backend system, for which SAPLogon does not have the necessary information), you must create the required entries manually.
To manually create an entry:
Access C:\Windows\System32\drivers\etc\ and locate the services file.
Open the services file in a text editor as an Administrator. for example, Write/Wordpad, Notepad++, or Visual Studio Code.
Note
Starting the editor as an Administrator lets Windows save your changes.
Add an entry to the services file, for example,
sapmsABC 3600/tcp.Save the services file.
The entries differ based on the server type that you use to connect to an SAP backend system. Entries format for each specific server type is described below.
Application Server Logon
When logging on to an SAP backend system via direct Application Server logon, you usually provide these two logon parameters:
ASHOST=application-server hostname
SYSNR=XY, backend’s system number
Syniti Replicate captures this data and automatically uses the 33XY port for connecting to the SAP application’s backend system. This port is the default port for RFC communication.
In most cases, no manual intervention is required. However, when the default gateway port of that system has been changed for some reason, you need to add the required entry to the services file as described above, and then replace the logon parameter SYSNR=XY with GWSERV=sapgwXY. In that case, the entry looks like, sapgwXY 33XY/tcp . Syniti Replicate then automatically gets the correct port from the operating system.
Message Server Logon
In this case, Syniti Replicate performs an additional step before logging on to an application server. It connects to the message server and requests for the hostname/IP-address of an application server that belongs to the given logon group. For this case, you usually pass the following parameters:
MSHOST=message server hostname
SYSID=ABC
GROUP=PUBLIC
When connecting to the message server, Syniti Replicate tries to get the port number corresponding to the sapmsABC service from the operating system. So, an entry (for example, sapmsABC 3600/tcp) needs to be added in the services file described above.
Note
The SAP BASIS team should confirm the port number that that message server is running on.
Registered Server
For registering an RFC server at a gateway, you usually provide parameters like:
GWHOST=gateway hostname
GWSERV=sapgwXY
PROGRAM_ID=program ID
Similar to the Application Server Logon case, Syniti Replicate opens a connection on the port corresponding to the sapgwXY service to the gateway. So, an entry (for example, sapgwXY 33XY/tcp ) needs to exist in the services file. XY is again the backend’s system number.
High Availability Registered Server/Group registration
For registering an RFC server at a group of gateways of a system, you provide parameters like
MSHOST=message server hostname
SYSID=ABC
GROUP=PUBLIC (optional, if not specified all gateways in the system are used)
Similar to the Message Server Logon case, Syniti Replicate then tries to obtain the port number corresponding to the sapmsABC service from the operating system. So, an entry (for example, sapmsABC 3600/tcp) needs to be added in the services file.