WebSphere Portal - Install WebSphere Portal with a response file

Install WebSphere Portal with a response file

+
Search Tips | Advanced Search

Contents

Overview
Response file parameters
Local install
Remote install

Overview

Use a response file, you can install WebSphere Portal without entering any information during the installation itself. Information you would normally enter as the installation progresses is instead gathered from the response file, which you can edit in advance to suit the needs.
Install with a response file is well suited to situations where the use of a graphical installation program is impractical or undesirable, or where you wish to install WebSphere Portal on multiple machines with a similar setup.
A sample response file, installresponse.txt, is located in the root directory of the Setup CD. Using a text editor, you can modify the values in this response file and use the Save as function to save the new response file to your local file system.
If you haven't already done so, review Installation scenarios before installing WebSphere Portal.
Hardware and software prerequisites should already be installed. Ensure that you have met the hardware and software prerequisites on the machine where you are installing WebSphere Portal, specifically for the memory and hard disk requirements.
You can override values in the response file by entering them on the command line itself. See the list of parameters below.
The response file you want to use must be on the same system as the Setup CD. In other words, if you are installing locally, the reponse file you want to use for the installation must be saved on the iSeries server. If you are installing remotely, the file must be saved on the Windows PC.
Only use the response file parameters documented here. The example response file may include parameters that are not valid for this version of WebSphere Portal.

Response file parameters

The following parameters can be specified in the response file or directly on the command line when issuing the install command.

Parameter default Description
-silent
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 logged.
If you want to use this response file but do not want to install silently, comment the parameter out.
-W userInputCDLoc2.cdPath="DIRECTORY_PATH"
WEBSPHERE APPLICATION SERVER CD LOCATION
Description: Specify the 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.
Note: This directory should contain the executable program used to launch the WAS installation program. For example: install.exe.
Replace the placeholder value "DIRECTORY_PATH" with the appropriate value for the system.
-W WPSCDLoc.cdPath="DIRECTORY_PATH"
WEBSPHERE PORTAL CD LOCATION
Description: Specify the directory path to the WebSphere Portal 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.
Note: This directory should contain the script files used to launch the WebSphere Portal Server installation program. For example: install.bat/install.sh.
Replace the placeholder value "DIRECTORY_PATH" with the appropriate value for the system.
-W basicConfig.choice="no"
WEBSPHERE PORTAL BASIC CONFIGURATION OPTION
Description: Specify whether you want to perform basic configuration of WebSphere Portal automatically when WebSphere Portal is installed. Although typically you will perform basic configuration automatically, there might be some situations where you want to install WebSphere Portal without performing configuration.
Note that if you do not perform configuration during installation, perform the configuration steps manually.
Values:

yes - Basic configuration is performed automatically as part of the WebSphere Portal installation. This is the default value and is assumed if the basicConfig.choice parameter is not specified.
no - Basic configuration is not performed during installation and must be performed manually after installation.

-W dependency.useValidation="false"
DISABLE DEPENDENCY CHECKING OPTION
Description: Specify whether you want to disable the prerequisite checking and input validation used during the WebSphere Portal installation. For example, due to changing product versions and capabilities, it is possible that you might be trying to install WebSphere Portal with a component that the installation program does not recognize as being at a supported level. However, if you are certain that the component should support WebSphere Portal, you can disable dependency checking and allow installation to continue.
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.rulesDirectory="DIRECTORY_PATH"
CUSTOM DEPENDENCY FILES LOCATION
Description: If you want to use custom dependency and validation rules, specify the directory where the custom rules files are located. This can be helpful when you do not want to disable dependency checking entirely but do need to tailor the dependency checking process for specific characteristics of the environment.
For information on using custom dependency and validation rules, refer to the dependency checking documentation in the WebSphere Portal Information Center.
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 the system.
-W os400DbUser.user=""
-W os400DbUser.password=""
DB2/400 USER PROFILE AND PASSWORD
Description: WebSphere Portal on iSeries deploys its configuration information directly to the DB2/400 iSeries database. The profile specified for the DB2/400 DB2 user will be the owner of the Portal database schemas. The user specified must be able to log onto the iSeries system, must have *USER authority, and must be able to create objects in the QSYS.LIB file system. When the basic configuration choice is specified as yes during a silent:
-W basicConfig.choice="yes"
a valid iSeries user profile and password for the target server must be specified.
-W wasInstance.wasInstance=""
WAS Instance
Description: This is the WAS instance where portal will be configured. The instance specified must be of type PME. When the basic configuration choice is specified as yes during a silent:
-W basicConfig.choice="yes"
a WAS instance of type PME must be specified.
-W installPortletsSequence.active="false"
INSTALL EMPTY WEBSPHERE PORTAL
Description: Specify whether you want to install WebSphere Portal as an empty portal, where WebSphere Portal is installed normally but no portlets are installed or deployed and no pages are created.
Values:

true - Portlets are installed and deployed and pages are created automatically. This is the default value and is assumed if the installPortletsSequence.active parameter is not specified.
false - Portlets are not installed or deployed and no pages are created.

Install WebSphere Portal locally with a response file

To install WebSphere Portal locally on the iSeries system, follow the instructions below.

Insert the WebSphere Portal Setup CD into the iSeries system.
Open an OS/400 command prompt and start the Qshell Interpreter by entering the following:
STRQSH

cd to the root directory of the CD...
cd /qopt/<cd_root>

where cd_root is the root directory of the WebSphere Portal Setup CD.
Enter the following to start installation:
install.sh -options "<path_to_file>/filename.txt"

where path_to_file is the full path to the response file containing the values you want to use for the installation, and filename.txt is the name of the file.
For security reasons, remove all user IDs and passwords from the response file when installation has completed.
Return to Installation scenarios to complete the installation process.

Install WebSphere Portal remotely with a response file

To install WebSphere Portal remotely from a Windows workstation connected to the iSeries system, follow the instructions below.

If you are installing on a machine with a firewall enabled, it is recommended that you disable the firewall before beginning installation.
If the WAS is not started, start it by entering the following command on an OS/400 command line:
STRSBS SBSD(QEJBAS5/QEJBAS5)

Insert the WebSphere Portal Setup CD.
Open a DOS command prompt and change to the root directory of the CD. For example, to change from the C:\ drive to the CD root directory on drive E:/, you would enter the following:
cd /D E:/<cd_root>

where cd_root is the root directory of the WebSphere Portal Setup CD. Note that the /D command is only necessary when changing from one drive to another.
Enter the following to start installation:
install400.bat <ISERIES_SYSTEM> <USER_ID> <PASSWORD> -options "<path_to_file>/filename.txt"

where ISERIES_SYSTEM is the name of the iSeries system on which you are installing WebSphere Portal, USER_ID and PASSWORD are the user ID and password you use to log on to that system, path_to_file is the full path to the response file containing the values you want to use for the installation, and filename.txt is the name of the file.
For security reasons, remove all user IDs and passwords from the response file when installation has completed.
Return to Installation scenarios to complete the installation process.

See also

Installation scenarios
Install remotely with the graphical interface
Install with the console interface

Parameter default	Description
-silent	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 logged. If you want to use this response file but do not want to install silently, comment the parameter out.
-W userInputCDLoc2.cdPath="DIRECTORY_PATH"	WEBSPHERE APPLICATION SERVER CD LOCATION Description: Specify the 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. Note: This directory should contain the executable program used to launch the WAS installation program. For example: install.exe. Replace the placeholder value "DIRECTORY_PATH" with the appropriate value for the system.
-W WPSCDLoc.cdPath="DIRECTORY_PATH"	WEBSPHERE PORTAL CD LOCATION Description: Specify the directory path to the WebSphere Portal 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. Note: This directory should contain the script files used to launch the WebSphere Portal Server installation program. For example: install.bat/install.sh. Replace the placeholder value "DIRECTORY_PATH" with the appropriate value for the system.
-W basicConfig.choice="no"	WEBSPHERE PORTAL BASIC CONFIGURATION OPTION Description: Specify whether you want to perform basic configuration of WebSphere Portal automatically when WebSphere Portal is installed. Although typically you will perform basic configuration automatically, there might be some situations where you want to install WebSphere Portal without performing configuration. Note that if you do not perform configuration during installation, perform the configuration steps manually. Values: yes - Basic configuration is performed automatically as part of the WebSphere Portal installation. This is the default value and is assumed if the basicConfig.choice parameter is not specified. no - Basic configuration is not performed during installation and must be performed manually after installation.
-W dependency.useValidation="false"	DISABLE DEPENDENCY CHECKING OPTION Description: Specify whether you want to disable the prerequisite checking and input validation used during the WebSphere Portal installation. For example, due to changing product versions and capabilities, it is possible that you might be trying to install WebSphere Portal with a component that the installation program does not recognize as being at a supported level. However, if you are certain that the component should support WebSphere Portal, you can disable dependency checking and allow installation to continue. 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.rulesDirectory="DIRECTORY_PATH"	CUSTOM DEPENDENCY FILES LOCATION Description: If you want to use custom dependency and validation rules, specify the directory where the custom rules files are located. This can be helpful when you do not want to disable dependency checking entirely but do need to tailor the dependency checking process for specific characteristics of the environment. For information on using custom dependency and validation rules, refer to the dependency checking documentation in the WebSphere Portal Information Center. 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 the system.
-W os400DbUser.user="" -W os400DbUser.password=""	DB2/400 USER PROFILE AND PASSWORD Description: WebSphere Portal on iSeries deploys its configuration information directly to the DB2/400 iSeries database. The profile specified for the DB2/400 DB2 user will be the owner of the Portal database schemas. The user specified must be able to log onto the iSeries system, must have *USER authority, and must be able to create objects in the QSYS.LIB file system. When the basic configuration choice is specified as yes during a silent: -W basicConfig.choice="yes" a valid iSeries user profile and password for the target server must be specified.
-W wasInstance.wasInstance=""	WAS Instance Description: This is the WAS instance where portal will be configured. The instance specified must be of type PME. When the basic configuration choice is specified as yes during a silent: -W basicConfig.choice="yes" a WAS instance of type PME must be specified.
-W installPortletsSequence.active="false"	INSTALL EMPTY WEBSPHERE PORTAL Description: Specify whether you want to install WebSphere Portal as an empty portal, where WebSphere Portal is installed normally but no portlets are installed or deployed and no pages are created. Values: true - Portlets are installed and deployed and pages are created automatically. This is the default value and is assumed if the installPortletsSequence.active parameter is not specified. false - Portlets are not installed or deployed and no pages are created.