Installing
WebSphere ESB is
a two-step process.
- The first step is to use the installation wizard to install a shared set
of core product files. These system files include command files
and other shared product binary files. System files can be updated by installing
refresh packs or fix packs.
- The second step is to use the Profile creation wizard to
create one or more profiles to make use of the shared system
files. Each profile defines a separate run-time environment, with separate
files (commands, configuration files, log files, and so on).
You do not have to install the product more than once on the same
machine to have multiple profiles. Install the product once and use the Profile
creation wizard to create multiple profiles.
Within WebSphere ESB,
a running server process, such as a deployment manager, can create, read,
update, or delete the configuration files, data files, and log files in its
profile. The server process has read-only access to the system files.
Figure 1. Separation of system files and profiles
WebSphere ESB can
be installed as either a stand-alone server or as a group of managed servers.
Scenarios
for installation
The following information describes scenarios for
installing the product in various topologies on one or more machines. Two
types of
WebSphere ESB topologies
are possible:
- Topologies for a stand-alone server
- Topologies for a managed group of servers
Topologies for a stand-alone server
A stand-alone
server profile has its own administrative console and all of the sample applications
(if you installed the Sample applications gallery feature). Each stand-alone
server is fully operational and is managed independently from all other servers.
The
following topologies for a stand-alone server is described in this topic:
- Scenario 1: Single-machine installation with one stand-alone server
- Scenario 2: Single-machine installation with multiple stand-alone
servers
- Scenario 3: Single-machine, with multiple installations
When installing for the first time, the recommended choice is
to use the Complete installation procedure. A Complete installation is the
easiest way to install WebSphere ESB,
and creates a fully-operational stand-alone server with the topology of scenario
1.
Topologies for a managed group of servers
A managed
group of servers is called a cell. After installing the WebSphere ESB software,
you use the profile wizard to create a deployment manager profile.
A
deployment manager manages the configuration for all of the managed nodes
in its cell and deploys applications to any managed node in the cell. All
of the profiles in the cell share command files and other product binaries
that are created during WebSphere ESB installation.
The
main reason to use managed nodes in a cell rather than using the same number
of stand-alone servers is the centralized administration that the deployment
manager provides for the cell.
To create a WebSphere ESB managed
node, you create a custom profile then federate the custom profile into the
cell.
The following topologies for a cell are described in this topic:
- Scenario 4: Single-machine installation for a cell of servers
- Scenario 5: Multiple
- -machine installation for a cell of servers, with the deployment manager
on its own machine
WebSphere ESB is
built on WebSphere Application Server Network Deployment.
You can augment WebSphere Application Server profiles
to become WebSphere ESB profiles,
converting from a WebSphere Application Server scenario
to WebSphere ESB.
Each of the following scenarios includes a diagram and a list
of detailed installation steps.
- Scenario 1: Install WebSphere ESB with
one stand-alone server on a single machine.
The simplest scenario
is to install WebSphere ESB on
a single machine with a stand-alone server profile. Each stand-alone application
server profile includes a server1 application server process. Installing WebSphere ESB creates
the set of system files. The Profile creation wizard creates the stand-alone
server profile. The profile is a separate data partition with files that define
the stand-alone server environment.
Figure 2. One stand-alone server
profile on a single machine
The easiest way to create a stand-alone server is to perform
a Complete installation. With a Complete installation, you get
a stand-alone server profile named default with a server
named server1.
- Perform a Complete
installation of WebSphere ESB. This installs the core product files and creates the first stand-alone
server profile.
- Start server1 using the First steps console or the startServer
server1 command.
- Scenario 2: Install WebSphere ESB with
multiple stand-alone servers on a single machine.
After installing
the WebSphere ESB system
files once on a machine, you can create several stand-alone server profiles
on the same machine.
This topology lets each profile have unique modules
and applications, configuration settings, data, and log files, while sharing
the same set of system files.
Creating multiple profiles creates multiple,
separate, server environments that you can dedicate to different purposes.
For example, each stand-alone server profile can form a separate Enterprise
Service Bus, for different departmental groups or organizations. In another
example, a stand-alone server profile can be a separate test environment that
you assign to a programmer or a development team.
You can use the same
procedure to create multiple stand-alone servers on more than one machine.
Updating
the core product files
By using multiple profiles with the same
system files, you get enhanced serviceability. When a refresh pack or a fix
pack updates the core product files on a machine, all of the server profiles
that were created from those files begin using the updated files.
- Perform a Complete
installation of WebSphere ESB. This installs the core product files and creates the first stand-alone
server profile.
- Start server1 for using the First steps console or the startServer
server1 command.
- Create
another stand-alone server profile using the Profile creation wizard on the
same machine.
- Scenario 3: Install multiple copies of WebSphere ESB with
stand-alone servers on a single machine.
In some situations,
you might prefer to not update all of the servers on a machine; for example,
to continue providing business services with some servers while applying service
to other servers. In such situations, simply install the product a second
time to create a second set of core product files. You can manage incrementally
the product updates to each installation.
Figure 3. Multiple copies
of WebSphere ESB on
a single machine
- Perform a Complete
installation of WebSphere ESB. This installs the core product files and creates the stand-alone
server profile.
- Perform another Complete
installation of WebSphere ESB. This installs another, separate set of core product files on the
same machine, and creates the stand-alone server profile to use the new set
of core product files.
- Scenario 4: Install a cell of managed server
nodes on one machine.
WebSphere ESB can
create a cell of managed servers on a single machine from one installation
of the core product files. The Profile creation wizard is first used to create
the deployment manager. After starting the deployment manager,
return to the Profile creation wizard to create one or more custom nodes.
When
you federate a custom node into the deployment manager cell, the node is converted
into a managed node. You then need to create a server, using the default WebSphere ESB server
template, to be able to deploy SCA modules onto the managed node.
The
deployment manager provides the administration for all managed nodes that
are in its cell. Each managed node has a server process, called the node
agent, that the deployment manager uses to manage servers on that node.
To be able to start servers, you must first start the node agent.
Periodically
the configuration and application files on a managed node refresh from the
master copy of the files hosted on the deployment manager during synchronization.
In
a cell, only the managed nodes run modules and applications, not the deployment
manager.
In certain secure environments, the Profile creation wizard
cannot federate a custom profile into a cell. Such cases require you to use
the addNode command instead. If you have configured the
deployment manager to use a JMX connector type other than the default SOAP
connector, use the addNode command to add the node to the
cell.
Figure 4. A managed node in a deployment manager cell
- Perform a Complete
installation of WebSphere ESB. This installs the core product files and creates the stand-alone
server profile that you can use to test the installation, for development,
and other uses. If you do not want to keep the stand-alone profile, you can
delete it later. Otherwise, you can perform a Custom installation, then create
the profiles that you want.
- Create
a deployment manager profile using the Profile creation wizard.
- Start the deployment manager using the First steps console or
the startManager command.
- Create a custom profile using the Profile creation wizard. During profile creation, choose whether to federate the custom node
then or later.
- Federate the custom node into the deployment manager cell. You can federate a custom node when creating the custom profile. Instead,
if you want to federate the custom node later, you can use the procedure described
in Federating custom nodes to a deployment manager
- Create a server or server cluster.
- Configure the server or cluster
for the SCA runtime required by mediation modules. Before
deploying any mediation modules onto the new server or cluster, configure
the server or cluster to indicate where queue destinations used by the SCA
runtime for the module are to be hosted.
- Start the server or cluster. You
can use the First steps console, administrative console, or the startServer
server1 command to start
a server. You can use the administrative console to start
a server group.
If you want more managed nodes on the same machine, you can repeat
steps 4 through 8 for
each new node.
If you want to add managed nodes on another machine,
that is much the same installation procedure, and is described more in Scenario
5.
- Scenario 5: Install a cell of managed server
nodes on several machines, with the deployment manager on its own machine.
The primary advantage of a cell over a stand-alone application server
is its scalability. Managing a cell to keep it in proportion with workload
levels is possible. In this scenario, the deployment manager is on machine
A, machine B has a managed node with a server, and machine C has a managed
node with a server cluster. All of the managed nodes are federated into the
same deployment manager cell.
The deployment manager can be on the same
machine as some of the managed server nodes or on its own machine.
Having
multiple machines and multiple managed nodes lets you use vertical and horizontal
scaling:
- Vertical scaling creates multiple managed nodes on the same
physical machine.
- Horizontal scaling creates cell members on multiple physical
machines.
Figure 5. Several managed nodes in a multi-machine
deployment manager cell
- On machine A, perform
a Complete installation of WebSphere ESB. This installs the core product files and creates the stand-alone
server profile that you can use to test the installation, for development,
and other uses. If you do not want to keep the stand-alone profile, you can
delete it later. Otherwise, you can perform a Custom installation, then create
the profiles that you want.
- Create
a deployment manager profile using the Profile creation wizard.
- Start the deployment manager using the First steps console for
Dmgr01 or the startManager command.
- On machine B, perform
a Complete installation of WebSphere ESB. This installs the core product files and creates the stand-alone
server profile on machine B.
- Create
a custom profile. During profile creation, choose whether
to federate the custom node then or later.
- Federate the custom node into the deployment manager cell. You can federate a custom node when creating the custom profile. Instead,
if you want to federate the custom node later, you can use the procedure described
in Federating custom nodes to a deployment manager
- Create
a server.
- Configure the server for the
SCA runtime required by mediation modules. Before deploying
any mediation modules onto the new server, configure the server to indicate
where queue destinations used by the SCA runtime for the module are to be
hosted.
- Start the server. You can use the First steps console,
administrative console, or the startServer server1 command
to start
a server.
- On machine C, perform
a Complete installation of WebSphere ESB. This installs the core product files and creates the stand-alone
server profile on machine B.
- Create
a custom profile. During profile creation, choose whether
to federate the custom node then or later.
- Federate the custom node into the deployment manager cell. You can federate a custom node when creating the custom profile. Instead,
if you want to federate the custom node later, you can use the procedure described
in Federating custom nodes to a deployment manager
- Create a cluster.
- Configure the cluster for
the SCA runtime required by mediation modules.
- Start
the server cluster.
You can review common installation scenarios to find a possible
match for the topology that you intend to install. Each product installation
diagram provides a high-level procedure for installing the components that
comprise the topology.
After determining a possible topology, follow the steps in the
overall procedure.