CONFIGURE ONE TIBCO HOST INSTANCE ON PRIMARY SERVER
1). Go to CONFIG_HOME/hkam/<host_instance_name>/scripts.
NOTE: In the configure-hkam.properties file, use only forward slashes ("/").
2). Edit configure-hkam.properties to specify the following variables:
tibco.hawk.version=5.1
tibco.hawk.home=<tibco-home>
Example: Your <hawk-home> is /home/amx/tibco/hawk/5.1, here is /home/amx/tibco.
tibco.hawk.config.home=<tibco-config-home>
3). Run the configure script from the command line:
- On Windows: configure-hkam.bat
- On UNIX: ./configure-hkam
4). Configure the CLEvent Publisher Microagent as per the instructions in Configuring CLEvent Publisher Microagent.
5). Modify the following properties:
Edit HAWK_CONFIG/bin/hawkagent.cfg to configure the following properties:
a). hma_plugin_dir "CONFIG_HOME/hkam/<host_instance_name>/plugin".
b). variables "CONFIG_HOME/hkam/<host_instance_name>/data/Hawk-amx_variables.properties".
c). auto_config_dir "CONFIG_HOME/hkam/<host_instance_name>/rulebases".
*6). For Hawk 5.x
If Hawk 5.x and TIBCO ActiveMatrix are installed in the same TIBCO_HOME on a machine, do the following:
- On Windows, confirm that attach.dll resides in TIBCO_HOME/tibcojre64/1.7.0/bin
- On Linux, copy libattach.so to TIBCO_HOME/tibcojre64/1.7.0/lib/amd64
*7). Configuring for TIBCO Enterprise Message Service.
For all the operating systems, do the following configurations:
Update tibco.env.EMS_HOME to point to EMS_ROOT in tibhawkagent.tra, if one of the following is true:
Enterprise Message Service was installed after installing Hawk 5.x
Enterprise Message Service and Hawk 5.x are installed in different TIBCO_HOMES
For example, EMS_HOME/ems/7.0
If Enterprise Message Service and Hawk 5.x are installed on different machines, copy the following JAR files from EMS_HOME/lib to HAWK_ROOT/lib:
jms.jar
tibjmsadmin.jar
tibjms.jar
tibcrypt.jar
*8). If the ActiveMatrix Administrator server or TIBCO Host instance is configured to use SSL-enabled Enterprise Message Service, modify the hawkems-<host_instance_name>.hma file located at CONFIG_HOME/hkam/<host_instance_name>/plugin with the following parameters:
<arguments>
<arg>-user</arg>
<arg>admin</arg>
<arg>-password</arg>
<arg></arg>
<arg>-server</arg>
<arg>ssl://localhost:7243</arg>
<arg>-version</arg>
<arg>8.0</arg>
<arg>-traceDir</arg>
<arg>%HAWK-Config Home%/tibco/cfgmgmt/hawk/logs</arg>
<arg>-traceFilename</arg>
<arg>emshma.log</arg>
<arg>-traceLevel</arg>
<arg>7</arg>
<arg>-ssl_trace</arg>
<arg>-ssl_vendor</arg>
<arg>j2se</arg>
<arg>-ssl_trusted</arg>
<arg>%TIBCO_EMS_HOME_ESC%/samples/certs/server_root.cert.pem</arg>
<arg>-ssl_private_key</arg>
<arg>%TIBCO_EMS_HOME_ESC%/samples/certs/server.key.p8</arg>
<arg>-ssl_expected_hostname</arg>
<arg>server</arg>
<arg>-ssl_password</arg>
<arg>#!5jXJBMnzj4234OBgOoAtWqQggon81D5HrKRxZVRHn/8=</arg>
</arguments>
-----------------------------------------------------------------------------------------------------------------
CONFIGURE MULTIPLE TIBCO HOST INSTANCES ON PRIMARY SERVER
1). For each TIBCO Host instance, configure the rulebases as described in previous steps #1->#2->#3!
2). Copy all the files from the plugins, rulebases and script folders in the hkam directories of all TIBCO Host instances to any one of the common plugins, rulebases and script folders.
3). Edit the generate-noderb-<Hostname>.properties in the scripts folder. Change the rulebase.dir to refer to the new rulebase location.
4). Copy all the properties from all the Hawk-amx_variables.properties in the data folders to the common Hawk-amx_variables.properties file.
5). Edit the common Hawk-amx_variables.properties:
HAWK_ANTRUNNER=<common-script-folder>/antrunner
HAWK_CONFIG_ROOT=<common-script-folder>
HAWK_RULEBASE_ROOT=<common-rulebase-folder>
HAWK_START_TH_CMD=<common-script-folder>/start_tibcohost
NOTE: Comment the other duplicate properties.
6). Modify the following properties:
Edit HAWK_CONFIG/bin/hawkagent.cfg to configure the following properties:
a). hma_plugin_dir <common-plugin-folder>
b). variables <common-data-folder>/common-Hawk-amx_variables.properties
c). auto_config_dir <common-rulebase-folder>
*7. Configuring CLEvent Publisher Microagent
a).Create the Event Definitions file using <common-plugin-folder>/eventdefs.xsd and reference the existing sample event definitions file sampleEventdefs.xml.
b).Create a Common Logging configuration file, and provide an entry for the file in the Event Definitions file. A sample common logging configuration file, sample_log4j.xml, is provided for reference.
If you are using sample_log4j.xml, update the CommonLoggingJMSAppender settings in the sample_log4j.xml file.
Edit hawkcleventpublisher.hma in <common-plugin-folder>, by providing the correct path and name of the Event Definitions file.
*8. Modify the EMS URL in the sample_log4j.xml .
CONFIGURE MULTIPLE TIBCO HOST INSTANCES ON REPLICATE SERVER
Most steps are the same as on primary servers except the following: Defect (
HKAM-351) - some properties were missed in Hawk-amx_variables.properties during the replicating. It causes Hawk rulebases not to work. As a workaround, you should copy the missed properties from the primary server to here and modify it manually.
Note: If you get the errror:
"Can't create AMX Service Microagent for Node [DevNode], Process id of node is not available. Make sure Hawk HMA process is running and Hawk Process Microagent is available."
If HMA is running in the background, HMA methods work fine. Check hawkagent.tra that the property "tibco.class.path.extended" contains "<tibco-home>/tibcojre64/1.7.0/lib/tools.jar".
