Antonio Sgro, SAPM Best Practices Senior IT Architect firstname.lastname@example.org. Tivoli Common Reporting through Cognos. Disclaimer.
The information on the new product or component is intended to outline our general product direction and it should not be relied on in making a purchasing or sales decision.
The information on the new product or component is for informational purposes only and may not be incorporated into any contract.
The information on the new product or component is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion.
Note: Will supplement other Tivoli product UI efforts (Operational console for monitoring/troubleshooting)
Query Studio (web-based)
Report Studio (web-based)
Available through the TIP interface
Launched via a drop down tool from the TIP interface
Launched as a OS native Java application
BIRT report designer via Eclipse
Launched as a stand alone Java application
TCRArchitectural Overview TCR for Asset & Performance Management
Cognos UI in TIP for Cognos report administration
View Cognos based Report
CLI –BIRT only
View BIRT based Report
Existing TCR UI for legacy reports
1. Extract key report info
Conversion Assistant annotates the TCR BIRT report (below) with SQL queries and other info
3. Complete final Cognos based TCR report
User completes report using TCR Report Studio (below) to fill in details
2. Generate draft Cognos based TCR report
Conversion Assistant creates draft new TCR report, preserving layout and annotating actions user should take
*Available from TCR .next
Memory Utilization Heat Chart
Application Response Time
Cell Tower Performance
Drag and Drop
Tivoli Common ReportingConsole
Tivoli Common Reporting
for Asset and Performance Management
Cognos BI Modeling
Cognos BI Reporting
Tivoli Reportingand Analytics Model
Tpae / Maximo
ecosystem DB(TSRM / CCMDB)
Client CGathering customers questions
TPM Data Center Model holds information what is running on each host system (VMWare images running on ESX, etc). This configuration data can easily get out of sync in case of an infrastructure failure (for example one of the hosts with several virtual machines crashes). This is a weak point of current TSAM solution. The report can help administrator to find out if current DCM is up to date and take corrective actions if necessary.
VM Existence Report
In current TSAM solution there is a possibility that some resources will exist without suitable reflection in component databases (VMs without reference to a service, IP addresses reserved but not used). The failure can produce inconsistency between information stored in component databases (TSAM, SRM, TPM) and real state on hypervisors. This set of reports can help identify those orphaned resources.
Orphaned Object Reports
ITM OS Agent
Tivoli Reportingand Analytics Model
which can be included
into the package
What was my system performance before the problem was reported?
What is my system performance after the change introduction?
Incidents / Problems / Changes
can be marked
over utilization chart
Different metrics from ITM
can be visualized on this kind
of chart (disk, memory, etc.)
User can easily examine system
performance (like CPU utilization)
before issue was reported or after
Incidents / problems / changes
can be aggregated within additional
dimensions (defined by data gathered
Which hardware/operating system is causing the biggest number of issues?
Show me CPU/memory/disk usage on the servers that have more than N incidents in the last week.
Different incident / problem /
change facts can be aggregated
are possible here:
Facts from ITM can be
added here as well