Setting Up the Latency Monitoring Process

Start the latency monitoring process for replication paths in the replication environment.

Prerequisites

Install and configure all the servers to be monitored. Verify that these servers have been registered and added to the Perspective Resources, and that you have the permission to perform this task.
Note: All resources in the path must be registered and authenticated for latency monitoring to take place. If ASE servers are not registered and authenticated, connection information cannot be obtained for latency monitoring.
The primary and replicate Replication Servers must be at version 15.1 or later. For a non-SAP primary database, the Replication Agent must also be version 15.1 or later.
To use rs_ticket in a replication environment to measure the latency of non-SAP replicate databases, you must install JDBC drivers to enable SAP Control Center for Replication to connect to those non-SAP replicate databases. See SAP Control Center Installation Guide > Installing JDBC Drivers for Third-Party Replicate Databases.

Task

From the Perspective Resources view, select a Replication Server and click Resource > Monitor.
Click Paths.
Select a path from the list.

Note: When selecting or highlighting a path, click outside the Path Name column. Clicking the path name opens the path dashboard.
Click Quick Admin to display the latency monitoring process administration view for the selected path.

Note: If the selected path's primary and replicate Replication Servers, or the Replication Agent for a non-SAP primary database, are not at version 15.1 or later, the Quick Admin option is disabled.

All replicate databases to which the selected path replicates data are listed in the administration view. For Adaptive Server databases, all parameters are populated automatically. For non-SAP databases, you need to provide the parameters manually in the administration view.
Specify the replicate database information, start and end dates, and the repeat interval time.
For non-SAP databases, click Test Connection to verify that the connection information is valid.
Repeat this step for all the listed replicate databases.
Click Start.

You can click the bar graph icon in the upper-right corner of the Latency window in the Replication Server Monitor's Paths view or in the Replication Path Dashboard to see the detailed latency history.

Latency Monitoring Process
Latency monitoring means executing the rs_ticket command at the primary database, retrieving the latency data from the replicate database, and storing the results in the SAP Control Center repository.

Parent topic: Configure

Previous topic: Authenticating a Login Account for a Managed Resource

Next topic: Setting Up Statistics Collection

Related concepts

Replication Latency

Related tasks

Stopping the Latency Monitoring Process

Displaying Latency

Related reference

Latency Chart Details

Data on Dashboards or Charts Is Missing