The members of a service integration bus are the application servers and clusters within which messaging engines for that bus can run. In a deployment manager cell, you can have a bus consisting of multiple servers, some or all of which are members of server clusters.
Use this task to add servers and server clusters as members of a bus.
A service integration bus that consists of multiple servers provides advantages of scalability, the ability to handle more client connections and greater message throughput. You can also deploy SCA modules to different servers; for example, to provide different resources and qualities of service, or to provide some separation for different departments within organizations, or perhaps to separate test and production facilities.
By configuring a cluster bus member instead, a messaging engine has the ability to run in one server in the cluster, and if that server fails, the messaging engine can run in an alternative server. Another advantage of configuring a cluster bus member is the ability to share the workload associated with an SCA module across multiple servers. An SCA module deployed to a cluster bus member is partitioned across the set of messaging engines run by the cluster servers. The messaging engines in the cluster each handle a share of the messages passing through the SCA module.
If you configure a cluster or server to host the queue destinations used by the SCA runtime, it is added as a member of the SCA.SYSTEM bus. For more information about configuring a cluster or server to host the queue destinations used by the SCA runtime, see Configuring a server or cluster to host queue destinations for mediation modules.
To add a server or server cluster as a member of a service integration bus, complete one of the following sub-tasks:
Last updated: Mon Mar 27 18:01:23 2006
(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)