tivoli netcool performance manager: modelmaker … ibm tivoli netcool performance manager:...

Tivoli Netcool Performance Manager: ModelMaker User Guide - Wireline Component

Netcool Performance Manager 1.3.1

Document Revision R2E1

Note

Before using this information and the product it supports, read the information in Notices on page 35.

This edition applies to version 1, release 3, modification 1 of Tivoli Netcool Performance Manager for Wireless and to all subsequent releases and modifications until otherwise indicated in new editions.

Copyright IBM Corp. 2007, 2011US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

1 About This Documentation . . . . . . . . . . . . 1Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Required skills and knowledge. . . . . . . . . . . . . . . 1Document conventions . . . . . . . . . . . . . . . . . . . . 1

Blank pages . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Document structure . . . . . . . . . . . . . . . . . . . . . . . 2User Publications . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Starting ModelMaker . . . . . . . . . . . . . . . . . . . . . 5Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Using list operations to generate xml . . . . . . . . . 6

Example list operations . . . . . . . . . . . . . . . . . . 7Example xml . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Creating and modifying universes . . . . . 11Mandatory sets of options . . . . . . . . . . . . . . . . . 11

Tivoli Netcool Performance Manager connection options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Universe options . . . . . . . . . . . . . . . . . . . . . . 13Technology pack options . . . . . . . . . . . . . . . 14

Create Universe scenarios . . . . . . . . . . . . . . . . . 14Specify entities . . . . . . . . . . . . . . . . . . . . . . . 16Specify KPI group names . . . . . . . . . . . . . . . 17Specify raw, summary and SBH data . . . . . . 19

Update Universes . . . . . . . . . . . . . . . . . . . . . . . 20Amend a universe with no database changes 20Split a universe . . . . . . . . . . . . . . . . . . . . . . . 21

4 Technology pack upgrade synchronization . . . . . . . . . . . . . . . . . . . . 23Technology pack upgrade scenarios . . . . . . . . . 23

Synchronizing a universe . . . . . . . . . . . . . . . 24

5 Tivoli Netcool Performance Manager reports in BO 25Universe structure . . . . . . . . . . . . . . . . . . . . . . . 26

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 26Top Level . . . . . . . . . . . . . . . . . . . . . . . . . . . 26BO Calendars . . . . . . . . . . . . . . . . . . . . . . . . 26NC Entities . . . . . . . . . . . . . . . . . . . . . . . . . . 27Raw KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Busy Hour KPIs . . . . . . . . . . . . . . . . . . . . . . 28Summary KPIs . . . . . . . . . . . . . . . . . . . . . . . 28

Using BO to produce Tivoli Netcool Performance Manager reports . . . . . . . . . . . . . . . . . . . . . . . . . 29

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . 29Performance . . . . . . . . . . . . . . . . . . . . . . . . . 29Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . 30Vendor filtering . . . . . . . . . . . . . . . . . . . . . . . 30

Stored Busy Hour reporting . . . . . . . . . . . . . . 30Log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Appendix A: Base xml file . . . . . . . . . . . . . . . 33

© Copyright IBM Corp. 2007, 2011 iii

iv IBM Tivoli Netcool Performance Manager: ModelMaker User Guide - Wireless Component

1 About This Documentation

This guide describes using IBM Tivoli® Netcool® Performance Manager ModelMaker to create and modify universes for use with Business Objects.

1.1 AudienceThis guide is intended for experienced administrators and users who are responsible for creating and maintaining Business Objects universes and for configuring reports.

1.2 Required skills and knowledgeThis guide assumes you are familiar with the following:

• Command line tools• Microsoft® Windows® operating systems• Business Objects XI release 2• Tivoli Netcool Performance Manager for Wireless

1.3 Document conventionsThis document uses the typographical conventions shown in the following table:

Table 1: General Document Conventions

Format Examples Description

ALL UPPERCASE

• GPS• NULL• MYWEBSERVER

Acronyms, device names, logical opera-tors, registry keys, and some data struc-tures.

Underscore See Document conventions For links within a document or to the Inter-net. Note that TOC and index links are not underscored. Color of text is determined by browser settings.

Bold • Note: The busy hour determiner is... Heading text for Notes, and Warnings.

© Copyright IBM Corp. 2007, 2011 1

1.3.1 Blank pages

Blank pages are used at the end of chapters to ensure the following chapter begins on an odd numbered page. These pages are intentionally blank. If the guide is printed double-sided and bound, each chapter will begin on a right-hand page.

1.4 Document structureThis document is organized in to the following chapters:

SMALL CAPS • The STORED SQL dialog box...• ...click VIEW...• In the main GUI window, select the

FILE menu, point to NEW, and then select TRAFFIC TEMPLATE.

Any text that appears on the GUI.

Italic • A busy hour is...• A web server must be installed...• See the User Guide

New terms, emphasis, and book titles.

Monospace • ./wminstall• $ cd /cdrom/cdrom0• /xml/dict• http://company.com/products/• addmsc.sh• Type OK to continue.

Code text, command line text, paths, scripts, and file names. Text written in the body of a paragraph that the user is expected to enter.

Monospace Bold [root] # pkginfo | grep -i perlsystem Perl5 On-Line Manual Pages

system Perl 5.005_03 (POD Docu-mentation)

system Perl 5.005_03

For contrast in a code example to show lines the user is expected to enter.

<Monospace italics>

• # cd <oracle_setup> Used in code examples: command-line variables that you replace with a real name or value. These are always marked with arrow brackets.

[square bracket] log-archiver.sh [-i][-w][-t] Used in code examples: indicates options.

Table 2: Document Structure

Chapter Description

Introduction Introduction to using ModelMaker, starting ModelMaker and using list operations.

Creating and modifying universes Creating and modifying BO universes for use with Tivoli Netcool Performance Manager.

Technology pack upgrade synchronization Technology upgrade outcomes and synchronization tasks.

Table 1: General Document Conventions (Continued)

Format Examples Description

2 IBM Tivoli Netcool Performance Manager: ModelMaker User Guide - Wireless Component

1.5 User PublicationsTivoli Netcool Performance Manager software provides the following user publications:

• release notes• user guides• online help

The documentation is available for viewing and downloading on the infocenter at:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.html

About This Documentation 3

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.html

2 Introduction

2.1 OverviewModelMaker enables users to access Tivoli Netcool Performance Manager databases from Business Objects. ModelMaker is a standalone command line application that provides the following functionality:

• creation of universes• selection of objects to include in a universe• modification of universes• synchronization of universe content following technology pack upgrade

2.2 Starting ModelMakerTo start ModelMaker:

1. In the Windows Start menu, select:

START=>PROGRAMS=>IBM=>TIVOLI NETCOOL=> MODELMAKER

A different location may have been chosen during installation. If a shortcut was created it will be available from the desktop.

The ModelMaker tool is started.


2.3 UsageUSAGE: mm_admin parameters - Create a Universe : [-create optionsXml] - Update a Universe : [-update optionsXml] - List the techpacks : [-list] [-tp optionsXml] [-f dir/outputfile] - List the entities : [-list] [-entities optionsXml] [-f dir/outputfile] - List the kpigroups : [-list] [-kpigroups optionsXml] [-f dir/outputfile]

The following table lists parameters for the mm_admin tool.

Table 3: ModelMaker parameters.

Note: If no output file is specified the operation will overwrite the input file with the output. If the out-put filename given is the same as the input file, the input file will be overwritten. If no location is given for the output file the current directory is used.

2.4 Using list operations to generate xmlUniverse generation options are specified in an .xml file. The file lists the technology pack names, entities and KPI groups to include in the universe. The -list commands are provided to generate lists of technology packs, entities and KPI groups. ModelMaker provides this information in the same xml format that can be used to create or update a universe. KPI groups and entities are chosen to create a universe of a manageable size.

The -list -tp command is used to produce an output file listing all technology packs. This file can be edited to leave only the technology packs that are required for the universe. The resulting file can be used as input for listing entities. This process is repeated so that the xml file is edited to leave only the entities that are required, with the resulting file used as input for listing KPI groups.

Option Description

-create <optionsXml> Create universe specified by the input options file.

-update <optionsXml> Update universe specified by the input options file.

-list -tp <optionsXml> [-f dir/outputfile] List all technology packs on the Tivoli Netcool Performance Manager database. Specify input options file to use to list technology packs. Optional - specify an output file using -f. See Note below.

-list -entities <optionsXml> [-f dir/outputfile]

List all entities available for the technology pack and any dependent technology packs. Specify input options file to use to list entities. Optional - specify an output file using -f. See Note below.

-list -kpigroups <optionsXml> [-f dir/outputfile]

List all KPI groups for all entities specified. Specify input options file to use to list KPI groups. Optional - specify an output file using -f. See Note below.


Note: All dependent GOMs, GOMLets, and technology packs will be included automatically for a spec-ified technology pack.

For all -list operations connection details for the Tivoli Netcool Performance Manager database server are required. These details are specified in the xml file. See Tivoli Netcool Performance Manager connection options.

