WebSphere Message Brokers
File: ah20602_
Writer: Kate Hostler

Reference topic

This build: July 31, 2007 21:30:25

Modes of installation and uninstallation

You can specify different modes for installation and uninstallation of runtime components and the Message Broker Toolkit.

Three modes are supported:

In this topic installer and uninstaller, used in example commands, denote where you must enter the specific names of the installation or uninstall wizard. For the names of the installation and uninstall wizards, and full details of these tasks, see the Installation Guide and Uninstalling.

Graphical mode

The installation and uninstallation wizards start in graphical mode if you invoke them with no options (the default mode). The wizards guide you through the installation or uninstallation process with a series of dialogs that present options and defaults. You can accept the default values, or change them to suit your environment and requirements.

This mode provides the highest level of information and guidance to help you complete installation or uninstallation. Use this mode when you are unfamiliar with the product, or if you want to monitor the installation or uninstallation progress.

If you click Cancel before the Install Progress or Uninstall Progress panel appears, you can exit the setup. If you choose to exit, your system returns to its state before launching the wizard. However, if you cancel the installation wizard after installation or uninstallation has completed, and the final summary panel is displayed, your system is not restored to its previous state: the installation wizard stops immediately. If you want to remove any program that has been installed, invoke the uninstallation wizard.

When you use the wizards, you might have to wait a few seconds to move to the next panel after clicking Next >. Progress is not always displayed on all panels. If you click Next > twice, you might skip an entire panel. To ensure the installer or uninstaller is progressing, you can monitor your CPU usage which increases greatly during both installation and uninstallation.

Console mode

Console mode presents a text-based interface with which you interact in a command window. It presents the same options as the graphical interface; you can choose values, and navigate through the process, using the keyboard only.

Start of changeThis mode is not available for installing or uninstalling the Message Broker Toolkit, nor for applying or removing service. All these operations are implemented by Installation Manager, for which only graphical and silent modes are supported.End of change

Use console mode if you want a command line rather than a graphical interface. This interface is also suitable for users with accessibility considerations; for example, those who use only the keyboard to choose values and navigate through installation, and those with screen reader software such as JAWS.

Invoke the installer using the following command. Use the same format for the uninstaller.

installer -console
Use these prompts to navigate through the installation:
  • 1 Move to the next panel
  • 2 Return to the previous panel
  • 3 Cancel and terminate the install program
  • 4 Redisplay the current screen

The default option is always displayed within brackets, for example [1]. If this is the correct choice, press Enter to continue.

Silent mode

If you invoke a silent installation or uninstallation, the wizard runs without any interaction. In this mode, the process is completed with default options, or according to a predefined set of options, as described below.

Use this unattended interface for automated installation or uninstallation over a large number of identical systems.

Silent mode does not provide any feedback to the caller, therefore you must view the log to check whether the action was successful.

You can perform a silent installation in the following ways:
  • With default settings.
    For example, for installation this results in these actions:
    • Check that prerequisite software is installed (runtime components only).
    • Install to the default directory.
    • Install all selectable features.

    Because the installation wizard for the runtime components checks for prerequisite software in silent mode, the program fails if the prerequisite software is not already installed. You can override this check if you use a response file (see Using response files), or include the appropriate parameter with a non-default value on the command invocation.

    To run a default silent installation, specify the -silent option on the command. For example, to install runtime components on Linux (x86 platform), enter the following command:
    setuplinuxia32 -silent 
  • With one or more non-default settings.

    If you want the installation wizard to use non-default values for one or more values, you can either specify non-default options on the command invocation, or specify a response file, as described in Using response files. The Installation Guide also provides further details about working with response files.

    A sample response file for the installation of the runtime components is provided in the sample-scripts directory of the root CD directory. This file includes detailed information about the options that you can change, and the values that you must enter to change them. You can tailor this file to your requirements, or you can generate a new response file, as described below.

    To run a tailored silent installation using a response file called response1.txt, specify the -silent option and the filename on the installation command. For example, on Linux (x86 platform), enter the following command:
    setuplinuxia32 -silent -options response1.txt
Related tasks
Installing
Applying service to runtime components
Uninstalling runtime components
Uninstalling the Message Broker Toolkit
Related reference
Using response files
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:30:25

ah20602_ This topic's URL is: