The rules, transactions, and other data supporting a Process Commander system are stored in one or more Oracle, IBM DB2 or Microsoft SQL Server databases. (Consult the Platform Support Guide for an exact current list of supported vendors and products.)

The database that contains the rules — all the instances of concrete classes derived from the Rule- base class — is known as the PegaRULES database. This database is also sometimes identified as the rulebase, but it contains more than rules.

Classes that are mapped to the PegaRULES database are known as internal classes. Concrete classes that correspond to rows of an external database are known as external classes.

In contrast to the persistent instances of rules and other objects in the PegaRULES database, instances on a user clipboard are temporary. When a user logs off, the system deletes the user's clipboard.

If the system saves an instance from the clipboard into the PegaRULES database, the saved copy remains after the user who created it logs off, and is available to other users. Thus, the PegaRULES database contains the persistent objects of Process Commander.

Through the database table and database data instances, Process Commander developers working with database administrators determine which classes of objects are stored into which database tables.

Although the PegaRULES database is sometimes called a rulebase, don't confuse the word rulebase — a physical collection of rules and other objects in a relational database — with the Rule- base class, an abstract class that has no instances.

	base class, external class, internal class, platform, prconfig.xml file, reports database, Rule- base class, schema
	About Database data instances About Database Table data instances How to detect lengthy PegaRULES database operations Working with the PegaRULES database How to limit connections to the PegaRULES database How to detect long database connection waits
	Atlas — Initial database tables

Definitions — P