Configuring the Sender WS Adapter

Configuring the sender WS adapter to send content from remote clients to the Integration Server.

1. Define the connection parameters.

   The sender adapter exposes an endpoint address with a default name generated from the channel, party, and service name.

   To define a different endpoint name, activate Custom endpoint address and enter the Endpoint address.

2. Define the processing parameters.

   Select how the message is to be processed by the Integration Engine from the Quality of Service list. For Exactly Once In Order, enter a Queue Name.

   For more information, see Quality of Service.

   Note Best Effort is not supported in WS-Reliable Messaging scenarios.
3. Set up reliable messaging

   If you want messages to be reliably delivered using the WS-Reliable Messaging (RM) standard, select Enable WS-RM.

   Note This option is not available if the selected Quality of Service is Best Effort.

   The Inactivity Timeout defines an interval in seconds. If the sender channel does not receive a message from the client during this interval, the sequence will be terminated due to inactivity. The default value is 1 week. To specify that sequences should never time out, enter a value of 0. This is not recommended unless you are sure that sequences are always closed properly. Otherwise, you will have to terminate sequences manually.

4. Set up addressing.

   Select Enable WS Addressing (WS-A) if an addressing header is required in the incoming message.

   Note WS-RM without WS-A is not supported, so if WS-RM is enabled this setting is implicitly set to ON.
5. Select the SOAP protocol version.

   Specify which SOAP version is to be used.

6. Define message-level security.

   On the WS-Security tab, specify which security checks are to be performed on the incoming message.

   Select Require Timestamp if a timestamp is required.

   If the message needs to be digitally signed, select Require Signature, choose whether a body signature is also required by selecting Require Signed Body Element, and specify the Signature Trust Store containing the signatures that will be accepted.

   Select Require Signed SAML 1.1 Assertion (SSO) if an SAML Assertion is needed, and specify the SAML Signature Trust Store containing the signatures that will be accepted.

   Note For SAML Authentication (SSO) to work, all the above features need to be activated.

   If the message needs to comply with the Web Services Interoperability Organization (WS-I) Basic Security Profile, activate BSP 1.0 Compliant. This option needs to be OFF if the sender is an SAP system.
7. Define message ID processing.

   On the Advanced tab, you can specify how message IDs are processed in the sender adapter. This includes the option of performing a duplicate check based on message IDs.

   Activate Enable Message ID Mapping if you want to customize message ID processing.

   Select the External Message ID Location, which can be either the WS-Addressing MessageID (if present), a SOAP header element, or an HTTP header field. In all but the WS-A case you also need to enter the name of the element/field.

   If you want to prevent a message with the same ID from being delivered more than once, activate Ignore Duplicate Messages.

   Activate Set XI Message ID to External Message ID to copy the ID from the selected location to the XI message header.
8. Define additional parameters.
   Note SAP currently uses this option for testing and debug purposes only.

   Activate Set Additional Parameters on the Advanced tab and enter the names and values for the additional parameters in the table.