Back Forward More about Library rules

About Library rules

Library generation

The system saves compiled CLASS files for library functions as disk files in each node. Use one of these procedures to compile one or more libraries. Some affect only your current node; others force eventual recompilation on all nodes of cluster.

<env name="Initialization/extractLibraries" value="true" />

NoteYour current RuleSet list is not relevant when you generate a library. The system compiles all versions of each function in the library. At runtime, users execute a version appropriate to their own RuleSet list.

Deleting a library

When you delete a library rule with the Delete (Delete) toolbar button, the system also deletes all function rules in the library (of all RuleSet Versions for the RuleSet ), and the assembled and Java-compiled functions in the library. In a multinode cluster, if you delete a library rule, the system pulse processing performed by the Pega-RULES agent on other nodes deletes the library and functions.

Overriding a standard function

To override a standard function:

  1. Create a library in your application RuleSet with the same name as the standard library that contains the function.
  2. Use Save As to copy the standard function into your library, retaining the function name.
  3. Update the function Java code as desired, being careful to consider the effect of your changes on existing calls to the function.

CautionDo not reference or override any function or library in the Pega-WB RuleSet; they are reserved. The names and capabilities of these functions are subject to change.

Regenerating one or all libraries

You can extract and compile libraries through any of several facilities:

No check out, always available

zzzChange library rules with care, noting these restrictions:

Related topics About the System Management application
About Function rules

zzzAbout Library rules