Configuring the Receiver XI
Adapter
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.
● In the Integration Server, to forward messages to a business system and the ABAP proxy runtime or AS Java and the Java proxy runtime.
...
1. Select the Transport Protocol:
○ HTTP 1.0
○ HTTPS 1.0
2. Select the Message Protocol:
○ XI 3.0 on the Integration Server
■ To connect an ABAP-based Integration Engine, Web AS 6.40
■ To connect the PCK
■ To connect the Adapter Engine
■ To connect the Java proxy runtime
○ XI 2.0 on the Integration Server
■ To connect the Adapter Engine (SE)
■ To connect an ABAP-based Integration Engine, Web AS 6.20
○ XI in the PCK
To connect to the Integration Server
3. On the Integration Server, the Adapter Engine is called Integration Server.
This selection is not available in the PCK.
4. On the Integration Server, select the addressing 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 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.
○ HTTP Destination (also specify in PCK)
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 must be an RFC destination of type H (HTTP connection to an SAP system).
■ In the case of a non-ABAP-based receiver, the destination must be an RFC destination of type G.
Logon data is contained in the destination.
More
information:
Configuring the
Channel for ABAP Proxy Receivers,
Configuring the
Channel for Java Proxy Receivers
5. On the Integration Server, select the Authentication Type:
○ Use logon data for SAP systems
You make these entries in the PCK as well, 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
In the PCK, you make the following additional entries for certificate logon with transport protocol HTTPS:
■ Specify the certificate name.
■ Specify the keystore.
○ 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.
6. If you want to make additional settings for Web service security in the corresponding receiver agreement, choose Select Security Profile.
The Security Profile is Web Services Security.
This option is only available for the XI 3.0 message protocol.
More
information:
Receiver
Agreement
7. To transfer the stations that a message passes through in Process Integration in the XI message, choose Transfer Hop List.
This option is only available for the XI 3.0 message protocol.
The hop list is required for sending acknowledgments.
More
information:
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.
8. Under 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.
9. Under Number of Retries, define how many attempts should be made to send an outbound message in the case of an error.
10. 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 Integration Server when errors occur.