Accessing Configuration Data in the Receiver Direction 

Use

You usually access configuration data at two different locations:

·        In the modules

·        In the adapter

Integration

The configuration data is available to the adapters since adapters are subscribed to the CPA callback.

CPAcallback is not available to the modules. See also: Accessing Configuration Data at Runtime under 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.

You can use the NormalizationManager to convert external addresses to internal address representations and the other way around. See also: 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 published using the CCI ConnectionSpec. You do not have to determine the key once again using the address data.

You can access the configuration data as follows:

¡        Make the key information of the communication channel known to the ConnectionFactory using ConnectionRequestInfo.

Open CCIConnectionFactory.java and search for the character string CS_CIDMCF.

¡        Use the key of the communication channel in ManagedConnectionFactory to identify the communication channel.

Open SPIManagedConnectionFactory.java and search for the character string CS_CIDLKUP.

·        Reading the security settings (optional)

Reading the security settings is the last step to be executed in the receiver/outbound direction. 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 there.

You can read the security settings directly from the collaboration agreement object if they have been made known there by the LookupManager.getBinding method.

You can also use the OutboundRuntimeLookup methods getBindingValueAs[X]. This is the recommended procedure.

Open CCIInteraction.java and search for the character string CS_OUTBOUND.