Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 RamK Sharma (RamKS157)
Morgan Stanley

Morgan Stanley
US
RamKS157 Member since 2018 35 posts
Morgan Stanley
Posted: Mar 14, 2019
Last activity: Mar 15, 2019
Posted: 14 Mar 2019 22:58 EDT
Last activity: 15 Mar 2019 1:40 EDT
Closed

Connect rest service asynchronously

I have requirement to send service request and do not wait for response. I tried run RunInParallell but it requires connect-wait to be used to wait parent requestor till child requestor finishes. Is there any way to not wait for child requestor with RunInParallel connector?

To see attachments, please log in.
Pega Platform
Low-Code App Development
Data Integration

Posted: 5 years ago
Posted: 14 Mar 2019 23:25 EDT
RamK Sharma (RamKS157)
Morgan Stanley

Morgan Stanley
US

On putting 0 in connect-wait method gives the following error -

2019-03-14 23:19:16,458 [BTHREAD0, eon_id=932] [TABTHREAD0] [                    ] [        DMT:01.01.01] (      internal.mgmt.Executable) ERROR crvpegadev1-frm.webfarm-dev.ms.com| Proprietary information hidden ramshar - Exception
com.pega.pegarules.pub.PRRuntimeException: Couldn't queue batch activity for invoking Rule-Connect-REST in parallel; make sure you use the Connect-Wait method along with 'run in parallel'.

 

To see attachments, please log in.
Posted: 5 years ago
Posted: 15 Mar 2019 1:40 EDT
Subramanyam Kopparam (SUBRAMANYAM-1)
PEGA
Cloud Development Architect, PDC
Pegasystems Inc.
IN

In Connect REST Under Service tab Choose the queuing in Processing Options.

 

Processing options
You can allow connector requests from this Connect REST to be processed asynchronously in parallel with the calling activity, or in background by an agent. (The mode of execution of each connector request is determined by the Execution mode parameter of the Connect REST method, as enabled by the values in these two fields.)
 
Intended for Optional. Select:
immediate execution — the REST connector executes synchronously; the calling activity waits for results.
queuing (response will not be available) — the REST connector executes asynchronously, with calls placed in a queue. The calling activity continues without waiting for results.
Queuing, when selected, occurs only if also specified in the Connect REST method.
 
Request processor Optional. If you selected queuing for the Intended for field, identify here a Connect Request Processor data instance that defines the classes and other characteristics of the queued connector requests, and for which the RuleSet key part matches the RuleSet of this Connect REST rule.
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice