Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 2

Installation and Basic Configuration

The TIBCO Hawk installer provides a custom profile, TIBCO Hawk Admin Agent, during product installation. If you would like to use TIBCO Enterprise Administrator to monitor the Hawk data, you must install TIBCO Hawk Admin Agent along with the Hawk components.

In order for the Hawk Admin Agent to auto-register with the TEA server, create an entry for the Admin Agent machine in the TEA server machine’s host file and also create an entry for the TEA server machine in the Hawk Admin Agent machine’s host file.

Refer to the "Understanding the Installation Profiles" section in the TIBCO Hawk Installation, Configuration, and Administration guide.

To verify if the Admin Agent is installed, you can check if it is available under the Start menu:

Start > All Programs > TIBCO > TIBCO Hawk Admin Agent <version> >.

Configuration

After installing TIBCO Hawk and the Admin Agent, you must do the following:

•	Configure the location of the transport that will be used in the <TIBCO_HOME>/tea/agents/hawk/<version>/bin/tibhawkteaagent.tra file.See Configuring Transport Installation Location.

•	Configure the Hawk domain and transport to be used in the <CONFIG_FOLDER>\tibco\cfgmgmt\hawkteaagent\config\hawk-domain-transport-cfg.xml file. See Configuring Hawk Domain and Transport.

•	Configure the Admin Agent in the configuration files located in <CONFIG_FOLDER>/hawkteaagent/config directory. See Configuring the Location for Log Files.

Configuring Transport Installation Location

The following transport modes are available to be configured as a means of communication between Hawk Agent and Admin Agent:

•	TIBCO DataGrid (distributed as a part of Hawk installation)

•	TIBCO Rendezvous® (RV)

•	TIBCO Enterprise Message Service™ (EMS)

At least one transport mode should be configured in the <CONFIG_HOME>/tibco/cfgmgmt/hawkteaagent/config/hawk-domain-transport-cfg.xml file of Admin Agent to enable message or event communication among various Hawk Agent and Admin Agent.

TIBCO Hawk 5.2 installation has TIBCO Rendezvous configured as the default mode of message and event transport between Hawk Agent and HMA, as well as between Hawk Agent and Hawk WebConsole.

For details on configuration for all transport modes, refer to the ’Configuring Transport Modes’ section in the TIBCO Hawk Installation, Configuration, and Administration guide.

If either TIBCO DataGrid or TIBCO Rendezvous is chosen as a transport between the Hawk Agent and Admin Agent, the same is used as a transport between the Hawk Agent and the Hawk Microagent or other AMI based applications. You cannot configure it to use a different transport. However, if you choose to use TIBCO Enterprise Message Service as the transport between the Hawk Agent and the Admin Agent, you can only use TIBCO Rendezvous as the transport between the Hawk Agent and the Hawk Microagent or other AMI based applications.

TIBCO Rendezvous and TIBCO Enterprise Message Service are two independent products that need to be installed separately. Additional configurations need to be performed manually based on whether they are installed before or after installing TIBCO Hawk 5.2, and whether any of them share the same <TIBCO_HOME> installation folder.

If you install TIBCO Rendezvous and TIBCO Enterprise Message Service before you install TIBCO Hawk and you install all three in the same TIBCO_HOME, the installers will automatically configure their values in the tibhawkteaagent.tra configuration file and you need not do it manually. Update the <TIBCO_HOME>/tea/agents/hawk/<version>/bin/tibhawkteaagent.tra file for <EMS_HOME> and <RV_HOME> if any of the following is true:

•	If you use an existing transport (TIBCO Rendezvous or TIBCO Enterprise Message Service) either from a previous installation of TIBCO Hawk 4.x or independent installations of these TIBCO products in the same TIBCO_HOME where Hawk 5.2 is installed.

•	If you install TIBCO Rendezvous or TIBCO Enterprise Message Service in the same TIBCO_HOME after installing TIBCO Hawk 5.2.

•	If you currently use or are planning to use a different TIBCO_HOME for each of the TIBCO Rendezvous, TIBCO Enterprise Message Service , and TIBCO Hawk components.

Configuring Hawk Domain and Transport

The Admin Agent can monitor multiple domains configured with different or same transports.

The monitored domain names must be unique within and across different transport types.

The Admin Agent can monitor multiple transports at the same time. Each of those transports supports multiple domain configurations.

Domain Transport Configuration File (hawk-domain-transport-cfg.xml)

Configure the domains in <CONFIG_FOLDER>\tibco\cfgmgmt\hawkteaagent\config\hawk-domain-transport-cfg.xml directory. It follows the DomainTransportCfg.xsd XML schema. The possible choices for domain transports are TIBCO Rendezvous transport or TIBCO Enterprise Message Service transport.

If you choose the TIBCO Rendezvous transport, values for the following fields should be specified:

•	Hawk Domain Name: The name of the TIBCO Hawk domain.

•	Rendezvous Service, Rendezvous Network, and Rendezvous Daemon: These attributes together configure the TIBCO Rendezvous parameters for communicating with TIBCO Hawk agent.

•	Hawk Security Impl (Optional): The name of the class implementing the security policy.

