Back Forward About Service Request Processor data instances

New Queuing Options Dequeuing Options History

Purpose

Proj-318 5.4 When an EJB, HTTP, Java, JMS, MQ, or SOAP service rule is configured to process service requests asynchronously, or is configured to requeue failed service requests for a later execution attempt, service request information is stored as a persistent object in a request queue in the PegaRULES database. Use service request processor instances to specify:

Specify which request processor a service is to use on the Service tab for an EJB, HTTP, Java, JMS, MQ, or SOAP service rule. The first key to the request processor instance is the name of a service package. The Request Processor field in the service rule lists only those request processors that have the same service package name as the service rule. The Pega-IntSvcs agent monitors the queue and processes queued items.

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 Pega-IntSvcs 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. ABLAL

For more information, see these PDNPega Developer Network articles:

Access

noteCreate the Service Package data instance before creating any service rules with that package name.

To review service request processors:

Category

The Data-Admin-RequestProcessor-Service class contains service request processor data instances. This class is part of the Integration Resources category.

Integration-Resources category
Help System home pageHelp Home