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.

Creating an operational environment

Installing a new installation of WebSphere Application Server ND with the response file creates an operational environment by default. The installer program:

Installs the new product code.
Creates the default profile.
You can create additional profiles using any of these available methods:
- Use the Profile Management tool.
  See Creating profiles through the graphical user interface.
- Use the manageprofiles command.
  See the description of the manageprofiles command.
- Install with the response file with the createProfile="true" option and select a cell profile, a deployment manager profile, a custom profile, or a standalone appserver profile with the -OPT profileType="profile_type" option.
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

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.
Edit the file to customize the values for your installation.
Save the file as myresponsefile.txt, for example.

Start the installation. For example: [AIX]

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

[Windows]

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

After the installation, examine the logs for success.

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 Network Deployment

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.

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 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. 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/WAS/silentFiles/myresponsefile.txt" 
        -silent -log # !/usr/IBM/WAS/myOptionFiles/log.txt  @ALL

install -options "/opt/IBM/WAS/silentFiles/myresponsefile.txt" 
        -silent -log # !/opt/IBM/WAS/myOptionFiles/log.txt  @ALL

[Windows]

install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" 
            -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt  @ALL

See Troubleshooting installation for more information.

Example of the default file

Edit the version of the file that ships with the WebSphere Application Server ND product. The following example is not guaranteed to be an accurate representation of the file that ships with the product.

