Configuration - IBM Tivoli Monitoring

1. Populate the agent depot
   • Populate the agent depot from the installation image
     • Windows
     • Linux/UNIX

   • Populate the agent depot with the tacmd addBundles command
     • Change the location of the agent depot

   • Manage the agent depot
   • Sharing an agent depot across your environment

2. Deploy OS agents
   • Requirements for the tacmd createNode command
   • Use the tacmd createNode command

3. Deploy non-OS agents
   • Deploy through portal
   • Deploy through command-line

4. Deploy Netcool/OMNIbus System Service Monitor (SSM) agents
   • Install an SSM agent
   • Uninstall an SSM agent
   • Install an SSM patch
   • Uninstall an SSM patch
   • Start an SSM agent
   • Stopping an SSM agent
   • Restarting an SSM agent
   • Configure an SSM agent
   • Bulk deployment of NetCool SSM agents
   • Query deployment status of Netcool SSM agents

5. Bulk agent deployment
   • Deployment processing model
   • Deploy status
     • Deployment Status workspaces
     • Deployment attribute groups and situations

   • Organizing deployments using groups
     • Deploy groups
       • Deploy groups best practices

     • Bundle groups
       • Bundle groups best practices

     • Group properties

   • Best-practice deployment procedures
     • Deployment planning and preparation
     • Deployment

6. Work with non-agent bundles
   • Deploy a non-agent bundle
   • Update a non-agent bundle
   • Remove a non-agent bundle

7. Run deployment in a Hot Standby environment
8. Self-describing agent installation
   • Manage your self-describing agent installations
     • Specify products and versions installed on monitoring server and portal server by automatic self-describing agent process

   • Terminal self-describing agent installation errors
     • Retrying the self-describing agent installation

   • Enable or disable self-describing agent capability

9. Monitor your operating system via a System Monitor Agent
   • Install the System Monitor Agent on Windows systems
   • Configure the System Monitor Agents on Windows
   • Uninstall the Windows System Monitor Agent
   • Install the System Monitor Agent on Linux or UNIX systems
   • Contents of the silent response file
   • Configure the System Monitor Agents on Linux or UNIX
   • Uninstall the Linux or UNIX System Monitor Agent
   • Define common configuration parameters: accessing centralized configuration information

10. Configure IBM Tivoli Monitoring components
    • Start Manage Tivoli Enterprise Monitoring Services
      • Start Manage Tivoli Enterprise Monitoring Services on Windows computers
      • Start Manage Tivoli Enterprise Monitoring Services on Linux or UNIX computers

    • Change the configuration of the Tivoli Enterprise Monitoring Server
    • Configure or changing the Tivoli Enterprise Monitoring Automation Server connection
      • Configure or changing the monitoring server connection for agents
      • Configure the handling of pure events by the monitoring server

    • Configure AIX, Solaris, HP-UX, and Linux monitoring components for IPv6 communication
    • Configure Windows monitoring components for IPv6 communication
    • Start and stop components
    • Specify network interfaces
    • Control port number assignments
      • Configure port number assignments for the monitoring server
      • Configure port number assignments for the monitoring automation server
      • Configure port number assignments for the portal server
        • Change the port number for the IBM Tivoli Monitoring Service Console
        • Change the port number for desktop client connections to the portal server

      • Configure port number assignments for monitoring agents
        • Add the KDE_TRANSPORT environment variable

    • Configure the heartbeat interval
    • Restarting the Tivoli Enterprise Portal Server after reconfiguration
    • Verify the dashboard data provider is enabled
    • Switching to a different Tivoli Enterprise Portal Server database
    • Silent configuration of the Performance Analyzer
    • Configure historical data collection for the Performance Analyzer warehouse agent
    • Tivoli Monitoring protocol usage and protocol modifiers
      • KDE_TRANSPORT Structure
      • KDE_TRANSPORT Transmission Control Protocol
      • PORT
      • SKIP and COUNT
      • EPHEMERAL
      • POOL
      • KDE_TRANSPORT User Datagram protocol
      • KDE_TRANSPORT Hypertext Transfer Protocol
      • How to change KDE_TRANSPORT settings

11. Additional Linux and UNIX configuration steps
    • Disable fsync() calls
    • Configure permissions for a monitoring server on a non-NIS Solaris computer
    • Linux requirements for the localhost host name
    • Set ulimit values for the Warehouse Proxy Agent

