Using event sequencing in a Network Deployment environment

Event sequencing can be used in a Network Deployment environment, with or without a high availability manager. Consult the table in this topic to ensure that your particular topology is supported.

Note that Service Component Architecture (SCA) destinations for any component using event sequencing cannot be partitioned. Therefore, if you are using clusters, you can have only one active messaging engine per cluster.

Table 1. Event sequencing support in a Network Deployment environment
Topology Is event sequencing supported?
Standalone server Yes
No clusters Yes
Applications are clustered. Messaging engines and destinations are not clustered. Yes
Messaging engines are clustered. Applications and destinations are not clustered. Yes
Messaging engines and destinations are clustered. Applications are not clustered. No. Clustered destinations are partitioned and cannot be used with event sequencing.
Applications and messaging engines are clustered (same cluster). Destinations are not clustered. Yes
Applications, messaging engines, and destinations are clustered (same cluster). No. Clustered destinations are partitioned and cannot be used with event sequencing.
Applications and messaging engines are clustered (different clusters). Destinations are not clustered. Yes
Applications, messaging engines, and destinations are clustered (different clusters). No. Clustered destinations are partitioned and cannot be used with event sequencing.

Using event sequencing in a high availability environment

High availability (HA) support means that system subcomponents, such as the event sequencing runtime, are made highly available and the workload can be distributed in the case of a node or daemon failure.

Although event sequencing requires a singleton service to process the event messages on a destination, an HA manager provides the necessary services to ensure that this process is not a single point of failure. Instead, the event sequencing runtime fails over to another server in the cluster in the event of a system crash.


Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)