In this post we will see the requestor types in Pega. Imagine you are logging into any application. As soon as you log in, the data for that session will be stored in either memory or database. So whatever activity you do in an application, is basically like playing with data.
It can store, remove and update data.
Now let us move to Pega. As soon as you access (login) Pega, a session object is created in memory. Each session has its associated temporary memory area in that server called Clipboard.
- Clipboard is a collection of threads.
- Thread is a collection of Pages.
- Pages contain data in name value pairs.
Pega also determines which applications the user can access and build the ruleset list based on the applications. We will discuss about this in detail.
What is Requestor?
- From the name, we can say that it can be any people or object which requests for a service.
- Now imagine Pega platform and think who can be the requestor for the Pega Platform. It can be the developers, users, other applications etc.,.
- There are four requestor types in Pega.
- Browser (H)
- Batch (B)
- Application (A)
- Portal (P)
Designer studio -> System -> General -> Systems, Nodes & Requestors
You can see all requestor types repeating twice for both systems – pega & prpc.
If you see, my current system name is ‘pega’ and the other 4 requestors under ‘prpc’ are reserved for special situations.
- All Requestors accessing Pega platform must fall under a Requestor type.
- Each Requestor can be identified uniquely by Requestor ID.
How to create Requestor types in Pega?
- As soon as Pega platform is installed, 4 requestor types of system name gets created.
- In addition, 4 requestor types of system prpc is created.
No need to manually create Requestor type.
1) What is Browser Requestor type?
- Normally developers or end users access Pega platform using a browser (IE, Chrome). So as soon as we hit the Pega URL, a requestor of type ‘browser’ is created.
How Pega determines the application the Browser requestor belongs?
1. If Operator ID is available for the requestor.
Operator ID -> Access Group -> Application
2. If Operator ID is not available (at login page / Agent).
Requestor Type -> Access Group -> Application
Here we are not able to determine the Operator ID or access group from the login page.
So Pega uses the Browser requestor type to determine the Access group and application and locates the authentication rules.
- Every browser requestor starts with ‘H’ and must belong to a Pega application.
2) What is Batch Requestor Type?
- Typically internal background process (Agents) comes under Batch requestors.
How Pega determines the application the Agent requestor belongs?
Let’s start with basics. There are two types of Agent.
Note: To know about standard and advanced agent please check in my below post.
In the Agent Rule, we configure the Access group in security tab.
For Standard agent:
Standard agent completely ignores this field. It uses the access group of the Operator, which queues an entry to the Standard agent.
For Advanced agent:
a) Pega use the access group specified in the Security tab, to determine the application and locate the agent activity rule.
b) If Access group in security tab is empty, then Pega uses the access group specified in the browser requestor type to determine the application and locate the agent activity rule.
- Every batch requestor starts with ‘B’.
3) What is Application Requestor Type?
- Typically for Listeners and external application service, requests come under application requestor type.
How Pega determines the application the Application requestor belongs?
Let’s discuss about Listeners and services that external application uses.
Both the Listeners and Services are included under Service Package.
Pega use the access group specified in the Service package to determine the application and locate the service rule.
- Every App requestor starts with ‘A’.
4) What is Portal Requestor Type?
- For HTTP access as a portlet in conjunction with Service Portlet rules.
- Pega use the access group specified in the Portlet Service package to determine the application.
- Every Portal requestor starts with ‘P’.
How to debug various requestors types in Pega?
There are three ways to trace/ debug Requestors.
1. SMA (System Management Application)
We can perform various functions like trace, Clipboard analysis, performance analysis from the landing page.
Designer Studio -> System -> Operations -> SMA -> Requestor Management
Here use, SMA -> Agent Management, to determine the requestor ID for each agent rule.
The highlighted in red colour, indicates the service package the file listener belongs.
2. Remote Tracer
Using tracer -> Remote tracer, we can trace various browser sessions.
Clipboard -> System Pages -> pxRequestor
You will find all the details regarding the requestor.
Hope you are clear with the available four requestor types in Pega 🙂