You can uninstall the IBM® MQ MQI clients and
servers on Windows systems by using the control panel,
the command line ( msiexec ), MQParms, or by using the
installation media, in which case you can optionally remove queue managers as well.
Before you begin
By default, uninstallation logging is not enabled on
Windows. To ensure that you receive an uninstallation log, carry out the following procedure:
- In a command prompt, open the registry editor by issuing the command
regedit.
- Create, or edit, the appropriate registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
- Under this registry key add the following information:
- Name
- Logging
- Data type
- REG_SZ
- Value
- voicewarmup
- Save the updated registry key.
Procedure
The first part of the procedure ensures that there are no IBM MQ programs or processes running:
-
If you are running IBM MQ with the Microsoft Cluster Service (MSCS), remove the queue managers from
MSCS control before uninstalling IBM MQ. Perform the
following steps for each queue manager currently under MSCS control :
-
Take the queue manager resource offline.
-
Destroy the resource instance.
-
Migrate the queue manager files back from shared drives. This step is shown as optional in
Removing a queue manager from MSCS
control. However, it is mandatory in this case.
-
Stop all IBM MQ applications associated with the
installation you are uninstalling.
-
Close all Managed File Transfer agents.
-
For a server installation, end all IBM MQ
activity:
-
Log in as a user in the group
mqm
.
-
Stop all running queue managers and listeners by using the IBM MQ Explorer, or by entering the following commands:
- Set up your environment to work with the installation you want to uninstall by entering the
following command:
MQ_INSTALLATION_PATH\bin\setmqenv -s
where MQ_INSTALLATION_PATH is the location where IBM MQ is installed.
- For each queue manager, enter the following command to stop the queue manager:
endmqm queue_manager_name
- For each queue manager, enter the following command to stop any listeners associated with the
queue manager:
endmqlsr -m queue_manager_name
-
Stop IBM MQ.
To do this right-click the IBM MQ icon in the system tray, then select Stop IBM MQ.
-
Close all IBM MQ windows.
-
Stop any monitoring service.
When all processes associated with IBM MQ
are no longer running, you can uninstall IBM MQ:
-
Uninstall IBM MQ by using one of the following
methods:
If you have to cancel the uninstallation process before it is finished, you
might have to reconfigure
IBM MQ with the Prepare
IBM MQ wizard because the rollback of the deletion of
the
IBM MQ service is unable to set the service's user
account password. Use the following command to reconfigure
IBM MQ:
MQ_INSTALLATION_PATH\bin\amqmjpse.exe -r
For more information about the
Prepare IBM MQ Wizard, see
Configuring IBM MQ with the Prepare IBM MQ Wizard.
-
Check the Windows event log and restart the system
if necessary.
If event ID 10005 is written to the Windows event log, you must restart the system to complete the
uninstallation process.
- Optional:
If you are uninstalling the last or only installation of IBM MQ, you can remove all the information about previous
installations that is retained on the system, if you want to. You should use the
ResetMQ.cmd for this purpose; see Clearing IBM MQ installation settings
for more information.
The following registry values remain after uninstallation:
- My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere MQ\LogDefaultPath
- My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere MQ\WorkPath
- My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\IBM\WebSphere
MQ\LogDefaultPath
- My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\IBM\WebSphere
MQ\WorkPath
Data folders will also remain and are located at
MQ_DATA_PATH\Config, where
MQ_DATA_PATH is the location of the IBM MQ data directory. Most of the remaining files contain text
such as INI files, error logs, and FDC files. The executable shared library
mqzsd.dll also remains.
If a client is installed on a system where the LogDefaultPath registry value
remains from a previous server installation, a client installation will attempt to create this
directory if it does not already exist. If this behavior is not wanted, remove the LogDefaultPath
registry value before installing the client.