Capturing server events for workflow or API calls

The Server Events form captures the server changes that you record. You can use the Server Events form to notify other servers of cache changes if multiple servers are sharing the same database. The form can also notify interested clients of cache changes and user or group events. For more information, see Using-server-events-in-workflow.

Related topics

Types-of-events-you-can-record

Defining-workflow-to-automate-processes

The Server Events form enables you to capture server-related activities and use them in workflow and API programs. You can select the server events that you want to record, search and view the returned entries, and create a workflow to notify companion servers and interested clients of server changes that might affect them. For information about setting Server Event options, see Logging-server-events.

Tip

You might find server events especially helpful in a load-balanced environment. However, with the server groups feature, you do not need to use server events as part of the mechanism for communicating between servers in a load-balanced environment. For more information, see Configuring-a-hardware-load-balancer-with-AR-System.

To access this form in a browser, open the AR System Administration Console and click System > General > Review Server Events.

The following table describes the server events and the associated tasks:

Action

Reference

Understand how the server event form is created and how it is different from other forms.

Understand the type of server activities that you can record as server events. 

Learn how to specify the server activities that you want to log and make available for workflows or APIs. 

Understand how to view and interpret the server event records from the search results. 

Understand how to use a server event to trigger a workflow.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*