Question

4
Replies
1050
Views
MarianeA Member since 2016 72 posts
Murex
Posted: February 3, 2017
Last activity: February 6, 2017
Closed

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:

  • 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

***Moderator Edit: Vidyaranjan | Updated Categories***
Data Integration
Moderation Team has archived post
Share this page LinkedIn