If you're looking for TIBCO Hawk Interview Questions for Experienced or Freshers, you are at right place. There are lot of opportunities from many reputed companies in the world. According to research TIBCO Hawk has a market share of about 0.32%. So, You still have opportunity to move ahead in your career in TIBCO Hawk. Mindmajix offers Advanced TIBCO Hawk Interview Questions 2019 that helps you in cracking your interview & acquire dream career as TIBCO Hawk Developer.
Q. What is TIBCO Hawk Rulebase ?
1. A Rulebase is a collection of rules that contain management logic.
2. Rulebases consists of rules that are made up of data sources, tests and actions.
3. A Rulebase must have atleast one rule, a rule must have atleast one test and a test must have atleast one action.
4. Datasources are microagent methods that collect data synchronously or asynchronously and return it to an agent.
5. Datasource is the source of input data and it is always a method of microagent.
6. After the information is received, one or more tests are applied to evaluate the information to compute a true/false value which is used to trigger the actions
Subscribe to our youtube channel to get new updates..!
Q. What are the different ways of creating TIBCO Hawk RuleBases ?
There are multiple ways for creating the rulebases.
1. Hawk Display
2. Hawk Accelrator
Using TIBCO Hawk Display, you can create rulebases with specialized rules. (TIBCO Hawk Display is not included in TIBCO Runtime Agent). Hawk allows you to specify a very large number of alert conditions and alert results.
Using Hawk Accelerator, you can edit the templates according to your need and generate the rulebases using scripts, this is very easy.
For both the options, you must have purchase the full TIBCO Hawk product and Hawk Accelerator to create TIBCO Hawk rulebases.
The same rulebase can be loaded on a single service, or multiple services.
Multiple rules defined in the same rulebase can monitor a particular application or system function.
For example, an application rulebase could include one rule for issuing a medium-level alert if disk space or CPU usage exceeds certain thresholds. Another rule could issue a high-level alert and send a pager message to the system administrator if the application process terminates.