Replication Monitoring Services is designed to monitor the replication environment. When something happens in your environment, server and component status changes. These changes are displayed in the event log. RMS allows you to create event triggers to monitor these changes.
Event triggers notify you when some events occur in the replication environment. RMS executes the script when the specified event occurs. For example, a user can set up a script to be notified with an e-mail message when a connection suspends. You can create an event trigger for any server or component that the RMS monitors.
Creating an event trigger for a Replication Server
In the object tree, select the Replication Server.
On the right side of the desktop, select the event log pane.
Double-click the Add Server Event Trigger icon.
Select the status change that will trigger the event.
As an option, enter a “Wait before executing” value. This notifies RMS to wait for the event to change before executing the trigger.
To execute a trigger at each monitoring interval, rather than only once, select “Execute at Each Interval.”
Enter the name of the script for RMS to execute when the event occurs.
Click OK. The new event displays in the Event Log pane.
RMS API commands for trigger-related tasks are:
add event trigger – sets up a trigger, such as a process or a script, that is executed by the RMS when a specific event occurs.
drop event trigger – removes a trigger that the RMS is monitoring.
get triggers – displays information about the triggers that are monitored by the RMS.
For detailed information about these APIs, see Chapter 9, “Replication Monitoring Services API,” in the Replication Server Reference Manual.
