Discussion

3
Replies
1611
Views
SGOPALAN Member since 2011 12 posts
Virtusa Corporation
Posted: 4 years ago
Last activity: 3 years ago
Closed

Calling a REST Connector rule with Queue option, requires explicit Commit

Hello All,

We have a REST Connector rule that we want to invoke asynchronously. So in the Connector rule configuration, we set under Processing options and "Intended For" as "Queuing(response will not be available)". We also created a new Request Processor that referred to "System-Queue-ExecutionRequest-Connect-Default" Queue class. This request processor was referred inside the REST Connector rule under the Processing options --> "Request Processor".

In the activity that invokes this Connector rule, we set the "Execution Mode" to "Queue".

Now the problem here is the requirement of the Commit call after the Connector rule call in the activity. If i dont have a commit, the item is not queued at all.

Is there a way by which it can be auto-committed, without the activity invoking explicit commit.

I went through the following link for setting up the Connector rule as Queued items.

https://pdn.pega.com/integration/how-to-call-web-services-using-queued-…

The above article also suggests we need to have an Explicit Commit. But again that was written for 5.5. I am using 7.1.8

The users in our system are very consious on the response time, so we made the Connect rule call as Queued.

But Adding the Commit statement breaks the Guardrail, and triggers a severe Data Integrity warning. I am not sure how i can justify this. Because i was hoping PRPC Engine would internally take care of the Commit part (once a Connector call is made as Queued) , without expecting an explicit Commit call.

Am i missing something here??

Please help

Swami

Data Integration
Moderation Team has archived post
Share this page LinkedIn