Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE)

Valid for SAP NetWeaver 7.3 SAP NetWeaver Process Integration (SAP NetWeaver PI) provides different runtime engines to process XML messages and to provide connectivity between components, partners and systems that are based on different technical protocols and standards: the Integration Engine (based on AS ABAP) and the Advanced Adapter Engine (based on AS Java). Both engines provide a slightly different set of adapters for connectivity. More information: Installation and Connectivity Options Which runtime engine you can use depends on the chosen installation option. For example, when you have installed SAP NetWeaver PI as standard dual-stack version, you can use both the Integration Engine and the Advanced Adapter Engine. Whereas, when you use the Advanced Adapter Engine Extended (AEX), a new installation option in SAP NetWeaver 7.3 which is technically based on AS Java only, you can only use the Advanced Adapter Engine as runtime engine. Using AEX has many advantages compared to a standard dual-stack installation of SAP NetWeaver PI. For more information, read section Advanced Adapter Engine Extended of the online documentation. However, the decision to use a particular installation option depends also on the set of adapters you need for connectivity. In order to promote the usage of the AEX, the widely used IDoc adapter, which in former releases only runs on the Integration Engine, has also been developed as part of the Advanced Adapter Engine as of release SAP NetWeaver 7.3. Therefore, also customers who install AEX can also use the IDoc adapter. Note: Note the following name convention: The IDoc adapter version that runs only on the Integration Engine (based on AS ABAP) is called IDoc adapter (IE) in the following (technical adapter type in Integration Directory IDOC_IE). More information: Configuring the IDoc Adapter (Integration Engine) The IDoc adapter version that runs on the Advanced Adapter Engine (based on AS Java) is called IDoc adapter (AAE) (technical adapter type in Integration Directory IDOC_AAE). More information: Configuring the IDoc Adapter (Advanced Adapter Engine)

Note that, however, IDoc adapter (AAE) has some limitations as compared to IDoc adapter (IE). The following table lists which features are supported in each case, and serves as a basis to decide on which adapter version to go for: Availability and Tool Integration Attribut/Feature Available in SAP NetWeaver (PI) Release IDoc Adapter (IE) SAP NetWeaver XI 3.0 SAP NetWeaver 7.0 (including EHP) SAP NetWeaver PI 7.1 (including EHP) SAP NetWeaver 7.3 As of 3.1x, IDoc metadata can be retrieved SAP applications based on SAP Basis 3.1 or higher SAP Web Application Server 6.20 or higher Non-SAP applications with a certified IDoc interface, for example EDI systems (requires a reference SAP system to connect to for IDoc metadata) Available transactions in backend systems: Maintain ports in the IDoc adapter (IDX1) Load, display, and delete metadata (IDX2) Display IDoc XML messages (IDX5) Reporting transactions Configuration via channel and sender/receiver agreement in Integration Directory Supported IDoc Adapter (AAE) SAP NetWeaver 7.3

Supported IDoc segment versions Supported releases/versions of the integrated software

As of 3.1x, IDoc metadata can be retrieved SAP applications based on releases including SAP Basis 4.0 and higher

Tool integration

Administration via Runtime Workbench Integrated with RFC destinations in SAP NetWeaver Administrator Configuration via channel and integrated configuration in Integration Directory

Automatic generation of adapter (Integration Directory)

Not supported

Communication, Connectivity, Security Settings Attribut/Feature Supported data transfer languages IDoc Adapter (IE) IDoc Adapter (AAE) Supports the exchange of IDocs with SAP applications running in any single codepage, or in Unicode mode.

(codepages of connected systems, Unicode, etc.) Quality of service Communication with systems with multiple code pages (Multi Display/Multi Processing - MDMP) systems Communication with JCObased IDoc senders and receivers Connection setting modes

EO, EOIO with qRFC 1) Supported for IDoc inbound processing (sender adapter)

EO, EOIO 2) Not supported

Supported

Not supported

Connection configuration via RFC destination (transaction SM59)

Security Partner conversion IDoc Packaging 4)

Segment data change/reduction Automatic segment data reduction

Basic authentication Transport level security Supported Supported (as of EHP 1 for SAP NetWeaver PI 7.1) Not supported Supported (not relevant segments that were added in later releases are filtered out automatically) Not supported

Connection configuration via RFC destination in SAP NetWeaver Administrator and via destination (transaction SM59; connection type = T) Basic authentication 3) Supported. Supported (but not at outbound side) Not supported Not supported

Enhancement by adapter modules

Supported

Auditing, Monitoring ,and Tracing Functions Attribut/Feature ALE Audit IDoc Adapter (IE) IDoc Adapter (AAE) Supported Acknowledgment handling (XI message to ALEAUD and vice versa) is supported. Supported 5) Not supported (transaction IDX5) Transaction IDX5 Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor) Not supported

IDoc tracing IDoc monitoring

Status tracking SYSTAT

(analysis and further processing of messages that have not been processed) RFC monitoring Message persistence in the IDoc adapter

Supported Supported 6)

Not supported Not supported. Message is persisted in messaging system with correlation data persisted in adapter.

Comments 1) For more information in EOIO behavior and serialization concept for IDoc adapter (IE), see Serializing IDocs. 2) Not supported: Best Effort, qRFC and function module IDOC_INBOUND_IN_QUEUE 3) Not supported: Security on transport level, principal propagation 4) IDoc packaging: see figure below 5) IDoc tracing for IDoc inbound processing is supported by a tracing API on the Integration Server. IDoc tracing for IDoc outbound processing is supported by transaction IDX5 on the Integration Server (in conjunction with tracing API on in receiver system). 6) Message correlation information can be stored in IDoc adapter. IDoc Packaging The IDoc adapters support IDoc packaging as illustrated in the following figures.
IDoc Inbound Packaging
IDoc/RFC XML

A1 A2 A3 An

A1 A2 A3 An

Supported by IDoc adapter (IE) IDoc adapter (AAE)

A1 A1 A2 A3 An An A2 A3

Supported by IDoc adapter (IE) IDoc adapter (AAE)

IDoc Outbound Packaging

XML IDoc/RFC

A1 A2 A3 An

A1 A2 A3 An

Supported by IDoc adapter (IE) IDoc adapter (AAE)

A1 A2 A3 A1 A2 A3 An An

Supported by IDoc adapter (IE)