About The Cisco Crs Engine - Cisco CRS-1 - Carrier Routing System Router Administration Manual

About the Cisco CRS Engine

Note
About the Cisco CRS Engine
Cisco Customer Response Solutions Administration Guide, Release 4.1(1)
1-8
Cluster management consists of two main elements:
Cluster Manager—Receives updates about cluster status and subsystem
•
states.
Cluster View Daemon (CVD)—Java code that interacts with NodeManager
•
and implements inter-node communication on behalf of the cluster. It detects
availability of the other nodes, components and services, provides consistent
cluster view and dynamically elects a master service. .
The CVD has two interfaces:
One that monitors inside the node, using:
•
– Node Manager to monitor and control local processes.
Cluster Manager publisher/subscriber to communicate with local
–
applications, such as Step Editor and Application Administration.
Another that monitors outside the node and communicates with other nodes
•
in the cluster.
For detailed information about CRS clusters, see
CRS System."
The Cisco CRS Engine (CRS Engine) enables you to run multiple applications to
handle Java Telephony Application Programming Interface (JTAPI) calls or
HTTP requests.
While you can deploy the CRS Engine and Unified CM on the same server,
deploying them on separate servers allows you to handle greater call volume.
The CRS Engine uses JTAPI to request and receive services from the Computer
Telephony Interface (CTI) manager that controls Unified CM clusters. The CRS
Engine is implemented as a Windows service that supports multiple applications.
You can use a web browser to administer the CRS Engine and your CRS
applications from any computer on the network. You can use the
CRS Administration web interface to start and stop the CRS Engine, configure
system parameters, monitor CRS Engine activity, and view real-time and
historical reports that include total system activity and application statistics.
Chapter 1 Introducing Cisco Customer Response Solutions
Chapter 8, "Managing the Cisco