If you do not want to use the graphical user interface
to install WebSphere® ESB,
you can perform a silent, or background, installation on a distributed
system by using files called response files. Instead of displaying
a graphical user interface, or a "wizard," the silent installation
causes the installation program to read all of your responses from
a file that you provide. An example response file, responsefile.wesb.txt, is shipped with
default values and can be used to silently install WebSphere ESB.
Response files, also called options files, are used to pass command-line
options to the installation program.
Before you begin
Windows® Vista™
and Windows 2008 operating
systems: Performing a silent installation of
WebSphere ESB Version
6.2 on these operating systems requires Administrator privileges.
If you launch the silent installation using standard user privileges,
you are presented with an elevation prompt for Administrator privileges
before you are allowed to continue. You can avoid this prompt by running
the silent installation from a Command Prompt window that is opened
by performing the following actions:
- Right-click a Command Prompt shortcut.
- Click Run As Administrator.
Important: 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.
For more information about installing from the
command line, see the WebSphere ESB Technote Additional Information for Silent Installation of WebSphere Process Server.
Procedure
To install silently using the
response file, perform the following steps.
- Log on to the operating system.

On Linux® and UNIX platforms: After inserting
a DVD into a drive, some Linux and UNIX operating systems require
you to mount the drive.
- Copy the sample response file responsefile.wesb.txt from the WBI directory
on the disc labeled WebSphere Enterprise
Service Bus V6.2
DVD to a place that you can easily identify on your system,
and save it with a new name, such as myoptionsfile.txt.
- Edit the file using a flat file editor of your choice on the target
operating system, customizing it with the parameters for your system.
Read the directions in the response file to choose appropriate values
for all of the options you must set for your specific silent installation.
You
can modify all of the parameters in the response file, but pay attention
to the following options and values:
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" causes the installation
to fail.
For example, the License Acceptance should be: -OPT
silentInstallLicenseAcceptance="true"
- Change the value of the wpsInstallType option
to designate one of the following types of installation:
- For a typical installation you must have a profile to create an
operational WebSphere ESB environment.
You can create a profile silently by specifying certain values in
your response file that will create a profile during the installation
process. Change the value of the option profileType to
one of the following values:
- deploymentManager - creates a profile with a deployment manager.
For example:
-OPT profileType="deploymentManager"
- standAlone - creates a profile with a stand-alone server. For
example:
-OPT profileType="standAlone"
- custom - creates a profile with an empty node, which you can configure
after installation.
-OPT profileType="custom"
- none - does not create a profile during installation. Use this
value if you do not want to create a profile during the silent installation
process. After installation, you will need to run the Profile Management
Tool in order to create a profile.
-OPT profileType="none"
All profile-related options in the responsefile.wesb.txt file begin with
PROF_. (The options are the same as parameters for the manageprofiles
command, but in the response file, they begin with the prefix PROF_
to designate them as profile options.) You can modify these profile
options depending on what you have selected for profileType. For more
information, read the descriptions in the response file.
Note: If
you want to use the response file to create a new profile for an existing
installation, comment out the
-OPT installType="installNew" section
of your response file, remove the comments from the
-OPT createProfile section
of the response file, and change the value of the option
-createProfile to
true.
For example:
#-OPT installType="installNew"
-OPT createProfile="true"
- If you designated a deployment environment installation (-OPT
wpsInstallType="ndGuided"), you must designate additional
options to define that installation. Change the value of the ndGuidedInstallType option
to one of the following values:
For more information about the deployment environment, see Planning
for WebSphere ESB and Implementing a deployment environment.
Note: You can always go back to the WebSphere Enterprise
Service Bus V6.2 DVD
in the WBI directory to view the example response
file responsefile.wesb.txt and review the
default options and values.
- Save your changes in your copy of the response file.
- Run the command to install WebSphere ESB using
your custom response file. The commands shown assume that you have
copied your response file into a temporary directory and renamed it
as myoptions.txt before customizing the file.
Run the following command from either the product DVD or from
the temporary location where you have saved the contents of the electronic
image from Passport Advantage®.

On Linux and UNIX platforms: install
-options /tmp/WBI/myoptions.txt -silent
On Windows platforms:
install.exe -options "C:\temp\WBI\myoptions.txt" -silent
What to do next
Verify the success of the
installation by examining the
log.txt log file.
The log file is located as follows, where
install_root
represents the location of the
WebSphere ESB:

On Linux and UNIX platforms: install_root/logs/wbi/install/log.txt
On Windows platforms: install_root\logs\wbi\install\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 if INSTCONFSUCCESS
is included in the last line, the installation was successful.
If
the string INSTCONFPARTIALSUCCESS or INSTCONFFAILED appears in the
last line of the file without INSTCONFSUCCESS, problems were detected
during installation. INSTCONFPARTIALSUCCESS indicates that the installation
completed but errors were generated; INSTCONFFAILED, that the installation
failed completely.
See the description of all log files in Installation and profile creation log files.
You can review other useful
troubleshooting information in the following topics:
If the installation was successful, and you chose to
create a stand-alone profile or deployment manager profile, you can
start the server or deployment manager from its First steps console
to verify that your installation is operational. See Options on the First Steps
console for more details. You can also use the installation
verification tools to verify your installation. For more information,
see Verifying the installation.