Back Forward Atlas — Initial Requestor types (Data-Admin-Requestor)

 About Requestor Type data instances

When installed, Process Commander contains four requestor types for the system name pega, plus a reserved requestor type prpc.BROWSER for special situations.

Typically, the four pega requestor types are all you need. If you choose a new system name, copy these four requestor types using Save As to create four requestor types for the new system name. See How to change the system name.

System ID

Name

Purpose
pega APP

For listeners and for access to Process Commander from an external client system, such as through a service request (other than JSR-168 requests using Rule-Service-Portlet rules). Requestor sessions using this requestor type instance have requestor IDs that start with the letter A.
pega BATCH

Background processing, such as performed by, listeners, services, agents, and daemons. Requestor sessions using this instance have a requestor ID that starts with the letter B. As initially installed, all BATCH requestors have access to the PRPC:Agents access group.
pega BROWSER

For HTTP or HTTPS access to the Process Commander portal using Microsoft's Internet Explorer Web browser on a Windows workstation, or from a browser presenting a Pega Composite Application. Requestor sessions using this instance have a requestor ID that starts with the letter H.

As initially installed, all BROWSER requestors have access to the PRPC:Unauthenticated access group.
pega PORTAL

For HTTP access as a portlet in conjunction with Service Portlet rules. Requestor sessions using this instance have a requestor ID that starts with the letter P. C-765 R-10659 R-10631
prpc BROWSER

Reserved for special situations. Do not use except as advised by Global Customer Support.

Up About Requestor data instances
Up Atlas — Initial Data Instances