1.

Explain Requestor Type in Pega. What are the different types of Requestor types in Pega?

Answer»

A Data-Admin-Requestor instance defines a requestor type. The BROWSER requestor type, for example, indicates CHARACTERISTICS of INTERACTIVE user connections, such as guest connections, utilizing INTERNET Explorer or another web browser. Agents employ the BATCH requestor type for background processing.

Pega Platform comes with four requestor types for the system name we specify during installation, as well as a reserved requestor type prpc.BROWSER for exceptional cases. Typically, we only require the four requestor types that contain your system name. If we want to modify the system name after installation, we go to Designer Studio => System => Settings => System Name to get to a landing page tab where we can do so. When we change a system's name, NEW requestor instances are created that correspond to the previous name's instances. If the prior system name did not include all requestor types for some reason, the missing requestors are also produced when the system is renamed.

Following are the different requestor types in Pega:

  • Application:This is used by listeners and external client systems to access the Pega Platform, such as through a service request (other than JSR-168 requests using Rule-Service-Portlet rules). Requestor IDs that begin with the letter A are used in requestor sessions that use this requestor type instance.
  • Batch: This is used by listeners, services, agents, and daemons all executing background processing. The requestor ID for requestor sessions using this instance begins with the letter B. All BATCH requestors have access to the PRPC:Agents access group when it is first IMPLEMENTED. If you make a change to Data-Admin-Requestor.BATCH so that it no longer has access to the PRPC:Agents access group and subsequently upgrades the Pega Platform, the system may fail to start.
  • Browser: This is used for accessing the Pega Platform portal via a web browser via HTTP or HTTPS, or from a browser displaying a Pega composite application. The requestor ID for requestor sessions utilising this instance begins with the letter H. All BROWSER requestors have access to the PRPC:Unauthenticated access group when it is first implemented.
  • Portal: This is used in conjunction with Service Portlet rules, for HTTP access as a portlet. The requestor ID for requestor sessions utilising this instance begins with the letter P.


Discussion

No Comment Found