You can track information specific to one agent, microagent or application by writing this information to a log file in an action that is part of a rule. To do this, set up a rule that retrieves specific information (such as free disk space), give it a test that always evaluates to true, and write the important information to a log file. For example, you might create a rule with the data source Performance: LogicalDisk: percent free Space (Microsoft Windows) or
file system: getByPartition: percent free (Unix) to be collected every five minutes. The rule might have a test such as
percent free != -1 which would always be true. The test might have an action such as echo
logfile.dat (which would be prefixed in Microsoft Windows with cmd /c). This would append information on free disk space to a specific log file.
Refer to the TIBCO Hawk Programmer's Guide for further details. The sample AMI API code provided in
HAWK_HOME/examples/ami_api may help you in understanding the concepts and getting started.
This error occurs whenever a Microsoft Windows service's performance DLL (service htpps4.1 in this case) fails to load. Each failed load also causes the application (Hawk HMA) to leak memory. The problem lies in the Microsoft Windows performance counter libraries. To fix this problem, rename the DLL listed in the error message.
On UNIX, quoted strings with embedded blanks cannot be passed as command arguments to UNIX shell scripts by means of the Custom::execute,
Custom::executeForNumber and
Custom::executeForString methods. The Java Virtual Machine (JVM) parses these strings as blank delimited tokens and passes them as separate arguments.
When using the process:getProcess method (UNIX) or
performance: ProcessCount method (Microsoft Windows), you may find that process names longer than a certain length cannot be matched exactly. This limit on process names comes from the operating system functions used to collect this information.
In the Process::getProcess and Process
::getInstanceCountbyCommand methods, the full command may not be returned. The command is truncated to between 55 and 80 characters, depending upon the operating system, and contains the same information as the
ps -ef utility. To get the full command, use a script that utilizes the UCB
ps utility (for example,
/usr/ucb/ps -auxww | grep -c mycommand) in conjunction with
Custom::executeForNumber().
To start a process you want to run in the foreground, create a utility that the TIBCO Hawk agent can invoke with custom:execute and pass it the process you want to execute in the foreground. This utility is responsible for setting all the permissions required to start and display the GUI application.
In the Rulebase Test Editor, if PostedCondition is specified as
${Posted.x} > 0 and saved, it is displayed by the Test editor as
PostedConditionExist when you reopen the rulebase. Both of these represent the same expression. Similarly,
${Posted.x} == 0 is displayed as
!PostedConditionExist.
To resolve this issue, comment the <Resource> tag that points to H2 database from context.xml file in
HAWK_HOME/webconsole/tomcat/webapps/hawkwebconsole/META-INF folder to work in no database mode.