SAP transport


A SAP system provides access to processes and data in business application programs such as a SAP R/3 enterprise application program. The Transaction Server provides a SAP transport that can be used to connect to an existing SAP system.
Once the transport is defined and validated, you create a SAP transport map to interact with the SAP business application programming interface (BAPI) and its Remote Function Call communication interface (hereinafter referred to as the RFC interface).

Assumptions

The information in this section assumes the following:

  • You have knowledge of SAP programming and know how to implement the BAPI and RFC interface that is associated with SAP application programs.
  • There is an existing SAP enterprise application server running one of the following SAP software releases.
    • SAP R/3 4.6c
    • mySAP ERP 2004 ECC 5.0
    • mySAP ERP 2005 ECC 6.0
    • SAP WAS 6.20 and SAP WAS 6.40
  • For the Mitsubishi MESInterface IT product and the Enterprise Gateway for Siemens ERPC product, a SAP proxy server must be installed on a Windows computer that has access to the SAP enterprise application server. The SAP proxy server support is only required for those embedded products. It is important that the Transaction Server version is at the same level as the SAP Proxy.
    For more information, see Installing the SAP Proxy.

  • There is a license key for the SAP transport installed on the node.

    SAP on Enterprise Gateway for Linux

    32-bit Linux
    The SAP transport for the Enterprise Gateway for Linux product requires the compat-libstdc++-296-2.96-144.el6.i686 (or equivalent) compatibility libraries to be installed on the Linux system. If this is not done the SAP transport type will not appear in the transport type pick list. Ask your Linux system administrator to install the compatibility libraries. You will need to restart the runtime after this has been done.
    The following shows the command that can be used to install the compatibility libraries on a Centos 6 Linux distribution.
    yum install compat-libstdc++-296

    64-bit Linux
    The SAP Transport for the Enterprise Gateway for 64-bit Linux product requires the compat-libstdc++-33-3.2.3-72.el7.x86_64 ( or equivalent ) compatibility libraries to be installed on the 64-bit Linux system. If this is not done the SAP transport type will not appear in the transport type pick list. Ask your Linux system administrator to install the 64-bit compatibility libraries. You will need to restart the runtime after this has been done.
    The following shows the command that can be used to install the compatibility libraries on a Centos 7 Linux distribution.
    yum install compat-libstdc++-33

Transaction Server and SAP software interaction

The Transaction Server supports one-way or bidirectional interaction between the node and the enterprise SAP business application program. In both cases, the initiator is the Transaction Server.

One way transaction

A one way transaction is configured to invoke an RFC interface from the node and deliver the data to the external SAP business application program. This pattern is used for status notification. A transaction of this type can be placed into a store and forward queue when connectivity to the SAP application server is lost.
The SAP transport connects to the SAP enterprise application server either directly or via a Windows proxy server. When a trigger executes, the RFC interface selected in the transport map executes on the SAP enterprise application server using the data specified in the transport map.

Bidirectional transaction

A bidirectional transaction allows data to be passed from the external SAP enterprise application server to the node where the RFC interface references parameters (as either export or changing). A bidirectional transaction is not suitable to be placed into a store and forward queue when connectivity to the SAP server is lost.

What's Inside