Installing a customized installation package (CIP) using silent
installation refers to using a 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 use the response file. To install
silently, you must accept the license agreement in the agreement option.
Before you begin
You can install a customized installation
package (CIP) that includes a WebSphere Application Server product and one
or more maintenance packages and other customizations. The Installation Factory
must create a CIP before you can install the CIP. See IBM Installation Factory for WebSphere Application Server for
more information about creating a customized installation package (CIP).
Knowing what component to install
and in what order to install the component are important considerations. At
some time before starting this installation, see Planning to install the Feature Pack for Web Services. The
scenarios describe typical topologies for the product.
Note on silently installing WebSphere Application Server on Microsoft® Windows Vista™ and Windows 2008 operating systems: Performing a silent installation
of Websphere Application Server Version 6.1 on a machine running these operating
systems requires Administrator privileges. If you launch 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:
- Right-click a Command Prompt shortcut.
- Click Run As Administrator.
About this task
Use this procedure to perform a silent installation of the product.
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.
Procedure
- The operating system
requirements for a feature pack are the same as for a Version 6.1 application
server installation. However, you need to ensure that you have enough free
disk space to install the feature pack and the included maintenance onto the
application server installation.
- 1450 MB of free space available in your target installation directory
for the feature pack and included maintenance. This is in addition to the
required Version 6.1 application server product.
- 600 MB of free space available in your temporary directory
- Copy the response file as myoptionsfile.txt to
your disk drive and customize it. You should copy the file into the same directory
as the existing response file for ease of use.
See Customizing the response file for a feature pack CIP.
The
name of the original file is responsefile.WEBSV.txt.
- Change to the directory of the CIP that contains the install command
and run the command using your custom response file.
For example, if you saved
myoptionsfile.txt into the same directory as the original response file, change
into the WEBSV directory and issue a command such as the following:
./install -options myoptionsfile.txt
-silent
install -options myoptionsfile.txt -silent
install.exe -options myoptionsfile.txt -silent
Results
The installation
wizard installs the feature pack and records installation events in the installation
log files in the app_server_root/logs/install/webservices directory.
![[AIX HP-UX Linux Solaris Windows]](../../dist.gif)
Certain events can
prevent ISMP from starting the Installation wizard. Such an event is not enough
disk space to launch the Installation wizard for example. If your installation
fails and there is no information in the installation logs, use the
-is:javaconsole parameter
to record entries for events that cause the ISMP program to fail to start
the installation wizard. The syntax of the
install command
for observing such events is:
./install -is:javaconsole
install.exe -is:javaconsole
Avoid trouble: Although
the usage of
-is:javaconsole is supported, the usage of
-console,
for example
install -console, is not supported.
gotcha
What to do next
Go to Installing a CIP to
continue the installation and configuration of your system.