WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Deployment environment patterns

A deployment environment pattern specifies the constraints and requirements of the components and resources involved in a deployment environment. The patterns are designed to meet the needs of most business requirements and are intended to help you create a deployment environment in the most straightforward way.

A guided installation wizard exists to implement the patterns to simplify the installation process.

Each of the three deployment environment patterns addresses a specific set of requirements. Most requirement sets can be met using one of these patterns.

These descriptions are not intended as installation instructions. To create a deployment environment that fits one of the patterns, you make selections during installation, profile creation, or in the administrative console.

Single cluster pattern

The single cluster pattern is suitable for scenarios that are focused on running applications and on synchronous invocations. Any messaging requirements should be kept to a minimum with this pattern. Service Component Architecture (SCA) internal asynchronous invocations, the Java™ Message Service (JMS) and MQ messaging bindings do not support multiple messaging engines in the same cluster. If your modules require any of these, choose one of the other patterns, in which the messaging infrastructure is in a separate cluster from the application deployment target.

All components are run on a single cluster:
  • Service Component Architecture (SCA) application bus members
  • SCA system bus members
  • Common Event Interface (CEI) bus members
  • CEI server
  • Application deployment target

    You configure the application deployment target to support SCA applications.

Figure 1. Single cluster pattern
The image shows 3 nodes participating in a single cluster. All of the buses and deployment environment functions are supported by the single cluster.

Remote messaging pattern

The remote messaging pattern provides a separate cluster for the messaging role. This pattern is suitable for scenarios involving asynchronous invocations, because the cluster can be scaled for this load. The components are divided between the two clusters.

Remote messaging cluster:
  • Service Component Architecture (SCA) application bus members
  • SCA system bus members
  • Common Event Interface (CEI) bus members
Support infrastructure and application deployment target cluster:
  • CEI server application
  • Application deployment target

    You configure the application deployment target to support SCA applications.

Figure 2. Remote messaging pattern
The image shows two nodes taking part in the messaging function; while nodes 2 and node n take part in the support function and application deployment targets.

Remote messaging and remote support pattern

With this three-cluster pattern, resources are allocated to the cluster that handles the highest loads. This pattern is the most flexible and versatile, and is preferred by most users. The components are divided between the three clusters.

Remote messaging infrastructure cluster:
  • Service Component Architecture (SCA) application bus members
  • SCA system bus members
  • Common Event Interface (CEI) bus members
Remote support infrastructure cluster:
  • CEI server application
Application deployment cluster:
  • Application deployment target

You configure the application deployment target to support SCA applications.

Figure 3. Remote messaging and support pattern
A remote messaging cluster is shown on nodes 1 and 2; a remote support cluster, on nodes 2 and n; an application deployment cluster, on nodes 2 and n.

Resource allocation example

The following figure shows one way in which resources might be allocated using the remote messaging and remote support pattern. Because the heaviest load for this installation is for application use, there are more resources allocated (server1, server2 and server6) for the application deployment target cluster (Cluster 3) than the other functions.

Figure 4. Resource allocation example
Host A has Server 1 and Server 3. Host B has server 2, server 4, and server 5. Host C has server 6 and server 7.

concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/cpln_topologypat.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).