Show TOC

Configuring the Adapter in the Integration DirectoryLocate this document in the navigation structure

Configure adapters in the communication channel in the Integration Directory.

You have first defined message types, interfaces, and mappings in the Enterprise Services Repository at design time. 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 Template

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

The following objects must be created for the message exchange using the Integration Server:

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