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.

You 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:

  1. Installs the new product code.

  2. Creates the default profile.

    You can create additional profiles using any of these available methods:

    The only other way to create a profile is when installing with the installation wizard GUI. The wizard installs the product files and creates the selected profile.

 

Installing with a response file

  1. Copy the responsefile.nd.txt file from the WAS directory on the product disk to a place that you can easily identify on your system.

  2. Edit the file to customize the values for your installation.

  3. Save the file as myresponsefile.txt, for example.

  4. Start the installation. For example:

    install -options /tmp/WAS/myresponsefile.txt -silent
    
    

    install -options C:\temp\WAS\myresponsefile.txt -silent
    
    

  5. After the installation, examine the logs for success.

 

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

INSTCONFFAIL

Total installation failure.

INSTCONFSUCCESS

Successful installation.

INSTCONFPARTIALSUCCESS

Installation errors occurred but the installation is still usable. Additional information identifies the errors.
app_server_root/wasprofileprofile.log

  • Traces all events that occur during the creation of the named profile

  • Created when using the Profile Creation wizard or the wasprofile 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/wasprofile/wasprofile_delete_ profile.log

  • Traces all events that occur during the deletion of the named profile

  • Created when using the Profile Creation wizard or the wasprofile 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.
profile_root/logs/pctLog.txt Logs all profile creation events that occur when using the Profile Creation wizard

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\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.

Configuration action failed:

Unsuccessful ANT script configuration.

Configuration action succeeded:

Successful ANT script configuration.

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

  • The response file is in English and is intended to be copied and edited.

  • Edit this file directly with your flat file editor of choice.

  • All lines preceded by a hash mark (#) are comments.

  • The file must exist to perform a silent installation. The installation program reads this file to determine installation option values when you install silently.

  • Save the file in a location that you can identify when you specify the fully qualified path as part of the installation command.

  • If you do not specify a value for a property, the default value is used.

    Note that for the silentInstallLicenseAcceptance option, the default value of false prevents the installation from running.

  • If you are installing on a Windows platform, your user ID must belong to the administrator group and must have the advanced rights Act as part of the operating system and Log on as a service. If you select the following option when your user ID does not comply, the installation fails

    -OPT PROF_winserviceCheck="true"
    
    

  • Avoid using the following reserved folder names as values:

    Reserved names: Avoid using reserved folder names as field values. The use of reserved folder names can cause unpredictable results. The following words are reserved:

    • cells

    • nodes

    • servers

    • clusters

    • applications

    • deployments


Related information
Customizing the response file for a Network Deployment CIP Installing a CIP silently Preparing the operating system for product installation Directory conventions

 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
AIX is a trademark of the IBM Corporation in the United States, other countries, or both.