IBM Tivoli Netcool Performance Manager, Version 1.3.2
Model Maker 1.2.0
Document Revision R2E1
Getting Started with Common
Reporting Guide
Note
Before using this information and the product it supports, read the information in “Notices” on page 31.
© Copyright IBM Corporation 2011, 2012.
Contents
About this information . . . v
Getting started with Common Reporting
1
Common Reporting on Tivoli Netcool Performance Manager . . . 1Accessing Common Reporting in Tivoli Netcool Performance Manager . . . 1
Common Reporting . . . 2
Web-based report authoring . . . 3
Performing ad-hoc reporting . . . 4
TCR Time contents . . . 4
Reports containing both wireless and wireline data . 7 Getting started with wireline reports . . . 7
Limitation on selecting resources in wireline reports . . . 7
Optimizing the common pack attribute data source to improve report performance . . . 7
Wireline data sources . . . 8
Wireline Report Templates . . . 8
Using the wireline report template . . . 9
Design considerations for wireline report authors 13 Getting started with wireless reports . . . 15
Authoring a simple report . . . 15
Authoring an efficient report . . . 16
Authoring a drill-down report . . . 18
Authoring a charting report . . . 19
Drill-through reports . . . 21
Including multiple granularity items in the same report . . . 25
Known Common Reporting issues. . . 29
Additional resources . . . 29
Books . . . 30
Web Resources . . . 30
Notices
. . . 31
Trademarks . . . 33
About this information
TheIBM Tivoli Netcool®Performance Manager: Getting Started with Common Reporting Guidedescribes how to get started with Common Reporting in Tivoli Netcool Performance Manager.
Getting started with Common Reporting
This information explains how users of Tivoli Netcool Performance Manager wireless and wireline components can get started with Tivoli Common Reporting for network performance management. You are guided through the basic reporting tasks, with particular emphasis on techniques that are unique to performance management.
Tivoli Common Reporting is based on IBM Cognos Business Intelligence, an enterprise reporting solution. It delivers a subset of IBM Cognos Business Intelligence functionality as a common reporting platform across the Tivoli portfolio. By using Model Maker IBM Cognos Edition, you can extend the domain-specific reporting capabilities of technology packs to Common Reporting by deploying common packs on your system.
This information is not a comprehensive guide to Tivoli Common Reporting or IBM Cognos, or a substitute for their respective documentation sets. Rather, it is complementary information that focuses on specific reporting issues for
performance management reporting on telecommunications technology.
Common Reporting on Tivoli Netcool Performance Manager
An overview of Tivoli Common Reporting for Tivoli Netcool Performance Manager users.
Accessing Common Reporting in Tivoli Netcool Performance
Manager
Wireless users access Common Reporting from a separately installed Tivoli Common Reporting interface. Wireline users access Common Reporting in the Tivoli Netcool Performance Manager console. As both applications share the Tivoli Integrated Portal user interface, the basic steps are the same.
Before you begin
Ensure that you have the appropriate login credentials from your administrator.
Procedure
1. Log in to the Tivoli Integrated Portal.
2. In the left navigation, expandReporting>Common Reporting. The Common Reporting tab opens showing you the Working with reports page.
Common Reporting
Use the Common Reporting task to publish, find, manage, organize, and view your organization’s Business Intelligence content, such as reports, scorecards, and
agents. If you have the necessary permissions, you can access the Report Studio and Query Studio or access the administration functions for content
administration, including scheduling and distributing reports, and creating jobs. You view reports in Cognos Viewer.
System administrators also use the portal to administer servers, optimize performance, and set access permissions.
Users of Cognos Connection will be familiar with the Common Reporting task. Cognos Connection is the Web portal for IBM Cognos Business Intelligence 8. It is the starting point to access Business Intelligence information and the functionality of IBM Cognos 8.
For more information, see theIBM® Cognos®8 Business Intelligence Getting Started
Guideat http://publib.boulder.ibm.com/infocenter/c8bi/v8r4m0/topic/ com.ibm.swg.im.cognos.wig_cr.8.4.0.doc/wig_cr.html
Report Studio
Report Studio is a Web-based tool that professional report authors use to build sophisticated, multiple-page, multiple-query reports against multiple databases. With Report Studio, you can create any report that your company requires, such as invoices, statements, and weekly sales and inventory reports.
For more information about Report Studio, see theReport Studio Professional Authoring User Guideat http://publib.boulder.ibm.com/infocenter/c8bi/v8r4m0/ topic/com.ibm.swg.im.cognos.ug_cr_rptstd.8.4.1.doc/ug_cr_rptstd.html.
Query Studio
Query Studio is the reporting tool for creating simple queries and reports in Tivoli Common Reporting.
For more information about Query Studio, see the Query Studio User Guideat http://publib.boulder.ibm.com/infocenter/c8bi/v8r4m0/index.jsp?topic=/ com.ibm.swg.im.cognos.ug_cr_qstd.8.4.0.doc/ug_cr_qstd.html.
Administration
From the Administration component, you can perform server administration, data management, security and content administration, activities management, and portal services administration.
For more information about the Administration component, see the IBM Cognos 8 Administration and Security Guideat http://publib.boulder.ibm.com/infocenter/ c8bi/v8r4m0/index.jsp?topic=/com.ibm.swg.im.cognos.ug_cra.8.4.1.doc/ ug_cra.html.
Web-based report authoring
Create reports in a Web-based tool that professional report authors use to build sophisticated, multiple-page, multiple-query reports against multiple databases. You can create any reports that your company requires, such as invoices, statements, and weekly sales and inventory reports.
Procedure
1. Log in to the Tivoli®Common Reporting interface, and go toCommon Reporting.
2. In the Work with reportswindow on the right chooseReport Studiofrom the Launchdrop-down list. This opens up theReport Studio, a Web-based application.
3. Use the menu controls to create a report or edit existing ones by formatting the layout and manipulating the data that appears in the report.
4. Save your report, and run it at any time.
What to do next
Learn more about Web-based report authoring in Report Studio Professional Authoring User Guideavailable on clickingF1from theReport Studio.
Report Specifications
When you author a report, you actually create a report specification. The report specification is an XML representation of the queries and prompts that are used to retrieve data, as well as the layouts and styles used to present the data. For simplicity, the report specification is called the report.
Report specifications can be useful to report authors for troubleshooting. You can see the XML specification for a report at any time by selecting Tools> Show Specifications from Report Studio.
For information about working with report specifications, see the Report Studio Professional Authoring User Guide.
Models and packages
Because stored data is typically designed for storage and not for reporting, a data modeler uses Framework Manager to create metadata models. A model structures, adds to, and manages data in ways that make sense to business users. For
example, a model defines business rules, data descriptions, data relationships, business dimensions and hierarchies, and other administrative tasks.
Planning and creating a model is an important task that should be performed by a modeler or a modeling team familiar with both the database structure and the needs of the users.
After the metadata model is defined, modelers create a package to make metadata available to report authors. Each package must contain all the information that a specific user or group of users needs to create reports. The Model Maker tooling in Tivoli Netcool Performance Manager simplifies the creation of packages for Tivoli Netcool Performance Manager users.
Generally, each report can contain data from only one package. However, using Model Maker, modelers can combine models and create a single package from multiple models to allow reporting across multiple dimensions.
Performing ad-hoc reporting
Create reports ad-hoc by using simple queries and formatting.
Before you begin
To perform ad-hoc reporting you have to have some report packages imported.
Procedure
1. Log in to the Tivoli Common Reporting interface, and go toCommon Reporting.
2. In the Work with reportswindow on the right choose theQuery Studiofrom theLaunchdrop-down list.
3. Select a package to work with. This opens a Newwindow where you can create the new report.
4. From the navigation on the left drag and drop data items you want to include in your report.
Tip: Change the appearance of the data by using the menu icons at the top.
5. Once your data and appearance is edited, save the report by specifying a Name, and optionally aDescription, and aScreen tip.
Results
You have now created your ad-hoc report.
What to do next
Learn more about authoring the reports in the IBM Cognos Query Studio User Guide.
TCR Time contents
The following timestamp items are available in the TCR Time base common pack.
Day, Hour, Minute
Presentation View Description Oracle Type Oracle function used when populating column
Standard Timestamp Timestamp representing the start of the time period being reported on. Aligns with the granularity of the calendar.
TIMESTAMP loaddatewhereloaddateis the timestamp for the interval we are populating the table with. 01/01/2011 00:00:00
Date Date of the associated calendar entry (that is, midnight of that day).
DATE trunc(loaddate ,'DD')
Year-Month-Day (2012-03-27) VARCHAR(10) to_char(loaddate, 'YYYY-MM-DD') Day Day in the month (1-31). SMALLINT to_char(loaddate,'DD')
YMD-H 2012-03-27 16:00 VARCHAR(16) to_char(trunc(loaddate, 'HH24'), 'YYYY-MM-DD HH24')
YMD-H 30 Min String representation of the 30 minute interval timestamp column for example,
01/01/2011 00:30:00
VARCHAR(16) to_char(ts30, 'YYYY-MM-DD
HH24:MI') wherets30is the loaddate timestamp truncated to a 30 minute interval
30 Minute Current minute integer value of the 30 minute interval timestamp.
SMALLINT to_char(ts30, 'MI')
YMD-H 15 Min String representation of the 15 minute interval timestamp column for example,
01/01/2011 00:15:00
VARCHAR(16) to_char(ts15, 'YYYY-MM-DD HH24:MI') where ts15 is theloaddate
timestamp truncated to a 15 minute interval
15 Minute Current minute integer value of the 15 minute interval timestamp
SMALLINT to_char(ts15, 'MI')
YMD-H 10 Min Current minute integer value of the 10 minute interval timestamp.
VARCHAR(16) to_char(ts10, 'YYYY-MM-DD HH24:MI') wherets10is theloaddate
timestamp truncated to a 10 minute interval
10 Minute Current 30 minute value of the timestamp (50).
SMALLINT to_char(ts10, 'MI') YMD-H 5 Min String representation of the 5
minute interval timestamp column for example, 01/01/2011 00:05:00
VARCHAR(16) to_char(ts5, 'YYYY-MM-DD HH24:MI') wherets5is theloaddatetimestamp truncated to a 5 minute interval 5 Minute Current minute integer value
of the 5 minute interval timestamp.
SMALLINT to_char(ts5, 'MI')
Minute Current single minute value (59).
SMALLINT to_char(loaddate,'MI')
Year, Quarter, Month, Day
Presentation View Description Oracle Type Oracle function used when populating column
Year Year in 4-digit format for example, 2012.
SMALLINT to_char(loaddate,'yyyy') Quarter Quarter of the year (1,
2, 3 or 4).
SMALLINT to_char(loaddate,'Q') Year-Quarter 2010-1 VARCHAR(7) to_char(loaddate, 'YYYY-Q') Month (Numeric) Month (01-12). SMALLINT to_char(loaddate,'mm')
Month Name of the Month. VARCHAR trim(to_char(loaddate,'MONTH')) Year-Month 2010-03 VARCHAR(7) to_char(loaddate, 'YYYY-MM') Days in Month Number of days in the
month (31).
SMALLINT ADD_MONTHS(to_date(TO_CHAR(loaddate, 'yyyymm')||'01', 'yyyymmdd'),1) -to_date(TO_CHAR(loaddate,
'yyyy-mm')||'-01', 'yyyy-mm-dd') Week of Year Week of year (1-53)
where week 1 starts on the first day of the year and continues to the seventh day of the year.
Week of Quarter Week of Quarter (1-13) 13 weeks per quarter.
SMALLINT to_char(loaddate,'ww') -(to_char(loaddate,'Q') - 1)*13 Week of Month Week of month (1-5)
where week 1 starts on the first day of the month and ends on the seventh.
SMALLINT round(to_char(loaddate,'dd')/7 + 1)
whereloaddateis the timestamp interval we are populating.
Weekday Name of the Day. VARCHAR trim(to_char(loaddate,'DAY')) Day of Year Day of year (1-366). SMALLINT to_char(loaddate,'DDD') Day of Week Day of week (1-7). SMALLINT to_char(loaddate,'D')
ISO Year and Week
Presentation View Description Oracle Type Oracle function used when populating column Year (ISO) 4-digit year based on ISO
standard.
SMALLINT to_char(loaddate, 'IYYY') Week (ISO) Week of year (1-52 or 1-53) based
on ISO standard.
SMALLINT to_char(loaddate, 'IW') Year-Week-Day (ISO) Year, week, and Day based on
ISO standard for example, 2012-W13-2.
VARCHAR(10) to_char(loaddate, 'IYYY-"W"IW-') || to_char(floor(loaddate -trunc(loaddate, 'IW')) + 1)
Keys
Presentation View Oracle Type
TIMESTAMP_KEY_5 TIMESTAMP TIMESTAMP_KEY_10 TIMESTAMP TIMESTAMP_KEY_15 TIMESTAMP TIMESTAMP_KEY_30 TIMESTAMP HOUR_KEY TIMESTAMP DAY_KEY TIMESTAMP WEEK_KEY TIMESTAMP WEEK_KEY_ISO TIMESTAMP MONTH_KEY TIMESTAMP QUARTER_KEY TIMESTAMP YEAR_KEY TIMESTAMP YEAR_KEY_ISO TIMESTAMP DATE_KEY_5 DATE DATE_KEY_10 DATE DATE_KEY_15 DATE DATE_KEY_30 DATE DATE_KEY_HOUR DATE DATE_KEY_DAY DATE DATE_KEY_WEEK DATE
DATE_KEY_WEEK_ISO DATE
DATE_KEY_MONTH DATE
DATE_KEY_QUARTER DATE
DATE_KEY_YEAR DATE
DATE_KEY_YEAR_ISO DATE
TIME_RANGE_END DATE
CANDLETIMESTAMP CHAR(16)
END_CANDLETIMESTAMP CHAR(16)
Reports containing both wireless and wireline data
You have the option to install the Common Pack Service so that you can include data from both the wireless and wireline databases in reports.
While you can include both wireless and wireline data in the same report, there is currently no relationship between the data.
Getting started with wireline reports
This information can help you get started with Common Reporting on wireline networks with Tivoli Netcool Performance Manager.
Limitation on selecting resources in wireline reports
A limitation in Tivoli Common Reporting affects the number of resources that you can select in wireline reports. You must not directly select more than 180 resources when authoring reports from Tivoli Netcool Performance Manager models in Report Studio or Query Studio.
Directly selecting more than 180 resources can push the number of characters in your query over a known limit, and cause the report to fail with an error. However, this limitation does not apply when selecting the resources in a group. To select large numbers of resources, use the select alloption on the report prompt page to select all the resources in a group. Then use filtering to select the resources you want.
Alternatively, you can design reports to limit your selection to less than 180 resources.
Optimizing the common pack attribute data source to improve
report performance
For improved performance, it is recommended that you review the common pack attribute data sourceibm.tivoli.tnpm.packname.resourceType.attributeattribute to see if all the properties are required. If some properties are not needed, you can remove them from the data source file.
Removing data sources improves the overall query time for all data sources that require properties. Removing data sources also reduces the amount of temporary space that Tivoli Common Reporting requires to merge the data.
Wireline data sources
Wireline reports use two types of data source, a raw data source or a summary data source.
Raw data source
Raw data is collected on the collection-time interval as configured in the wireline component.
v Snapshot of the value of a metric for a particular timestamp based on
collection interval (example 15 minutes).
v Used to display the detail raw value of a metric for a particular resource
based on the collection interval.
v Timestamp return will be adjusted based on selected time zone in the
prompt page. Summary data source
The summary data source collects 24-hour-data pre-aggregated by Proviso based on the timezone configured on Proviso. There are 5 types of
aggregation available in the summary-datasource, that is:- sum, count, max, min and average.
v Raw Data is pre-aggregated into daily (24 hours) based on the time zone
configured in the wireline component
v Metric value is aggregated into 5 values, MIN, MAX, AVERAGE,
COUNT and SUM.
v Data are always aggregated based on timezone configured in the
wireline component and are not affected by the time zone selected in the prompt page.
Wireline Report Templates
You can use the provided templates to quickly get started with creating reports, without having to build the prompt pages from scratch.
TNPM Wireline Raw Report Template
These report templates replace an older template called TNPM Wireline Report Template, so if you have this older version on your system, do not use it. The default prompt page in this template allows you to select a date and time when generating a report, making it suitable for use with the raw data source. This template is not suitable for the summary data source because summary data source is pre-aggregated into 24 hours so the time do not have any impact to the report and it create confusion.
TNPM Wireline Summary Report Template
The default prompt page in this template allows you to select a date, but not a time, when generating a report and is suitable for the following types of report:
v Raw data source reports that do not need a time selection. For example, the
"Device Health Summary Report" report in ALU 5529 SDC to show raw metrics for a full day in 24 hours.
v Summary data source reports, as the summary data source does not support
time selection.
v Reports with a mixture of raw data source and summary data source. In this
which is how summary data sources are aggregated. This avoids the issue where the raw data source and summary data source results do not match. For
example, the "All KPI Report" mixes both raw and summary data sources.
The default prompt page
The default prompt page in this template allows you to select a date, but not a time, when generating a report and is suitable for the following types of report:
v Raw data source reports that do not need a time selection. For example, the
"Device Health Summary Report" report in ALU 5529 SDC to show raw metrics for a full day in 24 hours.
v Summary data source reports, as the summary data source does not support
time selection.
v Reports with a mixture of raw data source and summary data source. In this
scenario, ensure that no time is selected so data is always in 24 hours blocks, which is how summary data sources are aggregated. This avoids the issue where the raw data source and summary data source results do not match. For
example, the "All KPI Report" mixes both raw and summary data sources.
Using the wireline report template
The following procedure explains how to use the TNPM Wireline Report Template to create a report. In the example procedure, we use the Alcatel 5529 SDC common pack to illustrate the steps. You can modify the charts or tables you need, and delete the rest.
About this task
This task assumes that the Alcatel 5529 SDC common pack package has been published, and that the TNPM Wireline Raw Report Template is available in Common Reporting.
Procedure
1. In the Tivoli Integrated Portal, select Reporting>Common Reporting.
2. On the toolbar, click Launchand selectReport Studio.
3. On the Select a package window, underPublic Folders, select the ibm.tnpm.wireline.commonpackage. Report Studio opens.
4. On the Welcome window, selectOpen an existing report or template.
5. On the Open page, select theTNPM Wireline Raw Report Template and click Open.
6. For this example, we use the Alcatel 5529 SDC package. SelectFile>Report Package.
7. On the Report Package window, Select the ibm.tnpm.alcatel.5529.sdcpackage and clickOK. A prompt window opens. When you open a wireline data model, you are prompted for the values normally provided in the default report prompt screens.
8. On the prompt window, click Canceland on the next window, clickOK. All Alcatel 5529 SDC objects are now available in the Insertable Objectspane.
9. Save the report as Wireline_Test_ReportinMy Folders.
The report template contains a Chart Type section containing charts like the following charts.
The template contains a Table section containing lists (tables) like the following lists.
TheInsertable Objects pane contains the available Alcatel 5529 SDC Key Performance Indicators (KPIs). Expand TNPM alcatel_5529_sdc (Presentation) to show the KPIs.
There are 10 different groups of metrics, divided into raw and summary metrics. Because of the frequency of data collection, raw metrics are suitable for both charts and tables, while summary metrics are best suited for tables.
10. Start by modifying the time series chart. To create a time series report, select one or more raw metrics and drag them to theSeriesdrop box, and select a
timeobject and drag it to thex-axisdrop box. You can also drag an object to populate the y-axis or populate the other annotation fields, such as the x- and y-axis titles.
11. The Tivoli Netcool Performance Manager collection interval can be up to 1 minute, so reduce the time granularity for plotting the chart fromHH:MM:SS toHH:MM. This results in better plotting of results in the chart and avoids overlapping data points caused by the longer collection frequency.
a. Double-click the time object. TheData Item Expresssion - timewindow opens.
b. In the Expression Definitionpane, replace the existing definition with the following definition.
substring(cast([TNPM alcatel_5529_sdc (Presentation)].
[ibm.tnpm.alcatel_5529_sdc.Card.Raw].[time],varchar(30)),1,16) +
IF(extract(hour,[TNPM alcatel_5529_sdc (Presentation)]. [ibm.tnpm.alcatel_5529_sdc.Card.Raw].[time]) < 12) THEN ( ' AM ' ) else ( ' PM ')
Note: There are separate time objects for both Interface and Device, ensure that they are correctly mapped. For example,
ibm.tnpm.alcatel_5529_sdc.Card.Raw and
ibm.tnpm.alcatel_5529_sdc.Ethernet LAG.Raw.
12. You must add a repeater to the chart so that the chart query runs for each resource that you select.
a. Drag a repeater object to the chart box.
b. Modify the repeater properties.
c. Link the repeater to the appropriate query. In this example, we are setting ChartQuery1to repeat for the resource name.
13. The Tablesection contains list items that you can update. From the Insertable Objects pane, drag insertable objects into the list . For example, to create a Card Summary report:
a. ExpandTNPM alcatel_5529_sdc (Presentation)>
b. DragresourceName into the first column.
c. Drag CPU Utilization (max)into the next column.
d. DragMemory Utilization (max) into the next column
14. Return to Common Reporting and click theMy Folderstab.
15. FindWireline_Test_Reportin the list of reports and click the Runbutton to run the report.
16. The template contains a prompt page, that prompts for the time range, the report group, and the resources when running the report. Complete each step in the prompt page, and run the report.
There is a limitation on the number of resources that you can include in a report. Ensure that you do not select more than 180 resources.
Design considerations for wireline report authors
For best results when authoring reports for Common Reporting, keep in mind the following design considerations and limitations.
Be aware of the following behavior:
v The data source test in Tivoli Common Reporting always fails for attribute data
sources, but that does not mean that there is a problem with the data source. The test fails because there is no value for the??group??parameter. The Cognos Servlet indicates that an invalid group name was provided. The??group??
parameter value is normally provided at a prompt page when running the report so is not present when running the data source test function.
v TheTCR Timedimension in wireline common packs supports only a data
granularity of 15 minutes. Therefore, although they are in the data model, do not use theTCR Timeinsertable objects for 10 minute and 5 minute granularity.
v If you include images in your reports, test them thoroughly with the Excel
output.
Time zone limitation for pre-1.3D common packs
This limitation occurs if you develop reports using the report templates, with the new prompt page, delivered in wireline common 1.0.1 BCP for common packs developed prior to 1.3D.
Regardless of what time zone is selected in the new default prompt page, it does not affect the report result. The report still works in GMT, not the time zone selected in the prompt page.
Modifying timestamps in custom charts to round up to minutes
instead of milliseconds
By default, timestamps in reports created by using the wireline data models are rounded up to milliseconds. This task explains how to change the report to round the timestamps up to minutes instead.
About this task
This procedure assumes that time data item found on the Source is inserted into the chart or table in Report Studio as shown. Repeat these steps as required while creating custom charts or tables.
Procedure
1. Double-click on atimedata item. The Data Item Expression window opens.
substring(cast( data_item_path ,varchar(30)),1,16)
where data_item_path is the path of the selected data item. This expression removes seconds and milliseconds, resulting in the display of year-month-day hour:minute only.
3. Save the expression by clickingOK.
Limitations on selecting time ranges for summary data
There are two limitations on how you can select time ranges for summary data.
You must use the default start time for summary data
Wireline reports containing summary data must use the default start time in the prompt page or no summary data is displayed in the report.
To display reports containing summary data for the same start and end date, you must use the default start time of 12:00 AM in the prompt page. If you modify the start time to a value other than 12:00 AM, then no summary data is returned. For example, the following filtering condition on a table or graph containing summary data returns no data.
Start date= April 28 Start time > 1:00AM End date=April 28 End time = > any
You must select time ranges in multiples of one day
SymptomsSummary data is aggregated for one day (24 hours) even if the selected time range is less than one day. Summary data for periods of more than one day, but not a multiple of 24, is aggregated up to the next 24-hour period.
Causes
Summary data cannot show data aggregated for a partial day. Example: Less than 24 hours
For example, if you select a time range of 10 hours as follows: Start Time: 1:00 AM
End Time: 11:00 AM
Raw data is returned for the specified time range of 10 hours. Summary data should be also aggregated for this 10-hour period. However, the summary data is aggregated for one day (24 hours).
Example: More than 24 hours
For example, if you select a time period of 32 hours, the data is aggregated for 48 hours (2 x 24 hours).
Conforming to Cognos reporting guidelines
To conform to the Cognos reporting guidelines, leave table cells with no data blank rather than using a dash (-) to indicate no data.
In wireline reports for previous wireline versions, dashes were used (-) in table cells where there is no data.
Microsoft Excel formatting limitations
When authoring reports, be aware that wireline users can still experience some formatting problems with charts that have a decimal number on the y-axis. These issues are due to formatting limitations in Microsoft Excel 2007.
If this problem occurs, use Report Studio to modify the chart and change the data format property of the y-axis to theNumber with 2 decimal placesoption. Also, be aware that for best results when exporting reports to Excel, users are directed to always select Microsoft Excel 2007. Due to formatting limitations in older versions of Excel, exporting in versions such as 2000 or 2002 can produce incompatible charts. Always ensure that you test your reports in Microsoft Excel 2007.
If you include icons in your reports, test them thoroughly with the Excel export option.
Report titles and labels are displayed in ASCII format
Certain technology packs do not automatically convert theresourceAliasattribute from ASCII format to text. If you are working with reports on one of these packs, titles and labels are displayed as a long ASCII string.
If you are creating Common Reporting reports for one of these technology packs, open Report Studio and modify the affected titles or labels to useresourceName
instead of resourceAlias.
Getting started with wireless reports
This information can help you get started with Common Reporting on wireless networks with Tivoli Netcool Performance Manager.
Authoring a simple report
You can follow these basic steps to create a simple report. This example uses the package created when the Huawei GSM BSS common pack is published.
Procedure
1. In Common Reporting, select a package. In this example, select the Huawei GSM BSS package.
2. On the toolbar, click Launchand selectReport Studio. Report Studio opens.
3. On the Welcome window, selectCreate a new report or template.
4. On the New window, selectList, and clickOK. An empty report opens containing a list (a single row table).
5. Select a Time attribute from the Insertable Objects window and drag it into the list. For best results, use the keys where possible. In this example, drag the TCR Time (Presentation) >Time> Keys>DATE_KEY_HOURkey into the list.
6. Select a primary key or an entity ID and drag it into the list right beside the DATE_KEY_HOURkey. Ensure that your selection is in the list, if a singleton is created, clickUndo and try again. In this example, dragTNPM Mobile GSM (Presentation) ->TNPM GSMCell->CELL_IDinto the list.
7. Select metrics and drag them into the list next to theCELL_IDcolumn. In this example, dragTNPM Huawei GSM BSS V900 Measurements (Presentation) ->TNPM Huawei GSM BSS V900 Measurements Cell Measurements->
Cell.AMR_calls->Cell.Huawei.GSM.AMR_calls-> CALL_DROP_AMRFR_CAll_FAIL_TIMES.
8. Create a prompt page by highlightingCELL_IDand DATE_KEY_HOUR, and clicking the Build prompt pagebutton on the toolbar. The prompt page is automatically generated.
9. Save the report as Simple_ReportinMy Folders.
10. Return to Common Reporting and click theMy Folderstab.
11. FindSimple_Reportin the list of reports and click theRunbutton to run the report.
Authoring an efficient report
The Tivoli Netcool Performance Manager database relies heavily on an Oracle feature called Partition Pruning to efficiently process data. Reports must be defined in a certain way to ensure that Oracle has enough information to identify data partitions.
About this task
You can build a prompt page to ensure that Oracle has the required information to identify data partitions. These steps assume that you have created a list report with 15-minute data by dragging the appropriate report items into the report.
Procedure
1. As this data is 15-minute data, drag theDATE_KEY_15key into the report.
You remove this key later as it is used only as a quick method to build a prompt.
2. Select theDATE_KEY_15column and click the Build Promptpage button on the toolbar. A prompt is created for the report.
3. Return to the report definition page and remove theDATE_KEY_15column by right-clicking and selecting cut. You must remove the key or the report displays only the raw data with the drill up.
Authoring a drill-down report
In this example, we edit theSimple_Reportreport to allow drill up and drill down levels for both time and resource (entity) in the report.
Procedure
1. In Common Reporting, select the package used to create the simple report. In this example, select the Huawei GSM BSS package.
2. On the toolbar, click Launchand selectReport Studio. Report Studio opens.
3. Select Open an existing report or template, selectSimple_Reportand Open.
4. Save the report as Drill_Down_Report.
5. Edit the report to use Cell Hierarchyand Time (Dimensional)by completing the following steps:
a. Delete theCELL_IDand theDATE_KEY_HOURcolumns.
b. In the vertical toolbar beside the Insertable Objects window, point to the Query Explorer button to see Query Explorer and selectQuery1.
c. Delete both filters. to remove the current prompt pages. With the removal ofCELL_ID, andDATE_KEY_HOUR, these filters are no longer useful in the context of this report.
d. Point to Page Explorer button to see the Page Explorer, right-click on Prompt Page1and selectDeleteto delete the prompt page.
e. In Page Explorer, clickPage1to return to the list.
f. Drag the following elements into the list. You can navigate further into the file structure as required.
v TCR Time (Presentation)>Time (Dimensional)>Year>Day v CDM Mobile GSM (Presentation)> CDM GSM>Cell Hierarchy >
Network to Cell>Cell
6. From the main menu, select Data>Drill Behaviour.
7. On the Basictab of the Drill Behaviour window, select the Allow drill-up and drill downoption and clickOK. You can now drill on entity and time when you run this report. If you want, you can also add a filter to restrict the time scope on which the report is displayed, the prompt page is not as useful in this scenario as it would restrict the drilling process.
8. Add a filter to limit the time scope of the report by completing the following steps:
a. In the vertical toolbar beside the Insertable Objects window, point to the Query Explorer button to see Query Explorer and selectQuery1.
b. In the Insertable Objects window, select the Toolboxtab.
c. Drag a filter into the Detailed Filters pane from the Insertable Objects pane . In this example, the filter is set to report on the previous 7 days. In the dialog box for the calculation, insert the following calculation:
[TCR Time (Presentation)].[Time].[DATE_KEY_DAY] > _add_days(current_date, -8) AND
[TCR Time (Presentation)].[Time].[DATE_KEY_DAY] <= _add_days(current_date, -1)
d. For this filter to work, theDATE_KEY_DAYkey must be in the report. DragDATE_KEY_DAYinto the list.
e. TheDATE_KEY_DAYkey does not need to be displayed so you can hide it. Select the title of the column, and in the Properties window, setBox Typeto none, Select the column body and in the Properties window, set Box Typeto none.
9. Save theDrill_Down_Reportreport.
10. Return to Common Reporting and click theMy Folderstab.
11. FindDrill_Down_Reportin the list of reports and click theRunbutton to run the report.
12. When the report viewer has appeared, the entries under Cell and Day should be highlighted, you can click these entries to perform a drill down or you can right-click and select drill up to perform a drill up.
Authoring a charting report
Charts are a graphical representation of tabular data. They can be used to quickly identify large numeric data for different areas of business. They are commonly used in dashboard style reports.
Procedure
1. In Common Reporting, select a package.
2. On the toolbar, click Launchand selectReport Studio. Report Studio opens.
3. On the Welcome window, selectCreate a new report or template.
4. On the New window, selectChart, and click OK. The Insert Chart window is displayed.
5. In the Chart grouplist, select a group. For this example, select Column.
6. In the Chart Typepane, select a chart type. For this example, selectColumn with 3-D Visual Effect.
7. Click OK. A blank chart displays in the work area.
8. A column chart has three drop zones; Default measure (y-axis),Series, and Categories (x-axis).
9. From the Sourcetab in the Insertable Objects pane, drag a data item to the Seriesdrop zone. In this example, we drag the Raw KPI to theSeriesdrop zone.
10. From the Sourcetab in the Insertable Objects pane, drag a TCR data item to the Categories drop zone. In this example, we also include the CELL_ID measure from the Orders query subject in the Default measuredrop zone.
Drill-through reports
Creating drill-through access within a report makes it easier for you to navigate through large reports or to link separate reports containing related information. When you create drill-through access, you can create a bookmark that lets you navigate through a particular dimension of a report or pass a parameter from a source report to a target report. When the drill-through data item value in the source report is selected, the target report opens. The target report is filtered on the parameter that was passed from the source report. This filtering allows you to link separate reports with related information. For the following example, we set up drill-through access using two separate reports: a target report, and a source report.
Authoring a drill-through target report
A target report opens after you click a data item value in a source report. Typically, this report contains related or more detailed information about the source report. Setting up drill-through access gives the user quick access to detailed information without having to navigate through folders to run another report.
About this task
TheMTP3_DSP_IDresource is set up as the drill-through text in the target report. When you click the MTP3_DSP_IDdrill-through text, the target report opens, displaying raw data for KPIs for the MTP3_DSP_IDthat was selected in the source report.
TheDate_Key_Hourkey is added to the report and hidden; it is used in the drill through, but not required in the report.
Procedure
1. Create or open a list report to use as the target report.
2. AddMTP3_DSP_ID,Date_Key_Hour,Date_Key_Hourand raw KPIs columns.
3. Hide theDate_Key_Hourkey in the report:
a. Click the list column body for theDate_Key_Hourdata item and, in the Properties panel, setBox Type = None.
b. Click the list column title for theDate_Key_Hourdata item and, in the Properties panel, setBox Type = None.
4. Save the target report. For this example, save the target report asTest Target report.
What to do next
Create a source report that contains raw data for all resources.
Authoring a drill-through source report
A source report contains the data item value that you can click to drill-through to the target report to view more detailed information.
About this task
To set up the source report to contain the drill-through definition, you need to know the name and location of the target report and the parameter used in the filter of the target report.
Procedure
1. Create or open a list report to use as the target report.
2. AddMTP3_DSP_ID,Date_Key_Hour, and raw KPIs columns.
3. In the work area, select the item to be used as the drill-through. For this example, select MTP3_DSP_IDas the drill-through.
Note: To activate the Drill-Through Definitions option, you must first make a selection in the work area.
4. Click Launchon the toolbar and selectDrill-Through Definitions. The Drill-Through Definitions window is displayed.
5. Click the New Drill-Through Definitionbutton. A new Drill-Through definition is created.
6. UnderReport, choose the target report.
7. Select the target report and click the Openbutton. For this example, select Test Target report.
8. From the Actionlist, select how the target report renders during drill-through.
v Run The Report, runs the report and displays the most recent data.
v View Most Recent Report, displays the most recent saved output version of
the report.
v Default, uses the report action defined in Cognos Connection.
9. From the Formatlist, select the output format for the report when it runs. You can chooseHTML,PDF,Excel 2007,Excel 2002,Excel 2000 Single Sheet, Delimited Text (CSV),XML, andDefault, which uses the output format defined in Cognos Connection.
10. Optionally, select theOpen In New Windowcheck box to open the target report in a new window when it is accessed from the source report. If you do not select this check box, the target report replaces the source report in the Cognos Viewer.
11. Click Editto display details the parameters from the target report. The Parameters window is displayed.
12. From the Methodlist, select the method for passing the parameter. You can choose from Do Not Use Parameter, which does not pass the parameter;Pass Data Item Value, which passes a value from a data item within the source report;Pass Parameter Value, which passes a parameter value from the source report; orDefault, which does not pass the parameter. For this example, select Pass Data Item Value.
13. From the Valuelist, select the Data Item value from the source report. In this example, we useDate_Key_Day andMTP3_DSP_ID.
14. Click OK. The parameters to pass to the drill-through definition display in the Parameters pane on the Drill-Through Definitions window.
15. From the Display Prompt Pageslist, select an option for when to display the prompt pages. The available options are Always,Based On The Default Prompt Settings Of The Target Report, andOnly When Required Parameter Values Are Missing. For this example, selectOnly When Required Parameter Values Are Missing.
16. Click OK. Report Studio updates the report. The data item being used as a drill-through object becomes a hyperlink, and the drill-through icon is displayed.
17. Run the report to test the drill-through. The source report opens in Cognos Viewer and the data items containing the drill-through definition display as hyperlinks that allow you to drill-through to the target report.
18. From the column containing the drill-through definition links, click a
hyperlink. The drill-through target report displays with detailed information about the selected item. In this example, the target report opens and displays detailed information about the raw KPIs for the selected resource and date range.
Including multiple granularity items in the same report
You can include items of multiple granularity in the same report. Use this set of examples and information to help you with this feature.
Displaying multiple granularity items with drill-down only
This example task assumes that you want to display data of multiple granularities in the same report. You can drill up and drill down by time or by resource, in this example, the drill-down is by time. The lowest level of granularity is 5 minutes, the 5-minute timestamp value is displayed in the report. The other data is drilled down to this level.
About this task
Granularity KPI
5 min BSCLOOP_FAIL_APPLY_TRSL_FAIL
10 min IMM_ASS_CH_ALLOC_REQ_SD
15 min PREFER_TCHH_IP_HDLC_TRANS
30 min IMM_ASS_CH_ALLOC_FAIL_SD
60 min TCH_CALL_DROP_TA
The report definition is as follows:
To report correctly, additional information needs to be added to the report:
Procedure
1. From theKeysfolder under the Timesobject, drop and drag theDATEkeys of all the traffic data of a higher granularity.
(As we are reporting at 5 minutes, we drop in the keys for 10, 15, 20, 30, and Hour)
2. Hide those keys in the report:
a. Keeping the Ctrl key pressed, click the column headers and column of each of these keys.
b. In the Properties pane, setBox Type property toNone.
Note: To view these objects again, view the report definition in Page Structure mode: View>Page Structure.
3. Run the report.
Results
The 5-minute data is displayed. The other timestamps are drilled down.
Due to the way Common Reporting displays reports, metrics that have a greater time granularity than the level at which the report is based can show duplicate results. You can avoid these duplicates by using the method detailed in the “UDC calculations and drill downs” on page 27 topic. The UDC is as follows:
if (DATE_KEY_15 = DATE_KEY_HOUR) then ([TCH_CALL_DROP_TA])
else null
Displaying multiple granularity items with drill up and drill down
This example task assumes that you want to display data of multiple granularities in the same report. You can drill up and drill down by time or by resource. Here we are going to create a report with some counters drilled up and some drilled down by time.About this task
Taking the example data in the table, we create a report that reports data at 30-minute intervals. Hence we expect the 5, 10 and 15 minute data to drill up and the hourly data to drill down.
Granularity KPI
5 min BSCLOOP_FAIL_APPLY_TRSL_FAIL
10 min IMM_ASS_CH_ALLOC_REQ_SD
15 min PREFER_TCHH_IP_HDLC_TRANS
30 min IMM_ASS_CH_ALLOC_FAIL_SD
60 min TCH_CALL_DROP_TA
Procedure
1. Drag all the KPIs, CELLID, and 30 minute object into the table. For each object that we want to drill down on, we must include the key for that granularity. Therefore, in this example, we drag in theDATE_KEY_HOURkey.
2. Hide those keys in the report:
a. Keeping the Ctrl key pressed, click the column headers and column of each of the keys.
b. In the Properties menu, setBox Type toNone.
Note: To view these object again, view the report definition inPage Structure mode: View>Page Structure.
3. Run the report.
UDC calculations and drill downs
This example partially replicates the functionality of Tivoli Netcool Performance Manager - Wireless Component. In a drill-down scenario, we create a User Defined Calculation (UDC) that is calculated at run time as the sum of two other
calculations. However, one raw counter has a 5-minute granularity and the other has an hourly granularity. The expected result is that we add the counters together only when the timestamps match, that is, on the hour.
The report result is as follows; we add the hourly column only when the timestamps are equal.
This result is achieved as follows, the method used here avoids problems with data corruption.
Add the following columns to the report: [TNPM Huawei BSS Measurements
(Consolidation)].[Cell.Huawei.Generic.Local_switch_call_drops]. [BSCLOOP_FAIL_APPLY_TRSL_FAIL]
[TNPM Huawei BSS Measurements
(Consolidation)].[Cell.Huawei.Generic.TCH_call_fail_per_cell]. [TCH_CALL_DROP_TA]
When creating the UDC, use the column values rather than the database values. That is, when creating the expression in the Data Item Expression window, choose the metrics from theData Itemstab, rather than theSourcetab.
This method performs the calculation on the visible results in the existing columns, rather than the values taken from the database.
Edit the UDC formula to be something as follows:
IF
( [TCR Time (Presentation)].[Time].[DATE_KEY_5] = [TCR Time (Presentation)].[Time].[DATE_KEY_HOUR] ) THEN
(
[BSCLOOP_FAIL_APPLY_TRSL_FAIL] +[TCH_CALL_DROP_TA] )
ELSE
([BSCLOOP_FAIL_APPLY_TRSL_FAIL] )
Now that the UDC is complete the two metrics you added can be hidden by setting the Box Typeproperty tononein the Properties pane.
If the timestamps match we add the counters together, otherwise we display only the counter from the 5 minute data.
Known Common Reporting issues
Common Reporting in Tivoli Netcool Performance Manager 1.3.2 is based on IBM Tivoli Common Reporting 2.1, which delivers a subset of IBM Cognos Business Intelligence 8.4.1 functionality.
When working with performance management reports in Common Reporting, you might encounter some of the following known limitations or issues. These issues or limitations can be caused by Tivoli Netcool Performance Manager, or by the
underlying IBM Tivoli Common Reporting or IBM Cognos BI products.
Known issues are documented in theKnown Issues with Tivoli Netcool Performance Manager 1.3.2technote in the Support knowledge base at
http://www-01.ibm.com/support/docview.wss?uid=swg21574017.
This technote contains known issues with Model Maker IBM Cognos Edition and Common Reporting on Tivoli Netcool Performance Manager, including installation, Model Maker and Common Pack Service issues, and Common Reporting issues. Other known Common Reporting issues are listed in the Tivoli Common Reporting 2.1 documentation at http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/ index.jsp?topic=/com.ibm.tivoli.tcr.doc_21/ctcr_troubleshooting.html.
Additional resources
Use the following resources to find more information about IBM Tivoli Common Reporting and IBM Cognos Business Intelligence 8.
Community
Service Management Connect (SMC) is a new Integrated Service Management technical community on developerWorks, which connects developers and product experts with clients and partners through blogs, forums, and wikis. Check out SMC for reporting best practices and other useful information.
To access SMC, join the Register and create a developerWorks profile: https://www.ibm.com/developerworks/dwwi/jsp/Register.jsp Join the Network and Service Assurance group at:
https://www.ibm.com/developerworks/servicemanagement/nsa/index.html Monitor the Tivoli Netcool Performance Manager Best Practices page for Common Reporting best practices:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/
home?lang=en#/wiki/Tivoli%20Netcool%20Performance%20Manager/page/Best %20Practices
Books
The following books are available:
v IBM Cognos 8 Business Intelligence: The Official Guideby Dan Volitich. v IBM Cognos 8 Report Studio Cookbookby Abhishek Sanghani.
Web Resources
Check out other useful Web resources for Tivoli Common Reporting.
The Cognos Proven Practices documentation
Created by Cognos experts from real-life customer experiences, Cognos Proven Practices is your source for rich technical information that is tried, tested, and proven to help you succeed with Cognos products in your specific technology environment.
http://www.ibm.com/developerworks/data/library/cognos/ cognosprovenpractices.html
Common Reporting
For more information about using the product or for technical assistance, visit the IBM®Cognos® Resource Center at http://www.ibm.com/software/data/support/ cognos_crc.html. This site provides information about support, professional services, and education.
See the Cognos 8 BI at the information center at http://publib.boulder.ibm.com/ infocenter/c8bi/v8r4m0/index.jsp
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
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: IBM Director of Licensing
IBM Corporation North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing
Legal and Intellectual Property Law IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "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 might not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information 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 use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation 2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM‘s application programming interfaces.
If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at http://www.ibm.com/legal/copytrade.shtml.
Other company, product, and service names may be trademarks or service marks of others.
Additional copyright notices
The following copyright information is for software used by Tivoli Netcool Performance Manager Wireline Component.
Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3
This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing
copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply. IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS
DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE
AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO
OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors
distribute the software in accordance with the terms specified in this license.
SCOTTY Stack
This software is copyrighted by Juergen Schoenwaelder, the Technical University of Braunschweig, the University of Twente, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing
copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply. IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS
DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE
AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN “AS IS” BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO
OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
Various copyrights apply to this package, listed in 3 separate parts below. Please make sure that you include all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001.
Part 1: CMU/UCD copyright notice: (BSD like)
Copyright © 1989, 1991, 1992 by Carnegie Mellon University Derivative Work - 1996, 1998-2000
Copyright © 1996, 1998-2000 The Regents of the University of California All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU
and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Part 2: Networks Associates Technology, Inc copyright notice (BSD) Copyright © 2001, Networks Associates Technology, Inc
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
v Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
v Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
v Neither the name of the NAI Labs nor the names of its contributors may be used
to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 3: Cambridge Broadband Ltd. copyright notice (BSD)
Portions of this code are copyright © 2001, Cambridge Broadband Ltd. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
v Redistributions of source code must retain the above copyright notice, this list of
v Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
v The name of Cambridge Broadband Ltd. may not be used to endorse or promote
products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
BLT 2.4u
Portions (c) 1993 AT&T, (c) 1993 - 1998 Lucent Technologies, (c) 1994-1998 Sun Microsystems, Inc., and (c) 1987-1993 The Regents of the University of California. Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of AT&T, Lucent Technologies Inc., Sun Microsystems, Inc. and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.
THE COPYRIGHT HOLDERS AND OTHER CONTRIBUTORS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR OTHER CONTRIBUTORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
CMU-SNMP 1.14
CMU/UCD copyright notice: (BSD like)
Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this
