Products | Versions |
---|---|
TIBCO Hawk | - |
Not Applicable | - |
Resolution
=======
For a workaround, "posted condition" should be used, which is also the advanced option to combine two different rule in one test condition. In the first rule, use the method OnStarterStateChanged to detect starter becoming disabled. When the test condition becomes true, the action part would be "posted condition". In "Advanced Test Editor" select "Clear Test" and give it the states of starter resumed. By setting this, the value of posted condition would remain 1 until states of starter resumed. This "Advanced Test Editor" is quite flexible and you are able to select "Clear Timer" and give it the period of this posted condition remain 1. This value should be greater than 180 (Escalation period) and less than 180*2 seconds.In the second rule, use any of the Synchronous methods as a data source, such as Method: getUptime of Self microagent. In "Test Builder", Selected $(posted.XXX) == 1 as a test condition. In "Action Editor", Resume the starters, in advance option, selected escalation period with 180 second. This example used OnStarterStateChanged. You can also use any other Asynchronous method in this way to achieve your "Escalation Period" goal.
An example rulebase file for reference is attachmed to this kb (Filename: monitoringprocessstarter.hrb). Deploy this rulebase to a test Process or service and re-deploy it. Refer to the TIBCO Administrator-> User’s Guide-> Chapter 8 Setting Deployment Options-> Adding a Custom Rulebase to a Process or Service.