Using server events in workflow
Recording server events enables you to communicate internal (non-data) server changes to processes outside the server and to use workflow to notify companion servers or interested clients of changes that affect them.
You can create workflow that is triggered when a server event is recorded. For example, you might want to create a filter that fires when an entry is submitted to the Server Events form, indicating that an object change occurred. The filter should execute a Run Process action that runs the arsignal program to force a companion AR System server to reload its cache. The filter should have one such action for each companion server.
To make the machine1 server reload its cache, construct the filter run process action as follows:
arsignal -g machine1
If machine1 was running on specific port 2033, the action would be as follows:
arsignal -g machine1:2033
For more information about arsignal, see arsignal.exe or arsignal.