Start of Content Area

Function documentation Adapter Configuration in the Integration Builder  Locate the document in its SAP Library structure

Use

Adapters are configured in the communication channel of the Integration Directory.

You use the Enterprise Services Repository at design time to define message types, interfaces, and mappings.

This is where the adapter metadata and communication channel templates are stored as adapter objects.

      Adapter metadata contains the adapter-specific configuration data.

      You create communication channel templates in customer projects to simplify adapter configuration.

More information: Adapter Metadata, Communication Channel Templates, Adapter Objects

The system administrator uses the Integration Directory at configuration time. This is where the administrator configures the adapter.

You must create the following objects to configure an adapter:

      Communication Party

      Communication Component

      Communication channel

      Collaboration agreement

Prerequisites

The adapter that you develop for the Adapter Framework must fulfill the following criteria:

      An Adapter-Framework-compliant JCA adapter must implement the Adapter Framework configuration CPA API.

      The adapter must not contain configuration information outside the Integration Directory.

The only exceptions are default values or values that must be known in the deployment descriptor of the JCA Resource Adapter at deploy time SAP NetWeaver Administrator (NWA).

       Start SAP NetWeaver Administrator.

       Choose Configuration Management Infrastructure Management and Application Resources->Show all: All Resource Adapter.

       Choose com.sap.aii.adapter.sample.ra.

       Choose Properties.

      The adapter must have a metadata schema.

It must be defined exactly for this adapter type.

      The adapter implementation must guarantee the consistency of the message addresses and the communication channels used.

You must not import address information in the communication channel that does not correspond to the address information in the collaboration agreement.

Depending on the adapter type you can use either getBindingByChannelId(channelId) or InboundRuntimeLookup.

      If addresses have to be converted to external protocols or IDoc scenarios must be supported, you must support header mapping and address normalization in the adapter.

You must not save the corresponding settings in the communication channel.

More information: Converting Addresses Using Header Mapping and Normalization

 

End of Content Area