Adapter message flow

Hi,
Any one explain the message flow in XI
Thanks in advance

Hi Deepan,
Message flow is the pipeline steps in XI.Pipeline is nothing but the steps performed in integration engine at runtime. After the message is converted to xml in adapter engine it goes to integration engine for processing. In IE these pipeline steps process the message further. These include: receiver determination, interface determination, message split, and mapping, routing, call adapter.
When a source message reaches the Integration server
the messages under goes this
a) Receiver Determination:
This steps determines the systems that sends and receive the messages.
b) Interface Determination:
For each receiver determination there should be an interface to receive the message.
c) Message Split:
If more than one receiver 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.
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714f85ffc11d5b3ea0050da403d6a/framese
More Info in the Blog <a href="/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi Message Flow in XI</a> By Siva Maranani
Regards
San

Similar Messages

Where to find detail message flow in scenario of AQ to DB adapter?

I have installed hub, aq and DB adapter. The repository, adapters seem to be run fine. I put some messages in AQ and found out that there were no messages appeared in DB. The messages could be found in AQ_OUTBOUND_QUEUE. Sine there is no error message in adapter log files(trace is turned on), I am not sure it's the hub problem or adapter problems. Where should i check the message flow so to decide the problem?
Any constructive advice is welcome.

Hi Johnson,
Have you set the queue to the event in the deploy tab of AQ application in iStudio? If not then please set your OUTBOUND_QUEUE to the corresponding event and then do push metadata after starting the adapter. You can have a look at "Appendix A -> Deployment -> Setting Queues" of Interconnect User guide for this.
regards,
Sandeep

Message flow between advanced adapter engine and messaging system for ICO scenarios

