CPI Runtime on PO -Error reprocessing and multithreading

[former_member595583]

Hi,

PO has 2 features error reprocessing and multithreading ( suppose you have to process a very high volume interface ). Now these are not a default option on CPI (In CPI you can implement error reprocessing via JMS Queue)

Now I wanted to know if we design the integration on CPI and deploy on PO CPI runtime ( for my premise to premise interface )then can we take advantage of PO for these features

1) Can we increase the multithreading like for any other PO interface

2) Will the error reprocessing work for CPI integration content like it works for any other PO interface .

[Sriprasadsbhat]

Hello Rahul,

Below might help you

1) Currently interface level scaling is not supported in SAP CPI- It is planned in roadmap and you can follow the same for availability ( Q4 2021 )

https://roadmaps.sap.com

2) There is no in built capabilities - You need to model your integration using JMS or Data Store or any other equivalent retention services.

Regards,

Sriprasad Shivaram Bhat

[former_member595583]

Hi Sriprasad,

Thanks for reply but my question was for CPI runtime and not CPI , because once CPI runtime is deployed on PO it would use the PO resources , so what would be the mechanism for multithreading ( if it has to run for high volume ) for these deployed interfaces ?

So in short if I have to accept 20 parallel soap request can I do that ?

[MortenWittrock]

Hi Rahul

The CPI runtime is completely separate from the PO pipeline, so you don't have access to those PO features, sadly.

Regards,

Morten

[former_member595583]

Hi Morten,

Thanks for the reply . But then in that case if I have a very high volume synchronous interface , suppose around 500,000 individual sales order ( so message size is small , but many individual orders) a day then how will I use multithreading to ensure I process many orders a time if I am using CPI runtime on PO.

So the FCAserverthreadcount is not applicable for interfaces running on CPI runtime ?

Is there any other way to increase the parallel processing ( not from splitting in CPI design as the messages are small and single )?

[MortenWittrock]

Hi rahul.singh3

FCAServerThreadCount is specific to NetWeaver, and I'm not aware of a similar option for the CPI runtime. But as a general observation, since this is for on-premise to on-premise integration (i.e. local files, local queues etc.), you might be better off creating this in PO, where you have that functionality already available.

Regards,

Morten

[former_member595583]

Hi Morten,

Considering SAP recommendation is to use CPI runtime where possible for premise to premise integration ( as it has more design patterns and would be easy to migrate in future if one of the legacy premise system goes cloud )

are we really saying that the interfaces deployed using CPI runtime would always be single threaded ? And there is not any way to increase multithreading ?

So if it’s a synchronous SOAP interface we won’t be able to make 15-20 parallel calls ?