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" -silent
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" -silent
The granular assignment of applications to a Web server is new in Version 6.
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.
If no installation logs exist, refer to temporary log file, temporaryPluginInstallLog.txt in your temporary 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 -W silentInstallLicenseAcceptance.value="true" directive, the installation does not occur. The fact that the license entry was not accepted is recorded in temporaryPluginInstallLog.txt in the user temporary directory.
For example, the root user on a Linux system would normally find the file in the /tmp/temporaryPluginInstallLog.txt directory.
If any response file validation results in a failure, the failure is listed in the temporaryPluginInstallLog.txt file, then the installation fails.
install -options fully_qualified_options_response_file_name -silent -log # !fully_qualified_log_file_name @ALL
install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt @ALL
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt @ALL
install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt @ALL
Verify or troubleshoot the installation if the app_server_root/product/logs/log.txt file or the app_server_root/product/logs/wasprofile/pctLog.txt file does not contain a record of any problems, but problems exist.
If the error happens early in the installation, look for the logs in the system temporary directory. The installation program copies the logs from the system temporary directory to the logs directory at the end of the installation.
See Troubleshooting installation and Installation component troubleshooting tips for more information.
In a silent install, responsefile validation has been coded into the install. If response file validation does not pass, the failure is recorded in the temporaryPluginInstallLog.txt file.
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.
################################################################################ # # 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: # # install -options "responsefile.txt" -silent # ################################################################################ # Note: Synchronous Silent Installs # --------------------------------- # On non-Windows operating systems, silent installs will execute in a synchronous process. # The process will not return until the silent install has completed. # # For the silent install to run synchronously on Windows, you must run the # executable in the following way: # # START /WAIT install.exe -options "response_local.txt" -silent # # ################################################################################ ################################################################################ # # TROUBLE SHOOTING TIP # # If no signs of an install are visible, reference the temporary log file # (temporaryPluginInstallLog.txt) # in the user's temporary directory for signs of cause. # ################################################################################ # Note: Default Web server Plugins install locations # ---------------------------------------- # # Below are the default install locations for each supported operating system. # # AIX: "/usr/IBM/WebSphere/Plugins" # # HP-UX, Linux, and Solaris: "/opt/IBM/WebSphere/Plugins" # # Windows: "C:\Program Files\IBM\WebSphere\Plugins" # # Note: On unix operating systems, spaces in the install location is not supported. ################################################################################ ################################################################################### # # 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 # (temporaryPluginInstallLog.txt) # 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\plugins\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 Type # # Valid Options : local WebSphere Application Server and Web server on same machine # remote WebSphere Applicaiton Server and Web server on seperate machines. # -P pluginSettings.installType="local" ################################################################################ # # pluginDestination # # Web server Plugins for IBM WebSphere Application Server V6 install location # -P pluginProductBean.installLocation="C:\Program Files\IBM\WebSphere\Plugins" ################################################################################ # # WAS V6 Existing Location # # Valid Options : Existing WebSphere Application Server Version 6.0 install home directory. # # Note : This option is valid for local install type. # The install will use the directory entered below. # -W websphereLocationWizardBean.wasExistingLocation="C:\Program Files\IBM\WebSphere\AppServer" ################################################################################ # # Web server to configure # # Valid options # : none Install binaries only. No Web server configuration. # : ihs IBM HTTP Server V6 # : apache Apache Web Server V2 # : domino5 Lotus Domino Web Server V5 (supported on HP-UX) # : domino6 Lotus Domino Web Server V6 or V6.5 (not supported on HP-UX) # : sunone Sun ONE Web Server 6.0 or Sun Java System Web Server V6.1 # : iis5 Microsoft Internet Information Services V5 (supported on Windows) # : iis6 Microsoft Internet Information Services V6 (supported on Windows) # # Note : Specify only one Web server to configure. # -P pluginSettings.webServerSelected="ihs" ################################################################################ # # Web server Configuration File 1 # # Valid options for Web server configuration file 1 # # ihs : httpd.conf # apache : httpd.conf # domino5 : Notes.jar # domino6 : Notes.jar # sunone : obj.conf # # Note : File must exist # -P pluginSettings.webServerConfigFile1="C:\Program Files\IBM HTTP Server\conf\httpd.conf" ################################################################################ # # Web server Configuration File 2 # # Valid options for Web server configuration file 2 # # domino5 : names.nsf # domino6 : names.nsf # sunone : magnus.conf # # Note : File must exist # -P pluginSettings.webServerConfigFile2="" ################################################################################ # # Web server port number # # Specify the Web server port for the Web server selected to be configured. # -P pluginSettings.portNumber="80" ################################################################################ # # Domino 6 User ID # # Specify the Domino 6 User ID. (only specify value when configuring Domino 6 on # Linux, Solaris, and AIX platforms) # # Note : Domino 6 is supported on Windows, but this value is not required on Windows. # -W domino6UserIDPanel.userID="notes" ################################################################################ # # 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. # -P pluginSettings.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 installer generating # the plugin-cfg.xmlfile location at install time and configuring # Web server to use this location. This is the recommended option. # # "<file_location>" : User may enter an existing file location. Web server will be # configured to use this existing plugin-cfg.xml file location. # If file is specified, it must exist, or the install will not proceed. # -P pluginSettings.pluginCfgXmlLocation="" ################################################################################ # # WebSphere Application Server Machine HostName # # remote install type : enter the hostname of the WebSphere Application Server machine. # local install type : hostname of machine being installed to will be used. # -P pluginSettings.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 install. # -P pluginSettings.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 hostname detected on machine (Recommended) # "<HOSTNAME>" : Where <HOSTNAME> is a Web server hostname on the machine. # -P pluginSettings.webServerHostName=""