Review WebSphere MQ Everyplace messages to understand the difference between these two classes and where you should use each.
To use these classes within a WebSphere MQ Everyplace client, you must include the mqimqe.jar file located in the classes directory of the WebSphere Business Integration Event Broker installation directory in your CLASSPATH. This jar file is transferable to systems that do not have WebSphere Business Integration Event Broker installed if you want a WebSphere MQ Everyplace client to communicate with a broker that has not been installed locally on that system.
You are recommended to use the optimized jar file mqimqec.jar with the MQeMbMsgObject class. mqimqec.jar contains sufficient classes for you to use MQeMbMsgObject but, at approximately 25KB, is significantly smaller than mqimqe.jar. mqimqec.jar is particularly useful if you use a WebSphere MQ Everyplace thin client.
When you put a message on a bridge queue for the WebSphere MQ Everyplace node, you must specify the message type. The types supported by the WebSphere MQ Everyplace node are listed below:
You can set the message type as shown:
mqeMsg.putInt(MQeMbMsgObject.TYPE_OF_MSG, MQeMbMsgObject.TYPE_MQE);
All available fields are defined in the MQeMbMsgObject class. See other fields in WebSphere MQ Everyplace publish/subscribe methods.
MQeMsgObject mqeMsg = new MQeMsgObject();or
MQeMbMsgObject mqeMsg = new MQeMbMsgObject();