1. Cloud Native System Administrator's Guide
  2. Configuring the Task Processor

5 Configuring the Task Processor

This chapter describes how to configure the task processor to improve performance and handle rule-processing errors for Oracle Communications Order and Service Management (OSM).

In most cases, you can use the default configuration for the task processor.

About Configuring the Task Processor

The task processor evaluates rules, event delays, and timer delays to determine when to transition to the next task in a process. The task processor is implemented as one or more task processor threads running on WebLogic servers. There are two types of task processors: the rule task processor evaluates orders at rules and the delay task processor evaluates orders at delays. You can configure additional task processors to improve performance.

Configuring the Task Processor for Performance

You can use the oms-config parameters to tune the number and type of task processors.

There are two types of task processors:

  • Rule Task Processor, which evaluates only rules.

  • Delay Task Processor, which evaluates only delays.

You may want to reconfigure the number or type of task processors as the amount of data you handle grows.

For rule task processors, the following parameters apply:

  • oracle.communications.ordermanagement.RuleDelayTaskPoller.MaxRuleTaskProcessors. Specifies the maximum number of rule task processors; minimum value 1; maximum 50; default value is 1.

  • oracle.communications.ordermanagement.RuleDelayTaskPoller.Interval. Specifies the pause time in milliseconds between two invocations of the rule and delay task processors; minimum value 1000; maximum value 60000; default value is 5000.

For delay task processors, the following parameters apply:

  • oracle.communications.ordermanagement.RuleDelayTaskPoller.MaxDelayTaskProcessors. Specifies the maximum number of delay task processors; minimum value 0; maximum 50; default value is 1.

  • oracle.communications.ordermanagement.RuleDelayTaskPoller.Interval. Specifies the pause time in milliseconds between two invocations of the rule and delay task processors; minimum value 1000; maximum value 60000; default value is 5000.

There must be at least one rule task processor running. The number of delay task processors can be 0 or above.

If there is a backlog of rule or delay tasks, you can increase the number of rule or delay task processors.

OSM will adjust the number of rule and delay task processors to use no more than 10% of the connection pool size that is configured for the WebLogic instance. The adjusted numbers are written in the managed server's log file. If the adjusted number of rule and delay task processors does not meet your performance requirement, increase the connection pool size or decrease the parameter oracle.communications.ordermanagement.RuleDelayTaskPoller.Interval.