### installresponse.txt
###
### Response file for IBM WebSphere Portal 6.1.0.3 silent Installation
###
### Edit this file with the values appropriate for your environment.
###
### IMPORTANT: ALL VALUES MUST BE ENCLOSED IN DOUBLE QUOTES ( "" ).
###
### To use this response file, specify...
###
### -options /path/to/installresponse.txt
###
###
### 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
###
### 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
###
### 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"
###
### INSTALL TYPE
###
### 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="full"
###
### WEBSPHERE PORTAL INSTALLATION LOCATION (NON-ISERIES)
###
### Specify the directory where you want to install WebSphere Portal.
### This will also be the location for WAS if you selected
### to install a new instance.
### Do not specify a directory that includes any of the following characters:
### ~!@#$%^&*()_+{}|"<>?`=[];',.
###
### 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="/opt/IBM/WebSphere"
###
### WAS INSTALLATION CHOICE
###
### Install on a new instance or install on an existing instance of WAS.
###
### "install" - Install a new instance of WAS.
###
### "use" - Install on an existing instance of WAS.
### If you choose this option the wasListPanel.existingWasLocation
### value must also be specified.
###
-W wasPanel.installChoice="install"
###
### EXISTING WAS INSTALLATION LOCATION
###
### This is the value of the existing WAS
### 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 WAS INSTALLATION LOCATION (NON-ISERIES)
###
### Sometimes the Portal install program cannot detect an existing
### WAS(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. The ID and password may contain
### any English alphanumeric character, as well as any of the following symbols:
### .-_!()?[]`~
### Other characters or symbols are not permitted.
### Additionally, the password must be at least 5 characters long.
###
###
-W wasAdmin.user="wpsadmin"
-W wasAdmin.password=""
###
###
### WAS NODE NAME
###
### Specify the node within the WAS 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 that the following
### characters are not permitted in the node name:
### ~ !@#$%^&*()_+{}|:"<>?`=[]\;',./
###
### Note: You must replace the "DefaultNode" value with the node name that you
### want to use for your default node.
###
###
-W nodeHost.nodeName="DefaultNode"
###
###
### WAS HOST NAME
###
### Specify the fully qualified host name or IP address of the
### computer running WAS. For example,
### "hostname.yourco.com".
### Note: Avoid using the underscore (_) character in machine names.
### Internet standards dictate that domain names conform to the host name
### requirements described in Internet Official Protocol Standards RFC 952 and
### RFC 1123. Domain names must contain only letters (upper or lower case) and
### digits. Domain names can also contain dash characters (-) as long as the
### dashes are not on the ends of the name.
###
###
-W nodeHost.hostName="hostname.yourco.com"
###
###
### Begin Installing Services
###
###
###
###
### INSTALL THE WEBSPHERE PORTAL SERVICE (WINDOWS ONLY)
###
### 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
###
### 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="/cdimg/IL-Setup"
###
###
### INSTALL CD LOCATIONS
###
###
###
###
### WAS CD LOCATION
###
### Directory path to the WAS 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.
###
### Conventions for specifying path information...
###
### CD Platform
### W-1 Windows for ia32
### W-2 Windows for amd64
### I-2 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-2 Solaris x64
### H-1 HP-UX parisc
### HI-2 HP-UX ia64
### ZL-2 Linux for zSeries
### PL-1 Linux for ppc32
### PL-2 Linux for ppc64
###
-W userInputCDLocWas.cdPath="/cdimg/IL-2"
###
### ARCHIVE CD 1
###
### Required for: Archive install
###
### Directory path to the first archive install image
###
### 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="/cdimg/IL-3"
###
### ARCHIVE CD 2
###
### Required for: Archive install
###
### Specify the directory path to the second archive install image
###
### 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="/cdimg/IL-4"
###
### CONFIGURATION ARCHIVE CD
###
### Required for: Archive install
###
### Directory path to the Portal configuration archive install image.
###
### CD Platform
### W-5 Windows
### IL-5 Linux for x86 or amd64
### A-5 AIX
### SS-5 Solaris sparc
### SO-5 Solaris x64
### H-5 HP-UX parisc
### HI-5 HP-UX ia64
### I-5 iSeries
### ZL-5 Linux for zSeries
### PL-5 Linux for ppc
###
### If installing on WAS 7 use *-5a
### For example use: W-5a or IL-5a
###
###
-W userInputCDLocProfile.cdPath="/cdimg/IL-5"
###
### Advanced Options
###
###
### Dependency Checking
###
### Disable prerequisite checking and input validation
###
### 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="true"
###
### Custom Dependency Files
###
### 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
###
### 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)
###
### 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)
###
### 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 <portname>=<value>
### 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)
###
### 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)
###
### 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)
###
### 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 <portname>=<value>
### 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)
###
### 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 WAS.
###
### 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
###
### 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)
###
### 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)
###
### 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"