The following are uses for metadata in Interchange:
You can configure pickups to attach metadata to messages Interchange consumes from back-end applications or trading partners.
You can set rules that direct inbound messages to specified deliveries, based on rules.
When using JMS as an application transport, metadata parameters are appended to the BytesMessage or TextMessage. See JMS transport configuration.
To comply with ebXML standards, Interchange supports message metadata elements with message payloads. The metadata elements are information about message payloads, such as the identity of the CPA to use for message processing.
Metadata also can be exchanged between Interchange and a back-end system via application transports.
To comply with AS4 standards, Interchange supports message metadata elements with message payloads.
See AS4 metadata.
To comply with RosettaNet standards, Interchange supports message metadata elements with message payloads.
Message handling refers to optional processing of inbound or outbound messages based on metadata attributes and actions. Interchange lets you set up conditions to:
See Message handler.
You can perform post-processing commands on each inbound message immediately after Interchange has received, processed and written it to an application delivery. You also can execute post-processing commands after sending messages to partners. Interchange by default passes seven items of message metadata to the post process. See Post-processing configuration.
Metadata are used by all APIs, including Java inline processing and pluggable transports. Using APIs requires obtaining an optional developer’s license.