Installing a customized installation package (CIP) using
silent installation refers to using a response file to supply installation
options without user interaction. To configure the installation, change
the options in the response file before you issue the installation
command. Silent installation mode does not accept interactive installation
options. To specify non-default options during a silent installation,
you must edit the response file in advance. To install silently, you
must accept the license agreement in the agreement option.
About this task
You can install a customized installation package (CIP)
that includes WebSphere ESB and
one or more maintenance packages and other customizations. You must
create a CIP using the Installation Factory before you can install
it. See Creating customized installation packages for more information
about creating a customized installation package (CIP).
A silent
installation uses the installation wizard to install the product in
silent mode, without the graphical user interface. Instead of displaying
a wizard interface, the silent installation causes the installation
program to read all of your responses from a file that you provide.
Use
this procedure to perform a silent installation of the product.
Procedure
- Log on to the operating system.
On i5/OS® platforms: Ensure
that the user profile has *ALLOBJ and *SECADM special authorities.

On Linux® and UNIX® platforms: After
inserting the product media into the drive, some Linux and UNIX operating
systems require you to mount the drive.
- Copy the sample response file responsefile.wesb.txt from the WBI directory
of the CIP to a place that you can easily identify on your system
and save it with a new name, such as myoptionsfile.txt.
- Edit the file using a flat file editor of your choice,
on the target operating system, to customize it with the parameters
for your system. Read the directions contained within 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 parameters:
- Required: Make sure that you change the -OPT
silentInstallLicenseAcceptance parameter to a value of "true": -OPT
silentInstallLicenseAcceptance="true". Leaving it with a
value of "false" causes the installation to fail.
- Change the value of the -OPT wpsInstallType parameter
to designate one of the following types of installation:
- "typical": a full installation of WebSphere ESB that
allows you to optionally create a stand-alone server, deployment manager,
or custom profile during installation. This is the default.
- "ndGuided": a full installation of WebSphere ESB that
guides you through setting up a deployment environment, creating a
deployment manager based on a deployment environment pattern or defining
a deployment environment that you have previously created.
- If you perform a "typical" installation, you
must create a profile to have an operational WebSphere ESB environment.
You can create a profile silently by specifying certain values in
your response file that will create a profile during the installation
process. Change the value of the parameter -OPT profileType to
one of the following values:
- "deploymentManager": creates a profile with a
deployment manager. For example:
-OPT profileType="deploymentManager"
- "standAlone": creates a profile with a stand-alone
server. For example:
-OPT profileType="standAlone"
- "custom": creates a profile with an empty node,
which you can configure after installation.
-OPT profileType="custom"
- "none": does not create a profile during installation.
Use this value if you do not want to create a profile during the silent
installation process. After installation, you must run the Profile
Management Tool to create a profile.
-OPT profileType="none"
- If you want to create a profile for an existing installation,
comment out the -OPT installType="installNew" section
of your response file, remove the comments from the -OPT createProfile section
of the response file, and change the value of the parameter -OPT
createProfile to "true". For example:
#-OPT installType="installNew"
-OPT createProfile="true"
For more information about creating profiles silently,
see Creating profiles using the manageprofiles command.
- If you designated a deployment environment installation (-OPT
wpsInstallType="ndGuided"), you must designate additional
parameters to define that installation. Change the value of the -OPT
ndGuidedInstallType parameter to one of the following values:
Also, change the value of the parameter -OPT profileType to "none".
For
more information about deployment environments, see Introduction: Planning for WebSphere ESB and Implementing a deployment environment.
- To silently install a CIP on an existing installation (rather
than to create a new installation), set the -OPT installType parameter
to "installAndPatch" or "addFeature",
and the -OPT if_cip_modifyexistinginstall to
either "maintenanceOnly" (which installs only product
binaries and does not perform any profile customizations) or "customizationAndMaintenance" (which
performs profile customizations in addition to installing the product
binaries). For more on profile customizations, see Build Definition wizard: Profile customization panel.
Note: You can always review the default parameters and values
in the example response file responsefile.wesb.txt located in the WBI directory
on the WebSphere ESB media.
- Save your changes in your copy of the response file.
- Run the install command from either
the WebSphere ESB product
media or from the temporary location where you have saved the contents
of the electronic image from Passport Advantage® to install WebSphere ESB using
your custom response file. The command examples assume
that you have copied your response file into a temporary directory
and renamed it as myoptions.txt before customizing
the file.

On Linux and UNIX platforms: install
-options /tmp/WBI/myoptions.txt -silent
On Windows® platforms:
install.exe -options "C:\temp\WBI\myoptions.txt" -silent
On a System i® server (from a Qshell): INSTALL -options /tmp/WBI/myoptions.txt
-silent
Results
The installation wizard and (if you elect to create a profile
during installation) the Profile Management Tool record installation
events in various log files. See Installation and profile creation log files for
descriptions of these log files.