Installing silently

Perform a silent, or background, installation of the feature pack by using a response file. Instead of displaying a graphical user interface, the silent installation causes the installation program to read all of your responses from this file that you provide. The response file passes command-line options to the installation program. An example response file, responsefile.wbmpsfep.txt, is supplied with default values that you must customize.

Before you begin
This task covers installing silently. There are alternative routes to installing the feature pack: Ensure that you are installing the feature pack on a supported WebSphere Business Process Management version 6.2.0.1 product. You can apply the feature pack to installations of the following products:
  • WebSphere Process Server version 6.2.0.1 or later.
    Restriction: You cannot apply the feature pack to an installation of the WebSphere Process Server Client.
  • WebSphere Enterprise Service Bus version 6.2.0.1 or later.
  • WebSphere Business Modeler Publishing Server version 6.2.0.1 or later.
  • WebSphere Business Monitor version 6.2.0.1 or later.
You can apply the feature pack to single- or stacked-product installations.
Important: The installed product or products must be at version 6.2.0.1 or later.
The operating system requirements for the feature pack are the same as for the underlying product. For more information on the hardware and software required by products, see the following Web pages:

Download and extract the feature pack.

For example, create two directories, fep_download and fep_installation_image. Then, download the feature pack to the fep_download directory and extract the downloaded file to the fep_installation_image directory. Do not move any files out of the fep_installation_image directory. After extraction, the fep_installation_image directory contains the directory WBMPSFEP, which contains the install executable file.

On Windows Vista and Windows Server 2008 operating systems: Performing a silent installation of the feature pack on these operating systems requires administrator privileges. If you start the silent installation using standard user privileges, you are presented with an elevation prompt for administrator privileges before you are allowed to continue. You can avoid this prompt by running the silent installation from a Command Prompt window that is opened by performing the following actions:
  1. Right click a Command Prompt shortcut.
  2. Click Run As Administrator.
About this task
The feature pack includes sets of widgets that you can use with Business Space powered by WebSphere, depending on the WebSphere product that you have installed. Widgets are grouped into the following features:
  • Business Leader feature: Contains the EAR files and the deployment and removal scripts for other features.
  • Business Leader widgets: Contains the new tools. These tools include enhanced methods for monitoring your business environment, setting actions to improve your business position and define metrics to monitor progress towards these goals..
The WebSphere Business Process Management products included in the installation to which you apply the feature pack determine which of the features can be installed.
Table 1. Installable features based on underlying products
Products in the chosen installation Which features will be installed
  • WebSphere ESB by itself.
  • WebSphere Process Server by itself.
  • WebSphere Business Monitor by itself
  • or a combination of these products in an installation.
Business Leader widgets.
  • WebSphere Business Modeler Publishing Server by itself.
  • WebSphere Business Modeler Publishing Server or a combination of the BPM products with Publishing Server
Business Leader widgets and Business Leader feature
  1. Log on to the system.
    • On AIX, HP-UX, Linux and Solaris operating systems:

      Log on as root or as the non-root user ID that installed the product to which you want to apply the feature pack.

      Run the ls -al command at the root of the installation to find the user ID that was used to install the product.

    • On Windows operating systems:

      Log on as a user who belongs to the administrator group or as the non-administrator user ID that installed the product to which you want to apply the feature pack.

  2. Copy the responsefile.wbmpsfep.txt file located in the WBMPSFEP directory of the extracted installation image to another location.
  3. If you have not already done so, read the IBM International Program License Agreement. It is located in the following directory:
    • On AIX, HP-UX, Linux and Solaris operating systems:
      /WBMPSFEP/lafiles
    • On Windows operating systems:
      \WBMPSFEP\lafiles
    If you agree to the terms of the agreement, continue with the installation process.
  4. Edit the copy of the response file using a flat file editor of your choice on the target operating system, customizing it with the parameters for your system. Read the directions in the response file to choose appropriate values for all of the options you must set for your specific silent installation.
    Important: On AIX operating systems. To prepare the file for a silent installation on AIX, use UNIX line-end characters (0x0D0A) to end each line of the response file. The safest method of preparing the file is to edit the file on the target operating system.
    You can modify all of the parameters in the response file, but pay attention to the following options and values:
    • Change the silentInstallLicenseAcceptance option value in the file to a value of "true". Leaving it with a value of "false" causes the installation to fail. For example:
      -OPT silentInstallLicenseAcceptance="true"
    • If you are installing as a non-root or non-administrator user ID, the installation will not be registered with the operating system. You must accept this limitation in order to install. Do this by uncommenting the allowNonRootSilentInstall option and leaving it with a value of "true". For example:
      -OPT allowNonRootSilentInstall="true"
    • Select the installation to which you want to apply the feature pack by setting the installLocation option. In the following example, install_root is the directory path to your WebSphere Business Modeler Publishing Server installation:
      -OPT installLocation="install_root"
      The installation must be listed in the NIF registry. If you are installing as a non-root or non-administrator user, be sure you have write permission to the install_root directory.
      Restriction: You cannot install the feature pack on a WebSphere Process Server Client installation. If you set the installLocation option to a WebSphere Process Server Client installation location, the feature pack installation fails.
  5. Start the feature pack installation program by running the install command in the WBMPSFEP directory of the feature pack installation image. In the following example commands, path/my_responsefile.wbmpsfep.txt represents the fully qualified path of the response file that you edited:
    • On AIX, HP-UX, and Solaris operating systems:
      /WBMPSFEP/install.sh -options path/my_responsefile.wbmpsfep.txt -silent 
    • On Linux operating systems:
      /WBMPSFEP/install -options path/my_responsefile.wbmpsfep.txt -silent 
    • On Windows operating systems:
       \WBMPSFEP\install.exe -options path\my_responsefile.wbmpsfep.txt -silent
Results
The installer installs the feature pack and records installation events in the installation log file. Verify the success of the installation by examining this file located as follows:
  • On AIX, HP-UX, Linux and Solaris operating systems:
    install_root/logs/WBMPSFEP/install/log.txt
  • On Windows operating systems:
    install_root\logs\WBMPSFEP\install\log.txt

If this log file contains the string INSTCONFSUCCESS on the last line, then the installation was successful. Other strings, such as INSTCONFPARTIALSUCCESS or INSTCONFFAILED, can occur on other lines in the file, or even on the last line, but if INSTCONFSUCCESS is included in the last line, the installation was successful.

If the string INSTCONFPARTIALSUCCESS or INSTCONFFAILED appears in the last line of the file without INSTCONFSUCCESS, problems were detected during installation. INSTCONFPARTIALSUCCESS indicates that the installation completed but errors were generated; INSTCONFFAILED means that the installation failed completely. In either case, the log file provides information to troubleshoot the problems.

Tip: If you are logged in as a non-root or non-administrator user, you might not find a log in the install_root/logs/WBMPSFEP/install/ directory after a failed installation attempt. When the installer runs, a log file is created in your user home directory. If the installation fails, the installer attempts to move the log to the install_root directory; however, without the necessary permission to move the file to the install_root directory, the attempt fails and the log remains in your home directory. Look for the log.txt file in the user_home/WBMPSFEP directory.
What to do next
Run the deployment scripts associated with the features you installed. These scripts enable functions provided by the feature pack. See Deploying and configuring widgets for the feature pack for more information.