Instead of using the Installation wizard, you
can install WebSphere ESB non-interactively, using a response file. This is
a simple text file that contains the information required by the installer.
The response file responsefile.esb.txt is shipped with default
values, and can be edited and used to silently install WebSphere ESB.
Before you begin
Before you silently install
WebSphere ESB you
must ensure that:
- your system meets all the hardware and software requirements. See http://www.ibm.com/software/integration/wsesb/sysreqs/ for
more information.
- you have prepared your operating system for installation. See Preparing the operating system for installation ..
- you are logged on as root on a Linux or UNIX system, or as a member of
the Administrator group on a Windows system.
Why and when to perform this task
The example
responsefile.esb.txt response file can
be found in the WBI directory on the product CD 1. It does not get installed.
Note:
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.
Steps for this task
- Copy the file responsefile.esb.txt from the WBI directory
on product CD 1 to a place that you can easily identify on your machine and
save it with a new name, such as myoptionsfile.
- 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,
as described in Customizing the options response file .
To create an operational WebSphere ESB environment
you must have a profile. You can create a deployment manager profile, a stand-alone
server profile, or a custom profile that becomes a managed node when you add
the node into a deployment manager cell.
You can create a profile silently
by customizing the profile options response file for the profile that you
intend to create, as described in
Creating profiles silently . The names of the original profile response files
are:
- Stand-alone server profile: responsefile.pcaw.esb.standAloneProfile.txt
- Deployment manager profile: responsefile.pcaw.esb.dmgrProfile.txt
- Custom profile: responsefile.pcaw.esb.managedProfile.txt
Do not add an options line to any of the profile creation response files
that includes the following parameter:
-silent
This is
not required. When the
WebSphere ESB silent
installation attempts to call a silent profile response file, this parameter
prevents the creation of the profile.
- Save your changes in your copy of responsefile.esb.txt.
- Type the command to install WebSphere ESB:
On Linux and UNIX platforms: mnt_cdrom/ESB/install
-silent -options /tmp/ESB/myoptionsfile.txt (where /tmp/ESB/myoptionsfile.txt is
the location of your customised response file).
On Windows platforms: "CD_drive_D:\ESB\install"
-silent -options "C:\temp\ESB\myoptionsfile.txt" (where C:\temp\ESB\myoptionsfile.txt is
the location of your customised response file).
Result
The Installation wizard and the Profile creation wizard record installation
events in the following log files:
On Linux and UNIX platforms:install_root/logs/wbi/log.txt
On Windows platforms: install_root\logs\wbi\log.txt
where
install_root represents the location of the
WebSphere ESB installation.
Verify
the success of the installation by examining this log file. If the last line
of the file contains the word INSTCONFSUCCESS, the
WebSphere ESB features
you selected and
WebSphere Application Server were
installed successfully.
Note: Terms such as INSTCONFPARTIALSUCCESS or INSTCONFFAILED
may appear in the log file, but as long as INSTCONFSUCCESS is included in
the last line, the installation was successful.
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:
install -options fully_qualified_options_response_file_name
-silent
-log # !fully_qualified_log_file_name @ALL

The
following example is for AIX sytems:
install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt"
-silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt @ALL

The following example
is for Linux systems, HP-UX systems, and Solaris systems:
install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt"
-silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt @ALL

The following example is for Windows
systems:
install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt"
-silent -log # !C:\IBM\WebSphere\silentFiles\log.txt @ALL
What to do next
If installation was successful, after you have created a
WebSphere ESB stand-alone
server or deployment manager profile, start the server or deployment manager
from its First steps console to verify that your installation is operating
properly.