Limitations of SAP PI 7.3(single-stack Java installation)
Introduction
Two options while installing SAP PI 7.3 :
1.) Single stack Java installation
2.) Traditional Dual stack installation
*This presentation will cover limitations of Single stack installation.
*But in some of the case alternatives will be provided.
*SAP introduced the Advance Adapter Engine (AAE) in PI 7.10. The AAE provides end-to-end message processing to be executed completely in the java-stack. This increases performance significantly since messages will no longer be passed back-and-forth between the ABAP and the java stacks. With this java-only processing, a new configuration object is also introduced in the Integration Directory to configure the end-to-end scenarios. This new configuration object is “Integrated Configuration Object”, or ICO, and is used to configure the scenarios which will only be processed in the java-only engine.
*With PI 7.30, AEX was created. AEX, a java-only ESB, is built on AAE
*The dual-stack installation continues to be available as an installation option. The architecture remains unchanged from the previous releases.
Note: *Please note the distinction between AAE and AEX
*AAE: AAE is an adapter engine which provides message processing in the java-only stack. AAE is installed in both dual-stack and single-stack PI installations of PI 7.1 and above.
*AEX: AEX is a java-only installation of PI, which uses the AAE.
1.) Decentralized adapter Engine doesn’t work in ICO/ ICO works with only same type of adapter engine.
*Error while assigning different adapter engine in sender and receiver communication channel: “Assigned sender and receiver communication channels are not configured for the same adapter engine; ensure that all channels are configured for the same adapter engine”
*So, If you want to work on Java based adapter and decentralized adapter engine then use classic configuration, as classic configuration supports both java based adapter and classic configuration. This can be monitor in SXMB_MONI transaction of ABAP stack.
Even this functionality is not supported on PI 7.3.1
2.) Advance Adapter Engine can not use Idoc adapter. As Idoc adapter is based on ABAP stack
*AAE cannot use Idoc adapter as Idoc adapter is based on ABAP stack but in PI 7.3 (Java stack) we have IDOC_AAE adapter available.
*If you still want to work with IDOC adapter only then install Dual stack
3.) Advance Adapter Engine can not use HTTP adapter.As HTTP adapter is based on ABAP stack
*AAE cannot use HTTP adapter as HTTP adapter is based on ABAP stack but in PI 7.3 (Java stack) we have HTTP_AAE adapter available.
* If you still want to work with HTTP adapter only then install Dual stack.
4.) AAE cannot use the WS adapter. As WS is an ABAP adapter
*If you want to work with WS adapter then install Dual stack.
Note: For all ABAP based adapter
*We can assign only java based adapter in ICO. It will not allow to assign ABAP based adapter in ICO as they are on Integration Engine.
*For Ex. Below are the list of ABAP and JAVA based adapters for a communication component
Below are the list of communication channels available in ICO for a communication component
Only Java based adapters are available in ICO
5.) ccBPM is not available for AAE
*ccBPM is not available for AAE. As ccBPM uses ABAP’s work-flow engine to orchestrate the messages.
*In case if it is required in your project then install Dual Stack.
6.) Extended Receiver Determination is not available in ICO
*Extended receiver Determination have used earlier in classic configuration.
![clip_image009[1]](http://lh5.ggpht.com/--4-X7a_5vN0/UjxjrPfIqsI/AAAAAAAABb0/mrZsoXOpmbw/s1600-h/clip_image009%25255B1%25255D%25255B2%25255D.gif "clip_image009[1]"){kind=small}
How ever Routing based on XPath expression is available
![clip_image009[2]](http://lh5.ggpht.com/-mdb5NpVm238/Ujxjtm0SbdI/AAAAAAAABcM/fxgNJinEBm4/s1600-h/clip_image009%25255B2%25255D%25255B2%25255D.gif "clip_image009[2]"){kind=small}
*Install Dual Stack for Extended Receiver determination in case it is required
7.) Using Integration Directory’s Receiver Rule is not available
*Receiver Rule is not available using Integration Directory
8.) Parameterized Mapping
*Using mapping parameters in Operations Mapping is not available in ICO.
![clip_image009[3]](http://lh4.ggpht.com/-7uFleKXfDGI/UjxjxYw-xZI/AAAAAAAABck/T2aB1jVNEt4/s1600-h/clip_image009%25255B3%25255D%25255B2%25255D.gif "clip_image009[3]"){kind=small}
*No parameterized mapping in ICO
*This is still available with Dual Stack
![clip_image009[4]](http://lh6.ggpht.com/-4idhKOkn8BI/Ujxj3JNl4FI/AAAAAAAABdE/VmTbps_wS_c/s1600-h/clip_image009%25255B4%25255D%25255B2%25255D.gif "clip_image009[4]"){kind=small}
9.) ABAP mapping cannot used by AAE
*ABAP mapping is executed in ABAP, therefore cannot be used by AAE.
ABAP mapping is present in PI 7.3 with Dual stack installation.
10.) AAE does not support “Maintain Order at Run Time”
*Maintain Order at run Time is not available in ICO. This was available in Classic configuration.
with Dual stack installation functionality of Maintain order at Run Time can be achieved with Java based adapter
*Below is the result of Maintain Order at Run Time in classic configuration for Java Based adapter.
11.) No more SXMB_MONI transaction
No message will be available in SXMB_MONI transaction of PI(ABAP Stack) system for Configuration scenario which are based on ICO.
But in SAP PI 7.3 we still have many option for monitoring the message in NWA for Single stack.
Summarizing AAE Limitations
AAE limitation in ICO for PI7.3 and PI 7.31 release:
Terms to understand
*AAE : AAE is an adapter engine which provides message processing in the java-only stack. AAE is installed in both dual-stack and single-stack PI installations of PI 7.1 and above.
*AEX: AEX is a java-only installation of PI, which uses the AAE. With PI 7.30, AEX was created. AEX, a java-only ESB, is built on AAE, but with all the ABAP dependencies removed
*ICO: “Integrated Configuration Object”, or ICO, and is used to configure the scenarios which will only be processed in the java-only engine.
*Classical configuration : Integration Directory configuration with Receiver Determination, Interface Determination, Sender and Receiver Agreements, and Communication Channels. These configurations are what we will call as “classical” configuration, and will be processed by both ABAP and java engines.
Contact:+918008002022
