You are here: Reference > Standard data instances > Requestor types

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

About Requestor Type data instances

When installed, Pega 7 contains four requestor types for the system name you choose during installation, plus a reserved requestor type prpc.BROWSER for special situations.

Typically, the four requestor types containing your system name are all you need. If you choose a new system name after installation, select > System > Settings > System Name to access a landing page tab that lets you change the system name.

System ID

Name

Purpose

(your system ID) APP

For listeners and for access to PRPC 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.

(your system ID) 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.

(your system ID) BROWSER

For HTTP or HTTPS access to the PRPC portal using a web browser, 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.

(your system ID) 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.

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