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.

Install the product with an options response file after logging on as root on a platform such as AIX or Linux, or as a user that belongs to the administrator group on a Windows platform. Some steps of the installation procedure on a Windows platform require the user to belong to the administrator group and to have the advanced user rights Act as part of the operating system and Log on as a service.

You can also install a customized installation package (CIP) with an options response file. A CIP is produced by the Installation Factory.

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 disc or in the downloaded installation image.

Mode of use

The installation wizard can read an existing options response file and run silently without displaying the graphical user interface.

Installing silently

The options file lets the Installation wizard run in silent mode. The wizard reads the options file to determine responses and does not display the graphical user interface. The following command uses a copy of the options file named myresponsefile.txt for a silent installation:
install -options "myresponsefile.txt" -silent

Creating an operational environment

Version 6 installation of the Network Deployment product is a two-step process:
  1. Installing the core product files and feature files.
  2. Creating a profile for the deployment manager, a managed node, or a stand-alone application server.

The sample options response file, responsefile.nd.txt, controls the first part of the installation and can also start the second part of the installation. To create a profile after installing the core product files, use the option in the responsefile.nd.txt file that identifies the response file for creating a profile. The profile response file lets you use the Profile Creation wizard silently.

To edit and use the appropriate response file for creating a profile, perform the following procedure:
  1. Copy the appropriate file from the WAS directory on the product disc to a place that you can easily identify on your machine. The example files are:
    To create one: Copy the following response file:
    Deployment manager profile responsefile.pct.NDdmgrProfile.txt
    Application server profile responsefile.pct.NDstandAloneProfile.txt
    Custom profile responsefile.pct.NDmanagedProfile.txt
  2. Edit the file to customize the values for your installation.
  3. Save the file.
  4. Edit the responsefile.nd.txt file to identify the location and name of the profile response file. The installation path must be 80 characters or less. Change the value of the -W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation option to identify the file. For example:
    [AIX] [HP-UX] [Linux] [Solaris]
    -W pctresponse...fileLocation=
    "/tmp/WAS/responsefile.pct.NDdmgrProfile.txt"
    
    [Windows]
    -W pctresponse...fileLocation=
    "C:\temp\WAS\responsefile.pct.NDdmgrProfile.txt"
    
  5. Start the installation. For example:
    [AIX] [HP-UX] [Linux] [Solaris]
    install -options /tmp/WAS/myresponsefile.txt -silent
    
    [Windows]
    install -options "C:\temp\WAS\myresponsefile.txt" -silent
    
  6. 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 WebSphere® Application Server Network Deployment: The following table shows the installation logs, content, and indicators of success and failure for WebSphere Application Server Network Deployment:

See Troubleshooting installation for more information.

Usage notes

Option descriptions

Use the following description of options as a worksheet to plan your values. Refer to the individual descriptions of directives in the following list to help plan your responses:

-W silentInstallLicenseAcceptance.value="false"
# -W detectedexistingcopypanelInstallWizardBean.choice="addFeatures"
Platform specific: -P wasProductBean.installLocation="/usr/IBM/WebSphere/AppServer"
Platform specific: -P wasProductBean.installLocation="/opt/IBM/WebSphere/AppServer"
Platform specific: -P wasProductBean.installLocation="C:\Program Files\IBM\WebSphere\AppServer"
-P samplesProductFeatureBean.active="true"
-P javadocsProductFeatureBean.active="true"
-W ndsummarypanelInstallWizardBean.launchPCT="true"
-W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation=""

Refer to the following list of values to plan your responses to the options in the file:

-W silentInstallLicenseAcceptance.value="false"
Valid values are true or false. You must accept the license agreement before you are allowed to install the product.
Default value Description Your value
false By changing the silentInstallLicenseAcceptance.value 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\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.

Change the value to true to accept the license agreement and install the product. You cannot install the product with the default value.

 
Non-CIP only: -W detectedexistingcopypanelInstallWizardBean.choice= "addFeatures"
The only valid value for this directive is addFeatures. Leave the line commented if you are not adding features to a previous installation.
Default value Description Your value
Commented out Uncomment the line to add features to an existing installation in an incremental migration.

Change the value of the following -P wasProductBean.installLocation= directive to the directory of the existing installation.

To avoid problems, set the feature active properties for currently installed features to false. To install a new feature, set the feature active property to true.

For example, suppose that you have an existing installation of the product with the Javadocs feature installed, but not the Samples feature. To install the Samples feature, set the following directives accordingly:
  • -P samplesProductFeatureBean.active=true
  • -P javadocsProductFeatureBean.active=false

The feature selection options are described after the installation type option.

 
CIP only: -W detectedexistingcopypanelInstallWizardBean.choice= "installNew"
Valid values for this directive are
  • installNew (default)
  • addFeaturesAndFixes
Default value Description Your value
installNew If you are adding features and maintenance to an existing installation:
  1. Comment the line to install a new installation.
  2. Uncomment the line to add features to an existing installation in an incremental migration.
  3. Change the value of the following -P wasProductBean.installLocation= directive to the directory of the existing installation.
  4. To avoid problems, set the feature active properties for currently installed features to false. To install a new feature, set the feature active property to true.
    For example, suppose that you have an existing installation of the product with the Javadocs feature installed, but not the Samples feature. To install the Samples feature, set the following directive values:
    • -P samplesProductFeatureBean.active=true
    • -P javadocsProductFeatureBean.active=false

    The feature selection options are described after the profile update warning option.

 
-P wasProductBean.installLocation=
  • [AIX] -P wasProductBean.installLocation="/usr/IBM/WebSphere/AppServer"
  • [Linux] [HP-UX] [Solaris] -P wasProductBean.installLocation="/opt/IBM/WebSphere/AppServer"
  • [Windows] -P wasProductBean.installLocation="C:\Program Files\IBM\WebSphere\AppServer"
Default value Description Your value
Varies per product disc The installation root directory for the product. Specify a valid directory.

The default installation location is for a Windows system. Comment the Windows line to install on an operating system such as AIX or Linux.

Uncomment the line that describes your platform and optionally change the location. The installation path must be 80 characters or less.

[AIX] [HP-UX] [Linux] [Solaris]
Important: Do not use symbolic links as the destination directory. Symbolic links are not supported.

Spaces are also not supported in the name of the installation directory.

On a Windows system, the directory can contain spaces. Enclose a directory name with spaces within double quotation marks as shown in the Windows example.

 
CIP only: -W profileUpdateWarningPanelWizardBean.active="true"
Valid values are true or false.
Default value Description Your value
true The CIP can include maintenance packages that update existing profiles. Updated profiles are not rolled back if you uninstall the maintenance packages because of the possibility that you have made configuration changes to the profile that you do not want to lose.

Use the backupConfig command to back up the configuration from an existing profile before installing the CIP. You can also archive the entire profile directory using systems commands to copy directories.

If the CIP includes profile maintenance, a true value causes a warning panel to display. A false value does not display the warning panel.

 
-P samplesProductFeatureBean.active="true"
Valid values are true or false.
Default value Description Your value
true This option installs the Samples feature.

Change the value to false to skip the installation of the Samples feature.

Change the value to false during an incremental installation if the Samples feature is already installed.

Do not use a value of true if the Samples feature is already installed.

 
-P javadocsProductFeatureBean.active="true"
Valid values are true or false.
Default value Description Your value
true This option installs the Javadocs feature.

Change the value to false to skip the installation of the Javadocs feature.

Change the value to false during an incremental installation if the Javadocs feature is already installed.

Do not use a value of true if the Javadocs feature is already installed.

 
-W ndsummarypanelInstallWizardBean.launchPCT="true"
Valid values are true or false.
Default value Description Your value
true A value of true launches the Profile Creation wizard silently.

This option controls launching the Profile Creation wizard silently at the end of the installation of the core product files and features. The Profile Creation wizard can create one of the three available profile types for the Network Deployment product.

 
-W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation=""
Valid values are the absolute path and file name of the customized options file for a profile. The original files are located in the WAS directory on the product disc or the downloaded installation image.
You must copy the appropriate file to a location on your machine where you can edit and save the file. The names of the original profile response files are:

Each file contains a planning area for marking your values.

Default value Description Your value
none This option must specify the absolute path to the customized options file for the appropriate profile.

For example:

[AIX] [HP-UX] [Linux] [Solaris]
-W pctresponse...fileLocation=
"/tmp/WAS/responsefile.pct.NDdmgrProfile.txt"
[Windows]
-W pctresponse...fileLocation=
"C:\temp\WAS\responsefile.pct.NDdmgrProfile.txt"
 



Example responsefile.nd.txt file for a CIP

A customized installation package (CIP) can include one or more maintenance packages and customized profiles.

