Uninstalling runtime components in silent mode

Remove the runtime components without user interaction in silent mode .

Always use the WebSphere® Message Broker uninstall wizard to remove product components, unless otherwise stated. Do not use the uninstallation program that is provided by the operating system; for example, geninstall on AIX®, or swremove on HP-UX.

On HP-UX Version 11.23, and on Linux® on POWER™, a known restriction prevents the creation of the uninstall wizard. If this situation occurs, use the alternative command specified in these instructions. Also check the readme.html file to ensure that no additional operating systems are affected by this restriction.

You can remove WebSphere Message Broker without user interaction. This process is called unattended (or silent) removal. This topic describes how to run the uninstallation program silently without a response file; the program assumes all the default values.

If you want to complete a silent uninstallation, but have non-default requirements, you can use a response file. A response file is a text file that contains values for the options that you select when you uninstall WebSphere Message Broker. For more details of how to create, edit, and employ a response file to specify your requirements, see Using response files.

For information about silent mode and alternative modes available, see Modes of installation and uninstallation.

To start the uninstaller in silent mode, complete the following steps:

  1. Stop all running processes that use any part of WebSphere Message Broker (brokers, Configuration Manager, and the User Name Server) before you uninstall. Use the mqsilist (list resources) command to check which components are running. Stop each component using the mqsistop command.
  2. On Windows and Linux on x86, end any active sessions of the Message Brokers Toolkit.
  3. If you do not plan to reinstall on this computer, delete all the brokers (mqsideletebroker command), Configuration Managers (mqsideleteconfigmgr command), and User Name Servers (mqsideleteusernameserver command) that are associated with this installation. When you delete a component, all its associated data and resources are deleted; if you want to retain component data, do not delete that component.
  4. If you have created DB2® or Derby databases on Windows with the mqsicreatedb command, delete them with the mqsideletedb command. If you delete the last database, the Database Instance Manager is also deleted (the Database Instance Manager controls all appropriate databases in a single system; if you have another installation, this component might not be deleted if databases associated with the other installation remain). Databases created by the Default Configuration wizard can also be deleted in this way.
  5. Run the following command from outside the installation directory, specifying the full path (this method of invocation ensures that the full directory structure is removed during uninstallation):
    • On HP-UX systems that are running Version 11.23 only, and on Linux on POWER systems:
      /install_dir/_uninst_runtime_jvm/jre/bin/java -jar /install_dir/_uninst_runtime/uninstall.jar -silent
    • On all other operating systems:
      install_dir/_uninst_runtime/uninstaller -silent
    where install_dir is the home directory of your WebSphere Message Broker installation.

    If you accepted the default location during installation, this directory is as follows:

    • On Windows, C:\Program Files\IBM\MQSI\6.0
    • On AIX, HP-UX, and Solaris, /opt/IBM/mqsi/6.0
    • On Linux, /opt/ibm/mqsi/6.0
    The uninstallation program runs without interaction.
Related tasks
Uninstalling runtime components in graphical mode
Uninstalling runtime components in console mode
Related reference
mqsideletebroker command
mqsideleteusernameserver command
mqsilist (list resources) command
mqsistop command
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:05

ah18841_