This topic describes the response file for performing a silent installation of the Web server plug-ins for WebSphere Application Server.
Install the product silently using an options response file.
The responsefile.txt file has directives that set installation options. Comments in the file describe how to set the string value for each directive.
Use the options file to run the Plug-ins installation wizard in silent mode, which is referred to as installing silently. The wizard reads the options file to determine responses and does not display the graphical user interface. Use the following command to use a copy of the options file named myresponsefile.txt for a silent installation:
install -options myresponsefile.txt
The sample options response file is named responsefile.txt. The file is in the plugin directory on the product disc or in the downloaded installation image.
The Plug-ins installation wizard can read an existing options response file and run silently without displaying the graphical user interface.
The options file supplies the values to the Plug-ins installation wizard when installing silently. The wizard reads the options file to determine responses and does not display the graphical user interface. Use the following command to use a copy of the options file named myresponsefile.txt for a silent installation:
install -options myresponsefile.txt
As you install an application, you can install it on the Web server definition in addition to the application server. All applications on the Web server definition are listed in its plug-in configuration file. After propagation, the real Web server can access the applications.
The sample options response file, responsefile.txt, controls installing the binary plug-ins, configuring the Web server, and creates a script for creating the Web server definition on a remote application server machine. The script is customized according to values supplied in the responsefile.txt file. The script is generated to run on the application server machine to create the Web server definition.
If the Web server is on the same machine as a stand-alone application server, the responsefile.txt file can create the Web server definition directly without creating a script. To edit and use the response file for installing the plug-ins and configuring the Web server and application server, perform the following procedure:
install -options path/myresponsefile.txt
If no installation logs exist, refer to temporary log file, log.txt in your <userhome>/plglogs directory. You can also cause ISMP to record status about a problem that is preventing the installation from occurring, as described in the following section.
For example, if you start the silent installation without accepting the license in the -OPT silentInstallLicenseAcceptance="false" directive, the installation does not occur. The fact that the license entry was not accepted is recorded in log.txt in the <userhome>/plglogs directory.
If any response file validation results in a failure, the failure is listed in the plglogs file, then the installation fails. If all validations pass, the installation occurs. Then, the Plug-ins installation wizard records installation events in the following log files. The log files are in the plugins_root/logs/install directory:
Edit the version of the file that ships with your WebSphere Application Server product. The following example is not guaranteed to be an accurate representation of the file that ships with the product.
# ********************************************************************** # # Response file for Web Server Plug-ins for WebSphere Application # Server V6.1 Install # # ********************************************************************** ################################################################################ # # A common use of an options file is to run the wizard in silent mode. This lets # the options file's author to 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 "/<responsefile.path>/responsefile" # ################################################################################ ################################################################################ # # Invoke the install wizard in silent mode for both local and remote install # whenever the response file is used. # -silent ################################################################################ # # TROUBLE SHOOTING TIP # # If no signs of an install are visible, reference the log file (plglogs/log.txt) # in the /tmp/InstallShield directory for signs of a cause. # ################################################################################### # # 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 /tmp/InstallShield/plglogs temporary directory. # # By changing this 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>/plugin/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" ################################################################################ # # Operating System Prerequisite Checking # # If you want 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" ################################################################################ # # install Type # # Valid Options : # local WebSphere Application Server and Web server on same machine # remote WebSphere Application Server and Web server on separate machines. # -OPT installType="local" ################################################################################ # # Plugins Install Location # # The desired install location of Web Server Plugins for IBM WebSphere # Application Server V6.1. Specify a valid directory into which the product # should be installed. This directory must be either empty or not exist. # # Below is the default Web Server Plugins install location for the i5 # operating system. # # i5OS Default Install Location: # # -OPT installLocation="/QIBM/ProdData/WebSphere/Plugins/V61/webserver" # -OPT installLocation="/QIBM/ProdData/WebSphere/Plugins/V61/webserver" ################################################################################ # # Profile Location # # The desired install location of Web Server Plugins profiles. For new installs, # specify a valid directory into which the profiles should be installed. This # directory must be either empty or not exist. # # Below is the default profile install location for the i5 operating system. # # i5OS Default Profile Install Location: # # -OPT defaultProfileLocation="/QIBM/UserData/WebSphere/Plugins/V61/webserver" # -OPT defaultProfileLocation="/QIBM/UserData/WebSphere/Plugins/V61/webserver" ################################################################################ # # Allow Profile Location Override # # This option allows users to overrule the empty default profile location requirement. # # Valid values: # true - Allow profile location override # false - Do not allow profile location override # # If desired, uncomment the following entry # # -OPT allowOverrideProfileLocation="true" # ################################################################################ # # WAS V6.1 Existing Location # # Valid Options : Existing WebSphere Application Server V6.1 install home directory. # # Note : This option is valid for local install type. # The install will use the directory entered below. # # Below is the default WebSphere Application Server install location for the i5 # operating system. # # i5OS Default Install Location: # # -OPT wasExistingLocation="/QIBM/ProdData/WebSphere/AppServer/V61/<EDITION>" # # where Edition = "Express" for WebSphere Application Server - Express # = "Base" for WebSphere Application Server # = "ND" for WebSphere Application Server Network Deployment # -OPT wasExistingLocation="/QIBM/ProdData/WebSphere/AppServer/V61/Express" ################################################################################ # # Web server to configure # # Valid options # : none Install binaries only. No Web server configuration. # : ihs IBM HTTP Server V6 or V6.1 # : domino6 Lotus Domino Web Server V6 or V6.5 (not supported on HP-UX) # # Note : Specify only one Web server to configure. # -OPT webServerSelected="none" #=============================================================================== # # IHS-specific Administrator settings # #=============================================================================== # # HTTP Administration Port number # # Specify the HTTP Administration Port number (only specify value when configuring IHS) # -OPT ihsAdminPort="" # # IHS Administrator User ID/Group for IHS Administration server # # Specify the IHS Administrator server userid and user group. (only specify value # when configuring IHS) # -OPT ihsAdminUserID="" -OPT ihsAdminUserGroup="" # #================================================================================ ################################################################################ # # Web Server Configuration File 1 # # Valid options for Web Server configuration file 1 location # # ihs : httpd.conf # domino6 : Notes.jar # # Note : File must exist # # Below is the default Web Server Configuration file location for the i5 # operating system. # # i5OS Default Web Server Configuration file Location: # # For IHS (IBM HTTP Server) # -OPT webServerConfigFile1="/www/<YourWebServerName>/conf/httpd.conf" # # For Lotus Domino 6 # -OPT webServerConfigFile1="/QIBM/ProdData/LOTUS/DOMINO605/Notes.jar" # -OPT webServerConfigFile1="" #=============================================================================== # # DOMINO-specific settings # #=============================================================================== # # Web server Configuration File 2 # # Valid options for Web server configuration file 2 location # # domino6 : names.nsf # # Note : File must exist # # File can be found under the DOMINO instance directory you defined when # you created your DOMINO instance # -OPT webServerConfigFile2="" ################################################################################ # # Domino 6 User ID # # Specify the Domino 6 User ID. # -OPT domino6UserID="notes" # #================================================================================ ################################################################################ # # Web server port number # # Specify the Web server port for the Web server selected to be configured. # -OPT webServerPortNumber="80" ################################################################################ # # Web server Definition Name # # A web server definition allows for Web server administration through the WebSphere # admin console. # # Note : No spaces are allowed in the Web server definition name. # -OPT webServerDefinition="webserver1" ################################################################################ # # plugin-cfg.xml File Location # # This file will be generated by the plugin installer. # # Valid options: # "" : leaving the string empty will result in the installer generating the # plugin-cfg.xml file location at install time and configuring the Web # Server to use this location. This is the recommended option. # # "<file_location>" : User may enter an existing file location. The Web Server # will be configured to use this existing plugin-cfg.xml file # location. If a file is specified, it must exist, otherwise # the install will not proceed. # -OPT pluginCfgXmlLocation="" ################################################################################ # # WebSphere Application Server Machine HostName # # remote install type : enter the hostname of the WebSphere Application Server machine. # local install type : "" (hostname of the machine being installed to will be used.) # -OPT wasMachineHostName="" ################################################################################ # # Advanced User Options available in silent installs only # # Map all the existing deployed applications to the Web server. # # Valid Options # true : Web server Definition is mapped as a target to the existing # deployed applications such as snoop and hitcount (Recommended) # false : No applications are mapped to the Web server definition. # # Note : If not set to a valid option of true or false, the installer will set to # true and continue the install. # -OPT mapWebserverToApplications="true" ################################################################################ # # Web server Hostname # # In advanced scenarios where a user has multiple Web server hostnames on a # machine, set the entry below to the Web server hostname used to configure. # # Valid Options : # "" : Install will resolve to the hostname detected on the machine (Recommended) # "<HOSTNAME>" : Where <HOSTNAME> is a Web server hostname on the machine. # -OPT webServerHostName="" ################################################################################ # # WAS Profile Name # # Specify the name of the WAS Profile to be configured. This option is only valid # in local install scenarios. # # Valid options: # "<WAS_profile_name>" : User must enter the name of an existing WAS profile # leaving the string empty will result in the installer # using the name of the default profile # Example: -OPT profileName="AppSrv01" # -OPT profileName=""