CPI to CPI Connection and both tenants will be on different subaccounts at different regions.

[Yogita1]

Hello Guys,

I am having some concerns about CPI to CPI Connection so please help me if anyone has any clue or faced similar issue:

We need to connect two CPI tenants which will be on different subaccounts at different regions. 

What will be the recommend adapter for the connection .HTTP adapter is one of the option but do we have any limitations for using the HTTP adapter. Below are the use cases:

Number of calls between two tenants
High volume Scenarios
Any latency during transmission
Huge payload

[robertot4s]

Hi @Yogita1 ,

Communication between both CPI's is similar to communication between an external web application and CPI, so you don't have limitations about the number of calls. It is important to take into account the licensing model for messages, because a huge volume scenario can has an important impact: https://me.sap.com/notes/2942344

About latency, you must consider the location (cloud provider and region) where each CPI is deployed.

About payload size, here you have some information:

https://help.sap.com/docs/integration-suite/sap-integration-suite/optimize-performance

https://help.sap.com/docs/integration-suite/sap-integration-suite/limit-size-of-incoming-messages 

Hope it helps!

Regards,

Roberto

[Yogita1]

Hi @robertot4s ,

I am unclear about this — could you please clarify which adapter is suitable for connecting both CPI systems?

Thanks

Yogita

[robertot4s]

Hi @Yogita1 ,

There isn't any specific adapter to connect CPI systems, you can use standard adapters like HTTP/HTTPS. ProcessDirect adapter is only for iflows deployed in the same tenant.

Regards,

Roberto

[Yogita1]

Hi @robertot4s 

Can we use JMS or XI adapter also for connection?

Thanks

Yogita

[robertot4s]

Hi @Yogita1 ,

With JMS adapter you can't because it is for local JMS queues in the same tenant.

With XI protocol maybe... but I don't see the advantage. Personally, I don't like XI protocol, it is like an old protocol from PI/PO for on-prem integration engines...

Regards,

Roberto