SIBus Explorer
Service Integration Bus Explorer is tool provided by IBM that allows you to browse the queues on your WebSphere Application Service. You can see individual messages, internal queues, clear queue points etc. The path to get this information requires so many clicks, that SIBus Explorer will quickly become an indispensable tool.
There is a similar product out there for MQ (and other providers) called HermesJMS but I’m not sure if anyone has gotten it to work in WAS v6, so YMMV.
Related Posts
- Do not use forward slashes in SIBus Destination names with JMS
- WebSphere Default Messaging (SIBus) and WebService Error Handling
- WebSphere Process Server - Business Process Choreographer Explorer Customization and Tuning Options
- Exploring IBM SOA Technology and Practice reviewed by Don Ferguson
- Exploring The Contents of a WID Module Project
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
March 26th, 2008 at 4:01 pm
A couple of other related tools on alphaWorks that are worth a look:
IBM Client Application Tool for JMS - SWT or Swing based J2EE client application that allows you to browse JNDI and send/receive messages using the available JMS resources
Service Integration Bus Performance - SWT based application that enables you to easily enable and monitor PMI statistics relevant to messaging
March 26th, 2008 at 4:59 pm
Thanks David.. I had no idea either of those two tools existed. (It’s tough to manage that firehose of IBM information!)
I’ll definitely be giving them both a workout.
August 12th, 2008 at 12:29 pm
[...] the need to be able to place a JMS Message onto a Service Integration Bus Queue. I tried to use the SIBus Explorer, but it really didn’t like my WebSphere v6.1 configuration and would always throw an [...]
November 17th, 2008 at 6:49 am
Would the SIBus Explorer work if security is turned on?
The last time i tried( a while ago) it did not work.
Manglu
November 17th, 2008 at 9:39 am
Hi Manglu,
Yes, it works with security. You have to ensure you get the client key for the server etc. I do recall that I was not able to get it working with WAS 6.1 security though.. (worked on 6.0)