12. Additional Tivoli Enterprise Portal configurations
    • Connecting the Tivoli Enterprise Portal Server on Windows to a different monitoring server
    • Use SSL between the portal server and the client
      • Enable and disabling SSL for the Tivoli Enterprise Portal Server
      • Disable SSL

    • Reverting from the IBM HTTP Server to the internal web server
      • Portal server
      • Browser client
      • Desktop client
      • Web Start client

    • Configure HTTP communication between the portal client and server
      • Browser client
      • Desktop client
      • Web Start client
      • Change the ports used by IHS

13. Performance tuning
    • Disable TCP-delayed acknowledgments on AIX systems
    • Tivoli Enterprise Monitoring Server
      • Tivoli Enterprise Monitoring Server tuning recommendations for large-scale environments

    • Avoid distributing unused situations
    • Check ulimit settings for open file descriptors (UNIX/Linux only)
    • Disable extra fsync() calls by specifying KLGCB_FSYNC_ENABLED=0 (UNIX/Linux only)
    • Minimize Tivoli Enterprise Monitoring Server shutdown time by specifying DELAY_STOP=1 (UNIX/Linux only)
    • Avoid storing short-term history data at the Tivoli Enterprise Monitoring Server, if possible
    • Tivoli Enterprise Monitoring agents
    • Agentless Monitoring
      • Adjust the thread pool size, refresh interval, and cache time-to-live parameters for your environment
      • To monitor many monitoring servers, spread the target monitoring servers across multiple process instances
      • Avoid collecting historical data for the KR2_WMI_Event_Log attribute group

    • Tivoli Enterprise Portal Server
      • Portal server parameter tuning
      • For environments with more than 10 events per minute, consider disabling the Event Assistant
      • Perform periodic table maintenance for Tivoli Enterprise Portal Server DB2 database tables

    • Tivoli Enterprise Portal client
      • Tuning the portal client JVM
      • Portal client parameter tuning
      • Avoid displaying a large number of events in the Situation Event Console

    • Tivoli Data Warehouse
      • For all but the simplest environments, database administrator skills are needed to manage the warehouse database
      • Historical data collection
      • Warehouse Proxy Agent
        • Warehouse Proxy internals
        • Tuning the Warehouse Proxy Agent on AIX and Linux systems
        • Use multiple Warehouse Proxy Agents
        • Check ulimit settings for open file descriptors (UNIX/Linux only)
        • Disable logging to the WAREHOUSELOG table and use trace to monitor Warehouse Proxy Agent export activity
        • If using DB2 for z/OS for Tivoli Data Warehouse database, increase the idle thread timeout parameter
        • Configuration parameter changes used in large-scale environments

      • Summarization and Pruning Agent
        • Number of worker threads
        • Set the maximum Java heap size
        • Enable more detailed trace in log files
        • Consider disabling shifts and vacations
        • Minimize the number of summarization intervals used
        • Set the max worker threads and max rows per transaction appropriately for your environment

      • Database tuning
      • Relational database design and performance tuning for DB2 Database servers

    • Terminology
    • Performance factors
      • Database design details
        • Table spaces
          • Performance and table space types
          • File system caching on a Windows system

        • Buffer pools
        • Logging
          • Circular logging
          • Log retain logging
          • Log performance

        • Database maintenance
          • REORG
          • RUNSTATS
          • REBIND
          • Dynamic SQL
          • Static SQL

      • Application design details
      • Hardware design and operating system usage
        • Memory
        • CPU
        • I/O
        • Calculating disk space for an application
        • Disk efficiency
        • Selecting disk drives
        • Parallel operations
        • Network

    • Tuning
      • Database manager configuration tuning
        • Parameters

      • Database configuration tuning
      • Buffer pools
      • Registry variables

    • Monitor tools
      • SNAPSHOT and EVENT monitors
        • SNAPSHOTs
        • DB2BATCH

    • Optimizing queries
      • Processing queries
      • Define custom queries

    • Optimizing situations

14. Tivoli Data Warehouse solutions
    • New in Version 6.3 Fix Pack 2
    • New in Version 6.3
    • Plan considerations for the Tivoli Data Warehouse
    • Estimate the required size of your database
      • Step 1: Determine the number of detailed records per day for each attribute group
      • Step 2: Determine the hard disk drive footprint for each attribute group
      • Step 3: Determine the amount of detailed data for each attribute group
      • Step 4: Calculate the amount of aggregate data for each attribute group
      • Step 5: Determine the estimated size of your database

    • Understanding the disk requirements for your database
    • Increase the size of your database (DB2 for Linux, UNIX, and Windows only)
    • Plan assumptions
      • Preliminary planning is complete
      • Environment assumptions
      • The data warehouse is remote from the portal server
      • Agent warehouse database upgrade

    • Firewall considerations for the Tivoli Data Warehouse
    • Compressing historical data transmission
    • Next steps
    • Summary of supported operating systems

