Show TOC

Configuring the Java HTTP Adapter on the Sender ChannelLocate this document in the navigation structure

Prerequisites

You have launched the PI integration directory for the Java HTTP adapter and have chosen to configure the sender channel.

Context

You use this procedure to configure the sender Java HTTP adapter to convert the HTTP request to XI message and then forward it to the AAE for processing.

Procedure

  1. In the Parameters tab, in the Transport Protocol , select HTTP 1.1 .
  2. Determine how the sender system sends the HTTP request and select one of the options for the message protocol.

    • POST

    • GET

  3. Select the Adapter Engine on the Integration server, or select a non-centrally installed Adapter Engine.
  4. In the Parameters tab, choose the General tab.
  5. Determine the type of HTTP input and then perform the following steps.

    For more information, see HTTP Requests Supported by the Java HTTP Adapter .

  6. If the HTTP input is through the form submission, choose Set Form and enter the Main Payload Parameter Name to specify the name of the request parameter whose value should be copied to the XI main payload.
  7. If the HTTP request is a multipart request where one or more different sets of data are combined into a single body, choose Set Multipart .
  8. If you want the attachments in the HTTP request to be copied as XI message attachments, choose Keep Attachments .
  9. In the Parameters tab, choose the Advanced tab
  10. If you want to save adapter-specific attributes in the message header of the XI message, choose Set Adapter-Specific Message Attributes .

    • If you want to copy the HTTP header values into XI dynamic headers, choose HTTP Header Fields and enter the HTTP header names in the corresponding fields namely HTTP Header Fields (Field 1 (HeaderFieldOne),....,Field 6 (HeaderFieldSix))

    • If you want to copy the HTTP URL parameters as XI dynamic headers, choose URL Parameters and enter the HTTP URL parameter names that map to their respective dynamic headers in the corresponding URL parameter field namely URL Parameters (Parameter 1 (URLParamOne),...Parameter6(URLParamSix)) .

    • If you want to set the headers of the HTTP response message using XI dynamic headers, choose HTTP Header Fields (Synchronous Response) and enter the HTTP response header names namely HTTP Header Fields (Field 1 (HeaderFieldOne),....,Field 6 (HeaderFieldSix)) .

      Note

      The attribute for the adapter is http://sap.com/xi/XI/System/HTTP.

      For more information, see Adapter-Specific Message Attributes in the Message Header .

  11. Set the Adapter Status to Active to enable the messages to be exchanged.
  12. Choose Set Additional Parameters and enter the Name and Value .
    Note

    This section is present for extension purposes and need not be configured.

  13. In the Module tab, you can specify the modules for the adapter.
    Note

    CallSapAdapter is the default module in the module processor for configuring the sender adapter. The module is of type Local Enterprise Bean.

    For more information, see Adding Modules to the Module Processor .

Results

You have configured the Java HTTP adapter for the sender channel. To trigger a call to the Java HTTP adapter on the sender channel use the URL: http:// <hostname:port> / <path> ? <query-string>

Where,

  • path = /HttpAdapter/HttpMessageServlet

  • query-string = ?interfaceNamespace= <interfaceNamespace> &interface= <interface> >& senderService= <senderService> &senderParty= <senderParty> &receiverParty= <receiverParty> &receiverService= <receiverService> &qos= <qos> &queueid= <queueid> &msgguid= <msgguid>

Note

The parameters msgguid is optional. The parameter queueid is specified only if the QoS is EOIO.