If you choose Enterprise Message Service transport, values for the following fields should be specified:

•	Enterprise Message Service Server URL: The location of the Enterprise Message Service server.

•	Enterprise Message Service User and Enterprise Message Service Password: The login credentials to access the Enterprise Message Service server.

Refer to the following examples on how to configure Hawk Domains and their respective transports. One or more Hawk domains can be monitored. You require one DomainTransport section per monitored domain as follows.

For example, the configuration for the TIBCO Rendezvous transport domain (default) is as follows:

---

 

<!-- AS transport domain -->

<hk:DomainTransport>

<hk:HawkDomainName>as-domain</hk:HawkDomainName>

<hk:Transport>

<hk:ASTransportCfg>

<hk:listenUrl></hk:listenUrl>

<hk:discoverUrl>tibpgm://8989/</hk:discoverUrl>

<hk:invocationTimeout>30000</hk:invocationTimeout>

<hk:receiveBufferSize>1000</hk:receiveBufferSize>

<hk:virtualNodeCount>100</hk:virtualNodeCount>

<hk:workerThreadCount>32</hk:workerThreadCount>

</hk:ASTransportCfg>

</hk:Transport>

<hk:SecurityPolicy></hk:SecurityPolicy>

</hk:DomainTransport>

---

 

Configuring Admin Agent

All the required configuration parameters are stored in the following files:

−	hawk-domain-transport-cfg.xml

−	logback-config.xml

−	hawk-tea-agent.properties

These files are located in the <CONFIG_FOLDER>/hawkteaagent/config directory. The following options can be configured:

Table 2 Admin Agent Properties Options

Parameter	Default Value	Description
hawk.tea.agent.hostname	localhost	Admin Agent host name. In the case of remote connection, use IP Address instead of DNS/Host Name.
hawk.tea.agent.port	8701	Admin Agent port.
auto.config.tea.server.url	None	TEA server URL, where the Admin Agent automatically registers. In the case of remote TEA server, use the IP Address of the TEA server URL instead of DNS or Host Name. If you do not want to auto-register the Admin Agent with the TEA server then you should comment of this parameter out.
hawk.tea.agent.jdbc.user	None	The JDBC user.
hawk.tea.agent.jdbc.password	None	The JDBC password.
hawk.tea.agent.jdbc.url	jdbc:h2:tcp://localhost/~/hawk_tea_agent_db	The JDBC URL.
max.connection	30	The JDBC connection pool's maximum number of connections.
login.timeout	60 secs	The JDBC pool connection login timeout in seconds.
retention.period	604800000	The Time in milliseconds to retain the Hawk Alert in persistence store.

Configuring the Location for Log Files

The Admin Agent uses logback for application logging. By default, the logs are generated under CONFIG_FOLDER/hawkteaagent/config/logback-config.xml. You can modify various configuration parameters and change the default settings.

For example, the default configuration is as follows:

---

 

<configuration scan="true">

<!-- Configure log location and filename. -->

<property name="LOG_HOME" value=
"<CONFIG_HOME>/tibco/cfgmgmt/hawkteaagent/logs" />

<property name="LOG_FILE_NAME" value="hawk-tea-agent" />

<appender name="STDOUT" class=
"ch.qos.logback.core.ConsoleAppender">

<!-- encoders are assigned the type         ch.qos.logback.classic.encoder.PatternLayoutEncoder
        by default -->

          <encoder>

            <pattern>%date{dd MMM yyyy;HH:mm:ss.SSS} [%thread]              %-5level %logger{36} - %msg%n</pattern>

          </encoder>

</appender>

 

<appender name="FILE"

          class="ch.qos.logback.core.rolling.RollingFileAppender">

          <file>${LOG_HOME}/${LOG_FILE_NAME}.log</file>

          <append>true</append>

          <rollingPolicy            class="ch.qos.logback.core.rolling.FixedWindowRollingPo                                                            licy">

          <fileNamePattern>${LOG_HOME}/${LOG_FILE_NAME}.%i.log</fi                                                    leNamePattern>

          <minIndex>1</minIndex>

          <maxIndex>10</maxIndex>

          </rollingPolicy>

          <triggeringPolicy

            class="ch.qos.logback.core.rolling.SizeBasedTriggering                                                          Policy">

            <maxFileSize>10MB</maxFileSize>

          </triggeringPolicy>

          <encoder>

            <pattern>%date{dd MMM yyyy;HH:mm:ss.SSS} [%thread]               %-5level %logger{35} - %msg%n</pattern>

          </encoder>

</appender>

<!-- Define log levels for individual category -->

        <logger name="com.tibco.tea.agent.hawk" level="INFO" />

        <logger name="com.tibco.hawk" level="WARN" />

      <logger name="com.tibco.tea.agent.internal" level="ERROR" />

        <logger name="org.eclipse.jetty" level="ERROR" />

<!-- Root logger -->

         <root level="INFO">

           <appender-ref ref="FILE" />

           <!-- <appender-ref ref="STDOUT" />-->

          </root>

</configuration>

---

 

Copyright © Cloud Software Group, Inc. All Rights Reserved