Launch IBM MQ Explorer
We can launch IBM MQ Explorer by using one of three methods:
- system menu
- MQExplorer command
- strmqcfg command
To launch IBM MQ Explorer by using the system menu on Linux, or the start menu on Windows, left-click on the installation to launch.
On Windows, open the start menu, and select the IBM MQ Explorer installation entry under the IBM MQ group corresponding to the installation to launch. Each instance of IBM MQ Explorer listed is identified by the name chosen for its installation.
On Linux, the system menu entry for IBM MQ Explorer is added to the Development category; where it appears within the system menu is dependent on the Linux distribution (SUSE or Red Hat), and the desktop environment (GNOME or KDE). On SUSE, left-click...
Computer > More Applications...
...and find the installation of IBM MQ Explorer to launch under the Development category. On Red Hat, the installation of IBM MQ Explorer to launch can be found under...
Applications > Programming
The MQExplorer command and the strmqcfg command are stored in...
MQ_INSTALLATION_PATH/bin
MQExplorer.exe (the MQExplorer command) supports standard Eclipse runtime options including the following:
- -clean
- Clean the caches used by the eclipse runtime to store bundle dependency resolution and eclipse extension registry data. Using this option forces eclipse to reinitialize these caches.
- -initialize
- Initializes the configuration being run. All runtime-related data structures and caches are refreshed. Any user/plugin defined configuration data is not purged. No application is run, any product specifications are ignored and no UI is presented (for example, the splash screen is not drawn).
We can enter either the MQExplorer command or the strmqcfg command from the command line to launch IBM MQ Explorer. For more information about the strmqcfg command, see strmqcfg in the IBM MQ online product documentation.
If we have multiple installations of IBM MQ, see Multiple installations of IBM MQ Explorer.
To trace IBM MQ Explorer, use the runwithtrace.cmd; see Troubleshooting