A schedule is a configuration object that defines when a rulebase, rule, test or action is active.
For example, you might have a rulebase that should be used only during business hours, so you create a schedule with an inclusion period of Mondays through Fridays, 9 AM to 5 PM. The schedule may also define exclusion periods, or times when the object must not be active, such as between 12:00 PM and 12:59 PM for lunch. A schedule is active (or “in-schedule”) during inclusion periods only if no exclusion period applies. This will be available as .hsf file.
Applying Schedules to Rulebase Objects:
After defining a schedule in the Schedule Editor dialog, you can apply it to any rule, test or action in a rulebase.
Process to promote Hawk rules to other environments – External and Internal Variables
Rulebases should never change from one environment to another. They should be built to run on any server or any environment.
In order to do this you should always use external variables anytime a value could differ between environments or servers. The external variables file is treated like a configuration file and is expected to be different on every server or environment the rulebase is deployed.
Related Page: How To Monitor SLA’s Using TIBCO Hawk Rulebase
Referencing External Variables:
External variables are variables defined by a user on the machine where the TIBCO Hawk agent runs.
Subscribe to our youtube channel to get new updates..!
First, you define the variable values in a properties file on the local machine. Then you specify the variable file using the -variable option when starting Hawk Agent. Then you can reference the external variable in a rulebase.
Using the Monitoring Archive Utility. The monitoring archive, MAR file, contains one or more monitoring configurations. A monitoring configuration is a TIBCO Hawk rulebase template.
The MAR utility converts TIBCO Hawk rulebases into templates so that they can be deployed to any target within any TIBCO Administrator domain. A rulebase template, in a MAR file, has the extension .hrt.
The rulebases can contain two types of rules:
These rules use the data source of the microagents belonging to TIBCO applications, such as TIBCO BusinessWorks or TIBCO Adapters. Each of these applications have an unique type.
2. Agent-specific or non-application specific.
These rules do not use the data source of the microagents belonging to TIBCO applications.
Lets say if we have multiple bw engines in the domain and all the engines needs to have similar kind of monitoring, then we can go for MAR utility. First we need to develop a rulebase and then use it as a template with MAR. Now you can go and deploy this MAR file from admin and deploy it on all the bw engines present in the domain or the required ones. By doing so, we don’t need to create the rulebases separately for each and every bw process.
I used two rulebases here bw.hrb and TibRendezvous.hrb and created the mymar.mar file in the following way.
Create mar file
mar c[v]df “description” marfile inputfiles [-Xtype]
Update mar file
mar u[v]df “description” marfile inputfiles [-Xtype]
Extract mar file
mar x[v]f marfile [inputfiles]
mar x[v]pf properties marfile [inputfiles]
List the contents of mar file
mar t[v]f marfile
C:ProgramDataTIBCO_HOMEtibcocfgmgmthawkbin>mar cvf bwmar.mar ./
INFO: Mar File: bwmar.mar
INFO: Command: CREATE
INFO: Input Rulebase: ./
INFO: Processing file: C:ProgramDataTIBCO_HOMEtibcocfgmgmthawkbinbwmemory
INFO: Processing file: C:ProgramDataTIBCO_HOMEtibcocfgmgmthawkbinTibRende
INFO: Create new mar file: bwmar.mar
INFO: Adding rulebase: bwmemoryusage-bwengine.hrt
INFO: Adding rulebase: TibRendezvous.hrt
After creating the mar mymar.mar file, I am able to deploy it from admin as shown in the below screenshots. Now, this utility made bw.hrb rulebase deployed in all the bw engines(2 bw processes) present in my test domain as I have enabled “Enable all” option in admin and TibRendezvous.hrb deployed in my machine, which is a single machine available in this test domain. Finally I have shown the screenshot of hawk display how the rulebases got created.