Cisco Cisco IPCC Web Option Maintenance Manual
A different mechanism is used for the real-time data feed to Administration & Data Servers or
Administration Clients. See the "
Administration Clients. See the "
" section,
for more information.
Node Manager
Each Unified ICM component (except the Administration Client) includes a Node Manager
process. The Node Manager is in charge of restarting Intelligent Contact Management processes
that have failed. For example, each Logger and each CallRouter has its own Node Manager. If
a Logger and CallRouter are installed on the same machine, two separate Node Managers run
on that machine. If Loggers for multiple customers run on a single machine, a separate Node
Manager runs for each customer.
process. The Node Manager is in charge of restarting Intelligent Contact Management processes
that have failed. For example, each Logger and each CallRouter has its own Node Manager. If
a Logger and CallRouter are installed on the same machine, two separate Node Managers run
on that machine. If Loggers for multiple customers run on a single machine, a separate Node
Manager runs for each customer.
When a failure occurs in a single-customer Unified ICM system, the Node Manager might shut
down the machine to initiate a reboot. However, in a Cisco Unified Intelligent Contact
Management Hosted environment when a Logger or CallRouter fails, components for other
customers might still be active on the machine. In such a case, the Node Manager for a Cisco
Unified Intelligent Contact Management Hosted component does not shut down and reboot the
machine, and manual intervention is required to restore the failed component.
down the machine to initiate a reboot. However, in a Cisco Unified Intelligent Contact
Management Hosted environment when a Logger or CallRouter fails, components for other
customers might still be active on the machine. In such a case, the Node Manager for a Cisco
Unified Intelligent Contact Management Hosted component does not shut down and reboot the
machine, and manual intervention is required to restore the failed component.
If the Node Manager does initiate a reboot, the Node Manager itself restarts when the machine
reboots. The Node Manager then starts the other processes for the component.
reboots. The Node Manager then starts the other processes for the component.
To set up automatic restart for any component, access the Web Setup tool's Service Management
page to set a component's service as Automatic rather than Manual.
page to set a component's service as Automatic rather than Manual.
See Also
For more information on Node Manager start-up options, refer to the Installation Guide for
Cisco Unified ICM/Contact Center Enterprise & Hosted.
Cisco Unified ICM/Contact Center Enterprise & Hosted.
Central Controller
The Central Controller includes the CallRouter and Logger. The CallRouter and Logger processes
are typically on separate computers. However, in smaller call center configurations the CallRouter
and Logger processes can be on the same computer. The Logger process is always on the same
computer.
are typically on separate computers. However, in smaller call center configurations the CallRouter
and Logger processes can be on the same computer. The Logger process is always on the same
computer.
Note: Beginning with Unified ICM 7.0(0), the Logger changed from a single process to two
running processes—one process handling configuration data and the other handling historical
data. This allows parallel processing of the two kinds of data and, thus, a more efficient Logger.
However, these two processes are still part of a single Logger node; that is, the functionality of
the Logger remains essentially unchanged. Therefore, throughout this manual, reference will
generally continue to be made to the Logger, without distinguishing between the separate
processes. However, you should be aware that the new split in the Logger does affect failure
and failover behavior. For example, if the historical Logger on side A fails, the system fails
over to the historical Logger on side B; however, the still functioning configuration Logger on
side A continues to be used.
running processes—one process handling configuration data and the other handling historical
data. This allows parallel processing of the two kinds of data and, thus, a more efficient Logger.
However, these two processes are still part of a single Logger node; that is, the functionality of
the Logger remains essentially unchanged. Therefore, throughout this manual, reference will
generally continue to be made to the Logger, without distinguishing between the separate
processes. However, you should be aware that the new split in the Logger does affect failure
and failover behavior. For example, if the historical Logger on side A fails, the system fails
over to the historical Logger on side B; however, the still functioning configuration Logger on
side A continues to be used.
Administration Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 8.x
18
Chapter 2: Fault Tolerance
Central Controller