on 09-15-2011 10:04 AM
Hello experts,
earlier today I found this article:
http://www.itworld.com/soa/109637/architectural-principles-usage-sap-pi-a-soa-environment
and I was wondering if there was an official SAP statement regarding this:
SAP PI usage is not recommended for synchronous communication since it places a significant load on the infrastructure services for servicing a synchronous request. Also, SAP PI cannot guarantee the QoS and response time in processing a sync request.
- For User Interface scenarios (such as a WebDynpro UI), the UI can directly consume enterprise services. SAP PI should not be used in UI driven scenarios if the backend is exposed as enterprise services.
can somebody point me to some document on this?
Thanks in advance!
Tricky!
We are using PI 7.11, and when it comes to synchronous calls there are a majority of our interfaces giving us excellent response times and performance. The AAE designs helps better the cause. Most of our UI based solutions, ex. CRM screens call sync interfaces through PI.
But if a decision has to be made to route the calls not via PI, then the driving factors could be;
1. What if PI has a scheduled down time and the UI cannot afford this?
2. The UI portal could be a BCM based solution i.e it still needs to provide results even though PI could be down.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stefan,
We are in the same boat as Shabz on this. We have a very huge portal completely relying on PI for all synchronous communication with the back end (ECC and several other legacy systems as well) and are pretty much happy with the response time and the problem we have currently is any outage in PI (even a very short duration) is causing the whole portal to be unavailable. This has proven costly in some situations.
We are still trying to get the system stabilised.
Regards
Jai
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.