Configuring the Receiver XI Adapter 

Use

You configure a receiver XI adapter for the following situations:

●      In the Integration Server, for example, to send XML messages from the Integration Server to a PCK. The PCK is the receiver.

●      In the Integration Server, to send XML messages to an Integration Engine.

●      In the PCK, to send XML messages from the PCK to the Integration Server. The Integration Server is the receiver.

Integration

You configure the adapter on the Parameters tab page during the definition of a communication channel in the Integration Server or in the PCK. You cannot enhance this adapter with your own modules on the Module tab page in the module processor.

Prerequisites

...

       1.      You have created a new communication channel or have opened an existing one.

       2.      On the Parameters tab page you have selected the adapter type XI.

       3.      You have selected the Receiver radio button to define the adapter as a receiver adapter.

Activities

To configure the adapter, specify the following:

Transport Protocol

●      HTTP

●      HTTPS

Message Protocol

Integration Server

PCK

●      XI 3.0 To connect an ABAP-based Integration Engine, Web AS 6.40. To connect the PCK. To connect the XI 3.0 J2SE Adapter Engine, see Plain J2SE Adapter Engine. To connect the Java proxy runtime. ●      XI 2.0 To connect the XI 2.0 plain J2SE Adapter Engine. To connect an ABAP-based Integration Engine. To connect an ABAP-based Integration Engine, Web AS 6.20. The protocol cannot be used to connect the PCK.

●      XI To connect to the Integration Server.

Adapter Engine

Select the central or a non-central Adapter Engine. This selection is not available in the PCK.

Addressing Type

Integration Server	PCK
URL Address Make the following entries: ●      Target Host: Specify the host name of the receiver system. ●      Service Number: Specify the HTTP port. ●      Path Prefix: Path prefix of the receiver The address of the PCK is: http://<host>:<port>/MessagingSystem/receive/AFW/XI <host> is the host name of the receiver system. <port> is the http port. /MessagingSystem/receive/AFW/XI is the path prefix.	URL Address Specify the address of the receiver.
HTTP Destination Specify the address of the receiver. The destination in the receiver system must be defined so that the message can be processed. ●      In the case of an ABAP-based receiver, the destination is an RFC destination of type H (HTTP connection to an SAP system). ●      In the case of a non-ABAP-based receiver, the destination is an RFC destination of type G. Logon data is already defined in the destination. For more information about settings, see: ●      Configuring the Channel for ABAP Proxy Receivers ●      Configuring the Channel for Java Proxy Receivers

Authentication Data

Integration Server	PCK
Use logon data for SAP systems. If you want to exchange messages with an ABAP-based receiver, specify the following: ●      User name ●      User password ●      Logon language ●      Client	User name/password Enter the user name. ●      Enter the password for the user and confirm. ●      Logon language Specify the logon language of the SAP system. ●      Client Define the client of the SAP system. Certificate logon for the HTTPS transport protocol: ●      Specify the certificate name. ●      Specify the keystore.
Logon data for non-SAP systems If you want to exchange messages with a non-ABAP-based receiver, specify the following: ●      User name ●      User password
Anonymous logon If the receiver does not execute any authentication, choose this option.

Security Settings

If you want to make additional settings for web services security in the relevant receiver agreement on the Integration Server or in the PCK, set the Web Services Security indicator. This option is only available for the XI 3.0 message protocol.

Transfer Hop List

If you set this indicator, the items of the message in XI are transferred in the XI message. This option is only available for the XI 3.0 message protocol.

The hop list is required to send acknowledgments. See also: Processing Acknowledgment Messages

If you do not want the hop list to be transferred outside your own system landscape, do not set the indicator.

If you want to send a request message outside your system landscape (B2B) and the hop list is deleted, the following option enables you to receive an acknowledgment:

●      The sender of the request message (communication party and service) must be created in the Integration Server that receives this request message. A receiver channel of adapter type XI that references your Integration Server in the target address must be created for this sender.

●      When the acknowledgment arrives at your Integration Server, it can only be forwarded to the original sender of the message if the corresponding request message has not been deleted or archived.

Further Input Options in the PCK

●      Persist Duration

Specify the length of time in Days, Hours, Minutes, and Seconds that asynchronous messages are to be stored in the Adapter Framework message store, depending on the communication channel.

In asynchronous message processing, the Persist Duration must correspond to at least the product of Number of Retries and Retry Interval.

●      Number of Retries

Define how many attempts should be made to send an outbound message in the case of an error.

●      Retry Interval

Specify the retry interval in days, hours, minutes, and seconds, after which the system should attempt to forward a message from the PCK to the SAP XI Integration Server when errors occur.