Uninstalling the WebSphere MQ BTM extension

This section describes how to uninstall the WebSphere MQ BTM extension from the following supported platforms:

Uninstalling the WebSphere MQ BTM extension from Windows

1. Stop the WebSphere MQ configuration (qpcfg) and monitoring (qpmon) extensions.
2. Stop WebSphere MQ programs that do not end with the queue manager such as listeners that are configured for manual start/stop and trigger monitors.
3. Stop all of your WebSphere MQ applications.
4. Stop the queue manager using endmqm –w
5. Stop any forgotten WebSphere MQ programs or applications that are preventing the queue manager from stopping. Do not continue until endmqm –w ends.
6. Navigate to Start > Programs > IBM WebSphere MQ > WebSphere MQ Explorer and expand WebSphere MQ Explorer.
7. Right-click the queue manager you are using and select Properties > Exits.
8. Select the exit for TrueSight Middleware and Transaction Monitor and click Remove.
9. Click OK and exit the Explorer.
10. Remove the dll files:
    • For WebSphere MQ 7.1 or later:
    1. • Remove the 32-bit btmmq_71.dll from the staging directory to the default 32-bit exits directory. For example: C:\Program Files (x86)\IBM\WebSphere MQ\exits
       • Remove the 64-bit btmmq_71.dll from the staging directory to the default 64-bit exits directory. For example: C:\Program Files (x86)\IBM\WebSphere MQ\exits64
    • For WebSphere MQ 7:
    1. • Remove the 32-bit btmmq_70.dll from the staging directory to the default 32-bit exits directory. For example: C:\Program Files (x86)\IBM\WebSphere MQ\exits
       • Remove the 64-bit btmmq_70.dll from the staging directory to the default 64-bit exits directory. For example: C:\Program Files (x86)\IBM\WebSphere MQ\exits64
11. Start the queue manager, MQ applications, listeners, trigger monitors and WebSphere MQ configuration (qpcfg) and monitoring (qpmon) extensions as required.

Uninstalling the WebSphere MQ BTM extension from UNIX

1. Stop the WebSphere MQ configuration (qpcfg) and monitoring (qpmon) extensions.
2. Stop WebSphere MQ programs that do not end with the queue manager such as listeners that are configured for manual start/stop and trigger monitors.
3. Stop all of your WebSphere MQ applications.
4. Stop the queue manager using endmqm –w
5. Stop any forgotten WebSphere MQ programs or applications that are preventing the queue manager from stopping. Do not continue until endmqm –w ends.
6. Edit the qm.ini file to remove the exit information. Do not remove the ExitPath section even if added during installation as an exit added later might be using those paths now. Do note these paths for a later step. Remove the ApiExitLocal section for the BTM Extension.
   
   qm.ini
   ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
ApiExitLocal:
Name=BTMExtension
Sequence=3
Function=EntryPoint
Module=<btmmq71 or btmmq70>


7. Edit the mqs.ini file to remove the exit information. This was an optional step so the exit cannot be configured here. Remove both the ApiExitTemplate and ApiExitCommon sections for the BTM Extension.
   
   mqs.ini with added exits
   ApiExitTemplate:
Name=BTMExtension
Sequence=3
Function=EntryPoint
Module=btmmq
ApiExitCommon:
Name=BTMExtension
Sequence=3
Function=EntryPoint
Module=<btmmq71 or btmmq70>


8. Remove the following files from the ExitsDefaultPath and ExitsDefaultPath64 directories (from the qm.ini file noted earlier).
   • For WebSphere MQ 7.1 or later remove the btmmq71* versions of the files.
   • For WebSphere MQ 7 remove the btmmq70* versions of the files.
9. Restart the queue manager, MQ applications, listeners, trigger monitors and WebSphere MQ configuration (qpcfg) and monitoring (qpmon) extensions as required.

Uninstalling the WebSphere MQ BTM extension from i5/OS

1. Stop the WebSphere MQ configuration (qpcfg) and monitoring (qpmon) extensions.
2. Stop WebSphere MQ programs that do not end with the queue manager such as listeners that are configured for manual start/stop and trigger monitors.
3. Stop all of your WebSphere MQ applications.
4. Stop the queue manager using endmqm –w
5. Stop any forgotten WebSphere MQ programs or applications that are preventing the queue manager from stopping. Do not continue until endmqm –w ends.
6. Remove libbtmutil.so from from the directory specified by the MQS_HOME system environment variable (for example, /MQS_HOME/BTM/logs).
7. Edit the qm.ini file to remove the BTM WebSphere MQ API exit information. Remove the ApiExitLocal section for the BTM Extension.
   
   qm.ini
   ApiExitLocal:
Name=BTMExtension
Sequence=3
Function=EntryPoint
Module=lib/BTMMQ
   
   where:
   lib is the library name to which the agents files were restored.
   
   
8. Edit the mqs.ini file to remove the exit information. This was an optional step so the exit cannot be configured here. Remove both the ApiExitTemplate and ApiExitCommon sections for the BTM Extension.
   
   mqs.ini with added exits
   ApiExitTemplate:
Name=BTMExtension
Sequence=3
Function=EntryPoint
Module=lib/BTMMQ
ApiExitCommon:
Name=BTMExtension
Sequence=3
Function=EntryPoint
Module=lib/BTMMQ
   
   where:
   lib is the library name to which the agents files were restored.
   
   
9. Restart the queue manager, MQ applications, listeners, trigger monitors and WebSphere MQ configuration (qpcfg) and monitoring (qpmon) extensions as required.