TIBCO Hawk HTTP Adapter is a Web application based on the TIBCO Hawk Console API, which facilitates monitoring and management of TIBCO Hawk agents. It allows you to perform discovery, monitoring of agent status, monitoring of agent alerts, method invocation, method subscription, and many more activities on TIBCO Hawk and third-party products. You can also filter the information to view specific data.
The XML output can also be used by an HTML or other XML-aware application. This allows you to access the data from a wide variety of operating systems and the majority of Web servers, such as Tomcat, WebLogic, and JRUN 4. A sample HTML application that uses the XML data is provided with TIBCO Hawk HTTP Adapter and is described in
Chapter 4, Using the Sample HTML Interface.
In addition, TIBCO Hawk HTTP Adapter can be used as a console data provider that can be accessed by other TIBCO Hawk applications using standard HTTP protocol.
TIBCO Hawk HTTP Adapter uses a Java servlet to expand the functionality of the Web server. For more information about servlets, see
http://Java.sun.com/Products/servlet/index.htm.
TIBCO Hawk HTTP Adapter supports the monitoring and management of multiple TIBCO Hawk domains with the same type of transport (that is, TIBCO Rendezvous, TIBCO EMS, or TIBCO DataGrid). It does not support configuring domains with mixed transport types. You can view agent, alert, microagent and method information for all TIBCO Hawk domains in your configuration.
The configuration file used to configure the domains for HTTP Adapter is located in
<HAWK_HOME>\5.2\adapters\http\WEB-INF\classes directory. Refer to the
TIBCO Hawk Installation, Configuration, and Administration guide for details on how to use this file.
This document assumes that you are familiar with installing and using TIBCO Hawk. The TIBCO Hawk-specific terms shown in TIBCO Hawk HTTP Adapter are not described or explained in this document. Please refer to the TIBCO Hawk documentation for information about TIBCO Hawk.
The HTTP Adapter supports HTTPS transport if the web server is configured to accept requests over HTTPS transport. No specific configuration is required on the HTTP Adapter side.