When ModelMaker is installed, a default .xml file is created with parameters for Tivoli Netcool Performance Manager database and BO connections. This file can be used as a starting point for creating an input .xml file.

2.4.1 Example list operations

To list technology packs for a specified Tivoli Netcool Performance Manager database:mm_admin -list tp myoptions.xml -f myoptions_tp.xml

To list entities for specified technology pack(s):mm_admin -list entities myoptions_tp.xml -f myoptions_entities.xml

To list KPI groups for specified entities:mm_admin -list kpigroups myoptions_entities.xml -f myoptions_groups.xml

2.4.2 Example xml

List technology packs example input - myoptions.xml<options><tnpmw>

<name>connection1</name><host>hostname.locale.com</host><port>1521</port><sid>VTDB</sid><user>virtuo</user><password>password</password><service>vtdb</service>

</tnpmw></options>

Introduction 7

List technology packs example output and list entities input - myoptions_tp.xml<options>

<tnpmw>

<name>connection1</name>

<host>hostname.locale.com</host>

<port>1521</port>

<sid>VTDB</sid>

<user>virtuo</user>

<password>password</password>

<service>vtdb</service>

</tnpmw>

<techpacks>

<techpack name="Nokia UMTS UTRAN"/>

</techpacks>

</options>

List entities example output and list KPI groups input - myoptions_entities.xml<options>

<tnpmw>



<port>1521</port>

<sid>VTDB</sid>

<user>virtuo</user>



</tnpmw>

<techpacks>


</techpacks>

<entities>

<entity name ="Cell" all="false"/>

<entity name ="BSC" all="false"/>

</entities>

</options>


List KPI groups example output - myoptions_groups.xml<options>

<tnpmw>



<port>1521</port>

<sid>VTDB</sid>

<user>virtuo</user>



</tnpmw>

<techpacks>


</techpacks>

<entities>

<entity name="Cell">

<group name="Nokia.rab.active_failures_ps"/>

<group name="Nokia.rab.access_complete"/>

</entity>

<entity name="BSC">

<group name="Nokia.rab.cell_failures_ps"/>

</entity>

</entities>

</options>

Introduction 9

3 Creating and modifying universes

3.1 Mandatory sets of optionsA base xml file is provided with ModelMaker for universe creation. See Base xml file. Mandatory sets of options are required in the input xml for ModelMaker -create and -update operations. These are:

• connection parameters• universe details• technology packs

The following is an example of mandatory ModelMaker options:<options>

<tnpmw><name>connection1</name><host>host.location.com</host><port>1521</port><sid>VTDB</sid><user>virtuo</user><password>password</password><service>vtdb</service>

</tnpmw><universe>

<server>csmserver.location.com</server><port>6400</port><user>username</user><password>password</password><auth_type>Enterprise</auth_type><folder>my_folder_1</folder><universe_name>my_universe_1</universe_name><maxObjects>2000</maxObjects><dateFormat>dd/mm/yyyy HH:mm</dateFormat>

</universe><techpacks>

<techpack name="Nokia UMTS UTRAN"/></techpacks><entities>

<entity_name="BSC"></entities>

</options>


3.1.1 Tivoli Netcool Performance Manager connection options

The connection element of the xml specifies how ModelMaker connects to the Tivoli Netcool Performance Manager database.

Tivoli Netcool Performance Manager database connection details are illustrated by the following example:

<tnpmw><name>connection1</name><host>host.location.com</host><port>1521</port><sid>VTDB</sid><user>virtuo</user><password>password</password><service>vtdb</service>

</tnpmw>

Where:

• name - is the connection name• host - is the Tivoli Netcool Performance Manager database server host name• port - is the Tivoli Netcool Performance Manager database server port number, optional -

normally 1521• sid - is the system identifier (SID), optional - normally vtdb• user - is the Tivoli Netcool Performance Manager database username, optional - normally virtuo• password - Tivoli Netcool Performance Manager database password• service - Tivoli Netcool Performance Manager database TNS name as defined on the CMS server

ModelMaker uses these parameters for two purposes:

• to connect to the TNMPW database for universe generation • to specify the connection parameter of the generated universe

When creating a new universe, ModelMaker analyses the list of registered BO datasource connections, and:

• if a connection with the specified name, in this example - connection1, does not exist, ModelMaker will create one and assign it to the new universe

• if a connection with the same name already exists, ModelMaker verifies that the connection parameters of the existing connection match the user properties and if not, exits with an error. If connection parameters match, ModelMaker will assign the connection to the new universe


