cancel
Showing results for 
Search instead for 
Did you mean: 

Pipe line steps ? Same for All Scenario's ? Not Same?

Former Member
0 Kudos

Hi All

My question is Pipe line steps are constant for all the scenario's

Irrespective of sender and receiver ?

Or For some scenario's will it differ? like BPM, Proxies ....?

Can any one help me on this pl.....

Anv...thanks and points to helpful answers

kiran LVS

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

all messages as pass thorugh pipe line steps .If it BPM then it gives BPM engine but this is done again through IS .

Former Member
0 Kudos

Hi

All messages in 'IS' will follow the same steps irrespective of sender/receiver

And the steps details are as follows

1. Receiver Determination--> Determine the receiver of the message using the Sender Service, Sender Interface and sender namespace.

2. Message Split --> if multiple receivers are found, split of the message for each receiver.

3 Interface determination --> Determine the inbound interface and the interface mapping for each of the receivers.

4 Message Mapping --> Execution of the mapping program!

5. Technical Routing -> The messages in mapped to the corresponding target Transport Protocol

6. Call Adapter --> The target adapter is called and the message is passed to the same.

Regards

--- prasad

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

1) Receiver Determination: Determines the system that participates in the exchange of the message.

2) Interface Determination: 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.

Also

Pipeline is the term used to refer to all steps that are performed during the processing of an XML message.

A pipeline represent a fixed processing run for particular XML messages and differs from other pipelines depending on the configuration of the Integration Engine. There are pipelines for a local Integration Engine in the sender or receiver system, or for a central Integration Engine that is configured as the Integration Server, for example.

The individual processing steps that an XML message must pass through when it is processed are called pipeline elements. Each pipeline element calls exactly one pipeline service.

Pipeline services provide functions for processing XML messages. They read and can change inbound XML messages, for example, the mapping or routing. They can also call processing processes, for example functions to create business data in an SAP component. The service type, number, and sequence are specified for each pipeline and cannot be changed.

The pipeline services are either part of the Integration Engine itself or originate from other areas of the SAP Exchange Infrastructure. A pipeline service can be used by more than one pipeline element.

http://help.sap.com/saphelp_nw04/helpdata/en/ff/3eb33b553e436ee10000000a114084/content.htm

Configuration guide may help you define that-

https://websmp102.sap-ag.de/~sapidb/011000358700001697502004E.PDF

Regards

Chilla

prabhu_s2
Active Contributor
0 Kudos

yes it is the same across the scenarios