Advanced Adapter Engine

Use in a Dual-Stack Installation of SAP NetWeaver PI

When you use the dual-stack installation option of SAP NetWeaver PI, you have the following options to configure the Advanced Adapter Engine for message exchange purposes:

Local Message Processing with the Advanced Adapter Engine

Using integrated configuration (in Integration Directory) you can define a local message processing on the Advanced Adapter Engine. The Advanced Adapter Engine provides mapping and routing for this locally. Message processing is only executed on the Advanced Adapter Engine from one adapter to another without the involvement of the Integration Engine. You can gain a great improvement in performance, because technically only the AS Java is involved.

You can implement all adapters on the Advanced Adapter Engine for a local Message Processing on the Advanced Adapter Engine, apart from the RNIF adapters and the CIDX adapters.

If you do not use the integrated configuration, message processing will continue to be controlled using the Integration Engine.

Central and Non-Central Advanced Adapter Engines

The Advanced Adapter Engine is a separate software component that is automatically installed on the Integration Server. In this case, it is the central Advanced Adapter Engine. However, you can also install the Advanced Adapter Engine separately on another host. This is then a non-central Advanced Adapter Engine.

Use with the Advanced Adapter Engine Extended

No Integration Engine is installed for this installation option, instead the Advanced Adapter Engine is provided as the runtime environment for message processing only.

Configuring Adapters of the Advanced Adapter Engine

To configure the adapters, you use communication channels in the Integration Directory. For more information on communication channels and other relevant configuration objects in the Integration Directory, see the Integration Directory documentation (SAP NetWeaver Library under  Function-Oriented View   Process Integration )

The sections referred to below contain detailed, adapter type-specific information on configuration.

More information:

• Configuring the RFC Adapter

  With the RFC adapter you can communicate with SAP systems using the RFC interface.

• Configuring the IDoc Adapter (Advanced Adapter Engine)

  With the IDoc Adapter (AAE) you can have IDocs processed by the Integration Engine and the Advanced Adapter Engine.

• Configuring the SOAP Adapter

  With the SOAP adapter you can integrate remote clients of Web services providers.

  You can integrate the Axis framework into the SOAP adapter.

• Configuring the Java HTTP Adapter

  With the HTTP Adapter (AAE) you can connect third-party system using the native HTTP interface (HTTP payload without SOAP envelope).

• Configuring the File/FTP Adapter

  With the File/FTP adapter you can exchange data with external systems using a file interface or an FTP server.

• Configuring the JDBC Adapter

  With the JDBC adapter you can access databases using JDBC.

• Configuring the JMS Adapter

  With the JMS adapter you can communicate with messaging systems using the JMS API.

• Configuring the Mail Adapter

  The Mail Adapter establishes the connection to e-mail servers.

• Configuring the Marketplace Adapter

  The Marketplace adapter supports the connection with marketplaces.

• Configuring the SAP BC Adapter

  The SAP Business Connector adapter (SAP BC Adapter) facilitates the exchange of data with the SAP Business Connector.

• Configuring the CIDX Adapter

  The CIDX adapter supports Chem eStandards, an open standard for business-to-business data exchange in the chemical industry.

• Configuring the RNIF Adapter

  Using the RNIF adapter (1.1 and 2.0) you communicate with systems that support the RosettaNet standard.

Additional Information

• To equip the adapter with additional functions, you can define generic modules for the majority of adapters in the module processor.

• In the Advanced Adapter Engine there is a queue for each connection and adapter type in the receiver direction. You can adapt the parameters for this queue in SAP NetWeaver Administrator for a queue separation.

  For more information on this, see the documentation for the technical configuration of SAP NetWeaver PI ( Configuring Process Integration (PI) After Installation ) under  Integration of Business Systems without Integration Engine  Integration Using the Advanced Adapter Engine   Java Service Properties for the Adapter Framework .

• You can archive messages in the Advanced Adapter Engine.

  You make the following entries:

  • In AS Java

    For more information about archiving XML messages, see SAP Service Marketplace.

    For more information, see Administration of the XML Data Archiving Service

  • In the Advanced Adapter Engine

    For more information, see More information: Configuring Message Archiving for the Adapter Engine .

• If a receiver system is not available, the Advanced Adapter Engine tries to re-send the messages.

  You can determine the number of attempts made to re-send and the intervals between retries for each receiver channel individually in the communication channel monitor.

  The default values are taken from the parameters xiadapter.outbound.numberRetries.default and xiadapter.outbound.retryInterval.default of service SAP XI Adapter: XI .

  For more information, see Monitoring Communication Channels

• For more information on implementing the non-central Adapter Engine in the Java proxy mode, see: Using the Non-Central Adapter Engine in Java Proxy Mode

• Configure the saving procedure for asynchronous message versions in SAP NetWeaver Administrator.

  For more information: Saving Message Versions in the Advanced Adapter Engine