Mapping JMS messages to MQe messages

This section describes how the JMS message structure is mapped to an MQe message. It is of interest to programmers who wish to transmit messages between JMS and traditional MQe applications.

As described earlier, the JMS specification defines a structured message format consisting of a header, three types of property and five types of message body, while MQe defines a single free-format message object, MQeMsgObject. MQe defines some constant field names that messaging applications require, for example UniqueID, MessageID, and Priority, while applications can put data into an MQe message as <name, value> pairs.

To send JMS messages using MQe, we define a constant format for storing the information contained in a JMS message within an MQeMsgObject. This adds three top-level fields and four MQeFields objects to an MQeMsgObject, as shown in the following example.
Figure 1. Mapping a JMS message to an MQeMQeMsgObject
Diagram showing how to map a JMS message to an MQeMsgObject, that is an MQe message. JMS message information is mapped onto the MQeMsgObject using MQeFields objects.These fields are listed in the text below.

The following sections describe the contents of these fields:


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.