[AIX HP-UX Linux Solaris Windows]This topic applies only on the i5/OS operating system.

responsefile.nd.txt

Installing WebSphere Application Server Network Deployment 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.

Verify that the required disk space is available.

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

[iSeries] The file is in the WAS directory on the product disc, the customized installation package (CIP), or the downloaded installation image.

Creating an operational environment

Installing the product 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:

Installing with a response file

  1. Copy the responsefile.WEBSV.txt file from the WEBSV directory of the feature pack installation image to a place that you can easily identify on your system.
  2. Copy the response file for the feature pack to a place that you can easily identify on your system. For the Web Services feature pack, copy the responsefile.WEBSV.txt file from the WEBSV directory. For the SOA feature pack, copy the responsefile.SOA.txt file from the SOA directory.
  3. Edit the file to customize the values for your installation.
  4. Save the file as myresponsefile.txt, for example.
  5. Start the installation. For example:
    [AIX] [HP-UX] [iSeries] [Linux] [Solaris]
    install -options /tmp/WAS/myresponsefile.txt -silent
    
    [Windows]
    install -options C:\temp\WAS\myresponsefile.txt -silent
    
    [iSeries]
    install -options /MYDATA/myresponsefile.txt
    
  6. After the installation, examine the logs for success.
[AIX HP-UX Linux Solaris Windows]

Logging

The installation wizard and profile management record installation events in the following log files.

Table 1. Installation and profile creation logs for WebSphere Application Server
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
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.
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.

Information that ISMP can log when it cannot start the Installation wizard

[AIX HP-UX Linux Solaris Windows] Verify or troubleshoot the installation if the app_server_root/logs/install/log.txt file or the app_server_root/logs/manageprofiles/pmt.log file does not contain a record of a problem, but problems exist. If the profile_root directory exists, the pmt.log file is in the logs/manageprofiles 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.

[AIX HP-UX Linux Solaris Windows] Certain events can prevent the installer 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 -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 
  • [AIX]
    install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" 
            -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt  @ALL
    
  • [Linux] [HP-UX] [Solaris]
    install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" 
            -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt  @ALL
    
  • [Windows]
    install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" 
                -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt  @ALL
[iSeries] Check the app_server_root/logs/install/log.txt file for success, partial success, or failure for an installation. If the app_server_root/logs/install directory does not exist, check the following locations for log files:
  • user_home/waslogs
  • user_home/niflogs/tmp/waslogs
where user_home is the home directory for the user performing the installation.

[iSeries] If the install completes indicating INSTCONFPARTIALSUCCESS, check the log files located under the user_data_root/profileRegistry/logs/manageprofiles directory for errors. Do not uninstall and attempt to reinstall. If you cannot determine the problem, contact IBM Support.

See Troubleshooting installation for more information.

[AIX HP-UX Linux Solaris Windows]

Installation type options and options for profiles

Options that you can 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:
  • 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

[AIX HP-UX Linux Solaris Windows] See the install command for more information about installation types and profile types.

[iSeries]
Parameter Valid values Default value Description
silentInstallLicenseAcceptance true, false false Specifies whether you accept the terms of the license agreement.
disableOSPrereqChecking true, false commented is false Disables operating system prerequisite checking. If a prerequisites check problem occurs, the installation stops when prerequisite checking is on.
installType installNew, addFeature installNew Specifies the type of installation to perform
createProfile true, false false Specifies whether to create a profile
feature samplesSelected, noFeature noFeature Specifies whether to install application server samples
installLocation A valid absolute file path /QIBM/ProdData/WebSphere/AppServer/V61/ND Specifies the desired install location of the product
defaultProfileLocation A valid absolute file path /QIBM/UserData/WebSphere/AppServer/V61/ND Specifies the desired profile install location
allowOverrideProfileLocation true, false commented, which means false Specifies whether to allow a user to override the default location for installing a profile.
profileType none, standAlone, cell, dmgr, custom cell Specifies whether to create a profile
PROF_enableAdminSecurity true, false false Specifies whether to enable administrative security
PROF_enableAdminSecurity true, false true Specifies whether to enable administrative security
PROF_adminUserName A valid user name ADMIN_USER_NAME Specifies the login user name if security is enabled
PROF_adminUserName A valid user name   Specifies the login user name if security is enabled

This value must be specified if PROF_enableAdminSecurity is set to true.

PROF_adminPassword A valid password ADMIN_PASSWORD Specifies the login password if security is enabled
PROF_adminPassword A valid password   Specifies the login password if security is enabled

This value must be specified if PROF_enableAdminSecurity is set to true.

[iSeries] Next: Go to Installing the WebSphere Application Server group PTF to continue the installation.




Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=rins_responsefile_nd61
File name: rins_responsefile_nd61.html