cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Steps

Former Member
0 Kudos

hi,

when the scenario runs wat will happens in background( internal process).

other than the execution routing rules, collabaration agreements, wat will happen in back ground.

how the file(file >xi->file scenario) picks and where it stores, after mapping wat will happen please let me know

thank u in advance.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Go through the blog by Siva to understand the processing.

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

With in Integration Engine, every msg is processed in a sequence of steps called XI Pipe line.

The steps in the pipe line are

1. Receiver Identification.

2. Interface Identification

3. Msg split.

4. Message Mapping.

5. Technical Routing

6. Call adapter.

Regards,

Jai Shankar

Answers (2)

Answers (2)

Former Member
0 Kudos

in XI it starts with Intergation engine from based on the requirement it will go to BPM and come back once it done thn it come to IS and give to adapter if it completes all process before calling adapter

in IS it exceuted pipe line steps.

regards

Sreeram.g.reddy

prabhu_s2
Active Contributor
0 Kudos

hi kiran

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 Detremination: For each receiver determine which interface will should receieve the message.

3) Message Split: If more than one receievers 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.