0 - No transformation

When this option is selected, no transformation is applied to the message, and it is passed as a byte array between the clients in the communication. This option is best used when only AMQP clients exchange messages.

1 - Basic Transformation

With this option selected when a message is exchanged over the AMQP protocol, the following header entries are converted:

This option is again best used when only AMQP clients exchange messages, but it also allows for server side filtering, based on the event's header and properties.

2 - Complete Transformation

With this option selected when a message is exchanged over the AMQP protocol, the following header entries are converted:

The footer of the AMQP message is converted to an event dictionary object and put under the "footer" key in the UM event dictionary and vice versa. If a UM event sent to an AMQP client has a "footer" dictionary object in the event dictionary, the content of that dictionary will be put as application properties of the AMQP message.

The delivery annotation, message annotations, application properties, and other standard properties of the AMQP message are also converted. For more information about mapping AMQP messages to Universal Messaging messages, see Appendix B: AMQP Messages to Universal Messaging message mappings.

3 - User Configurable

This option allows you to provide your own message converters. In order to use this option, do the following:

Provide a full class name as an AMQP_TRANSFORM JVM parameter to the server, e.g.

and this class should extend the abstract class:

If AMQP_TRANSFORM is not specified, this option will default to a null transform.