General Installation Problems And Resolutions; Agent Builder Application Support Is Not Displayed In Listappinstallrecs Output If It Is Manually Installed Without Recycling The Monitoring Server - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Table 7. Frequently asked questions for UNIX-based systems installation (continued)
Problem
Why does a Linux or UNIX-based
installation to a non-default path
create directories in the default
/opt/IBM/ITM path?

General installation problems and resolutions

This section describes general installation problems and resolutions.
Agent Builder application support is not displayed in
listappinstallrecs output if it is manually installed without
recycling the monitoring server
If you run the scripts to manually install the Agent Builder application support on
the Tivoli Enterprise Monitoring Server (TEMS) and specify both the user name
and password, the expected result is that the application support files are loaded
without causing the TEMS to restart. After that, if you run the tacmd
listapplinstallrecs command to verify the application support installation, the
support is not listed in the command output. As a result, a lower version
68
IBM Tivoli Monitoring: Troubleshooting Guide
Solution
This is an expected condition. The following example depicts an AIX installation
to a non-default location. The following links are created when the SetPerm
command is run:
/opt/IBM/ITM/tmaitm6
/opt/IBM/ITM/tmaitm6/links
/opt/IBM/ITM/tmaitm6/links/aix52
/opt/IBM/ITM/tmaitm6/links/aix52x6
/opt/IBM/ITM/tmaitm6/links/aix53
The SetPerm command creates those links by design. Some of the binaries have
hard-coded execution paths. This coding is required by the operating system in
order to invoke a program object in authorized mode [root owned with UID].
The IBM Tivoli Monitoring Installation and Setup Guide documents installation
on a single target location. However, by using local testing and configuration
control, you can install to multiple target locations and run Tivoli Monitoring
from all of them. For example, you can run multiple remote monitoring servers
on a single server. Of course, the multiple monitoring servers require a
non-default configuration, such as using different base port numbers.
v If all installations on the system are at the same maintenance level, running
the SetPerm command and updating the hard-coded /opt/IBM/ITM/tmaitm6/
links directory structure does not cause any problems.
v If all installations on the system are not at the same maintenance level,
running the SetPerm command and updating the hard-coded
/opt/IBM/ITM/tmaitm6/links directory structure can cause problems. This
scenario needs more testing than the scenario where all installations are at the
same level.
The following procedure might resolve problems you encounter in the latter
scenario:
v Maintain an installation on this system with the most current maintenance.
v Run the SetPerm command from this installation each time after other
installations apply maintenance or add agents.
v Run the SetPerm command from this installation each time after other
installations run the SetPerm command or the secureMain commands.
Note: For some cases, the OS Agents for example, only one agent can be
installed because of the agent's interaction with the operating system.