responsefile.nd.txt
Installing the product 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.
Verify that the required disk space is available.
See Preparing the operating system for product installation for more information.
Do not use the default response file that is shipped on the product disk to install the product because the value of the silentInstallLicenseAcceptance option is false. Copy the file to change the value to true.
Location of the response file
The sample options response file is named responsefile.nd.txt. The file is in the WAS directory on the product disk or the downloaded installation image.
We can also use an options response file named responsefile.nd.txt in the WAS directory of a customized installation package (CIP) produced by the Installation Factory.
Creating an operational environment
Installing a new installation of WebSphere Application Server Network Deployment with the response file creates an operational environment by default. The installer program:
Installing with a response file
Logging
The installation wizard and the Profile Creation wizard record installation events in the following log files.
Log files for WAS Network Deployment: The following table shows the installation logs, content, and indicators of success and failure for WAS Network Deployment for V6.1:
Table 1. Installation and profile creation logs for WebSphere Application Server products Log Content Indicators app_server_root/logs/log.txt Logs all installation events app_server_root/wasprofileprofile.log
app_server_root/logs/wasprofile/wasprofile_delete_ profile.log
profile_root/logs/pctLog.txt Logs all profile creation events that occur when using the Profile Creation wizard app_server_root\logs\instconfig.log (Not available on systems such as AIX or Linux) Logs the activities of ANT configuration scripts that run at the end of the installation procedure. Information that ISMP can log when it cannot start the Installation wizard
Verify or troubleshoot the installation if the app_server_root/logs/install/log.txt file or the profile_root/logs/pctLog.txt file does not contain a record of a problem, but problems exist. If the profile_root directory exists, the pctLog.txt file is in the logs directory. If the error happens early in the installation, look for the logs in the system temporary area. 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 pctLog.txt file is in the USER_HOME directory and is named .$~pctLog.txt. 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 the installer from starting the installation wizard. Such an event is not enough disc space to launch the installation wizard, for example. If your installation fails and there is no information in the installation logs, use the -log parameter to record entries for events that cause the installer program to fail to start the installation wizard. The syntax of the install command for logging such events is
install -options fully_qualified_options_response_file_name -silent -log # !fully_qualified_log_file_name @ALL
install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt @ALL
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt @ALL
install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt @ALL
See Troubleshooting installation for more information.
Installation type options and options for profiles
Options that use to install silently vary according to the installation task that you are performing:
- installNew
- addFeature
Options for creating profiles vary according to the profile that you are creating:
- Cell
- Deployment manager
- Stand-alone application server
- Custom
- None
Options for a new installation
-OPT silentInstallLicenseAcceptance= -OPT installType="installNew" -OPT feature= -OPT installLocation="/QIBM/ProdData/WebSphere/AppServer/V61/<edition>" -OPT defaultProfileLocation="/QIBM/UserData/WebSphere/AppServer/V61/<edition>"Options for creating a cell
-OPT allowNonRootSilentInstall="false" -OPT feature="samplesSelected" -OPT installLocation="/opt/IBM/WebSphere/AppServer" -OPT createProfile="true" -OPT profileType="cell" -OPT silentInstallLicenseAcceptance="true" -OPT traceFormat=ALL -OPT traceLevel=INFO -OPT PROF_appServerNodeName= -OPT PROF_appServerProfileName= -OPT PROF_cellName= -OPT PROF_defaultPorts= -OPT PROF_dmgrProfileName= -OPT PROF_enableAdminSecurity="false" -OPT PROF_hostName= -OPT PROF_isDefault= -OPT PROF_nodeName= -OPT PROF_nodeOmitAction= -OPT PROF_omitAction= -OPT PROF_portsFile= -OPT PROF_profilePath= -OPT PROF_serverName= -OPT PROF_startingPort= -OPT PROF_validatePorts= -OPT PROF_webServerCheck= -OPT PROF_webServerHostname= -OPT PROF_webServerInstallPath= -OPT PROF_webServerName= -OPT PROF_webServerOS= -OPT PROF_webServerPluginPath= -OPT PROF_webServerPort= -OPT PROF_webServerType= -OPT PROF_winserviceAccountType= -OPT PROF_winserviceCheck= -OPT PROF_winservicePassword= -OPT PROF_winserviceStartupType= -OPT PROF_winserviceUserName=Options for creating a deployment manager
-OPT allowNonRootSilentInstall="false" -OPT feature="samplesSelected" -OPT installLocation="/opt/IBM/WebSphere/AppServer" -OPT createProfile="true" -OPT profileType="deploymentManager" -OPT silentInstallLicenseAcceptance="false" -OPT traceFormat=ALL -OPT traceLevel=INFO -OPT PROF_cellName= -OPT PROF_defaultPorts= -OPT PROF_enableAdminSecurity="false" -OPT PROF_hostName= -OPT PROF_isDefault= -OPT PROF_nodeName= -OPT PROF_omitAction= -OPT PROF_portsFile= -OPT PROF_profileName= -OPT PROF_profilePath= -OPT PROF_serverName= -OPT PROF_startingPort= -OPT PROF_validatePorts= -OPT PROF_winserviceAccountType= -OPT PROF_winserviceCheck= -OPT PROF_winservicePassword= -OPT PROF_winserviceStartupType= -OPT PROF_winserviceUserName=Options for creating a stand-alone application server cell
-OPT feature="samplesSelected" -OPT installLocation="/QIBM/ProdData/WebSphere/AppServer/V61/<edition>" -OPT createProfile="true" -OPT defaultProfileLocation="/QIBM/UserData/WebSphere/AppServer/V61/<edition>" -OPT profileType="standAlone" -OPT silentInstallLicenseAcceptance="true" -OPT traceFormat=ALL -OPT traceLevel=INFO -OPT PROF_cellName= -OPT PROF_defaultPorts= -OPT PROF_enableAdminSecurity="false" -OPT PROF_hostName= -OPT PROF_isDefault= -OPT PROF_nodeName= -OPT PROF_omitAction= -OPT PROF_portsFile= -OPT PROF_profileName= -OPT PROF_profilePath= -OPT PROF_serverName= -OPT PROF_startingPort= -OPT PROF_validatePorts= -OPT PROF_webServerCheck= -OPT PROF_webServerHostname= -OPT PROF_webServerInstallPath= -OPT PROF_webServerName= -OPT PROF_webServerOS= -OPT PROF_webServerPluginPath= -OPT PROF_webServerPort= -OPT PROF_webServerType= -OPT PROF_winserviceAccountType= -OPT PROF_winserviceCheck= -OPT PROF_winservicePassword= -OPT PROF_winserviceStartupType= -OPT PROF_winserviceUserName=Options for creating a custom profile
-OPT allowNonRootSilentInstall="false" -OPT feature="samplesSelected" -OPT installLocation="/opt/IBM/WebSphere/AppServer" -OPT createProfile="true" -OPT profileType="custom" -OPT silentInstallLicenseAcceptance="true" -OPT traceFormat=ALL -OPT traceLevel=INFO -OPT PROF_cellName= -OPT PROF_dmgrAdminPassword= -OPT PROF_dmgrAdminUserName= -OPT PROF_dmgrHost= -OPT PROF_dmgrPort= -OPT PROF_enableAdminSecurity="false" -OPT PROF_hostName= -OPT PROF_isDefault= -OPT PROF_nodeName= -OPT PROF_omitAction= -OPT PROF_profileName= -OPT PROF_profilePath= -OPT PROF_serverName=
Option descriptions
Related information
Customizing the response file for a Network Deployment CIP Installing a CIP silently Preparing the operating system for product installation Directory conventions