Scribd
Upload
35 views3 pages

SAP PIPO Guru99 Tutorials4

The document outlines the structure and functioning of SAP PI, detailing the types of interfaces (outbound, inbound, and abstract) and the pipeline steps involved in message processing. It explains the role of the Adapter Engine in converting messages between different formats and the Business Process Engine's function in managing integration processes. Additionally, it describes the components of the SAP PI home page and the Enterprise Services Repository for designing integration scenarios.

Uploaded by

Bharath
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
35 views3 pages

SAP PIPO Guru99 Tutorials4

The document outlines the structure and functioning of SAP PI, detailing the types of interfaces (outbound, inbound, and abstract) and the pipeline steps involved in message processing. It explains the role of the Adapter Engine in converting messages between different formats and the Business Process Engine's function in managing integration processes. Additionally, it describes the components of the SAP PI home page and the Enterprise Services Repository for designing integration scenarios.

Uploaded by

Bharath
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

In PI, message is represented by an interface.

Interface -> structure of the message in XML format + direction

Based on the above criteria, there are three types of interfaces

Outbound interface - connect to the sender system


Inbound interface - connect to the receiver system
Abstract interface - connect to the BPE

When we configure integration logic (scenario) in the SAP PI as per our business
requirements, it is the integration engine which executes that configuration in a
step-wise manner. Pipeline is the term used to refer to all steps that are
performed during the processing of an XML message. The pipe-line steps consist of
the following:

Receiver Identification - determines the system that participates in the


exchange of the message.
Interface Determination - determine which interface will should receive the
message.
Message Split - if more than one receiver are found, PI will instantiate new
message for each receiver.
Message Mapping - mapping to transform the source message to destination
message format.
Technical Routing - bind a specific destination and protocol to the message.
Call Adapter - send the transformed message to the adapter or a proxy.

Adapter Engine

You must have noticed earlier that the integration engine handles messages in XML-
SOAP protocol only. But what if we have a sender and a receiver business system
where the data is not in the same format. We use the various adapters in the
Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and
format required by these systems, and vice versa.

As we have discussed earlier, SAP PI is a hub and spoke structure where the Adapter
Engine can be considered as spoke. We use the Adapter Engine to connect the
Integration Engine (Hub) to the external systems. The Adapter Framework is the
basis of the Adapter Engine. The Adapter Framework is based on the SAP J2EE Engine
(as part of the SAP Web Application Server) and the J2EE Connector Architecture
(JCA). The Adapter Framework provides interfaces for configuration, management, and
monitoring of adapters.

In a dual stack system, most of the adapters where based on the Java stack barring
two adapters which are based on the ABAP stack.

Java Stack

RFC adapter, SAP Business Connector adapter, file/FTP adapter, JDBC adapter, JMS
adapter, SOAP adapter, Marketplace Adapter, Mail adapter, RNIF adapter, CIDX
adapter

ABAP stack

IDOC adapter and HTTP adapter


When SAP PI moved from dual stack to single stack then these two adapters became
part of the Java stack. The modified adapter engine is known as the Advance Adapter
Engine and the two adapters are called the IDOC_AAE adapter and HTTP_AAE adapter
respectively.

Business Process Engine

The Business Process Engine is responsible for executing and persisting integration
processes.

BPM stands for cross-component Business Process Management or ccBPM and is also
called Integration process. An integration process is an executable, cross-system
process for processing messages. In an integration process you define all the
process steps that are to be executed and the parameters relevant for controlling
the process. Business Process Management provides SAP Exchange Infrastructure with
the following functions:

State-full message processing: The status of an integration process is


persisted on the Integration Server.
You can also use correlations to establish semantic relationships between
messages.
You implement integration processes when you want to define, control, and
monitor complex integration processes that extend across enterprise and application
boundaries i.e. collect/Merge, Split, Multicast

At runtime, the Business Process Engine executes the integration processes. The
integration process can send and receive messages using abstract interfaces only.

Build a scenario in SAP PI

We start from the Home page if we have to build a scenario in PI.

The home page will look similar to as given below:

Figure 6 – Home Page for SAP PI Java Stack

The Home page has hyperlinks to the following 4 working areas

Enterprise Services Repository (ESR)


Integration Directory (ID)
System Landscape (SL)
Configuration and Monitoring (CM)

Each hyperlink will open one application. All these four are Java application. ESR
and ID are swing applications. They are launched from the browser based on JNLP. So
for the first time it takes more time as it downloads the entire library file. But
from second time onwards, it takes less time to launch. SL and CM are pure web
applications and run on the browser.

Enterprise Services Repository

Here we design and create objects to be used in the making of an integration


scenario. The data flow in PI will look similar to as shown below:

We find the option to design the following

Interface objects – Service Interface, Message Type, Data Type


Mapping objects – Operation Mapping and Message Mapping
Integration Processes

PI uses integration repository to design message structure for both sender and
receiver systems and develop an interface message using corresponding message
structures which act as a point of interaction to the outside world. Data type and
Message type are used to simplify and modularize the design of a complex interface.

Operation Mapping allows transformation of source structure to target structure


when the two structures are different. But if the source and the target structure
are same then the operation mapping may be dispensed off. Similar to service
interface, message mapping is used to simplify and modularize the design of a
complex operation mapping. Message mapping can be implemented in 4 ways

Graphical Mapping
Java Mapping
XSLT Mapping
ABAP Mapping

Graphical mapping is the most used as it allows developer to map attributes of both
structures graphically to pass data using service interfaces. For the other three,
we have to develop the mapping by writing code. If it is a single stack server,
then the ABAP mapping will not be available.

There are other areas also, but they are not covered in this tutorial.

You might also like