IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Tivoli Common Reporting

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

---

Prerequisites for Tivoli Common Reporting

These are the prerequisite components for installing and running Tivoli Common Reporting packages in Tivoli Monitoring products.

To use the reports, you need the following components:

• IBM Tivoli Monitoring
  

• Tivoli Common Reporting

  IBM Tivoli Monitoring Version 6.3 Fix Pack 2 includes Tivoli Common Reporting Version 3.1.0.1, which is a component of Jazz for Service Management.

  The reports for the IBM Tivoli Monitoring Version 6.3 operating system agents, can be installed with Tivoli Common Reporting Version 3.1 or 2.1.1. (Tivoli Common Reporting Version 2.1.1 is provided with IBM Tivoli Monitoring Version 6.2.3.) For other monitoring agents, see the agent's user guide to determine the supported versions of Tivoli Common Reporting.

  If you want to upgrade an existing version of Tivoli Common Reporting Version 2.x to Version 3.1 or higher, the upgrade is a side-by-side process that results in two instances of Tivoli Common Reporting in your environment. You can remove the earlier version after you finish setting up Tivoli Common Reporting Version 3.1 or higher. If you want to migrate reports, including any custom reports or report scheduling, from the earlier version of Tivoli Common Reporting into the latest version, you must migrate the reporting data before installing the latest monitoring agent reports into Tivoli Common Reporting Version 3.1 or higher.

  If you have not done so already, install and configure Tivoli Common Reporting, using the information found in one of the following information centers:

  • "Installing Tivoli Common Reporting" topic in the Tivoli Common Reporting Information Center for Tivoli Common Reporting Version 2.1.1

  • "Installing Tivoli Common Reporting" topic in the Jazz for Service Management Information Center for Tivoli Common Reporting Version 3.1 or higher

  To ensure that Tivoli Common Reporting is running, go to http://computer_name:port_number/ibm/console/. The default port number for http is 16310 and for https is 16311. The default path to the server is /ibm/console. However, this path is configurable, and might differ from the default in your environment.

  If you already have an earlier version of Tivoli Common Reporting and you install a newer version in a different directory on the same computer system, the port assignment is different to avoid a conflict.

• Report packages

  Your product might have a separate reports package that must be extracted. See your product user's guide for instructions. This does not apply to the OS Agent reports, which are extracted as part of their installation.

  If you upgraded Tivoli Common Reporting to Version 3.1 or higher and you want to migrate reports, including any custom reports or report scheduling, from the earlier version of Tivoli Common Reporting into the latest version, you must migrate the reporting data before installing the latest monitoring agent reports into Tivoli Common Reporting Version 3.1 or higher. For instructions on how to export report packages from the earlier version of Tivoli Common Reporting and import the packages into the latest version of Tivoli Common Reporting, see the "Installing Jazz for Service Management" topic in the Jazz for Service Management Information Center.

• Historical data stored in a database manager product supported by IBM Tivoli Monitoring. For more information about supported databases, refer to "Supported databases for the Tivoli Data Warehouse" in the IBM Tivoli Monitoring Installation and Setup Guide.
  

• For the IBM Tivoli Monitoring agent reports Cognos package, refer your monitoring agent user's guide for report details. For more information on the operating system agent reports, see Operating System Agent Documentation. The documentation contains the required views for each report. If these views are not present, the report might not work. In order to ensure that the required views are present, run the following query against the Tivoli Data Warehouse:

  • DB2

    select distinct "VIEWNAME" from SYSCAT.VIEWS where "VIEWNAME" like '%V'

  • Oracle

    select distinct "VIEW_NAME" from USER_VIEWS where "VIEW_NAME" like '%V'

  • MS SQL Server

    select distinct "NAME" from SYS.VIEWS where "NAME" like '%V'

  In Tivoli Common Reporting, both BIRT and Cognos report engines can co-exist.

Parent topic:

Tivoli Common Reporting

---

+

Search Tips   |   Advanced Search