3.1.2 Universe options

ModelMaker only operates with the BO Central Management Server (CSM). To allow ModelMaker to connect to CSM, the following details must be provided:

<universe><server>csmserver.location.com</server><port>6400</port><user>username</user><password>password</password><auth_type>Enterprise</auth_type><folder>my_folder_1</folder><universe_name>my_universe_1</universe_name><maxObjects>4000</maxObjects><dateFormat></dateFormat>

</universe>

Where:• server - is the CSM server name• port - is the CSM server port number• user - is the CSM server username• password - is the CSM server password• auth_type - is the CSM authentication type, ModelMaker supports the following types:

• Enterprise• LDAP

• folder - is the universe location • universe_name - is the universe name• maxObjects - is the maximum number of objects permitted in the universe, this is optional. The

default is 2000. If this threshold is exceeded the operation will fail.• dateFormat - is the date format, this is optional. The default format is dd/mm/yyyy HH:mm. This

format applies to all date elements, including timestamps. The format can be changed to any format supported by BO. Consult your BO documentation for information on date formats.

For the selected options, ModelMaker will generate a universe with the name specified, on the CSM server under the folder specified. A folder must be specified. If the specified location folder does not exist, ModelMaker will not create a new one, but the universe will be created in server root folder.

If a universe with the same name already exists in the specified folder and if -create is being used, ModelMaker will exit with an error and a decision must be made whether to replace the existing universe or not. If the universe is to be replaced, the existing universe must first be manually removed.

Note: The use of a .<number> in a universe’s name is not supported. For example, <universe_name>Universes4c258.1</universe_name> is not supported.

Creating and modifying universes 13

3.1.3 Technology pack options

The technology packs to be included in the universe must be specified. There is no limit to the number that can be used for a universe. However, the size and maintainability of the resulting universe should be considered. A single technology pack with a sub-set of entities per universe is the norm, unless cross technology pack reports are required.

An example technology pack is specified below:<techpacks>

<techpack name="Nokia UMTS UTRAN"/></techpacks>

3.2 Create Universe scenariosThe scenario examples in this section build on the mandatory options. See Mandatory sets of options. The following table lists all possible options.

Table 4: xml options

Option set Mandatory Default Comment<tnpmw> Yes

<name> Yes<host> Yes<port> Yes 1521<sid> No vtdb<user> Yes virtuo<password> Yes<service> No

<universe> Yes<server> Yes<port> Yes<user> Yes<password> Yes<auth_type> Yes<folder> Yes<universe_name> Yes<maxObjects> No 2000<dateFormat> No dd/mm/yyyy

HH:mm<techpacks> Yes <techpacks all="true"/> can be used to specify all

technology packs.<techpack_name> Yes

<entities> No <entities all="true"/> can be used to specify all entities for a technology pack.

<entity_name> No <entity_name="all="true"/> can be used to specify all groups for an entity. For example: <entity_name="BSC" all="true"/>


If only mandatory options are specified, ModelMaker will apply default values for all other options. That is, it will generate all entities in the network hierarchy of the specified technology packs, and will include raw KPIs only. Only raw KPIS are generated by default. Daily/weekly/monthly measures for summaries and SBHs are not generated unless specified.

However, such a universe is likely to be very large and difficult to maintain. Limiting the number of entities (NC elements) and KPI groups will effectively reduce the size of the universe. The following sections describe the additional options that are used to specify the content of a universe.

<group_name> No<kpis> No

<raw> No Default is 15. The lowest level of granularity that can be reported on can be specified in minutes for raw data reporting. For example:<raw granularity="5">

<generate> No true<summaries> No

<daily> No false<weekly> No false<monthly> No false

<sbh> No Default is 60. The time boundary for busy hours can be specified. For example, for a sliding busy hour beginning at 15 minutes past the hour:<sbh granularity="15">

<daily> No false<weekly> No false<monthly> No false

Table 4: xml options

Option set Mandatory Default Comment


3.2.1 Specify entities

By default, no entities are included in a universe for the specified technology pack(s). A set of entities must be specified for a technology pack.

The -list parameter can be used to obtain entity names. For example:mm_admin -list -entities my_options1.xml -f my_options2.xml

where

• my_options1.xml - contains the set of technology packs to list entities for• my_options2.xml - is the output file ModelMaker will generate as the result of the list

operation.

The following xml illustrates how a set of entities can be specified:<options>

<tnpmw>....</tnpmw><universe>....</universe><techpacks>


<entity name="Network"/><entity name="Region"/><entity name="RNC"/><entity name="NodeB"/><entity name="Cell"/>

