Sunil's Notes: Perform a silent installation from a response file

The way silent install works is that you set all your installation options in installresponse.txt file such as where portal should be install or application server should be installed, port numbers, user name and password. Once your install response file is ready pass its location to portal installer, which will read all the required values from response file and wont prompt user for input. If there is an error in silent response then portal installer program will write it in log files you can read that error, make necessary changes and try again.

You can use silent response option either because your OS does not support Graphical mode or you want better control on install, Ex. You want to set the port numbers that portal should use or force portal to detect existing WAS. You can also think about silent install if you want to say disable prerequisite checking

You can find the template installresponse.txt file in IL-Setup CD, take that file set necessary values and then execute ./install.sh -options installresponse.txt

Important Note: Even when you use the graphical mode for installation, portal will capture all your inputs and create installresponse.txt file in WP_ROOT/log folder and then use it for installing portal. You can replicate the install by copying the installresponse.log file from one machine and playing it on other machine.

Important Note: Once the install is completed WP_ROOT/log/installmessages.txt file to check if the install was successful. It should have "EJPIC0004I: The installation has completed successfully." message.

This is sample installresponse.txt file that i used. It is pretty self explanatory.

################################################################################
#
# Response File for IBM WebSphere Portal 6.1.0.1 Silent Installation
#
# Before you can begin the installation of WebSphere Portal you must 
# first edit this response file with the values appropriate for your 
# environment. Refer to the comments to learn how to use the response file and 
# understand the various options.  You must carefully complete or change the 
# various values. If the values are not completed properly, the install may 
# be unsuccessful.
#
# IMPORTANT: ALL VALUES MUST BE ENCLOSED IN DOUBLE QUOTES ( "" ).
#
# To use this response file with the installation, specify -options 
# as a command line argument to the install script, where  is the 
# full path name of this response file.
# 
# Usage examples: 
#         install.sh -options /tmp/installresponse.txt
#         install.bat -options c:\temp\installresponse.txt       
#         install400.bat -options c:\temp\installresponse.txt (ISERIES REMOTE INSTALL ONLY)
################################################################################

################################################################################
#
# SILENT INSTALL CHOICE
#
# Description: Specify this parameter if you want to install WebSphere Portal
# silently.  When installing silently, the installation program will not display
# any graphical interface panels or solicit input from the user. Note that if a
# required parameter is not specified in this response file, an error message
# will be displayed. 
# 
# If you want to use this response file but do not want to install silently, 
# comment this parameter out. 
# 
################################################################################

-silent

################################################################################
#
# LICENSE ACCEPTANCE
#
# Description: This parameter specifies that you accept the license agreement
# for WebSphere Portal. By default it is set to false.  You must set it to
# true for the silent install to complete successfully.
#
# -G licenseAccepted="true"
# 
################################################################################

-G licenseAccepted="true"

################################################################################
#
# INSTALL TYPE
#
# Description: Select the type of install that best suites your needs
#
# Values:
# 
#   full  - Install a new version of Portal with full content and applications
#
#   admin - Install a new version of Portal with Administrative portlets and Welcome page
#
################################################################################

-W setupTypePanel.selectedSetupTypeId="admin"

################################################################################
#
# WEBSPHERE PORTAL INSTALLATION LOCATION  (NON-ISERIES)
#
# Description: Specify the directory where you want to install WebSphere Portal.
# This will also be the location for WebSphere Application Server if you selected 
# to install a new instance.
# 
# Be sure to follow the convention for specifying path information on your
# platform.  For example,
#
# Windows: C:\IBM\WebSphere
#   Linux: /opt/IBM/WebSphere
#
################################################################################

-W globalInstall.location="/software/IBM/WebSphere"

################################################################################
#
# WEBSPHERE APPLICATION SERVER INSTALLATION CHOICE
#
# Description: Specify wether you want to install on a new instance or install on
# an existing instance of WebSphere Application Server.
# 
# "install" - Install a new instance of WebsSphere Application Server.
#
# "use"     - Install on an existing instance of WebSphere Application Server.
#             If you choose this option the wasListPanel.existingWasLocation 
#             value must also be specified.
#
################################################################################

-W wasPanel.installChoice="install"

################################################################################
#
# EXISTING WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION
#
# Description: This is the value of the existing WebSphere Application Server
# if you selected to install on an existing instance.
#
# Be sure to follow the convention for specifying path information on your
# platform.  For example,
#
# Windows: C:\WebSphere\AppServer
# AIX: /usr/WebSphere/AppServer
# Linux: /opt/WebSphere/AppServer
# Solaris: /opt/WebSphere/AppServer
# HP-UX: /opt/WebSphere/AppServer
# iSeries ND:   /QIBM/ProdData/WebSphere/AppServer/V61/ND
# iSeries Base: /QIBM/ProdData/WebSphere/AppServer/V61/Base
################################################################################

# -W wasListPanel.existingWasLocation=""

################################################################################
# 
# OPTIONAL:
# UNDETECTED WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION (NON-ISERIES)
#
# Description: Sometimes the Portal install program cannot detect an existing
# WebSphere Application Server(WAS).   You cannot know this until install runtime
# when the silent install fails because the value of the above parameter
# wasListPanel.existingWasLocation cannot be validated. 
#
# When this error occurs, and you are certain that there is a valid WAS at the
# location specified above, uncomment this parameter and enter the same value
# specified above. 
#
# Be sure to follow the convention for specifying path information on your
# platform.  For example,
#
# Windows: C:\WebSphere\AppServer
# AIX: /usr/WebSphere/AppServer
# Linux: /opt/WebSphere/AppServer
# Solaris: /opt/WebSphere/AppServer
# HP-UX: /opt/WebSphere/AppServer
#
################################################################################

# -W was.undetectedWas="/opt/IBM/WebSphere/AppServer"

################################################################################
#
# ADMINISTRATIVE USER AND PASSWORD
#
# Enter the user ID and password for the Websphere Application Server
# administrator and WebSphere Portal.
#
################################################################################

-W wasAdmin.user="wasadmin"
-W wasAdmin.password="wasadmin"

################################################################################
#
# WEBSPHERE APPLICATION SERVER NODE NAME
#
# Description: Specify the node within the WebSphere Application Server cell to 
# which the WebSphere Portal application server will belong. This value must be 
# unique among other node names in the same cell. Typically this value is the 
# same as the short host name for the computer.
#
# Note: You must replace the "DefaultNode" value with the node name that you  
# want to use for your default node.
#
################################################################################

-W nodeHost.nodeName="DefaultNode"

################################################################################
#
# WEBSPHERE APPLICATION SERVER HOST NAME
#
# Description: Specify the fully qualified host name or IP address of the
# computer running WebSphere Application Server.  For example, 
# "hostname.yourco.com".
#
################################################################################

-W nodeHost.hostName="spinfotech.com"

################################################################################
#
# Begin Installing Services 
#
################################################################################

################################################################################
# 
# INSTALL THE WEBSPHERE PORTAL SERVICE (WINDOWS ONLY)
#
# Description: If you are installing WebSphere Portal on a machine 
# running Windows, specify whether you want to install it as a service.
# Using Services, you can start and stop services, and configure startup and 
# recovery actions.
#
# Note: If you are installing WebSphere Portal on a system that is 
# not running Windows, you can ignore this parameter or comment it out.
#
# Values:
#
#   true   - Install WebSphere Portal as service
#
#   false  - Do no install WebSphere Portal as service
#
################################################################################

-W allServices.services="false"

################################################################################
#
# End Installing Services 
#
################################################################################

################################################################################
#
# SETUP CD LOCATION 
# 
# Required for: Tradtional and Archive install
#
# Description: Specify the directory path to the Setup CD.
# Although this can be to a CD-ROM drive, for unattended
# installation this location is more likely to be a directory where electronic
# product images are stored, such as on a network drive.
#
# Be sure to follow the convention for specifying path information on your
# platform.  
#
################################################################################

-W cdSetup.cdPath="/software/WPS6.1/IL-Setup"

################################################################################
#
# INSTALL CD LOCATIONS
#
################################################################################

################################################################################
#
# WEBSPHERE APPLICATION SERVER CD LOCATION
#
# Description: Specify the directory path to the WebSphere Application Server 
# installation images.  Although this can be to a CD-ROM drive, for unattended 
# installation this location is more likely to be a directory where electronic 
# product images are stored, such as on a network drive.
#
# Be sure to follow the convention for specifying path information on your
# platform.  
#
# CD      Platform
#  W-1     Windows for ia32
#  W-2     Windows for amd64
#  I-1     iSeries
#  IL-1    Linux for x86
#  IL-2    Linux for x86-64
#  A-1     AIX on Power 32bit
#  A-2     AIX on Power 64bit
#  SS-1    Solaris sparc32
#  SS-2    Solaris sparc64
#  SO-1    Solaris x64
#  H-1     HP-UX parisc
#  HI-1    HP-UX ia64
#  ZL-2    Linux for zSeries
#  PL-1    Linux for ppc32
#  PL-2    Linux for ppc64
#
################################################################################

-W userInputCDLocWas.cdPath="/software/WPS6.1/IL-1"

################################################################################
#
# ARCHIVE CD 1
#
# Required for: Archive install
#
# Description: Specify the directory path to the first archive install image
# Be sure to follow the convention for specifying path information on your
# platform.  
#
# CD      Platform
#  W-3     Windows
#  IL-3    Linux for x86 or amd64
#  A-3     AIX
#  SS-3    Solaris sparc
#  SO-3    Solaris x64
#  H-3     HP-UX parisc
#  HI-3    HP-UX ia64
#  I-3     iSeries
#  ZL-3    Linux for zSeries
#  PL-3    Linux for ppc
#
################################################################################

