Designing Mappings for Adapter-Specific Message Attributes

The message header of a message contains a header for adapter-specific message attributes that the sender adapter can use to write additional information to the message header. This enables sender adapters to write information that is not known until runtime to the message.

Furthermore, developers have read and write-to access to adapter-specific attributes from within a mapping program.

XSLT programs (J2EE) and message mappings have mapping runtime constants that enable developers to access the same Java classes for adapter-specific-attribute mappings as in Java mapping programs. Mapping programs executed on the Integration Server support this kind of access. There is a separate interface for ABAP mappings.

More information:

• Java Mapping of Adapter-Specific Message Attributes

• XSLT Mapping of Adapter-Specific Message Attributes

• ABAP Mappings (see the interface documentation for the interface IF_MAPPING_DYNAMIC_CONF)