Copyright © Cloud Software Group, Inc. All Rights Reserved

Installation and Configuration

Installation

TIBCO Hawk HTTP Adapter is automatically installed with TIBCO Hawk 5.2. For more detail, please refer to TIBCO Hawk Installation, Configuration, and Administration Guide.

Deployment

To deploy TIBCO Hawk HTTP Adapter copy the HAWK_HOME/adapters/http directory to the webapps directory of your webserver (HAWK_HOME/webconsole/tomcat/webapps).

Configuration

If TIBCO Datagrid is used as the transport, copy the jar (as-common.jar) to the lib folder of Tomcat (HAWK_HOME/webconsole/tomcat/lib).

If TIBCO Rendezvous is used as the transport, copy the following JAR to the lib folder of Tomcat (HAWK_HOME/webconsole/tomcat/lib):

•	RV_HOME/lib/tibrvj.jar

If TIBCO Enterprise Message Service is used as the transport, copy the following JARs to the lib folder of Tomcat (HAWK_HOME/webconsole/tomcat/lib):

•	EMS_HOME/lib/tibrvjms.jar

•	EMS_HOME/lib/tibjms.jar

•	EMS_HOME/lib/TIBCrypt.jar

•	EMS_HOME/lib/jms.jar (in case of EMS 6.3) or EMS_HOME/lib/jms-2.0.jar (in case of EMS 8.0)

Make sure that TIBCO Datagrid and TIBCO Rendezvous shared libraries are in:

•	PATH (Windows)

•	LD_LIBRARY_PATH (Linux,Solaris)

•	SHLIB_PATH (HP-UX)

•	LIBPATH (AIX)

•	DYLD_LIBRARY_PATH (mac)

Logging Configuration

The HTTP Adaptor Server uses Log4j based logging to log trace messages in TIBCO Hawk HTTP Adapter server and underlying AMI/Console API Log file configuration is defined in web.xml as follows:

<!-- TibHawkXml log4j configuration file -->

<!-- This file will be picked from WEB-INF/classes folder-->

<init-param>

<param-name>log4j_config_file</param-name>

<param-value>/log4j_http_adapter.properties</param-value>

</init-param>

AMI Configuration

TIBCO Hawk HTTP Adapter publishes itself as a microagent (named as TibHawkServlet) using AMI. The AMI configuration for the TIBCO Datagrid transport is same as of the Console API configuration. In case of multiple TIBCO Datagrid domains, TIBCO Hawk HTTP Adapter AMI uses the last TIBCO Datagrid Domain configuration, configured in DomainTransportCfg.xml.

For TIBCO Rendezvous Domains, admin can configure a separate AMI. This is configurable in web.xml.

<!-- AMI Rendezvous(RV) configuration, to publish TibHawkXML servlet as a microagent-->

<init-param>

<!-- AMI RV service -->

<param-name>ami_rv_service</param-name>

<param-value>7474</param-value>

</init-param>

<init-param>

<!-- AMI RV network -->

<param-name>ami_rv_network</param-name>

<param-value></param-value>

</init-param>

<init-param>

<!-- AMI RV Daemon -->

<param-name>ami_rv_daemon</param-name>

<param-value>tcp:7474</param-value>

</init-param>

If TIBCO Rendezvous AMI parameters are not configured than the TIBCO Rendezvous Console parameters are used for AMI configuration. In case of multiple TIBCO Rendezvous domains, the last configured TIBCO Rendezvous domain parameters will be used for AMI communication.

For EMS Domain, the AMI communication will use the TIBCO Rendezvous AMI configuration in web.xml. If no TIBCO Rendezvous AMI configuration is configured, then it will use TIBCO Rendezvous AMI with default configuration:

Table 2 AMI Default Parameters for TIBCO Rendezvous Transport

Parameter	Definition	Default Value
Service	TIBCO Rendezvous session parameter	7474
Network	TIBCO Rendezvous Network parameter	""
Daemon	TIBCO Rendezvous Daemon parameter	tcp:7474

Domain Configuration

To configure a transport for a domain, edit the following parameters in web.xml under the TIBHawkXml definition

<!-- Domain transport configuration -->

<!-- This file will be picked from WEB-INF/classes folder-->

<init-param>

<param-name>DomainConfigFile</param-name>

<param-value>/DomainTransportCfg.xml</param-value>

</init-param>

The Hawk HTTP Adapter allows easier specification of multiple TIBCO Hawk domains. You can view agent, alert, microagent and method information for all TIBCO Hawk domains in your configuration simultaneously.

The DomainTransportCfg.xml file provides the configuration for the AlertCollector component and specifies the list of TIBCO Hawk domains and their corresponding transports. It follows the xml schema defined as per DomainTransportCfg.xsd. The DomainTransportCfg.xml and DomainTransportCfg.xsd files are located at the HAWK_HOME\adapters\http\WEB-INF\classes folder.

This DomainTransportCfg.xml is an example xml configuration that uses two different transports for two domains. There should be one DomainTransport section per managed domain as shown below.

<!-- RV transport domain-->

<hk:DomainTransport>

<hk:HawkDomainName>default</hk:HawkDomainName>

<hk:Transport>

<hk:RVTransportCfg>

<hk:service>7474</hk:service>

<hk:network></hk:network>

<hk:daemon>tcp:7474</hk:daemon>

</hk:RVTransportCfg>

</hk:Transport>

<hk:SecurityPolicy></hk:SecurityPolicy>

</hk:DomainTransport>

<!-- RV transport domain with security enabled -->

<hk:DomainTransport>

<hk:HawkDomainName>Hawk1</hk:HawkDomainName>

<hk:Transport>

<hk:RVTransportCfg>

<hk:service>7474</hk:service>

<hk:network></hk:network>

<hk:daemon>tcp:localhost:7474</hk:daemon>

</hk:RVTransportCfg>

</hk:Transport>

<hk:SecurityPolicy>COM.TIBCO.hawk.security.trusted.Trusted</hk:SecurityPolicy>

</hk:DomainTransport>

Copyright © Cloud Software Group, Inc. All Rights Reserved