Installing the feature pack on i5/OS from a System i server

Perform a silent, or background, installation of the feature pack directly from your System i® server onto an existing installation of a supported WebSphere® Business Process Management version 6.2.0.1 product by using a file called a response file. 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
Before starting this installation, complete the following actions:
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.
Only the Business Leader widgets are installed on System i.
  1. Log on to the System i system with a user profile that has *ALLOBJ and *SECADM special authorities.
  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 located in the WBMPSFEP/lafiles directory. If you agree to the terms of the agreement, continue with the installation process.
  4. Edit the copy of the response file. You can edit the file using a mapped drive and a text editor or by using the EDTF CL command from the i5/OS system command line. Read the directions in the response file to choose appropriate values for all of the options you must set for your specific silent installation. 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"
    • 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 Process Management product installation:
      -OPT installLocation="install_root"
      The installation must be listed in the NIF registry.
      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 will fail.
  5. Invoke the installation program for the feature pack by running the INSTALL command from the Qshell.
    In the following example commands, path/my_responsefile.wbmpsfep.txt represents the fully qualified path of the response file that you edited:
    1. On a CL command line, issue the STRQSH command to start the Qshell command shell.
    2. Issue the installation command from the WBMPSFEP subdirectory of the extracted installation image to start the installation program:
      install -options path/my_responsefile.wbmpsfep.txt -silent
      Important: Do not exit the Qshell session (PF3) until the installation has completed. Doing so might cause the installation to stop prematurely.
Results

The installer installs the feature pack and records installation events in the installation log file in the install_root/logs/wbmpsfep/install/log.txt directory. When the setup program completes, select F3 to exit. If you re-run the installer to install an additional feature, a new log.txt file is created and the existing one is appended with a number for example, log.txt.1.

You can verify the success of the installation by examining this log file. If it 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.

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.