Reference › Test Document Reference › Metrics › TIBCO Hawk Metrics

TIBCO Hawk Metrics

TIBCO Hawk is a tool for monitoring and managing distributed applications and operating systems. Unlike other monitoring solutions, TIBCO Hawk software uses TIBCO Messaging software for communicating and inherits many of its benefits. These benefits include a flexible architecture, enterprise-wide scalability, and location-transparent product components that are simple to configure.

DevTest has out-of-the-box integration with TIBCO Hawk for monitoring distributed applications and operating systems metrics in the context of testing. TIBCO Hawk provides in-container metrics for TIBCO BusinessWorks process archives. By using TIBCO Hawk, DevTest can monitor metrics of all activities in any TIBCO BusinessWorks process that is deployed. This integration facilitates peering inside of a process to understand where bottlenecks are occurring.

Prerequisites: Using DevTest with this application requires that you make one or more files available to DevTest. For more information, see Third-Party File Requirements in Administering.

Follow these steps:

1. Create a staging document.
2. On the Metrics tab of the staging document, click Add .
3. Select TIBCO Hawk from the drop-down list.

   The following parameters are available:

   • Transport: Select Rendezvous or EMS.
   • Hawk Domain: Enter the TIBCO Hawk domain.
   • Rendezvous Service
   • Rendezvous Network
   • Rendezvous Daemon
   • EMS Url
   • EMS User
   • EMS Password
4. Click OK.

   The Hawk Object Attribute Viewer opens.

5. Select the Process Archive and expand beneath it.
6. The GetProcessDefinitions method retrieves the process definitions that are defined in the Process Archive.
7. Use the Process Definition Name as parameter for the GetActivities method.

   TIBCO Hawk provides a number of metrics for Process Activities.

8. Provide a filter with the Process Definition Name and the Activity Name.
9. Select Method Return Values and click OK.

   Activity Metrics are now monitored for test cases staged with this staging document.

TIBCO Hawk can also be invoked in a test case, through TIBCO Hawk APIs.

Note: It takes a few minutes for TIBCO Hawk to initialize itself and achieve a ready state where it can report metrics. TIBCO notifies DevTest when this ready state is achieved. It is important to set lisa.net.timeout.ms to a fairly high value (at least 2-3 minutes) to avoid timeouts when using staging documents that collect the TIBCO Hawk metrics.