Posted: Wed Mar 29, 2006 4:50 am Post subject: Monitoring MQ objects in WAS 6.0.x MQSeries link
Newbie
Joined: 15 Jan 2003 Posts: 3 Location: AC - Germany
We allways do monitoring our MQ installations via the IBM Monitor mqmonntp.exe with best results on all our platforms. Now we have got a new feature called WebSphere MQ link who is an element of the WebSphere Application Server 6.0.x.
In conjunction with the possibility to create a virtual bus Server-sided on a AIX-platform and a foreign bus Client-sided - WebSphere MQ link offers the facility to declare a virtual Queuemanager on the one hand who will be able to connect to a real Queuemanager on the other hand via a MQ-Connection. Thus saves one installation of MQ and probably also costs. The declaration of the MQ objects needed server-sided (virtual !) is inside the WAS Admin-Console and the declaration of the MQ objects client-sided is normal MQ Admin biz.
Our problem is now, that we actual search a way to administrate and to monitor the MQ objects remote as they are components of the virtual QueueManager.
Has anyone an idea or even a solution for this?
Code:
Hello Paul Clarke (WebSphere MQ Development) - what is your mind ?
I would think that WAS 6 would provide metrics through the normal WAS mechanisms for monitoring what is going on with the new messaging provider. Consequently any tool that is certified to work with all the metrics generated by WAS 6 can monitor the messaging provider.
In other words, you may have to monitor this like it's an App Server and not like it's MQ.
Likewise with administration.
It would be fun for someone other than me to write code that translates mqsc commands into the appropriately formatted wsadmin (or whatever WAS v6 uses) commands to administer things in the messaging provider. _________________ I am *not* the model of the modern major general.
Joined: 15 Jan 2003 Posts: 3 Location: AC - Germany
Thanks for quick responding.
The answer is approximately that what I'am worry about. Because in our enterprise (not even a small one) the WAS Admin and the MQ Admin are different divisions and of course with different authorisations, too.
In other words, with MQ link WAS Admin's have to to administrate the MQ Part inside WAS (virtual QMGR) and MQ Admin's the Part outside WAS (the real QMGR's) hoping of peaceful coexistent.
Quote:
It would be fun for someone other than me to write code that translates mqsc commands into the appropriately formatted wsadmin (or whatever WAS v6 uses) commands to administer things in the messaging provider.
Naturally this, I can just approve.
For those who are interested in more information about MQ link, here the corresponding URL (german only !):
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum