*Standard agents can be configured to run on multiple nodes where as advanced agent we generally configure on a single node. Open the tracer, click on remote trace, in the drop down choose above requestor and click ok.įor the next agent run we can see the tracing the remote tracer. Now get the Requestor name of this agent. Goto Requestor Management –> Search with Agent name and see for a requestor with description, Waiting upto 60 seconds… Login to SMA –> Agent Management –> Agents –> Select Agent which we want to trace –> click on Delay –> Now the agent will be delayed for 60 seconds. When the standard agent wake it will execute the agent activity ‘N’ number of times(with status=scheduled) where ‘N’ is the number of Queue Items in the PR_SYS_QUEUS table.Ī queue is associated with the below status values.ġ) Scheduled :- This is initial status when a queue is been inserted into the table and which gets process by agent during next run.Ģ) Now-Processing :- This means that the Queue is picked by agent and is being processed.ģ) Broken-Queue:- When Queue items fails in its processing, the status will be updated to Broken-Queue. Queue Items can be put into agent queue table PR_SYS_QUEUES by using the method/activity Queue-For-Agent/QueueForAgent. When the Queue Items are there, standard agent will execute agent activity else it will not execute activity thus goto sleep. Modes Of Agent : – There are 3 different modes available.ġ) Legacy : – This mode is been deprecated from PRPC version 5.4.Ī) When an advanced wakes up at schedule time it will directly executes agent activity without bothering about Agent Queue Items.ī) Usually we will create advanced without applying AQM (Auto Queue Management) and these agents will be configured to run on Single Node.Ĭ) In an advanced Agent Work Object locking and Transactional Commit must be taken care by our self.ģ) Standard Agent :- Standard Agent will be applied with AQM.ĪQM (Auto Queue Management) :- This program is responsible for instructing the agent weather to execute associated agent activity or not. PRPC has a predefined master agent ‘System Pulse’, which wakes up all the user created agents at their schedule time.Īgent is an instance of Rule-Agent-Queue whereas agent Schedule is an instance of Data-Agent-Queue.

When an agent wakeup, it will run on the associated access Group. Schedule 2) Activity 3) Access Group 4) Mode.Īgents wakes up at the schedule time and executes its Associated activity.

Agent is internal background process or requestor, which gets associated with

Auto queue management pega