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 configuration; for clients in Pega Cloud Services environments, the nodes are
defined by Pega Cloud Services. For either type of cloud deployment, these settings cannot
be modified using Admin Studio.
- Viewing general system settings
Access the General landing page from Dev Studio by clicking Configure System General .
- Managing requestors
Monitor and debug requestor activity from the Requestors page in Admin Studio. The Requestors page displays summary information about Application, Browser, Batch, and Portal requestor types and lists all the active requestors in a specific cluster or node.
- Managing listeners
Use Admin Studio to manage listeners to debug and trace any problems with listener activity. You can view lists of available listeners. and associated nodes. You can also start, stop, restart, and trace listeners.
- Managing requestor pools
Requestor pools are sets of requestors that are dedicated to processing incoming service requests from a specific service package. Use Admin Studio, to manage requestor pools to tune the requestor pool configuration and efficiently manage the resources to improve the performance of services.
- Managing log categories
From Admin Studio, you can select which log messages to write to your log files by associating log levels with your categories.
- Integrating with APIs and services
You can use the Pega APIs to power client and mobile apps by using built-in Pega REST/JSON services. Pega APIs provide an extensive set of APIs to manage and interact with all aspects of your application, such as cases, assignments, and so on. The APIs are secured by user credentials and TLS/SSL. You must switch from App Studio to Dev Studio to configure security for the Pega API, which is the api service package.
- Specifying system-wide security parameters by using system data instances
Specify system-wide parameters, for example, the production level, to apply to all nodes in the system.
- Understanding temporary installation and browsing files
Temporary files are created in temporary files directories on the Pega Platform server to temporarily contain information that is required during installation or browsing.