Question
CGI
IN
Last activity: 24 Sep 2018 1:17 EDT
Service File: Execution Mode is Asynchronous execution
For Service File rule there are 2 Asynchronous processing options as below.
1. Execute Asynchronously (Queue For Execution)
2. Execute Asynchronously (Queue For Agent)
What is the different between them?
A request processor value has to be provided for both. The ProcessQueue agent from the Pega-IntSvcs Agents procecsses the items queued using Queue For Execution. Which agent will process Queue For Agent. Do we have to mention a custom agent for Queue For Agent? If yes, where it should be mentioned. Service Request processor does not have any field where agent name can be mentioned.
I have already referred below pdn link but it does not answer my questions above.
https://docs.pega.com/data-and-integration/how-asynchronous-service-processing-works
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
IT
The agent processing queued items is the ProcessServiceQueue in the in the Pega-IntSvcs ruleset.
Please check the following help page for further details:
https://community.pega.com/sites/default/files/help_v74/procomhelpmain.htm#engine/agents/eng-intsvcs-agent-con.htm
If the File Service execution mode is Queue for Agent the file service queues the request with status “Scheduled”, which means that it is processed by the node with the agent associated with the queue that wakes up first. This could be on any node running the agent in a multi node environment.
Instead if the execution mode is Queue for Execution the file service queues the request with status “Immediate” and spawns a batch requestor in a new thread on the same node to run the request. Thus, the queued item is processed straightaway.
This means that Queue for Agent is useful in a multi node environment to distribute the processing across the nodes.
This topic is addressed with greater details in the PRPC integration Specialist course available at the following link:
https://academy.pega.com/library/62-sp2/prpc-integration-specialist
Pegasystems Inc.
US
CGI
IN
Hi Jim,
Do you have any update...
Best Regards...
Pegasystems Inc.
US
Sorry for the delay. I will have an update later tonight or tomorrow AM/
CGI
IN
Hi Jim,
Do you have any update...
Best Regards...
CGI
IN
Hi Jim,
Do you have any update...
Best Regards...
CGI
IN
Hi Jim,
Do you have any update...
Best Regards...
-
Marc Bakermans Snehasis Panda
CGI
IN
Hi Jim,
Do you have any update...
Best Regards...
Accepted Solution
Pegasystems Inc.
IT
The agent processing queued items is the ProcessServiceQueue in the in the Pega-IntSvcs ruleset.
Please check the following help page for further details:
https://community.pega.com/sites/default/files/help_v74/procomhelpmain.htm#engine/agents/eng-intsvcs-agent-con.htm
If the File Service execution mode is Queue for Agent the file service queues the request with status “Scheduled”, which means that it is processed by the node with the agent associated with the queue that wakes up first. This could be on any node running the agent in a multi node environment.
Instead if the execution mode is Queue for Execution the file service queues the request with status “Immediate” and spawns a batch requestor in a new thread on the same node to run the request. Thus, the queued item is processed straightaway.
This means that Queue for Agent is useful in a multi node environment to distribute the processing across the nodes.
This topic is addressed with greater details in the PRPC integration Specialist course available at the following link:
https://academy.pega.com/library/62-sp2/prpc-integration-specialist
-
Veera Gundu
CGI
IN
Thanks...