Edit the version of the file that ships with the CIP. The following example is not guaranteed to be an accurate representation of the file that ships with the CIP.
################################################################################
#
# 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.
# 
# 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
# execution, use the following command line arguments when running the wizard:
# 
#    -options "D:\installImage\WAS\responsefile.nd.txt" -silent
#
################################################################################

###################################################################################
#
# License Acceptance
#
# Valid Options	: 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.value 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\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.
#
# 

-W silentInstallLicenseAcceptance.value="false"

################################################################################
#
# Install a new copy of IBM WebSphere Application Server product 
#
# If you are installing a new of copy of the product,  leave  the following line uncommented.
# Otherwise, comment the line.
#
#
-W NDdetectedexistingcopypanelInstallWizardBean.choice="installNew"


################################################################################
#
# Apply maintenance and add features
#
# If you are planning to apply maintenance, add features, or both on 
# top of an existing installation, uncomment the following line. 
#
# -W NDdetectedexistingcopypanelInstallWizardBean.choice="addFeaturesAndFixes"
#
# Please make sure installLocation is set to your existing install location.
#
#
# For additional features you wish to install, set the feature active
# properties to true.  
#
# NOTE: If the product edition of the custom installation package is 
#       different from the existing installation package, then the features
#       will not be added.
#
# For example, you have installed core product feature, now you want to install
# samples feature, the active properties should be:
#
# -P samplesProductFeatureBean.active="true"
# -P javadocsProductFeatureBean.active="false"
#


################################################################################
#
# IBM WebSphere Application Server Network Deployment, V6.0 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.
# 
# Below is the list of default install locations for each supported operating
# system.  By default, in this response file, the Windows install location is 
# used.  If you want to use the default install location for another operating
# system, uncomment the appropriate default install location entry (by removing '#') and 
# then comment out (by adding '#') the Windows operating system entry below.
#
#
# AIX Default Install Location:
#
#    -P wasProductBean.installLocation=/usr/IBM/WebSphere/AppServer	
#
#
# HP-UX, Solaris or Linux Default Install Location:
#
#    -P wasProductBean.installLocation=/opt/IBM/WebSphere/AppServer	
#
#
# Windows Default Install Location:
#


-P wasProductBean.installLocation="C:\Program Files\IBM\WebSphere\AppServer"

################################################################################
#
# Warning: the custom install package may update your existing profiles.
#
# This custom install package may update the runtime environment profiles
# in your runtime environment.  Tt is strongly recommended that you backup 
# all profiles before you continue.   If you uninstall this maintenance package
# at a later time, these profile updates will not be uninstalled because 
# additional custom modifications may have subsequently been made.  
# 
# For more information on profile management, see the wasprofile command
# documentation in the Information Center.
#
# The default value is "true", it will block the install unless you change
# the active property to "false".
#
# If you have already backed up your profiles or you wish to ingore the warnings,
# you can change it to "false".
#
# For example:
#
# -W profileUpdateWarningPanelWizardBean.active="false"
#

-W profileUpdateWarningPanelWizardBean.active="true"

################################################################################
#
# "Core Product Files" feature
#
# This feature is required by Application Server and will be installed by default. 
# Selection is not required.
#


################################################################################
#
# "Application Server samples" feature
#
# The selection state of the "Application Server samples" feature. Legal values
# are:
# 
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
# 
# For example, to select "Application Server samples" for installation, use
# 
#    -P samplesProductFeatureBean.active="true"
#


-P samplesProductFeatureBean.active="true"


################################################################################
#
# "Javadocs" feature
#
# The selection state of the "Javadocs" feature. Legal values are:
# 
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
# 
# For example, to select "Javadocs" for installation, use
# 
#    -P javadocsProductFeatureBean.active="true"
#


-P javadocsProductFeatureBean.active="true"


################################################################################
#
# WebSphere Application Server Profile Creation Tool (PCT)
#
# To launch the Profile Creation Tool SILENTLY at the end
# of the installation, please change the value to "true".
# Otherwise, change the value to "".
#
# Please Note: This will launch the latest PCT.  If the Custom Install Package
# contains profile customizations, this will launch the PCT installed in
# <WAS_HOME>/cip/<uid>/ProfileCreator.  Otherwise, it will launch the GM version
# PCT which can be found at <WAS_HOME>/bin/ProfileCreator.
# 

-W ndsummarypanelInstallWizardBean.launchPCT="true"


