A usage of MQJExplorer grows, a number of requirements have already been received. These are captured here.
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.
<Completed in V0.7 - see Advanced Put and Browsing>
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>
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:
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.
All table columns should be capable of sort. A visual indication of sorting should also be provided.
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.
When the settings change in the profile, on exit, MQJExplorer should offer to save the settings.
On restart of MQJExplorer, the tree should reflect the state it was in when last saved.
MQJExplorer should present the user with the ability to add additional plug-in Look and Feels.
MQSeries demons such as the queue manager itself and command servers should be allowed to be stopped/started from within MQJExplorer.
Allow multiple dialogs to be displayed concurrently without preventing other operations from blocking.
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.
<Completed 8/26/01>
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.
<Completed 8/26/01>
Dialogs and frames within MQJExplorer must have their minimum sizes constrained to prevent a usability error if the windows are made too small.
<Completed 8/14/01>
On many dialogs, pressing "enter" should activate the default button action.
<Completed in V0.7>
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.
<Completed 10/20/01>
Entry assist should be provided for MQMD Formats values.
Review the consistency of the system and check for broken or bad configurations. For example, ensure that the DLQ named actually exists.
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.
<Completed in V0.9>
Have MQJExplorer watch a directory for the arrival of new files. When a file arrives, move its contents to a queue.
Implement the capability for MQJExplorer to process dead letter queue messages similar to that performed today by MQ DLQ handler.
Move/copy messages from one queue to another.
From within the queue browser, delete selected messages
Allow/disallow certain MQJExplorer functions by role to provide a logical separation between administration and development.
Message depletion must show a progress bar if it takes too long
Provide the ability to send direct MQSC commands with an editor and remember facility.
<Completed in V0.11>
See also:
Last Updated: 12/18/2001