Show TOC

Connecting Advanced Adapter Engine Extended to an Integration ServerLocate this document in the navigation structure

Use

There are certain use cases where it is suitable to connect an Advanced Adapter Engine Extended (AEX) with a landscape based on an SAP NetWeaver PI dual-stack installation.

More information: Advanced Adapter Engine Extended

The basic communication is illustrated in the following figure:

Figure 1: Connecting an AEX with SAP NetWeaver PI

The figure shows an example that uses AEX in both modes: In combination with another SAP NetWeaver PI system (communication path 1) and standalone (communication path 2).

Example

Assume a situation that a global acting enterprise operates all communication to regional subsidiaries in standalone mode, whereas for all global communications an additional landscape based on an SAP NetWeaver PI standard installation is interconnected (because the latter provides the complete range of mediation and security capabilities of SAP NetWeaver PI).

Procedure

The end-to-end procedure to set up and run a scenario depends on the details of the integration scenario, the system landscape the scenario is deployed on, as well as on the particular choice of routing, connectivity and security settings.

You also have to take into consideration if the complete system landscape is owned by the same organization or if - as typically the case in business-to-business (B2B) scenarios - if different parts of the overall system landscape are owned and maintained by different business partners or organizations.

We show the basic steps to set up the following communication path: a sender system sends a message to the AEX. The message is then forwarded to the Integration Server of an SAP NetWeaver PI landscape. The Integration Server processes the message and sends it to a receiver system. This communication is illustrated in the figure above (communication path 1). For sake of completeness, the figure also shows a communication path where a message is forwarded by the AEX directly to the receiver. This communication (communication path 2 in figure above) is handled under Developing and Configuring Integration Scenarios (Using AEX Stand-Alone) .

Note

We can assume that in real-life scenarios both kinds of communication will be used in cooperation.

However, in this section we only show the basic steps to set up communication path 1. We assume that SAP NetWeaver PI and the AEX are installed on different hosts.

Tasks on the Side of the AEX Installation

In general, you proceed as described under Developing and Configuring Integration Scenarios (Using AEX Stand-Alone) . To set up the particular use case covered in this section, take note of the following characteristics:

When you specify the message flow in the Integration Directory, you describe the message flow from the sender system to the Integration Server.

When you define the integrated configuration, you therefore need to specify the following basic settings:

  • To configure inbound processing (direction from the sender system to the AEX), you need to assign a sender adapter according to the protocol or standard that is used by the sender.

  • To configure outbound processing (direction from the AEX to the Integration Server), you need to assign a receiver SOAP adapter . As Message Protocol , choose XI 3.0.

  • Under Connection Parameters , enter the URL of the Integration Server.

    Recommendation

    To determine the URL of the Integration Server, you can do the following: configure inbound processing on the side of the SAP NetWeaver PI installation. To do that, you define a sender agreement. Display the WSDL of the sender agreement. The WSDL contains the URL of the Integration Server. Note that in case AEX and SAP NetWeaver PI standard installation are hosted by different business partners (as the case in a B2B scenario), the URL has to be communicated by other means (for example, email).

Tasks on the Side of the SAP NetWeaver PI Installation

In general, you proceed as described under Developing and Configuring Integration Scenarios (Using the Integration Engine) or Developing and Configuring Integration Scenarios (Using AAE Locally) (depending on the chosen connectivity option). To set up the particular use case covered in this section, take note of the following characteristics:

  1. In the ES Repository you define the process integration scenario and the involved interface and mapping objects.

  2. In the System Landscape Directory you describe the relevant part of the system landscape.

  3. In the Integration Directory, you describe the message flow from the AEX to the receiver system.