Configuring a queue manager using memory only

This topic applies only to the Java™ code base.

It is sometimes required that applications have a queue manager which exists in memory only. MQe Version 2.0 provides the ability to configure and use a queue manager using memory resources only, without the need to persist any information at all to disk.

An MQe queue manager normally uses two mechanisms to store data:

The default is the MQeDiskFieldsAdapter, which persists information to disk.

Using the MQeMemoryFieldsAdapter instead of the MQeDiskFieldsAdapter for both of these tasks allows the queue manager to be defined, used to transmit and store messages, and deleted all without accessing a disk.

In-memory MQe queue managers have the following characteristics:

Solutions that find this particular configuration of an MQe queue manager useful have the following properties:

An example of the configuration technique can be seen in the examples.queuemanager.MQeMemoryQM class. Note that the MQeMemoryFieldsAdapter is instantiated explicitly at the start, and a reference is held until the point where the queue manager, and messages it contains are no longer required.

Note also that it is still important that in-memory queue managers have names which are unique within the messaging network.


Terms of use | WebSphere software

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