![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• A rulebase is a configuration object that provides the rules for the monitoring activities that are to be autonomously performed on an agent. At the core of all rulebase monitoring activity is the collection of data, testing of that data, and taking actions based on the test results. All monitored data is provided by the agent's microagents through microagent subscriptions. All actions taken by a rulebase are in the form of method invocations. Rulebase objects specify their data sources and actions using the MethodSubscription and MethodInvocation classes of the Console API. Therefore, understanding these, and related classes, is a prerequisite for using the Configuration API. For more information on these classes, refer to Chapter 2, Console API.
•
•
•
• The RulebaseElement class provides common methods to get and set the element's name and schedule parameters. The Rule, Test and Action classes do not require a name to be specified in the constructor. Only the Rulebase class requires a name specified in the constructor. In places where an array of RulebaseElement objects is required, all elements in the array must have unique names.The data source for a Rule is its source of input data, and is always a method subscription to a microagent. The data source of a Rule provides information about some condition on a managed node. After information is received, one or more tests are applied to evaluate it. The MethodSubscription of a data source provides a stream of data objects.The microAgentName and the method name used to construct the DataSource can be obtained from MicroAgentDescriptor and MethodDescriptor, respectively.
•
•
•
•
•
•
•
•
• All Test object state transitions cause its ConsequenceAction objects to be evaluated. The policy of the ConsequenceAction objects govern whether an evaluation results in an action execution. The ClearAction objects are a list of actions that will be executed when the Test object undergoes the T->F transition.Although operators can return different types, only those which return a Boolean value may be used in tests (i.e. as arguments to Test.setTestExpressionOperator() ). The other non-Boolean operators are used only as nested operators.
• For a more complete specification that encompasses all Unicode characters, see The Java Language Specification by Gosling, Joy, and Steele.For more information on overruling, see the TIBCO Hawk Administrator's Guide.MinutesInDay contains a set of 1440 continuous 1-minute intervals in a day. The MinutesInDay object is in-schedule if the time for checking the schedule is included in the MinutesInDay.DaysInWeek contains a set of 7 days in a week. A DaysInWeek is in-schedule if the day of date for checking the schedule is included in the DaysInWeek.DaysInMonth contains a set of 31 days in a month. A DaysInMonth is in-schedule if the day in the date for checking the schedule is included in the DaysInMonth.MonthsInYear contains a set of 12 months in a year. A MonthsInYear is in-schedule if the month of the date used for checking the schedule is included in the MonthsInYear.Because all schedules are stored in a single file, each agent will load the schedules at startup. However, the scheduler in the agent will evaluate a schedule only if the agent has loaded rulebases that reference that schedule. Such schedules are referred to as active because there is active interest in them.In the preceding example, agentX and +group1 belong to +groupX. Also, agent1 belongs to +group1 as well as +groupX.agent1 uses rulebase1. Agents in +group2 uses rulebase2 and rulebase3. All agents uses rulebase4 as rulebase4 maps to "++", the all group. All agents that are running under Windows operating system will uses rulebase1.
The -rulebases option supported by the agent (RulebaseEngine MicroAgent) can be used together with the RulebaseMap to specify additional rulebases.
• Retrieving and updating configuration objects on a TIBCO Hawk agent or repository is accomplished by invoking methods on the RuleBaseEngine or Repository microagents. This involved both the monitoring and management components of the TIBCO Hawk Console API as agents and microagents need to be discovered and method invocations are performed on the required microagents. See Appendix A, Common Configuration Object API Methods, for commonly used methods on RuleBaseEngine or Repository microagent when using the Configuration Object API.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |