Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 1 TIBCO Hawk Installation Overview : Post installation Tasks

Post installation Tasks
Verify the Installation
To verify the installation, ensure that all directories and files have been added correctly. For details, see TIBCO Hawk Directory Structure on page 246.
External JRE
For JVM microagents: If you have specified external JRE when installing TIBCO Hawk, then tools.jar in the .hma file must point to a JDK installation location.
If you plan to use an external JRE than the one supplied with TIBCO Hawk 5.2.0, please make sure that the correct values are set for JVM_LIB_PATH, JVM_LIB_DIR, JVM_LIB_SERVER_DIR, JAVA_HOME, JRE_HOME, JRE_ROOT in the .cfg and .tra files in CONFIG_FOLDER\bin.
Setting Permissions for Executing HMA on UNIX/Linux
TIBCO Hawk MicroAgent (HMA) process must execute under “root” privileges, on UNIX/Linux platforms.
This process internally gathers various system level information through different system artifacts such as, files, folders, scripts and so on. Access failure to such system-guarded items results in incorrect results of some of the microagent methods.
If the installation is done using root user, then the installation process, accordingly creates “setuid” permissions with root ownership for the TIBCO HMA executable.
If the installation is done using a non-root user, then after installation is complete, the root user must change the ownership of the following files to root and set the setuid permission as follows:
chown root tibhawkhma,
chown root starthma.sh
chmod u+s tibhawkhma
chmow u+s starthma.sh
Then, a normal user with executable permissions will be able to execute HMA with effective "root" permissions.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved