The cartridge requires that TIBCO is installed on the monitored host and that the following .jar files are present and available to the agent. These .jar files are commonly found in the directories listed below. Please note that the directory locations may vary depending on your installation and product versions.
Although not a requirement, having standalone Hawk monitoring configured is strongly recommended. This facilitates agent configuration and simplifies troubleshooting. In order to configure Hawk monitoring these .jar files should also be present in the TIBCO/tra/domain/”DOMAIN_NAME”/plugin directory.
Please ensure the tibjmsadmin.hma and hawkemshma.jar files are also present in the directory.
The tibjmsadmin.hma file can be copied from the ems/”version”/samples/admin/hawk directory. Please ensure the user, password, and server arguments are present and correct and outside of the block comment tags.
c:\TIBCO\hawk\lib:
agent.jar
ami.jar
console.jar
rvutils.jar
security.jar
talon.jar
utilities.jar
util.jar
c:\TIBCO\ems\5.1\lib\:
jms.jar
tibjms.jar
tibrvjms.jar
tibcrypt.jar
tibjmsadmin.jar*
C:\TIBCO\tibrv\8.1\lib:
tibrvj.jar
*Required in some installations
*Please note that this information is provided as an EXAMPLE only and that installation paths may vary. When the agent is configured, you will be asked to configure the agent properties to ensure it has access to these three directories. You will need to ensure that the Foglight Agent Manager has at a minimum read and execute permissions on these files.
The EMS Server must be part of the domain and must be visible in TIBCO Administrator. This is achieved by properly configuring the tibemsd.conf configuration file in your /TIBCO/cfgmgmt/ems/data folder and by using the Domain Utility to add the EMS to the administration domain if not already done. For more information on the Domain Utility, refer to “Chapter 4: EMS Server Plugin” in the Domain Utility documentation located in the /tra/”VERSION”/docs folder.
In order to configure the agent to use a Rendezvous connection, it is only necessary to provide the correct connection parameters in the Agent Properties. This includes the RV Service, Network, and Daemon fields.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center