Tuesday, January 11, 2011

How to install Quest QMX for Websphere MQ

Honestly, the documentation of Quests Management Extensions could be much more better. So as for the Extension for Websphere MQ Series.

Here you find the main steps how to install the QMX, in this case in a clustered environment running on Windows Server 2008 R2.

  1. Install SupportPac on every MQ Server Node. Therefore run the following setup from the server with QMX base frame framework and MQ extension installed: %programfiles%\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\MOM\MQSeries\IBMEventsMonitorSupportPacForWindows\setup.exe
  2. Install Telnet Server Feature on every MQ Server Node.
  3. Create a domain user. Add the user to the local group “TelnetClients” and to the local group “mqm” on all nodes.
  4. On the active node start a CMD and run the following command: runmqsc
  5. In the CLI run the commands (see step 6, 7 and 8) from the Quest Configuration Tool provided at the configuration site for MQ for every (!) queue and channel you have configured. You need the and even if they are not shown in the IBM documentation
  6. ALTER QMGR MONQ(MEDIUM) MONCHL(MEDIUM)
  7. ALTER QL('Q1') MONQ(QMGR)
  8. ALTER CHL('QM1.TO.QM2') CHLTYPE(SDR) MONCHL(QMGR)
  9. In the Quest Configuration Tool encrypt the username and password for the domain user account from step 3. Enter the username in the format domain\username
  10. Now add the filepaths to the username and password field at the configuration site for MQ
  11. Change the server name to the correct one. In a clustered environment use the cluster alias and verify, that you can reach the cluster with that. Otherwise take the IP (as I had to do because of customer configuration)
  12. Change the port to telnet (23)
  13. Safe your configuration
  14. Test the connection by right-click on the server name and select Test connection
  15. Now configure the channels, events and queues as you need it for your business
  16. Uncheck the Disabled checkbox and safe the configuration
  17. Start the monitoring by right-click on the server name and selecting Start
  18. Start the tracing console by right-click on the server name and select Show log
  19. There you can see if the extension works as expected.

All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.

0 Comments:

Post a Comment