Before you can view data collected by monitoring agents,
you must 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 are 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, and installing them
on a monitoring server is
also called seeding the monitoring server.
- Catalog and attribute (cat and atr) files are required
for presenting workspaces, online help, and expert advice for the
agent in Tivoli Enterprise Portal.
Note: 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. For more information,
see the IBM Tivoli Monitoring Troubleshooting Guide.
All
monitoring agents
require that application support be configured on all instances of
the following infrastructure components:
Note: The self-describing agent capability integrates
the installation of an agent with the dispersal and installation of
associated product support files throughout your 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.
- Dashboard data provider component of the Tivoli Enterprise Portal Server: If this optional
component is enabled, the portal server must be restarted after application
support has been installed on the portal 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).
Important: - If you are installing a non-OS agent remotely through the Tivoli Enterprise Portal (see Deploying 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 tacmd getfile, tacmd
putfile, and tacmd executecommand commands
will become inoperative.
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.
Configuring application support is a two-step process:
- Installing the application support files (from installation media).
- Enabling 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.
Table 1. Procedures for installing and enabling
application support| Operating system |
Monitoring servers |
Portal server |
Desktop clients1 |
|---|
| Windows |
Install and enable application support using
installation media. |
Install and enable application support using
installation media. |
Install and enable application support using
installation media. |
| Linux or UNIX |
- Install application support files from installation media.
- Seed the monitoring server using:
- itmcmd support2 command,
OR
- Manage Tivoli Enterprise Monitoring Services window
|
- Install application support files from installation media.
- Configure the portal server using:
- itmcmd config command, OR
- Manage Tivoli Enterprise Monitoring Services window
|
- Install application support files from installation media.
- Configure the desktop client using:
- itmcmd config command, OR
- Manage Tivoli Enterprise Monitoring Services window
|
| z/OS® |
This book does not describe configuring
application support for a monitoring server installed
on a z/OS system. See Configuring
the Tivoli
Enterprise Monitoring Server on z/OS for
information and instructions. The portal server and
desktop client are not supported on z/OS.
If you have a monitoring server on z/OS, use the procedures in this
book to configure application support on the portal server and
desktop clients.
|
- You need to 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.
|