Dear all,
I'm working on a PI 7.31 AEX box and created an ICO object for one interface with HTTP_AAE2IDoc scenario. The interface works quite well. When I looked in to message log of messages for this interface in PI monitor, I noticed that the internal XI message are put totally 5 times into the send queue and retrieved from send queue. In some steps I only see after retrieving a message from send queue and immediately put it back into send queue. Can someone please kindly explain the message flow between advanced adapter engine and messaging system and what exactly happens after each retrieving a message from send queue?
Below is an example of message log for one message:
12/08/2014 09:26:06.472 Information MP: processing local module localejbs/CallSapAdapter
12/08/2014 09:26:06.472 Information Application attempting to send an XI message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.478 Information Trying to put the message into the send queue
12/08/2014 09:26:06.499 Information Message successfully put into the queue
12/08/2014 09:26:06.499 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.499 Information The application sent the message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System. Returning to application
12/08/2014 09:26:06.500 Information HTTP adapter successfully processed interface PlantResponse_Out
12/08/2014 09:26:06.501 Information Trying to put the message into the send queue
12/08/2014 09:26:06.501 Information Message status set to DLNG
12/08/2014 09:26:06.513 Information Message successfully put into the queue
12/08/2014 09:26:06.513 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.515 Information Message status set to DLNG
12/08/2014 09:26:06.533 Information Trying to put the message into the send queue
12/08/2014 09:26:06.548 Information Message successfully put into the queue
12/08/2014 09:26:06.548 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.550 Information Message status set to DLNG
12/08/2014 09:26:06.551 Information Executing Request Mapping "http://styrolution.com/pi/Integration/PlantMaintenance/PlantResponse/PlantResponse_to_Zcol_Basf_Inotif02_Inotif01_Zeupm_Inotif01_Ludwigshafen" (SWCV 085d2320fb3b11e2cc0bf4d50aea8c33)
12/08/2014 09:26:06.563 Information Trying to put the message into the send queue
12/08/2014 09:26:06.571 Information Message successfully put into the queue
12/08/2014 09:26:06.571 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.573 Information Trying to put the message into the send queue
12/08/2014 09:26:06.573 Information Message status set to DLNG
12/08/2014 09:26:06.580 Information Message successfully put into the queue
12/08/2014 09:26:06.580 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.582 Information Message status set to DLNG
12/08/2014 09:26:06.583 Information Delivering to channel: IDOC_R
12/08/2014 09:26:06.583 Information MP: processing local module localejbs/IDocOutboundModuleBean
12/08/2014 09:26:06.583 Information XI message received for processing
12/08/2014 09:26:06.587 Information Sender Party: Sender Service:SXX Receiver Party: Receiver Service:RXXCLNT200 Communication Channel:IDOC_R
12/08/2014 09:26:06.588 Information IDOC metadata repository is RXX
12/08/2014 09:26:06.589 Information Control record is not mandatory - control record will be added if not available
12/08/2014 09:26:06.590 Information XML Payload parsed to idoc document list with number of idocs: 1
12/08/2014 09:26:06.595 Information Sending idoc message to receiver R/3 system with TID XIh{lsRI824UITC0009OalmW
12/08/2014 09:26:06.813 Information IDOC message sent to receiver R/3 system
12/08/2014 09:26:06.817 Information TID XIh{lsRI824UITC0009OalmW confirmed
12/08/2014 09:26:06.819 Information Message was successfully transmitted to endpoint <local> using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.821 Information Message status set to DLVD
Thanks & regards
Dingjun

Hello All,
Thanks for the prompt responses and with best information, But apart from this,I need how an adapter(File/JDBC) works along
with AAE in PI 7.1. When does the job of File/JDBC adapter is completed and resumed in a synchronous case. That is,
File Location --> file adapter -
> XI(AAE) --> JDBC adapter --> database.
In file sender, lets suppose we have synchronous settings(Best Effort). Now when File adapter's job is finished and when it
gets back the response back from XI. Please explain step by step from starting(file adapter polling the location) to getting the response coming back to XI.
Regards,
Achari.

Loop in message flow found

Hi all
I created a idoc to abap proxy for the xi adapter i used http destination with my destination defined in sm59.
In sxbm_moni i get the error:
LOOP_IN_MESSAGE_ROUTING
Loop in message flow found: system is.00.metsapxd, pipeline CENTRAL with inbound adapter XI already processed
Anyone know how to fix the error?
Thx

Hi,
I think your end business system i.e. where proxy exists -- this application system is configured as "integration engine/HUB". Try to keep it as (SXMB_ADM -> Integration engine configuration) type of business system as "applicaiton system" instead of integration engine/server.
Regards,
Rao.Mallikarjuna

Regarding Message Flow in XI

Hi Experts,
I was go through the Blog given by Siva Maranani
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
But in this After sending the Xi Message from send Queue to Integration Engine...
What wi be the process inside this IE.
Please let me know
Regards
Khanna

But as per my knowledge in the IS the Pipeline services wil be done( Includes Receiver det, Interface Det, Mapping, Logical rout, Tech. routing, Call Adapter, Message Split )
It means there is no further process inside the IE??????????
Messages received at the Integration Server are processed through a defined series of steps called Pipeline Services. These pipeline services are part of Integration Engine which in turn is a part of Integration Server
Only the XI Adapter wil pick the Xi msg from Send Queue to IE.......Thats it?????/
Yes. Thats the main task of XI Adapter. It also does the SLD lookup.

then this IE wil pass this XI Msg to the IS ..... Right????????
As mentioned, IE is part of IS
Regards,
Prateek

Message flow in XI

Hi all,
pls can anybody send me the link or documents for message flow in XI....and also it will be helpful if u send me some faqs and answers on XI..
thanks & regards,
Santosh

Hi Santosh,
The message flow is like below
1. From sender it reached Sender Adapter ( Communication
channel ).
2. From AE it goes to IE , inside IE it go through Pipeline steps.
3. From IE it will go to recievr side AE.
4. From reciever's AE it goes to Reciever's system.
- Satish

Message flow from XI To Receiver

Hi ,
There are several IDOC to JDBC scenarios running in our XI PRD server but now all the IDOCs are reaching XI,which is visible in IDX5 or SXMB_MONI but nothing has reached the Receiver as visible from Message monitoring.
In SXMB_MONI , i can see the errors CLIENT RECEIVE FAILED.pls figure out the problem and tell me how to proceed wid.
Thanx,
Laawanya

hi
as you are doing idoc-jdbc scenario check whether the reciver MT you maintained is of JDBC-XML structure
check Document Formats for Receiver JDBC adapter
check the blog for the message flow in xi:
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
Note:please reward points if solution found helpfull
Regards
Chandrakanth.k

SXMB_MONI is not showing any messages flow

Hi,
I am sending a request through SOAP adapter to SAP system. My scenario is executing fine. One strange thing I have seen is, in RWB, Message Monitoring I can see my outbound message and inbound message but in component monitoring I cannot see my SOAP adapter and RFC adapter are active.
Note: one more thing is I can not see anything in SXMB_MONI; no message flow is showing
Can any one tell me whats happening?

you need to have entry in SXMB_ADM entry in our XIserver
category :RUNTIME parameter:Logging value :1
category :RUNTIME parameter:Logging_sync value :1
category :RUNTIME parameter:Trace_level value :1
Regards
Sreeram.G.Reddy

How to convert XML to Binary in OSB Message flow

Dear All,
Can you please help me in converting XML to Binary in OSB Message flow.
Please help.
Thanks,

ah ok, then you have to apply a transformation from XML to some fixed length format, EDI style
probably you have 2 options: the traditional MFL
http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/consolehelp/mfls.html
or the (probably) more supported nXSD with a JCA adapter
http://docs.oracle.com/cd/E23943_01/integration.1111/e10231/nfb.htm
I will let you digest this info and then we can continue.
There are a number of threads in this forum on whether one technology is better than the other (as usual, google can assist you)

XI Message flow

I am trying to integrate a r/3 system with XI, can someone point me to possible data flow diagrams.
What can be a possible scenario here...?
Can someone also point me to the message flow within IR and ID for the above scenario..
Regards
Ravi

Hi,
Pipeline steps for XI Message flow steps , This might help you to understand
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.
Regards
Agasthuri Doss

Message flow

Hi all,
when the message is sent from sender,how does it go to receiever..i.e sequence of steps how msg flows from sender to receiver?
Regards,
keerthi

Hi,
Message flows according to these pipeline steps
- Inbound message
- Receiver determination
- Interface determination
- Receiver grouping (in case if receiver are more then one)
- Message branch according to receiver list (in case if receiver are more then one)
- Request message mapping
- Technical routing
-Call Adapter
-Response
message comes in the server and depending upon the request of client this is directed to ABAP Stack or Java stack By ICM.
Also Check out these blogs
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
regards
Aashish Sinha
PS : Reward points if helpful

Message flow direction

What exactly is the message flow direction ? In a sender system does the message moves from adapter engine to integration server or viceversa ? Similarly in a receiver system does the message move from Integration server to adapter engine ?

Hi Radhika,
The messages are picked up by the sender communication channel, send to resource adapter in adapter engine which does the required formats into xml.
Then it goes to Module Proccessor and all module works on this in a perticular manner.
then it goes to in a queue, and all the basic routing and mapping part is done here
and then it goes to Integration server Messaging Queue.
To receive the messge from Integration server Messaging Queue and upto receiver end whole process is done in reverse manner.
If the adapter involved is a Java based adapter, then the flow would be
Sender - Adapter Engine (sender) - Integration Engine - Adapter Engine (receiver) - Receiver
If say sender adapter is ABAP based, then it would be
Sender - Integration Server (Idoc/HTTP Adapter) - Integration Engine - Adapter engine (receiver) - Receiver
for more clarrification go throgh the following blog
Understanding message flow in XI
Regards
Sridhar Goli

Message Flow in Integration Engine

Dear Friends,
Kindly can someody share how the message is flowing in Intergration engine after the message taken from Adapter engine.
If you have any block diagram it will be helpful for me

Hi Karthik,
There are 6 stpes for the message processing thats only called
PIPELINE Steps.
what are all the steps involved in the Pipeline processing.
Sender Adapter picks up the file from the file system, converts it to XML and places it in the payload of an XI-SOAP message. Then it posts this message to the Integration Server pipeline via http(s).
XI pipeline steps are:-
->Sender Agreement
->Receiver Determination
->Interface Determination
->Interface Mapping
->Receiver Agreement.
When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:
1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
2) Interface Determination: For each receiver determine which interface will should receiver the message.
3) Message Split: If more than one receivers are found, Xi will instantiate new message for each receiver.
4) Message Mapping: Mapping to transform the source message to destination message format.
5) Technical Routing: Bind a specific destination and protocol to the message.
6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
message flow in XI
The life cycle of the message is explained in detail by taking an example scenario. The file is picked up by the Sender File adapter and the data is inserted into DB table by Receiver DB Adapter.
       The adapter engine uses the messaging system to log the messages at every stage. This log is called the Audit Log. The audit log can be viewed from the runtime work bench (RWB) to look into the details of the lifecycle of the message. During our journey we will also have a look at the messages that are logged at different stages.
