Advanced Adapter Engine 

Purpose

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.

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.

More information: Performing 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.

Implementation Considerations

The Advanced Adapter Engine is based on the Adapter Framework.

More information: Adapter Framework

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.

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.

Integration

You configure the Adapter in the Integration Directory. You define the parameters of the respective adapter during the definition of collaboration profiles in the communication channel.

It is possible to define generic modules for most adapters in the module processor to equip the adapter with additional functions.

More information: Defining Communication Profile, Defining Communication Channel, Defining Modules in Module Processor.

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

The Adapter Engine (Java SE) is still available: Working with the Adapter Engine (Java SE)

Features

The Advanced Adapter Engine provides the following adapters:

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

More information: RFC Adapter.

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

More information: SAP Business Connector Adapter.

●      The file/FTP adapter can exchange data with external systems using a file interface or an FTP server.

More information: File/FTP Adapter.

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

More information: JDBC Adapter.

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

More information: 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.

More information: SOAP Adapter, Axis Framework in SOAP Adapter.

●      The Marketplace adapter connects marketplaces to the Integration Engine.

More information: Marketplace Adapter

●      The Mail adapter establishes the connection to e-mail servers.

More information: Mail Adapter

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

More information: RNIF Adapter.

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

More information: CDIX Adapter.

Acknowledgments

More information: Acknowledgment Support in the Adapter Engine

Activities

Queue Separation for Receiver Channels

In the Adapter Engine there is a queue for each connection and adapter type in the receiver direction.

You can adapt the parameters for these queues in the Visual Administrator.

More information: Properties for Service PI AF Core

Archiving Messages

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.

More information: Administration of the XML Data Archiving Service

●      In the Advanced Adapter Engine

More information: Configuring Message Archiving for the Adapter Engine.

●      In the Runtime Workbench

More information:  Archiving in Background Processing.

Delete Messages

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.

More information: Background Processing

Resending Messages in Receiver Channels

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

Using the Non-Central Adapter Engine in Java Proxy Mode

More information: Using the Non-Central Adapter Engine in Java-Proxy Mode