Problem
Solution
TEMA not pre-installed
On Windows, when running the Installer for a Blue Medora monitoring agent for IBM Tivoli Monitoring, the following error message is displayed: "The environmental variable CANDLE_HOME is not set in this system. Please set it and run the installer again."
On Windows, when running the Installer for a Blue Medora monitoring agent for IBM Tivoli Monitoring, the following error message is displayed: "The environmental variable CANDLE_HOME is not set in this system. Please set it and run the installer again."
All Blue Medora monitoring agents for IBM Tivoli Monitoring require a pre-existing IBM TEMA exist before installation. Typically, an IBM Tivoli Monitoring Windows, Unix, or Linux OS Agent fulfills this requirement. Once an IBM agent with a TEMA has been installed, restart the Installer and enter the path of the pre-existing IBM Tivoli Monitoring installation (typically C:\IBM\ITM) when prompted to "Enter your Tivoli Monitoring installation directory".
Note: In addition to the ITM OS Agents, most other IBM ITM agents (such as the Oracle, DB2, MS-SQL, etc) also include the required TEMA files.
Note: In addition to the ITM OS Agents, most other IBM ITM agents (such as the Oracle, DB2, MS-SQL, etc) also include the required TEMA files.
JRE 1.5 not in path
Whole Attributes groups are not returning data, although the agent itself is reporting Availability and Log related data in the TEPS.
Whole Attributes groups are not returning data, although the agent itself is reporting Availability and Log related data in the TEPS.
Java 1.5 or greater is required to run most Blue Medora ITM Agents. The local installer for Windows installs Java 1.5 as part of the installation process. When performing a remote deploy of the agent to Windows systems, Java 1.5 or greater must already exist or be manually installed on the target system before the remote deploy is executed.
After Java is installed, JAVA_HOME must be set in the system environment and %JAVA_HOME%\bin must be on the system PATH. JAVA_HOME must be set to the top level Java directory, which is the directory with bin and lib subdirectories (for example,. C:\Program Files\IBM\Java50\jre). When JAVA_HOME is set correctly and %JAVA_HOME%\bin is part of the system PATH, then running java.exe from a command prompt displays the Java command usage help. If JAVA_HOME is not set correctly, the output of entering “java” or “java.exe” at the command prompt is: "the command is not recognized as an internal or external command, operable program, or batch file."
Note: If the system-wide Java installation is not at least 1.5, then the monitoring agents will not run. If the system Java installation cannot be upgraded, then you can install Java 1.5 into another directory and direct the agent to use the newly installed 1.5 Java installation. To change which version of Java the monitoring agent uses, edit KBx_run.bat files that exist in the IBM Tivoli Monitoring installation directory. The exact location differs depending on platform. The batch files assume that a working JAVA_HOME and PATH exist in the environment, so you can change the batch files to set JAVA_HOME and PATH to a different Java installation.
After Java is installed, JAVA_HOME must be set in the system environment and %JAVA_HOME%\bin must be on the system PATH. JAVA_HOME must be set to the top level Java directory, which is the directory with bin and lib subdirectories (for example,. C:\Program Files\IBM\Java50\jre). When JAVA_HOME is set correctly and %JAVA_HOME%\bin is part of the system PATH, then running java.exe from a command prompt displays the Java command usage help. If JAVA_HOME is not set correctly, the output of entering “java” or “java.exe” at the command prompt is: "the command is not recognized as an internal or external command, operable program, or batch file."
Note: If the system-wide Java installation is not at least 1.5, then the monitoring agents will not run. If the system Java installation cannot be upgraded, then you can install Java 1.5 into another directory and direct the agent to use the newly installed 1.5 Java installation. To change which version of Java the monitoring agent uses, edit KBx_run.bat files that exist in the IBM Tivoli Monitoring installation directory. The exact location differs depending on platform. The batch files assume that a working JAVA_HOME and PATH exist in the environment, so you can change the batch files to set JAVA_HOME and PATH to a different Java installation.
