How to handle Integrated Configuration performance impact on AAE/Java AS

[Former Member]

Hi there,

Recently I have moved a configuration scenario from standard flow involving both ABAP and Java stacks, to Integrated Configuration usage. Undoubtedly, this will increase the load on AAE/Java stack. However, do you have link to some clear (official - even better) guidelines - what configurational changes should be done on Java side in order to handle the performance impact of such transition?

Best Regards,

Lalo

[former_member184681 · Accepted solution]

Hi Lalo,

In fact, using AAE generates no traffic in ABAP stack at all (it is ommited when processing a message), while the traffic in Java stack should be lower than for normal scenario. The performance should be noticeably better, thanks to smaller number of persistence steps and no costly HTTP connections between stacks. For more details, please refer to this document:

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/2016a0b1-1780-2b10-97bd-be3ac62214c7

Important quotation from this document:

Since the Integration Engine is bypassed for local message processing in the AAE, the resource consumption both in memory and CPU is lower. This leads to higher message throughput, and faster response times which especially is important for synchronous scenarios.

Moreover, have a look at this document, especially its beginning, for details about the architecture of AAE processing:

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b

Hope this helps,

Greg

[Former Member]

Hi Greg,

Thank you for providing these documents, however I am well aware of them. What I meant is something like this: in "normal" scenario case the PI system setup has 50 WPs on ABAP side and 5 Java threads per adapter type (just for example), however when moved the scenario to a integrated configuration the load will be moved to Java stack - so its configuration (Java VM properties, JEE Services properties, eXchange profile, etc.) should change to adapt. Or the Java stack configuration does not need any adaptation at all ..?

Best Regards,

Lalo

[baskar_gopalakrishnan2]

> Or the Java stack configuration does not need any adaptation at all ..?

Since we avoid the persistence steps in Java stack and JVM 5+ has great performance and memory recycling for java stack, You might not need special configuration like setting work processess. But you might sure want to add java threads more.