Ibm tivoli common reporting

Ibm tivoli common reporting DEFAULT

Using the Power of IBM Tivoli Common Reporting to Make Smart Decisions: The Untold Story

  • CONNECT WITH US:

    Effective Reporting using Tivoli Common Reporting

    Suresh WilsonTechnology Manager - Prolifics

  • CONNECT WITH US:

    Agenda Reporting and its importance

    Basics of Tivoli Common Reporting

    Tivoli Data Warehouse

    TCR Data Model

    TCR - Components

    Live demo

    2

  • CONNECT WITH US:

    Speaker Introduction

    3

    Suresh WilsonTechnology Manager - Prolifics

    Technology Manager focusing on enterprise systems, cloud services, enterprise integration and performance management; focusing primarily on IBM WebSphere, Tivoli (CS&I) and Rational product lines.

  • CONNECT WITH US:

    Prolifics at a Glance

    4

    5-Years CompoundAnnual Growth Rate

    19%

    EmployeesWorldwide

    1,500

    Global PresenceUnited States, United Kingdom, Germany, India

    20+TechnologyAccelerators

    550+Technical

    Certifications

    Over 10 Technology and Solutions Awards since 2009

    including Business Agility, Customer Integration and Digital

    Experience, the first everBeacon Laureate for Business

    Agility

    Over 160 global customersare currently Fortune

    1000 companies

    Best-in-class architects andspecialty experts:

    BPM, Integration, Digital Experience, Security, Testing,

    Business Analytics and Enterprise Content Management

    End-to-End Project Expertise

    Rate of Repeat Engagements*

    91%

    Years inBusiness

    35+Offices

    14

    Awards

    Technology Expertise

    Fortune 1000

    *based on % revenue Source December 2013 internal revenue metrics

  • CONNECT WITH US:

    Collaborate and learn

    5

    Lets keep the session interactive..

    And lets learn something new

  • CONNECT WITH US:

    APM Core features

    Monitoring tools can (typically) provide:

    Real-time runtime status of servers and applications

    Ability to send alerts and notifications

    Integrate with ticketing or event management systems

    Ability to take automated actions

  • CONNECT WITH US:

    APM Reporting Why is it important? Wouldnt it be nice if the monitoring tool can also help in:

    Performing analytics

    Capacity planning

    Performance management

    Easily share performance and availability data

    Understanding SLA conformity

  • CONNECT WITH US:

    IBM Solutions and Reporting

    How does reporting work in the IBM APM world?

    Tool specific reporting (think TEPS, APM UI, SaaS APM UI etc.)

    Tivoli Common Reporting (for complete, feature-rich, customizable reporting)

    * TCR Integration in the IBM SaaS offering

  • CONNECT WITH US:

    Tivoli Common Reporting

    TCR is a shared reporting solution used by several IBM products

    Most APM agents provide ready to use out-of-the-box reports

    Based on the IBM Cognos BI software

    Integrated with Jazz for Service Management

  • CONNECT WITH US:

    Sample List of Out-of-the-Box Reports

    OS Reports

    SOA Reports

  • CONNECT WITH US:

    So, why are we having this session?Most APM customers

    Do not fully utilize the reporting features (or maybe uses out-of-the-box reports)

    Do not understand the power of Cognos BI

    And hence the objective is

    Understand how to use TCR from an APM user perspective

    Learn how to get more out of APM investment

  • CONNECT WITH US:

    Tivoli Common Reporting Data Flow

    TEPS Enable attributes for historical collection

    WPA Sends the real-time data to the warehouse

    SnP Define the summarization and pruning configuration

    JazzfSM

  • CONNECT WITH US:

    Tivoli Common Reporting Roles

    APM SME Application SME Cognos SME

    Enable/Optimize historical collection

    Manage APM configuration

    Determine which KPIs to report on

    Work with APM and Cognos SMEs to create efficient reports

    Create/Customize TCR Reports

    Add intelligence and user experience to reports

  • CONNECT WITH US:

    Tivoli Common Reporting Roles

    Or use that one person who can do it all

  • CONNECT WITH US:

    Effective Reports start with historical collection

  • CONNECT WITH US:

    Warehouse Filtering

    Enable the right attributes for historical warehouse collection

    1. Collect only the attributes necessary to meet the reporting requirements

    2. Use attributes filtering to minimize data collection and maximize value

    Example: WebSphere Request Analysis

  • CONNECT WITH US:

    Verify the data model

    TCR rely on the underlying data model to generate reports (comes with the APM agent reports)

    Verify the data model to make sure that it contains the correct attributes

    Use Cognos Framework Manager to make changes (only if needed)

  • CONNECT WITH US:

    Decide on how to visualize the data

    Understand the reporting requirements of the target audience

    Choose the correct reporting format

    Make the report customizable and extensible

    Make use of reporting workspaces

  • CONNECT WITH US:

    Key Reporting features

    Active Reports self contained reports, dynamic interaction

    Cognos Reporting Workspaces combine different reports to create custom reporting workspaces

    Numerous reporting formats to choose from

  • CONNECT WITH US:

    Sample reporting formats

  • CONNECT WITH US:

    APM Reporting DEMO

  • CONNECT WITH US:

    Sample reports

  • CONNECT WITH US:

    Sample reports

  • CONNECT WITH US:

    Learn More Prolifics at InterConnect

    24

    Monday How Broadcast Music, Inc. Devised and Enabled Enterprise Architecture from Corporate Strategy12:15 PM - 1:15 PM

    Integrating Salesforce.com and Oracle ERP Using IBM WebSphere Cast Iron2:00 PM - 3:00 PM

    Recommended Design Considerations for Enterprise Monitoring using SCAPM and Netcool OMNIbus5:00 PM - 6:00 PM

    Tuesday Smarter Integration Using the IBM SOA Foundation Stack: Best Practices and Lessons Learned8:00 AM - 9:00 AM

    Best Practices for Monitoring Your Cloud Environment and Applications9:30 AM - 10:30 AM

    Applicability of IBM SOA Approach In Manual Processes Automation 11:30 AM-11:50 AM

    Leveraging Governance in the IBM WebSphere Service Registry and Repository for IIB and DataPower12:30 PM - 1:30 PM

    Broadcast Music Inc. Release Rockstars: Program-Wide DevOpsSuccess with UrbanCode Deploy3:30 PM - 4:30 PM

    Empowering SmartCloud APM -Predictive Insights and Analysis: A Use Case Scenario5:30 PM - 6:30 PM

    Wednesday Architecting and Tuning IIB/eXtreme Scale for Maximum Performance and Reliability, Featuring TBC8:00 AM - 9:00 AM

    MasterCard's Modeling and Governance of Decisions and Processes for Improved Fraud11:00 AM - 12:00 PM

    How BMI is Revolutionizing the Music Business Using IBMs BPM and Integration Technology2:00 PM - 3:00 PM

    Integrating IBM Pure Application Systems and IBM UrbancodeDeploy: A GE Capital Case Study 2 :00 PM 3:00 PM

    Thursday Aetnas Vision for a Healthier World: Smarter Architecture and a Scalable Integration Bus9:00 AM - 10:00 AM

    Meet the Expert - Delivering Enterprise Applications: Faster. Cheaper. Better Thursday 12:00 PM 12:50 PM

    Using the Power of IBM Tivoli Common Reporting to Make Smart Decisions: The Untold Story2:30 PM - 3:30 PM

  • CONNECT WITH US:

    Thank You

    Your Feedback is Important!

    Access the InterConnect 2015 Conference CONNECT Attendee Portal to complete your session surveys from your smartphone, laptop or conference

    kiosk.

  • CONNECT WITH US:

    Lets Continue the Conversation.

    Suresh [email protected]

    Visit these useful links on the Prolifics website:Case Studies http://www.prolifics.com/resources/case-studiesWebcasts http://www.prolifics.com/resources/webcastsVideos http://www.prolifics.com/resources/videosSolution Briefs http://www.prolifics.com/resources/solution-briefsBlog http://www.prolifics.com/blogTwitter http://www.twitter.com/prolificsFacebook http://www.facebook.com/ProlificsTechProlifics TV http://www.youtube.com/prolificstv

  • Sours: https://cupdf.com/document/using-the-power-of-ibm-tivoli-common-reporting-to-make-smart-decisions-the-untold-story.html

    IBM Tivoli Common Reporting (TCR) pimC

    This page documents the enPortal integration for IBM Tivoli Common Reporting (TCR).

    If you are using portal version 5.4 or above please click here for the integration documentation applicable to it

    • Vendor: IBM
    • Product: Tivoli Common Reporting (TCR)
    • Supported Version(s): 2.1.1
    • Name of enPortal Integration Package: ibm.tcr_pimC
    • Required enPortal Version: 4.6.1 and above


    The following section documents supported platforms, installation, and configuration of the Tivoli Common Reporting (TCR) Product Integration Module on enPortal versions 4.6.1 and above.

    1. Support Matrix

    The following Operating System, Database, and Web Browser platforms are supported:

    1.1. Operating System

    Please see the list of supported Operating Systems on the System Requirements page.

    1.2. Database

    A special database is not required to implement this integration module. The AppBoard/enPortal database is used to store all configurations related to this integration module.

    1.3. Web Browser

    Please see the list of supported Web Browsers on the System Requirements page.

    2. Installation

    Perform the following steps to install the Tivoli Common Reporting (TCR) PIM:

    1. Install AppBoard/enPortal as detailed in the Installation documentation
    2. Download the file ibm.tcr_pimC.jar
    3. Start enPortal and login as a portal administrator
    4. Under the Advanced tab, select PIMImport
    5. Click the Browse... button
    6. Locate the file ibm.tcr_pimC.jar in the Open dialog
    7. Click the Start button to extract the files from the PIM .jar archive
    8. Under the Advanced tab, select XMLImport
    9. Click the Start button to load the PIM into the system
    10. Confirm that the following message is displayed: "Import completed; loaded the following file(s): load_ibm.tcr_pimC.txt"
    11. Under the Advanced tab, select Explore System
    12. Navigate to the /Directory/system/proxy/ folder and locate the “Manage Proxy” channel
    13. Right-click on the “Manage Proxy” channel and select Open to launch the channel
    14. In the Manage Proxy tool, click “Reset All”

    3. Integration Details

    The following sections provide special details for configuring the integration module after installation.

    3.1. Channel Types

    • Home - Channel that displays the default Home page for the logged in user, including full navigation controls (no custom configuration required)
    • Proxy - Channel that is used by the system to display Tivoli Common Reporting(TCR) channels (no custom configuration required)
    • TCR - A channel that displays the Tivoli Common Report entry page. ()
    • RunReport - A channel that allows a specific report to be run. (). Here are list of channel parameters:
      • ui.object: The path of a report object (for example: )
      • run.prompt: A flag to indicate whether to show prompt or not ()
      • ui.action: run, indicating to run a report
      • b_action: cognosViewer
      • run.outputFormat: The format of Report. The possible values are ()
    • ViewReport - A channel that displays a saved Report. Here are list of channel parameters:
      • ui.object: The path of a report object (for example: )
      • ui.name: The name of a report
      • ui.action: view, indicating to view a report
      • b_action: cognosViewer
      • run.outputFormat: The format of Report. The possible values are ()
    • QueryStudio - A channel that launches Query Studio

    3.2. Configuration

    After installing the Tivoli Common Reporting (TCR) PIM, perform the following steps to configure access to the host Tivoli Common Reporting (TCR) server:

    1. Click on the Applications tab
    2. Right-click on the name sample in the row for Tivoli Common Reporting (TCR) (ibm.tcr_pimC) and select Modify
    3. Fill in the items in the Modify Application Wizard dialog:
      1. Select the protocol used to access your Tivoli Common Reporting (TCR) server (http or https)
      2. Change the host name from "changeme" to the hostname or ip address that will resolve to your Tivoli Common Reporting (TCR) server
      3. Change the port to the port number of your Tivoli Common Reporting (TCR) server
      4. Click "Save" to keep your changes
    4. Click on the Integrations tab
    5. In the Explorer, under Packages, expand the cuculus.zonoscontrolcenter_pimA tree and click on the sample target. Confirm that the information you entered is displayed for your Tivoli Common Reporting (TCR) server
    6. Under the sample target, click on the Home channel. A login prompt should be displayed.
    7. Log in using the same credentials you would use for accessing the Tivoli Common Reporting (TCR) application in a browser. Confirm that the Tivoli Common Reporting (TCR) Home page is displayed.

    3.3. Create Channels

    After installing the Tivoli Common Reporting (TCR) PIM and configuring access to the host Tivoli Common Reporting (TCR) server, perform the following steps to create channels to display Tivoli Common Reporting (TCR) content:

    1. Click on the Applications tab
    2. Right-click on the name "sample" in the row for ibm.tcr_pimC and select a channel type
    3. In the "Channel Name" box, enter the name you want to give to the new channel
    4. For "Channel Type", select "3rd Party Pims"
    5. Select Pim, Class, and Target for your channel
    6. Click Next
    7. Click Finish
    8. Click on the Integrations tab
    9. In the Explorer, under Packages, expand the ibm.tcr_pimC tree and click on the sample target. Confirm that the new channel is listed along with the other sample channels

    Repeat the above steps to create additional channels. Select a different Channel Type in step 2 to create a different type of channel.

    3.4. Known Issues

    The following known issues are associated with this PIM:

    • There are currently not any known issues associated with this PIM

    3.5. License Usage

    In order for the AppBoard/enPortal administrator to configure the ibm.tcr_pimC PIM, the AppBoard/enPortal license.properties file must include licensing for at least one ibm.tcr_pimC server. The administrator can create one additional host ("target") in AppBoard/enPortal for each server license included in the license file.

    Each AppBoard/enPortal user maintains one user session with the Tivoli Common Reporting (TCR) server. The Tivoli Common Reporting (TCR) application must be licensed to support the number of users that will be accessing the application through AppBoard/enPortal.

    3.6. Version Support

    The following matrix details the supported Tivoli Common Reporting (TCR) and compatible AppBoard/enPortal versions:

    Package Name enPortal Version Tivoli Common Reporting (TCR) Supported Versions
    ibm.tcr_pimC 4.6.1+ 2.1.1

    To see the current enPortal version, run the command from the directory.

    4. Upgrades

    4.1. Upgrading from an older version

    Older versions of Tivoli Common Reporting (TCR) are not supported by this PIM, so this upgrade path is not supported. It is recommended that you validate the PIM in your Tivoli Common Reporting (TCR) environment to confirm that it supports the required functionalities.

    4.2. Upgrading to a newer version

    Perform the following steps when the Tivoli Common Reporting (TCR) server is upgraded to a newer version of Tivoli Common Reporting (TCR):

    1. Check the AppBoard/enPortal PIM online documentation to see if the new Tivoli Common Reporting (TCR) version is supported by the existing ibm.tcr_pimC PIM.
    2. Test if the new Tivoli Common Reporting (TCR) version is supported by the existing PIM that you have installed, perform the following steps:
      1. Click on the Applications tab
      2. Right-click on the row for the old Tivoli Common Reporting (TCR) server and select "Modify"
      3. Update the protocol, host, and port to reference the server where the new version of Tivoli Common Reporting (TCR) is running
    3. If the new Tivoli Common Reporting (TCR) version is not supported by the existing PIM that you have installed, perform the following steps to upgrade the PIM:
      1. Download the new PIM version from the PIM download site
      2. Follow the steps in the Installation section above to install and configure the new PIM version
      3. Re-create all Tivoli Common Reporting (TCR) channels to reference the new PIM
      4. [Optional] Perform the steps outlined in the Uninstall section below to remove the old PIM from the system

    5. Uninstall

    Perform the following steps to uninstall the ibm.tcr_pimC PIM:

    Uninstalling the ibm.tcr_pimC PIM will break all of the channels in your AppBoard/enPortal system that reference this integration.

    1. Click on the Integrations tab
    2. In the Explorer, under Packages, locate the ibm.tcr_pimC integration
    3. Right click on the integration name, and select "Delete"
    4. Click "Ok" to confirm that you want to delete the integration package


    What Links Here|

    Sours: https://ab.edge-technologies.com/edge-docs/index.php?title=integrations/ibm/ibm.tcr_pimC&oldid=5558
    1. Wedding program design ideas
    2. Baby driver minimalist poster
    3. Family tree collage ideas
    4. 2016 jeep wrangler exhaust

    We had to move the Tivoli Common Reporting Content store database. Both database DB2 servers are the same OS and same DB2 version otherwise this method is not working!

    To move the database from the old server to the new one we did the following steps:

    • Backup old database ( backup database cognos )
    • Copy backup file to new server ( scp … )
    • Restore database on new server ( restore database cognos to /app/db2db )
    • create tcradmin user on new server and assign required db2 rights.

    I spent about an hour googling where these database settings are stored with no success so finally I decided to find the configuration file myself. The database connection parameters are stored in cogstartup.xml file in the cognos configuration directory. We have changed the following parameter:

    <crn:parameter name=”server”>
    <crn:value xsi:type=”cfg:hostPort”>x.x.x.54:50001</crn:value>
    </crn:parameter>

    to

    <crn:parameter name=”server”>
    <crn:value xsi:type=”cfg:hostPort”>x.x.x.53:50001</crn:value>
    </crn:parameter>

    After restarting Jazz the cognos is now connected to the new database server.

    This entry was posted in DB2, Tivoli Common Reporting on by admin. Sours: https://www.solutioning.eu/category/tivoli-common-reporting/

    1 Introduction to Tivoli Common Reporting v3 Gil Arnold, IBM TCR Release Manager Dan Krissell, IBM TCR Architect

    2 Tivoli Common Reporting TCR is a feature that ships as an add-on to 60+ Tivoli licensed products (catalog link) Works with standard, out of the box Tivoli product reports that visualize key metrics and trends Helps you leverage your Tivoli data to show history and trends and answer questions like Which of my servers are under- and over-utilized in CPU, disk or memory? What is my server inventory by manufacturer? Includes both Cognos and BIRT report engines; standard report templates for Tivoli Highly active in the field supporting >3,000 customers TCR ecosystem includes active community on SMC Connect forums, videos, articles plus report templates, report catalog, documentation, courseware, and IBM support system Starting with V3, TCR leverages database, middleware, and UI services of JazzSM to provide a complete set of Reporting Services 2

    3 How do I know what product reports are available? Check the TCR report catalog: Check the TCR Report Catalog 3

    4 History of TCR 1.1 June Oct Oct Mar Dec 2010 TCR Q Q Mobile report (ipad) 4

    5 TCR V3.1 Overview TCR V3.1 became generally available March 8, 2013 with ITM 6.3 Other Tivoli products will adopt and support TCR V3 over time Reporting Workspace New version leverages services from Jazz SM including DB2, WAS, DASH, Admin Services Leverages Cognos 10.2 improvements Cross-Product Reporting Workspaces Mobile support Active Reports New/faster reporting engine with JDBC Eventing support Search across saved reports Trending lines (moving average etc.) Improved authoring tools Active Report Mobile Reports 5

    6 TCR V3 Key Enhancements Active reports Reports can have offline interactivity; more usable and engaging Reporting Workspaces Customers can drag and drop reports into a workspace Flat File support - Join flat file data to product data via web interface; easier for customers to integrate their data with Tivoli s Mobile add-on View, run, administer reports from ipad or other mobile device JDBC support - Simplifies configuration of back-end database Improved performance: New reporting engine provides optimized SQL generation Report eventing Automation rules around reporting For example, a report to help desk when performance degrades Integrated Indexed Search Search all reporting artifacts For example, look for a system name among saved reports More scalable with a DB2 out of the box content store 6

    7 Active Reports Interact with reports without the need for server requests. This means reports can be ed with interactive features. No coding required Clickable charts, sorting, radio button, tabs, cascading lists, checkbox filtering,...

    8 Reporting Workspaces Drag and drop pieces from different reports to create a workspace with reporting content Free form layout Add interactivity

    9 More Chart Selection and Updated Look & Feel

    10 Trending Help users make conclusions from the data with trend lines Add trending with just a few clicks Average across series or for each series Available in bar, line, area, bubble, and scatter charts

    11 Mobile View and run reports Mobile web support for most devices, including ipad, iphone, Android, Blackberry & Windows App for ipad, along with native app for Blackberry Interact with Active Reports offline with the ipad app On demand or schedule content to be delivered to user devices, sync via or directly to the server Formatted for mobile devices; utilize native device interactions and gestures (swipe, zoom, controls, etc)

    12 More Powerful Self-Service Ad hoc Reporting Multi-query ad hoc - As you drag and drop, the report is updated Bridge the gap between business users and professional authors Cross Compatibility with Report Studio Easily modify format and layout Resize widgets with a drag Filter data with a few clicks More charting options Trend lines

    13 Other Major Features Dynamic Query Mode New Java-based reporting engine means: Decrease time to value with JDBC support (DB2, Oracle, MSSQL, Netezza) Optimized SQL generation of complex queries Out of the box DB2 as the Content Store Prereq reports Check the database to be sure it s ready for reporting Event Studio Automation rules around reporting For example, instead of ing a report daily for someone to parse, only reports when a data meets criteria Integrated Indexed Search Search all reporting artifacts For example, look for a system name among saved reports

    14 Resources TCR DeveloperWorks: Frequently updated with new articles Check the report catalog for updates Message boards & new videos Free class: TCR Fundamentals ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=course_description&includeNotScheduled=y&cour secode=tos33 3 hours Topics include: Creating reports with charts, filters, prompts, graphics Admin tasks such as import reports, configuring data sources, LDAP integration How to interpret a data model Cognos Proven Practices Advanced topics

    15 Packaging TCR does not have a product ID or eassembly Instead it s the reporting service within the new Jazz for Service Management integration platform Products package the Jazz for Service Management media

    16 Jazz For Service Management An open & flexible architecture designed to enable simplified integration of multi-vendor tools for improved visibility, control and automation. VISIBILITY CONTROL AUTOMATION Directly access trusted, multi-vendor data from any source Visualize trusted, multi-vendor data from any source Easily plug in or swap out multi-vendor tools Integrate multi-vendor tools at a fraction of time/cost Develop integrations once and reuse them many times Stop reworking integrations with every point release Leverage open services to speed multi-vendor integration Linked Data OSLC Specifications Open Services Registry Security Reporting Administration Visualization

    17 Where To Find More Info 17

    18 Tivoli Common Reporting Community News Follow TCR news and interact with other users at mmunityview?communityuuid=9caf63c9-15a1-4a03-96b3-8fc700f3a364 (or use your search engine to find: Tivoli Common Reporting) How-to videos Catalogue of reports to download Tips and techniques Forums for general and specific help Sample style guide for consistent report layout 18

    19 Education First stop: TCR Website Videos including TCR introduction ITM reporting demo Importing reports Creating a data model Customizing a report Ad Hoc reporting Featured articles including Field Guide to TCR (a good place to start) Setting up TCR TCR High Availability configuration Setting up security Start at nityview?communityuuid=9caf63c9-15a1-4a03-96b3-8fc700f3a364 Or just Google Tivoli Reporting

    20 Formal Training For advanced training, see Cognos BI courses on Query Studio Report Studio Framework Manager For TCR 1.3 and 2.x, follow the Cognos BI 8.4 track For TCR V3, use Cognos BI 10.2 Start at 03.ibm.com/services/learning/ites.wss/us/en?pageTyp e=page&c=w113304m84371i29

    21 Jazz for Service Management Part Numbers (to get TCR 3.1) Jazz for Service Management 1.1 QuickStart eimage CIES8ML Jazz for Service Management 1.1 for AIX ML (Launchpad, PRS, Jazz Repository, TDI) CIER6ML Jazz for Service Management 1.1 for Linux ML (Launchpad, PRS, Jazz Repository, TDI) CIER7ML Jazz for Service Management 1.1 for Linux on System z ML (Launchpad, PRS, Jazz Repository, TDI) CIER8ML Jazz for Service Management 1.1 for Windows ML (Launchpad, PRS, Jazz Repository, TDI) CIER9ML IBM Tivoli Common Reporting 3.1 for AIX Multilingual IBM Tivoli Common Reporting 3.1 for Linux Multilingual IBM Tivoli Common Reporting 3.1 for Linux on System z Multilingual IBM Tivoli Common Reporting 3.1 for Windows Multilingual IBM Tivoli Common Reporting 3.1 Cognos Framework Manager Windows Multilingual CIES0ML CIES1ML CIES2ML CIES3ML CIES4ML IBM WebSphere Application Server V for Jazz for Service Management for AIX ML CIES5ML IBM WebSphere Application Server V for Jazz for Service Management for Linux ML CIES6ML IBM WebSphere Application Server V for Jazz for Service Management for Linux on System z CIES7ML IBM WebSphere Application Server V for Jazz for Service Management for Windows ML CIFS5ML IBM DB2 10.1, Enterprise Server Edition - Restricted Use - Quick Start and Activation CI71NML IBM DB2 Enterprise Server Edition for 64-bit AIX CI6W9ML IBM DB2 Enterprise Server Edition for Linux on AMD64 and Intel EM64T systems (x64) CI6W6ML IBM DB2 Enterprise Server Edition for Linux on System z CI6W7ML IBM DB2 Enterprise Server Edition for Windows on AMD64 and Intel EM64T systems (x64) CI6WEML IBM DB2 10.1, National Language Pack for AIX CI71QML IBM DB2 10.1, National Language Pack for Linux on AMD64 & Intel EM64T systems x64 CI71VML IBM DB2 10.1, National Language Pack for Linux on System z CI71XML

    22 TCR Part Numbers: IBM Tivoli Common Reporting for Windows 32 Bit Multilingual IBM Tivoli Common Reporting Windows 64 Bit Multilingual IBM Tivoli Common Reporting Linux 32 Bit Multilingual IBM Tivoli Common Reporting Linux 64 Bit Multilingual IBM Tivoli Common Reporting AIX 32 Bit Multilingual IBM Tivoli Common Reporting AIX 64 Bit Multilingual IBM Tivoli Common Reporting HP-UX 32 Bit Multilingual IBM Tivoli Common Reporting HP-UX 64 Bit Multilingual IBM Tivoli Common Reporting Solaris 32 Bit Multilingual IBM Tivoli Common Reporting Solaris 64 Bit Multilingual IBM Tivoli Common Reporting Linux on System z 32 Bit Multilingual IBM Tivoli Common Reporting Linux on System z 64 Bit Multilingual IBM Tivoli Common Reporting Cognos Framework Manager Multiplatform Multilingual CZZM7ML CI01HML CZZM8ML CI01JML CZZM9ML CI01KML CZZN0ML CI01NML CZZN1ML CI01LML CZZN2ML CI01MML CZZN3ML Reports are packaged either with the respective products, or downloadable via ISM. Report Catalog: 3e/page/Report%20Catalog?lang=en

    23 TCR Part Numbers: 2.1 IBM Tivoli Common Reporting Version 2.1 Windows Multilingual IBM Tivoli Common Reporting Version 2.1 Linux Multilingual IBM Tivoli Common Reporting Version 2.1 AIX Multilingual IBM Tivoli Common Reporting Version 2.1 HP-UX Multilingual IBM Tivoli Common Reporting Version 2.1 Solaris Multilingual IBM Tivoli Common Reporting Version 2.1 Linux on System z Multilingual CZQ7ZML CZQ80ML CZQ81ML CZQ82ML CZQ83ML CZQ84ML Cognos Framework Manager for IBM Tivoli Common Reporting Version 2.1 Windows Multilingual CZUR5ML

    Sours: https://docplayer.net/10960427-Introduction-to-tivoli-common-reporting-v3.html

    Reporting ibm tivoli common

    A head start on Tivoli Common Reporting and Cognos

    I've just started working with Tivoli Common Reporting 2.1.1 using cognos.

    Already installed the TCR and configured a datasource to a db2 database by going to: Reporting-Work with reports-Connection-Configuration-Ds connections.

    I want to make a small test report connecting to that data base but since I am new to this technology I don't know how to.

    Read somewhere that I need to have Framework Manager to create a model and then use Report or Query studio to create a report using that model. Can anyone help me by guiding me on how to start making this first test report?

    From these I am assuming I need this framework, then I have to configure something in that software to point to my db2 then create something of a model. Then use report or query to handle this model and create a report. I've been reading manuals for a few days but can't seem to get it working otherwise. Is there anyway to get already made reports and configure them to use my db without using framework manager? since I think framework only works in windows and I installed it in a SUSE.

    Sours: https://stackoverflow.com/questions/12354649/a-head-start-on-tivoli-common-reporting-and-cognos
    Tivoli Common Reporting Overview

    Tivoli Common Reporting 2.1.1

  • 2012 IBM Corp.

    Unit

    Tivoli Common Reporting architecture and overview

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 2

    Objectives When you complete this unit, you can perform the following tasks:

    Define Tivoli Common Reporting Distinguish between placement and function of the components:

    Tivoli Integrated Portal Tivoli Common Reporting Cognos report engine

    Describe the deployment general architecture Show how to use Tivoli Common Reporting to produce reports Detail current resources for more exploration TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 3

    Tivoli Common Reporting Tivoli Common Reporting is a common component that is shared across Tivoli.

    It adds value to Tivoli solutions by simplifying how information is visualized and shared through Cognos Connection.

    Is deployed with more than 50 Tivoli products Includes standard, ready-to-use Tivoli product reports for viewing key metrics and trends Includes both Cognos and BIRT report engines

    Customized reports through a drag-and-drop web-based editor

    Single user interface for all report formats, which means common scheduling, security, and administration

    Reports by email or for later viewing

    Output in HTML, PDF, Excel, XML, or CSV

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 4

    Produce reports in many formats from a consistent interface

    Throughput, such as network traffic or call volume

    Device, network, or resource availability Status of key performance indicators Server or system performance

    Utilization Capacity Trends

    Data that is collected from potentially any Tivoli product Detail or summarized historical data, real-time data in some

    cases

    Historical Tivoli data to answer questions such as: Which servers are under- and over-utilized in CPU, disk, or

    memory What is the server inventory by manufacturer Are there more traffic or usage spikes at regular times

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 5

    Components of Tivoli Common Reporting (simplified view)

    Tivoli Integrated Portal (embedded WebSphere Application Server)

    Tivoli Business Service Manager

    Tivoli Common Reporting

    Netcool/Impact

    Some applications that run in Tivoli Integrated Portal

    User interface

    Report selection

    Scheduling

    Running, printing, emailing, saving reports

    Cognos Business Intelligence server Reporting engine Report creation and editing tools

    Data sources Content store Single computer installation

    Distributed installation

    Existing Cognos BI instance

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 6

    Starting the Tivoli Integrated Portal

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 7

    Working with report packages

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 8

    Overview of the user interface

    Open the reporting page

    Click a report name to view a saved report or run the report Run with options: Other

    formats such as PDF or XLS; delivery mechanisms such as email or save in Tivoli Common Reporting

    Schedule the report for a later time

    Jobs: Schedule in batch TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 9

    IBM Tivoli Monitoring for Virtual Environments 7.1 IBM Tivoli Monitoring (One-minute report)

    Tivoli Application Dependency Discovery Manager 7.2.1

    Report examples

    Clickable links to drill down TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 10

    Tivoli products with Cognos reports Go to http://ibm.co/xhkDRC

    Click the Report Catalog icon

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 11

    How to use Tivoli Common Reporting

    Import reports and organize

    them

    Run live reports

    Schedule reports for viewing later

    Distribute reports to

    users

    Get reports from your

    Tivoli product

    Create your own reports

    1

    2

    3

    4

    Connect to the product

    data source, such as

    Tivoli Data Warehouse

    5

    1 TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 12

    Report designing tools

    Report Studio Starts from the user interface or in context from a report Opens in a new browser

    Query Studio Starts and runs in the Tivoli Integrated Portal user interface

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 13

    Cognos data model Source of the drag-and-drop report

    creation

    Business view of database tables Abstraction of complex relationships and

    content

    Computed attributes, filters, shortcuts Multiple options for securing reports Model that is created and maintained by

    using Framework Manager Requires Windows OS

    Query model

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 14

    Value of Tivoli Common Reporting Ready-to-use reports that are provided by Tivoli product developers

    No SQL or other programming necessary

    Report Studio to create sophisticated reports or edit product-provided reports Start web-based Report Studio in context from a report

    o You can run a provided report, like an IBM Tivoli Monitoring report, and start the editor in context to change something

    Query Studio provides ad hoc reporting Create reports with tables and charts

    o Novice users can create reports with intuitive dragging function by using the Query Studio for greater report use with little training

    Other capabilities Automatic emailing of reports Additional report formats

    o PDF and XML o Excel 2000 and 2000 Single Sheet, 2002, and 2007 o Comma-separated values (CSV)

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 15

    More resources You Tube videos

    Search for Tivoli Common Reporting o Videos with dates older than 2011 are probably about BIRT reports, not Cognos

    IBM Integrated Service Management Library https://www-304.ibm.com/software/brandcatalog/ismlibrary/

    Formerly Open Process Automation Library (OPAL) Tivoli-provided report packages for numerous products

    IBM developerWorks http://www.ibm.com/developerworks/spaces/tcr

    Best practices White papers Instructional videos

    Tivoli Common Reporting InfoCenter Product documentation and guidance

    o http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp

    TTE

  • 2012 IBM Corp.

    Unit

    Working with Tivoli Common Reporting product-provided reports

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 2

    Objectives When you complete this unit, you can perform the following tasks:

    Describe how to obtain ready-to-use Cognos reports for use with Tivoli Common Reporting

    Navigate the user interface to locate, submit, schedule, email, and print reports

    Import Cognos report packages by using Tivoli Common Reporting TTE

  • 2012 IBM Corp.

    Lesson 1: Introducing reports

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 4

    Ready-to-use reports Many Tivoli products provide Cognos and BIRT reports that are ready to

    use without any programming

    You can obtain report packages in one of these ways: Installed as part of the Tivoli product installation media Downloaded from IBM System Management Library (formerly OPAL)

    Report packages are installed in Tivoli Common Reporting in one of these ways: Through the IBM Cognos Administration console Wrapped in an installable package, such as InstallAnywhere Installed with the product itself

    After installation, you can access and run reports Consistent interface to locate, submit, view, schedule, email, or print reports Some exceptions, such as starting the report interface directly from a product

    window

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 5

    Tivoli products with Cognos reports Go to http://ibm.co/xhkDRC

    Click the Report Catalog icon

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 6

    Tivoli Common Reporting report packages

    Clickable links

    Personal folder

    Typical report packages

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 7

    Example report packages

    Netcool/OMNIbus ITCAM for Applications BIRT reports

    OMEGAMON XE for z/OS

    IBM Tivoli Monitoring

    Tivoli Usage and Accounting Manager

    TTE

  • 2012 IBM Corp.

    Lesson 2: Working with reports

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 9

    Running a report 1. Select a report package

    2. Select the report

    3. Specify input parameters and click Finish TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 10

    Utilization Details for Multiple Resources

    CPU

    Disk

    Memory TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 11

    Managing reports Report actions and options Keeping reports Viewing saved reports Managing folders Setting a Home folder Scheduling reports Opening a report in Report Studio

    TTE

  • IBM Software Group | Tivoli Software 2012 IBM Corp. 12

    Report actions

    Actions: Set properties Run with options Open with Report Studio Create a report view Schedule the repor

  • Sours: https://dokumen.tips/documents/tivoli-common-reporting-211-fundamentalspdf.html

    Now discussing:

    Install and configure TCR Cognos reports within IBM Tivoli Monitoring

    IBMTivoliMonitoring v6 Cognos Reporting Installation Best

    Practices

    September 2010

    InstallandconfigureTivoli Common Reporting

    Cognos-based reportswithinIBMTivoli

    Monitoring v6

    Document version 1.0

    Antonio Sgro, Services Availability Performances Management Best Practice Team

    Stefano Borghetti, IBMTivoliMonitoring Development

    Payal Chakravarty, IBMTivoli Common Reporting Development

    © Copyright International Business Machines Corporation 2010. All rights reserved.

    US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule

    Contract with IBM Corp.


    ii

    CONTENTS

    1 Overview..............................................................................................................4

    2 Installation ...........................................................................................................4

    2.1 Prerequisites ............................................................................................5

    2.1.1 TDW Configuration ................................................................................5

    2.1.2 Prepare TDW with Shared Dimensions ..................................................5

    2.1.2.1 Adding Tivoli Reporting and Analytics Model (TRAM) Dimensions..........5

    2.1.2.2 Creating and Populating the Managed System Dimension......................8

    2.2 Connecting to the TDW via Database Client over ODBC........................11

    2.3 Installation using the java tool.................................................................11

    2.4 Manual Installation .................................................................................16

    3 Configuration .....................................................................................................20

    3.1 Setup multiple TDW connection .............................................................20

    3.1.1 Setting up Database connection via ODBC using Database Client .......20

    3.1.2 Creating new database connection in TCR...........................................21

    4 Main Features....................................................................................................26

    4.1 OS Agents Data Model...........................................................................26

    4.2 Virtual Servers (VMWare VI) Agents Data Model ...................................30

    4.3 System P Agents Data Model.................................................................33

    5 IBMTivoliMonitoring Agents TCRCognos-based Reports ................................36

    6 Known issues.....................................................................................................39

    7 Appendix............................................................................................................39

    Useful links ........................................................................................................39

    Acronyms...........................................................................................................40


    Trademarks .......................................................................................................41

    iii


    1 Overview

    Reporting capability is one of the most important features inside an IT organization

    in order to have full visibility of the resources usage over the time. Tivoli Common

    Reporting is the Tivoli standard infrastructure for creating, viewing, and managing Tivoli

    product reports. Throughout the rest of this document, we will refer to Tivoli Common

    Reporting as TCR.

    More than 40 Tivoli products ship TCRreports providing historical views of

    availability, utilization, performance, and many other key metrics that helps users to take

    value of the collected data in terms of capacity plan, data analysis. TCR 1.1 and 1.2

    versions were built on a BIRT reporting technology that required too much programming

    skill, demanded too much knowledge of the database in order to create reporting. In

    order to address the above user’s panic and with the help of Cognos acquisition, TCR

    1.3 was built on top of Cognos reporting technology and several benefits were provided.

    � Simplified report editing (Launch web-based Report Studio in context from

    a report)

    � Ad-Hoc Reporting (Create ad-hoc, on the fly reports)

    � Other Misc. capabilities

    o Automatic emailing of reports

    o Additional report formats (XML. Excel 2000 & 2000 Single Sheet,

    2002, and 2007, CSV, html,pdf)

    o Greater granular data security (row-level authorization)

    In addition, the newest TCR based on Cognos technology brings values in terms of

    � Consistency in reporting with other Tivoli products

    � Allowing report data correlation with other Tivoli product data and business data

    � Allowing customers access (via upgrade) to IBMCognos advanced analytics

    modules for advanced reporting capabilities that were not possible with TCR 1.2.

    BIRT reporting continues to be supported by TCR, and some of the adopting

    products in the Tivoli portfolio may ship BIRT based reports as well as Cognos based

    reports.

    2 Installation

    In order to install TCRCognos-based reports, there are some prerequisites that need to be

    satisfied and that depends from the specific product that is releasing the set of reports. Cognos

    relies on a data model that helps normalize the data and make it easier to configurereports. The

    data model is unique to each product. The following section outlines how to configure the

    prerequisites.


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    2.1 Prerequisites

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

    TivoliMonitoring products.

    To use the reports, you need at least the following components:

    IBMTivoliMonitoring Version 6.2.2 Fix Pack 2 or later for OS Agents reports. (OS Agents can

    be at 6.2.1 level or later)

    • ITM 6.2.1 or later for ITCAM for Transactions reports 7.2.0.1

    • ITM 6.2.2 FP02 or later for System P and VMWare agents reports 6.2.2.1

    Tivoli Common Reporting Version 1.3

    • Report packages: your product might have a separate reports package that must be extracted

    For additional requirements, the specific product documentation needs to be consulted.

    Notes: With Tivoli Common Reporting 1.3, both BIRT andCognos report engines can co-exist.

    2.1.1 TDW Configuration

    In order to make TCRCognos-based reports working, some pre-configuration steps need to be

    executed on the TDW database. The following sections describe all of the necessary steps.

    2.1.2 Prepare TDW with Shared Dimensions

    Preparing the Tivoli Data Warehouse for Tivoli Common Reporting includes creating the

    shared dimensions which are required for running the TCRCognos-based reportsand

    using the data models. There are two types of dimensions you will create:

    1. IBMTivoli Reporting and Analytics Model (TRAM) Dimensions: This includes the

    Time Dimension and Computer System dimension which are used by products across

    Tivoli providing support for cross product reporting.

    2. ITM’s Managed System Dimension or Resource Dimension: This dimension

    consists of a normalized table of all the Managed Systems in the environment.

    2.1.2.1 Adding Tivoli Reporting and Analytics Model (TRAM) Dimensions

    The following dimensions tables are created by this procedure:

    • Schema IBM_TRAM: TRAM stands for Tivoli Reporting and Analytics Model which is the

    common data model used by Tivoli products.

    • Table TIME_DIMENSION with years of time dimensional data and granularity to a

    specified number of minutes. Each row of this table is a unique minute key with various

    dimensions related to it, such as hour, weekday, day of month, quarter etc.

    • Table MONTH_LOOKUP globalizes the month names for Time Dimension.

    • Table WEEKDAY_LOOKUP globalizes the weekday names for Time Dimension.

    5


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    • Other dimensions conforming to the Tivoli Common Data Model, such as

    ComputerSystem, BusinessService, and SiteInfo.

    You will need the database scripts included in the extracted reports package under the

    db_scripts directory.

    • Procedure

    IBM DB2

    1. Copy the database scripts (.db2 files) from the reports package to a location where

    they can be run against the Tivoli Data Warehouse. The scripts are in the

    db_scripts directory.

    2. Log in as a user with database administrative rights such as db2admin or db2inst1.

    Your user ID must have administrator access to create the IBM_TRAM schema.

    3. Connect to the database that you want to create the dimension tables for. This is

    your Tivoli Data Warehouse.

    db2 connect to WAREHOUS;

    4. If you have an older version of the database scripts already installed clean up the

    database:

    start clean.db2

    5. Create the schema and tables:

    db2 -tf create_schema_IBM_TRAM.db2

    After the command completes successfully, several new tables are created in the

    IBM_TRAM schema: TIME_DIMENSION, MONTH_LOOKUP, WEEKDAY_LOOKUP,

    ComputerSystem, BusinessService, SiteInfo, and so on.

    6. Create the stored procedure for generating the time dimension:

    db2 [email protected] -vf gen_time_dim_granularity_min.db2

    7. To populate TIME_DIMENSION table, call the time dimension stored procedure

    with dates and granularity to generate the timestamps. You can generate up to five

    years at a time or have the data regenerated every day.

    8. db2 call IBM_TRAM.CREATE_TIME_DIMENSION('start_date',

    'end_date', granularity_of_data);

    where start date and end date are in this format YYYY-MM-DD-HH.MM.SS.MILSEC

    and granularity of data is the frequency in minutes. For example, the following command

    generates from 12/31/2009 to 12/31/2010 with 60-minute granularity.

    db2 call IBM_TRAM.CREATE_TIME_DIMENSION('2009-12-31-00.00.00.000000',

    '2010-12-31-00.00.00.000000', 60);

    • Microsoft SQL Server

    1. Copy the database scripts (.sql files) from the reports package to a location where

    they can be run against the Tivoli Data Warehouse. The scripts are in the

    db_scripts branch of the directory where the reports package was extracted to.

    2. Customize the provided scripts by changing the default database name in the use

    statement (replace USE IBM_TRAM) to match the name of your Tivoli Data

    Warehouse database. If the name of your Tivoli Data Warehouse is "warehouse"

    the statement is “USE warehouse”:

    6


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    a. createSchema.sql

    b. createProcedure.sql

    c. clean.sql

    d. populateTimeDimension.sql Also, modify the boundary parameters for

    the time dimension and granularity. For example,

    e. @startDate = '2010-01-01 00:00:00',

    f. @endDate = '2010-07-08 00:00:00',

    @granularity = 60,

    If Monday must be the first day of the week, add the fourth parameter equal to

    1; otherwise, release three parameters.

    @weekday = 7

    3. If you have an older version of the database scripts already installed, clean up the

    database.

    sqlcmd -i clean.sql [-U username -P password] [-S hostname]

    4. Run the scripts at the MS SQL command line in this order:

    sqlcmd -i createSchema.sql [-U username -P password] [-S host]

    sqlcmd -i createProcedure.sql [-U username -P password] [-S host]

    sqlcmd -i populateTimeDimension.sql [-U username -P password] [-S host]

    • Oracle manual installation

    1. Copy the database scripts (.sql files) from the reports package to a location where

    they can be run against the Tivoli Data Warehouse. The scripts are in the

    db_scripts branch of the directory where the reports package was extracted to.

    2. Start an SQL *Plus session if it is not already running.

    3. Check that you can access remotely as sys user.

    4. If you have an older version of the database scripts already installed clean up the

    database (the procedure must be called by the sys user):

    clean.sql

    5. Take one of the following steps:

    • Oracle batch installation

    � If you can access remotely as sys user, run this commandand provide all

    the information that the script requires:

    @MY_PATH\setup_IBM_TRAM.sql

    � If you cannot access remotely as sys user, run this command locally at the

    Oracle server and provide all the information that the script requires:

    @MY_PATH\local_setup_IBM_TRAM.sql

    1. Copy the database scripts (.sql files) from the reports package to a location where

    they can be run against the Tivoli Data Warehouse. The scripts are in the

    db_scripts branch of the directory where the reports package was extracted to.

    2. Start an SQL *Plus session if it is not already running.

    7


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    3. If you have an older version of the database scripts already installed clean up the

    database (the procedure must be called by the sys user):

    clean.sql

    4. Create user IBM_TRAM (the script must be called by a user with system rights,

    such as SYS/SYSTEM):

    5. @MY_PATH\create_IBM_TRAM.sql TCR_PASS USER_TBSPC

    TEMPORARY_TBSPC

    where TCR_PASS is the password for the new user, USER_TBSPC is the default user

    tablespaces name (must exist), and TEMPORARY_TBSPC is the default temporary

    tablespaces name (must exist)

    6. Create the IBM_TRAM tables (the script must be called by the IBM_TRAM user

    created in the previous step):

    7. @MY_PATH\create_schema.sql USER_TBSPC

    where USER_TBSPC is the default user tablespaces name (must exist)

    8. Grant privileges to the user, such as ITMUSER (the script must be called by the

    IBM_TRAM user):

    9. @MY_PATH\grant_IBM_TRAM.sql USER

    where USER is the name of the user to grant privileges to.

    10. Create the procedure (the script must be called by the IBM_TRAM user):

    @MY_PATH\gen_time_dim_granularity_hr.sql

    11. Load the lookup data (the script must be called by the IBM_TRAM user):

    @MY_PATH\populateLookup.sql

    12. Generate the time dimension (the procedure must be called by the IBM_TRAM

    user):

    13. @MY_PATH\populateTimeDimension.sql StartDate EndDate Granularity

    where StartDate is the start date in the format 'yyyy-mm-dd HH:MM', EndDate is the

    end date in the format 'yyyy-mm-dd HH:MM', and Granularity is the number of minutes.

    Example:

    • Results

    @reports/myreports/populateTimeDimension.sql

    '2008-12-31 00:00' '2011-12-31 00:00' '60'

    The shared dimensions and time dimensions tables are complete.

    2.1.2.2 Creating and Populating the Managed System Dimension

    NOTE: This step is only required for OS Agents. If you are deploying reports for other

    agents you do not need to implement this step and can proceed to the next step.

    Preparing the Tivoli Data Warehouse for Tivoli Common Reporting also includes creating

    and populating the resource dimension table "ManagedSystem", which is required for

    running the Cognos-based reportsand using the data models. This dimension consists of a

    normalized table of all the Managed Systems in the environment

    • Before you begin

    8


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    Before starting the procedure to build the resource dimension table, you must first

    configure historical data collection for one or more of the following attribute groups,

    depending on the operating system you are getting reports for:

    Type

    Linux Linux IP

    Address

    UNIX UNIX IP

    Address

    Windows Computer

    Information

    Attribute

    group Table Summarize

    Linux_IP_Address Daily

    UNIX_IP_Address Daily

    NT_Computer_Information Daily

    You can configure historical data collection in the Tivoli Enterprise Portal or in the

    Command Line Interface. The following example shows how a local historical collection for

    NT Computer Information was created and distributed from the CLI:

    tacmd login -s MyComputer -u MyUser -p MyPassword

    tacmd tepslogin -s localhost -u sysadmin

    tacmd histconfiguregroups -t knt -o "NT Computer Information" -m -d YQMQDH -p

    Y=2y,Q=2y,M=1y,W=1y,D=6m,H=14d,R=7d

    tacmd histcreatecollection -t knt -o "NT Computer Information" -a "ComputerInformation" -c

    15m -i 15m -l TEMA -e "Needed for resource dimension table for TCR."

    tacmd histstartcollection -t "knt" -o "NT Computer Information" -u sysadmin

    See "Historical collection configuration" or tacmd histconfiguregroups, tacmd

    histcreatecollection, and tacmd histstartcollection in the IBMTivoliMonitoring

    Command Reference for details.

    • Procedure

    IBM DB2

    1. Log in as db2admin. Your user ID must have administrator access to create the

    resource dimension.

    2. Connect to the database that you want to create the resource dimension table for.

    This is your Tivoli Data Warehouse.

    db2 connect to WAREHOUS;

    3. Create the tables:

    db2 -tf gen_resources.db2

    After the command completes successfully, a new table is shown under the ITMUSER

    schema: ManagedSystem.

    4. Create the stored procedure to populate the ManagedSystem table:

    db2 [email protected] -vf populate_resources.db2

    5. To populate ManagedSystem table, call the stored procedure:

    9


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    db2 call ITMUSER.POPULATE_OSAGENTS();

    • Microsoft SQL Server

    1. Customize the provided scripts:

    a. In create_table.sql, change the default database name in the use

    statement (replace USE WAREHOUS) if it is different from the default.

    b. In create_procedure.sql, change the default database name in the use

    statement (replace USE WAREHOUS) if it is different from the default.

    c. In populate_agents.sql, change the default database name in the use

    statement (replace USE WAREHOUS) if it is different from the default.

    2. Run the scripts at the MS SQL command line in this order:

    sqlcmd -i create_table.sql [-U myusername -P mypassword] [-H myhost])

    sqlcmd -i create_procedure.sql [-U myusername -P mypassword] [-H myhost])

    sqlcmd -i populate_agents.sql [-U myusername -P mypassword] [-H my_host])

    • Oracle manual installation

    1. Start a SQL *Plus session if it is not already running.

    2. Run this command (path with no spaces) and provide all the information that the

    script requires:

    @MY_PATH\setup_populate_agents.sql

    • Oracle batch installation

    1. Start a SQL *Plus session if it is not already running.

    2. Create the ITMUSER.ManagedSystem table. The script must be called by the

    Tivoli Data Warehouse user, which is ITMUSER by default. If you used a different

    user name, modify the script for the correct name.

    @MY_PATH\create_table.sql

    3. Create the procedure to populate the table:

    @MY_PATH\create_procedure.sql

    • Results

    4. Start the procedure to populate the ManagedSystem table:

    5. begin

    6. POPULATE_OSAGENTS('ITMUSER');

    7. end;

    The ManagedSystem table is created and populated with managed systems of your

    environment.

    • Automating the Population of Managed System Table Regularly

    The Managed System table is dynamic i.e., the contents will change based on the changes

    in your environment. As and when new managed systems are added the table needs to be

    updated. Hence it is necessary to automate the task of populating this table regularly. In

    order to do this the stored procedure to populate the ManagedSystem table

    (POPULATE_OSAGENTS) needs to be called by a daily scheduled automated job.

    10


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    2.2 Connecting to the TDW via Database Client over ODBC

    Cognos uses ODBC to connect to the database. Hence it is important to first install a

    database client on the Tivoli Common Reporting server and have it connect to the Tivoli

    Data Warehouse.

    DB2

    Make sure you have deployed a DB2 database client on the machine where Cognos-based

    Tivoli Common Reporting engine is installed. The client should be of the same version as

    the database that Tivoli Data Warehouse is using. Connect the DB2 database client to the

    database server by running the Configuration Assistant, configuring the local net service

    name configuration, and restarting your system.

    Oracle

    Make sure you have deployed the Oracle database client on the machine where Cognosbased

    Tivoli Common Reporting engine is installed. Connect the Oracle database client to

    the database server by running the Oracle Net Configuration Assistant, configuring the

    local net service name configuration, and restarting your system.

    MS SQL Server

    Make sure you have deployed the MS SQL database client on the machine where Cognosbased

    Tivoli Common Reporting engine is installed. Connect the MS SQL client to the

    database server by running the MS SQL Management Studio Express, configuring the

    local net service name configuration, and restarting your system.

    Important: Note the name of the connection you have created as it is used when you

    install the reports in Section 2.3

    2.3 Installation using the java tool

    In order to install IBMTivoliMonitoringCognos-based Reports, it is needed to use the reports

    installer packaged with each set of Cognosreports.

    Here is the procedure to install the reports (as example, the OS Agents reports are installed)

    Procedure

    1. From the Cognosreports disk or the directory where the report package was extracted,

    launch the setup script:

    � setup.bat tcr_install_dir. (If Tivoli Common Reporting is installed in

    the default directory, you do not need to specify an installation directory.)

    � ./setup.sh tcr_install_dir

    2. Click Next on the following panel

    11


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    3. Select the Reports on the left side and click on the right arrow (circled in red in the next

    panel)

    4. Click on the Next button

    12


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    5. In the following panel complete the following:

    Installation Type = on TCR 1.3

    � Enter the directory where TCR is installed

    � Enter the Cognos user name and password

    And click on the Next button

    13


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    6. If you want to skip the TDW data source, check the devoted flag and click next but then it will

    be needed to be created manually

    7. In the next panel you will be prompted for the TDW data source connection parameters; after

    filling them, click on the Next button

    8. In the following screenshot, you will see a summary of all the installation steps and settings; if

    everything is ok, click on the Install button

    14


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    9. If the installation was successfully executed, you will see the following panel:

    15


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    2.4 Manual Installation

    The Cognos-based reports can be installed not only using the Java installation tool but

    using a manual procedure hereafter described (as example Virtual Server Reports are

    used to describe the manual installation procedure):

    1. In the ITM reports installation media, identify the reports zip file (ex. IBMTivoli

    Monitoring for Virtual Servers Reports.zip)

    2. Copy the report zip file in the TCR deployment directory:

    /products/tcr/Cognos/c8/deployment

    3. In the ITM Reports installation media, identify the images directory (ex.

    C:\IBM_Tivoli_Monitoring_Virtual_Servers_Reports\packages\VMwareVIAgents\im

    ages)

    4. Copy the content of the images directory in the TCR images directory

    /profiles/TIPProfile/installedApps/TIPCell/IBM

    Cognos 8.ear/p2pd.war/tivoli/ITM/images

    5. Launch the IBMCognos Administration from the TCR portal as described in the

    following figure:

    16


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    6. From the Configuration tab create a TDW data source

    7. From the Content Administration tab choice New Import Button and the report

    package that needs to be imported

    17


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    8. Click Next, choose a name for your report package, and then click Next again.

    9. Select the report package and click on the Next button

    18


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    10. Click Next twice, and on this panel choose the Save and run once option and click

    Finish.

    11. Finally, click Run and the report package will appear.

    19


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    3 Configuration

    General configuration information

    3.1 Setup multiple TDW connections

    Cognos supports the creation of multiple TDW connections. In order to do this you will need to

    do two things:

    1. Use the database client to set up an ODBC connection to your database as explained

    in Section

    2. Add the new connection in Cognos Administration

    3.1.1 Setting up Database connection via ODBC using Database Client

    DB2:

    Connect the DB2 database client to the database server by running the Configuration

    Assistant, configuring the local net service name configuration, and restarting your system.

    MS SQL Server:

    Connect the MS SQL client to the database server by running the MS SQL Management

    Studio Express, configuring the local net service name configuration, and restarting your

    system.

    Oracle:

    Connect the Oracle database client to the database server by running the Oracle Net

    Configuration Assistant, configuring the local net service name configuration, and restarting

    your system.

    Important: Note the name of the connection you have created as it is used in one of the

    following steps.

    20


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    3.1.2 Creating new database connection in TCR

    Once you have completed step 1 and are ready to set up the data source connection in TCR, browse to

    the TCR panel and launch IBMCognos Administration.

    In the Admin Panel, go to Configuration -> Data Sources.

    Select TDW that was created by the installation wizard. This is the data source name that

    is understood by Cognos for the ITM data model. DO NOT change this name.

    When you click on TDW it will take you to the database connections that the data source

    TDW points to. Here you will see a default TDW defined. Click on the New Connection icon

    to create a new database connection.

    21


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    As you can see in the figure above, the Data Source TDW contains six different database

    connections. Once configured, when a report is run the user is given the ability to choose

    which database to go against.

    Once you click the New Connection, the New Connection wizard will launch.

    Enter the Name for this connection. It’s a good practice to give this the same name as the

    database alias you have created in the client. Click Next.

    22


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    DB2

    In the next panel choose the database type from the drop down list i.e., either DB2,

    Oracle or Microsoft SQL Server (ODBC) and click Next.

    1. On the second panel choose an DB2 database as Type.

    2. On the third panel specify the name of the connection you have noted before as the DB2

    connect string, and in the Signon section specify a new User ID and Password.

    MS SQL

    1. On the second panel choose an Microsoft SQL Server database as Type.

    2. On the third panel specify the name of the connection you have noted before as the Server

    name, and in the Signon section specify a new User ID and Password.

    23


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    Oracle

    1. On the second panel choose an Oracle database as Type.

    2. On the third panel specify the name of the connection you have noted before as the

    SQL*Net connect string, and in the Signon section specify a new User ID and Password.

    On the third panel as explained above enter the database name and the user ID and

    password.

    24


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    Click the Test Connection link. In the next panel, click the Test Connection button

    If the connection is successful it will return saying the Connection is successful. You can

    then hit Close on this panel and the subsequent panel and then a final Finish to save this

    connection.

    Now when you look under the TDW data source you will find a new connection called

    “Production TDW”.

    Video Demo Link to set up data source connections:

    http://www.youtube.com/watch?v=0s3HbSkUySM

    25


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    4 Main Features

    4.1 OS Agents Data Model

    The data model for the Monitoring Agents for Windows OS, Linux OS, and UNIX

    OS reports will have the following features:

    • The model covers data from OS Agents only.

    • The model contains a subset of the attribute groups collected by OS Agents in

    aggregated form for time dimension: AVG, MIN, MAX, SUM, LAT, TOT, HI, LOW.

    • The model includes a Managed System dimension with the Agent Type attribute

    (on Windows, Linux, and UNIX systems). It is placed in the IBMTivoli

    Monitoring Shared Dimensions namespace.

    • The model includes all the aggregations handled by Summarization and Pruning

    from daily to yearly including the raw data.

    • The model contains forecasting based on the linear trend for the following

    metrics for each time dimension:

    For Linux:

    � KLZ_CPU_FCAST_XX.AVG_Idle_CPU

    � KLZ_Disk_FCAST_XX.AVG_Disk_Used_Percent

    � KLZ_VM_Stats_FCAST_XX.AVG_Used_Virtual_Storage_Pct

    � KLZ_Network_FCAST_XX.AVG_Bytes_Transmitted_per_sec

    � KLZ_Network_FCAST_XX.AVG_Bytes_Received_per_sec

    For UNIX:

    � System_FCAST_XX.AVG_Idle_CPU

    � Disk_FCAST_XX.AVG_Space_Used_Percent

    � Unix_Memory_FCAST_XX.AVG_Virtual_Storage_Pct_Used

    � Network_FCAST_XX.AVG_Transmitted_MB_Total

    � Network_FCAST_XX.AVG_Received_MB_Total

    For Windows:

    � NT_System_FCAST_XX.AVG_%_Total_Processor_Time

    � NT_Logical_Disk_FCAST_XX.AVG_%_Used

    � NT_Memory_64_FCAST_XX.AVG_Available_Usage_Percentage

    � NT_Server_FCAST_XX.AVG_Bytes_Transmitted/sec

    � NT_Server_FCAST_XX.AVG_Bytes_Received/sec

    The metrics data items names reflect the catalog attributes names with the following prefixes:

    – SUM_ into Sum

    – LAT_ into Latest

    – MIN_ into Minimum

    – MAX_ into Maximum

    – TOT_ into Total

    – AVG_ into Average

    – HI_ into Higher

    – LOW_ into Lower

    26


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    Linux

    UNIX

    Windows

    Agent Attribute Group

    Linux Linux CPU Averages KLZ_CPU_Averages

    Linux CPU KLZ_CPU

    Linux Disk KLZ_Disk

    Linux Network KLZ_Network

    Linux Process KLZ_Process

    Linux VM Stats KLZ_VM_Stats

    Linux Disk IO KLZ_Disk_IO

    Linux Disk Usage Trends KLZ_Disk_Usage_Trends

    Linux IO Ext KLZ_IO_Ext

    Linux NFS Statistics KLZ_NFS_Statistics

    Linux Process User Info KLZ_Process_User_Info

    Linux RPC Statistics KLZ_RPC_Statistics

    Linux Sockets Detail KLZ_Sockets_Detail

    Linux Sockets Status KLZ_Sockets_Status

    Linux Swap Rate KLZ_Swap_Rate

    Linux System Statistics KLZ_System_Statistics

    Linux User Login KLZ_User_Login

    UNIX Disk Disk

    Network Network

    Process Process

    Unix Memory Unix_Memory

    System System

    Disk Performance Disk_Performance

    NFS and RPC Statistics N_F_S_and_R_P_C_Statistics

    SMP CPU SMP_CPU

    Solaris Zones Solaris_Zones

    User User

    Windows Logical Disk Hourly NT_Logical_Disk

    Memory Hourly NT_Memory_64

    Network Interface Hourly NT_Network_Interface

    Process Hourly NT_Process_64

    Server Hourly NT_Server

    System Hourly NT_Process_64

    ICMP Statistics Hourly ICMP_Statistics

    IP Statistics Hourly IP_Statistics

    Cache Hourly NT_Cache

    Device Dependencies Hourly NT_Device_Dependencies

    Devices Hourly NT_Devices

    Event Log Hourly NT_Event_Log

    Monitored Logs Report Hourly NT_Monitored_Logs_Report

    Network Port Hourly NT_Network_Port

    Objects Hourly NT_Objects

    Paging File Hourly NT_Paging_File

    Physical Disk Hourly NT_Physical_Disk

    27


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    Table 1. Attributes groups supported by the data model

    Printer Hourly NT_Printer

    Processor Hourly NT_Processor

    Processor Summary Hourly NT_Processor_Summary

    Redirector Hourly NT_Redirector

    Server Work Queues Hourly NT_Server_Work_Queues_64

    Service Dependencies Hourly NT_Service_Dependencies

    Services Hourly NT_Services

    Thread Hourly NT_Thread

    Print Queue Hourly Print_Queue

    Process IO Hourly Process_IO

    TCP Statistics Hourly TCP_Statistics

    UDP Statistics Hourly UDP_Statistics

    The following figure shows the data model and some of its available attributes:

    28


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    Forecasting

    The OS Agents reports provide a new functionality to forecast potential future

    values for a set of metrics. This forecast is calculated using a linear trending based on

    historical data in a most recent time window.

    There are limits in the future for forecasting depending on the aggregation type:

    • Hourly: 60 hours in the future

    • Daily: 60 days in the future

    • Weekly: 1 year in the future

    • Monthly: 5 years in the future

    • Quarterly: no limit

    • Yearly: no limit

    For reference, these are the formulas used to compute the forecasted values:

    Input data:

    INPUT = i i

    where:

    xi

    yi

    { ( x , y ) : i = 1,

    2,

    Κ , n}

    = series of timestamps

    expressed as number of seconds from1970

    - 01-

    01 00 : 00 : 00

    = series of measurements

    ( x i , yi

    ) = metric value yi

    measured in the given time xi

    n = number of samples

    Output data

    1. Linear approximation of historical data expressed as:

    y = ax + b

    R2

    ∈ [ 0,

    1)

    2. to show correlation between historical data and computed linear

    approximation.

    Solution

    29


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    S

    S

    S

    S

    S

    xx

    yy

    xy

    x

    y

    a =

    b =

    R =

    =

    =

    =

    =

    =

    i=

    1

    i=

    1

    i=

    1

    n

    i=

    1

    n

    i=

    1

    d = nS

    n


    n


    n




    xx

    ( nS xy − S xS

    y ) / d

    ( S xxS

    y − S xS

    xy ) / d

    ( nS − S S ) / ( nS − S S )( nS − S S )

    R2

    = R

    2

    x x

    x y

    x

    xy

    y

    y

    i

    i

    i

    i

    i

    i

    y

    i

    − S

    i

    x

    S

    x

    x

    y

    xx

    x

    x

    yy

    Note: Related to forecasting, there is a subset of tables that are visible in the model, but

    cannot be used in custom queries andreports. These tables are contained in the following

    folders:

    • Forecast Hourly

    • Forecast Daily

    • Forecast Weekly

    • Forecast Monthly

    • Forecast Quarterly

    • Forecast Yearly

    Refer to the following link to see video demos of drag and drop report creation using the

    ITM OS Agents data model:

    http://www.youtube.com/watch?v=RiqnvvQ6Jho

    4.2 Virtual Servers (VMWare VI) Agents Data Model

    The VMware VI Agent Data Model is what you will see in Data Navigation tree of the Query

    and Report Studio. The data model is a layer built on top of the Tivoli Data Warehouse to

    make the data more consumable to the end user. The data model contains pre-defined

    relationships so that when you drag and drop elements across different tables and views

    they join and you do not have to manually write any SQL.

    y

    y

    30


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    The structure of the VMware VI Agents data model is shown in the figure below. Cognos

    data models are virtual star schema models separated into facts and dimensions. Facts

    are measurable quantities that can be aggregated like CPU Utilization, Number of

    Processors. Dimensions are the main identifiers by which facts can be grouped,

    aggregated and sliced and diced. For example, time and server are dimensions by which

    the fact CPU Utilization can be grouped.

    The data model contains two types of dimensions: the TCR Shared Dimension which are

    shared across Tivoli by products like Time and ITM for Virtual Servers Shared Dimension

    which are dimensions shared across the ITM for Virtual Servers agents like Datacenter,

    Clusters , Servers, Virtual Machines, Datastores etc. The facts in the data model are

    organized under folders by their summarization type like Daily and Hourly.

    On expanding Daily and Hourly you will be able to see the attribute groups (see figure

    below). Each attribute group corresponds to a table/view in the data warehouse. As you

    can see each attribute group contains a bunch of facts or measures like

    MIN_CPU_Utilization, AVG_CPU_Utilization and some identifiers like CPU_Number and

    Shift and Vacation periods.

    31


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    To build a report you need to follow this order for dragging and dropping elements:

    1. First drag one of the ITM for Virtual Servers Shared Dimensions like

    Datacenter/Cluster/Server/VMs.Server_Hostname

    2. Drag any metric from a related attribute group. For example if you want to look at

    Server related metrics, drag anything under the attribute groups starting with

    Server in their name. For VM, drag data from the attribute groups whose names

    start with VM.

    3. Finally drag and drop the Standard Timestamp from TCR Shared

    Dimensions.Time Dimension. For daily data you can use Date instead of Standard

    Timestamp. You can use any of the other time metrics to slice and dice the data.

    32


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    Refer to the following link to see video demos of drag and drop report creation using the

    VMware VI Agent data model.

    http://www.youtube.com/watch?v=8xbNDY4dBkc

    4.3 System P Agents Data Model

    The System P Agents Data Model is what you will see in Data Navigation tree of the Query

    and Report Studio. The data model is a layer built on top of the Tivoli Data Warehouse to

    make the data more consumable to the end user. The data model contains pre-defined

    relationships so that when you drag and drop elements across different tables and views

    they join and you do not have to manually write any SQL.

    The structure of the System P Agents data model is shown in the figure below. Cognos

    data models are virtual star schema models separated into facts and dimensions. Facts

    are measurable quantities that can be aggregated like CPU Utilization, Number of LPARs.

    Dimensions are the main identifiers by which facts can be grouped, aggregated and sliced

    and diced. For example, time and server are dimensions by which the fact CPU Utilization

    can be grouped.

    The System P Agents Data Model contains data for three agents: CEC Base Agent, AIX

    Premium Agent and VIOS Agent.

    When you expand the data model you will see TCR Shared Dimensions, CEC Base Agent,

    VIOS Agent and AIX Premium Agent.

    33


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    The data model contains two types of dimensions: the TCR Shared Dimension which are

    shared across Tivoli by products like Time and agent specific dimensions like CEC Base

    Agent Dimensions, VIOS Agent Dimensions and AIX Premium Agent Dimensions which

    are dimensions shared across the System P agents like ManagedSystem, LPAR etc. The

    facts in the data model are organized under folders by their summarization type like Daily

    and Hourly.

    On expanding Daily and Hourly you will be able to see the attribute groups (see figure

    below). Each attribute group corresponds to a table/view in the data warehouse. Each

    attribute group contains a bunch of facts or measures like AVG_CPU_Allocated and some

    identifiers like CPU_Number and Shift and Vacation periods.

    34


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    To build a report you need to follow this order for dragging and dropping elements:

    1. First drag one of the dimensions from a specific agent like LPAR from CEC Base

    Agent Dimensions or SystemName from AIX Premium Agent Dimensions.

    2. Drag any metric from a related attribute group. Note that dimensions and metrics

    should be dragged from the same agent.

    3. Finally drag and drop the Standard Timestamp from TCR Shared

    Dimensions.Time Dimensions. For daily data you can use Date instead of

    Standard Timestamp. You can use any of the other time metrics to slice and dice

    the data.

    An example of a report for the AIX Premium Agent is shown below.

    35


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    5 IBMTivoliMonitoring Agents TCR

    Cognos-based Reports

    Here is the list of ITM agents that already provided a set of TCRCognos based reports:

    � ITCAM for Transactions v7.2.0.1

    � ITM for Virtual Servers: VMware VI Agent v6.2.2

    � System P Agents (CEC, VIOS and AIX Premium) v6.2.2.1

    � ITM OS Agents v6.2.2 FP02

    Each of the above reports needs some Warehouse Data collection to be enabled and Daily and

    hourly summarization must be enabled for.

    The following section document the needed attributes groups, however all the details are

    documented in the specific product documentation.

    OS Agents Reports attributes groups:

    • Windows agent:

    o Logical_Disk

    o Memory

    o Process

    o Server

    o System

    • Linux agent:

    36


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    o CPU

    o Disk

    o Network

    o Process

    o VM_Stats

    • UNIX agent:

    o Disk

    o Network

    o Process

    o System

    o Memory

    System P Agents Reports attributes groups:

    • AIX Premium Agent

    o KPX_AMS_POOL

    o KPX_CPU_DETAIL

    o KPX_CPU_SUMMARY

    o KPX_ACTIVE_MEMORY_EXPANSION

    o KPX_DISKS

    o KPX_FILE_SYSTEMS

    o KPX_LOGICAL_PARTITION

    o KPX_LOGICAL_VOLUMES

    o KPX_NETWORK_ADAPTERS_RATES

    o KPX_NETWORK_INTERFACES

    o KPX_PAGING_SPACE

    o KPX_PHYSICAL_VOLUMES

    o KPX_VOLUME_GROUPS

    o KPX_PHYSICAL_MEMORY

    o KPX_SYSTEM_CALL

    o KPX_SYSTEM_IO

    o KPX_PROCESSES_SUMMARY

    o KPX_WPAR_INFORMATION

    o KPX_WPAR_NETWORK

    o KPX_VIRTUAL_MEMORY_MANAGEMENT

    • CEC Base Agent

    o KPK_AMS_POOLS

    o KPK_CPU_POOLS

    o KPK_GLOBAL_CEC

    o KPK_MON_LPARS

    o KPK_MON_UNMON_ALLOC

    o KPK_PER_LPAR

    • HMC Base Agent

    o No reports

    • VIOS Premium Agent

    o KVA_AMS_POOL

    o KVA_CPU_DETAIL

    o KVA_CPU_SUMMARY

    o KVA_DISKS KVA_FILE_SYSTEMS

    o KVA_INTERNET_PROTOCOL_DETAIL

    o KVA_INTERNET_PROTOCOL_SUMMARY

    o KVA_LOGICAL_PARTITION

    o KVA_LOGICAL_VOLUMES

    o KVA_NETWORK_ADAPTERS_RATES

    o KVA_NETWORK_MAPPINGS

    o KVA_PAGING_SPACE

    37


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6


    o KVA_VOLUME_GROUPS

    o KVA_PHYSICAL_MEMORY

    o KVA_SYSTEM_CALL

    o KVA_SYSTEM_IO

    o KVA_STORAGE_MAPPINGS

    o KVA_PROCESSES_SUMMARY

    o KVA_PROCESSES_DETAIL KVA_TCP

    VMWare Agent Reports attributes groups

    • Windows agent:

    o Logical_Disk

    o Memory

    o Process

    o Server

    o System

    • Linux agent:

    o CPU

    o Disk

    o Network

    o Process

    o VM_Stats

    • UNIX agent:

    o Disk

    o Network

    o Process

    o System

    o Memory

    ITCAM for Transactions Agent Reports attributes groups

    • For the Application Management Console agent (raw data):

    o AMC_Application

    o AMC_Client

    o AMC_Transaction

    o AMC_Server

    o AMC_Internet_Service

    o AMC_Internet_Service_Agent

    o AMC_Internet_Service_Element

    • For the Client Response Time agent (raw data, hourly, daily):

    o CRT_Application_Status

    o CRT_Transaction_Status

    • For the Web Response Time agent (raw data, hourly, daily):

    o WRT_Application_Status

    o WRT_Transaction_Status

    o WRT_User_Sessions

    • For the Robotic Response Time agent (raw data, hourly, daily):

    o RRT_Application_Status

    o RRT_Transaction_Status

    o RRT_SubTransaction_Status

    o RRT_Robotic_Playback_Events (raw data only)

    • For the Internet Service Monitoring agent (raw data, hourly, daily):

    o KIS_HOST_STATISTICS

    o KIS_MONITOR_STATUS

    38


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    o KIS_SERVICE_INSTANCE_STATISTICS

    o KIS_HTTP

    o KIS_ICMP

    • For the Transaction Tracking agent (raw data, hourly, daily):

    o Aggregates

    o Interactions

    6 Known issues

    There is a known issue when the TDW schema is different from ITMUser where the Cognosbased

    reports cannot be executed.

    VMWare agent workaround is documented at the following link:

    http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.tivoli.itmvs.doc/vmware622

    _user129.htm#wq154

    System P Agent workaround is documented at the following link:

    http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2/paix6221_us

    er177.htm#import

    The OS Agent workaround is to install the following Interim Fix that can be obtained through L2

    support opening a pmr:

    6.2.2.2-TIV_ITM_OS_AGENTS_REPORTS-LA0001

    The APAR number is IZ78074 and will be officially released within ITM 6.2.2 FP03

    7 Appendix

    Useful links

    Tivoli Common Reporting Web Site

    https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityvi

    ew?communityUuid=9caf63c9-15a1-4a03-96b3-8fc700f3a364

    Tivoli Common Reporting Support Site

    http://www-

    947.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Common_Reporting

    IBMTivoliMonitoring Administration Guide

    http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm6

    22fp2_admin.htm

    39


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    IBMTivoliMonitoring Operating System Agents User Guides

    http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/nav/3_0_3_2

    IBMTivoliMonitoring Operating System Agents TCRCognos-based Reports

    http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/main

    _unix170.htm#wq319

    IBMTivoliMonitoring for Virtual Server (VI VMWare Agent) TCRCognos-based Reports

    http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.tivoli.itmvs.doc/vmwar

    e622_user127.htm#wq149

    IBMTivoliMonitoring System P Agent TCRCognos-based Reports

    http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2/paix622

    1_user174.htm#wq168

    IBMTivoli Composite Application Manager for Transactions User Guide

    http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.2.0.1/ichomepage.html

    Acronyms

    IBMTivoliMonitoring support site

    www.ibm.com/support

    ITM IBMTivoliMonitoring

    TCRTivoli Common Reporting

    TDW Tivoli Data Warehouse

    TEMS Tivoli Enterprise Management Server

    TEP Tivoli enterprise Portal

    TEPS Tivoli Enterprise Portal Server

    WPA Warehouse Proxy Agent

    SPA Summarization Pruning Agent

    Table 1 - Acronyms

    40


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    Trademarks

    © Copyright IBM Corporation 2010

    IBM United States of America

    ®

    Produced in the United States of America

    All Rights Reserved

    The e-business logo, the eServer logo, IBM, the IBM logo,

    OS/390, zSeries, SecureWay, S/390, Tivoli, DB2, Lotus and

    WebSphere are trademarks of International Business

    Machines Corporation in the United States, other countries or

    both.

    Lotus, Lotus Discovery Server, Lotus QuickPlace, Lotus Notes,

    Domino, and Sametime are trademarks of Lotus Development

    Corporation and/or IBM Corporation.

    Java and all Java-based trademarks and logos are trademarks

    of Sun Microsystems, Inc. in the United States, other countries

    or both.

    Other company, product and service names may be

    trademarks or service marks of others.

    INTERNATIONAL BUSINESS MACHINES CORPORATION

    PROVIDES THIS PAPER “AS IS” WITHOUT WARRANTY OF

    ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING,

    BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

    NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

    FOR A PARTICULAR PURPOSE. Some states do not allow

    disclaimer of express or implied warranties in certain

    transactions, therefore, this statement may not apply to you.

    Information in this paper as to the availability of products

    (including portlets) was believed accurate as of the time of

    publication. IBM cannot guarantee that identified products

    (including portlets) will continue to be made available by their

    suppliers.

    This information could include technical inaccuracies or

    typographical errors. Changes may be made periodically to

    the information herein; these changes may be incorporated in

    subsequent versions of the paper. IBM may make

    improvements and/or changes in the product(s) and/or the

    program(s) described in this paper at any time without notice.

    Any references in this document to non-IBM Web sites are

    provided for convenience only and do not in any manner serve

    as an endorsement of those Web sites. The materials at those

    Web sites are not part of the materials for this IBM product and

    use of those Web sites is at your own risk.

    IBM may have patents or pending patent applications covering

    subject matter described in this document. The furnishing of

    this document does not give you any license to these patents.

    You can send license inquiries, in writing, to:

    41


    InstallandconfigureTivoli Common Reporting Cognos-based reportswithinIBMTivoliMonitoring v6

    IBM Director of Licensing

    IBM Corporation

    4205 South Miami Boulevard

    Research Triangle Park, NC 27709 U.S.A.

    42

    Sours: https://www.yumpu.com/en/document/view/7791053/install-and-configure-tcr-cognos-reports-within-ibm-tivoli-monitoring


    14234 14235 14236 14237 14238