Install a CIP silently

Install a CIP silently

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, use the response file. To install silently, accept the license agreement in the agreement option.
You can install a customized installation package (CIP) that includes a WAS product and one or more maintenance packages and other customizations. The Installation Factory must create a CIP before you can install the CIP. See Developing and installing customized installation packages 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 ND. The scenarios describe typical topologies for the product.

Overview

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. 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. See your Windows documentation for more information.

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.
Copy the response file as myoptionsfile to your disk drive and customize it.
See Customizing the response file for a ND CIP.
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.
Issue the proper command to use your custom response file. For example, issue a command such as the following:

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

"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:
Table 1. Installation and profile creation logs for WAS ND

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.

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 Profile Management tool or 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.

Log more information when InstallShield MultiPlatform (ISMP) cannot start the installation wizard.
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:
./install -is:javaconsole
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 a CIP to continue the installation and configuration of your system.

Customizing the response file for a ND CIP

Related information

Installing a CIP

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.
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 Profile Management tool or 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.