HTTP Transporter

The HTTP_TRANSPORTER activity sends a message from SAP ME to an external system over an HTTP or HTTPS communication channel, which is configured using a named HTTP destination. HTTP destinations are part of the SAP NetWeaver destination service and provide a clean separation between the transporter and configuration details of the communication channel (see Destination Service). Such details include the URL address, user authentication, and transport level security.

Once the HTTP connection has been established, it remains open until the collaboration system sends a response, or until the HTTP connection timeout has been reached (see Timeout Options for ICM and Web Dispatcher on SAP Help Portal at Start of the navigation path http://help.sap.com/nw73 Next navigation step SAP NetWeaver Library: Function-Oriented View Application Server Application Server Infrastructure Internet Communication Manager (ICM) Administration of the Internet Communication Manager Parameterization of the ICM and the ICM Server Cache Additional Profile Parameters Next navigation step SSL Parameters for ICM and Web Dispatcher End of the navigation path ). When the response is received, SAP ME ignores it. If a communication error occurs, SAP ME tries to re-execute the transport according to the retry option settings described below.

Prerequisites

You have configured the HTTP destination for the external system (see Maintaining HTTP Destinations).

Options

The following table describes options that you can set in Service Extension Maintenance to change the behavior of this activity:

Option	Description
HTTP_DESTINATION_NAME	HTTP destination name
MESSAGE_KEY	The lookup key the transporter uses to retrieve a message provided by another service extension. Note MESSAGE_KEY is applicable only when MESSAGE_SOURCE is set to SERVICE_EXTENSION. End of the note. The default value: com.sap.me.integration.HttpTransporterActivity.MESSAGE_KEY
MESSAGE_SOURCE	The source of the content transported in the message SERVICE_EXTENSION (Default): The message is provided by another service extension attached to the same extension point as this transporter. The service extension providing the message must be configured to execute before the transporter. API_INPUT: The service method input converted to the XML format API_RESULT: The service method output converted to the XML format
RETRY_ATTEMPTS	The number of attempts to execute the transport after a transport fails The default value: 0 Note This option is valid only when the transporter is configured to execute asynchronously. End of the note.
RETRY_INTERVAL	The time delay between the attempts to execute the transport after a transport fails The default value: 600000 milliseconds Note This option is valid only when the transporter is configured to execute asynchronously. End of the note.
RETRY_TYPE	RETRY_SINGLE (Default): Only this service extension is retried. Service extensions attached to the same execution point with a lower sequence are not executed. RETRY_ALL: This service extension and all extensions attached to the same execution point with a lower sequence are executed. Note This option is valid only when the transporter is configured to execute asynchronously. End of the note.