HTTP(S) services

SAP XI services support the HTTP transport protocol. HTTP embodies a client-server model in which an HTTP client opens a connection and sends a request message to an SAP XI server. The client request message is to invoke an SAP XI service. The SAP XI server dispatches the message containing the invocation and closes the connection.

The connector's HTTP and HTTPS protocol listeners make use of the HTTP client-server and the Request/Response models when handling client requests to a collaboration. However, the HTTP listener is not intended to function as an HTTP server-- proxy, intermediary, or otherwise. Rather the HTTP listener functions as an endpoint for use within an enterprise and behind a firewall. Accordingly, a separate web server or gateway must be deployed in the firewall to route client requests to the listener. For further information, see Overview of the adapter.

Synchronous HTTP(S) service

From the perspective of connector processing, a synchronous HTTP service is one that follows a Request/Response path. If the HTTP or HTTPS protocol listener successfully processes an HTTP request message, the body will contain the response and an HTTP status code of 200 OK. If a fault is returned, then the body contains the fault message and a status code of 500.

Asynchronous HTTP(S) service

From the perspective of connector processing, an asynchronous HTTP service is one that follows a request-only path. If the HTTP or HTTPS protocol listener successfully receives and processes a request-only operation, an HTTP status code of 202 Accepted is generated. You can also configure the connector to generate an HTTP status code of 200 OK --for further information see the HTTPAsyncResponseCode property inTable 32. If a fault occurs, an HTTP status code of 500 is generated. There is no response, although a fault body may be returned.

Copyright IBM Corp. 1997, 2004