Table of Contents

Managing system resources


Only available versions of this content are shown in the dropdown

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 job schedulers

    Job schedulers are internal background processes on the server that run activities on a periodic basis. Use the Jobs landing page to manage job schedulers in your application.

  • Managing queue processors

    Use the Admin Studio, Queue processor page to review information about queue processors in your system.

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

    Use Admin Studio to manage agents to debug and trace any problems with agent activity. You can also start, stop, restart, or trace agents.

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

  • Creating a content security policy

    Create a content security rule so that browsers load resources only from authorized web sites.

  • 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 Collaboration Center to ask questions, engage in discussions, share ideas, and help others.