about understanding the pi' message processing

[Former Member]

Dear All:

I wanna to know the detailed step of message process in PI,for example : message throught the adapter message system IS , Anyone can helpe me,or give me some doucument.

thanks!

kevin liang

[Former Member · Accepted solution]

Hi Kevin,

Please go through this blog, that support Kubra's quick points on Message flow.

[Understanding Message Flow in XI|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1717] [original link is broken] [original link is broken] [original link is broken];

Best Regards

Praveen K

[Former Member]

Hi Kevin,

Message flows from AE to IE, there it performs a series of pipeline steps and again it flows from IE to AE.

Me_ssage flow from Integration Server to Adapter Engine_ ::Check the Audit Log of message during return journey

The return journey commences when the IS has successfully processed the message and delivers it to the Messaging system using the URL u201Chttp://hostname:50000/MessagingSystem/receive/AFW/XIu201D

1.When the Integration Server (XI IS) finishes processing of the pipeline steps (like receiver determination, interface determination and interface mapping), the message has to be delivered to the required Receiving system. So the XI Integration server will send the message to the messaging system of the Adapter Engine (AE) using the mentioned above. Once the message is successfully received by messaging system, the message u201CThe message was successfully received by the messaging system. Profile: XI URL: http://hostname:50000/MessagingSystem/receive/AFW/XIu201D is logged.

2.As discussed Integration server and Adapter Engine use XI adapter for internal communication purposes. So the XI message that has been received by the messaging system URL is parsed by the XI Adapteru2019s protocol handler.

3.The XI message is put into the receive queue and persisted. During this stage messages like u201CUsing connection AFW. Trying to put the message into the request queue; Message successfully put into the queue.u201D are logged.

4.The XI messages that are put in the receive queue are retrieved by an application (Worker thread) and are sent to AFWListenerBean. AFWListenerBean is a module (an EJB) in Adapter Engine that is capable of parsing the XI message. On successful receive of the XI message by the AFWListenerBean, messages like u201CThe message was successfully retrieved from the request queue.u201D are logged and the status of the XI message is set to DLNG.

5.The AFWListenerBean reads the receiver agreement and the corresponding channel from the XI header to determine the appropriate adapter. In this stage the adapter channel is logged in the audit log. u201CDelivering to channel: XYZ_Channelu201D

6.The message is forwarded to the module processor where additional steps like structure conversions and extra modules specified in the adapter are performed.

7.The exit module is called and the message is sent to the appropriate adapter (DB Adapter in this case). The format conversion will be executed within the specific adapter and sent to the Receiving system (DB in this case) using the channel that has been determined by the AFWListenerBean and the required action is reformed (select statement is performed in this case). On successful processing of the message the status is set to DLVD

Thanks,

Sobha.

Edited by: Sobha C on Apr 20, 2009 7:21 AM

Edited by: Sobha C on Apr 20, 2009 7:25 AM

[Former Member]

Hi Kevin,

Kindly go through the below link..

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2f2a9fa2-0a01-0010-32ac-d281db72...

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

Thanks and Regards,

N.Jayanth Kumar

[Former Member]

hi,

Message flow from Adapter Engine to Integration Server

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

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

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

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

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

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

<h5>see also pipeline steps that are executed in Integration Server</h5>

also see this

[http://help.sap.com/saphelp_nw04/helpdata/en/1b/89d24032f68231e10000000a1550b0/frameset.htm]

[Former Member]

Hi Fatima,

your descrption is very helpful for me about message processing.

I have done file to idoc scenario and file to file scenario.

after activating the objects in integ.directory , i couldnt see the processed msgs in sxmb_moni for both scenario.

In RWB comoponent monitoring when i see communication channel monitor it shows only outbound msgs but both comm.channel functioning properly.even i could see the msgs in mesage monitoring(except outbound msgs). the outbound log shows the msg executed succesfully waiting in que. after some times it shows status: system error, error category:XI_J2EE_ADAPTER_XI_HANDLER , error code:SEND_CONSUMER_ERROR. I think the mesages not going in to integ.engine.

i thought it might be a cache problem .So I execute the Tcode SXI_CACHE it shows following error 1,Unable to Refresh Cache Contents 2, Error During Last Attempt to Refresh Cache. i double click the above error it shows following details.

Incorrect XML display for AlertCategory

Error during deserialization

Data loss occurred when converting 011136c23c9430359b57c0ef8949c630

Can you give me the solution

Thanks

Raja Mohamed

[former_member732072]

Hi Kevin,

Just check the following link

http://help.sap.com/saphelp_nw04/helpdata/en/1b/89d24032f68231e10000000a1550b0/content.htm

as well as the following link

http://help.sap.com/saphelp_nw04/helpdata/en/a4/31d940f52f7e7fe10000000a1550b0/content.htm

Best Regards.

[former_member200962]

Hi,

Very simple....create a scenario and test it.....then:

1) Login to SAP GUI

2) Go to transaction /nSXMB_MONI

3) Double-click on the message processing corresponding to your scenario

4) On the next page that opens you will see all the required steps:

Inbound Message

Receiver Determination

Interface Detemination etc....

Nothing much has changed in 7.0 and 7.1.....just one more step is added more of "XML validation"

Regards,

ABhishek.

Edited by: abhishek salvi on Apr 20, 2009 9:29 AM