################################################################################ # # V6.1 InstallShield Options File # # Wizard name: Install # Wizard source: setup.jar # # This file can be used to configure Install with the options specified below # when the wizard is run with the "-options" command line option. Read each # setting's documentation for information on how to change its value. # Enclose all values within a single pair of double quotes. # # A common use of an options file is to run the wizard in silent mode. This lets # the options file author specify wizard settings without having to run the wizard # in graphical or console mode. To use this options file for silent mode, use # command line arguments such as the following when running the wizard: # # -options "D:\installImage\WAS\responsefile.nd.txt" -silent # ################################################################################ ################################################################################# # # License Acceptance # # Valid Values: # true - Accepts the license. Will install the product. # false - Declines the license. Install will not occur. # # If no install occurs, this will be logged to a temporary log file in the # user's temporary directory. # # By changing the silentInstallLicenseAcceptance property in this response file # to "true", you agree that you have reviewed and agree to the terms of the # IBM International Program License Agreement accompanying this program, which # is located at CD_ROOT\was.primary.pak\repository\legal\lafiles. If you do not # agree to these terms, do not change the value or otherwise download, install, # copy, access, or use the program and promptly return the program and proof of # entitlement to the party from whom you acquired it to obtain a refund of the # amount you paid. # -OPT silentInstallLicenseAcceptance="false" ################################################################################ # Custom Install Package (CIP) Special Paramaters # # To install CIP on an existing installation, e.g. apply maintenance or # add feature, set the 'installType' option to 'installAndPatch', # for example: # # -OPT installType="installAndPatch" # # Please make sure you only set it once. This applies to other parameters as well. # # You can use 'feature' option to control whether to install samples or not. See the # "feature" section below for valid values for 'feature' option. # # In CIP install scenario, set 'installType' to 'addFeature' is the same as set it to # 'installAndPatch'. It is different from non-CIP install. # # By using the following option, you can choose whether to install profile customization # at CIP install time. # # Valid Options: # maintenanceOnly - Only installs product binary files. If the CIP contains profile # customizations, they will NOT be installed. # customizationAndMaintenance - Installs both product binary files and profile # customizations (if any). # -OPT if_cip_modifyexistinginstall=customizationAndMaintenance ################################################################################ # # NonRoot Install Settings # # The option indicates whether you accept the limitations associated with installing # as a non-root user, as follows: # # - Creation of a Windows or Linux service for WAS # - Native registration with the operating system # # Port conflicts may occur with other installations of WAS # that are not registered with the operating system. # # See the "Limitations of non-root installers" (rins_nonroot) file in the information # center for more information on performing these installation actions after # installation and avoiding port conflicts. # # Valid Values: # true - Accepts the limitations. Will install the product. # false - Do not accept the limitations. Install will not occur. # # Uncomment the following only if you are installing as a non-root user. Specify # one of the valid options listed above before proceeding to install: # #-OPT allowNonRootSilentInstall="true" ################################################################################ # # Operating System Prerequisite Checking # # To disable operating system prerequisite checking, uncomment # the following line. This will notify the installer to continue with # the installation and log the warnings even though the prerequisite checking # has failed. # #-OPT disableOSPrereqChecking="true" ################################################################################ # # Non-blocking Prerequisite Checking # # To disable non-blocking prerequisite checking, uncomment # the following line. This will notify the installer to continue with # the installation and log the warnings even though the prerequisite checking # has failed. # #-OPT disableNonBlockingPrereqChecking="true" ################################################################################ # # Install Type Settings # # The installType option designates the type of installation that will be # performed. # # The default installType option is to install a new copy of WebSphere # Application Server. # # Valid Values: # installNew - default value, installs a new copy. # addFeature - add features to an existing installation. ################################################################################ # # Install a New Copy # # To install a new copy, be sure that the installLocation option is set to a # new install location. # -OPT installType="installNew" ################################################################################ # # Incremental Install # # If you are installing additional features on top of an existing installation, # (e.g. incremental install), uncomment the following line. This will notify # the installer that you are doing an incremental install. # #-OPT installType="addFeature" # # Define the new features you want to install on top of an existing WebSphere # Application Server. The only additional feature available in WebSphere # Application Server is Application Server Samples. # # Ensure the feature option below is set to "samplesSelected" (-OPT feature="samplesSelected") # and the installLocation option is set to an "existing" WebSphere Application # Server install location. # ################################################################################ # # Create Profile for an Existing V6.1 Installation # # Valid values: # true - creates a profile for an existing installation # false - does not create a profile # # To create a profile for an existing installation, uncomment the following # entry. Comment out the "installType" option above since "installType" # and "createProfile" options cannot be specified at the same time. # # Be sure the installLocation option is set to your existing install location. # #-OPT createProfile="true" ################################################################################ # # "Application Server samples" feature # # The selection state of the "Application Server samples" feature. # # Valid options: # # samplesSelected - Indicates that the feature is selected for installation. # noFeature - Indicates that the feature is not selected for installation, # this is the default option. # # For example, to select "Application Server samples" for installation, use # # -OPT feature="samplesSelected" # # Note if feature="samplesSelected" and PROF_enableAdminSecurity="true", # provide a password by uncommenting and specifying a value for # PROF_samplesPassword in Administrative Security section below # -OPT feature="noFeature" ################################################################################ # # Install Location # # The install location of the product. Specify a valid directory into which the # product should be installed. If the directory contains spaces, enclose it in # double-quotes as shown in the Windows example below. Note that spaces in the # install location is only supported on Windows operating systems. Maximum path # length is 60 characters for Windows 2000 and Windows XP. # # Below is the list of default install locations for each supported operating # system when you're installing as a root user. By default, in this response # file, the Windows install location is used. To use the default # install location for another operating system, uncomment the appropriate # default install location entry and then comment out the # Windows operating system entry below. # # AIX Default Install Location: # #-OPT installLocation="/usr/IBM/WAS/AppServer" # # HP-UX, Solaris or Linux Default Install Location: # #-OPT installLocation="/opt/IBM/WAS/AppServer" # # i5OS Default Install Location: # #-OPT installLocation="/QIBM/IBM/WAS/AppServer/V61/product_offering" # # Windows Default Install Location: # -OPT installLocation="C:\Program Files\IBM\WebSphere\AppServer" # # If you are installing as non-root user on Unix or non-administrator on # Windows, the following default install locations are suggested. Be sure you # have write permission for the install location chosen. # # AIX Default Install Location: # #-OPT installLocation="user's_home/IBM/WAS/AppServer" # # Windows Default Install Location: # #-OPT installLocation="C:\IBM\WebSphere\AppServer" ################################################################################ # # Profile Creation Selection # # Use this option to indicate the type of profile you would like to create. # # Valid Values: # # cell - two profiles will be created, one with a deployment manager and # another with a managed node that is pre-federated into the cell. # deploymentManager - a profile will be created with a deployment manager. # standAlone - a profile will be created with a stand alone Application # server. # custom - a profile will be created with an empty node # none - a profile will not be created during installation. # # This option is required for the installation on ND. Do not comment it out! # # For example, to select "cell" profile creation for installation, use # -OPT profileType="cell" ################################################################################ # # Administrative Security # # Choose whether to enable Administrative security during the installation # process. # # If profileType="custom", Administrative security should be disabled, use #-OPT PROF_enableAdminSecurity="false" # # Valid Values: # true - Administrative security is enabled, user name and # password required. # false - Administrative security is not enabled. # -OPT PROF_enableAdminSecurity="true" ################################################################################ # # Security Options # # The following two options should only be uncommented when # PROF_enableAdminSecurity="true". # # If PROF_enableAdminSecurity="false", the following entries will be # disregarded. # # If PROF_enableAdminSecurity="true", the following entries are required and must # be filled out before proceeding with silent installation. # # Specify the user name for administrative security # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # -OPT PROF_adminUserName= # # Specify the password for the user specified in PROF_adminUserName # # Valid Values: # a character string # -OPT PROF_adminPassword= # # The following option should only be uncommented when feature="samplesSelected" and # PROF_enableAdminSecurity="true" # Specify the password for samples user # # Valid Values: # a character string # #-OPT PROF_samplesPassword= ################################################################################ ################################################################################ # # The following options are related to creating profiles and can only be used # when installType="installNew" or createProfile="true". The options are dependent # on the profileType option specified in the previous section. # ################################################################################ ################################################################################ # # Cell Profile # # If profileType="cell", use the following profile creation options: # ################################################################################ # # Deployment Manager Profile name # # Name of the profile for the deployment manager. The profile # name must be unique for this WAS installation. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_dmgrProfileName= ################################################################################ # # Application Server Profile name # # Name of the profile for the appserver. The profile # name must be unique for this WAS installation. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_appServerProfileName= ################################################################################ # # Profile path # # Specify a valid directory to contain the files that define the run-time environment, # such as commands,configuration files, and log files. # # Valid Values: An empty directory, the user must have proper permissions to the directory, # there must be adequate disk space, total path cannot be greater than 80 (windows) # #-OPT PROF_profilePath= ################################################################################ # # Default Profile # # To make this profile the default target of commands that do not use their profile parameter. # Valid Values: # true - make this the default profile. # false - do not make this the default profile. # #-OPT PROF_isDefault="true" ################################################################################ # # Host name # # Specify the host name for the Deployment Manager. The host name is the domain # name system (DNS) name (short or long) or the IP address of this computer. # Valid Values: a valid hostname or IP address # #-OPT PROF_hostName= ################################################################################ # # Deployment Manager Node name # # Node name for the deployment manager. Node names within a cell # must be unique. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_nodeName= ################################################################################ # # Application Server Node name # # Node name for the Application Server. Node name under one cell # has to be unique. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_appServerNodeName= ################################################################################ # # Cell name # # Specify the cell name for the profile to be created. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_cellName= ################################################################################ # # Starting Port # # Specify the starting port number for generating all ports for the profile. # Do not use this parameter with the PROF_portsFile or PROF_defaultPorts parameters. # # Valid values: a positive integer port value, within the valid port range # #-OPT PROF_startingPort= ################################################################################ # # Node Starting Port # # Specify the starting port number for the node portion of the cell. # Do not use this parameter with the PROF_nodePortsFile parameter. # # Valid values: a positive integer port value, within the valid port range # #-OPT PROF_nodeStartingPort= ################################################################################ # # Port File # # Specify the path to a property file containing the desired port values for # the new profile. Do not use this parameter with the PROF_startingPort or # PROF_defaultPorts parameters. # # Valid values: A fully qualified path to a valid ports property file # #-OPT PROF_portsFile= ################################################################################ # # Node Port File # # Specify the path to a property file containing the desired port values for # the new profile. Do not use this parameter with the PROF_startingPort or # PROF_defaultPorts parameters. # # Valid values: A fully qualified path to a valid ports property file that defines # port settings for the node portion of the cell. # Do not use this parameter with the PROF_nodeStartingPort parameter. # #-OPT PROF_nodePortsFile= ################################################################################ # # Default Ports # # Specify the default ports are to be used for the new profile. # Do not use this parameter with the PROF_portsFile or PROF_startingPort parameters. # # Valid values: # true - use WAS default ports. # false - do not use WAS default ports. # #-OPT PROF_defaultPorts="true" ################################################################################ # # Validate Ports # # Validate ports to ensure they are not reserved or in use. # Valid values: # true - enables port validation # false - disables port validation # #-OPT PROF_validatePorts="true" ################################################################################ # # WinService Check # # Specify whether you want to run this server as a windows service # # Valid values: # true - run as Windows service. # false - do not run as Windows service. # #-OPT PROF_winserviceCheck="true" ################################################################################ # # WinService Account Type # # Specify the type of the owner account of the Windows service to create. # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid values: specifieduser or localsystem # #-OPT PROF_winserviceAccountType= ################################################################################ # # WinService User Name # # Specify the user name for the windows service. Uncomment the # following ONLY if PROF_winserviceCheck="true" # # Valid values: a valid user name for the current system # #-OPT PROF_winserviceUserName= ################################################################################ # # WinService Password # # Specify the password for the user specified by the winserviceUserName parameter # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_winservicePassword= ################################################################################ # # WinService Startup Type # # Specify the start up method for the windows service # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid values: # manual - windows service must be started manually. # automatic - windows service will start automatically after reboot. # disabled - service is disabled. # #-OPT PROF_winserviceStartupType="automatic" ################################################################################ # # LinuxService Check # # Specify whether you want to run this server as a Linux service. # # Note that the root permission is required to enable Linux service. # # Valid values: # true - run as a Linux service. # false - do not run as a Linux service. # #-OPT PROF_enableService="true" ################################################################################ # # LinuxService User Name # # Name of the user you wish this service to be run as. Uncomment the # following ONLY if PROF_enableService="true". Linux services can only be created # from profile creation if the current user is the root user. # # Valid values: a valid Linux user name # #-OPT PROF_serviceUserName= ################################################################################ # # WebServer Check # # Specify whether you wish to set the web server definition. # # Valid values: # true - enable the creation of a webserver definition. # false - do not enable the creation of a webserver definition. # #-OPT PROF_webServerCheck="true" ################################################################################ # # WebServer Type # # Specify the type of web server you are creating. # Uncomment the following if and ONLY if PROF_webServerCheck="true". # # Valid values (case sensitive): IHS | IIS | SUNJAVASYSTEM | DOMINO | APACHE | HTTPSERVER_ZOS # #-OPT PROF_webServerType= ################################################################################ # # WebServer OS # # Specify the operating system of the system where the web server is # installed. Uncomment the following if and ONLY if PROF_webServerCheck="true". # # Valid values: linux | windows | aix | hpux | solaris | os390 | os400 # #-OPT PROF_webServerOS= ################################################################################ # # WebServer Name # # Name of the web server. Uncomment the following if and ONLY if # PROF_webServerCheck="true". # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_webServerName= ################################################################################ # # WebServer Hostname # # Specify the hostname of the system with the web server. Uncomment the following # if and ONLY if PROF_webServerCheck="true". # # Valid values: a valid hostname or IP address # #-OPT PROF_webServerHostname= ################################################################################ # # WebServer Port # # Specify the port from which the web server can be accessed. Uncomment the # following if and ONLY if PROF_webServerCheck="true". # # Valid values: a valid port number # #-OPT PROF_webServerPort= ################################################################################ # # WebServer Install Path # # Specify the installation path of the web server (local or remote). # Uncomment the following if and ONLY if PROF_webServerCheck="true". # # Valid values: a valid directory path # #-OPT PROF_webServerInstallPath= ################################################################################ # # WebServer Plugin Path # # Specify the path to the plugins that will be used by this web server. # Uncomment the following if and ONLY if PROF_webServerCheck="true". # # Valid values: a valid directory path # #-OPT PROF_webServerPluginPath= ################################################################################ # Omit Action # # Use this option to omit the config action specified in the Application Server # profile. # # Valid values: one of the following optional config actions # deployAdminConsole # defaultAppDeployAndConfig # samplesInstallAndConfig # #-OPT PROF_omitAction= ################################################################################ # # Deployment Manager Profile # # if profileType="deploymentManager", use the following profile creation # options: # ################################################################################ # # Profile name # # Name of the profile for the Deployment Manager. The profile # name must be unique for this WAS installation. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_nodeName= ################################################################################ # # Cell name # # Specify the cell name for the profile to be created. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # # -OPT PROF_cellName= ################################################################################ # # Starting Port # # Specify the starting port number for generating all ports for the profile. # Do not use this parameter with the PROF_portsFile or PROF_defaultPorts parameters. # # Valid values: a positive integer port value, within the valid port range # #-OPT PROF_startingPort= ################################################################################ # # Port File # # Specify the path to a property file containing the desired port values for # the new profile. Do not use this parameter with the PROF_startingPort or # PROF_defaultPorts parameters. # Valid values: A fully qualified path to a valid ports property file # #-OPT PROF_portsFile= ################################################################################ # # Default ports # # Specify the default ports are to be used for the new profile. # Do not use this parameter with the PROF_portsFile or PROF_startingPort parameters. # # Valid values: # true - use WAS default ports. # false - do not use WAS default ports. # #-OPT PROF_defaultPorts="true" ################################################################################ # # Validate Ports # # Validate ports to ensure they are not reserved or in use. # Valid values: # true - enables port validation # false - disables port validation # #-OPT PROF_validatePorts="true" ################################################################################ # # WinService Check # # Specify whether you want to run this server as a windows service # # Valid values: # true - run as Windows service. # false - do not run as Windows service. # #-OPT PROF_winserviceCheck="true" ################################################################################ # # WinService Account Type # # Specify the type of the owner account of the Windows service to create. # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid values: specifieduser or localsystem # #-OPT PROF_winserviceAccountType= ################################################################################ # # WinService User Name # # Specify the user name for the windows service. Uncomment the # following ONLY if PROF_winserviceCheck="true" # # Valid values: a valid user name for the current system # #-OPT PROF_winserviceUserName= ################################################################################ # # WinService Password # # Specify the password for the user specified by the winserviceUserName parameter # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_winservicePassword= ################################################################################ # # WinService Startup Type # # Specify the start up method for the windows service # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid values: # manual - windows service must be started manually. # automatic - windows service will start automatically after reboot. # disabled - service is disabled. # # -OPT PROF_winserviceStartupType="automatic" ################################################################################ # # LinuxService Check # # Specify whether you want to run this server as a Linux service. # # Note that the root permission is required to enable Linux service. # # Valid values: # true - run as a Linux service. # false - do not run as a Linux service. # #-OPT PROF_enableService="true" ################################################################################ # # LinuxService User Name # # Name of the user you wish this service to be run as. Uncomment the # following ONLY if PROF_enableService="true". Linux services can only be created # from profile creation if the current user is the root user. # # Valid values: a valid Linux user name # #-OPT PROF_serviceUserName= ################################################################################ # Omit Action # # Use this option to omit the config action specified # # Valid values: A valid name for an optional config action: deployAdminConsole # #-OPT PROF_omitAction="deployAdminConsole" ################################################################################ # # Stand-Alone Profile # # if profileType="standAlone", you may use the following profile creation # options: # ################################################################################ # # Profile name # # Name of the profile for the Application Server. The profile # name must be unique for this WAS installation. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # # -OPT PROF_cellName= ################################################################################ # # Starting Port # # Specify the starting port number for generating all ports for the profile. # Do not use this parameter with the PROF_portsFile or PROF_defaultPorts parameters. # # Valid values: a positive integer port value, within the valid port range # #-OPT PROF_startingPort= ################################################################################ # # Port File # # Specify the path to a property file containing the desired port values for # the new profile. Do not use this parameter with the PROF_startingPort or # PROF_defaultPorts parameters. # Valid values: A fully qualified path to a valid ports property file # #-OPT PROF_portsFile= ################################################################################ # # Default Ports # # Specify the default ports are to be used for the new profile. # Do not use this parameter with the PROF_portsFile or PROF_startingPort parameters. # # Valid values: # true - use WAS default ports. # false - do not use WAS default ports. # #-OPT PROF_defaultPorts="true" ################################################################################ # # Validate Ports # # Validate ports to ensure they are not reserved or in use. # Valid values: # true - enables port validation # false - disables port validation # #-OPT PROF_validatePorts="true" ################################################################################ # # WinService Check # # Specify whether you want to run this server as a windows service # # Valid values: # true - run as Windows service. # false - do not run as Windows service. # #-OPT PROF_winserviceCheck="true" ################################################################################ # # WinService Account Type # # Specify the type of the owner account of the Windows service to create. # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid values: specifieduser or localsystem # #-OPT PROF_winserviceAccountType= ################################################################################ # # WinService User Name # # Specify the user name for the windows service. Uncomment the # following ONLY if PROF_winserviceCheck="true" # # Valid values: a valid user name for the current system # #-OPT PROF_winserviceUserName= ################################################################################ # # WinService Password # # Specify the password for the user specified by the winserviceUserName parameter # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_winservicePassword= ################################################################################ # # WinService Startup Type # # Specify the start up method for the windows service # Uncomment the following ONLY if PROF_winserviceCheck="true" # # Valid values: # manual - Windows service must be started manually. # automatic - Windows service will start automatically after reboot. # disabled - service is disabled. # # -OPT PROF_winserviceStartupType="automatic" ################################################################################ # # LinuxService Check # # Specify whether you want to run this server as a Linux service. # # Note that the root permission is required to enable Linux service. # # Valid values: # true - run as a Linux service. # false - do not run as a Linux service. # #-OPT PROF_enableService="true" ################################################################################ # # LinuxService User Name # # Name of the user you wish this service to be run as. Uncomment the # following ONLY if PROF_enableService="true". Linux services can only be created # from profile creation if the current user is the root user. # # Valid values: a valid Linux user name # #-OPT PROF_serviceUserName= ################################################################################ # # WebServer Check # # Specify whether you wish to set the web server definition. # # Valid values: # true - enable the creation of a webserver definition. # false - do not enable the creation of a webserver definition. # #-OPT PROF_webServerCheck="true" ################################################################################ # # WebServer Type # # Specify the type of web server you are creating. # Uncomment the following if and ONLY if PROF_webServerCheck="true". # # Valid values (case sensitive): IHS | IIS | SUNJAVASYSTEM | DOMINO | APACHE | HTTPSERVER_ZOS # #-OPT PROF_webServerType= ################################################################################ # # WebServer OS # # Specify the operating system of the system where the web server is # installed. Uncomment the following if and ONLY if PROF_webServerCheck="true". # # Valid values: linux | windows | aix | hpux | solaris | os390 | os400 # #-OPT PROF_webServerOS= ################################################################################ # # WebServer Name # # Name of the web server. Uncomment the following if and ONLY if # PROF_webServerCheck="true". # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_webServerName= ################################################################################ # # WebServer Hostname # # Specify the hostname of the system with the web server. Uncomment the following # if and ONLY if PROF_webServerCheck="true". # # Valid values: a valid hostname or IP address # #-OPT PROF_webServerHostname= ################################################################################ # # WebServer Port # # Specify the port from which the web server can be accessed. Uncomment the # following if and ONLY if PROF_webServerCheck="true". # # Valid values: a valid port number # #-OPT PROF_webServerPort= ################################################################################ # # WebServer Install Path # # Specify the installation path of the web server (local or remote). # Uncomment the following if and ONLY if PROF_webServerCheck="true". # # Valid values: a valid directory path # #-OPT PROF_webServerInstallPath= ################################################################################ # # WebServer Plugin Path # # Specify the path to the plugins that will be used by this web server. # Uncomment the following if and ONLY if PROF_webServerCheck="true". # # Valid values: a valid directory path # #-OPT PROF_webServerPluginPath= ################################################################################ # # Omit Action # # Use this option to omit the config action specified # # Valid values: one of the following optional config actions # deployAdminConsole # defaultAppDeployAndConfig # samplesInstallAndConfig # #-OPT PROF_omitAction= ################################################################################ # # Developer Server # # Use this option to indicate that the default server is meant for development purposes only. # # Valid values: # true - mark this default server for development purposes only. # false - do not mark this default server for development purposes only. # #-OPT PROF_isDeveloperServer="true" ################################################################################ # # Custom Profile # # if profileType="custom", you may use the following profile creation options: # ################################################################################ # # Profile name # # Name of the profile for the Application Server. The profile # name must be unique for this WAS installation. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_profileName= ################################################################################ # # Profile path # # Specify a valid directory to contain the files that define the run-time environment, # such as commands,configuration files, and log files. # # Valid Values: An empty directory, the user must have proper permissions to the directory, # there must be adequate disk space, total path cannot be greater than 80 (windows) # #-OPT PROF_profilePath= ################################################################################ # # Default Profile # # To make this profile the default target of commands that do not use their profile parameter. # Valid Values: # true - make this the default profile. # false - do not make this the default profile. # #-OPT PROF_isDefault="true" ################################################################################ # # Deployment Manager Hostname # # Specify the hostname or address of the machine where the deployment manager # is running. # # Valid values: a valid deployment manager hostname # #-OPT PROF_dmgrHost="localhost" ################################################################################ # # Deployment Manager Port # # Specify the SOAP port of the deployment manager. # # Valid values: a valid port number # #-OPT PROF_dmgrPort="8879" ################################################################################ # # Deployment Manager Admin User Name # # Specify an administrative username that can be authenticated, if # administrative security on the deployment manager is enabled. # # Valid values: a valid deployment manager admin username # #-OPT PROF_dmgrAdminUserName= ################################################################################ # # Deployment Manager Admin Password # # Specify a password that can be authenticated, if administrative security # on the deployment manager is enabled. # # Valid values: a valid deployment manager password # #-OPT PROF_dmgrAdminPassword= ################################################################################ # # Host name # # Specify the host name for the Application Server. The host name is the domain # name system (DNS) name (short or long) or the IP address of this computer. # Valid Values: a valid hostname or IP address # #-OPT PROF_hostName= ################################################################################ # # Application Server Node name # # Node name for the Application Server. Node name under one cell # has to be unique. # # Valid Values: # a character string - do not use the following characters: # /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, } #

