SAP PI 7.1Advanced Adapter Engine

--- Chandra Shekhar Yella

Agenda

• Introduction to AAE

• Message flow in AAE

• Overview of Advanced Adapter Engine Extended• Overview of Advanced Adapter Engine Extended

• Sample IDoc to File scenario using AEX feature

• Summary

Introduction

• AAE is an evolution to AE and it is part of SAP Netweaver PI 7.1. There is no additional installation/ deployment is required to use the functionality of AAE. It is just upto the configuration

• Main feature of AAE is to support high volume data.

• The AAE enables for end to end message processing without the help of IE during runtime and also support the classical message processing using the ISruntime and also support the classical message processing using the IS

• Increase message processing speed and reducing resource consumption (both memory and processing time)

• Local processing with AAE, Integration Engine is not involved during the runtime (mapping and routing is carried within the AAE)

Message Flow Before & After AAE• Runtime Picture: Before AAE

• Runtime Picture: After AAE

AE (Classical) Processing vs. AAE (Local) Processing

Feature of AAE

• Supports both Synch and Async scenarios

• Sender and Receiver adapter are located in same AE i.e. Adapter to adapter communication.

• Available for all the adapters available in AE i.e. IDoc, HTTP and XI adapter are excludedin AE i.e. IDoc, HTTP and XI adapter are excluded

• Provide mapping, routing to by-pass IS

• ABAP mapping is not supported.

• ccBPM and Proxy not supported

• Single static routing (i.e no content based routing or msg split yet) [initial release of PI 7.1]

Configuring the AAE in the ID with the Integrated Configuration Object (ICO)

• Used for configuring the local processing within AAE. AAE provides routing and mapping services locally.

Basic Routing and Mapping

• At configuration time, instead of creating SA, RD, ID and RA you can create Integrated Configuration object

• Just one receiver, therefore RD is combined into the ID

• The ICO is used for local processing within the AAE only.

• ICO divides in 3 tab strips– Inbound Processing (Corresponds – Inbound Processing (Corresponds

to Sender Agreement)– Receiver Interface (Receiver

Determination and Interface mapping)

– Outbound Processing (Receiver Agreement)

• Once activated ICO objects are replicated to the AAEs local cache. That means all the routing and mapping are executed locally

Content Based Routing and Enhanced Receiver Determination for ICO (EhP1)

Integrated Configuration Object

• ICO Contains Receiver determination, Interface Determination, Sender Agreement • ICO Contains Receiver determination, Interface Determination, Sender Agreement and Receiver Agreement.

• The Integrated Configuration Object is transferred as one single object to the AAE.

• Each operation the Interface Determination, a separate entry is created in CPA

• Communication channel is not part of ICO.

AAE Message Flow

Message Prioritization within AAE

• Rules within component monitoring with 3 diff categories (high, low and normal) per • Rules within component monitoring with 3 diff categories (high, low and normal) per Sender/ Receiver Party/ component, interface, namespace.

• Corresponding to properties “messaging.prioritization.high”, “messaging.prioritization.low”, “messaging.prioritization.normal”

• All QOS supported

• Prioritization during runtime take place in principle, whenever for a given adapter type and at a given moment of time all worker threads are occupied

Advance Adapter Engine Extended (AEX)Extended (AEX)

AAE Evolution

• Fully independent, single stack solution based on SAP NW AS Java only

– Own integration domain– Own tools for design,

configuration and operations-- (ES Repository, ID, SLD, NWA,

monitoring)

• Powered by AAE introduced in 7.1

• Additional mediation and connectivity features to allow for major scenario shift to AEX

• Further support of Adapters– IDoc adapter in AAE– HTTP adapter in AAE

• Large (binary) file-to-file transfer

AEX Features

– Close gaps to enable major scenario shifts from dual-stack PI to AAE– Further support of adapters

• IDOC adapter in AAE• HTTP adapter in AAE

– Interface and mapping split on AAE– Optional message versions (on error / before routing / after mapping /

validation …)validation …)– User defined message search (replacing TREX)– XML Validation redesign (ESR schema based)– Fault Tolerance Improvement

• OutOfMemoryHandling• Safe Restart for huge message backlogs• Reduction of cluster communication (locking), e.g. EOIO message

sticking to cluster nodes• CPA Cache, Monitoring improvements

Benefits

– Reduction in overall TCO with single-stack• Faster installation (1 hr)*• Less hardware (½ hardware requirement)*• Fast restart (90 secs)*

– * Hardware dependent

– Drastically reduced resource consumption (scenarios can speed up to a factor 10)10)

• Conversely, need only 10% of resources for comparable performance, sizing cut down by factors

• Up to 60% less energy consumption

– Monitoring simplification with one dedicated toolset and one stack• All end-to-end monitoring and configuration information

– One database scheme

Sample IDoc To File scenario using AEX feature

• Multi Mapping scenario, Configuring the scenario for AAE and IDoc as sender CC

IDoc to File using IDoc to File using AEX

Summary (AAE)• The primary objective of using local processing in the AAE is to increase the

performance of message processing by eliminating the need for the ABAP stack during the process.

• By using the Integrated Configuration, we anticipate a 4 times improvement in performance

• ABAP stack no longer participates in the processing of messages, therefore, any functionality provided by ABAP will not be available when the Integrated Configurations

• Customers require high-volume throughput and AAE is designed to provide the same.

• AAE allows end-to-end message processing w/o invoking central ABAP-based pipeline of Integration Server.

• The Integrated Configurations tool can only be used for configuration of local processing using the Advanced Adapter Engine

• Following will not be available when using local processing in the AAE:Adapters: IDoc, HTTPMapping: ABAPccBPM

Summary

• Local processing comes with AAE by natural evolution of AE. Usage of local processing & Integrated Configuration Object is optional and processing via Integration Server is still another option.

• Supports both central & de-central configuration.

• Provides mapping, routing functionalities to by-pass IE & improves performance on IS.IS.

• Improved performance/message turnaround for adapter-to-adapter communication.

• Allows customers to distribute execution of mission-critical processes. (Message prioritization).

Thank YouThank You