Network Deployment (Distributed operating systems), v8.0 > Applications > Service integration > High availability and workload sharing
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.
A WAS cell (the main administrative domain) consists of one or more server processes, which host resources such as applications or messaging engines. The cell is partitioned into groups of servers known as core groups, which are defined by the user. Each core group has its own high availability manager and operates independently of other core groups. Core group boundaries do not overlap. Within each core group are dynamic logical groupings of servers known as high availability groups. The HAManager determines the membership of the HAGroups at run time. Each core group can have a number of policies, which apply to particular HAGroups and determine the high availability behavior of resources running within the HAGroup.
See Set up a high availability environment for more information about WAS high availability in general.
Service integration high availability and workload sharing configurations