Tivoli Monitoring, Version 6.2

Procedure

Complete the following steps to configure the Summarization and Pruning agent.

Note:
A Reload button is available on the configuration windows. Click Reload at any time during the procedure to restore the original settings.
  1. Log on to the computer where the Summarization and Pruning agent is installed and begin the configuration:
    1. Open the Manage Tivoli Enterprise™ Monitoring Services window:
      • On Windows, click StartProgramsIBM Tivoli MonitoringManage Tivoli Monitoring Services.
      • On Linux or UNIX, change to the install_dir/bin directory and run the following command:
        ./itmcmd manage [-h install_dir] 
        where install_dir is the installation directory for IBM Tivoli Monitoring. The default installation directory is /opt/IBM/ITM.
    2. Right-click Summarization and Pruning Agent.
    3. On Windows, click Configure Using Defaults. On Linux or UNIX, click Configure. If you are reconfiguring, click Reconfigure.
  2. Review the settings for the connection between the Summarization and Pruning agent and the hub Tivoli Enterprise Monitoring server. These settings were specified when the Summarization and Pruning agent was installed.
  3. When you are finished verifying or entering information about the hub monitoring server:

    A multi-tabbed configuration window is displayed with the Sources tab at the front.

    Figure 56 shows the configuration window for a Summarization and Pruning agent on Windows (with values displayed for a DB2 warehouse database). The configuration window for a Summarization and Pruning agent on Linux or UNIX is similar.

  4. Add the names and directory locations of the JDBC driver JAR files to the JDBC Drivers list box:
    1. On Linux or UNIX, use the scroll bar at the bottom of the window to display the Add and Delete buttons, which are located to the right of the JDBC Drivers list box.
    2. Click Add to display the file browser window. Navigate to the location of the driver files on this computer and select the Type 4 driver files for your database platform. See Table 99 for the names and default locations of the driver files to add.
    3. Click OK to close the browser window and add the JDBC driver files to the list.

    If you need to delete an entry from the list, select the entry and click Delete.

  5. In the Database field, select the database platform you are using for the Tivoli Data Warehouse from the drop-down list: DB2, SQL Server, or Oracle.

    The default values for the database platform you selected are displayed in the other text fields on the Sources tab.

  6. Change the default value displayed in the Warehouse URL field if it is not correct. The following table lists the default Tivoli® Data Warehouse URLs for the different database platforms:
    Table 100. Tivoli Data Warehouse URLs
    Database platform Warehouse URL
    IBM® DB2® jdbc:db2://localhost:60000/WAREHOUS
    Oracle jdbc:oracle:thin:@localhost:1521:WAREHOUS
    Microsoft SQL Server 2000 or SQL Server 2005 jdbc:sqlserver://localhost:1433;databaseName=WAREHOUS
  7. Verify the JDBC driver name, which is displayed in the Warehouse Driver field. (Note that the Warehouse Driver field displays the driver name, in contrast to the driver files that are listed in the JDBC Drivers field.)

    The following table lists the JDBC Type 4 driver names for each database platform:

    Table 101. JDBC driver names
    Database platform JDBC driver name
    IBM DB2 com.ibm.db2.jcc.DB2Driver
    Oracle oracle.jdbc.driver.OracleDriver
    Microsoft® SQL Server

    com.microsoft.sqlserver.jdbc.SQLServerDriver

    Note:
    This is the name of the 2005 SQL Driver. Do not use the SQL Server 2000 JDBC driver, even if the Tivoli Data Warehouse was created in Microsoft SQL 2000. (The name of the 2000 SQL driver was com.microsoft.jdbc.sqlserver.SQLServerDriver. Note the reversal of the string jdbc.sqlserver.)
  8. If necessary, change the entries in the Warehouse User and Warehouse Password fields to match the user name and password that were created for the Tivoli Data Warehouse. The default user name is itmuser and the default password is itmpswd1.
  9. In the TEP Server Host and TEP Server Port fields, enter the host name of the computer where the Tivoli Enterprise Portal Server is installed and the port number that it uses to communicate with the Tivoli Data Warehouse server.
  10. Click Test database connection to ensure you can communicate with the Tivoli Data Warehouse database.
  11. Select the Scheduling tab to specify when you want summarization and pruning to take place. You can schedule it to run on a fixed schedule or on a flexible schedule:
    Note:
    If you select Fixed, the Summarization and Pruning agent does not immediately perform any summarization or pruning when it starts. It performs summarization and pruning when it runs. It runs according to the schedule you specify on the Scheduling tab. If you select Flexible, the Summarization and Pruning agent runs once immediately after it is started and then at the interval you specified except during any black out times.
  12. Specify shift and vacation settings in the Work Days tab:

    When you enable and configure shifts, IBM Tivoli Monitoring produces three separate summarization reports:

    Similarly, when you enable and configure vacations, IBM Tivoli Monitoring produces three separate summarization reports:

    Complete the following steps to enable shifts, vacations, or both:

  13. Select the Log Parameters tab to set the intervals for log pruning:
  14. Specify additional summarization and pruning settings in the Additional Parameters tab:
    1. Specify the number of additional threads you want to use for handling summarization and pruning processing. The number of threads should be 2 * N, where N is the number of processors where the Summarization and Pruning agent is running. A higher number of threads can be used, depending on your database configuration and hardware.
    2. Specify the maximum rows that can be deleted in a single pruning transaction. Any positive integer is valid. The default is 1000. There is no value that indicates you want all rows deleted.

      If you increase the number of threads, you might consider increasing this value if your transaction log allows for it. The effective number of rows deleted per transaction is based on this value divided by the number of worker threads.

    3. Indicate a time zone for historical data from the Use timezone offset from drop down list.

      This field indicates which time zone to use when a user specifies a time period in a query for monitoring data.

      • Select Agent to use the time zone (or time zones) where the monitoring agents are located.
      • Select Warehouse to use the time zone where the Summarization and Pruning agent is located.
      Note:
      • Skip this field if the Summarization and Pruning agent and the monitoring agents that collect data are all in the same time zone.
      • If the Tivoli Data Warehouse and the Summarization and Pruning agent are in different time zones, the Warehouse choice indicates the time zone of the Summarization and Pruning agent, not the warehouse.
    4. Specify the age of the data you want summarized in the Summarize hourly data older than and Summarize daily data older than fields. The default is 1 for hourly data and 0 for daily data.
  15. Save your settings and close the window. Click Save to save your settings. On Windows, click Close to close the configuration window.



Feedback

[ Top of Page | Previous Page | Next Page | Contents | Index ]