15. Schema Publication Tool
    • Generate SQL for data warehouse tables
    • Use the schema publication tool in updated mode
    • Use the schema publication tool in migrate mode
    • Use the Schema Publication Tool for database compression

16. Tivoli Data Warehouse range partitioning
    • Specify range partitioned tables for the Warehouse Proxy Agent
    • Configuration parameters
    • Specify range partitioned tables for the Summarization and Pruning Agent
    • Configuration parameters
    • Specify range partitioned tables for the schema publication tool

17. Specify where tables and indices are created
    • Environment variables

18. Tivoli Data Warehouse solution using DB2 for Linux, UNIX, and Windows
    • Supported components
    • Prerequisite installation
    • Implementing a Tivoli Data Warehouse solution using DB2 for Linux, UNIX and Windows
      • Solution steps

    • Step 1: Create the Tivoli Data Warehouse database
      • Create the warehouse database on DB2 for Linux, UNIX and Windows
      • Create a warehouse user on Windows
      • Create a warehouse user on Linux or UNIX
      • Limit the authority of the warehouse user
      • Set database and instance configuration values
      • Activating the DB2 listeners on a UNIX DB2 server

    • Step 2: Install and configure communications for the Warehouse Proxy Agent
      • Cataloging a remote data warehouse
      • Configure an ODBC data source for a DB2 data warehouse
      • Configure a Warehouse Proxy Agent on Windows (ODBC connection)
      • Configure a Warehouse Proxy Agent on Linux or UNIX (JDBC connection)
      • Start the Warehouse Proxy Agent

    • Step 3: Configure communications between the Tivoli Enterprise Portal Server and the data warehouse
      • Configure a Windows portal server (ODBC connection)
      • Configure a Linux or AIX portal server (DB2 for Linux, UNIX and Windows CLI connection)
      • Start the portal server

    • Step 4: Install and configure communications for the Summarization and Pruning Agent
    • Step 5: Install and configure communications for the Tivoli Performance Analyzer
      • Configure an ODBC data source for a DB2 data warehouse
      • Configure Tivoli Performance Analyzer on Windows (ODBC connection)
      • Configure Tivoli Performance Analyzer on Linux or UNIX (JDBC connection)
      • Start Tivoli Performance Analyzer

19. Tivoli Data Warehouse solution using DB2 on z/OS
20. Tivoli Data Warehouse solution using Microsoft SQL Server
21. Tivoli Data Warehouse solution using Oracle
    • Supported components
    • Prerequisite installation
    • Implementing a Tivoli Data Warehouse solution using Oracle
      • Solution steps

    • Step 1: Create the Tivoli Data Warehouse database
      • Create the warehouse database on Oracle

    • Step 2: Install and configure communications for the Warehouse Proxy Agent
      • Create a TNS Service Name
      • Configure an ODBC data source for an Oracle data warehouse
      • Configure a Warehouse Proxy Agent on Windows (ODBC connection)
      • Configure a Warehouse Proxy Agent on Linux or UNIX (JDBC connection)
      • Start the Warehouse Proxy

    • Step 3: Configure communications between the Tivoli Enterprise Portal Server and the data warehouse
      • Configure a Windows portal server (ODBC connection)
      • Configure a Linux or AIX portal server (JDBC connection)
      • Start the portal server

    • Step 4: Install and configure communications for the Summarization and Pruning Agent
    • Step 5: Install and configure communications for Tivoli Performance Analyzer
      • Create a TNS Service Name
      • Configure an ODBC data source for an Oracle data warehouse
      • Configure a Tivoli Performance Analyzer on Windows (ODBC connection)
      • Configure Tivoli Performance Analyzer on Linux or UNIX (JDBC connection)
      • Start Tivoli Performance Analyzer

