The IBM Integration Bus, formerly known as the IBM WebSphere Message Broker Family, provides a variety of options for implementing a universal integration foundation based on an enterprise service bus (ESB)

In this module we discuss how to remove an existing installation of IBM Integration Bus (IIB) 9.0 components for starting IIB 9.0 Administration. The various components are

  1. WebSphere MQ
  2. IBM Integration Bus Component
  3. IBM Integration Bus Toolkit
  4. IBM Integration Bus Explorer

    These components can be installed separately on different operating systems and in various modes i.e. Graphical, Console and Silent modes. Graphical or GUI, so we may have to take different approaches, depending on how the initial product is installed, however the default method will be to use a silent approach, and only refer to a GUI un-install if things do not work at a command shell-level.

Link to PDF version of Uninstall IIBM 9.0

Un-Installing IIB 9.0 for Developers (Free version)

As root, look and see what is installed vie the default /opt folder. You may have installed IB 9.0, the IB Toolkit and IB Explorer in different locations. In this guide we will presume they are installed in the default folders as per standard installations.

Stop all products

Before we remove the installations, we need to check that we have no running products, below is our check-list of actions:

  • Check for running Broker Nodes
  • Check for running IB Toolkit (only if this is a desktop machine as opposed to server)
  • Check for running IB Explorer
  • Check for running Queue Managers (WMQ)

Check for running Broker nodes

First, I switched to the mqm user. In my installation, I used mqm as my main IIB administration user, now you may have different users to administer IIB vs WMQ. Also you may notice that I have used .bashrd to automatically source the IIB profile.

  • Open an appropriate shell using admin user
[root@localhost opt]# su – mqm
Last login: Tue Feb 17 20:21:46 GMT 2015 on pts/2

Note: Here is my .basrc

[mqm@localhost ~]$ vi .bashrc
# .bashrc
# Source global definitions
if [ -f /etc/bashrc ]; then

. /etc/bashrc



# Uncomment the following line if you don’t like systemctl’s auto-paging feature:



# User specific aliases and functions

source /opt/ibm/mqsi/

  • Issue the mqsilist command to list all the running brokers
[mqm@localhost ~]$ mqsilist
BIP1281I: No brokers have been defined on this machine.
BIP8071I: Successful command completion.

In my example, we can see that I have no brokers, but I might have had a broker running, so below is a set of steps to help you stop running brokers.

Note: If you have running Brokers, then use mqsistop to stop the running brokers for example, use the following steps for Broker called

  • Verify Broker State
[mqm@localhost ~]$ mqsilist
BIP1284I: Broker ‘Brk01Verify’ on queue manager ‘QMVerify02’ is running.
BIP8071I: Successful command completion.
  • Stop Broker
[mqm@localhost ~]$ mqsistop Brk01Verify
BIP8071I: Successful command completion.

If you wish to remove a broker, you can, however it is not necessary as the installer will remove the broker. I sometimes remove the broker manually first, the reason for this is to ensure that the broker’s trace logs and other pertinent running foot prints are cleared from the file-system. At broker creations, It is possible to specify a file-location other than the standard default, so removing the broker helps you understand how to clean up your system

  • Remove Broker

If you remove a broker by just using the command mqsideletebroker it will only remove the broker, not the queue manager associated. To remove the broker, the QM and trace files use the following command

[mqm@localhost ~]$ mqsideletebroker Brk01Verify -q -w
Waiting for queue manager ‘QMVerify02’ to end.
WebSphere MQ queue manager ‘QMVerify02’ ended.
WebSphere MQ queue manager ‘QMVerify02’ deleted.
BIP8071I: Successful command completion.


  • Re-verify Broker Status


[mqm@localhost ~]$ mqsilist
\BIP1281I: No brokers have been defined on this machine.
BIP8071I: Successful command completion.

Check for running Queue Manager(s)

We can also check for the existence and the state of any WMQ Queue Managers, that we will want to clear when WMQ is uninstalled. You may choose to not remove WMQ, so you can skip this step if you wish to keep WMQ installed.

  • List Queue Manager(s)
