A message is a collection of data sent by one application and intended for another application. MQe messages differ from those supported by MQ messaging:
{ } [ ] # ( ) : ; , ' " =
Table 1 describes the different data types:
Type | Description |
---|---|
ASCII | String or a dynamic array of invariant ASCII strings, excluding any of the characters { } [ ] # ( ) : ; , ' " = |
Boolean | True or false value |
Byte | Fixed array, or a dynamic array of byte values |
Double floating point | Value, fixed array, or a dynamic array of double floating point values |
Fields | Object or a dynamic array of fields objects (thus nesting of fields objects is supported) |
Floating point | Value, fixed array, or a dynamic array of floating point values |
Integer | 4 byte value, fixed array, or a dynamic array of integers |
Long integer | 8 byte value, fixed array, or a dynamic array of long integers |
Short integer | 2 byte value, fixed array, or a dynamic array of short integers |
Unicode | String or a dynamic array of Unicode strings |
Additionally, messages include a UID (unique identifier) which is generated by MQe. This UID uniquely identifies each individual message object in the entire MQe network and is constructed from the:
MQe adds property related information to a message (and subsequently removes it) in order to implement messaging and queuing operations. When sending a message between queue managers, you can add resend information to indicate that data is being retransmitted.
Messages can also have attributes. Attributes are fundamental to the MQe security model and allow selective access to content and the protection of content. They have the following properties:
Property | Description |
Authentication | Controls access |
Encryption | Protects the contents when the object is dumped (and allows restoration) |
Compression | Reduces storage requirements (for transmission and storage) |
Rule (Not applicable to C code base) | Controls permitted operations |
For more information on the properties in Table 2, see Security.