Response Route SAP

Introduction: Sections Phase 6 and SAP.

Note: The SAP service must be licensed and activated on the Integration Server to use this Response Route. Please contact our support or sales staff.


If the SAP service of the Integration Server is active, the output data can also be forwarded to connected SAP systems. For this purpose, Lobster_data can call a function module (RFC) on the SAP system. See also section SAP RFC.

images/download/attachments/36579069/SAP_1_EN-version-3-modificationdate-1583118369448-api-v2.png

images/download/attachments/36579069/SAP_2_EN-version-3-modificationdate-1583129076349-api-v2.png

(1) The SAP alias of the connected system (see configuration file ./etc/sap.xml).

(2) The name of the function module to be called on the SAP system.

(3) If this option is selected, all records are transferred to the function module, otherwise, an RFC call is made for each record. The nodes in the destination structure for fields and structures may only be traversed once per RFC call. In contrast, the nodes for tables may be traversed multiple times. Each iteration corresponds to one line in the table.

(4) To make this option selectable, the profile must have an Input Agent of type HTTP(S) and (3) must be set. If (4) is set and (5) is not set, then the RFC response is returned to the external client (that sent the HTTP request to the profile) as HTTP response (including HTTP headers). If (5) is set, then (6) must also be set to Synchronous for option (4) to be selectable. If (4) is then set, the first converted result of the subsequent profile that was triggered by this Response Route is returned as the HTTP response. See also section Profile Chains. Note: The HTTP response is always encoded in UTF-8.

(5) The response of the SAP system can be forwarded to another profile via Message. Below you specify the name of the subsequent profile and its Message Context and Message Queue. So the subsequent profile needs to have an Input Agent of type Message.

(6) There are three different types of messages.

  • Synchronous. The profile sends the message and does not continue until the response has been received.

  • Asynchronous. The profile sends the message and continues immediately. The response is irrelevant for the further profile execution.

  • Persistent. Works almost like Asynchronous. Additionally, however, if the remote system cannot be reached, the message will be stored and the Lobster_data tries to resend the message every 50 ms. If the message could not be delivered after a certain time, it is lost.

(7) If this checkbox is set, the response of a called subsequent profile is awaited and evaluated. That is, the Response Route only gets the status success if the RFC call and the subsequent profile were successful. If the checkbox is not set, only the RFC call need to be successful.

(8) The format in which the data is passed on to the subsequent profile. The format must correspond to the document type of the subsequent profile.