Adapter-Specific Message Attributes in the Message Header 

Use

Some adapters support specific message attributes, which contain additional information about messages. This information is not located in the payload of the message, but in additional message header fields.

Every adapter has a defined set of attributes, which are described individually as part of the configuration for each of the adapters.

These attributes can be accessed in routing and mapping by using the attribute namespace and the technical name of the attribute. The attribute namespace comprises the namespace in the Integration Repository in which the adapter metadata for the adapter is saved and the name of the adapter metadata object.

The adapter namespaces for the adapters shipped by SAP therefore have the following format:

http://sap.com/xi/XI/System/<Adapter Metadata Object Name of Adapter>

The SAP adapter metadata objects are located in the namespace http://sap.com/xi/XI/System of software component SAP BASIS.

Features

Sender Adapter

Sender adapters that support specific message attributes can optionally add these attributes to messages.

You need to set these attributes explicitly in the adapter configuration. For more information about each of the sender adapters, see Adapter-Specific Message Attributes in the following sections:

●     Configuring the Sender RFC Adapter

●     Configuring the Sender Plain HTTP Adapter

●     Configuring the Sender File/FTP Adapter

●     Configuring the Sender JMS Adapter

●     Configuring the Sender SOAP Adapter

●     Configuring the Sender Mail Adapter

The attributes that are created can be used in routing, mapping, or receiver adapters of the same type.

Receiver Adapter

Receiver adapters that support these specific message attributes can optionally read these attributes from messages instead of using static parameters from the adapter configuration.

You need to set these attributes explicitly in the adapter configuration. For more information about each of the receiver adapters, see Adapter-Specific Message Attributes in the following sections:

●     Configuring the Receiver Plain HTTP Adapter

●     Configuring the Receiver File/FTP Adapter

●     Configuring the Receiver JMS Adapter

●     Configuring the Receiver SOAP Adapter

●     Configuring the Receiver Mail Adapter

These attributes can be either created in the mapping, or in some cases, sent by sender adapters of the same type.

Industry-Specific Adapters

For more information about adapter-specific message attributes in industry-specific adapters, see:

●     Configuring the RNIF Adapter (RNIF 1.1)

●     Configuring the RNIF Adapter (RNIF 2.0)

●     Configuring the CIDX Adapter

Routing

You can incorporate adapter-specific attributes when configuring logical routing (receiver determination and interface determination). When creating routing conditions, you can specify an adapter-specific attribute as a context object in the expression editor. To evaluate the routing condition at runtime, the current value of the attribute is read from the message header. Routing is not available in the PCK.

Mapping

In the mapping, you can use Java functions to get read and write access to message attributes. See also: Java Mapping of Adapter-Specific Message Attributes

Monitoring

Message attributes are listed in the message header DynamicConfiguration in message monitoring. For monitoring on the Integration Engine, see Displaying XML Message Versions.