Customize the Queued execution for Connect-REST
Hello,
We would like to customize the error handling of the Connect-REST (determine the client/server error, send email notification on failure, retry mechanism, etc..)
Previously when calling the Connect-REST method we were setting the execution mode to Queue. The Connect-REST's Request Processor had as Queuing option the Queue Class "System-Queue-ExecutionRequest-Connect-Default".
In order to customize our error handling, we did the following:
Hello,
We would like to customize the error handling of the Connect-REST (determine the client/server error, send email notification on failure, retry mechanism, etc..)
Previously when calling the Connect-REST method we were setting the execution mode to Queue. The Connect-REST's Request Processor had as Queuing option the Queue Class "System-Queue-ExecutionRequest-Connect-Default".
In order to customize our error handling, we did the following:
- Created a Queue under Class System-Queue-ExecutionRequest-Connect- (Create a new Class System-Queue-ExecutionRequest-Connect-MX)
- Created a Connect Request Processor (queue class name: System-Queue-ExecutionRequest-Connect-MX)
- Edited the Connect rule (to reference above Request processor)
- Edited the activity that calls the Connect-REST method: execution mode of the Connext-REST method is 'queue'
- Added an Agent "ProcessMXConnector" (Standard) whose agent activity's class is System-Queue-ExecutionRequest-Connect-MX which does the following:
- Opens by handle the System-Queue-ExecutionRequest-Connect-MX Object through the pyItemId retrived from the Primary Page
- Retrieves and saves the page of Connect-REST Request
- Calls the Connect-Rest giving it the corresponding page (execution mode is Run)
- Based on response, do some functional processing based on the response
The problem is :
- we cannot trace the Agent "ProcessMXConnector" although it is visible in the Agent Management.
- the pyAttempts remains to 0 for all the queue items under the CL System-Queue-ExecutionRequest-Connect-MX (Request Processor attempts set to 10 and configured to keep in queue on save and fail)
- Agent Name of the item in the Queue is null
I would like to make sure if there are any missing configurations? Any missing security configuration preventing the Agent's activity to be ran?
Is it because the Agent name is not specified (I would have assumed the Agent name will be automatically picked up)? If yes, how to set it ?
How to proceed and make sure the Connect Request Processor is indeed calling the Agent "ProcessMXConnector" 's activity?
(PS I added a similar post on the documentation found under https://pdn.pega.com/how-call-web-services-using-queued-execution-v55#comment-442966)
Any help will be greatly appreciated :)
Thank you,
Mariane
Pegasystems Inc.
IN
Hi
Are you getting any relevant error in the log file ? If there is some issue related to agent activity and the agent fails to run it , it logs an entry in the PegaRule log file indicating the error types. So when you are saying that you are not able to trace it , checking the log file will give you some idea about the issue.
Murex
LB
Hello Santanu,
Thank you for your reply, it is most appreciated :)
I checked the log file and there is not any relevant error concerning the issue.
I was able to locate the problem though: The item is indeed queued in the Queue (that I created, CL System-Queue-ExecutionRequest-Connect-MX) however I am not able to specify the Agent Name of the queued item (OOTB property pyAgentName is empty)
I tried to manually set the property pyAgentName of the request but the property got saved under pyOtherPages as if the OOTB "pyAgentName" property is part of the request.
I am attaching the item queued in the CL System-Queue-ExecutionRequest-Connect-MX for your convenience.
Hello Santanu,
Thank you for your reply, it is most appreciated :)
I checked the log file and there is not any relevant error concerning the issue.
I was able to locate the problem though: The item is indeed queued in the Queue (that I created, CL System-Queue-ExecutionRequest-Connect-MX) however I am not able to specify the Agent Name of the queued item (OOTB property pyAgentName is empty)
I tried to manually set the property pyAgentName of the request but the property got saved under pyOtherPages as if the OOTB "pyAgentName" property is part of the request.
I am attaching the item queued in the CL System-Queue-ExecutionRequest-Connect-MX for your convenience.
I think if we figure out how to set the Agent Name of the request queued then our problem will be solved because the agent is indeed running periodically but it seems that it does not know it has items to process
Many Thanks,
Mariane
MDCloud
CY
Hi Mariane,
Do you have AQM enabled for your agent?
Following step seems redundant since Standard agent retrieves item from the queue automatically and agent activity is executed on the saved page:
- Opens by handle the System-Queue-ExecutionRequest-Connect-MX Object through the pyItemId retrived from the Primary Page
Murex
LB
Hello Lapso,
Thank you for your reply, it is most appreciated :)
Yes I have AQM enabled for my agent.
I would like to add one note (not sure if it helps): the queued item is saved under the Class System-Queue-ExecutionRequest-Connect-MX and not under the Class System-Queue-DefaultEntry (which usually stores the items of the Standard Agents)
Many Thanks,
Mariane