cancel
Showing results for 
Search instead for 
Did you mean: 

Difference betwwen P2P and ICO in PI7.1

0 Kudos

Dear all,

Just needed to know the differences between P2P and Integrated Configurations when both bypass the Integration Server.

When to use each one of them. Explain with example for each.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

HI,

Addition to the above....

ICO - for performance improvements where all the steps will be executed in java stack itself no need to send the data to abap stack ,persist the data...by avoiding all these steps internally..will improve the processing time of the message...

P2P - point to point for controlling the configuration throgh the middleware system which enables the loose coupling of the systems and serves the puprose of ESB...if enterprise landscape demands...just uses the runtime of the IS...but the data will not pass through any of the components of PI...

HTH

Rajesh

former_member181962
Active Contributor
0 Kudos

Hi,

Integration server consists of Integration Engine(Whichis on ABAP stack) and Adapter Engine (Java stack).

Using ICO, you can bypass Integrayion Engine (But you cannot really say you can bypass integration server, since the message has to go through Adpater engine anyhow).

But where as using PTP, you can bypass the whole Integration server (Both IE and AE).

Also, for PTP you got to ensure a set of pre requistites like,

1) both sender and receiver interfaces have same structure, no mapping, no dynamic receiver determination etc.

Whereas these are not required for ICO.

Best Regards,

ravi

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Integrated Configuration Object will be used if you prefer to run the message transformation /processing in Advance adapter engine(Java stack) and fully by pass Integration Engine (classical engine/abap stack)

Example in SAP PI 7.1 - if you have source and target adapters are java adapters then you can go for it.

example File to Jdbc or SOAP to JDBC

PI 7.1 EHP ... In addition to above adapters, Proxy adapters are also covered in Advance Adapter Engine.

PI 7.3 - All the adapters including HTTP, IDOC are covered in AAE.

P2P - Point to Point communication. We can use P2P both in Advance Adapter Engine and Integration engine (abap stack). Based on the requirement, you decide whether one to one communciation or one to many or so..