Most, if not all, monitoring products use a local agent that runs as a
server-side MQ app, and that agent communicates out-of-band with a central
server monitoring app. If you rely on MQ as the comm transport and MQ has
problems, e.g. channel, outage, etc., then you can't relay any meaningful
status back to the central monitor. I suppose it all depends on how far
you want to take it before you realize it might be more cost effective to
buy a solution.
"Miller, Dennis"
<[EMAIL PROTECTED]
OM> To
Sent by: MQSeries [EMAIL PROTECTED]
List cc
<[EMAIL PROTECTED]
n.AC.AT> Subject
Re: Connecting to more than one
queue managers on solaris, linux
08/31/2004 08:13
PM
Please respond to
MQSeries List
<[EMAIL PROTECTED]
n.AC.AT>
I understand your hesitance to use MQ client for such an app. But think
about what you are really asking. An app on one server with MQM
credentials for other servers? An app on one server with access to MQM
internals on another server? Hmmm...
I'm sure you know that without MQ-Client, you cannot even connect to a
single QMgr across servers, much less multitudes of them. So, if your
thinking about monitoring even one qmgr by an app running on a different
system, you are talking about some sort of client model, by definition.
But it needn't necessarily be the MQ client. You could for example,
write a monitoring agent and run it locally on each qmgr. The user
interface for your monitoring app is then a client to these agents,
requesting services and receiving replies from them. If you are
so-inclined, you can even conduct the request/reply exchanges using
local connections and MQ messages (although, depending on what you are
doing, one might question the wisdom of running a monitoring application
in-band like that).
It is somewhat analagous to how the command server works, only
customized to your specific requirements.
-----Original Message-----
From: Pavel Tolkachev [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 31, 2004 1:31 PM
To: [EMAIL PROTECTED]
Subject: Re: Connecting to more than one queue managers on solaris,
linux
Thanks Dennis,
This is a low-level monitoring application (requiring mqm credentials,
by the way). Making it an MQ client makes running listener or configured
a pre-requisite to operate the app even if there is no business purpose
for them to be there and creates a whole number of security issues with
the too-far-going implications of their possible solutions. I will have
to either live with these consequences or go for running several
instances of the app instead (which is not ideal for my cause,
either..).
Pavel
"Miller, Dennis"
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
OM> cc:
Sent by: MQSeries Subject: Re: Connecting
to more than one queue managers on solaris, linux
List
<[EMAIL PROTECTED]
n.AC.AT>
08/31/2004 04:05
PM
Please respond to
MQSeries List
Yes, you can do it in the server app. Just use the MQ client. A server
app from the perspective of the application architecture can be a client
from the perspective of MQ.
-----Original Message-----
From: Pavel Tolkachev [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 31, 2004 10:30 AM
To: [EMAIL PROTECTED]
Subject: Re: Connecting to more than one queue managers on solaris,
linux
Thanks David,
Is there absolutely no way to do it in the Server app? What is so
different between Windows and Unix that you can do it on one but not the
other?
Thanks,
Pavel
"David C.
Partridge" To:
[EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
RIMEUR.COM> Subject: Re: Connecting
to more than one queue managers on solaris, linux
Sent by: MQSeries
List
<[EMAIL PROTECTED]
.AC.AT>
08/31/2004 11:58
AM
Please respond to
MQSeries List
Using MQ Client you can do this - each thread can own a connection to
different QM.
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
--
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
--
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
