WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Planning WebSphere ESB installation scenarios

There are various scenarios in which you can use WebSphere ESB. The different scenarios affect how you install WebSphere ESB. This topic describes common installation scenarios and links to the associated installation procedures.

Before you begin

Installing WebSphere ESB is a two-step process.
  1. 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.
  2. 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
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.

Why and when to perform this task

Each of the following scenarios includes a diagram and a list of detailed installation steps.

Alternatives for this task

Result

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.

What to do next

After determining a possible topology, follow the steps in the overall procedure.

After creating your WebSphere ESB, you can run the samples to explore its functions. You can also move on to deploy your own mediation modules, or to adapt the server and bus environment to your needs.

Related concepts
An enterprise service bus with links to WebSphere MQ networks
Related tasks
Choosing a bus environment
Creating a single-server enterprise service bus
Creating a multiple-server enterprise service bus without clustering
Multiple-server enterprise service bus with clustering
Creating a multiple enterprise service bus topology

Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\tasks\twesb_instscenarios.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)