22. Tivoli Data Warehouse solutions: common procedures
    • Configure the Summarization and Pruning Agent (JDBC connection)
    • Configure the Warehouse Proxy Agent on Linux or UNIX: command-line procedure
    • Configure the Summarization and Pruning Agent on Linux or UNIX: command-line procedure
    • Start the Summarization and Pruning Agent
    • Install multiple Warehouse Proxy Agents
      • Set a permanent socket address for a proxy agent
      • Verify the configuration

    • Run the warehouse agents autonomously
      • Configure a Warehouse Proxy Agent to run autonomously
      • Configure a Summarization and Pruning Agent to run autonomously

    • Configure summarization and pruning without the Tivoli Enterprise Portal Server
      • Examples

    • Test the connection between the portal server and the Tivoli Data Warehouse
      • 1. Create the query
      • 2. Create a workspace
      • 3. Assign the query to the workspace

    • Tuning the performance of the Warehouse Proxy
      • Database initialization
      • Work queue
      • Connection pool
      • RPC threads and export requests
      • Timeout values

    • Configure the Warehouse Proxy Agent and Summarization and Pruning Agent using the new graphical interface
    • Install the Warehouse Proxy Agent and Summarization and Pruning Agent in silent mode, using the silent response file
    • Install the Warehouse Proxy Agent in silent mode on UNIX, using the silent response file
    • Install the Summarization and Pruning Agent in silent mode on UNIX, using the silent response file
    • Upgrade the Warehouse Proxy Agent and Summarization and Pruning Agent in silent mode, using the silent response file
    • Upgrade the Warehouse Proxy Agent and Summarization and Pruning Agent using remote deploy
    • Warehouse Proxy Agent silent install response file sample
    • Warehouse Proxy Agent silent config response file sample
    • Summarization and Pruning Agent silent install response file sample
    • Summarization and Pruning Agent silent config response file sample
    • Configure the Warehouse Proxy Agent using the Tivoli Enterprise Portal
    • Configure the Summarization and Pruning Agent using the Tivoli Enterprise Portal
    • Remotely starting and stopping the Warehouse Proxy Agent using the Tivoli Enterprise Portal
    • Remotely starting and stopping the Summarization and Pruning Agent using the Tivoli Enterprise Portal
    • Remotely deploying the Warehouse Proxy Agent
    • Remotely deploying the Summarization and Pruning Agent
    • WAREHOUSELOG and WAREHOUSEAGGREGLOG tables

23. Use Tivoli Common Reporting and monitoring agent reports
24. Integrate event management systems
25. Set up event forwarding to Netcool/OMNIbus
    • Architecture overview
      • Event behavior
      • IBM Tivoli Monitoring Event Synchronization component

    • Architecture scenarios
      • One hub Tivoli Enterprise Monitoring Server and one Netcool/OMNIbus ObjectServer
        • Installation and configuration

      • Multiple hub Tivoli Enterprise monitoring servers and one Netcool/OMNIbus ObjectServer
        • Installation and configuration

      • One hub Tivoli Enterprise Monitoring Server and multiple Netcool/OMNIbus ObjectServers
      • Installation and configuration
      • Multiple IBM Tivoli Monitoring agents and one Netcool/OMNIbus ObjectServer
        • Installation and configuration for agents sending events to the Netcool/OMNIbus Probe for Tivoli EIF
        • Installation and configuration if agents are sending events to the Netcool/OMNIbus Probe for SNMP

      • Netcool/OMNIbus Multitiered and High-availability Architecture
        • Installation and configuration

      • Integration with Tivoli Business Service Manager
        • Installation and configuration

    • Installation and configuration
      • Install the IBM Tivoli Monitoring Event Synchronization Component
      • Install from a wizard
      • Install from the command-line
      • Install from the command-line using a silent installation
      • Update the Netcool/OMNIbus ObjectServer with IBM Tivoli Monitoring attributes, tables, and triggers
        • Update gateways to map attributes
        • Update the bidirectional failover gateway to replicate tables
        • Update the OMNIbus database schema in the collection tier
        • Update the OMNIbus database schema on single-tier or aggregation tier ObjectServers
        • Change the default deduplication trigger
          • Change the default deduplication trigger using Netcool/OMNIbus Administrator
          • Use the nco_sql command to modify the deduplication trigger in environments without a bidirectional failover gateway
          • Use nco_sql to modify the agg_deduplication trigger in environments with a bidirectional failover gateway

        • Update the OMNIbus database schema in the display tier

      • Start and stop the IBM Tivoli Monitoring Situation Update Forwarder
      • Configure the Netcool/OMNIbus EIF probe
        • Update the rules files of the EIF probe
        • Customize the rules file

      • Configure the OMNIbus server for program execution from scripts
      • Configure the hub monitoring server to forward events
        • Control event forwarding rate

      • Verify installation and configuration
        • To verify unidirectional event flow:
        • To verify bidirectional event flow:

26. Upgrade from a previous installation of IBM Tivoli Monitoring and Netcool/OMNIbus integration
    • Upgrade the IBM Tivoli Monitoring Event Synchronization Component
    • Upgrade from a wizard
    • Upgrade existing IBM Tivoli Monitoring events to use new OMNIbus attributes
    • Replace the default deduplication trigger
    • Update the EIF Probe Rules