-W archiveMediaPanel1.cdPath="/software/WPS6.1/IL-3"

################################################################################
#
# ARCHIVE CD 2
#
# Required for: Archive install
#
# Description: Specify the directory path to the second archive install image
# Be sure to follow the convention for specifying path information on your
# platform.  
#
# CD      Platform
#  W-4     Windows
#  IL-4    Linux for x86 or amd64
#  A-4     AIX
#  SS-4    Solaris sparc
#  SO-4    Solaris x64
#  H-4     HP-UX parisc
#  HI-4    HP-UX ia64
#  I-4     iSeries
#  ZL-4    Linux for zSeries
#  PL-4    Linux for ppc
#
################################################################################

-W archiveMediaPanel2.cdPath="/software/WPS6.1/IL-4"

################################################################################
#
# CONFIGURATION ARCHIVE CD
#
# Required for: Archive install
#
# Description: Specify the directory path to the Portal configuration archive
# install image. Be sure to follow the convention for specifying path information
# on your platform.  
#
# CD      Platform
#  W-5     Windows
#  IL-5    Linux for x86 or amd64
#  A-5     AIX
#  SS-5    Solaris
#  H-5     HP-UX
#  I-5     iSeries
#  ZL-5    Linux for zSeries
#  PL-5    Linux for ppc
#
#  If installing on WebSphere Application Server 7 use *-5a
#  For example use: W-5a or IL-5a
#
################################################################################

-W userInputCDLocProfile.cdPath="/software/WPS6.1/IL-5"

################################################################################
#
# Advanced Options
#
################################################################################

################################################################################
#
# Dependency Checking     
#
# Description: Specify whether you want to disable the prerequisite checking 
# and input validation used during the WebSphere Portal installation. 
#
# Note: Because prerequisite checking and input validation play an important 
# role in ensuring a successful installation, it is recommended that disable 
# dependency checking only when absolutely necessary.
#
# Values:
#
# true - Dependency checking is performed. This is the default value and is 
#        assumed if the dependency.useValidation parameter is not specified. 
# false - No dependency checking is performed. 
#
################################################################################

-W dependency.useValidation="false"

################################################################################
#
# Custom Dependency Files     
#
# Description: If you want to use custom dependency and validation rules, 
# specify the directory where your custom rules files are located. 
#
# This parameter is not required if you have disabled dependency checking 
# (specified a value of "false" for the dependency.useValidation parameter).
#
# Replace the placeholder value "DIRECTORY_PATH" with the appropriate value for 
# your system.
#
################################################################################

#-W dependency.rulesDirectory="DIRECTORY_PATH"

################################################################################
#
# USER SPECIFIED PORT SCAN RANGE FOR WEBSPHERE ADMIN SERVER     
# 
# Description: When you you want to specify port values for the WebSphere Admin 
# Server, one option is to specify a range of port values that will be searched 
# until a block of free ports is found.  These two properties specify the 
# search range to scan.  If any of the ports in a block are busy, the remaining
# range is scanned for a free block.
#
# Portal sets the default starting port to scan value to 10000.  
#
#    -W adminPortBlockInput.startingPortToScan="10000"
#
# Portal sets the default ending port to scan value to 65000. 
#  
#    -W adminPortBlockInput.endingPortToScan="65000"
#
################################################################################

# -W adminPortBlockInput.startingPortToScan="10000"
 
# -W adminPortBlockInput.endingPortToScan="65000"

################################################################################
#
# USER SPECIFIED PORT BLOCK SIZE FOR WEBSPHERE ADMIN SERVER (NON-ISERIES)
#
# Description:  This property determines the number of consecutive ports that 
# will be used for configuring the WebSphere Admin Server.  When searching for 
# a block of free ports, the Websphere Portal install will search in increments 
# of this number.  Do not enter a number lower than 25. 
#
# The default port block size is 25.
#
#   -W adminPortBlockInput.portBlockSize="25"
#
################################################################################

# -W adminPortBlockInput.portBlockSize="25"
 
################################################################################
# USER SPECIFIED PORTS FILE PATH FOR WEBSPHERE ADMIN SERVER (NON-ISERIES)     
# 
# Description: When you want to specify port values for the WebSphere Admin 
# Server, one option is to specify a file that defines all of the WebSphere 
# Admin Server port values.  Each line in the file has a = 
# pair.  See the file WASDefaultPortsFile.props in your cdsetup directory for 
# a ports file example.
#
# The file's content is not validated so any errors will cause the install   
# program to fail.
#  
# Be sure to follow the convention for specifying path information on your 
# platform. Full path is required. 
# 
# When this parameter is specified, the other WebSphere Admin Server port 
# values are ignored (adminPortBlockInput.startingPortToScan, 
# adminPortBlockInput.endingPortToScan, adminPortBlockInput.portBlockSize).
#  
################################################################################

