Replication Environment Management Using RMS

To monitor a replication environment, you must set up a Replication Monitoring Services (RMS) domain. This domain consists of the servers in your environment you want to monitor using the RMS. In a three-tier management solution, the Replication Manager connects to the RMS, which then connects to the various servers in your replication environment.

To set up the RMS domain and monitor servers in this domain, you can either:

In a three-tier replication environment, you can perform some monitoring through Replication Manager, and additional monitoring through the RMS API at the command line.

The following topics provide information on how to monitor RMS using the Replication Manager plug-in and the API. For those tasks for which you can use both interfaces, only the Replication Manager plug-in is described in detail, while the name of API is identified. For those tasks that can be performed using only the API, detailed API information is given.

• Adding a Server
  Add servers to the Replication Monitoring Services (RMS) server folder in Sybase Central for monitoring.
• Dropping a Server
  Drop servers from the Replication Monitoring Services (RMS) domain.
• Viewing Monitored Objects in Sybase Central
  View monitored objects in Replication Manager the same as in a two-tier environment.
• Setting Configuration Parameters for Monitored Replication Objects
  Set the configuration properties for these replication objects monitored by Replication Monitoring Services (RMS): Replication Server, Replication Agent thread, remote RMS server, database connections and logical connections, and routes.
• Management of a Logical Group of Servers
  Replication Monitoring Services (RMS) enables you to define a set of servers as a logical group and monitor the group as a single entity.
• Suspending or Resuming Components in the Replication Environment
  Suspend or resume these monitored components in the replication environment: RepAgent in Adaptive Server, Replication Agent and DSI connection in Replication Server, routes, queues (resume only), and replication in a Replication Agent.
• Shutting Down Monitored Servers
  Shut down any monitored Replication Server, Replication Agent, or Mirror Replication Agents using Replication Monitoring Services (RMS).
• Server Rollup Status
  The RMS status shows the lowest status reported, for example, if the status of any server in the list is not UP, then the status for the RMS is reported as SUSPECT.
• Latency and Heartbeat Information Generation
  The RMS heartbeat feature uses the stored procedure rs_ticket to generate latency information, which is the amount of time it takes for a transaction to move from the primary database to the replicate database. You can use this information to monitor Replication Server performance, module heartbeat, replication health, and table-level quiesce.
• Creating an Event Trigger for a Replication Server
  Create event triggers to monitor server and component status changes.
• Related API Commands
  In addition to the Replication Manager plug-in, you can also use the Replicaiton Monitoring Services (RMS) API to monitor your replication environment.