Setting | Description |
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: 1. priority 2. delivery count / redelivery count 3. durable / delivery mode 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: 1. priority 2. delivery count / redelivery count 3. durable / delivery mode 4. Time To Live (TTL) 5. First Acquirer / JMS_AMQP_FirstAcquirer The AMQP message's footer is converted to an event dictionary object and put under the "footer" key in the UM event's dictionary and vice versa - if an UM event being sent to an AMQP client has an "footer" dictionary object in the event dictionary, the content of that dictionary will be put as application properties of the AMQP message. If the message being transformed is a JMS message, then the JMS headers will be properly converted. |
3 - User Configurable | This option allows you to provide your own message converters. In order to use this option, do the following: 1. Enable the "AllowUserTransformation" option. 2. Provide a full class name as an AMQP_TRANSFORM JVM parameter to the server, e.g. -D AMQP_TRANSFORM=foo.bar.MyTransformer and this class should extend the abstract class: com.pcbsys.nirvana.server.plugins.protocols .amqp.transformation.aTransformation |