Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Service Request Processor data instances

Updated on November 23, 2022

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.

The following tabs are available on this form: Use service request processor instances to specify:
  • How to handle the queued service request objects
  • Which queue to use
  • How many times to run the requests if they fail the first time
  • Whether to store the request object with the results of the processing after the processing is finished.
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.

For more information, see these Pega Community articles:

  • How asynchronous service processing works
  • Configure a service to process requests asynchronously
  • Configure a service to queue a failed service requests for another attempt


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

In Dev Studio, in the navigation panel, click RecordsIntegration-ResourcesService Request Processor to access the Service Request Processors in your system.


The Data-Admin-RequestProcessor-Service class contains service request processor data instances. This class is part of the Integration Resources category.
  • Previous topic MQ Server form - Completing the Environment tab
  • Next topic Service Request Processor - Completing the New or Save As form

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us