Note: This article is targeted for the newbieu2019s who want to understand the message flow in Adapter Engine. So the insight into the message lifecycle is provided here by taking only the Technical adapters (File/ JDBC/ JMS/ Mail) into consideration. It doesnu2019t delve into the lifecycle of the messages that have reached XI Adapter Engine using RNIF/ BC/ CIDX adapters.
ONWARD JOURNEY:
Fig1. 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. Here 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)
Fig2. Audit Log of message during onward journey
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
br>
Fig3. Message flow from Integration Server to Adapter Engine
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.

Regarding message flow in sap xi

HI
i want to the flow of message from outbound system to inbound system completly.
ie i want to know ---which components like message interfaces,rd,id,sa,ra,.............such types.i want to know the complete flow and after which step which is to be taken place.
also i want to know the steps involved in pipeline and when it will be called in the above sequence.
thanks in advance.

Hi
The steps involved in XI message flow are below.
1.Receiver Identification - Determines which system to participate in an exchange with the incoming message.
2.Interface Determination - For each receiver system determines which interfaces should receive a message.
3.Message Split - If multiple receivers are found, XI will instatiate a new message for each receiver.
4.Message Mapping - Call the mapping program to transfer the message structure to the receiver format.
5.Technical routing - Bind a specific destination and protocol to the message.
6.Call adapter. Send the transformed message to the adapter or proxy.

