Nick,
In answer to you email.
Adding a queue manager to MQ Explorer via the GUI will also update the
WMQ_Handles.xml, but can be manually updated too (make sure MQ explorer is closed if editing the file). the file on windows is located somewhere like
C:\Users\name\IBM\WebSphereMQ\workspace\.metadata\.plugins\com.ibm.mq.explorer.ui
example file with two queue managers -
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE QueueManagerHandles SYSTEM "WMQ_Handles.dtd">
<QueueManagerHandles>
<QueueManagerHandle commandLevel="910" connnectionType="2" name="QMRY01" platform="3" uuid="QMRY01_2019-08-17_19.31.09" visible="1" refreshInterval="-1" autoReconnect="0" userIdState="1" expiryInterval="300" waitInterval="30" connName="QMRY01(1414)" channel="SYSTEM.ADMIN.SVRCONN" securityExitName="" securityExitLocation="" securityExitData="" useridCompatibilityMode="1" passwordMode="1" userid="" sslCipherSuite="SSL_RSA_WITH_AES_256_CBC_SHA256" sslFipsRequired="0" sslPeerName="" sslResetCount="0" sslPersonalStore="F:\keys\mq\mqexplorer\qmkey.jks" sslPersonalStorePw="********" sslTrustedStore="F:\keys\mq\mqexplorer\qmkey.jks" sslTrustedStorePw="********" uniqueId="QMRY01/QMRY01/1414/SYSTEM.ADMIN.SVRCONN"/>
<QueueManagerHandle commandLevel="910" connnectionType="2" name="QM5A01" platform="3" uuid="QM5A01_2018-06-26_10.04.43" visible="1" refreshInterval="-1" autoReconnect="0" userIdState="1" expiryInterval="300" waitInterval="30" connName="QM5A01(1414)" channel="SYSTEM.ADMIN.SVRCONN" securityExitName="" securityExitLocation="" securityExitData="" useridCompatibilityMode="1" passwordMode="1" userid="" sslCipherSuite="SSL_RSA_WITH_AES_256_CBC_SHA256" sslFipsRequired="0" sslPeerName="" sslResetCount="0" sslPersonalStore="F:\keys\mq\mqexplorer\qmkey.jks" sslPersonalStorePw="********" sslTrustedStore="F:\keys\mq\mqexplorer\qmkey.jks" sslTrustedStorePw="********" uniqueId="QM5A01/QM5A01/1414/SYSTEM.ADMIN.SVRCONN"/>
</QueueManagerHandles>
Queue managers can be grouped in folders (sets) if you want. These are held in WMQ_Sets.xml
Other alternatives to MQ Explorer that I have used are QPASA (now Truesight Middleware Monitor ) and MQMon. Both are commercial offering but MQMon does not cost much and has a lot of useful tools. Truesight Middleware Monitor is good for alerting and throughput analysis.
Regards,
Rab.
Dear Rab,
Many thanks for your prompt response:)
This is what I was actually looking for..
Since I haven't experience on something like this, could you pls send me a sample of this xml file, in order to
see the structure and the connection records layout?
How did that xml file generated ? Have you created manually by yourself?
Cheers Nick.
------------------------------
Rab McGill
------------------------------
Original Message:
Sent: Tue April 07, 2020 09:52 AM
From: Rab McGill
Subject: Running MQ Explorer into Eclispe issues
Hi,
We use MQ Explorer to administer MQ to a certain extent. It is a GUI so we do no use it for mass administration. Each of the admins (about 8 of us) has a copy of of MQ explorer installed and a copy of centrally managed WMQ_Handles.xml file. We have about 1000 queue managers defined in this file. Each admin has their own login to MQ (via ldap, id and password). We don't need multiple copies of MQ explorer. We connect to Linux, AIX, Windows , I-series and and z-os. The majority of our estate is Linux and we use ssh and command line to mass administer our Linux estate.
regards,
Rab.
------------------------------
Rab McGill
Original Message:
Sent: Tue April 07, 2020 03:07 AM
From: NIKOLAOS DAKORONIAS
Subject: Running MQ Explorer into Eclispe issues
Hello MQ community users,
I have installed MQ Explorer v9.1.4 into Eclipse 2020-03 (4.15.0) on Windows client platform in order to connect and access a few target Windows based Queue Managers (mainly v7.5, v.8)
I have managed to connect to the specific queue managers, but when trying
retrieve the queues or channels or other objects listed under this queue manager, the search is endless and finally fails...
So, I am not able to see any object listed under the connected MQ manager.
Notice that the idea, is to run multiple instances of MQ explorer under my account and the same will be applied for a few other accounts, for administration purposes.
I have followed the article below: https://www.ibm.com/support/pages/how-run-multiple-instances-mq-explorer-75-or-80
Btw, the article says that the above is NOT applicable to MQ v7.5 and later versions on Windows.
Do you think, that might be the reason for the failure?
Should I try the same on a Linux box?
Thanks in advance,
Cheers Nick
------------------------------
Nick Dakoronias
------------------------------