on 03-06-2008 1:19 PM
We're in the process of validating our 7.0 system and can't get around the fact that our time critical interfaces are not processed quickly enough when a significant load is dumped on the PI system. We're moving from 2.0 to 7.0 and do not have this issue in 2.0. We've installed 7.0 on the same hardware as our 2.0 system. Our consultants have configured the interfaces to be sent to "high" priority queues but these queues appear to be getting no more time slices of the corresponding software engines than the regular queues.
Is there any other mechanism or server configuration within PI that could be used to help make sure that a given interface will be processed regardless of server load???
Thanks in advance,
Chad
Since there is a huge change in PI 7.0 from 2.0, so you should first check the hardware requirements to install the PI7.0 In my point of view your hardware is causing a problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chad,
>>Our consultants have configured the interfaces to be sent to "high" priority queues but these queues appear to be getting no more time slices of the corresponding software engines than the regular queues.
Have a look at this guide
Make sure all the steps in this guide are followed correctly. You should be able to get it.
If still the queues are not priporitized, raise a OSS message with SAP. This might be a bug. If so they will provide you with the correction.
Regards,
Jaishankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe that "priority queuing" is what the consultants put in place for us already with no success.
Could you supply a link to the procedural document???
Chad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
There might be 2 concerns for this issue :
1. Check the Java performance statistics of the system with the help of Basis guys. They will have already tools for that.
2. Check whether is there any Java memory leaks. These errors can be found in default trace file in visual amdin/Os level. This will decrease the performance of Java engine.
Thanks,
Ramesh
Hi Richardson,
You need to implement priority queuing mechanism, in which you can give the details of interface specific in that procedure.
That interface will be processed with priority.
Give your personal maiID, so that I will send you the procedural document.
Provide me the rewrd points, if u feel useful.
Thanks,
Ramesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We had an SAP XI BASIS consultant complete the sizing exercise and we were told that our existing hardware would not be a problem.
Current Server Specs:
CPU - Quad 2.8 GHz Intel Xeon MP
RAM - 12 Gig
OS - Windows 2003
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems ok.
Probabily you can go through the below mentioned document to Scale up XI.
Regards,
Sarvesh
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.