[mqm@localhost ~]$ dspmq
[mqm@localhost ~]$

In the example above we can see that the sdpmq command returns empty, so this means that on this machine, there are no Queue Mangers. If there are, then follow the steps below to stop and remove the QMgr’s

Let’s say that we have a QM called QMVerify1, the steps to stop the QM and remove it are listed below.

  • Check Status of Queue Manager(s)
[mqm@localhost ~]$ dspmq
  • Stop Queue Manager(s)
[mqm@localhost ~]$ endmqm QMVerify1
Quiesce request accepted. The queue manager will stop when all outstanding work
is complete.
  • Re-check QM status
[mqm@localhost ~]$ dspmq
QMNAME(QMVerify1) STATUS(Ended normally)
  • Remove Queue Manager (s)
[mqm@localhost ~]$ dltmqm QMVerify1
WebSphere MQ queue manager ‘QMVerify1’ deleted.

Stop running instances of Installation Manager

To check for running instances of Installation Manager (IM) we can use the ps command as root user to list running IBMIM processes

  • Find IM processes
ps -ef | grep InstallationManager


[root@localhost opt]# ps -ef | grep InstallationManager
root 3080 6840 0 10:31 pts/2 00:00:00 grep –color=auto InstallationManager
root 4141 1 0 Feb17 ? 00:02:06 /opt/IBM/InstallationManager/eclipse/jre_6.0.0.sr9_20110208_03/jre/bin/java -Xms40m -Xmx512m -Xquickstart -Xgcpolicy:gencon -jar /opt/IBM/InstallationManager/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar -os linux -ws gtk -arch x86 -showsplash -launcher /opt/IBM/InstallationManager/eclipse/IBMIM -name IBMIM –launcher.library /opt/IBM/InstallationManager/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.200.v20120522-1813/ -startup /opt/IBM/InstallationManager/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar –launcher.overrideVmargs -exitdata 23e800a -toolId ibmim -accessRights admin -vm /opt/IBM/InstallationManager/eclipse/jre_6.0.0.sr9_20110208_03/jre/bin/java -vmargs -Xms40m -Xmx512m -Xquickstart -Xgcpolicy:gencon -jar /opt/IBM/InstallationManager/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
You have new mail in /var/spool/mail/root

Stop running instances of IBMIM using root

  • Kill the process IDs

You can either kill the application, or lose it in a desktop GUI (if the machine is a desktop)

[root@localhost opt]# kill -9 3080 4141

Stop running instances of Integration Toolkit Manager

Find running instances of the IBM Integration Toolkit, by using ps and grep

  • Locate the running instances
[root@localhost IntegrationToolkit90]# ps -ef | grep IntegrationToolkit


root 3568 9379 0 10:33 ? 00:00:00 /bin/bash /opt/IBM/IntegrationToolkit90/launcher -product
root 3829 3807 7 10:33 ? 00:00:05 /opt/IBM/IntegrationToolkit90/jdk/jre/bin/javaw -Xquickstart -Xms40m -Xmx1024m -Xmnx64m -Xgcpolicy:gencon -Xscmx96m -Xshareclasses:name=IBMSDP_%u -Xnolinenumbers -XX:MaxPermSize=256M -Xmaxf0.1 -Xminf0.05 -Xverify:none -jar /opt/IBM/IntegrationToolkit90//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -os linux -ws gtk -arch x86 -showsplash -launcher /opt/IBM/IntegrationToolkit90/eclipse -name Eclipse –launcher.library /opt/IBM/IntegrationToolkit90//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.2.R36x_v20101019_1345/ -startup /opt/IBM/IntegrationToolkit90//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -exitdata 2ce0006 -install /opt/IBM/IntegrationToolkit90 -product -vm /opt/IBM/IntegrationToolkit90/jdk/jre/bin/javaw -vmargs -Xquickstart -Xms40m -Xmx1024m -Xmnx64m -Xgcpolicy:gencon -Xscmx96m -Xshareclasses:name=IBMSDP_%u -Xnolinenumbers -XX:MaxPermSize=256M -Xmaxf0.1 -Xminf0.05 -Xverify:none -jar /opt/IBM/IntegrationToolkit90//plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
root 4164 6840 0 10:34 pts/2 00:00:00 grep –color=auto IntegrationToolkit

