cancel
Showing results for 
Search instead for 
Did you mean: 

data flow in Xi?

Former Member
0 Kudos

hi all,

can any one tell me how the data is flowing in Xi,

that is how data is moving from IR and ID and what steps that Data is flowing in ID.

and i am bit confused with how data is moving from integaration server also.

plaese help me in this....

thanks & regards,

Madhav

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

refer this blog:

/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi

Regards,

Indira D

Answers (6)

Answers (6)

Former Member
0 Kudos

HI

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 doesnu2019t ensure the message to be 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.

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 u2013Configuration time. This cache is referred to as CPA cache).

This message is then sent to module processor for further processing. During the process of sending the message to module processor, the message u201CApplication attempting to send an XI message asynchronously using connection AFWu201D is logged.

The module processor performs steps like structure conversion, communication channel specific conversions (that have been specified in the u201Cmodule tabu201D of the adapter channel). These conversion modules are executed in the same sequence as mention in the communication channel.

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 u201CMessage trying to put into the send Queueu201D and u201CMessage successfully put into the queueu201D 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.

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 u201CThe message was successfully retrieved from the send queue and message status set to DLNGu201Dare logged.

The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with which the Adapter framework has register itself.

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 u201CThe message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFWu201D is logged and the message statues is set to DLVD means message has been successfully delivered to the endpoint( XI IS in this case)

you can refer the baove steps in the following blog

/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi

PIPELINE:

XI messages are passed through a series of processing steps called xi pipeline. A pipeline service is an abap object class that performs a particular processing step on a message. All the messages that are received at the integration server are processed in a consistent way.

URL for sending a message to a pipeline is:

http://<host>:<port>/sap/xi/engine?type=entry

PIPELINE Steps:

Receiver Identification:

To determine which systems should participate in an exchange with the incoming message.

Interface Determination: For each receiver system determine which interface should receive a message.

Message Branch:

If multiple receivers are found, XI instantiate a new message for each receiver

Request Message Mapping:

Call the mapping program to transform the message structure to the receiver format.

Outbound Binding:

Bind a specific destination and protocol to the message.

Call Adapter:

Send the transformed message to the adapter or proxy.

cheers

reward points if found useful

former_member556603
Active Contributor
0 Kudos
Former Member
0 Kudos

Hi,

Pipeline :

When a source message reaches the Integration server

the messages under goes this

a) Receiver Determination:

This steps determines the system that participates in the exchange of the message.

b) Interface Detremination:

For each receiver determine which interface will should receieve the message.

c) Message Split:

If more than one receievers are found, XI will instantiate new message for each receiver.

d) Message Mapping:

Mapping to transform the source message to destination message format.

e) Technical Routing:

Bind a specific destination and protocol to the message.

f) Call outbound Adapter:

Send the transformed message to the adapter or a proxy.

Note: reward points if solution found helpfull

Thanks,

Soumya.

Former Member
0 Kudos

Hello Madhav,

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).....

And also Check these docs,

/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f79be190-0201-0010-96b9-f00...

*******Reward points,if found useful

Former Member
0 Kudos

Here is ID Flow:

Sender Agreement:

To identify the respective sender

Receiver Determination: Who is the receiver?

Interface determination: Inbound Interface and corresponding Mapping.

Receiver Agreement:

Corresponding Receiver channel

Thanks,

Boopathi

Former Member
0 Kudos

Hi,

Go thru this blog,

/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi

Message flow:

/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Regards,

Shabari