################################################################################
# If you choose to run Profile Creation Tool silently at the end of the
# installation, you must
# 1. get a copy of the PCT response file of Profile creator (from CD) and put to a temp dir
#    such as: /tmp/WAS/responsefile.pct.NDdmgrProfile.txt           For DMGR profile creation
#             /tmp/WAS/responsefile.pct.NDmanagedProfile.txt        For Manage profile creation
#             /tmp/WAS/responsefile.pct.NDstandAloneProfile.txt     For Stand alone profile creation
# 2. modify the response file by filling in the required options/values. 
# Note: If the values are not completed properly, the configuration may be unsuccessful. 
# 3. specify below the absolute path to your modified response file. 
# 
# For example, -W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation="/tmp/WAS/responsefile.pct.NDdmgrProfile.txt"


-W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation=""

Example responsefile.nd.txt file

Edit the version of the file that ships with the WebSphere Application Server Network Deployment product. The following example is not guaranteed to be an accurate representation of the file that ships with the product.
################################################################################
#
# 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.
# 
# 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
# execution, use the following command line arguments when running the wizard:
# 
#    -options "D:\installImage\WAS\responsefile.nd.txt" -silent
#
################################################################################

###################################################################################
#
# License Acceptance
#
# Valid Options       : 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.value 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\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.
#
# 

-W silentInstallLicenseAcceptance.value="false"

################################################################################
#
# 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.
#
# -W NDdetectedexistingcopypanelInstallWizardBean.choice="addFeatures"
#
# Please make sure installLocation is set to your existing install location.
#
# For already installed features, you need to set the feature active property
# to false.  For new features you want to install, you need to set the active
# properties to true.
#
# For example, you have installed core product feature, now you want to install
# samples feature, the active properties should be:
#
# -P samplesProductFeatureBean.active="true"
# -P javadocsProductFeatureBean.active="false"


################################################################################
#
# IBM WebSphere Application Server Network Deployment, V6.0 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.
# 
# Below is the list of default install locations for each supported operating
# system.  By default, in this response file, the Windows install location is 
# used.  If you want to use the default install location for another operating
# system, uncomment the appropriate default install location entry (by removing '#') and 
# then comment out (by adding '#') the Windows operating system entry below.
#
#
# AIX Default Install Location:
#
#    -P wasProductBean.installLocation=/usr/IBM/WebSphere/AppServer       
#
#
# HP-UX, Solaris or Linux Default Install Location:
#
#    -P wasProductBean.installLocation=/opt/IBM/WebSphere/AppServer
#
#
# Windows Default Install Location:
#


-P wasProductBean.installLocation="C:\Program Files\IBM\WebSphere\AppServer"


################################################################################
#
# "Core Product Files" feature
#
# This feature is required by Application Server and will be installed by default. 
# Selection is not required.
#


################################################################################
#
# "Application Server samples" feature
#
# The selection state of the "Application Server samples" feature. Legal values
# are:
# 
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
# 
# For example, to select "Application Server samples" for installation, use
# 
#    -P samplesProductFeatureBean.active="true"
#


-P samplesProductFeatureBean.active="true"


################################################################################
#
# "Javadocs" feature
#
# The selection state of the "Javadocs" feature. Legal values are:
# 
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
# 
# For example, to select "Javadocs" for installation, use
# 
#    -P javadocsProductFeatureBean.active="true"
#


-P javadocsProductFeatureBean.active="true"


################################################################################
#
# WebSphere Application Server Profile Creation Tool 
#
# To launch the Profile Creation Tool SILENTLY at the end
# of the installation, please change the value to "true".
# Otherwise, change the value to "".
# 


-W ndsummarypanelInstallWizardBean.launchPCT="true"


################################################################################
# If you choose to run Profile Creation Tool silently at the end of the
# installation, you must
# 1. get a copy of the PCT response file of Profile creator (from CD) and put to a temp dir
#    such as: /tmp/WAS/responsefile.pct.NDdmgrProfile.txt        For DMGR profile creation
#             /tmp/WAS/responsefile.pct.NDmanagedProfile.txt     For Manage profile creation
#             /tmp/WAS/responsefile.pct.NDstandAloneProfile.txt  For Stand alone profile creation
# 2. modify the response file by filling in the required options/values. 
# Note: If the values are not completed properly, the configuration may be unsuccessful. 
# 3. specify below the absolute path to your modified response file. 
# 
# For example, -W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation=
#        "/tmp/WAS/responsefile.pct.NDdmgrProfile.txt"


-W pctresponsefilelocationqueryactionInstallWizardBean.fileLocation=""




Related information
Customizing the response file
Reference topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=rins_responsefile_nd
File name: rins_responsefile_nd.html