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

Creating a single-server enterprise service bus

The simplest topology is an enterprise service bus consisting of a single server, as created if you install WebSphere ESB in a stand-alone server profile.

Why and when to perform this task

In a single-server enterprise service bus, the SCA.SYSTEM bus has the one server as its only bus member. When you install a mediation module into WebSphere ESB, the queue destinations used by the module are defined on that bus member. These queue destinations are used by the SCA runtime exploited by the mediation module as a robust infrastructure to support asynchronous interactions between components and modules.

The server hosts a messaging engine that provides the service integration technologies used by the queue destinations and the processing of requests.

Figure 1. A single-server bus. A bus environment showing one service integration bus, with one ESB server as a bus member. This figure also shows an SCA module deployed into the bus environment, where the destinations needed are assigned to the bus member.A bus environment that comprises one server. The SCA.SYSTEM bus has the server as a bus member, which contains a messaging engine.

In a stand-alone profile, there can be only one messaging engine in a bus, a topology that is adequate for some scenarios.

A single messaging engine might not be adequate if the number of client connections becomes excessive, if the rate of message throughput cannot be sustained by the one messaging engine, of if the size of messages needs more space than the one messaging engine can provide in its data store.

To add more than one messaging engine to a service integration bus, you need to use a profile for a managed node in a deployment manager cell.

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.

Steps for this task

  1. Perform a Complete installation of WebSphere ESB. This installs the core product files and creates the first stand-alone server profile.
  2. Start server1 using the First steps console or the startServer server1 command.

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

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