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
      Attention: If you are using EMS 8.2 and above, use tibjms-2.0.jar.
    • tibcrypt.jar
  • 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>-encryptedPassword</arg>
<arg/>
<arg>-server</arg>
<arg><ems-server-url></arg>
<arg>-server_in_agent_name</arg>
<arg>-ssl_trace</arg>
<arg>-ssl_vendor</arg>
<arg><ssl-vendor-used-by-ssl-client></arg>
<arg>-ssl_trusted</arg>
<arg><path-to-ssl-trusted-certificate></arg>
<arg>-ssl_identity</arg>
<arg><path-to-ssl-identity-provider-certificate></arg>
<arg>-ssl_expected_hostname</arg>
<arg>server</arg>
<arg>-ssl_password</arg>
<arg><ssl-certificate-encrypted-password></arg>
</arguments>