WebSphere MQ Everyplace messages comprise Java objects, derived from the base class MQeFields, unlike WebSphere MQ messages which are defined as byte arrays with a message header and a message body.
Objects derived from both of these classes can be placed on the WebSphere MQ bridge queue named on the MQeInput node. Each message class produces different behaviors and each has advantages in different circumstances, as described below. You can find details of how to use both of these classes, as well as available fields and methods, in WebSphere MQ Mobile Transport.
WebSphere MQ Everyplace typically uses the MQeMsgObject class to store the messages that are put to and read from WebSphere MQ Everyplace queues. The WebSphere MQ Everyplace server within WebSphere Business Integration Message Broker supports this type of message.
The MQeMsgObject class is free format. Instead of having fixed attributes, you can create your own. This allows it to contain almost any type of object that can be stored within Java. When passing this information to a broker, this poses a problem because the MQMD within WebSphere Business Integration Message Broker is not free format and therefore cannot be easily formatted.
If this class is put to a bridge queue specified within the input node, all the predefined fields within the message are placed into the MQMD. All other non-supported fields within an MQMD are placed in the payload part of the message. This allows the message to be reconstructed if it is sent back to WebSphere MQ Everyplace by one of the nodes within the message flow (primarily the MQeOutput node). It does have the disadvantage that the payload part of the message cannot be parsed within the broker, but does mean that you can use special WebSphere MQ Everyplace fields, such as pic.
You cannot model messages of class MQeMsgObject
in the workbench. These message are not supported in the MRM domain and cannot
be parsed or modified in a message flow.
The MQeMbMsgObject class is specifically tailored for passing WebSphere MQ messages into WebSphere Business Integration Message Broker. A message constructed from MQeMbMsgObject only passes into the message flow those fields that are compatible with the broker.
This means that the payload can be parsed and therefore manipulated. So that you can, for example, store it in a database. However, you cannot use certain special WebSphere MQ Everyplace fields, such as pic. All undefined fields supplied within this message are not passed to WebSphere Business Integration Message Broker. Therefore, if this message is routed back to a WebSphere MQ Everyplace queue, the unrecognized fields are no longer present in the message.
You can model messages of class MQeMbMsgObject
in the workbench. These message are supported in the MRM domain and can be
parsed, modified and created in a message flow.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac10110_ |