Working with events

RM enables you to add a trigger that the RMS server executes when a specific event occurs in the replication domain. A trigger identifies a process or script to execute. An example of an event is when the status of a server or component changes.

Event triggers are only implemented in a three-tier environment.
If the controlling RMS is selected in the left pane, all event triggers defined within the replication domain are displayed in the Event tab window.
If you select a server in the left pane, event triggers defined for the server are displayed in the Event tab window.
If a Replication Server is selected in the left pane, the “Add Server Event Trigger” and “Add Component Event Trigger” wizards display in the Event tab window. The window also displays any existing event triggers defined for the selected server or for components of the server. The properties of the defined event triggers are displayed in the window.
If any other server is selected in the left pane, only the “Add Server Event Trigger” wizard displays in the Event tab window. The window also displays any existing event triggers defined for the selected server. The properties of the defined event triggers are displayed in the window.
Double click one of the “Add” entries to open a dialog box, and define an event trigger.
Component event triggers can be created on components of a server. Currently, only components of a Replication Server can have event triggers: connection, logical connection, route, queue, and partition.

You can also work with event triggers through the RMS API. See the Replication Server Reference Manual for more information about adding event triggers through the API.