Removing IBM Websphere broker services on AIX, Linux, Solaris - Middleware News

Removing IBM Websphere broker services on AIX, Linux, Solaris

In some situations, you may want to remove broker services from a server where you install IBM® WebSphere® MQ and WebSphere Event Broker. Removing broker services involves deleting the queue manager, the configuration manager, the broker itself, and the database tables used for storing associated information.

Before you begin

There are several situations in which you may want to remove the broker services from a Linux® deployment; for example:

• When you want to replace the WebSphere Event Broker configuration (possibly to use different ports for the listeners)
• When you are uninstalling WebSphere MQ and WebSphere Event Broker, and you want to be sure you are leaving a clean configuration

Procedure

1. Log on to the server hosting WebSphere MQ and WebSphere Event Broker as root.
2. Remove the broker services as follows:
   1. Open the Message Broker Command Console..
   2. Navigate to the directory where you installed WebSphere Event Broker.
   3. Stop the message broker with the following command:

      su - mqsi -c "mqsistop broker_name"

      For example:

      su - mqsi -c "mqsistop BRKR_SCCS"

   4. Delete the message broker with the following command:

      mqsideletebroker broker_name

      For example:

      mqsideletebroker BRKR_SCCS

   5. Stop the configuration manager with the following command:

      su - mqsi -c "mqsistop config_manager_name"

      For example:

      su - mqsi -c "mqsistop CMGR_SCCS"

   6. Now delete the configuration manager with the following command:

      mqsideleteconfigmgr config_manager_name -n

      For example:

      mqsideleteconfigmgr CMGR_SCCS -n

      You will see a confirmation:

      BIP8071I: Successful command completion. 

      You can verify that the broker has been removed by ensuring that it no longer appears in the results when you run the following command:

      mqsilist

3. Remove the queue manager as follows:
   1. Open a terminal and navigate to the root of the WebSphere MQ installation.
   1. Stop the queue manager with the following command:

      su - mqsi -c 
        "/opt/mqm/bin/endmqm queue_manager_name"

      For example,

      su - mqsi -c 
        "/opt/mqm/bin/endmqm sccs.queue.manager"

      You will see a confirmation message:

      Quiesce request accepted. 
      The queue manager will stop when all outstanding work is complete.

   2. Delete the queue manager with the following command:

      dltmqm queue_name

      For example:

      dltmqm sccs.queue.manager

      You will see a confirmation message:

      WebSphere MQ queue manager 'sccs.queue.manager' deleted.

4. Still on the same server, remove the data source for WebSphere Event Broker as follows:
   1. Open the ODBC Tool by clicking Start > Programs > Administrative Tools > DataSources (ODBC).
   2. Click the System DSN - System Data Sources tab.
   3. Select the datasource that you created for WebSphere Event Broker, and then click Remove.
5. On the IBM DB2® server, open a DB2 Command Window and drop the database that stores WebSphere Event Broker data.
   Note: Make sure the database is not in use; all users must be disconnected from the database before the database can be dropped.
   For example, if your database is called BRKRDB:

   DB2 DROP DATABASE BRKRDB