High availability and workload sharing
Use these topics to learn about high availability and workload sharing.
- WAS high availability
- Workload sharing
- High availability
- Service integration high availability and workload sharing configurations
Subtopics
- WAS high availability
The WAS high availability framework eliminates single points of failure and provides peer to peer failover for applications and processes running within WAS. The WAS high availability framework also allows integration of WAS into an environment that might be using other high availability frameworks, such as HACMP, in order to manage non-WAS resources.- Workload sharing
We can configure multiple service integration messaging engines to distribute workload across multiple application servers. This allows us to scale out the system to handle larger workloads.- High availability
We can make messaging engines highly available in the service integration environment.- Service integration high availability and workload sharing configurations
The configuration of messaging engines in service integration is very flexible. We can have a single messaging engine that does not provide high availability or workload sharing. With a cluster bus member, we can have a single highly available messaging engine. Alternatively, with a cluster bus member, we can have multiple messaging engines that share workload, or that share workload and also provide high availability.
Related:
Mechanisms for stopping messaging engines Section 11.3 of the IBM Redbooks publication: WAS v6 System Management & Configuration Handbook Set up a high availability environment