adapter engine

[Former Member]

hi xi experts,

can u explan me the difference between centrialized and local adapter engine and where both are located.

[Former Member]

Hi vijaya,

thats a very good question.

actually when INTEGRATION SERVER is installed centrel adapter engine is installed automaticaly.

optionaly u can install several decentrelized AE.

the local/decentrelized AE needs its own instance of J2EE engine

the local/decentrelized can be located in any remote host and also any remote host can have multiple local AE installed in it.

Generally the advantage of using local AE is to

1)avoid single pont of failure

2)distribute the load of adapters

3)OS dependency

Hope you r very clear now.

Regards

Biplab

[Former Member]

hi,

You can run the non-central Adapter Engine in Java proxy mode. Registration of the adapters in the SLD is deactivated in this mode. The collaboration profile agreement service (CPA service) does not read the CPA cache from the Integration Directory.

The Adapter Engine is a separate software component that is automatically installed on the Integration Server. In this case, it is the central Adapter Engine.

check the links..

[http://help.sap.com/saphelp_nw04/helpdata/en/45/1918d2636d6c1ae10000000a1553f6/content.htm]

[http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm]

Regards,

Prakasu

[former_member556603]

Hello Vijaya,

Adapter Engine

Purpose

You use the Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and external 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.

Implementation Considerations

The Adapter Engine is based on the adapter framework.

More information: Adapter Framework

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

Integration

You configure the adapters in the configuration part of the Integration Builder. 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 each adapter in the module processor to equip the adapter with additional functions. For more information about creating your own modules and adapters, see Adapter and Module Development.

Features

The Adapter Engine provides adapters, which you use to do the following, depending on their configuration:

● Communicate with SAP systems using the RFC interface (RFC adapter)

● Enable data exchange with the SAP Business Connector (SAP Business Connector adapter)

● Exchange data with external systems using a file interface or an FTP server (file/FTP adapter).

● Access databases using JDBC (JDBC adapter).

● Communicate with messaging systems using the JMS API (JMS adapter).

● Integrate remote clients or Web Service providers using the SOAP adapter (SOAP adapter)

● Connect marketplaces to the Integration Engine (Marketplace Adapter).

● Connect e-mail servers to the Integration Engine (Mail adapter).

● Communicate with systems that support the RosettaNet standard (RNIF adapter, RNIF 1.1 and RNIF 2.0).

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

Acknowledgments

Receiver adapters support system acknowledgments if they are requested by the sender. They are triggered if the message is processed successfully by the adapter. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters do not request any acknowledgments.

For more information about acknowledgments, see Processing Acknowledgment Messages.

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.

For more information, see SAP Service Marketplace at service.sap.com/instguidesnw04, Installation, SAP XI ® Configuration Guide - SAP XI 3.0.

All services and service parameters are listed and explained in the appendix of the guide.

The parameters for queue settings for each adapter types are under SAP XI AF Core.

EOIO Processing

More information: Changing Exactly Once in Order Processing in the Adapter Engine

Archive Messages

You can archive messages in the Adapter Engine.

You make the following entries:

● In Web AS Java

For more information about archiving XML messages, see XML Data Archiving - Configuration Guide for J2EE Applications on SAP Service Marketplace at service.sap.com/instguidesNW04 → SAP NetWeaver → Installation → SAP WebAS → SAP WebAS 6.40.

More information: Administration of the XML Data Archiving Service

● In the Adapter Engine

For more information, see SAP Service Marketplace at service.sap.com/instguidesnw04, Installation, SAP XI ® Configuration Guide - SAP XI 3.0, under Configuring Message Archiving for the Adapter Engine and the PCK.

● In the Runtime Workbench

More information: Background Processing ® Archiving.

Delete Messages

You can only delete messages in the 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 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

Thanks,

Satya Kumar

Reward if it is usefull