Page Comparison

In general, a rules manager process runs periodically (i.e. every 5 seconds) in the background on the host control system.  It is responsible for the following tasks:

• Monitor rules configuration files for changes to any rule definitions.

• Monitor each rule to determine if it is time to evaluate the criteria and, if the criteria are satisfied, perform the specified output actions.

• Write operating data to the rules configuration file so that processing of rules can continue seamlessly across any system restarts.

• Perform diagnostic tests for debugging rules on a development system.

• Log all activity to the NtRtMgr console.

A manager process is not provided with TSENTRY.  Custom implementations of a rules processing system can either use the default tpriRpsProcessor class to create a rules processor object or they can extend the tpriRpsProcessor class to customize the rules processor object.  All that is required then within the manager process is to create and initialize the tpriRpsProcessor or tpriRpsProcessor‑derived object and then periodically call the ProcessRules() member function to perform rules processing.