Future enhancements

A usage of MQJExplorer grows, a number of requirements have already been received. These are captured here.

Support for MQRFH2 header

The IBM MQSeries Integrator product makes use of RFH2 headers. This requirement asks for the inclusion of RFH2 header generation, probably as part of Advanced Put Message function.

Security exit support

This enhancement will provide both a local and remote MQ Security exit to prevent unauthorized access to the queue manager.
<Completed in V0.6 - see Security>

Browse more messages

Currently, the browse function only shows the first 200 messages. It is desired to show more if more exist. This should be allowed in 2 modes:

Be able to specify how many messages may be viewed at one time. Default will be 200 but the capability to specify All should be allowed.
Be able to browse forward and back to see the next chunk and previous chunk

Put delimited messages from file

There should be the ability to read a file of simple delimited messages and put each of those messages to the queue as separate messages. For example, newline terminated, character terminated etc. In the future, CMI should be incorporated to allow arbitrary selection of messages from a CMI template.

Sorting table columns

All table columns should be capable of sort. A visual indication of sorting should also be provided.

Asynchronous operations

Most activities in MQJExplorer are synchronous. For example, consume messages will not release the program for other activities. Examination of this should be performed to see if it would be possible to perform asynchronous operations.

Save profile on exit

When the settings change in the profile, on exit, MQJExplorer should offer to save the settings.

Inclusion of tree state in profile

On restart of MQJExplorer, the tree should reflect the state it was in when last saved.

Selection of additional L&Fs

MQJExplorer should present the user with the ability to add additional plug-in Look and Feels.

Start/Stop MQSeries demons

MQSeries demons such as the queue manager itself and command servers should be allowed to be stopped/started from within MQJExplorer.

Background dialogs

Allow multiple dialogs to be displayed concurrently without preventing other operations from blocking.

Check that the command server is running

MQJExplorer requires that the MQSeries command server is running. Once connected to a queue manager, this can be determined quickly and an error/warning dialog displayed to ensure that the no progress is made until the command server started.

MQJExplorer console logging

Provide the ability to have MQJExplorer log its data to a JTextArea or other window for viewing at some future time. In addition, allow the log to also be written to its original location in addition to the console.

Constraints on resize

Dialogs and frames within MQJExplorer must have their minimum sizes constrained to prevent a usability error if the windows are made too small.

Support of default button action

On many dialogs, pressing "enter" should activate the default button action.

Add support for JMS

IBM's MQSeries JMS support comes with a tool called JMSAdmin which allows managed objects to be stored in a JNDI repository. Support for JMS within MQJExplorer will add the ability to work with these options.

Entry Assist - MQMD Formats

Entry assist should be provided for MQMD Formats values.

System review

Review the consistency of the system and check for broken or bad configurations. For example, ensure that the DLQ named actually exists.

MQSI - ESQL Assistance

Include support for generating ESQL statements based on contents of message (or elsewhere ...). For example, parse an XML message and generate assignments based on the values.

Directory Watcher

Have MQJExplorer watch a directory for the arrival of new files. When a file arrives, move its contents to a queue.

Execute MQSC commands

Provide the ability to send direct MQSC commands with an editor and remember facility.