Kill the process as root, or close the GUI using a XSession (if a desktop is being used)

Kill process ID’s

[root@localhost IntegrationToolkit90]# kill -9 3568 3829

Uninstalling the IBM Integration Toolkit

Because the IB Toolkit was installed as part of Integration Bus for developers, IBM Installation Manager was used, so you can manually uninstall the Integration Toolkit using the IM GUI. But since we are focusing on silent-command-line approaches, we will issue a command-line command to uninstall Integration Toolkit.

Navigate to the uninstallation directory and prepare to run the following script with the correct path:

Linux platform package_group_dir/uninstall/
  • Execute the uninstall script

When the process completes, check the log file for errors. The file YYYYMMDD_TIME.xml is written to the following directory:

Linux platform /var/ibm/InstallationManager/logs.
  • Restart your computer to complete the uninstallation of the IBM Integration Toolkit.
  • Delete the uninstallation directory (/opt/IBM/IntegrationToolkit) if it still exists.

Uninstalling the IBM Integration Explorer

We can now also uninstall the Integration Explorer

  • Navigate to the uninstallation directory. The default location on Linux is
  • Run the ./Uninstall_IBM_Integration_Explorer script
  • Review the logs to ensure the uninstall completed successfully
  • Delete any remaining directories

Uninstalling IBM Installation Manager

To uninstall IBM Installation Manager (IBMIM), we can use the several commands. Depending on the user that was used to install the application, we can use the following syntax:


  • On Linux and UNIX systems, for an administrator: uninstall –launcher.ini silent-uninstall.ini
  • On Linux and UNIX systems, for a non-administrator: uninstall –launcher.ini

Note: The installation path above, is presumed to be the default path, please change as required.

Since we installed IBM Integration Bus for Developers using root, we will use the root user again to remove it.

  • Issue the uninstall command
/var/ibm/InstallationManager/uninstall/uninstall –launcher.ini silent-uninstall.ini


[root@localhost uninstall]# /var/ibm/InstallationManager/uninstall/uninstall –launcher.ini silent-uninstall.ini
Uninstalled from the /opt/IBM/InstallationManager/eclipse directory.
  • Remove any residual unneeded directories in the /opt/IBM folder.

Uninstalling WMQ

You can leave WMQ installed, for another/new instance of IIB, however if you choose to remove WMQ, we will resort to the standard approach to a WMQ uninstall, which is quote universal.

We presume you have already stop all WebSphere MQ applications associated with the installation you are uninstalling and end any WebSphere MQ activity associated with the installation you are uninstalling:

  • Log in as root.

Uninstall WebSphere MQ using the rpm command:

On a system with a single installation instance, we find out the names of the packages (components) currently installed on the Linux system.

  • Run the following grep command to locate rpms
rpm -qa | grep MQSeries


[root@localhost WebSphere_MQ]# rpm -qa | grep MQSeries





























Remove all the components at the same time by appending all the package names to the rpm command arguments. For example, to remove the runtime, Server and SDK components enter the following command:

rpm -ev MQSeriesRuntime MQSeriesServer MQSeriesSDK etc

  • Run the following command(s) in order to remove all WMQ rpms
packages=rpm -qa | grep MQSeries | awk '{ print $1 }' | tr '\n' ' '
echo $packages
rpm -ev $packages

The following command above, will search for WMQ rpms, then call rpm –ev to remove them all. Essentially is takes the output of the rpm -qa | grep MQSeries which results in a new line separated output, then replaces the new line with space, and thus we can remove all the rpms with one command.


In this chapter, we have learned how to uninstall all the components of IIB9.0 silently on a Linux CentOS 7 server. The IIB 9.0 product we used for the initial install was the free demo known as IBM Integration Bus for Developers.

This module is a sample chapter which is included in the IIB 9.0 course which will be released Q1 2015. To learn more about the courses available from The Middleware Shop, please go to to see a full list of the current courses available.


Leave a Reply