IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Agent Installation Guides > UNIX Agent Installation Guide
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Agent installation and configuration
Agent installation and configuration requires the use of the IBM Tivoli Monitoring Installation and Setup Guide and agent-specific installation and configuration information.
To install and configure the monitoring agent, use the "Installing monitoring agents" procedures in the IBM Tivoli Monitoring Installation and Setup Guide.
If you are installing silently by using a response file, see "Performing a silent installation of IBM Tivoli Monitoring" in the IBM Tivoli Monitoring Installation and Setup Guide.
In addition to the installation and configuration information in the IBM Tivoli Monitoring Installation and Setup Guide, use this agent-specific installation and configuration information to install the monitoring agent.
- Requirements for the monitoring agent
Before installing this monitoring agent, review its specific requirements.
- Enable the monitoring agent to run as a nonroot user
The "Post-installation steps for nonroot installations" section of the IBM Tivoli Monitoring Installation and Setup Guide describes the post-installation setup process required to enable a nonroot user. Those instructions result in the availability of root authority to the underlying IBM Tivoli Monitoring processes. These instructions, in contrast, remove root authority from the underlying processes.
- Set up the monitoring agent in a cluster environment
You can install and set up the monitoring agent in an HACMP clustered environment by following these instructions.
- Filtering capabilities on the names of processes
You can distinguish process names that are longer than 768 characters, so that situations can be defined on the relevant part of the name. You can also use this enhancement for filtering processes of any length.
- Complying with FIPS requirements
The monitoring agent complies with the Federal Information Processing Standard (FIPS) 140-2. This computer security standard requires stronger checksum algorithms (for example, SHA-256 and SHA-512) when you define situations for checking file changes.