</entities>

To create a universe for this configuration the -create parameter is used. For example:mm_admin -create my_options1.xml

This will generate a new universe that will contain all raw KPIs for the five entities for the specified technology pack (and dependencies). Raw KPIs are generated for entities by default. Daily/weekly/monthly measures for summaries and SBHs for the five entities are not generated by default, and must be specified. Including or excluding raw KPIs can also be specified. See Specify raw, summary and SBH data.

Entity names are case insensitive. Entity names as specified in the Tivoli Netcool Performance Manager database must always be used. Top-level entities are not created by default. For example, if an entity Cell is specified its parents (NodeB, RNC, etc,.) will not be created automatically.


3.2.2 Specify KPI group names

By default, no KPI groups are included in a universe for the specified entities. The content of a universe can be limited further by specifying which KPI groups to include. The exact KPI group names must be used. The -list parameter is used to obtain KPI group names. For example:

mm_admin -list -kpigroups my_options2.xml -f my_options3.xml

where

• my_options2.xml - contains the set of entities to list KPI group names for• my_options3.xml - is the output file ModelMaker will generate as the result of the list

operation.

For example, to obtain KPI groups for the entity Cell for a specified technology pack, my_options2.xml may contain the following:

<options>......<techpacks>


<entity name="Cell"/></entities>

</options>

The resulting output in my_options3.xml would contain all KPI groups for the specified entity, for example:

<options>...<techpacks>


<entity name="Cell"><group name="Nokia.RAN_Accessibility.Service_Level"/><group name="Nokia.RAN_Accessibility.Traffic"/><group name="Nokia.RAN_Integrity.RCPM"/><group name="Nokia.RAN_Mobility.InterSystem_Handover"/>...<group name="Nokia.cell_busy_hour_kpi"/>...<group name="Nokia.wbts_wn3.mac_hs_transmit"/>

</entity></entities>

</options>

If no entity names are specified in the input xml then all group names for all entities will be listed in the output file.


In the BO universe SBH UDCs are grouped with other SBH KPI, and summary UDCs are grouped under the predefined group: User Defined Calculations. UDCs are grouped by entity.

In the xml options file UDCs are listed for the entity they have been created under. For example, a UDC Counter_BSC_UDC exists for the entity BSC, and will appear grouped under that entity:

<entity name="BSC" all="false"> <group name="Counter_BSC_UDC"/> <group name="Ericsson.Ater_Interface"/> <group name="Ericsson.GPRS_EGPRS_QoS"/>

The required group names can now be copied to the options file to create a universe, for example:mm_admin -create my_options4.xml

Where the configuration file my_options4.xml contains details of the technology pack, entities and KPI groups to use to create the universe, for example:

<options> <connection name="my_connection_1">

... </connection> <techpacks>

<techpack name="Nokia UMTS UTRAN"/> </teckpacks> <entities>

<entity name="Network"/><entity name="Region"/><entity name="RNC"/><entity name="NodeB"/><entity name="Cell">

<group name="Nokia.traffic.dch_duration_cs_voice_calls.drnc"/><group name="Nokia.traffic.dch_duration_cs_voice_calls.srnc"/><group name="Nokia.traffic.dch_duration_data_calls_dl.drnc"/><group name="Nokia.traffic.dch_duration_data_calls_ul.drnc"/>

</entity></entities>

</options>


3.2.3 Specify raw, summary and SBH data

By default, ModelMaker generates only raw KPIs by default. Including summary or SBH data must be specified. Raw data, summaries or SBHs, for daily, weekly and monthly measures can be included or excluded. For example:

...<entities>...</entities>

<kpis><raw granularity="30">

<generate>false</generate></raw><summaries>

<daily>true</daily><weekly>false</weekly><monthly>false</monthly>

</summaries><sbh granularity="60">

<daily>true</daily><weekly>false</weekly><monthly>false</monthly>

</sbh></kpis>

</options>

Granularity - raw

The lowest level of granularity that can be reported on, can be specified in minutes for raw data reporting. For example:

<raw granularity="5">

is reflected in the BO Raw Calendars available

Granularity - stored busy hours

If SBHs use sliding busy hours the time boundary for sliding busy hours must be specified. A sliding busy hour is a busy hour that is calculated based on the busiest hour of the day, across intervals other than hourly boundaries. For example, from 10:15 to 11:15 or 10:30 to 11:30. The time boundary for sliding busy hours is set in minutes.


For example:<sbh granularity="15">

sets the time boundary for sliding busy hours to 15 minutes passed the hour.