# -W adminPortBlockInput.portsFilePath="c:\cdSetup\WASDefaultPortsFile.props"

################################################################################
#
# USER SPECIFIED PORT SCAN RANGE FOR WEBSPHERE PORTAL SERVER (NON-ISERIES)     
# 
# Description: When you want to specify the port values for the WebSphere Portal
# Server, one option is to specify a range of port values that will be searched 
# until a block of free ports is found.  These two properties specify the 
# search range.  If any of the ports in a block are busy, the remaining
# range is scanned for a free block.  
#
# Portal sets the default starting port value to 10025. 
# 
#   
#   -W portalPortBlockInput.startingPortToScan="10025"
#
# Portal sets the default ending port to scan value to 65000. 
#  
#    -W portalPortBlockInput.endingPortToScan="65000"
#
################################################################################

# -W portalPortBlockInput.startingPortToScan="10025"
 
# -W portalPortBlockInput.endingPortToScan="65000"

################################################################################
#
# USER SPECIFIED PORT BLOCK SIZE FOR WEBSPHERE PORTAL SERVER (NON-ISERIES)
#
# Description:  This property determines the number of consecutive ports that 
# will be used for configuring the WebSphere Portal Server.  When searching for 
# a block of free ports, the Websphere Portal install will search in increments 
# of this number.  Do not enter a number lower than 25. 
#
# The default port block size is 25.
#
#   -W portalPortBlockInput.portBlockSize="25"
#
################################################################################

# -W portalPortBlockInput.portBlockSize="25"

################################################################################
#
# USER SPECIFIED PORTS FILE PATH FOR PORTAL SERVER (NON-ISERIES)     
# 
# Description: When you want to specify port values for the WebSphere Portal 
# Server, one option is to specify a file that defines all of the Portal 
# Server port values.  Each line in the file has a = 
# pair.  See the file WPDefaultPortsFile.props in your cdsetup directory for 
# a ports file example.
#
# The file's content is not validated so any errors will cause the install   
# program to fail.
#  
# Be sure to follow the convention for specifying path information on your 
# platform. Full path is required. 
# 
# When this parameter is specified, the other portal server port values
# are ignored (portalPortBlockInput.startingPortToScan, 
# portalPortBlockInput.endingPortToScan, portalPortBlockInput.portBlockSize).
#  
################################################################################

# -W portalPortBlockInput.portsFilePath="C:\cdSetup\WPDefaultPortsFile.props"

################################################################################
#
# SET THE PORTAL PROFILE AS THE DEFAULT WEBSPHERE PROFILE (NON-ISERIES)     
# 
# Description: This parameter specifies whether the Portal profile should 
# be the default profile.   The default behavior is to set Portal's profile as 
# the default when no other profiles exist in WebSphere Application Server.
#
# Values:
# 
#   "True"  - Sets the Portal profile as the default profile. 
#   
#   "False" - Leaves the existing default profile as is. 
#  
################################################################################

# -W detectProfileAction.isDefault="True"

################################################################################
#
# CUSTOMIZING PORTAL PROFILE 
#
# PORTAL PROFILE NAME     
# 
# Description: By default, the name of Portal's profile is wp_profile.  If 
# multiple Portal profiles exist in the same instance of WebSphere Application
# Server, a number is added to the default name to make it unique, such as
# wp_profile1.  
#
# The name must be unique within the profiles of the WebSphere 
# instance.
# 
# PORTAL PROFILE PATH (NON-ISERIES)   
# 
# Description: The profile path contains the path to Portal's profile.  
# By default, it is set to a subdirectory of WebSphere's profile directory using
# the profile name.
#
# You can change the name of the profile by supplying the profile name 
# and/or the  profile path like this:
#     -W detectProfileAction.profileName="my_profile_name"
#     -W detectProfileAction.profilePath="c:\full\path\my_profile_name"           
################################################################################

# -W detectProfileAction.profileName="wp_profile"

# -W detectProfileAction.profilePath="C:\Program Files\IBM\WebSphere\AppServer\profiles\wp_profile"

################################################################################
#
# SET THE FILE PERMISSIONS ON UNIX SYSTEMS (UNIX-ONLY)     
# 
# Description: This parameter specifies the file permissions for the files 
# installed to the Portal installation directory.  Valid values are in the range
# of 000 - 777.
#
# The default value is 550. 
# 
#  
################################################################################

# -W defaults.unixFilePermissions="550"
Perform a silent installation from a response file

1 comment:
