This documentation supports the 22.1 version of BMC Helix Innovation Studio.To view an earlier version, select the version from the Product version menu.

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.

Important

Only the rules with Trigger Type as Timer Event are displayed in the Rule pool management UI.

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

  1. Log in to BMC Helix Innovation Studio and navigate to the Administration tab.
  2. Select Server settings > Rule pool management.

The Rule pool management UI is displayed.
Rule pool management UI.png

Rule pool management interface details

The following image describes the Rule pool management interface:

Rule pool management interface overview.png

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: 

  • Escalation icon.png—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.
  • 221_No conflicts.png—Indicates that no conflicts were identified for this rule.
  • 221_Conflicts for rules.png—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.
    For example, if rule 1 shows a conflict because of rule 4, the 221_Conflicts for rules.pngicon is displayed for both the rules.

Important: The 221_No conflicts.pngand 221_Conflicts for rules.png icons are displayed only for the rules in BMC Helix Innovation Studio and not for the escalations defined in Action Request System.

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: Access rule in design mode.png.

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:

  • BMC Helix Innovation Studio system rules
  • Rules defined in out-of-the-box applications or libraries
  • Escalations created in Action Request System

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.

To reassign the rule

  1. Log in to BMC Helix Innovation Studio and navigate to the Administration tab.
  2. Select Server settings > Rule pool management.
  3. On the Rule pool management UI, from the Available pools list, select the pool, and click on the rule assigned in the pool.
  4. From the Assigned pool field, click Reassign.
  5. On the Reassign rule dialog box, from the Assign to list, select the pool to which you want to reassign the rule.
    Assign to.png
  6. Click Save.

The rule is reassigned to the new pool. 

Related topics

Creating-rules

Defining a trigger for a rule

Creating escalations

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*