Introduction to MQe queues
MQe queues store messages. The queues are not directly visible to an application and all interactions with the queues take place through queue managers. For queue proxies, in the case of Java™ queue rules, refer to Queue rules. Each queue manager can have queues that it manages and owns. These queues are known as local queues. MQe also allows applications to access messages on queues that belong to another queue manager. These queues are known as remote queues. Similar sets of operations are available on both local and remote queues, with the exception of defining message listeners. Refer to Message listeners for more information. The Queue types section provides more information on the different types of queue you can have.
Messages are held in the queue's persistent store. A queue accesses its persistent store through a queue store adapter. These adapters are interfaces between MQe and hardware devices, such as disks or networks, or software stores such as a database. Adapters are designed to be pluggable components, allowing the protocols available to talk to the device to be easily changed.
Queues may have characteristics, such as authentication, compression and encryption. These characteristics are used when a message object is stored on a queue. Security provides more information on this.