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

Creating a multiple enterprise service bus topology

You might want to deploy and manage SCA modules in a distributed bus environment; for example, with separate enterprise service buses for different departments or to separate test and production facilities.

Why and when to perform this task

Each stand-alone profile or deployment manager profile that you create has its own administrative cell that can be seen as the administrative domain for a separate enterprise service bus.

Your complete bus environment might be made up of several stand-alone and deployment manager cells, each representing a separate enterprise service bus, with its own SCA.SYSTEM bus used for SCA modules.

Besides the SCA.SYSTEM bus used for SCA modules, you can also create other service integration buses that you can use to support the service integration logic provided by the modules. For example, the SCA.APPLICATION.cell_name.Bus is provided and used to define JMS queue destinations and other JMS resources for modules deployed with JMS bindings.

You can create other buses for use as in WebSphere Application Server; for example, for applications acting as service requesters and providers within WebSphere ESB, or to link a bus to WebSphere MQ.

You can also use a WebSphere ESB deployment manager to manage separate application servers, for use with applications and modules deployed onto WebSphere Application Server.

Whilst you can use these other buses separately, you can also connect them to allow messages to pass between the buses. You can also connect together buses in different organizations. When buses are interconnected, applications can send messages to applications on other buses, and use resources provided on other buses. Published messages can span multiple buses where the links between the buses are configured to allow it.

A service integration bus must be contained within a single cell; that is, a bus cannot span multiple cells. However, a cell can contain more than one bus. In this case, each bus in the cell is "foreign" to each other bus in the cell. You can connect buses together within a cell, or between different cells.

The process for linking one bus to another bus is the same, whether the buses are in the same cell or in different cells.

Figure 1. A multiple-enterprise service bus topology
Each enterprise service bus has its own SCA.SYSTEM bus on which you deploy mediation modules.

There are several different ways to create a multiple enterprise service bus topology; for example:

Steps for this task

  1. Install a single-server enterprise service bus on one machine. Complete the steps to create installation scenario 1 This effectively creates one enterprise service bus, with its own SCA.SYSTEM bus.
  2. Install a cell of managed server nodes on several machines. Complete the steps to create installation scenario 5 with the server clusters distributed across managed nodes, across several machines, according to your needs.

    If you want one or more of the nodes on the same machine, you can either use the same installation of WebSphere ESB or use separate installed copies of WebSphere ESB on the same machine.

What to do next

You can now run the WebSphere ESB samples and deploy service applications into your enterprise service bus.
Related concepts
An enterprise service bus with links to WebSphere MQ networks
Related tasks
Planning WebSphere ESB installation scenarios

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\tjj0004_.html

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