Methods

When I start a GUI process with the method custom:execute in the Microsoft Windows environment, the process only runs in the background. How can I cause such a process to run in the foreground?

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.

Custom: execute run in the foreground on a system wide basis by changing how the TIBCO Hawk agent service is configured. Follow these steps:

1. Select Start--Settings--Control Panel, then double-click Services.
2. Choose the TIBCO Hawk service and click Startup.
3. In the Service window that appears, click the System Account radio button in the Log On As panel.
4. Check the Allow Service to Interact with Desktop check box.

All processes spawned by the TIBCO Hawk agent are now in the foreground.

Platform: Not Specified

Version: All

I call a script using the method custom:executeForNumber(executeForString), but the microagent terminates the script before it is finished because it takes too long. What should I do?

Here are a few possibilities. Note that your script has to return within 10 seconds.

If the script collects information over an interval of time, you can split the functionality of the script into multiple scripts and call them using a set of actions with increasing escalation periods.
The script can spawn an application instrumented with AMI that collects the information and returns it to the rulebase asynchronously. You can then create a rule that responds to the asynchronous information.
The script can spawn a process that writes information to a log file, and you can create a rule that responds to additions to the log file.

Platform: Not Specified

Version: All

Why do I get a negative ID Process or ID Thread number?

When subscribing to Process/Thread methods on the performance microagent, the ID Process or ID Thread column may display a negative number other than -1. This is not an error; the negative number signifies that this particular instance of Process/Thread no longer exists and this row is taken out in the next subscription interval. In this case, -1 as a Process ID is reserved for Process instance _Total, and -1 as a Thread ID is resolved for Thread instance  _Total/_Total.