3.3 Update Universes

3.3.1 Amend a universe with no database changes

This section covers scenarios where no database changes have occurred since a universe was last generated and all that is required is to amend the universe.

For example, a universe contains all raw and daily/weekly/monthly measures for summaries and SBHs. To remove raw counters from the existing universe the options file can be modified by amending a section to ignore the generation of raw counters. For example:

<options>...</entities>


<generate>false</generate></raw><summaries>

<daily>true</daily><weekly>true</weekly><monthly>true</monthly>


<daily>true</daily><weekly>true</weekly><monthly>true</monthly>

</sbh></kpis>

</options>

Having modified and saved the options file, the file is updated and the universe re-generated. For example:

mm_admin -update my_options1.xml

This results in raw counters being deleted from the universe. Users will no longer be able to report on raw counters. No other changes occur to existing elements in the universe. The internal structure of other BO classes will not be changed and all non raw data user reports will continue to work on the universe as before the modification.

Using the same approach it is possible to exclude or include entities, KPI groups and summaries/SBHs.

Note: If an element is deleted from a universe and then added back in, the internal BO presentation of the element will be likely to change and previous user reports may be affected.


3.3.2 Split a universe

This scenario explains how to duplicate and modify an existing universe. In this example a single large universe is split in to four smaller universes for raw, daily, weekly, and monthly reports.

To achieve this:

1. Import the universe from the CSM repository in to a local file system.

This can be done using the BO Designer application. For information on using BO Designer, refer to your Business Objects documentation.

2. Using BO Designer change the name of the universe.

3. Close the universe in BO Designer and rename the configuration file.

4. Export the renamed universe back to the CSM repository.

5. Using ModelMaker modify the new options file as required.

6. For example:<options>

<universe>....<folder>my_folder_1</folder><universe_name>my_universe_1_part1</universe_name>

</universe><entities>...</entities>


<generate>true</generate></raw><summaries>

<daily>false</daily><weekly>false</weekly><monthly>false</monthly>


<daily>false</daily><weekly>false</weekly><monthly>false</monthly>

</sbh></kpis>

</options>

7. Using ModelMaker, generate the new universe. For example:mm_admin -update my_options1_part1.xml

8. Repeat Step 1 through to Step 7, as required.


4 Technology pack upgrade synchronization

4.1 Technology pack upgrade scenariosFollowing the upgrade of a technology pack for Tivoli Netcool Performance Manager a number of outcomes are possible. For example, the upgraded technology pack may include a number of new KPIs or the removal of a number of KPIs from the technology pack. This in turn will have an impact on any universe using the upgraded technology pack.

Note: The command for modifying a universe and synchronizing a universe after a technology pack upgrade, are the same.

The possible technology pack upgrade scenarios are described in the following table.Table 5: Possible technology pack upgrade scenarios

Upgrade Scenario BO Upgrade Scenario Impact on existing reports

Add NC element Add NC element No Impact.

Add NC attribute Add NC attribute

Add KPI Group Add KPI Group

Add KPI Add KPI

Rename NC attribute Rename NC attribute The logical name on the existing reports will be changed.All related reports will be updated with new names.

Rename KPI Group Rename KPI Group

Rename KPI Rename KPI

Delete NC attribute Delete NC attribute Reports related to the deleted ele-ment will fail.Delete KPI Group Delete KPI Group

Delete KPI Delete KPI

Column Type Correction (correction of column type, precision and size)

N/A No Impact.


4.1.1 Synchronizing a universe

To synchronize a universe following a technology pack upgrade, use the -update parameter. For example:

mm_admin -update my_options1.xml

This produces an updated modelmakerUpdate.log which records any changes to the universe. Log files are located in the log folder in the ModelMaker installation directory.

<install directory>/log

The modelmakerUpdate.log must be consulted for changes to the universe. It is then necessary to manually amend the input options.xml file with the changes in the log file, and modify the universe using the -update command. For example:

mm_admin -update my_options1_1.xml

NC Column Transfer(within the same NC table)

N/A No impact, however users will be notified that the old column will no longer have data and another column shall be used instead.

Traffic Column Transfer(within the same table or across two tables with update of the corresponding Traffic Tables, SBH and Summary)

N/A

KPI Data Copy (across two tables) Move KPI from one group in to another group.

NC Entity Merge (within the same table)

N/A

Table 5: Possible technology pack upgrade scenarios

Upgrade Scenario BO Upgrade Scenario Impact on existing reports


5 Tivoli Netcool Performance Manager reports in BO

This chapter provides information on the production of Tivoli Netcool Performance Manager reports in BO. This chapter includes the following topics:

• Universe structure• Using BO to produce Tivoli Netcool Performance Manager reports• Log files


5.1 Universe structure

5.1.1 Introduction

This chapter explains how a generated universe is structured. This chapter offers an overview of the content of the Universe Pane of the BO Designer.

5.1.2 Top Level

The following top level navigation nodes will appear in BO Designer.

5.1.3 BO Calendars

The BO Calendars node contains all the calendars required to build contexts for raw, SBH and Summary KPIs. The default date format is dd/mm/yyyy HH:mm. In order to support the correct time aggregation, separate calendar views are created.


5.1.4 NC Entities

The NC Entities node contains all the entities for the universe in alphabetical order.

NC attributes

Each Entity node contains all the NC attributes for the entity.

5.1.5 Raw KPIs

Each Raw KPI node contains Raw KPI Group nodes.

Raw KPI groups

Each Raw KPI Group node contains raw KPIs for that group.

Tivoli Netcool Performance Manager reports in BO 27

5.1.6 Busy Hour KPIs

The Busy Hour KPIs node contains Daily, Weekly and Monthly nodes. A User Defined Calculations node will appear for UDCs under each of the Daily, Weekly and Monthly nodes. UDCs are not available for Raw KPIs.

5.1.7 Summary KPIs

The Summary KPI node contains Daily, Weekly and Monthly nodes. A User Defined Calculations node will appear for UDCs under each of the Daily, Weekly and Monthly nodes.


5.2 Using BO to produce Tivoli Netcool Performance Manager reports

5.2.1 Restrictions

Alarms

Reporting of Tivoli Netcool Performance Manager alarms is not supported in ModelMaker.

Single user mode

ModelMaker supports single user mode only. Single user mode means that only one user can connect to the Tivoli Netcool Performance Manager database for use with BO.

Tivoli Netcool Performance Manager objects and classes in BO

Users can create new classes and move objects in BO. Users can also create their own objects and classes etc,. Moving objects from one generated class to another generated class is not supported. Generated objects and classes cannot be modified.

Following a universe upgrade all objects that have been moved will be deleted, with the exception of objects moved to top level folders.

Raw reporting on UDCs

Raw reporting on UDCs is not available. UDCs are supported for SBH and summaries only.

5.2.2 Performance

Calendars

Time filtering

Use CALENDARS, and not TSTAMP under a KPI group for time filtering. This simplifies reports across KPI groups.

When specifying a time filter use the lowest time interval for filtering.

For example, for data using a 15 minute interval, use the 15-min object under the Calendar class even if you are selecting daily data:

• Do not use: CalDay = '1 Jan 2009'• Do use: Cal15Min between '1 Jan 2009 00:00' and '1 Jan 2009 23:59'

Better structured queries and performance are achieved using Calendars and finer granularities of time intervals.

Cross-group reporting

When performing a cross-group report the join of the query is performed on the CMS server side with the universe parameter JOIN_BY_SQL set to No. This parameter can be reset to Yes to force the joining of sub-queries on to the database side. This will improve performance.


Refer to your Business Objects documentation for more information.

Note: This applies to reports using raw and summary data only. Changing the parameter JOIN_BY_SQL set to Yes will have a negative impact on SBH reports. Separate universes would be necessary for raw and summary, and SBH reports.

Universe size

The maximum default size of a universe is 2000 objects. Large universes can lead to a significant degradation in performance. It is recommended that the size of a universe on a moderately specified system should not exceed 10,000.

5.2.3 Aggregation

Aggregation over time and entity

Tivoli Netcool Performance Manager supports aggregating over time and aggregating over entity. If a report is aggregated over time, values in a report can be "rolled up" by an interval of time. For example, 15 minute data can be rolled up to a day. If a report is aggregated over element, values in a report can be rolled up by element. For example, data for cells can be rolled up to a BSC.

In Tivoli Netcool Performance Manager KPIs most often use the same aggregation type for both time and entity, but this is not always the case. In BO only aggregation over time is supported. Where a KPI has different aggregation for time and entity, aggregation for time is used.

Null aggregation

Null aggregation is not supported in BO. See SBH - Null aggregation.

5.2.4 Vendor filtering

Because traffic tables have no vendor id, the only method that can be used to filter vendor specific data is using a KPI group’s NC parent.

Use Entity attributes from the NC ENTITIES class, and not IDs under a KPI group for entity filtering.

• Do not use: cell_id from a KPI group• Do use: NC Entities>>Cell>>cell_id dimension

5.2.5 Stored Busy Hour reporting

