Process Orchestration: Sizing Calculation for PI/BPM system

[Former Member]

Hi experts,

I need to calculate a correct sizing for a new Process Orchestration system. I know all expected runtime PI-interfaces and we also have some assumptions regarding the BPM processes which are planned to be run.

Since there is no sizing possibility in the quick sizer available yet for PO as such, I found a forum entry where it was mentioned that the BPM sizing and PI sizing should be done separately.

Now, after doing both sizings (BPM based on the following guide http://service.sap.com/~sapidb/011000358700000454652010E/ and PI based on the PI quicksizer tool) I am wondering what I need to do with the 2 SAPS values I get as a result? Do I just need to add those 2 values to get the final sizing for the PO machine?

Thanks for all your help!

Best Regards

H.

[Former Member · Accepted solution]

SAP answered my question: Just add the two calculated SAPS values for PI and BPM.

[Former Member · Accepted solution]

I would add that you have to respect the individual peak times of PI and BPM. If they overlap you have to add the numbers. If the peaks occur at different times for PI and BPM I would not add them up.

Did you move from a PI dual stack to a PO single stack? Do the real life resource requirements match the calculated values? I would expect the single stack to use less resources than a dual stack so that even with added BPM no bigger machine than before would be required. Can you share what you learned?

Best regards,

Ulf

[Former Member · Accepted solution]

Hi Ulf,

Regarding your questions:

- We installed a complete new machine. However there were some dual-stack PI scenarios which we have added to the total sizing calculation of the PI (AEX) part.

- Real life scenario experience: Good question! We are not completely live yet with all the interfaces and BPM processes which were taken into account for the sizing calculation. Therefore I cannot tell you yet unfortunately.

- Single vs. Dual-Stack: Yes correct, this was anyway the initial idea of SAP to have a smaller hardware footprint by using only one single stack. For our calculation that means: Since BPM is anway running only on the Java stack and since the PI calculation part was only based on AEX (which is also only based on Java-Stack), the calculated two SAPS values for the BPM and PI(AEX) part should reflect only the needed hardware for one stack (the Java-stack).

Sizing of the PI part mainly depends on your expected scenarios and the volume of those. That's why you need to add the number of messages and the peak times.

The BPM calculation is more focussed on how many users have access to how many tasks in the UWL at the same time.

Hope this helps a bit.

Best Regards

Harald

[PaulBartlett]

2756077 - Process Orchestration Sizing is specific on the addition of AEX and BPM values to get the total PO sizing. However there is no specific information nor references about how to do the BPM sizing!