a period (.) is not valid if it is the first character. # #-OPT PROF_cellName= ################################################################################ # # Port File # # Specify the path to a property file containing the desired port values for # the new profile. Do not use this parameter with the PROF_startingPort or # PROF_defaultPorts parameters. # Valid values: A fully qualified path to a valid ports property file # #-OPT PROF_portsFile= ################################################################################ # # Federate Later # # Specify whether federation of the node will be done at a later time. # # Valid Values: # true - federate this node later. # false - federate this node now. #-OPT PROF_federateLater="false" ################################################################################ # # Tracing Control # # The trace output format can be controlled via the option # -OPT traceFormat=ALL # # The choices for the format are 'text' and 'XML'. By default, both formats will be # produced, in two different trace files. # # If only one format is required, use the traceFormat option to specify which one, # as follows: # # Valid Values: # text - Lines in the trace file will be in a plain text format for easy readability. # XML - Lines in the trace file will be in the standard Java logging XML format # which can be viewed using any text or XML editor or using the # Chainsaw tool from Apache (http://logging.apache.org/log4j/docs/chainsaw.html). # # The amount of trace info captured can be controlled using the option: # -OPT traceLevel=INFO # # Valid Values: # # Level Numerical Level Description # OFF 0 No trace file is produced # SEVERE 1 Only severe errors are output to trace file # WARNING 2 Messages regarding non-fatal exceptions and warnings # are added to trace file # INFO 3 Informational messages are added to the trace file # (this is the default trace level) # CONFIG 4 Configuration related messages are added to the trace file # FINE 5 Tracing method calls for public methods # FINER 6 Tracing method calls for non public methods except # getters and setters # FINEST 7 Trace all method calls, trace entry/exit will include # parameters and return value

Installation type options and options for profiles

Options used to 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 appserver
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/WAS/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/WAS/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 appserver 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/WAS/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

See the install command for more information about installation types and profile types.

Related information

Customizing the response file for a ND CIP
Installing a CIP silently
install command
Preparing the operating system for product installation
Directory conventions

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.