Show TOC

Using Advanced Adapter Engine Extended Stand-AloneLocate this document in the navigation structure

Use

This is the basic communication flow when using Advanced Adapter Engine Extended (AEX) stand-alone:

Figure 1: Basic Communication Flow When Using AEX Stand-Alone

More information: Advanced Adapter Engine Extended

In this section, you will find information on how to set up this kind of communication.

Procedure

1. Design Integration Content

You define the software components for your development project in the System Landscape Directory (SLD). You design your integration content in the ES Repository.

In this section, we describe the general procedure when you follow the top-down design approach, which means that you start with a process model and based on the model specify all other integration content.

More information about the basic concepts: Design Time

Note

There is the option either to design the integration yourself from scratch or to use integration details already designed and delivered by SAP where you can modify this content according to your needs. We will go into the aspects of both approaches in this chapter.

Both of these approaches normally come into play in real-life projects. A typical scenario would, for example, be that you use predefined content (and enhance it) to outline one part of the integration scenario, whereas another part has to be built completely from scratch. For the specific aspects that you have to consider when using predefined content shipped by SAP, see Using Predefined Integration Content .

  1. Define the software components you need for your developments.

    Note

    You need these entities in order to organize the ESR content (interfaces, mappings, for example) you define with the following steps.

    More information: Organizing and Managing Content in ESR

  2. Log in to the ES Repository and choose the usage profile Advanced Adapter Engine Extended.

    More information: Usage Profile

  3. Define a process integration scenario for your overall process.

    More information: Defining Process Integration Scenarios

  4. Define the necessary interface objects.

    More information: Defining Interface Objects

  5. Define the necessary mapping objects.

    More information: Defining Mappings

  6. Activate your ESR objects.

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.

Note

As compared to an SAP NetWeaver PI standard installation, the user interface of the Integration Directory for the AEX provides only access to the following configuration object types:

  • Communication party

  • Communication component without party

    Caution

    Integration process components (communication components based on integration processes from the ES Repository) cannot be created.

  • Integrated configuration

  • Configuration scenario

  • Value mapping group

Recommendation

We recommend that you use a process integration scenario from the ES Repository as configuration template. Doing this, you can configure inbound processing, routing, mapping and outbound processing semi-automatically.

More information: Configuring Process Integration Scenarios

Caution

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

Defining Collaboration Profile

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

More information: Defining Collaboration Profile

Caution

For the communication channel, you can only specify one of the adapter types listed under Advanced Adapter Engine Extended .

Configuring Message Exchange

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

  1. Logon 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

    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

  3. Activate the configuration objects.