Before installing WebSphere® ESB,
you must ensure that a series of prerequisites have been met.
The prerequisites are:
- Plan your installation.
For more
information about planning your installation and on the databases
required by WebSphere ESB,
see the topics under Planning for WebSphere ESB.
- Ensure that your system meets all hardware and software requirements,
and that you have enough space (including temporary space) for your
installation. See http://www.ibm.com/support/docview.wss?uid=swg27006912 for more information.
- An installation package (IIP) containing WebSphere Application Server Network Deployment
and Feature Pack for Web Services is installed as part of the WebSphere ESB installation.
There are restrictions for the type of integrated IIP that can be
used along with the WebSphere ESB installer.
- The IIP must contain WebSphere Application
Server Network Deployment and Feature Pack for Web Services.
- The IIP must be at the same or a higher maintenance level than
required by the WebSphere ESB installer.
- The IIP must have only one primary offering of WebSphere Application Server Network Deployment
and one additional offering of Feature Pack for Web Services.
- The WebSphere Integration
Developer product comes with a default integration test client. If
you plan to use this installation of WebSphere ESB as
the integration test client instead, refer to Planning to install WebSphere Enterprise Service Bus for use by WebSphere Integration Developer for information on how to set
up this scenario.
- Prepare your operating system for installation. See Preparing the operating system for WebSphere ESB installation for links to platform-specific
information.
- If you plan to install WebSphere ESB over
an existing installation of WebSphere Application
Server or WebSphere Application
Server Network Deployment, ensure that the product architectures match.
You cannot install a 32–bit version of WebSphere ESB over
a 64–bit version of WebSphere Application
Server or WebSphere Application
Server Network Deployment; you cannot install a 64–bit version of WebSphere ESB over
a 32–bit version of WebSphere Application
Server or WebSphere Application
Server Network Deployment.
- If you plan to install from images obtained from Passport Advantage®, see Special considerations when installing from Passport Advantage for
guidelines concerning user permissions and directory setup.
- Ensure that DB2® is started
by the database instance owner prior to installing WebSphere ESB.
Database administrator (DBA)
privileges are required for the database configuration panels that
are part of creating a deployment manager profile for a deployment
environment. If you plan to use the deployment environment feature
of the product installer or Profile Management Tool, and want to use
a database other than Derby Network Server as your database product,
the user ID you provide for the "User name to authenticate with the
database" field on the database configuration panels must have DBA
privileges.
The user ID requires DBA privileges even if you
elect to postpone database creation during the installation or profile
creation procedure. This is because electing to postpone database
creation prevents creation of the Common database only. When the installer
or Profile Management Tool configures a deployment environment (clustered
topology), it also creates the required tables and schemas on the
back-end database server for the Business Process Choreographer, the
Common Event Infrastructure, and the messaging engines -- in addition
to the Common database. This requires that the user ID have DBA privileges
so that these schemas and tables can be created without database permission
errors.
If the user ID does not have DBA privileges, use this
workaround:
- Install the product without creating a profile.
- Use the Profile Management Tool to create the deployment manager
and the custom profiles using the Advanced path for all. Do not use
the Typical or Deployment environment paths. Select the option to
delay the execution of the database scripts during deployment manager
profile creation.
- Federate the custom profiles to the deployment manager.
- Have the DBA create the Common DB. The information at the following
site provides the necessary scripts to manually create database objects: Creating the Common database and tables after profile creation or augmentation.
- Using the administrative console, create the required deployment
environment. See Creating deployment environments for more
information.
- If you plan to use DB2 Universal Database™, you must perform the following steps before
installing:
- If you are configuring a DB2 database
on a DB2 client with the server
on a remote system, make sure the client system is configured to communicate
with the server and that the DB2 node
is cataloged. For more information, refer to the DB2 Universal Database documentation.

On Linux® and UNIX® platforms: If you are
configuring a DB2 database on
a Linux or UNIX system, source the database environment
by performing the following steps: - Modify /etc/group and make sure the user
ID that installed the product is in the same group as the db2instance.
- Source the database environment by running the db2instance/sqllib/db2profile script
(replace db2instance with the name of your database
instance).
- Stop all server, deployment manager, and node agent processes
on any products for which you intend to add features, or that you
plan to extend. For instructions on how to perform these tasks, see Stopping servers and nodes.
- Uninstall all maintenance packages on products you intend to
add features to or that you plan to extend. Start the Update Installer
program with the updi_root/update command
to search for and uninstall all maintenance packages. Do this because
features and components necessary to convert the products have not
had any maintenance applied to them. If you remove all maintenance
packages, your entire product will be at the same release level. You
can then reapply the maintenance packages.
On Linux platforms: Ensure
that your WebSphere ESB installation
has the following items:- Kernel and C runtime library
- Current and
all compatibility versions of the C++ runtime library
- X Window libraries and runtime
- GTK runtime libraries
If the prerequisites are satisfied, you are ready to install the
product.