1 - Admin and Security 2 - Rule Caches -Configured in the Pegarules.

xml file -These caches work to keep the performance high - System Pulse runs once a minute. It is run auto from each node, checks the pr_sys_updatescachetable and updates the node cache. This is very effective in a multi-node environment where data modficcations can be refelcted throughout all nodes. - "Rule is Dirty" between the time the update has been initiated and the update has been committed by the DB Cache. 1. Rule Cache - Auto Cleared by System - NOT to be manually clea red. Data is not stored in the system cache until called a minimum of 3 times.No t recommended to clear manually unless System puls e has an issue, cause Clearing will make the system slow and you will need take time and run all the main rules again so they are ase embled in the cache. 2. Rule Assembly Cache- Auto Cleared by System - NOT to be manua lly cleared 3. Dictionary Cache- Auto Cleared by System - NOT to be manually cleared.store class and property information. - Conclusion Cahe - Property Definition Cache 4. Static Content Cache - Can be cleared by the Developer when R ules are imported using ImportExport Servlet 5. Lookuplist Cache - Can be cleared by the Developer when Rules are imported using ImportExport Servlet Note: general, the following four events are published to the pr _sys_updatescache table: Cache (changes to the rules) DELLC (Lookup list cache changes) Index (Lucene Index) RFDEL (Rule File Deletes)

3 - Designing Applications that ensure data integrity 4 - Locking - Object locks last for 120 minutes and then does not release the lock, but updates the pr_Sys_locks table as "Expired". When another requester requests this WO then it is release from the original user and given to the new requester. - Lock Keys - Ideally takes the Obj Key or the pzInsKey - Lock Strings - Stored in the pr_Sys_Locks table with lock information - When another WO is Called through a WO (Eg: Spinoff), then in the acti vity, use the Work-AcquireWorkObject method (if pzInsKey is accessible or if pzI nskey is not accessible use Assign-AcquireWorkObejct method in the a ctivity). If calling a non-WO then can use the Obj-Open or Obj-Openby-handle

- For WO locking is enabled in the Class Group (Data-Admin-Classgroup)' - For Non-WO Classes, locking can enabled in the Class itself - Cover object ideally will get locked to one user if a Covered object i s being used. But this can be customized so several users can work in the same c over. 5 - Integrating with external systems 6 - Using Performance tools 7 - Rule Resolution and Advanced Topics

1. 2. 3. 4. 5. tree

Check the cache. If the rule is there, go to Step 8. Choose all instances with correct purpose Discard rules where Availability = No Discard inapplicable RuleSets and Versions Discard all candidates not defined on a class in the

ancestor

6. Rank remaining candidates by: Override, Class, RuleSet, Circu mstance, Circumstance Date, date/time; remove all that are withdrawn or hidden b y other withdrawn candidates - (If there is more than on e valid time range for a Rule, then the rule with the end date closest to the system date is chosen. If there are several dates where the end date is equivale nt, then the rule with the start date closest to the system date is chosen.) 6 a.Discard all choices that occur in the ranked list af ter the first default rule 7. Set the cache 8. Find best instance (and check to make sure there is not a dup licate) 9. Check that Availability does not show BLOCKED 10. Security Verify that the Requestor is authorized to see the Rule

8 - Agents - Advanced Topics - Two Logics or processing * Business Logic - what the agent is supposed to do. Each agent that is listed in the Agents rule has one task it accomplishes * Transactional Logic - the system functions which enable the bu siness logic process taking out a lock on the work object to be updated, committ ing changes to the database, etc. Done Automatically. - Agents belong to Rulesets (if required system-wide, create in the high est ruleset) - Rule resolution works differently for the agents rules, because agents are system-wide (no matter how many nodes are in the system), rather than being enabled for a particular user. Multiple Agents can be created in one Ruleset but in different Versions. Rule Resolutions finds the one from th e latest Ruleset version. - Agents belong to two main classes: - Agents rules (instances of Rule-Agent-Queue) - Agent Schedules (instances of Data-Agent-Queue) - Queue Modes

- Legacy - Transaction processing and Business Processing are in Agent Activity. Runs Agent as it Wakes up without using a Queue. - Standard - Agent Rule has only the Business login. Auto queue manager will handle the Transaction.when the agent wakes up, it immediately chec ks the agent queue to see if there are any entries for that agent. If there are, it processes the entries until either the Max Records number of entries have been processed, or the queu e is empty whichever comes first. After this processing, the agent stops and go es back to sleep for its specified interval. - Advanced - ransaction processing and Business Processing are i n Agent Activity. However, unlike the Legacy mode, the agent activity in Advance d mode may still use the agent queue functionality; it just must do so explicitly (rather than the Standard mode, where the agent queue is engaged automatically). So when the agent wakes up, it runs the activity directly, and that activity may either call the agent qu eue, or just do processing without a queue. - Queue-For-Agent Method -Agents run activities to accomplish their tasks. To provide inf ormation to the agent activities, your application must place entries into an ag ent queue so the agent knows that there is work to process.T he Queue-For-Agent method takes appropriate data from the work object or assignm ent that an agent needs to have, and stores that dat a in a queue entry for the agent. - If calling from a Flow you can directly call the Queue for Age nt Activity - If calling within an Activity you can call the Queue-For-Agent Method.

================================================================= Decelare Rule: ================ Expression - Work with Top Level and Sub level Page properties from PRPC 5.5 and above. Only Declare Rule which can work with Backward chaining. Constraints Triggers Onchange - Triggered with When rules and Booleand expressions Index - Creates a Mapping between Fields in the RDB and PRPC. This way reports c an be generated more efficiently (Eg: when the Values in a table are taken into the Clipboard, they appear as a Page l ist, but difficult to create reports based on a selected set of properties, but using Index this is easier) Page - Creates a Temporary Read only page in the Clipboard as and when a propert y used in the Page is Triggered. Declare Pages are used at Node or Thread level and are usually used for enterprise system functionalities.

Rule Types - Speacial Differences ================================= Data Admin Operator ID Data Admin Operator AccessGroup *Rule OBJ FlowAction*

Rule HTML Harness Rule HTML Section Rule HTML Fragment System Management Application (SMA) ==================================== Listener Management Requester Management System Management Build Info Sys Info Node Info Java VM Info Agent Management Administration Index Mngt Config Mngt Pulse Stat Requester pools SMA can only monitor nodes in one type of Application Server (Eg: Weblogic or We bsphere) in a multi server environment.

Parameter Passing ================= Parameters can be passed only to the below type of rules: - Process Rules - Activities - Sections Priviledges are available for: - Attachment Category - Access Role to object -