Install silently

 

+

Search Tips   |   Advanced Search

 

 

Overview

Installing WAS ND 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.

This topic describes installing silently on any supported operating system.

Before starting this installation, see the following topics:

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. To specify non-default options during a silent installation, use the response file. To install silently, accept the license agreement in the agreement option.

 

Procedure

  1. Log on to the operating system.

    In addition, select a umask that would allow the owner to read/write to the files, and allow others to access them according to the prevailing system policy. For root, a umask of 022 is recommended. For non-root users a umask of 002 or 022 could be used, depending on whether or not the users share the group.

    To verify the umask setting,...

    umask

    To set the umask setting to 022,...

    umask 022

    When installing on a Windows system, a Windows service is automatically created to autostart the appserver 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.

    If you plan to run the appserver 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.

  2. Copy the response file as myoptionsfile to your disk drive and customize it.

    The name of the original file is responsefile.nd.txt. Do not add an options line to any of the profile creation response files that includes the following parameter:

    -silent

    The -silent parameter is not required. If it exists in any of the files, the file cannot create a profile during a silent product installation.

  3. Issue the proper command to use your custom response file. For example, issue a command such as the following:

    • *nix:

      mnt_cdrom/WAS/install -options /tmp/WAS/myoptionsfile.txt -silent

    • Windows:

      "disc_drive_D:\WAS\install" -options "C:\temp\WAS\myoptionsfile.txt" -silent

 

Results

The installation wizard and the Profile Management tool record installation events in the following log files:

Log Content Indicators
app_server_root/logs/install/log.txt Logs all installation events. For non-root installs could be located in $HOME
Return code Meaning
0 Success
1 Failure
2 Partial Success
app_server_root/logs/manageprofiles/profile_name_create.log

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

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.

If installing as non-root user, silent install is failing, and log.txt does not exist, check $HOME/vpd.properties and remove all references to WAS v6.1.

Log more information when InstallShield MultiPlatform (ISMP) cannot start the installation wizard.

Verify or troubleshoot the installation if the files...

...do not contain a record of a problem, but problems exist. If the error happens early in the installation, look for the logs in the system temporary area or in...

The installation program copies the logs from the system temporary area to the logs directory at the end of the installation.

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.

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:

For *nix...

./install -is:javaconsole

Windows...

install.exe -is:javaconsole

Ensure that you have at least 250 MB free in your temporary directory before attempting to install WAS.

 

What to do next

Go to Installing the product and additional software to continue the installation and configuration of your system.


Customizing the response file

 

Related Reference

install command

 

Related information

Installing the product and additional software