Configuring a queue manager using memory only

This section applies only to queue managers using the Java programming interface.

It is sometimes required that applications have a queue manager which exists in memory only. WebSphere MQ Everyplace 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.

A WebSphere MQ Everyplace 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 WebSphere MQ Everyplace queue managers have the following characteristics:

Solutions that find this particular configuration of an WebSphere MQ Everyplace 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.



© IBM Corporation 2002. All Rights Reserved