Create a Queue Processor rule to queue your items. You can use a Queue Processor rule for immediate or delayed processing, for tasks such as sending emails to users or updating the database of user logins.
In Dev Studio, click.
Add a label and a ruleset to your queue processor.
Click Create and open.
In the Associated with node type list, click a node type to associate with your queue processor.
Determine the time when you want your queue processor to run by selecting one of the following options:
In the Number of threads per node field, enter the number of threads that you want to process your items in a node.
In the Class field, specify the class of an item that you want to queue.The class that you specify must contain the activity that you want your queue processor to resolve.
In the Activity field, specify an activity that you want your queue processor to resolve.
Modify any of the following fields:
Field Field Description Max attempts The number of attempts that you want your queue processor to perform before the item is moved to the broken items queue. The default value is 3. Initial delay (in minutes) The amount of minutes for the processor to wait before retry to process an item. The default value is 1. Delay factor The factor by which the initial delay value is multiplied to calculate the period of time between successive retry attempts. The default value is 2.
In the Alerts configuration section, in the Long running queue processor threshold field, change the threshold for long running queue processor activities.An alert is saved to the log file when the activity’s execution time exceeds the threshold value. For more information, see PEGA0117 alert: Long-running queue processor activity.
- Replacing an agent with a Queue Processor rule for real-time messages
Use Queue Processor rules for better performance and greater flexibility instead of agents. Replace an existing agent with a standard Queue Processor rule to process real-time messages.
- Replacing an agent with a Queue Processor rule for delayed messages
Use Queue Processor rules for better performance and greater flexibility instead of agents. Replace an existing agent with a dedicated Queue Processor rule to process delayed messages, for tasks such as scheduling a review a week after a certain date.
- Node classification for Queue Processor rules
For better performance, use node classification for your Queue Processor rules. Decide on which nodes your Queue Processor rules run by associating node types with Queue Processor rules.
- Stream node configurations for a Queue Processor rule
A Queue Processor rule requires at least one stream node to run. Without a stream node, messages cannot be queued to or retrieved from the Kafka server.