Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Managing system resources

Updated on April 5, 2022

Admin Studio is a workspace for system administrators, database administrators, and security administrators which provides runtime information and configuration options for system resources.

  • 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.

  • Reviewing requestor pool information

    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.

  • Pega 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.

  • Deployment behind a reverse proxy

    To deploy Pega Platform™ behind an HTTP proxy server, use XF-* extension headers. Deploying in this manner does not require any additional configuration of Pega Platform.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us