Installing the product silently

You can perform a silent, or background installation by using files called response files. In this case, instead of displaying a graphical user ("wizard") interface, the silent installation causes the installation program to read all of your responses from a file that you provide. The response file responsefile.wps.txt can be used to silently install WebSphere Process Server. The response file is shipped with default values.

Before you start

Before installing WebSphere Process Server using this procedure, ensure that:
  • You are installing WebSphere Process Server for the first time and that you want to do so silently. If your proposed installation does not meet these criteria, see Installing the product for descriptions of other installation procedures.
    Draft comment:
    Add the following bullet when the Planning the installation section exists: You have reviewed the topics outlining possible installation topologies. See xref to Planning the installation topics.
  • Your system meets all hardware requirements and that you have installed all required software corequisites and prerequisites. See Hardware and software requirements for more information.
  • You have prepared your operating system for installation. See Preparing the operating system for installation for instructions.
  • You are installing the product as the root user on a Linux or UNIX system, or as a member of the Administrator group on a Windows system.
  • Draft comment:
    Steve: Do we need to add the bullet on disabling global security to this topic since it can cover the use case on using an Existing WAS or WAS ND?

Avoiding the use of the -silent option within the response file

Do not use the -silent option within the response file. Doing so can cause the profile creation to fail.

Response file location

The example responsefile.wps.txt response file can be found in the WBI directory on WebSphere Process Server CD 1. It does not get installed.

Important: Icon indicating AIX platforms On AIX platforms: To prepare the file for a silent installation on AIX, use UNIX line-end characters (0x0D0A) to end each line of the options response file. The safest method of preparing the file is to edit the file on the target operating system.

Required disk space

Refer to Required disk space for information on how much disk space will be required.

Installing WebSphere Process Server using the response file

To install WebSphere Process Server silently, do the following:
  1. Copy the file responsefile.wps.txt from the WBI directory on WebSphere Process Server CD 1 to a place that you can easily identify on your machine and save it with a new name, such as myoptionsfile.
  2. Edit this file using a flat file editor of your choice, on the target operating system, to customize it with the parameters for your system. Read the directions within the response file to choose appropriate values. A sample response file is shown in Example responsefile.wps.txt file.
    Important: Make sure that you change the license acceptance statement in the file to a value of "True". Leaving it with a value of "False" will cause the installation to fail.
  3. To create an operational WebSphere Process Server environment, you must have a profile. You can launch the Profile Wizard and create a profile silently by specifying certain values at the end of your copy of responsefile.wps.txt.
    • To launch the Profile Wizard and create a profile silently at the end of the installation process, do the following:
      1. At the end of your copy of responsefile.wps.txt, change the value of the option -W summaryPanel_InstallWizardBean.launchPCAW to true. For instance,
        -W summaryPanel_InstallWizardBean.launchPCAW="true"
      2. Copy the profile response file for the type of profile you want to create from the WBI directory on WebSphere Process Server CD 1 to a place that you can easily identify on your machine and save it with a new name, such as MyStandaloneProfile. The names of the original profile response files are:
        • Stand-alone server profile: responsefile.pcaw.wps.standAloneprofile.txt
        • Deployment manager profile: responsefile.pcaw.wps.dmgrProfile.txt
        • Custom profile: responsefile.pcaw.wps.managedProfile.txt
      3. Edit this profile response file using a flat file editor of your choice, on the target operating system, to customize it with the parameters for your system. Read the directions within the response file to choose appropriate values. See the following topics for more information:
      4. Change the value of the option -W pcawResponseFileLocationQueryAction_InstallWizardBean.fileLocation from "" to identify the absolute file path of the (modified) profile response file. For instance,
        -W pcawResponseFileLocationQueryAction_InstallWizardBean.fileLocation=
        "/opt/IBM/WebSphere/MyOptionFiles/MyStandaloneProfile.txt"
    • To not launch the Profile Wizard and create a profile silently, ensure that the value of the option -W summaryPanel_InstallWizardBean.launchPCAW is false. For instance,
      -W summaryPanel_InstallWizardBean.launchPCAW="false"
  4. Save your changes in your copy of responsefile.wps.txt.
  5. Use one of the following commands to install WebSphere Process Server. The commands shown assume that you have copied the responsefile.wps.txt file into a temporary directory and renamed it as myoptions.txt before customizing the file.
    • Icon indicating Linux platformsIcon indicating UNIX platforms On Linux and UNIX platforms:
      install -options /tmp/WBI/myoptions.txt -silent
    • Icon indicating Windows platforms On Windows platforms:
      install.exe -options "C:\temp\WBI\myoptions.txt" -silent
Verify the success of the installation by examining the WebSphere Process Server log file. If the last line of the file contains the word INSTCONFSUCCESS, the WebSphere Process Server features you selected and WebSphere Application Server Network Deployment were installed successfully. The log file is located as follows, where install_root represents the location of the WebSphere Process Server installation:
  • Icon indicating Linux platformsIcon indicating UNIX platforms On Linux and UNIX platforms: install_root/logs/wbi/log.txt
  • Icon indicating Windows platforms On Windows platforms: install_root\logs\wbi\log.txt
If this log file contains the string INSTCONFSUCCESS on the last line, then the installation was successful. Note that other terms such as INSTCONFPARTIALSUCCESS or INSTCONFFAILED can occur on other lines within the file, or even on the last line, but as long as INSTCONFSUCCESS is included in the last line, the installation was successful. If the installation was not successful, examine other log files to determine why. See the descriptions of relevant log files listed in Log files, of error messages in Error messages: installation and profile creation and augmentation, examine the section Troubleshooting below, and refer to Troubleshooting installation for tips on troubleshooting your installation.

If the installation was successful, after you have created a WebSphere Process Server stand-alone or deployment manager profile, start the server or deployment manager from its First Steps console to verify that your installation is operating properly. See Options on the First Steps console for more details.

Draft comment:
Use this text when the IVT actually checks WPS: If the installation was successful, after you have created a WebSphere Process Server stand-alone or deployment manager profile, run the Installation Verification Test (IVT) from the First Steps console to verify that your installation is operating properly. See "xref to Verifying the installation topic tins_ivt.dita" for more information.

Troubleshooting

Be precise when supplying values in the file: Customize the options response file precisely to let the installation program read the option values that the file contains. Incorrect specifications affect the silent interface of the Installation Wizard. For example, always use the correct case within property names, which are case-sensitive. In addition, always enclose values in double quotation marks.

If the error is an invalid option value, InstallShield for Multiplatforms (ISMP) displays a warning message that you must confirm and stops the installation.

Compare your options response file to the responsefile.wps.txt file that is shipped with the product to make the necessary corrections. After correcting the file, reinstall.

Certain events can prevent the InstallShield for Multiplatforms (ISMP) from starting the Installation Wizard silently. Such an event is not enough disk space to launch the Installation Wizard, for example. If your installation fails and there is no information in the installation logs, use the -log parameter to record entries for events that cause the ISMP program to fail to start the Installation Wizard. The syntax of the install command for logging such events is as follows:

Icon indicating AIX platforms On AIX platforms:
install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" 
        -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt  @ALL
Icon indicating HP-UX platformsIcon indicating Linux platformsIcon indicating Solaris platforms On HP-UX, Linux, and Solaris platforms:
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" 
        -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt  @ALL
Icon indicating Windows platforms On Windows platforms:
install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" 
            -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt  @ALL

Example responsefile.wps.txt file

The response file provided with the product, before modification, will be similar to the following:

################################################################################
#
# Licensed Material - Property of IBM
# 5724-L01
# (C) Copyright IBM Corporation 2005. All Rights Reserved.
# US Government Users Restricted Rights- Use, duplication or disclosure
# restricted by GSA ADP Schedule Contract with IBM Corp.
#
################################################################################
################################################################################
#
# InstallShield Options File
#
# Wizard name: Install
# Wizard source: setup.jar
#
# This file can be used to configure Install with the options specified below
# when the wizard is run with the "-options" command line option. Read each
# setting's documentation for information on how to change its value.
# 
# 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:
# 
#    -options "D:\installImage\WBI\responsefile.wps.txt" -silent
#
################################################################################
###################################################################################
#
# 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 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\WBI\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"
################################################################################
#
# Incremental Install
#
# If you are installing additional features on top of an existing installation,
# (e.g. incremental install), uncomment the following line.  This will notify
# the installer that you are doing an incremental install.
#
# -W wbiDetectionPanel_InstallWizardBean.optionSelected="1"
#
# Please make sure installLocation is set to your existing install location.
#
# For already installed features, you need to set the feature active property
# to false.  For new features you want to install, you need to set the active
# properties to true.
#
# For example, you have installed the Samples Gallery feature, now you want to
# install the Public API Javadoc(tm) feature, the active properties should be:
#
# -P brbeansProductFeatureBean.active="false"
# -P emsProductFeatureBean.active="false"
# -P samplesProductFeatureBean.active="false"
# -P javadocsProductFeatureBean.active="true"
################################################################################
#
# IBM WebSphere Process Server, V6.0 Install Location
#
# The install location of the product. Specify a valid directory into which the
# product should be installed. If the directory contains spaces, enclose it in
# double-quotes as shown in the Windows example below. Note that spaces in the
# install location is only supported on Windows operating systems.
# 
# Below is the list of default install locations for each supported operating
# system.  By default, in this response file, the Windows install location is
# used.  If you want to use the default install location for another operating
# system, uncomment the appropriate default install location entry (by removing '#') and
# then comment out (by adding '#') the Windows operating system entry below.
#
#
# AIX Default Install Location:
#
#    -P wbiProductBean.installLocation=/usr/IBM/WebSphere/ProcServer
#
#
# HP-UX, Solaris or Linux Default Install Location:
#
#    -P wbiProductBean.installLocation=/opt/IBM/WebSphere/ProcServer
#
#
# Windows Default Install Location:
#
-P wbiProductBean.installLocation="C:\Program Files\IBM\WebSphere\ProcServer"
################################################################################
#
# Use Existing IBM WebSphere Application Server V6.0
#
# If you intend to use an existing installation of WebSphere Application Server V6.0 or
# WebSphere Application Server Network Deployment, V6.0, uncomment the following line
# (by removing '#').
#
# -W wasdetectionpanelInstallWizardBean.optionSelected="1"
#
# You must then set the above WebSphere Process Server install location to the install root
# of the existing WAS installation.
#
# Note that the install will fail if WebSphere Process Server has already been installed
# in the existing WAS install location.
#
################################################################################
#
# Setup Type
#
# This value is required for the installation. Do not change this!
#
-W setuptypepanelInstallWizardBean.selectedSetupTypeId="Custom"
################################################################################
#
# "Business Rule Beans (deprecated)" feature
#
# The selection state of the "Business Rule Beans (deprecated)" feature. Legal 
# values are:
#
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
# 
# For example, to select "Business Rule Beans (deprecated)" for installation, use
#
#    -P brbeansProductFeatureBean.active="false"
#
-P brbeansProductFeatureBean.active="false"
################################################################################
#
# "Extended Messages (deprecated)" feature
#
# The selection state of the "Extended Messages (deprecated)" feature. Legal 
# values are:
#
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
#
# For example, to select "Extended Messages (deprecated)" for installation, use
#
#    -P emsProductFeatureBean.active="false"
#
-P emsProductFeatureBean.active="false"
################################################################################
#
# "Samples Gallery" feature
#
# The selection state of the "Samples Gallery" feature. Legal values are:
#
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
#
# For example, to select "Samples Gallery" for installation, use
#
#    -P samplesProductFeatureBean.active="true"
#
-P samplesProductFeatureBean.active="true"
################################################################################
#
# "Public API Javadoc (tm)" feature
#
# The selection state of the "Public API Javadoc (tm)" feature. Legal values are:
#
#    true  - Indicates that the feature is selected for installation
#    false - Indicates that the feature is not selected for installation
#
# For example, to select "Public API Javadoc (tm)" for installation, use
#
#    -P javadocsProductFeatureBean.active="true"
#
-P javadocsProductFeatureBean.active="true"
################################################################################
#
# WebSphere Process Server Profile Wizard
#
# To launch the Profile Wizard SILENTLY at the end
# of the installation, please change the value to "true".
# Otherwise, set the value to "false".
#
-W summaryPanel_InstallWizardBean.launchPCAW="false"
################################################################################
# If you choose to run Profile Wizard silently at the end of the
# installation, you must
# 1. get a copy of the Profile Wizard response file (from CD) and put to a temp dir
#    such as: /tmp/WBI/responsefile.pcaw.wps.dmgrProfile.txt           For DMGR profile creation
#             /tmp/WBI/responsefile.pcaw.wps.managedProfile.txt        For Manage profile creation
#             /tmp/WBI/responsefile.pcaw.wps.standAloneProfile.txt     For Stand alone profile creation
# 2. modify the response file by filling in the required options/values. 
# Note: If the values are not completed properly, the configuration may be unsuccessful. 
# 3. specify below the absolute path to your modified response file. 
# 
# For example,
# -W pcawResponseFileLocationQueryAction_InstallWizardBean.fileLocation=
# "/tmp/WBI/responsefile.pcaw.dmgrProfile.txt"-W
# pcawResponseFileLocationQueryAction_InstallWizardBean.fileLocation=""

Terms of use | | Broken links

Last updated: Tue Feb 21 17:40:17 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)