Show TOC

Procedure documentationProcessing Messages with the Advanced Adapter Engine Locate this document in the navigation structure

 

You use the Advanced Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and non-SAP systems. You use the various adapters in the Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.

Local Message Processing with the Advanced Adapter Engine

Using Integrated Configuration 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.

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

For more information, see Execute integrated configuration

If you do not use Integrated Configuration, Message Processing will always be performed by the Integration Engine to execute the routing and mapping there.

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.

Note Note

For Frequently Asked Questions (FAQs) about adapters of the Advanced Adapter Engine and references to the FAQs for each of the individual adapters, see SAP Note 821268.

End of the note.

Procedure

  • Configure the adapter in the Integration Directory.

    For more information, see Defining the Communication Profile, Defining the Communication Channel

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

      For more information, see RFC adapter

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

      For more information, see SAP Business Connector adapter

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

      For more information, see File/FTP Adapter

    • With the JDBC adapter you can access databases using JDBC.

      For more information, see JDBC Adapter

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

      For more information, see JMS adapter

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

      You can integrate the Axis framework into the SOAP adapter.

      For more information, see SOAP Adapter, Axis Framework in SOAP Adapter.

    • The Marketplace adapter connects marketplaces to the Integration Engine.

      For more information, see Marketplace adapter

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

      For more information, see Mail Adapter

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

      For more information, see RNIF Adapter

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

      For more information, see CIDX Adapter

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

    For more information, see Defining Modules in the Module Processor

  • For more information about creating your own modules and adapters, see Developing Adapters and Modules

  • In the 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 NetWeaver Administrator for a queue separation.

    For more information, see Properties for Service XPI: AF Core

  • You can archive messages in the Advanced Adapter Engine.

    You make the following entries:

  • You can only delete messages in the Advanced Adapter Engine if they have the status FAILED or DELIVERED.

    To do this, you make specifications in the Runtime Workbench.

    For more information, see Background Processing

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

    You can determine the number of attempts made to resend 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 Communication Channel Monitor

  • You can find information on employing the non-central Adapter Engine in Java proxy mode under: Using the Non-Central Adapter Engine in Java Proxy Mode.

More Information

The Advanced Adapter Engine is based on the Adapter Framework.

For more information, see Adapter Framework

You can use the Adapter Engine (Java SE) on platforms on which the AS Java is not supported, but where there is a Java Runtime 5.0 or higher.

For more information, see Working with the Adapter Engine (Java SE)

For more information on supporting acknowledgments in the Advanced Adapter Engine, see: Acknowledgment Support in the Adapter Engine.