Procedure documentationConfiguring the Sender SOAP Adapter Locate this document in the navigation structure

 

Configure the sender SOAP adapter to be able to send content from remote clients or Web service servers to the Integration Server/PCK.

Prerequisites

  • The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

    Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel

  • You cannot add your own modules to this adapter.

Procedure

  1. Select theTransport Protocol as HTTP.

  2. If you want to send information from a remote client or a Web service server to the Integration Server/PCK, select the Message Protocol as SOAP 1.1. If you want to send an XI message from a legacy system or AAE using the SOAP Adapter, select the Message Protocol as XI 3.0.

    Using the XI 3.0 message protocol, you can, for example, configure the communication between the Advanced Adapter Engine and ABAP proxies generated in back-end systems. Note that there are restrictions for using this option. For more information, see SAP Note 1247043.

  3. Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine.

    This selection is not available in the PCK.

1. Define Security Parameters

  1. If you want to make additional settings for security in the relevant sender agreement on the Integration Server or in the PCK, select Select Security Profile.

    More information: Security Settings for Sender SOAP Adapter

    Note Note

    If you select Security Profile, there must be exactly one sender agreement for the defined communication channel.

    End of the note.

  2. Under Security Profile select:

    • Web Services Security

    • S/MIME

  3. Specify the Persist Duration for messages in days, hours, minutes, and seconds.

Note Note

Security Parameters are available only if you select the Message Protocol as SOAP 1.1.

End of the note.
2. Define Conversion Parameters

  1. If the adapter is to expect a message without a SOAP envelope, selectUse No SOAP Envelope.

    In addition specify nosoap=true in the URL.

    The adapter puts the whole message in the XI payload.

  2. To include the header of the Web service message in the XI message, select Keep Headers.

  3. To include attachments of the Web service message in the XI message, select Keep Attachments.

  4. If the XI header information is to be included in the encoded string, select Use Encoded Headers.

  5. If the XI header information is to be included in a query string, select Use Query String.

Note Note

Conversion Parameters are available only if you select the Message Protocol as SOAP 1.1.

End of the note.
3. Define Processing Parameters

Under Quality of Service, specify how the message is to be processed by the Integration Engine/PCK.

For Exactly Once In OrderQuality of Service enter the Queue Name.

More information: Quality of Service and

Ensuring Exactly Once in the Sender Adapter

4. Define Adapter-Specific Message Properties

  1. Select the Advanced tab page.

  2. To save adapter-specific attributes in the message header of the XI message, select Set Adapter-Specific Message Properties.

    • The following attributes are added to the XI message header if the sender makes them available, and if you select Variable Transport Binding.

      • Remote User: (technical name: SRemoteUser)

      • Remote Host: (technical name: SRemoteHost)

      • SOAP Action (technical name: SHeaderSOAPACTION)

      To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:

      • Variable Header: (technical name: XHeaderName1)

      • Variable Header: (technical name: XHeaderName2)

      • Variable Header: (technical name: XHeaderName3)

      The names of the fields and parameters must correspond to the names of the fields and parameters that also go through the HTTP request.

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

5. Define the Adapter Status

Set the adapter to Active to enable messages to be exchanged.

Note Note

Adapter Status is available only if you select the Message Protocol as SOAP 1.1.

End of the note.

Result

You have configured the sender SOAP adapter. You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option.

  • http://hostname:portname/XISOAPAdapter/MessageServlet?channel=partyname:service name:channelname

    If you have not created a party, enter channel=servicename:channelname.

  • http://hostname:port name/XISOAPAdapter/MessageServlet?senderParty=name of the sender party<&senderService>=name of the sender service<&interface>=name of the interface<&receiverParty>=name of the receiver party<&receiverService>=name of the receiver service<&interfaceNamespace>=name of the interface namespace