Accessing Configuration Data in the Receiver Direction

Use

Access to configuration data normally takes place in the adapter and modules.

Integration

The CPA callback is only available to adapters, not to modules. Only adapters can register for the callback.

More information: Accessing Configuration Data in the Modules

Features

Once the message has passed through the modules, it is transferred to the JCA adapter.

The following tasks can be performed here:

  • Address conversion (optional)

    Address conversion may be necessary if the internal message protocol has to be mapped to an external protocol. To enable you to do this, identifiers are specified in the communication party in the Integration Directory. In the collaboration agreement, the identifier is then specified for the assigned communication channel that the communication parties have agreed upon.

    More information: Identifiers , Defining the Receiver Agreement , Defining the Sender Agreement .

    You can use the NormalizationManager to convert external addresses to internal address representations and the other way around.

    More information: Converting Addresses Using Header Mapping and Normalization

  • Reading the configuration data for the receiver communication channel using the communication channel key (mandatory)

    In the JCA adapter, the communication channel key is transferred in the CCI ConnectionSpec. You do not need to use the address data again in the adapter to get the key.

    You can access the configuration data as follows:

    • To make the key of the communication channel known, use ConnectionRequestInfoof the ConnectionFactory at the time of the allocateConnection() call in the JCA adapter.
    • Use the key of the communication channel in 
      ManagedConnectionFactory
      to identify the communication channel.
  • Reading the security settings (optional)

    Reading the security settings is an additional option. All attribute references that are defined in the <SecurityAttributes>area of the <MessageProtocol>tag are displayed in the collaboration agreement and the selection is saved in the collaboration agreement.

    The security settings can be read directly from the collaboration agreement once they have been determined there using the LookupManager.getBinding method.