Adapter Configuration in the Integration Builder 

Use

You configure adapters in the communication channel of the Integration Builder.

The Integration Builder comprises the Integration Repository and the Integration Directory. You use the Integration Repository at design time to define message types, interfaces, mappings, and so on. The adapter metadata and communication channel templates are saved here as adapter objects.

·        Adapter metadata contains the adapter-specific configuration data.

·        Communication channel templates are usually created in customer projects. They simplify adapter configuration.

The system administrator uses the Integration Directory at configuration time. Among other things, you configure the adapters here.

You must create the following objects to configure an adapter:

·        Communication party

·        Service

·        Communication channel

Prerequisites

An adapter that is developed for use in the Adapter Framework must fulfill the following prerequisites:

·         The JCA adapter must implement the Adapter Framework configuration CPA API.

·         The JCA adapter must not contain configuration information outside the Integration Directory. The only exception to this rule is the default settings or values that must be known in the deployment descriptor of the JCA resource adapter at deployment time.

·         The JCA adapter must have a metadata schema. It must be defined exactly for this particular adapter type.

·         The definition of the adapter metadata should contain a global attribute Adapter Status, which activates or deactivates processing of the specific communication channel.

·         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 getBindingByChannelId(channelId) or InboundRuntimeLookup for this purpose.

·         The adapter must support header mapping and address normalization if addresses have to be converted to external protocols or IDoc scenarios must be supported. You must not save the corresponding settings in the communication channel. See also: Converting Addresses Using Header Mapping and Normalization