About Service Request Processor data instances
About  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:

• 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 PDN articles:

• 25029 How asynchronous service processing works
• 25030 How to configure a service that processes requests asynchronously
• 25031 How to configure a service that queues failed service requests for another attempt

Access

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

Select > Integration > Resources and select the Service Request Processor link to access the Service Request Processors in your system. Or, you can use the Records Explorer to review or create 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.

Associated RuleSet

When you save a service request processor data instance, the system automatically associates it with a RuleSet of the Application rule for the current application. This association assists with application packaging. You can update the associated RuleSet using the field in the upper right corner of the form. See Identifying parts of rule and data forms.

If there is no RuleSet associated with the data instance (for example, for existing instances not previously associated with a RuleSet), the Associated RuleSet displays [none].

Integration-Resources category
Help Home