
Configure an XI receiver 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 for sending XML messages to an Integration Engine.
In the Integration Server for forwarding messages to a business system and the ABAP proxy runtime or the AS Java and the Java proxy runtime.
Select the Transport Protocol :
HTTP 1.0
HTTPS 1.0
Select the Message Protocol :
XI 3.0 or XI 3.1
For connecting an ABAP-based Integration Engine, Web AS 6.40.
For connecting the PCK
For connecting the Advanced Adapter Engine
For connecting the Java proxy runtime
Note the following for using the XI 3.0 and XI 3.1 protocols:
Using Message Protocol XI 3.0 :
If you send an asynchronous message from the Integration Server to the Advanced Adapter Engine, confirm the receipt with a synchronous response, an “internal” acknowledgment, and also an HTTP 200 OK ( “Your request has reached the required server” ). It is time-intensive to set up the “internal” acknowledgment and can affect performance.
Using Message Protocol XI 3.1 :
If you use this message protocol, no “internal” acknowledgment is set up and sent back synchronously but just an HTTP 202 message instead. This can have a positive effect on system performance.
For connecting the Adapter Engine (SE)
XI 2.0 for connecting an ABAP-based Integration Engine, AS 6.20
Adapter Engine is Integration Server in the Integration Server.
Define Type of Address
In the Integration Server, select an address type:
URL Address
Specify the following:
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 for 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.
HTTP Destination
Specify the address of the receiver.
The destination must be defined in the receiver system in order that the message can be processed.
The RFC destination must be of type H (HTTP connection to an SAP system) for an ABAP-based receiver.
The RFC destination must be of type G for a non-ABAP-based receiver.
Logon data is stored in the destination.
Define Authentication Data
Select the Authentication Type :
Using Logon Data for SAP Systems
You make these entries under User Name/Password .
If you want to exchange messages with an ABAP-based receiver, specify the following:
User name
User password
Logon language
Client
Use 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.
Define Security Settings
If you want to make additional settings for Web service security in the relevant receiver agreement for signing and encrypting messages, choose Select Security Profile .
The Security Profile is Web Services Security .
This option only exists for message protocol XI 3.0.
Transfer Stations of Message (Hop List)
To transfer in the XI message the stations in the Process Integration that a message passes through, choose Transfer Stations of Message (Hop List) .
This option only exists for message protocol XI 3.0.
The hop list is required for sending acknowledgments.
For more information: Processing Acknowledgment Messages .
If the hop list is not to go beyond the limits of the system landscape, do not set this flag.
If you want to send a request message outside of your system landscape (B2B) and the hop list is deleted, then it is possible to get an acknowledgment back:
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 you Integration Server in the target address must be created for this sender.
If the acknowledgment arrives at your Integration Server, it can then only be forwarded to the original sender of the message if the relevant request message has neither been deleted nor archived.