IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Install and enable application support
Before you can view data collected by monitoring agents, install and enable application support for those agents. Application support files provide agent-specific information for workspaces, helps, situations, templates, and other data.Application support for a monitoring agent includes two types of files:
SQL files Required for adding product-provided situations, templates, and policies to the Enterprise Information Base (EIB) tables maintained by the hub monitoring server. These SQL files are also called seed data. For the SQL files, use the option... Advanced → Add TEMS application support
...provided in the Manage Tivoli Enterprise Monitoring Services.
Catalog and attribute (cat and atr) files Required for presenting workspaces, online help, and expert advice for the agent in Tivoli Enterprise Portal. For the cat and atr files, use the option... Advanced → Utilities → FTP Catalog and attribute file
...provided in the Manage Tivoli Enterprise Monitoring Services.
There is a limit of 512 catalog and attribute files that can reside on a Tivoli Enterprise Monitoring Server. When this limit is reached, the Tivoli Enterprise Monitoring Server will not start and the message Number of installed packages exceeds the maximum of 512 is displayed in the error log. See the Troubleshooting Guide.
All monitoring agents require that application support be configured on all instances of the following infrastructure components:
- Tivoli Enterprise Monitoring Server (both hub and remote monitoring servers)
- Tivoli Enterprise Portal Server
- Tivoli Enterprise Portal desktop client, if the desktop client was installed from the installation media.
You do not need to configure application support for desktop clients downloaded from the Tivoli Enterprise Portal Server using IBM Web Start for Java.
The self-describing agent capability integrates the installation of an agent with the dispersal and installation of associated product support files throughout the IBM Tivoli Monitoring infrastructure. The self-describing agent feature makes it possible for new or updated IBM Tivoli Monitoring agents to become operational after installation, without having to perform additional product support installation steps or restarting the monitoring server or portal server. For more information see Self-describing agent installation. However, the following components are not able to dynamically refresh application support and require a restart after application support has been installed by the self-describing agent feature:
- Tivoli Enterprise Monitoring Automation Server: If this optional component is installed with the Hub monitoring server, the automation server must be restarted after application support has been installed on the Hub monitoring server by the self-describing agent feature.
Application support for monitoring agents is installed independently of where and when the monitoring agents themselves are installed:
- Install application support for a particular type of monitoring agent on the monitoring servers, portal server, and portal desktop clients. Install agents of that type on any managed system in the environment that is compatible with the agent.
- Install application support for a type of monitoring agent before or after any monitoring agents of that type are installed. After you install application support for a particular type of monitoring agent, you can add any number of agents of that type to your environment without having to install application support again.
For example, you can install application support for a Linux OS monitoring agent (the agent type) to a Windows monitoring server (using the IBM Tivoli Monitoring installation media for Windows). Later, you can install any number of Linux OS monitoring agents to Linux computers in your environment (using the IBM Tivoli Monitoring installation media for Linux).
- If you are installing a non-OS agent remotely through the Tivoli Enterprise Portal (see Deploy non-OS agents), application support for the agent must be installed on the Tivoli Enterprise Portal Server before the agent is deployed.
- When you install application support for an IBM Tivoli Composite Application Manager agent on the V6.2.2 fix pack 2 (or subsequent) version of the Tivoli Enterprise Monitoring Server, do not select for installation the File Transfer Enablement component.
If you do, the File Transfer Enablement component shipped with the V6.2.2 fix pack 2 (or subsequent) monitoring server will be replaced, and the following commands will become inoperable...
Because application support for some IBM Tivoli Monitoring 6.x-based distributed agents is included on the Base Infrastructure DVD, you may see application support files that do not apply to all systems.
Configure application support is a two-step process:
- Install the application support files (from installation media).
- Enable the application support (sometimes referred to as adding or activating the application support).
On the portal server and portal desktop clients, application support is enabled when the component is configured. On monitoring servers, application support is enabled by seeding the database with agent-specific information.
The procedures for configuring application support differ by operating system, as summarized in Table 1. On Windows, both installation and enablement of application support are accomplished during the installation of the monitoring servers, portal server, and desktop clients. On Linux or UNIX, this two-step process is more visible, with the enablement step done separately from the installation.
On Windows, for monitoring server, portal server, desktop clients install and enable application support using installation media.
On Linux or UNIX...
- For monitoring server install application support files from installation media then seed using...
itmcmd support2
...or the Manage Tivoli Enterprise Monitoring Services window
- For portal server, install application support files from installation media, then configure the portal server using:
- itmcmd config
...or Manage Tivoli Enterprise Monitoring Services window
- Configure the desktop client using:
itmcmd config
..or the Manage Tivoli Enterprise Monitoring Services window
Configure application support for desktop clients that are installed from the installation media. You do not need to configure application support for desktop clients that are installed by using IBM Java Web Start to download the client from the Tivoli Enterprise Portal Server.
You can seed a nonlocal monitoring server, even if one is not installed on the local computer, by installing the support using option 3, Install TEMS support for remote seeding, then using Manage Tivoli Enterprise Monitoring Services to seed the nonlocal monitoring server. You cannot use itmcmd support to seed a nonlocal monitoring server.
There is no way to uninstall the application support files laid down without uninstalling the Tivoli Enterprise Monitoring Server.
See
- Selecting the correct support media
- Configure application support on the IBM Tivoli Monitoring Base DVDs
- Configure application support for nonbase monitoring agents
- Configure application support on nonlocal monitoring servers
Parent topic:
Install IBM Tivoli Monitoring