Configuration II - IBM Tivoli Monitoring
- Agent configuration and environment variables
- Configuration files preserved during an upgrade
- Preserving user custom settings
- Files that are preserved on upgrade
- Files that are not preserved on upgrade
- Product behavior with custom configuration settings
- Persistent configuration changes
- Example 1: Overriding the CTIRA_HOSTNAME to change the host name section of the Managed System Name
- Example 2: Altering an existing variable KDC_FAMILIES
- Environment variables
- Common environment variables
- Tivoli Enterprise Portal Server environment variables
- Tivoli Enterprise Monitoring Server environment variables
- Tivoli Enterprise Monitoring Automation Server environment variables
- Tivoli Data Warehouse environment variables
- Tivoli Monitoring Service Console variables
- Common agent environment variables
- Operating system agent environment variables
- Maintaining the EIB on Linux or UNIX
- Securing the IBM Tivoli Monitoring installation on Linux or UNIX
- Uninstall IBM Tivoli Monitoring
- Uninstall the entire IBM Tivoli Monitoring environment
- Uninstall an individual IBM Tivoli Monitoring agent or component
- Uninstall a component on Windows
- Uninstall a component on Linux or UNIX
- Uninstall OMEGAMON Monitoring Agents
- Remove an agent through the Tivoli Enterprise Portal
- Uninstall the Warehouse Proxy
- Uninstall components and agents silently
- Perform a silent uninstallation on a Windows computer
- Perform a silent uninstallation on a Linux or UNIX computer
- Uninstall the event synchronization component
- Uninstall event synchronization manually
- Uninstall IBM Tivoli Monitoring components for a dashboard environment
- Uninstall IBM Tivoli Monitoring components for a dashboard environment in console mode
- Perform a silent uninstallation of IBM Tivoli Monitoring components for a dashboard environment
- Silent response file for uninstallation of IBM Tivoli Monitoring components for a dashboard environment
- Uninstall the Tivoli Authorization Policy Server or tivcmd Command Line Interface for Authorization Policy using the graphical user interface
- Uninstall the IBM Infrastructure Management Dashboards for Servers using the graphical user interface
- Additional resources
- IBM Tivoli Monitoring 6 Welcome Kit
- General education and support Web sites
- Product documentation and IBM Redbooks
- Education offerings
- Service offerings
- Other resources
- Documentation library
- IBM Tivoli Monitoring library
- Documentation for the base agents
- Related publications
- Other sources of documentation
- Support for problem solving
- Use IBM Support Assistant
- Obtaining fixes
- Receive weekly support updates
- Contacting IBM Software Support
- Determine the business impact of a problem
- Describing problems and gathering information
- Submitting problems
- High Availability Guide for Distributed Systems
- Overview
- Monitor functions and architecture
- Monitor functions
- Data visualization
- Situations, events, and alerts
- Event-management integration
- Workflow policies
- Historical data collection
- Monitor architecture
- Typical configuration
- Optional components
- Open Services Lifecycle Collaboration
- Agent resiliency
- High Availability considerations for the Tivoli Enterprise Monitoring Server
- IBM Tivoli Monitoring portal navigation
- Configure for high availability and disaster recovery
- Configure the hub monitoring server for high availability and disaster recovery
- Configure for portal server high availability and disaster recovery
- Configure for IBM Dashboard Application Services Hub high availability and disaster recovery
- Configure for agent and remote monitoring server high availability and disaster recovery
- Configure for warehouse high availability and disaster recovery
- Configure for Warehouse Proxy Agent high availability and disaster recovery
- Configure for Summarization and Pruning Agent high availability and disaster recovery
- Configure for Tivoli Performance Analyzer high availability and disaster recovery
- The hot standby option
- Use hot standby
- Hub Tivoli Enterprise Monitoring Servers
- Remote monitoring servers
- Tivoli Enterprise Monitoring agents
- Tivoli Enterprise Portal server
- Tivoli Enterprise Automation Server
- Failover scenario
- Configure failover support
- Configure the hot standby feature for hub monitoring servers
- On Windows systems: Configuring the hot standby feature for hub Tivoli Enterprise Monitoring Server
- On Linux or UNIX systems: Configuring the hot standby feature for hub monitoring servers
- Configure the hot standby feature for remote monitoring servers
- On Windows systems: Configuring the hot standby feature for remote monitoring servers
- On Linux or UNIX systems: Configuring the hot standby feature for remote monitoring servers
- Configure the hot standby feature for monitoring agents
- Configure the hot standby feature for automation servers
- Verify that failover support is working
- Self describing feature in a failover environment
- The clustering of IBM Tivoli Monitoring components
- Clustering overview
- Supported configurations
- Set up Tivoli Monitoring components in a clustered environment
- What to expect from the IBM Tivoli Monitoring infrastructure in a clustered environment
- Clustered hub monitoring server
- Clustered portal server
- Clustered data warehouse
- Clustered Summarization and Pruning Agent
- Clustered Warehouse Proxy Agent
- Clustered agentless monitoring
- Situations
- Workflow policies
- Short-term data collection
- Long-term data collection
- Tivoli Enterprise Console event integration
- Maintenance
- Create clusters with Tivoli Monitoring components in an HACMP environment
- Prepare for the base cluster
- Define the base cluster for Tivoli Monitoring
- Building a base HACMP cluster for the monitoring server
- Building a base HACMP cluster for the portal server and data warehouse components
- Install DB2 for the base HACMP cluster
- Create the database for the portal server or data warehouse on clusternode1
- Cataloging the portal server and the data warehouse database on clusternode2
- Add the database to the base cluster
- Install the monitoring server on its base HACMP cluster
- Install and set up the monitoring server on clusternode1
- Tivoli Enterprise Monitoring Server reconfiguration procedure for the AIX HACMP environment
- Test the monitoring server on clusternode1
- Set up the monitoring server on clusternode2
- Add the monitoring server to the resource group of the base cluster
- Create start and stop scripts for the monitoring server
- Add the monitoring server as an application server to the base cluster
- Add HACMP monitoring for the monitoring server processes
- Test the monitoring server failover to clusternode2
- Install the portal server on its base HACMP cluster
- Install and set up the portal server on clusternode1
- Test the portal server on clusternode1
- Set up the portal server on clusternode2
- Add the portal server to the resource group of the base cluster
- Create start and stop scripts for the portal server
- Add the portal server as Application Server to base cluster
- Add monitoring for the portal server process
- Test the portal server failover to clusternode2
- Install the Warehouse Proxy Agent or Summarization and Pruning Agent on its base HACMP cluster
- Install and set up the Warehouse Proxy Agent and Summarization and Pruning Agent on clusternode1
- Test the Tivoli Data Warehouse components in the cluster
- Set up the Warehouse Proxy Agent and Summarization and Pruning Agent on clusternode2
- Add the Warehouse Proxy Agent and the Summarization and Pruning Agent to the resource group of the base cluster
- Create start and stop scripts for the Warehouse Proxy Agent and the Summarization and Pruning Agent
- Add the Warehouse Proxy Agent and the Summarization and Pruning Agent as Application Server to base cluster
- Add monitoring for the Warehouse Proxy Agent and the Summarization and Pruning Agent process
- Test the Warehouse Proxy Agent and the Summarization and Pruning Agent failover to clusternode2
- Known problems and limitations
- Create clusters with monitoring components in a System Automation for Multiplatforms environment
- Scenarios tested
- Prepare for the base Tivoli Monitoring cluster with Tivoli System Automation for Multiplatform
- Gathering cluster nodes information
- Check the cluster nodes environment
- Plan for the cluster tiebreaker network device
- Install Tivoli System Automation for Multiplatforms on the cluster nodes
- Create a cluster with all Tivoli Monitoring Components
- Set up a cluster for Tivoli Monitoring
- Building a Base Tivoli System Automation for Multiplatforms Cluster for the Monitoring Server component only
- Building a Tivoli System Automation for Multiplatforms Cluster for the portal server and Tivoli Data Warehouse components
- Install/Configuring DB2
- Building the portal server and Tivoli Data Warehouse Cluster
- Create the Database for Portal server/Tivoli Data Warehouse on node1
- Cataloging the Portal server/Tivoli Data Warehouse Database on node 2
- Install the monitoring server on its base Tivoli System Automation for Multiplatforms cluster
- Install and set up the monitoring server on clusternode1
- Test the monitoring server on clusternode1
- Set up the monitoring server on clusternode2
- Add the monitoring server to the resource group of the Base Cluster
- Test the monitoring server failover to clusternode2
- Install the portal server on the Tivoli System Automation for Multiplatforms cluster
- Install and set up the portal server on clusternode1
- Test the portal server on clusternode1
- Add the portal server to the resource group of the Base Cluster
- Test the portal server failover to clusternode2
- Install the Warehouse Proxy Agent on a Tivoli System Automation for Multiplatforms cluster
- Install and set up the Warehouse Proxy Agent on clusternode1
- Add the Warehouse Proxy Agent to the resource group of the Base Cluster
- Test the Warehouse Proxy Agent failover to clusternode2
- Install the Summarization and Pruning Agent on a Tivoli System Automation for Multiplatforms cluster
- Install and set up the Summarization and Pruning Agent on clusternode1
- Add the Summarization and Pruning Agent to the resource group of the Base Cluster
- Test the Summarization and Pruning Agent failover to clusternode2
- Perform IBM Tivoli Monitoring Maintenance on a Tivoli System Automation for Multiplatforms cluster
- Applying a fix pack to the Hub Tivoli Enterprise Monitoring Server
- Applying a fix pack to the Tivoli Enterprise Portal Server
- Applying a fix pack to the Warehouse Proxy Agent
- Applying a fix pack to the Summarization and Pruning Agent
- Known problems and limitations
- Create clusters with Tivoli Monitoring components in a Microsoft Cluster Server environment
- Set up the hub monitoring server in a Microsoft Cluster Server
- Set up basic cluster resources
- Install and set up the monitoring server on clusternode1
- Add the monitoring server resource to your resource group
- Registry Keys replication
- Test the monitoring server on clusternode1
- Set up the monitoring server on clusternode2
- Check environment variables
- Monitor server user validation
- Test the monitoring server on clusternode2
- Set up the portal server in a Microsoft Cluster Server
- Set up basic cluster resources
- Install and set up DB2 on a Microsoft Cluster Server
- Install DB2 on clusternode1
- Install DB2 on clusternode2
- Add the DB2 resource type to the Cluster Administrator
- Transforming the DB2 instance into a clustered instance
- Add the DB2 resource to the resource group
- Install and set up the portal server in the cluster
- Set up the portal server database and ODBC DSN in the cluster
- Install and set up the portal server in clusternode1
- Add the IBM Eclipse Help Server resource to the resource group
- Add the portal server resource to the resource group
- Test the portal server in the cluster
- Set up Tivoli Data Warehouse components in a Microsoft Cluster Server
- Set up basic cluster resources
- Install and set up DB2 on a Microsoft Cluster Server
- Install and set up Tivoli Data Warehouse components in the cluster
- Set up the Tivoli Data Warehouse database and ODBC DSN in the cluster
- Install the Warehouse Proxy Agent and the Summarization and Pruning Agent in the cluster
- Add the Warehouse Proxy Agent resource to the resource group
- Add the Summarization and Pruning Agent resource to the resource group
- Test the Tivoli Data Warehouse components in the cluster
- Upgrade IBM Tivoli Monitoring in a Microsoft Cluster environment
- Tivoli Monitoring maintenance on the cluster
- Known problems and limitations
- Configure the cluster creation
- Autonomous mode and autonomous agents
- Achieving High-Availability with the autonomous agent
- Autonomous mode agent switch from a secondary monitoring server back to the primary hub monitoring server
- Agent configuration parameters
- Switchback processing
- Predefined scripts
- EIF Information
- Documentation library
- IBM Tivoli Monitoring library
- Documentation for the base agents
- Related publications
- Tivoli Monitoring community on Service Management Connect
- Other sources of documentation
- Support information
- Program Directory