Page 1 of 2

Genarating and Testing Hawk Rulebases

Generate a new Hawk Rulebase
Refer to: http://appintegration.putnaminv.com/esb/tibcobw/BWInfrastructure/mini/hawkRulebases.html

Active a hawk rulebase

The location where the rulebase needs to be placed would be - /opt/putnam/tibco/hawk/autoconfig. Once the rulebase is migrated to the correct location, re-start the hawk agent. For more details on restarting the hawk agent , refer to: http://appintegration.putnaminv.com/esb/tibcobw/BWInfrastructure/mini/hawkAgents.html# For verifying whether the rulebase is successfully activated please refer to the hawk log file at /opt/putnam/tibco/hawk/logs/Hawk.log.

Testing the Rulebase

All rulebases generated should be tested at least once before migrating them to the production environment. Though paging an application team is not possible in TEST environments we can atleast ensure that proper email messages are sent as part of the Hawk Alert. The correct way to test a hawk rulebase is to append a line to the log file that would satisfy the test defined in the rulebase. For example, if you are using the default test (ERROR(?!.*DATALOSS)|EXCEPTION (?!.*DATALOSS)/i), then you can append each of the following lines to the log file and ensure that in each case (except item 5), an alert is raised. ERROR error EXCEPTION exception BW-ADVISORY-300000 subject [_RV.ERROR.SYSTEM.DATALOSS.OUTBOUND.BCAST] Ensure that the consequence action takes place i.e. an email is been received. If you receive an email, it would mean that the rulebase was tested successfully. Verify the contents of the email to make sure, there were no errors. Append a line: echo line >> log.txt echo ADV_NAME=REGISTRATION.NO_RESPONSE >> FOPM_PROCESSING.log

Testing for REGISTRATION.COLLISION Errors

Since the REGISTRATION.COLLISION errors occur on detection of a duplicate RV Subscriber with the same CM Name, it is a bit tedious to simulate this. The best way to simulate this scenario, is to run both the service instance of the same BW App in Active-Active mode. Normally, all RV based applications are deployed in Active-Passive Mode. In order to perform the tests for this, the Fault Tolerant setting for the application can be modified to false. i.e. <isFT>false</isFT>

Page 2 of 2

Start the application and view both the log files. When both the service instances are started, there would be a REGISTRATION.COLLISION error in the log file. Once the error occurs in the log file, hawk rulebase will detect the advisory message and terminate the application. NOTE: Once the hawk rulebase is successfully tested, revert back the setting made for running the application in Active-Active mode.

Page last modified on October 20, 2008, at 12:13 PM

Powered by

PmWiki