Hi,
Pipeline Steps called flow of XI .....
Hoe XI will pick up any message and Transfers explained in below.......
1. For the message to be picked up by the communication channel, the channel should be associated with a
sender agreement. Mere creation of a communication channel be doesn’t ensure the message to polled
and picked up by the adapter. The message reaches the adapter in its native message format. As the
communication in SAP XI happens in XI message format, a module inside the adapter converts the
message in native format into XI message format.
2. During this process, a message ID is generated for the message. To build the XI header (sender
agreement details like the sender system, sender message interface and the interface namespace) the
details are fetched by performing a CPA lookup(collaboration-partner-agreement are the configuration
object details that have been created using the configuration time. The details are updated into the
runtime cache when you activate the Configuration objects in Integration builder –Configuration time.
This cache is referred to as CPA cache).
3. This message is then sent to module for further processing. During the process of sending the
message to module processor, the message “Application attempting to send an XI message
asynchronously using connection AFW” is logged.
4. The module processor performs steps like structure conversion, communication channel specific
conversions (that have been specified in the “module tab” of the adapter channel). These conversion
modules are executed in the same sequence as mention in the communication channel.
5. After the successful execution of the conversion modules, the appropriate module (call SAP adapter
module) of the module processor is called which will send this message for persistent storage. This
message is put into the Send Queue of the messaging system for further processing. Messages like
“Message trying to put into the send Queue” and “Message successfully put into the queue” are logged
during this process. A confirmation message (success/ failure) is sent back to the sender application at
this stage. This confirmation message is used by the channel to perform various steps like deleting the
file that has a processing mode as delete.
6. The message that has been put in the Send Queue has to be picked up and sent to the Integration
Engine. The Adapter Engine and XI Integration server use XI Adapter for internal communication
purposes. So the XI Adapter picks up message from the send queue and parses the XI message. In this
process, the status of the message is set to DLNG and. Messages like “The message was successfully
retrieved from the send queue and message status set to DLNG”are logged.
7. The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with
which the Adapter framework has register itself.
8. On successful SLD look up, the message is sent via HTTP to the XI IS pipeline, using the pipeline URL
(http://hostname:abap-httpport/sap/xi/engine?type=entry). . If this is successful, a message
“The message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry
using connection AFW” is logged and the message statues is set to DLVD means message has been
successfully delivered to the endpoint( XI IS in this case).....
Regards,
Soumya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.