Parent focal entities

If a SBH query is created where the entity id of the SBH is higher then the SBH determiner entity (the SBH determiner is being rolled up), incorrect values will be returned for the determiner.

This issue can be worked around by creating two queries on the same web intelligence document. One for the SBH determiner KPI only, and one for the associated KPIs. The results of both queries can be copied in to one report where the contexts would be:


• for the SBH determiner - BH DETERMINER ONLY

• for the associated KPI values, context name to match the SBH name

Ranked stored busy hour reports

SBH rank uses Sum Aggregation, therefore you cannot filter a SBH report by rank.

SBH - Null aggregation

Null aggregation is not supported in BO. Any KPI in Tivoli Netcool Performance Manager with Null aggregation will have its aggregation set to SUM in BO. In BO this will be most noticeable in ranking reports.

In ranking reports where rolling up (aggregating) the values of KPIs is used, ranked values will be summed and not ranked.

If a universe is created with a SBH RANK measure, the rank value will be summed when it is rolled up to its parent entity. This also happens for values rolled up over time. For example:

Time Rank ValueDay1 13:00 1 50Day1 14:00 2 20Day1 22:00 3 10Day1 03:00 1 50Day1 11:00 2 20Day1 14:00 3 10

On roll up to a week, the values will appear as:

Time Rank ValueWeek 1 12 160

It is recommended that the BH RANK measure is not used in rolled up reports.

Determiners

When creating a SBH report, the determiner must be included in the report. The determiner filters all existing SBH data for the SBH definition.

When creating a report on a SBH determiner only, the user must select the following context: (sbh_busy_hour_daily <entity level>).

Contexts

ModelMaker attempts to generate optimal contexts for each SBH definition. However, contexts can override each other when the same KPIs are used in several SBH definitions. BO may request that you choose a proper context for your query. Context names correspond closely to SBH definition names, so choosing a context should be straightforward.


This may occur:

• in a universe where KPI groups contain only SBH determiner KPIs, and not SBH value KPIs.• in a SBH report containing only the SBH determiner KPI and not the SBH value KPIs.

For example, if a SBH report has only the SBH determiner KPI, choose a default BH DETERMINER ONLY context from one of the following:

• daily BH - DBH Sbh Busy Hour Daily <focal entity name>• weekly BH - WBH Sbh Busy Hour Daily <focal entity name>• monthly BH - MBH Sbh Busy Hour Daily <focal entity name>

For example, DBH Sbh Busy Hour Daily Cell.

5.3 Log filesModelMaker produces the following two log files:

• modelmaker.log - contains error and troubleshooting information.• modelmakerUpdate.log - contains information on any changes following updating or

synchronizing a universe. The purpose of this log is to inform users how their reports might be affected following changes to a universe.

Log files are located in the log folder in the ModelMaker installation directory.<install directory>/log

The logging level for the modelmaker.log can be changed by amending the log’s threshold in the following file:

<install directory>/components/config/log4j.properties

For example, to change the logging level to DEBUG:log4j.appender.FILE=org.apache.log4j.RollingFileAppenderlog4j.appender.FILE.Threshold=DEBUGlog4j.appender.FILE.File=./log/modelmaker.log.....

There are three threshold settings: DEBUG, INFO and ERROR. DEBUG level can adversely impact performance.


Appendix A : Base xml file

A.1 xml file content<?xml version="1.0" encoding="UTF-8"?><options>

<tnpmw><name></name><host></host><port>1521</port><sid>VTDB</sid><user>virtuo</user><password></password><service></service>

</tnpmw> <universe>

 <server></server>

 <port>6400</port>

 <user></user>

 <password></password>

 <auth_type>Enterprise</auth_type>

 <universe_name></universe_name>

 <folder></folder>     </universe> <kpis> <raw granularity="30"> <generate>true</generate>

</raw> <summaries> <daily>false</daily> <weekly>false</weekly> <monthly>false</monthly> </summaries> <sbh granularity="60"> <daily>false</daily> <weekly>false</weekly> <monthly>false</monthly> </sbh> </kpis></options>


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 grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785,U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.3-2-12, Roppongi, Minato-ku, Tokyo 106-8711Japan

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 may 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 Corporation5300 Cork Airport Business ParkKinsale RoadCorkIreland.

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 measurements 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.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.


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.

If you are viewing this information in softcopy format, the photographs and color illustrations may not appear.

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 www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

37

Printed in the Republic of Ireland

IBM


tivoli netcool performance manager: modelmaker … ibm tivoli netcool performance manager:...

Documents