SAP Gateway 

The SAP Gateway forms the bridge between an SAP System and an external system, thus enabling data to be exchanged between the systems. All Remote Function Calls (RFCs) have to be carried out via an SAP Gateway (with CPI-C log).

When using R/3 Travel Planning with connection to the reservation system Amadeus Global Travel Distribution at least one SAP Gateway must be involved in the configuration, as an external application on an NT server (the Amadeus Gateway) is integrated in the system infrastructure.

This can also be a local SAP Gateway. For stability and security reasons we recommend that you set up a local SAP Gateway: If a problem should occur with the SAP Gateway when using a local SAP Gateway, you only need to restart this local SAP Gateway; the Amadeus Gateway and API server are not affected by the problem.

If you do not want to use a local SAP Gateway, set up the SAP Gateway on the application server on which the R/3 Travel Planning is installed.

 

For general information on setting up an SAP Gateway, see the SAP Library under Basis Components ® Basis Services / Communication Interfaces ® SAP Communication: Configuration ® SAP Gateway.