Monitoring the quality of data in a grid
Monitor the quality of replicated data on servers in a grid so that the Connection Manager can route client applications to the servers based on the apply failures and transaction latency.
When the quality of data is monitored, the Connection Manager can route client connections to the replication servers based on the number of apply failures, the transaction latency, and the workload. When the quality of data is not monitored, the Connection Manager can route client connections based on the workload only. The Connection Manager uses service level agreements (SLAs) to determine which server to connect with a client application. SLAs are configured on the pages.
To monitor the quality of replicated data for a grid:
- On the OAT menu, click .
- On the Routing Topology page or the Server List page, select a server in the grid to be the master server for data quality.
- On the Actions menu, click Modify Server.
- Select the option to monitor the quality of data.
When the quality of data is monitored, the number of failed transactions on the replication servers in a grid are counted. When you synchronize data, you can reset the failed transaction count on the replication servers in the grid or you can continue to add to the current count. To maintain accurate information about the quality of data, reset the count when you synchronize the data.
The failed transaction count is reset on the Replicates page with the Check or Sync Data action. or