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 Network Deployment. The
scenarios describe typical topologies for the product.
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
- Log on to the operating system.
![[Windows]](../../windows.gif)
When installing on a Windows
® system, a Windows service is automatically created
to autostart the application server if your installer user account
has the following advanced user rights:
- Act as part of the operating system
- Log on as a service
For example, on some Windows systems,
click
Administrative Tools > Local Security Policy > User
Rights Assignments to set the advanced options. See your Windows documentation for more
information.
If you
plan to run the application server as a Windows service, do not install from a user
ID that contains spaces. A user ID with spaces cannot be validated.
Such a user ID is not allowed to continue the installation. To work
around this problem, install with a user ID that does not contain
spaces.
- 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.
- Change to the directory of the CIP that contains the install command
and run the command using your custom response file.
./install -options myoptionsfile.txt
-silent
install -options myoptionsfile.txt -silent
install.exe -options myoptionsfile.txt -silent
Results
The installation wizard
and the Profile Management tool record installation
events in the following log files:
Table 1. Installation
and profile creation logs for WebSphere Application Server Network Deployment
Log |
Content |
Indicators |
app_server_root /logs/install/log.txt |
Logs all installation events |
- Return code
- Meaning
- 0
- Success
- 1
- Failure
- 2
- Partial Success
|
app_server_root/logs/manageprofiles/profile_name_create.log |
- Traces all events that occur during the creation of the named profile
- Created when using the Profile Management tool or
the manageprofiles command
|
- INSTCONFFAIL
- Total profile creation failure.
- INSTCONFSUCCESS
- Successful profile creation.
- INSTCONFPARTIALSUCCESS
- Profile creation errors occurred but the profile is still functional.
Additional information identifies the errors.
|
user_data_root/profileRegistry/logs/manageprofiles/create.log |
- Traces all events that occur during the creation of the named profile
Created when using the Profile Management tool or
the manageprofiles command
Created when using the manageprofiles command
|
- INSTCONFFAIL
- Total profile creation failure.
- INSTCONFSUCCESS
- Successful profile creation.
- INSTCONFPARTIALSUCCESS
- Profile creation errors occurred but the profile is still functional.
Additional information identifies the errors.
|
app_server_root/logs/manageprofiles/profile_name_delete.log |
- Traces all events that occur during the deletion of the named profile
Created when using the manageprofiles command
|
- INSTCONFFAIL
- Total profile deletion failure.
- INSTCONFSUCCESS
- Successful profile deletion.
- INSTCONFPARTIALSUCCESS
- Profile deletion errors occurred but the profile is still deleted. Additional
information identifies the errors.
|
app_server_root/logs/install/
installconfig.log.gz |
- Logs the activities of ANT configuration scripts that run at the end of
the installation procedure
- Gzip file
|
- Configuration action failed:
- Unsuccessful ANT script configuration.
- Configuration action succeeded:
- Successful ANT script configuration.
|
app_server_root/logs/install/
installconfig.log |
- Logs the activities of ANT configuration scripts that run at the end of
the installation procedure
|
- Configuration action failed:
- Unsuccessful ANT script configuration.
- Configuration action succeeded:
- Successful ANT script configuration.
|
If
the profile_root directory
does not exist, the pmt.log file is in the USER_HOME
directory. Issue the env command to display the USER_HOME
directory on operating systems such as AIX or Linux. See the environment variable
settings on Windows system to display the value of the variable.
![[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
Ensure that you have at least
250 MB free in your temporary directory before attempting to install WebSphere
Application Server.
What to do next
Go to Installing a CIP to
continue the installation and configuration of your system.