Expose bapi/RFC as web-service PI 7.0 VS ECC 6

[Former Member]

Hi PI Gurus,

what do you recommend using to expose a RFC  as web-service  PI or ECC.

I have noticed that we can directly expose  BAPI/RFC using ECC 6   so will there be any advantage importing BAPI/RFC to PI and then exposing it ?

I think directly from ECC the performance might be better ? Is there a way on ECC that where we can check the logs ( for eg errors while attempting to  access web service  ).

Thanks for your time.

Raj

[former_member184720 · Accepted solution]

Hi Raj - You can directly expose it from ECC.

You can find the logs under SOAMANAGER for web service calls.

Reference : http://help.sap.com/saphelp_nwpi711/helpdata/en/af/7591e6b48944ba884cd2eb800789d1/content.htm

unless there is some kind specific monitoring requirement, there is no point in hosting a web service in PI.

Incase your web service involves frequent changes then it might be easy to maintain in PI.

Message was edited by: Hareesh Gampa

[Former Member · Accepted solution]

Thanks Hareesh for the information.

What about performance which is better exposing from   ECC or PI ?

Will this also apply for consuming web-services from third party  ECC VS PI ?

[former_member184720 · Accepted solution]

Hi Raj - If you can consume/Expose the web service directly in ECC, then involving PI is an additional process step .

Ofcouse PI would be helpful, if there are multiple parties involved in the integration.

I mean incase the service exposed by ECC has to be consumed by multiple vendors then it would be good to host in PI as a central repository.

In addition we have better monitoring capabilities in PI.

Performance depends on factor such as message size, transformation involved etc but as i mentioned if you can consume/expose directly then i personally don't use PI.