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


Deployment environments

A deployment environment is a collection of configured clusters, servers, and middleware that collaborates to provide an environment to host Service Component Architecture (SCA) interactions. For example, a deployment environment might include a host for message destinations and administrative programs.

Planning deployment environments requires that you design the physical layout (topology) of the deployment environment so you can meet your business needs for capacity, availability, scalability and failover support. Some key aspects of the design involve the number and relative placement of the servers on the hardware that comprises your deployment environment.

Stand-alone environment

It is possible to deploy mediation modules to a stand-alone server. This is the easiest environment to set up, but a stand-alone server does not connect to other servers, its capacity is limited to the resources on the same computer system, and it does not include failover support.

If you require more capacity, scalability, availability or failover support than a stand-alone server provides, you need to consider a deployment environment of interconnected servers.

Interconnected servers

A deployment environment is a collection of interconnected servers that supports mediation modules

The servers in a deployment environment can run on one or more host systems. Servers can be grouped into clusters to support load-balancing and failover.

In addition to the performance, availability, scalability, isolation, security, and stability characteristics that cannot be provided by a stand-alone server, a deployment environment of interconnected servers or clusters has the additional advantage that you can manage all the servers or clusters from a centralized deployment manager.

Deployment environment patterns

Creating a deployment environment is straightforward if you use one of the supplied deployment environment patterns, provided you know your requirements and plan accordingly. There are three patterns:
  • Single cluster.
  • Remote messaging.
  • Remote messaging and remote support.
If none of the patterns meet your requirements, you can plan and create your own customized deployment environment.

Deciding when to create the deployment environment

In addition to planning the deployment environment, you must also decide when to create it. You can choose one of the following options:
  1. Create the deployment environment when you install the software, using the installation wizard or silent installation.
  2. Install the software on the host systems that you intend to use. Then use the Profile Management Tool or manageprofiles command to create the deployment environment.
  3. Install the software on the host systems that you intend to use. Use the Profile Management Tool or manageprofiles command to create deployment manager and custom profiles. Then create the deployment environment using the administrative console of the deployment manager.
The option you choose depends on the complexity of the deployment environment. If one of the supplied deployment environment patterns meets your requirements, choose option 1 or 2; if none of the supplied patterns meet your requirements, choose option 3.

Regardless which method you use to create the deployment environment, you can still manage some aspects of the deployment environment using the administrative console. (For example, you can add more nodes to the deployment environment.) However some aspects you cannot change if you created the deployment environment using options 1 or 2. (For example, you cannot change database types.)


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_depenv.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).