Adapter engine is named as (Advanced) Adapter engine from the version 7.1 onwards. The reason is you can process the message within adapter engine itself. So the same document is good enough.
In Pi 7.1 we can process messages either through adapter engine (By configuring SA,RA,ID,RD) or through Advance Adapter Engine (by configuring Integrated Configuration step).
So you mean to say that if I follow the below document, then I can process the messages through Non-central Adapter engine on both AE and AAE (as referred above).
In Pi 7.1 we can process messages either through adapter engine (By configuring SA,RA,ID,RD) or through Advance Adapter Engine (by configuring Integrated Configuration step).
If you configure SA,RA,IF,RD the message will go by the Advanced Adapter Engine and later to the Integration Engine (ABAP side). SAP recommends to use, if it's possible because in SAP PI 7.1 not all adapters are in the AAE, the integrated configuration object. With this object all proccesing is in the AAE and the PI dont need to send the message to the ABAP-side and you increment the efficency.
>>So you mean to say that if I follow the below document, then I can process the messages through Non-central Adapter engine on both AE and AAE (as referred above).
Let me put this way, Decentral engine is like one more adapter engine installed and u also have the flexibility to chosse the routing of messages from Central or de-central AAE (when u configure ur CC, at that point u can chosse between AAE and decentral AAE)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.