CccaComponentSide

• Base type Enumeration

The functional components of the enterprise contact center application are fault tolerant. To achieve fault tolerance, two separate, interconnected, dependent hosts (one identified as 'sideA' and the other identified as 'sideB') will implement the functional component; one host will be the 'active' side and the other will be the 'standby' side. The two hosts are considered to be a 'duplex pair' of a functional component. This syntax is used to identify the side (A or B) that this host represents of a duplex pair of an enterprise contact center fault tolerant functional component. That one side is identified as 'sideA' does not imply that the 'A' side is always the primary; at any given time, either side could be the 'active' side. Setting the side identifier is completely arbitrary; the side is designated when installed and configured by the system administrator. When an event occurs that causes a fail-over from one side to the other, the side which was the 'standby' side then becomes the 'active' side while the previously-active side thus becomes the standby side. Most often, when the fail-over occurs, the side which was 'active' initiates a restart and then comes back up as the 'standby' side. The standby side is completely aware of the current status of the enterprise contact center application and is ready to assume functional responsibility immediately when instructed. When a fail-over occurs, there is little, if any, loss of functionality or context. Typically, a system impairment or failure event will cause a fail-over to occur but an administrator can initiate a fail- over by deliberately stopping the active side of a functional component.