Show TOC

Procedure documentationSetting Up Scenarios Using Local AAE-Based Message Processing Locate this document in the navigation structure

 

When using an SAP NetWeaver PI dual-stack installation, you can set up scenarios in such a way that communication between the sender and receiver system is performed locally by the central Advanced Adapter Engine (AAE) without involving the Integration Engine. Technically, at runtime only AS Java is involved.

Recommendation Recommendation

Although the Integration Engine and Advanced Adapter Engine are installed on the same Integration Server, the Integration Engine is not involved in this type of message processing. This means you can usually achieve a higher level of performance than if the Integration Engine were involved.

End of the recommendation.

Caution Caution

Note the following restrictions for design time, compared to a full installation of SAP NetWeaver PI:

  • You can only use process integration scenarios for process modeling.

  • You cannot use integration processes (ccBPM).

  • The following adapter types are not supported: IDoc (ABAP-based), XI, HTTP (ABAP-based), WS-RM.

End of the caution.

More information: SAP NetWeaver PI Dual-Stack Installation (under Local Message Processing Using the AAE)

Procedure

1. Design Integration Content

You design the integration content in the same way as described under Setting up Scenarios Using Dual-Stack Message Processing (see section 1. Designing Integration Content).

2. Configure Integration Content

At configuration time you specify how messages have to be exchanged between the individual systems or applications of the existing system landscape – in accordance with the process model and additional integration content specified at design time.

More information about the basic concepts: Configuration Time

Key tools for this phase are the System Landscape Directory and the Integration Directory.

Caution Caution

Note that for the configuration of AAE-based message processing you can only use process integration scenarios as configuration template.

End of the caution.
Defining Collaboration Profile

This task involves the definition of communication components, communication channels and (optional) communication parties.

More information: Defining Collaboration Profile

Caution Caution

For the communication channel, you can only use adapter types that run on the AAE.

More information: Configuring Adapters under Configuring Adapters of the Advanced Adapter Engine

End of the caution.
Configuring Message Exchange

This task involves the configuration of the inbound processing, routing, mapping and outbound processing (phases of message processing).

  1. Log on to the Integration Directory.

  2. Create an integrated configuration and specify the corresponding attributes for each of the phases of message processing.

    More information: Defining the Integrated Configuration

    Recommendation Recommendation

    As far as you have defined a process integration scenario at design time, you can use the model configurator to specify the message exchange.

    More information: Configuring Process Integration Scenarios

    End of the recommendation.

  3. Activate the configuration objects.