The following agents in the Pega-IntSvcs ruleset process queued service and connector requests.
Service requests of any of seven service types can process service requests asynchronously. When configured to do so, EJB, HTTP, Java, JMS, MQ, SOAP and File services use the Queue Manager infrastructure to store service requests as persistent objects in the PegaRULES database.
The class, queuing and dequeueing options for the service request are determined by a Service Request Processor data instances. See About Service Request Processor data instances.
The first execution of an asynchronous service request occurs in the service requestor, but in a separate background Thread that executes after, rather than before, the service response is set. Queuing and the ProcessServiceQueue agent are used for the second and subsequent retries, if configured. Queuing also occurs when configured through a Queue When condition on the Fault tab or Response tab of the service rule.
The ProcessServiceQueue agent is disabled by default. To enable it, select the Enabled? option for it on the Schedule tab of the agent schedule instances (Data-Agent-Queue class).
When the ProcessServiceQueue agent executes a queued service request, the execution is performed with the authorization profile of the service/listener.
For more information, see PDN article How asynchronous service processing works.
SOAP and HTTP connector requests can be processed asynchronously. The class, queuing and dequeueing options for the service request are determined by a Connect Request Processor data instances. See About Connect Request Processor data instances and More about SOAP connector rules.
The ProcessConnectQueue agent is disabled by default. To enable it, select the Enabled? option for it on the Schedule tab of the agent schedule instances (Data-Agent-Queue class).
When the ProcessConnectQueue agent executes a queued connector request, the execution is performed with the authorization profile of the service/listener.