Assigning rules to a pool for load distribution
A rule uses a Trigger element that defines the conditions under which a rule is initiated. For example, a rule might run when a request more than eight hours old has not been closed by support personnel.
Depending on the frequency of execution and the type of activity triggered, rules may consume significant resources in the system. To reduce the load on the system, administrators can distribute the rules among pools and assign the rules to a specific pool. Depending on the frequency of execution and the type of activity triggered, rules may consume significant resources in the system
The Rule pool management interface provides an insight into how all rules are scheduled in a pool. Administrators use these statistics to schedule new rules in the pool, as well as move the existing rules to a pool where they are less likely to conflict with other rule’s execution.
Before you begin
Make sure you have defined the available pools and the pool number when you define the trigger for your rule in the Rule designer. For more information, see Defining-a-trigger-for-a-rule.
To access the Rule pool management interface
- Log in to BMC Helix Innovation Studio and navigate to the Administration tab.
- Select Server settings > Rule pool management.
The Rule pool management UI is displayed.
Rule pool management interface details
The following image describes the Rule pool management interface:
The following table describes the fields in the Rule pool management interface:
Annotation | Field | Description |
|---|---|---|
1 | Available pools | Displays the list of all the available pools. |
2 | Pool list | Displays the available pools, rules, and escalations assigned in the pool. The following icons provide additional details about the rules and escalations in the list:
Important: The |
3 | Rule name | Displays the name of the rule or escalation. For custom rules, you can view the link to open the rule in design mode. For example: |
4 | Interval/Schedule | Displays the timer type you have selected to trigger the rule. |
5 | Execution count | Indicates the number of times the rule or escalation was triggered. |
6 | Average latency (sec) | Displays the average time delay (in seconds) while triggering a rule. |
7 | Average execution time (sec) | Displays the average runtime (in seconds) a rule requires to complete execution. |
8 | Assigned pool | Displays the pool number assigned for the rule or escalation. You can define the assigned pool when you create or modify the rule or escalation. For more information, see Defining-a-trigger-for-a-rule.Important: While creating or modifying a rule or an escalation, the pool number should be between 1 and the number of available pools. If the pool number is blank or outside the valid range, the rule or the escalation is assigned to pool number 1. For example, if the number of the available pool is 5 and assign the rule or the escalation to pool 7, the rule or escalation is assigned to pool number 1. You can configure the number of available pools by configuring the Private-RPC-Socket setting from the Centralized Configuration form. For more information, see Configuration settings N-R. Or you can define the maximum threads for Escalation queue from the Ports and Queues tab in the Server Information form. For more information, see Setting ports and RPC numbers. |
9 | Reassign | Enables you to reassign the rule to a different pool. For more information, see To reassign the rule. Important: You can reassign only the custom rules. You cannot reassign a read-only rule to a different pool. The read-only rules include:
|
10 | Last start date | Displays the date when the rule was last triggered. |
11 | Last end date | Displays the date when the rule was last completed. If the rule is still running the Last end date field will be empty. |
12 | Conflicts | Displays the list of all the rules with conflicts and the list of rules that creates the conflicts. The table displays the name of the rule and its average latency time. |
—Indicates that this is an escalation defined in Action Request System. The details for the escalations are read-only. You cannot update or reassign any escalations.
—Indicates that no conflicts were identified for this rule.
—Indicates that conflicts were identified for this rule. This icon is displayed for the rules with conflicts and for the rules that create the conflicts.
icons are displayed only for the rules in BMC Helix Innovation Studio and not for the escalations defined in Action Request System.
.To reassign the rule
- Log in to BMC Helix Innovation Studio and navigate to the Administration tab.
- Select Server settings > Rule pool management.
- On the Rule pool management UI, from the Available pools list, select the pool, and click on the rule assigned in the pool.
- From the Assigned pool field, click Reassign.
- On the Reassign rule dialog box, from the Assign to list, select the pool to which you want to reassign the rule.
- Click Save.
The rule is reassigned to the new pool.
Related topics