System Management Instances and Components
Overview
This topic describes the core and peripheral instances and their components within the System Management user interface.
Core Instance
A Core Instance is a collection of components of Callback software that are installed together and controlled by a single monitoring process (Core Monitor). A core instance contains the "core" of the Callback functionality including Queue Manager and components such as Provider and the Operation Mode service.
Two core instances are present in a high availability environment. This allows for "warm standby" redundancy.Only one core instance is active (primary) at a time, meaning only one Queue Manager is running. The other core instance (backup) is ready to take over when needed in the case of an automatic failover. You may also perform a manual failover from the primary to backup core instance at any time via the Make Primary button in the System Management interface. Core instances can be set to Maintenance Mode for scheduled shutdown and maintenance of a server.
One core instance is present in a standalone environment. This environment is not configured for warm standby redundancy.
Peripheral Instance
A Peripheral Instance contains components that are connected to a core instance, but may or may not be necessary for the operation of the system. An example of a peripheral instance would be one that includes a GlobalCall IVR.
There is no warm failover between peripheral instances. However, peripheral instances will connect to the new primary core instance upon failover.Components
A component is a service or program that performs a portion of Callback functionality. The System Management user interface shows information about each component that is a part of a core or peripheral instance.
- Non-controllable components are shaded gray and listed first in alphabetical order.
- Controllable components are unshaded and listed second in alphabetical order.
