All About SAP PI (Process Integration)

Example: for understanding the concept of SAP PI in a clear way we can an example of a large-scale Dairy Industry, which operates in a huge area of a state and even dominates the entire region. However alongside there a few small- scale dairy industries which also operate in the same region, and run parallel to the large-scale industry which does not make profit primarily because of their price variation as compared to large-scale industry. For avoiding the pricing conflict and maintaining the same price all over the region, the large scale and small-scale industry with the help of SAP PI together decide to link together. With the help of SAP PI (Process Integration), they inter-connect with each other and begin working as a single unit. Through the medium of SAP PI both they are able to exchange all the information related to the dairy industry, which even encompasses pricing as well as sharing equal amount of profit.  

Prior to SAP PI, through the medium of point-to-point communication, business would connect with each other. However, this process did not turn out very helpful especially for the complex and multiple processes. Mediated communication or the Integration broker is utilized and SAP PI adapts this system in a very effective way, and paves way for a more smoother communication between the multiple businesses. This enables the interconnection of various process via a central location which is known as Integration Broker, quite unlike the point to point connection which is more like a spider web. The integration broker or the server is an important part of mediated communication which comprises of the Java based Advanced Adapter Engine (AAE) and an integration engine meant for routing purposes. The mediated communication is typically based on an integration broker which is executed through exchanging XML messages.

Lets know more how SAP PI effectively manages the XML messages with the help of the Integration Broker. Generally, the exchange of data or message in SAP PI tutorials takes place in the four phases listed below: 

Message Transformation: During the message exchange it alters the entire structure of the business data.

Message Routing: encompasses forwarding a message sent by a sender system to one or more of the receiver systems

Connectivity Adapters: Connecting the integration broker and receiver system, the adapter transforms the incoming message into an inbound message and later it converts it to the format of the receiving system at the other end.

Integration Processes: Cross component Business Process Management (ccBPM) comprises of the functions meant or enhancing the service orchestration.

 

For messages the SAP PI offers a message level security primarily for the XI message protocol, for the SOAP adapter, for mail adapter, for the RosettaNet protocol, , for the CIDX protocol and for connectivity with WSRM (Web Service Reliable Messaging) enabled systems. 

In SAP PI message level security is all enabled through the usage of encryption, Username token digital signature, SAML Assertion, Certificate token, etc. The different methods of authentication are all supported by WS infrastructure for transport level which encompasses the basic authentication (Password and Username), SAP assertion ticket, and HTTP over SSL.

Connecting the Integration Server with WSRM (Web Service Reliable Messaging) Enabled System

The user utilizes a communication channel of adapter type WS, for connecting with WSRM enabled system.

For connecting the Integration Server to a WS consumer, the user utilizes a sender agreement with an assigned WS sender adapter.

The user utilizes a receiver agreement with an assigned WS receiver adapter for connecting the integration server to a WS provider

Report this Page