Every system requires ongoing administration, housekeeping, and management. Pega Platform provides extensive facilities for managing the system and managing system-wide data.

• Managing system resources

  Admin Studio is a workspace for system administrators, database administrators, and security administrators which provides runtime information and configuration options for system resources. On-premises clients can use the Admin Studio System settings page to verify the system settings for a node or cluster, to diagnose configuration issues across the cluster, and to download the prconfig.xml configuration file. For clients on client-managed environments, this page shows you the nodes that you have defined in your Kubernetes deployment

• Managing background processing resources

  Meet highly challenging background processing requirements by creating job scheduler rules to run scheduled tasks and queue processor rules for asynchronous processing.

• Monitoring the health of your system

  Pega Platform provides a variety of tools to help you monitor the health of your system. It is important to monitor the system logs to be alerted of possible problems. For ways to identify and resolve system issues, refer to the topics listed below.

• Preassembling rules in an application

  The Static Assembler utility enables the preassembly and caching of rules that belong to an application. These actions improve the response time for interactive users after a system startup or when new ruleset versions are imported into the system.

• Managing your Pega Platform database

  The Pega Platform relational database holds the rules, data instances, work items, history, and other concrete objects from the internal classes of your Pega Platform system. External classes, by definition, correspond to tables in other databases and are not part of the Pega Platform database.

• Managing your high availability cluster

  You can manage your high availability cluster using the HA Cluster Management page or in a Network Operations Center (NOC) integrated with the Pega API.

• Moving applications between systems

  You can migrate rules and data between instances of Pega Platform by using interactive tools in Dev Studio or by using command-line tools. You can develop rules on one system and deploy them on other systems. As a best practice, use Deployment Manager to promote applications.

• Understanding Requestor Type data instances

  Users and external systems connect to Pega Platform using one of four requestor types. Requestor type data instances define the types of requestors that can access your system, such as a browser session, an external application, or an internal background process.