Whenever I have duplicate entries in the MQX section, they do have the different connection parameters - one for what I use for MQX, and the other is the MBX.
But it's not consistent, or at least I haven't identified the pattern, because I have numerous connections where the connection parms are different between MQX and MBX (validated by looking at the actual channel instances on the QM when I make both connections), yet they do not have duplicate entries in the MQX section.
"MBX does not allow you to add a broker using an existing MQExplorer queue manager connection, as far as I know, nor discover a broker that is on a newly added queue manager to MQExplorer. I continue to find this annoying."
Yeah, it would be nice if your MBX install would partner with MQX better and identify a WMB Broker on a QM in the MQ Explorer section and maybe prompt you if you would like to add it, if not just do it automatically for you. This might require that both MQX and MBX use the same connection parameters.
You would still need the ability to only add an MBX connection over an MBX specific channel and not have any MQX ability to the QM - separation of duties between MQ Admins and MB Admins if required.
Peter Potkay
From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf Of Jefferson Lowrey
Sent: Monday, August 12, 2013 10:42 AM
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: MQ Explorer and MB Explorer to the same QM over different channels
I'm going to use MQExplorer to mean MQ and MBX to mean Broker Explorer.
MBX will discover any local brokers attached to local queue managers, and show both.
MBX will allow you to connect to a broker that does not already have a queue manager known to MQExplorer. I believe when this happens, MBX adds a queue manager definition to MQExplorer.
I believe that if you use the same set of connection information in MBX as an existing qmgr connection - same hostname/port/channel/etc - that MBX will *not* add an additional qmgr definition to MQExplorer.
MBX does not allow you to add a broker using an existing MQExplorer queue manager connection, as far as I know, nor discover a broker that is on a newly added queue manager to MQExplorer. I continue to find this annoying.
So I think the reason you have duplicate qmgr entries is that you added a qmgr to MQExplorer using one set of connection information and added the same qmgr to MBX using a different set of connection information. In cases where you don't have duplicate qmgrs, it's because the connection information is the same.
Thank you,
Jeff Lowrey
IT Specialist, Consultant
Internet jlowrey-r/Jw6+rmf7HQT0dZR+***@public.gmane.org<mailto:jlowrey-r/Jw6+rmf7HQT0dZR+***@public.gmane.org>
From: "Potkay, Peter M (CTO Architecture + Engineering)" <Peter.Potkay-***@public.gmane.org<mailto:Peter.Potkay-***@public.gmane.org>>
To: MQSERIES-JX7+OpRa80QeFbOYke1v4oOpTq8/***@public.gmane.org<mailto:MQSERIES-JX7+OpRa80Ties2YCUG/***@public.gmane.orgniwien.ac.at>,
Date: 08/12/2013 05:47 AM
Subject: [MQSERIES] MQ Explorer and MB Explorer to the same QM over different channels
Sent by: MQSeries List <MQSERIES-JX7+OpRa80QeFbOYke1v4oOpTq8/***@public.gmane.org<mailto:MQSERIES-JX7+OpRa80QeFbOYke1v4oOpTq8/***@public.gmane.org>>
________________________________
Can someone explain how MB Explorer and MQ Explorer interact with connection details to any one particular QM? I want to use an MQ Explorer specific channel for the MQ Explorer connection and an MB Explorer specific channel for the MB Explorer connection.
I have yet to see a consistent pattern on how this works. For some QMs I have two entries in the MQ Explorer section even though I only added it once up there. I think its picking up the connection details sometimes from the MB Explorer section. But it's not that way for all of my QMs.
Do these 2 Explorers allow parallel unique connection details for any one QM?
If yes, what is the correct order to add the connections? The MB Explorer one first, then the MQ Explorer one?
MQ Explorer 7.5.0.2
MB Explorer 8.0.0.2
Peter Potkay
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html