Invalid request bo for BAPI_GOODSMVT_CREATE call in Message Flow.

Hi, all
I call BAPI_GOODSMVT_CREATE in my message flow through SAP adapter node.
Here is the xml format BO created in ESQL,
<NS1:SapbapigdmvcrtWrapper xmlns:NS1="http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapbapigdmvcrtwrapper">
<SapBapiGoodsmvtCreate>
 <SapGoodsmvtHeader>
 <PstngDate>2008-07-02</PstngDate>
 </SapGoodsmvtHeader>
 <SapGoodsmvtCode>
 <GmCode>03</GmCode>
 </SapGoodsmvtCode>
 <SapGoodsmvtItem>
 <Material>PWRPACK52</Material>
 <Plant>1000</Plant>
 <StgeLoc>0001</StgeLoc>
 <MoveType>201</MoveType>
 <EntryQnt>33.000</EntryQnt>
 <EntryUom>PC</EntryUom>
 <EntryUomIso>PCE</EntryUomIso>
 <Costcenter>1000</Costcenter>
 </SapGoodsmvtItem>
</SapBapiGoodsmvtCreate>
</NS1:SapbapigdmvcrtWrapper>
By switch on user trace on broker, I got the message that the request bo is not correct.
But I can running BAPI_GOODSMVT_CREATE function without error in SAP GUI function builder test with same input data.
The only thing I am not sure is the posting date, for ESQL messageset, it's defined as DATE, I populated it by CURRENT_DATE function. But in the funtion builder test GUI, I input it as 02.07.2008 format. Is this the problem?

Change the data format to YYYYMMDD also doesn't work.
And changed the user profile data format dd.mm.yyyy to yyyy-mm-dd, still remain bo xml input date yyyy-mm-dd, still doesn't work.

Adapter message flow

Similar Messages

Maybe you are looking for