Silently installing WebSphere Process Server or the Client

You can perform a silent, or background installation on a distributed system 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 or the Client. The response file is shipped with default values.

Before you begin

Before installing using this procedure, ensure that:
  • You want to install silently and that you do not have WebSphere Process Server or the Client already installed. If your proposed installation does not meet these criteria, see Installing the software for descriptions of other installation procedures.
  • You have decided on the type of installation you prefer:
    • A Custom installation, which lets you select the product features you wish to install. It can also install WebSphere Application Server Network Deployment, and allows you to run the Profile wizard at the end of the installation to create a WebSphere Process Server profile.
    • A Client installation, which installs the WebSphere Process Server Client and can install WebSphere Application Server Network Deployment.
  • You have decided whether to install WebSphere Application Server Network Deployment as part of your WebSphere Process Server or Client installation or to instead use an existing installation of WebSphere Application Server or WebSphere Application Server Network Deployment, version 6.0.x.x.
  • You have reviewed possible installation topologies in Planning installation topologies.
  • 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.

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 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 response file. The safest method of preparing the file is to edit the file on the target operating system.

Required disk space

For information on space requirements, see WebSphere Process Server detailed system requirements at http://www.ibm.com/support/docview.wss?uid=swg27006205 and select the link to your version of WebSphere Process Server.

Installing using the response file

To install 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. An example 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.
    If you are installing a WebSphere Process Server Client environment, go to step 4. If you are installing a WebSphere Process Server environment, go to step 3.
  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 Creating profiles silently 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. To create an operational WebSphere Process Server Client environment, do not select any of the optional features (such as samples and JavadocTM) and do not create a profile as part of the installation. Doing so will cause the installation to fail. Refer to the sample response file for an example of how to create a Client installation.
  5. Save your changes in your copy of responsefile.wps.txt.
  6. 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 platforms Icon 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 log.txt log file. If the last line of the file contains the word INSTCONFSUCCESS, the components you selected were installed successfully. The log file is located as follows, where install_root represents the location of the WebSphere Process Server or Client installation:
  • Icon indicating Linux platforms Icon 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. Also refer to Recovering from profile creation or augmentation failure for troubleshooting tips if the profile did not create successfully.

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. You can also use the installation verification tools to verify your installation. See Using the installation verification tools 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 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 (for example, not having enough disk space to launch the Installation wizard). 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 platforms Icon indicating Solaris platforms On HP-UX and Solaris platforms:
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" 
        -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt  @ALL
Icon indicating Linux platforms On Linux 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 WebSphere Process Server, before modification, is similar to the following:
################################################################################
#
# Licensed Material - Property of IBM
# 5724-L01, 5655-N53 
# (C) Copyright IBM Corporation 2005, 2006. 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 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\LICENSES.  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.
#
# 

-G licenseAccepted="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:
#
# NOTE: The Windows operating system limits the length of a fully qualified path 
#       to 256 characters. A long pathname for the installation root directory makes
#       it more likely that this limit will be exceeded when files are created during 
#       normal product use. IBM recommends that you keep the pathname of the installation
#       root directory as short as possible.

-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
#
# The type of installation you wish to perform. Legal values are:
#
#    Custom  - Performs a custom installation of WebSphere Process Server, including
#              optional features which can be enabled below.
#    Client - Performs a client-only installation of WebSphere Process Server. Optional
#             features such as Samples and Javadocs are not installed. 
#
#    Additional Notes for a Client Install
#       - When running a client install, all features must be set to "false"
#       - The Profile Wizard cannot be started after a Client-only Install
#
# For example, to perform a Client installation, use
#
#    -W setuptypepanelInstallWizardBean.selectedSetupTypeId="Client"

-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"
#
# This value must be set to false for "Client" only installs.

-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"
#
# This value must be set to false for "Client" only installs.

-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"
#
# This value must be set to false for "Client" only installs.

-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"
#
# This value must be set to false for "Client" only installs.

-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".
#
# This option does not apply for the "Client" Setup Type.


-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.wps.dmgrProfile.txt"
#
# This option does not apply for the "Client" Setup Type.


-W pcawResponseFileLocationQueryAction_InstallWizardBean.fileLocation=""

Last updated: Wed 01 Nov 2006 07:47:12

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