Create the On-Premise Source System in the Cloud Connector

You have to allow access to an on-premise system in the Cloud Connector.

Context

The Cloud Connector controls the access to on-premise systems.

When adding the system information, you enter internal and virtual system information:

  • The internal host and port specify the actual host and port under which the backend system can be reached within your corporate network. It must be an existing network address that can be resolved on your corporate network and has network visibility for the Cloud Connector. The Cloud Connector tries to forward the request to the network address specified by the internal host and port, so this address needs to be real.

  • You can virtualize the system information in case you like to hide your internal host names from the cloud. The virtual server name can be an arbitrary name which does not need to exist. We recommend to use a virtual (cloud-side) name that is different from the internal name.

Procedure

  1. Log on to the Cloud Connector Administration on https://<hostname>:8443.

    <hostname> refers to the machine on which the Cloud Connector is installed. If installed on your machine, you can simply enter localhost.

  2. In the left-side menu of the administration UI, select Cloud To On-Premise.
  3. In the Subaccount field, choose the subaccount of your SAP Datasphere tenant.
  4. On the Access Control tab, in the Mapping Virtual to Internal System section, click (Add) to add a new mapping for your source system.
  5. In the Add System Mapping dialog, use the following values:

    1. Choose ABAP system as Back-end Type.

    2. Select RFC as Protocol.

    3. We recommend to choose With load balancing (system ID and message server) as Connection Type.

    4. If connection type 'With load balancing (system ID and message server)' was set:

      Maintain the message server of the ABAP system as Message Server.

      Enter the system ID as System ID. The system ID is a three-char identifier that is also found in the SAP Logon configuration. Alternatively, it is possible to directly specify the message server port in the System ID field. If you are not sure about the message server port number, call transaction SMMS in the source system.

      If connection type Without load balancing (application server and instance number) was set:

      Maintain the hostname of the application server as Application Server.

      Enter the instance number of the source system as Instance Number. Alternatively, it is possible to directly specify the RFC port in the Instance Number field. If you are not sure about the RFC port number, call transaction SMGW in the source system, then display the gateway trace file. It should contain a line like this:

      Bind service sapgw00 (socket) to port 3300

    5. Optional: You can virtualize the system information in case you like to hide your internal host names from the cloud. The virtual information can be chosen arbitrarily and does not need to exist. The fields will be pre-populated with the values of the configuration provided in the step before.

      If connection type With load balancing (system ID and message server) was set:

      The Virtual Message Server and the Virtual System ID will later be used when maintaining the communication system in the SAP BW bridge tenant pointing to the on premise source system.

      If connection type Without load balancing (application server and instance number) was set:

      The Virtual Application Server and the Virtual Instance Number will later be used when maintaining the communication system in the SAP BW bridge tenant pointing to the on-premise source system.

    6. Optional: Enter a Description.

    7. Set Check Internal Host and choose Finish.

Results

As a result, you have defined the source system in Cloud Connector. It should be shown as Reachable in the column Check Result.