Administrator's Guide - IBM Tivoli Monitoring
- Introduction
- New in this release
- Tivoli Management Services
- Tivoli Management Services components
- Tivoli Enterprise Portal client
- Desktop, Browser, and Java Web Start clients
- Historical data collection
- System administrator tasks
- Performance Monitoring service provider
- Prepare the Tivoli Enterprise Portal environment
- Browser client
- Windows write and delete privileges
- Add your company logo and URL
- Start the Tivoli Enterprise Portal client
- Use Web Start to download and run the desktop client
- Install the IBM JRE
- Windows: Installing the IBM JRE
- Linux: Installing the IBM JRE
- Enable tracing for the JRE
- Downloading and running the desktop client
- Manually creating a shortcut for the Web Start client
- Start the desktop client on another portal server
- Start the browser client on another portal server
- Specify the browser used for Launch Application and for online help
- Add operating platforms to the Navigator view
- Prepare your dashboard environment
- Roadmaps
- Set up a basic monitoring environment without single sign-on and without per user authorization controls
- Set up a monitoring dashboard environment with single sign-on and with per user authorization controls
- Migrate a basic monitoring dashboard environment to a dashboard environment with single sign-on and per user authorization controls
- Set up load balancing for a high availability dashboard environment
- Create a connection to the IBM Tivoli Monitoring dashboard data provider
- Create custom dashboard pages that display monitoring data
- Configure an HTTP Server to load balance multiple Tivoli Enterprise Portal Servers
- Set Clone IDs on each Tivoli Enterprise Portal Server
- Generate the plugin-cfg.xml file
- Control UISolutions imports
- Edit environment configuration settings
- Tivoli Enterprise Portal client configuration settings
- Edit the client parameters
- Portal client parameter list
- Enable the HTTP proxy server
- Set application properties for Linux and UNIX systems
- Set the environment variable when the hub is on a z/OS system
- Tivoli Enterprise Portal Server configuration settings
- Edit the portal server environment file
- Portal server environment variables
- Prune events on the portal server database
- Control the size of event attachments
- Control the number of logon attempts
- Tivoli Enterprise Monitoring Server configuration settings
- Tivoli Enterprise Monitoring Automation Server configuration settings
- Enable user authentication
- User authentication through the hub monitoring server
- Prerequisites for configuring authentication on the hub monitoring server
- Configuration procedure
- Configure user authentication from the command line
- Configure authentication by using Manage Tivoli Enterprise Monitoring Services
- Ldapsearch for LDAP information
- ldapsearch command-line options
- Sample ldapsearch command (no TLS/SSL)
- Sample ldapsearch command (with TLS/SSL)
- LDAP user authentication through the portal server
- Prerequisites for configuring LDAP authentication on the portal server
- About single sign-on
- Roadmap for setting up the portal server to use an LDAP user registry and single sign-on
- Use Manage Tivoli Enterprise Monitoring Services to configure the portal server for LDAP authentication
- Use the Linux or UNIX command line to configure the portal server for LDAP authentication
- Use the TEPS/e administration console
- Start the TEPS/e administration console
- Configure the portal server for LDAP authentication using the TEPS/e administration console
- Start and stop TEPS/e
- Configure TLS/SSL communication between the portal server and the LDAP server
- Map Tivoli Enterprise Portal user IDs to LDAP distinguished names
- Reconfigure the browser client for SSO
- Import and export LTPA keys
- Manage new LDAP users
- Disable LDAP authentication on the portal server
- Migrate LDAP authentication from the monitoring server to the portal server
- Authentication through the Tivoli Enterprise Monitoring Automation Server
- LDAP user authentication using Microsoft Active Directory
- Before you begin
- Roadmap overview
- Plan and create monitoring server and portal server users within Active Directory
- Create and configure the portal server user accounts and permissions, if desired
- Enable and configure LDAP user authentication for the portal server, if desired
- Start the TEPS/e administration console
- Map portal client userids to LDAP Distinguished Names
- Enable LDAP authentication within the portal server
- Configure TEPS/e for TLS/SSL, if necessary
- Enable and configure LDAP user authentication for the monitoring server, if desired
- Active Directory LDAP verification tools
- User scenarios
- Authenticate monitoring server userids with Microsoft Active Directory
- Authenticate portal server userids with Microsoft Active Directory
- Enable TEPS/e administration
- Define the wasadmin password
- Enable ISCLite (TEPS/e eWAS server administration)
- Log into the TEPS/e administration console
- Define the LDAP user registry in the Integrated Solutions Console
- Add your LDAP user registry to the eWAS realm
- (Optionally) test the LDAP lookup within TEPS/e
- Define a test userid using portal server user administration
- Use Tivoli Enterprise Portal user authorization
- Administer Users
- Users and User Groups
- Permissions
- Applications
- Navigator views
- Member Of and Members
- Manage user IDs
- Manage user groups
- Notes on user administration
- Troubleshooting logon error messages
- Use role-based authorization policies
- Authorization policy concepts
- Predefined roles and permissions
- Prepare to enable authorization policies
- Policy management scenarios
- Best practices for creating authorization policies
- Create and assign administrator roles
- Create and assign policy distributor roles
- Policy management examples
- Enable authorization policies in the portal server
- Authorization policy auditing
- Change the Authorization Policy Server configuration properties after installation and configuration
- Manage the authorization policy store
- Work with multiple domains
- Deployment scenarios
- Multiple domains with shared roles and authorization policies
- Multiple domains with independent authorization policies
- Create policies for specific IBM Tivoli Monitoring domains
- Securing communications
- Configure TLS/SSL communication between the hub monitoring server and the LDAP server
- Configure TLS/SSL communication between Dashboard Application Services Hub and the dashboard data provider
- Use third party certificate authority signed certificates for the portal server
- Configure TLS/SSL communication for the Dashboard Application Services Hub server
- Configure TLS/SSL communication with the Authorization Policy Server
- Use the WebSphere generated certificates to configure TLS/SSL for the Authorization Policy Server
- Use third party certificates to configure TLS/SSL for the Authorization Policy Server
- Configure the tivcmd CLI for TLS/SSL
- Configure TLS/SSL communication between the portal server and the Authorization Policy Server
- Configure TLS/SSL communication between the load balancing HTTP Server and each portal server's local HTTP server
- Extracting the portal server's local HTTP server public signer certificate
- Configure TLS/SSL communication for the IBM HTTP Server used for load balancing multiple portal servers
- Configure TLS/SSL communication between Dashboard Application Services Hub and an HTTP server used for load balancing multiple portal servers
- Export the IBM HTTP Server signer certificate
- Add the HTTP Server certificate to the Dashboard Application Services Hub trust store
- Enable FIPS for IBM Tivoli Monitoring
- Enable SP800-131a for IBM Tivoli Monitoring
- Import the TEPS/e certificates into the portal server keyfile database
- Use the GSKit command-line interface to work with key databases and certificates
- Use the GSKit iKeyman utility to work with key databases and certificates
- Set the JRE for GSKit and starting Key Manager
- Create a new key database
- Create a new public-private key pair and certificate request
- Use a temporary self-signed certificate
- Receive the CA-signed certificate
- Saving the password to a stash file
- Audit logging
- Audit log XML elements mapped to the ITM Audit attribute group
- Audit log XML example
- Audit environment variables
- Take Action and command execution audit logging
- Situation event integration with Tivoli Enterprise Console
- Default mapping of situation events to IBM Tivoli Enterprise Console events
- Expand a generic event message situation description
- Generic mapping for agent specific slots
- Assign severity for Tivoli Enterprise Console events
- Localize message slots
- Situation event statuses and IBM Tivoli Enterprise Console event generation
- Synchronize situation events
- Check the IBM Tivoli Enterprise Console event cache
- Change the configuration of the event synchronization on the event server
- Define additional monitoring servers for the event synchronization on the event server
- Close sampled events
- Change rule set parameters for the omegamon.rls rule set file
- Use the Rules Check utility
- Edit the Event Integration Facility configuration
- Specify EIF forwarding for a situation event
- Customize the event message
- Update the XML used by the MCS Attribute Service
- Use the NetView console through the IBM Tivoli Enterprise Console event viewer
- Situation event integration with Tivoli Netcool/OMNIbus
- Configure connectors for the common event console
- Common Event Console Configuration window
- Purpose of extra table columns
- TEC Connector tab: defining information for extra table columns
- OMNIbus Connector tab: defining information for extra table columns
- Best practices for using event synchronization
- Troubleshooting problems with connection to Tivoli Enterprise Console server on Linux systems
- Maintaining monitoring agents
- Agent tasks in the Tivoli Enterprise Portal
- Add an agent through the Tivoli Enterprise Portal
- Configure an agent through the Tivoli Enterprise Portal
- Start, stopping, and recycling an agent through the Tivoli Enterprise Portal
- Update an agent through the Tivoli Enterprise Portal
- Remove an agent through the Tivoli Enterprise Portal
- Update an agent through the command-line interface
- Clear the Deployment Status table
- Change the monitoring server an agent connects to
- Self-describing monitoring agents
- Self-describing event flow at the monitoring server
- Self-describing agent installation
- Self-describing agent installation errors
- Dynamically updating the self-describing installation options
- Suspend the self-describing capability
- Self-describing auto refresh and seeding
- Enable or disable the self-describing capability at the monitoring server
- Enable or disable the self-describing capability at the agent
- Determine if agents are enabled for self-description
- Environment variables that control the self-describing capability
- Agent Management Services
- Features of the Tivoli Agent Management Services
- Tivoli Agent Management Services installation and configuration
- Monitor the availability of agents
- Manage the agent manually
- Agent-based services
- Autonomous capabilities
- Environment variables for autonomous behavior
- Situation limitations
- UTF-8 encoded XML files
- Configure Agent Management Services on Tivoli System Monitor Agent
- Private situations
- Private situation operation
- Private situation XML specification
- Exported enterprise situation XML specification
- Private situation examples
- Private history
- Enterprise situation override XML specification
- SNMP alerts
- SNMP alert configuration
- Trap configuration XML specification
- SNMP element
- TrapDest element
- TrapAttrGroup element
- Situation element
- StatTrap
- SNMP PassKey encryption: itmpwdsnmp
- MIB for SNMP alerts and agent emits
- OMNIbus configuration for SNMP
- Configure OMNIbus to receive SNMP alerts
- Sample OMNIbus rules for SNMP alerts
- Enable OMNIbus heartbeat automation
- EIF events
- EIF event configuration
- EIF event mapping XML specification
- EIF event destination configuration XML specification
- Common slots for EIF emitted events
- EIF life cycle event
- EIF heartbeat event
- Master reset event
- Sending private situation events by using TLS/SSL communication
- Agent Service Interface
- Start the Agent Service Interface
- Access Authorization Group Profile
- Agent Service Interface - Agent Information
- Agent Service Interface - Situations
- Agent Service Interface - History
- Agent Service Interface - Queries
- Agent Service Interface - Service Interface Request
- Agent Service Interface request - Agent information
- Agent Service Interface request - Agent subnode list
- Agent Service Interface request - Attribute files list
- Agent Service Interface request - Attribute file contents
- Agent Service Interface request - Attribute group report
- Agent Service Interface request - Agent table and situation list
- Agent Service Interface request - Private situation control
- Agent Service Interface request - Situation summary
- Agent Service Interface request - Agent monitoring statistics
- Agent Service Interface request - History report
- Agent Service Interface request - Configuration control
- Centralized Configuration
- Centralized Configuration overview
- Centralized Configuration design
- Configuration load list XML specification
- Configuration load list keyword substitution
- Environment variables in the configuration load list
- Bootstrap configuration load list
- Environment variables for Centralized Configuration
- Enable password encryption in configuration files on z/OS
- Centralized Configuration sample setup
- Centralized Configuration startup
- Initiating Centralized Configuration with agent environment variables
- Initiating with enterprise monitoring agent environment variables
- Set Centralized Configuration environment variables during system monitor agent installation
- Initiating Centralized Configuration with a load list file
- Initiating by manually placing the load list file
- Initiating with remote deployment of non-agent bundles
- Initiating with tacmd putfile
- Initiating Centralized Configuration with a service interface request
- Initiating in the Agent Service Interface
- Initiating using the Service Interface API (kshsoap)
- Agent autonomy on z/OS
- Manage historical data
- About historical data collection
- Historical data collection configuration
- Change the directory for short-term history files
- Performance impact of historical data requests
- Impact of large amounts of historical data on the monitoring server or agent
- Requests for historical data from large tables
- Scheduling the warehousing of historical data
- Use a data mart to improve long or complex queries
- Sample data mart SQL script for IBM Tivoli Monitoring
- Tivoli Data Warehouse and short-term history configuration
- Tivoli Data Warehouse range partition migrations
- Migrate non-partitioned tables to partitioned tables for DB2 on Linux, UNIX, and Windows
- Migrate non-partitioned tables to partitioned tables for DB2 on z/OS
- Migrate non-partitioned tables to partitioned tables for Oracle
- Summarization and pruning configuration
- About the Summarization and Pruning agent
- Best practices for summarization and pruning
- Summarized and pruned data availability
- Configure summarization and pruning for attribute groups
- Configure summarization and pruning for managed system groups
- Change global configuration settings
- How to disable the Summarization and Pruning agent
- Error logging for stored data
- Collect Agent Operations Log history
- Conversion process for using delimited flat files
- Estimate space required to hold historical data tables
- Limit the growth of short-term history files
- What to do when the short-term history file directory size reaches its limit
- Convert short-term history files to delimited flat files
- Convert files using the krarloff program
- Convert history files to delimited flat files on Windows systems
- Archive procedure using the Windows AT command
- Location of the Windows executable files and historical data collection table files
- Location of Windows historical data table files
- Convert history files to delimited flat files on an IBM i system
- Storing the historical data stored on an IBM i system
- Conversion process on an IBM i system
- After running the krarloff rolloff program
- Convert history files to delimited flat files on UNIX Systems
- History data conversion overview
- Perform the history data conversion
- Perform a one-time conversion
- Scheduling basic automatic history conversions
- Customize your history conversion
- Convert history files to delimited flat files on HP NonStop Kernel Systems
- Convert history files to delimited flat files on z/OS systems
- Automatic conversion and archiving process on z/OS systems
- Convert files using the KPDXTRA program
- Attribute formatting
- About KPDXTRA
- DD names required to be allocated for KPDXTRA
- KPDXTRA parameters
- KPDXTRA program messages
- Location of the z/OS executable files and historical data table files
- Manual archiving procedure
- Maintaining the Persistent Data Store
- Use your historical data for analytic usage
- Warehouse Proxy agent for analytics
- Tivoli Enterprise Monitoring Agent for analytics
- Examples of historical data collection for analytics
- Tivoli Common Reporting
- Tivoli Common Reporting overview
- Prerequisites for Tivoli Common Reporting
- Upgrade from a previous version of monitoring agent reports
- Limitations
- Ensure that historical reporting is enabled
- Create and maintain the dimension tables
- Configure the Summarization and Pruning agent to create and maintain the dimension tables
- Create the dimension tables using the Schema Publication Tool
- Manually creating and maintaining the dimension tables
- Import reports using the report installer
- Import and run IBM Cognos reports
- Run a prerequisites scan
- Connecting to the Tivoli Data Warehouse using the database client over ODBC
- Import reports through the Dashboard Application Services Hub
- Import and run BIRT reports
- Replicating the Tivoli Enterprise Portal Server database
- Understanding the Tivoli Enterprise Portal Server database
- Run the migrate-export script
- Run the migrate-import script
- Run migrate-import from source Windows to target Windows
- Run migrate-import from source Windows to target Linux or UNIX
- Run migrate-import from source Linux or UNIX to target Windows
- Run migrate-import from source Linux or UNIX to target Linux or UNIX
- IBM Tivoli Monitoring Web Services for the SOAP server
- About the SOAP client
- Configure Tivoli Monitoring Web Services (SOAP server)
- Define hubs
- Define hubs on Linux and UNIX using the CLI
- Add users
- Configure IBM Tivoli Monitoring Web Services (SOAP server) on UNIX and Linux systems
- Tuning SOAP transaction performance on AIX systems
- Enable SOAP security
- Verify the configuration
- Use IBM Tivoli Monitoring web services
- Start the SOAP client and making a request
- Use your browser
- Use the SOAP client command-line utility (kshsoap)
- Issuing SOAP requests as system commands
- SOAP methods
- IBM Tivoli Monitoring web services scenarios
- Generate daily logical operation summaries and charts
- Obtaining data snapshots and offline table and charts
- Sending alerts into an IBM Tivoli Monitoring platform
- Create collaborative automation using SA IO
- Acknowledging an event within an IBM Tivoli Monitoring platform
- Report contents
- Enable the IBM Tivoli Monitoring Charting Web Service
- Use the Tivoli Management Services Discovery Library Adapter
- Use the z/OS Tivoli Management Services Discovery Library Adapter
- MIB SNMP agent event descriptions
- Agent operation log
- Support information
- Reference Guides
- Command Reference
- Messages Guide
- Troubleshooting Guide
- Accessibility
- Documentation library
- IBM Tivoli Monitoring library
- Documentation for the base agents
- Related publications
- Tivoli Monitoring community on Service Management Connect
- Other sources of documentation
- Glossary