27. Customize Event Integration
    • Configure IBM Tivoli Monitoring Situation Update Forwarder event flow to OMNIbus
    • Change the configuration values of the IBM Tivoli Monitoring Situation Update Forwarder
    • Update the IBM Tivoli Monitoring Situation Forwarder to forward event status updates to additional monitoring servers
    • Customize how the IBM Tivoli Monitoring OMNIbus triggers handle event status updates from the monitoring servers
      • Configure acknowledgement expiration and resurface status update event behavior
      • Configure stop situation event behavior for pure situations
      • Edit the eventcmd procedure
      • Edit the writeitmcmd procedure

    • Change the default acknowledgment timeout used when sampled events are deleted or cleared in Netcool/OMNIbus
    • Edit the configuration parameters that the hub monitoring server uses to forward events
    • Specify which situations forward events to Netcool/OMNIbus
    • Convert from unidirectional architecture to bidirectional architecture
    • Customize event status processing behavior when agent switching is used or the agent goes offline
    • Create a Netcool/OMNIbus WebGUI tool to launch from WebGUI to the Tivoli Enterprise Portal

28. Understanding and Customizing the Event Contents
    • Default mapping of situation events to OMNIbus events
    • Generic mapping for agent-specific slots
    • Customize the list of OMNIbus attributes that are cached
    • Add event classes for new and updated agents to the MCS Attribute service used by the EIF Slot Customization function
    • Installation
    • About customizing the format of the event message attribute
    • Localize the event message attribute

29. Installation worksheets
    • Windows hub monitoring server worksheet
    • Windows Tivoli Enterprise Monitoring Automation Server worksheet
    • Linux or UNIX hub monitoring server installation worksheet
    • Linux or UNIX Tivoli Enterprise Monitoring Automation Server worksheet
    • Windows remote monitoring server worksheet
    • Linux or UNIX remote monitoring server installation worksheet
    • Windows portal server worksheet
    • Linux portal server worksheet
    • Generic Windows monitoring agent worksheet
    • Generic Linux or UNIX monitoring agent worksheet
    • Windows portal desktop client worksheet
    • Linux portal desktop client worksheet
    • Monitor server communications protocol details worksheet

30. Perform a silent installation of IBM Tivoli Monitoring
    • Create and using a Windows response file
      • Automatically creating agent response files on Windows
      • Run the silent installation from the command-line with parameters
      • Run the silent installation using SMS
      • Windows: Installing and configuring the Tivoli Enterprise Monitoring Automation Server in silent mode
      • Install the dashboard data provider in silent mode

    • Perform a silent installation on a Linux or UNIX computer
      • Install components with a response file
      • Configure components with a response file
      • Automatically creating agent response files on Linux or UNIX
      • Linux/UNIX: Installing and configuring the Tivoli Enterprise Monitoring Automation Server in silent mode
      • Install the dashboard data provider in silent mode

    • Perform a silent installation of software packages using IBM Installation Manager
      • Install or update software packages in silent mode
      • Install or update silently from authenticated repositories with IBM Installation Manager
      • Recording a response file
      • Agent data location

31. Firewalls
    • Determine which option to use
      • Flow of connection establishment
      • Permission at the firewall
      • Server address continuity
      • Number of internet zones

    • Basic (automatic) implementation
    • Implementation with ephemeral pipe
    • Implementation with partition files
      • Sample scenarios
        • Scenario 1: Hub monitoring server INSIDE and monitoring agents OUTSIDE
        • Scenario 2: Hub and remote monitoring servers INSIDE and monitoring agents OUTSIDE
        • Scenario 3: Hub monitoring server INSIDE, remote monitoring server and agents OUTSIDE

      • Windows: Editing the partition file
      • UNIX and Linux: Editing the partition file
      • Create the partition file manually
        • Sample partition file

    • Implementation with firewall gateway
      • Configuration
      • Activation
      • IPv4 Address Data
      • IPv6 Address Data
      • XML Document Structure
      • Warehouse Proxy Configuration
      • Example gateway configuration scenario

    • Firewall network address translation (NAT) or multiple network interface cards
      • Define a Tivoli Enterprise Portal Server interface on Windows
      • Define a Tivoli Enterprise Portal Server interface on Linux or UNIX

    • Firewall scenarios for Tivoli Enterprise Portal
    • Firewall gateway redundancy configurations

32. IBM Tivoli product, platform, and component codes

 

+

Search Tips   |   Advanced Search