For those of you who don’t know that much about IS02 here’s the short-short summary:
- Can administer (deploy to multiple eg’s at once, start/stop flows, create/delete execurtiongroups) local and remote brokers
- Support SSL connection to the configuration manager queue manager
- Can subscribe to and present statistics and accounting data. The drawback here is that access to an unsecured SYSTEM.DEF.SVRCONN is required (an mqm nightmare)
- Integrated with the WMQ Explorer (showing broker, configuration manager and mq objects side by side)
Back in may I wrote a post on the IS02 support pack. The background story was a customer of mine who currently set up multiple message brokers (WebSphere Message Broker) in an active-active cluster utilizing WebSphere MQ workload balancing features.
From a management/tool view-point the message broker has been all but complete. I was very excited to try out the IS02 support pack as it’s a lean alternative to the all-but-lean Message Broker Toolkit.
The previous post covered the functionality of version two, the version three of IS02: WebSphere Message Broker Explorer Plug-in was released a couple of days ago and today I gave it a shot.
The conclusion is (based on a setup where the configuration manager is installed on a separate box from the eclipse platform):
- Your configuration data (configuration manager connection) is now persisted and wil appear after restart of the eclipse platform.
- Message sets still can’t be removed
- You still need do create sender and receiver channels despite the fact that you’re using WebSphere MQ clusters where the broker(s) and configuration manager’s queue managers are within the same cluster.
So, a bit better but more need to come before this becomes really useful.