Perform a silent, or background, installation of the feature
pack from your System i® server
onto an existing installation of WebSphere® Process
Server or WebSphere Enterprise
Service Bus (WebSphere ESB),
version 6.2.0.1 or later, by using a file called a response file.
The silent installation uses your responses from this file. The response
file passes command-line options to the installation program. An example
response file, responsefile.wpswesbfep.txt, is
supplied with default values that you must customize.
Before you begin
Before starting this installation, complete the following
tasks:
- Ensure that you want to install on an i5/OS® system. For alternative installation
procedures, click the following links:
- To install on a Linux®, UNIX®, or Windows® system using an interactive interface,
see Installing the feature pack on Linux, UNIX, and Windows.
- To install on a Linux, UNIX, or Windows system silently by using a response
file, see Installing the feature pack silently on Linux, UNIX, and Windows.
- To install on a z/OS® system,
see Installing the feature pack on z/OS.
- Ensure that you install from a System
i server. You cannot install a feature pack remotely, for example
from a Windows workstation.
You must install a feature pack from a System i server using a local command-line
installation.
- Ensure that your user profile has *ALLOBJ and *SECADM special
authorities.
- Ensure that you install the feature pack on a supported WebSphere Business Process
Management, version 6.2.0.1 or later, product. You can apply the feature
pack to installations of the following products:
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 those for
the 6.2.0.1 product. For information about the hardware and software
that are required by products, see the following Web pages:
- Download the feature pack and extract the contents to an integrated
file system (IFS) directory on the System
i server from which you will perform the installation. For instructions
on downloading and extracting the feature pack, see the following Web site.
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 WPSWESBFEP, which contains
the install executable file.
About this task
The content of the feature pack is 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:
- Administration feature: The Administration widgets provide
a way for administrators to manage and monitor the individual components
-- including modules and services -- of your business process management
solution.
- Human Task Management feature: This feature includes two
sets of widgets. The Human Task Management widgets provide a way for
your business users and managers to easily view, assess, and drill
down into human tasks and business processes in your business process
management solution. The My Work Organizer widgets enable business
users and managers to quickly plan and organize their tasks.
A third feature, which is called the Feature Pack Business Space
widgets feature, is installed silently with every feature pack installation.
It contains the enterprise archive (EAR) files and the deployment
and removal scripts for the other features.
Procedure
- Log on to the System
i system with a user profile that has *ALLOBJ and *SECADM special
authorities.
- Copy the responsefile.wpswesbfep.txt file,
which is located in the WPSWESBFEP directory
of the extracted installation image, to another location.
- If you have not already done so, read the IBM® International Program License Agreement,
which is located in the WPSWESBFEP/lafiles directory. If you agree to the terms of the agreement, continue with the
installation process.
- Open the copy of the response file that you created in
step 2, and
customize it with the parameters for your system. 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, in particular, note 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"
- Specify whether to perform a new installation or add a feature
to an existing feature pack installation by setting the installType option
to one of the following values:
- installNew: Select this value to install
a new copy of the feature pack.
- addFeature: Select this value to add features
to an existing feature pack installation. This option can be used
only on installations where WebSphere Process
Server V6.2.0.1 is installed.
For example,
-OPT installType="installNew"
or
-OPT installType="addFeature"
- Specify 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 New Install Framework (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
fails.
- Set values for the administrationSelected and humanTaskManagementSelected options.
Valid values depend on whether you are applying the feature pack to
an installation of WebSphere Process
Server or WebSphere ESB.
Refer
to
Table 1 for
guidelines about choosing values for the
administrationSelected and
humanTaskManagementSelected options.
Important: If you select options that are not valid for an installation
(for example, if you select to install the Human Task Management feature
on a WebSphere ESB installation),
the feature pack installation fails.
Table 1. Installable features (based on underlying products)Product in the installation |
Which features can be installed |
How to set options in the response file |
WebSphere ESB
only |
- Administration
- Feature Pack Business Space widgets
|
|
WebSphere Process
Server only |
- Administration, Human Task Management, or both
- Feature Pack Business Space widgets
|
Alternatively, you can select to install just the Administration
feature or just the Human Task Management feature. In this case, set
only the value of the option you want to install to true. Important: You must install either the Administration feature
or the Human Task Management feature, or the installation will fail.
Tip: If you elect to install only one feature, you can rerun
the installer at a later time to install the other feature. If you
applied maintenance to the installed feature, to ensure that the fixes
are applied to the new feature, choose one of these methods: - Remove the existing maintenance from the feature pack before installing
the new feature, install the new feature, and reapply the maintenance.
- If a later maintenance package is available than the one that
is installed, install the new feature and install the higher-level
maintenance package on the feature pack.
|
- Invoke the installation program for the feature pack by
running the INSTALL command from the Qshell.
In the following example commands,
path/my_responsefile.wpswesbfep.txt represents
the fully qualified path of the response file that you edited:
- On a CL command line, issue the STRQSH command
to start the Qshell command shell.
- Change directories to the WPSWESBFEP subdirectory
of the extracted installation image and enter the install command
to start the installation program:
install -options path/my_responsefile.wpswesbfep.txt -silent
Important: Do not exit the Qshell session (press F3) 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 following log file: install_root/logs/wpswesbfep/install/log.txt.
When the setup program completes, press F3 to exit. If you rerun the
installer to install another 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.
Log file location after invalid installations: If you set the
installLocation option
to an invalid location (one that is not in the NIF registry), the
directory location in which the log file ends up depends on whether
the location actually exists:
- If the installation location does exist, the log file is copied
to that directory.
- If the installation location does not exist, the log file remains
in the directory user_home/wpswesbfeplogs.
What to do next
Run the deployment scripts that are associated with the
features that you installed. These scripts enable functions that are
provided by the feature pack. See Deploying and configuring widgets for the feature pack for more
information.
Installing another feature as you add WebSphere Process Server to an installation of WebSphere ESB: When you install WebSphere Process
Server to an installation of WebSphere ESB
that includes the feature pack, and you want to add the Human Task
Management feature from the feature pack, you must create a new response
file and rerun the feature pack installer using the procedure in this
topic. The version of WebSphere Process
Server you add must be 6.2.0.1 or later.
If you applied maintenance
to the installed feature pack, to ensure that the fixes are applied
to the feature you plan to install, choose one of these methods:
- Remove the existing maintenance from the feature pack before installing
the new feature, and reapply the maintenance.
- If a later maintenance package is available than the one that
is installed, install the new feature and install the higher-level
maintenance package on the feature pack.
Set the options in the new response file as follows:
- Set the silentInstallLicenseAcceptance option
to true:
-OPT silentInstallLicenseAcceptance="true"
- Set the installType option to addFeature:
-OPT installType="addFeature"
- Set the installLocation option to the installation
to which you want to apply the feature pack:
-OPT installLocation="install_root"
- Set the administrationSelected option to false (this
feature is already installed):
-OPT administrationSelected="false"
- Set the humanTaskManagementSelected option
to true:
-OPT humanTaskManagementSelected="true"
- Feature Pack Business Space widgets feature is already installed.
After you install the new feature, you must deploy it,
as described in Deploying and configuring widgets for the feature pack.