What's new in WebSphere MQ Explorer V7.1: Part 1
mattchapman 1200004X8B Comments (2) Visits (17088)
This is the first of several blog entries describing changes in the new release of WebSphere MQ Explorer, available as a component of WebSphere MQ V7.1, and separately through SupportPac MS0T.
Repackaging MQ Explorer
The first change I'll describe is very noticeable if you're familiar with earlier versions of MQ Explorer. Before installing MQ Explorer V7.0 and earlier you have to first install a prerequisite package called the 'IBM WebSphere Eclipse Platform'. This is an installer that provides the Eclipse SDK (version 184.108.40.206 for WebSphere MQ V7.0).
As of V7.1 this is no longer the case. The MQ Explorer component of WebSphere MQ and the SupportPac are now self-contained packages. This has been achieved by building MQ Explorer using Eclipse's Rich Client Platform. This results in a subset of the Eclipse SDK (version 3.6.2 for this release) being included with MQ Explorer, but only those features and plugins that are needed by MQ Explorer. This means that the installation is quicker and easier, and less disk space is required. Look out for a future blog entry to show how to use MQ Explorer within an existing Eclipse-based environment.
If you've just upgraded from V7.0, the associated installation of the 'IBM WebSphere Eclipse Platform' will not be automatically uninstalled; you would need to uninstall this yourself if you no longer need it.
Improved multiple selections
The other change I'd like to cover today are usability improvements in the area of multiple selections. This builds on the initial work done in WebSphere MQ V7.0.1. It is now possible to select multiple items in both the navigator view and in object tables in the content view of MQ Explorer. This is a relatively small change, and some operations are still only applicable to single selections, but let's look in more detail at some examples of where multiple selections can be a big time-saver.
If you start MQ Explorer and have a number of remote queue managers that are initially disconnected, connecting to them one at a time would take a while. Now you can select them all, such as by clicking on the first one, then clicking on the last one whilst holding down the Shift key. If you then right-click you can see that the 'Connect' action is enabled for multiple selections. This will then proceed with connecting to each queue manager in turn. You may see a progress dialog for this:
Connect example (click image to enlarge)
The connection process uses Eclipse's progress service which means that if the operation completes quickly you don't even see the progress dialog at all, the queue managers just change state from disconnected to connected. If the connection process takes a while, depending on the speed of the network connection and the number of queue managers, then the progress dialog is shown.
Now what if you had a number of queues you no longer wanted? Previously you would have had to right-click and select Delete... on each one in turn. Furthermore you would get an 'Are you sure?' dialog, plus then an 'Object deleted successfully' message for each queue. Now you can select them all at once and you'll see a single confirmation dialog:
Delete example (click image to enlarge)
At first you'll still see an 'Object deleted successfully' message but notice that now there is a tick box to suppress these dialogs:
Success example (click image to enlarge)
Ticking (selecting) this option will suppress all similar messages, such as when creating and deleting objects. These actions will then complete successfully without showing a dialog - if the action is not successful then you'll still see an appropriate error dialog.
One more thing you can do with tables in MQ Explorer is to select one or more rows and then copy the contents as text to the clipboard (via the Edit menu or Control+C key combination) This can then be pasted into a text file as a way of exporting the contents of the table. The first line of the text shows the column headers, then a line for each row of the table. Each attribute of the table is separated by tab characters.
Export example (click image to enlarge)
Actions that do not support multiple selections will be greyed out. Let me know in the comments if you can think of any other operations that would benefit from working with multiple selections.
Read the rest of the series: