Cisco Cisco Unified IP Interactive Voice Response (IVR) 8.0(1) Administrator's Guide
4-6
Cisco Unified CCX Serviceability Administration Guide Release 8.0(1)
Chapter 4 Using Tools
Using a Command Line Interface to Start and Stop Services
•
Click the radio button before the service that you want to stop and click the Stop button.
The Status changes to reflect the updated status.
•
Click the radio button before the service that you want to restart and click the Restart button.
A message indicates that restarting may take a while. Click OK.
•
To get the latest status of the services, click the Refresh button. The status information is updated
to reflect the current status.
to reflect the current status.
Using a Command Line Interface to Start and Stop Services
You can start and stop some services though the Command Line Interface (CLI). For a list of services
that you can start and stop though the CLI and for information on how to perform these tasks, refer to
the Command Line Interface Reference Guide for Cisco Unified CCX.
that you can start and stop though the CLI and for information on how to perform these tasks, refer to
the Command Line Interface Reference Guide for Cisco Unified CCX.
About Unified CCX Datastore
Datastores are components that allow you to manage and monitor historical, agent, repository, and
configuration data across all servers in the Unified CCX cluster.
configuration data across all servers in the Unified CCX cluster.
Note
Support for High Availability and remote servers is available only in multiple-server deployments.
The Unified CCX Cluster uses the publisher/subscriber database model for data replication across the
system. Under normal circumstances, the database master acts as the source of data and the other node
acts as the target for the data. In other words, the database master is the publisher and the other node is
the subscriber.
system. Under normal circumstances, the database master acts as the source of data and the other node
acts as the target for the data. In other words, the database master is the publisher and the other node is
the subscriber.
Note
In the Tools > Datastore Control Center > Datastores web page, the first node installed in the cluster
is marked as publisher (with an icon marked P). This should not be confused with the
is marked as publisher (with an icon marked P). This should not be confused with the
publisher/ subscriber model being discussed here. In Unified CCX 8.0(1), the term publisher is used to
denote only the first node in the cluster and does not indicate that node to be the source of the data. The
publisher/subscriber mentioned in these pages refer to the source and destination of the data respectively.
Typically, the database master node acts as the source and the other node acts as the destination.
denote only the first node in the cluster and does not indicate that node to be the source of the data. The
publisher/subscriber mentioned in these pages refer to the source and destination of the data respectively.
Typically, the database master node acts as the source and the other node acts as the destination.
The publisher/subscriber database model enables Unified CCX to provide high-availability and failover
support. To support this on the database level, the data must be available on multiple nodes of the cluster.
To have such data availability, replication is used for the Agent, Historical, and Repository datastore.
The Configuration datastore does not use replication; instead, it uses atomic transactions to commit data
changes to all active Configuration datastores in the cluster.
support. To support this on the database level, the data must be available on multiple nodes of the cluster.
To have such data availability, replication is used for the Agent, Historical, and Repository datastore.
The Configuration datastore does not use replication; instead, it uses atomic transactions to commit data
changes to all active Configuration datastores in the cluster.