Pulse

The Pega-RULES agent performs periodic processing known as a system pulse. This processing synchronizes the contents of the in-memory rule cache on that node with rules stored in the PegaRULES database. The pulse helps each node coordinate processing and synchronize operations, including the contents of the rule cache.

In a multinode clustered system, a rule updated by a user on node North is retained in the rule cache on node North, and also committed to the PegaRULES database. For a brief interval, users at another node in the cluster — for example South — may have a stale copy of that rule in the rule cache on the South server node. When pulse processing for South completes, the South rule cache has the current rule.

Between pulses, updated rules are noted in the pr_sys_updatescache table, corresponding to the System-Updates-Cache class. To see a list of updates not yet posted by pulse processing, review the standard report System-Updates-Cache.InstanceList.All. The Type column indicates the action: CACHE for rule changes, DELLC for deleted lookup list, and so on. BUG-3797 R-18759

Background processing to support the full-text search facilities also occurs during pulse processing. Similarly, library recompilation requested on one node is propagated and repeated on other nodes by pulse processing. PROJ-338

The Agent Schedule data instance named Pega-RULES.<node> defines the pulse interval. B-19353 not Data-Admin-System The default interval is 60 seconds. B-20293

In the System Management application, select Administration > Pulse Status to see the date and time of the most recent pulse on each node. CLINIC 11/7/05

	agent, node, rule cache
	About Agent Schedule data instances Understanding the Pega-RULES agent Understanding the full-text search facility

Definitions