Advanced Adapter Engine Local Message Processing: Bypassing the

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 1

Advanced Adapter Engine Local

Message Processing: Bypassing

the Integration Engine

Applies to:

SAP NetWeaver Process Integration 7.1 (SAP PI 7.1)

Summary

This article subscribe to local message processing in the Advanced Adapter Engine (AAE), bypassing the Integration Engine (ABAP stack of the Integration Server), using Integrated Configurations.

Author: Amarpreet Singh

Company: Infosys Technologies Ltd

Created on: 6 November 2009


© 2009 SAP AG 2

Table of Contents

Introduction……………………………………………………………………………………………………………….3

Introduction ......................................................................................................................................................... 3

Fundamentals ................................................................................................................................................. 3 Real Time Example: Step-by-Step Procedure ............................................................................................................. 7

Disclaimer and Liability Notice .......................................................................................................................... 15


© 2009 SAP AG 3

Introduction

Primarily the objective of using the local processing in the AAE is to improve the performance of the message processing by eliminating the need for the ABAP stack. By doing this, we can still keep the existing monitoring and support functionalities.

We make Integration Configurations instead of the Configuration Scenarios that are generally made. By doing this, the number of hits to the IS are reduced and the performance improved by around 4 times.

The restrictions of doing this are:

Since the ABAP stack is not used, the functionalities provided by the ABAP stack are not available.

Mainly the following are not used here:

Adapters: IDoc, HTTP

Mapping: ABAP, ccBPM

Proxies

Multi-mapping and message splits are also not included. Design time usage of the Enterprise Service Repository and the configuration use of the Integration Directory is the same as before.

Also available are the usages of the Runtime Workbench, message mapping using XSLT and java mapping.

Fundamentals

The AAE local message processing provides all the features of the message processing done using the Integration Engine but here only one Persistence step is done, against 4 in the latter scenario. So the performance is improved manifolds.

Fig 1: Scenarios using IS and AAE message processing


© 2009 SAP AG 4

Now we shall see how the local processing is simpler/ lighter:

Fig 2: Local processing vs. Processing via IS


© 2009 SAP AG 5

As we can see that the Integration Server step is missed out, leading to a 3 fold improvement, basically three steps, persistence, Transfer and parsing are skipped. Also skipped is the routing step, basically because the Integration Configuration object contains all the steps inside itself. This would be discussed a bit later. As we can see, three persistence steps are missed in the local processing, hence improving the performance.

Fig 3: Local processing in the AAE

The architecture of the local processing is:

1. Provides mapping, routing by-passing the Integration Server.

2. The communication is Adapter to Adapter.

3. Can be used for both Sync and async scenarios.

4. The AAE provides routing and mapping services locally.


© 2009 SAP AG 6

Further features include:

1. Sender and receiver adapters located on the same Adapter Engine

2. Support of decentral Adapter Engine with central configuration and monitoring.

3. Available for adapter types hosted on the Adapter Engine.

4. One to one message mapping

5. Single Static Routing

6. ACL‘s

7. Mapping Lookups

8. Principal Propagation (if supported by the adapter)

9. Value Mapping, Sequence Mapping

10. Schema Validation

11. Header Mapping (if supported by the adapter)

12. Message Prioritization

The missing features are:

1. Adapters not supported:

IDoc

http

XI

2. iSpeak

3. No ABAP based mapping types

4. No content based routing or message split supported.

To Summarize, the Integration Configuration Object contains:

1. Contains sender-& receiver agreement and interface determination

2. Is transferred to the CPA-Cache of the individual AAE with a reference to the mapping maintained within the interface determination section

3. For each operation in interface determination a separate entry is created in CPA (receiver interface determination)

4. The integrated configuration object is transferred as one single object to the AAE.


© 2009 SAP AG 7

Real Time Example: Step-by-Step Procedure

The Enterprise Service (ES) Repository will continue to be used to design the interfaces and mappings. The design steps are the same as used in the Configuration Scenarios.

In the Integration Directory, a new configuration tool is introduced, namely Integrated Configurations. The Integrated Configurations tool can only be used for configuration of local processing using the Advanced Adapter Engine; it cannot be used for messaging going through the Integration Server. This single tool combines the configurations of Receiver Determination, Interface Determination, Sender Agreement, and Receiver Agreement. The Sender Communication Channel and Receiver Communication Channel will still need to be configured separately.

To make an Integrated Configuration Object, we shall follow the following steps:

1. Create Sender Communication Channel

a. Create the SOAP Sender Communication Channel. Right-click on the Communication Channel, and select New.

Fig 4: Creating Sender Communication Channel


© 2009 SAP AG 8

b. Provide all the configuration parameters for the SOAP Sender Communication Channel. When complete, save the configuration.

Fig 5: Providing all Configurations for Sender Communication Channel


© 2009 SAP AG 9

2. Create Sender Communication Channel

a. Create the RFC Receiver Communication Channel. Right-click on the Communication Channel of a Business Component or Business System, and select New.

Fig 6: Creating RFC Receiver Communication Channel


© 2009 SAP AG 10

b. Provide all the configuration parameters for the RFC Receiver Communication Channel. When complete, save the configuration.

Fig 7: Providing all Configurations for Receiver Communication Channel


© 2009 SAP AG 11

3. Create Integrated Configuration

a. Create the Integrated Configurations. Right-click on the Integrated Configurations, and select New.

Fig 8: Creating Integrated Configuration Object


© 2009 SAP AG 12

b. With the Integrated Configurations, all the information required for the message processing can be entered within this one tool. In the first tab, Inbound Processing, the Sender Communication Channel must be entered. In this case, it is CC_SOAP_Sender_XXXX that we created beforehand.

Fig 9: Inbound Processing in ICO


© 2009 SAP AG 13

c. In the second tab, Receiver Interfaces, we must enter the Receiver Communication Component, the Receiver Interface, and, optionally, the Operations Mapping.

Fig 10: Receiver Interfaces in the ICO


© 2009 SAP AG 14

d. In the third tab, Outbound Processing, we must enter the Receiver Communication Channel which we created beforehand. Save and activate all the configurations.

Fig 11: Outbound processing in ICO


© 2009 SAP AG 15

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Advanced Adapter Engine Local Message Processing: Bypassing the

Documents

Transcript of Advanced Adapter Engine Local Message Processing: Bypassing the