SRS Rules - Broadcasts
(Doc ID 1296513.1)
Last updated on DECEMBER 23, 2024
Applies to:
Oracle Network Management for Utilities - DMS - Version 1.12.0.3 and laterOracle Utilities Network Management System - Version 1.12.0.3 and later
Information in this document applies to any platform.
Purpose
Broadcast Related Rules
NOTE: This page is applicable to NMS versions 2.3.0.0 and newer.
For previous releases, refer to the documentation in the Configuration Assistant.
For previous releases, refer to the documentation in the Configuration Assistant.
The purpose of this page is to describe JMService rules that can be configured. For each rule, there are the following values to specify:
- set_name
- A name used to identify what set a rule should belong to. This value, along with the rule_name value, comprise the primary key for the srs_rules table. If not using the defaultRuleSet rule, then you should have at least one set of rules called "normal", as that is what set JMService will attempt to use in that case.
If a set_name value is specified in a rule description, then no deviation should be made from that name in the configuration. If a set_name is not specified, or a * is listed, specify this rule as needed for each rule set that can be changed in the Authority tool. - rule_num
- An integer value, used in conjunction with set_name to comprise the primary key for the srs_rules table.
- rule_active
- This should be set to either 1 or 0. A value of 1 would indicate that the rule is actively in use in the rule set. Specifying a value of 0 is a way to deactivate a rule in a set without having to remove it from the population script.
- incident_type
- See each individual rule description for valid value for this column.
- rule_name
- A character string. The name of the rule itself.
- rule_value_1
- A character string. See each individual rule description for valid and default values, if applicable.
- rule_value_2
- An integer value. See each individual rule description for valid and default values, if applicable.
- ncg_cls
- Used in conjunction with the ncg_idx value to narrow the application of a rule to a specific control zone, if desired. Only a small subset of the rules are eligible to use these values -- see the individual rule descriptions. A value of 0 should be specified if a) ncg_cls and ncg_idx do not apply to a rule or b) it is desired to have the rule values apply to all control zones.
- ncg_idx
- Used in conjunction with the ncg_cls value to narrow the application of a rule to a specific control zone, if desired. Only a small subset of the rules are eligible to use these values -- see the individual rule descriptions. A value of 0 should be specified if a) ncg_cls and ncg_idx do not apply to a rule or b) it is desired to have the rule values apply to all control zones.
- zone
- Name of the control zone, derived from the combination of ncg_cls and ncg_idx.
- rule_value_integer_1
- An integer value. See each individual rule description for valid and default values, if applicable.
- rule_value_integer_2
- An integer value. See each individual rule description for valid and default values, if applicable.
- rule_value_integer_3
- An integer value. See each individual rule description for valid and default values, if applicable.
- rule_value_integer_4
- An integer value. See each individual rule description for valid and default values, if applicable.
- rule_value_integer_5
- An integer value. See each individual rule description for valid and default values, if applicable.
Class-based rules
There are a number of rules (such as commonStopClass and openGroupThreshold) which can be specified for multiple device classes. rule_value_1 for these rules can either be the name of a device class or a special class combination using + to specify a class and all its descendants and - to omit a class.
Examples:
- class1
- Specifies class1
- class1+
- Specifies class1 and all its descendants
- class1+,-class1
- Specifies all the descendants of class1 but not class1 itself
- class1,class2
- Specifies class1 and class2. Identical to configuring two instances of the rule (one for class1 and one for class2).
- class1+,-class2
- Specifies class1 and all its descendants except class2
- class1+,-class2+
- Specifies class1 and all its descendants except class2 and class2's descendants
Broadcast Related Rules By Function
-
Broadcast related rules
These rules control how calls and jobs get broadcast, including which calls appear in the viewer.
Scope
This document is intended for NMS system administrators.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |