IBM. Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

Transcription

1 IBM Tivoli Netcool Performance Manager Tivoli Netcool Performance Manager - Application Studio Document Revision R2E1 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide IBM

2 Note Before using this information and the product it supports, read the information in Notices on page 91. Copyright IBM Corporation 2015, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents About this information v Intended audience v Service Management Connect v Tivoli Netcool Performance Manager technical training v Support information v Conventions used in this publication vi Typeface conventions vi Chapter 1. Introduction Tivoli Netcool Performance Manager - Application Studio components Organization Chapter 2. Software requirements and prerequisite software Supported configurations Prerequisites for installing Tivoli Netcool Performance Manager - Application Studio tools.. 6 Chapter 3. Configuring the prerequisite software on the server Creating the nasaccess user Configuring Tivoli Common Reporting for Oracle database Configuring the nasaccess data source for Oracle connection Starting Jazz for Service Management application servers Stopping Jazz for Service Management application servers Configuring the nasaccess data source Chapter 4. Installing and configuring IBM Cognos Framework Manager Configuring IBM Cognos Framework Manager connections (Optional) Configuring Framework Manager Oracle connection Chapter 5. Installing the Tivoli Netcool Performance Manager - Application Studio TCR Time schema installation scripts Installing the TCR Time schema WirelessModelling tool Opening WirelessModelling tool Configuring WirelessModelling tool CreateModel tool Location of the CreateModel script file Installing Resource Metric Viewer Creating a logins file with appropriate passwords 22 Uninstalling Resource Metric Viewer Chapter 6. Creating Tivoli Netcool Performance Manager common pack data models Overview of creating Tivoli Netcool Performance Manager common pack data model for Wireless pack modelers Creating a Tivoli Netcool Performance Manager common pack data model containing a raw data model Creating a Tivoli Netcool Performance Manager common pack data model containing a summary definitions model Creating a Tivoli Netcool Performance Manager common pack data model containing a busy hour definitions model Data model filtering Filtering metrics from a model in an existing CIF file Filtering intervals from existing CIF files Creating a model properties file Generating the Tivoli Netcool Performance Manager common pack data model contents Publishing a Tivoli Netcool Performance Manager common pack data model Opening a project in Framework Manager Chapter 7. Getting started with Common reporting Chapter 8. Resource Metric Viewer Resource Metric Viewer setup Enabling the Resource Metric Viewer with existing Tivoli Netcool Performance Manager common pack data models Active Event List Using the Resource Metric Viewer Logging in to the reporting interface Constructing a report by selecting a subset of resources and metrics Constructing a report based on KPI comparisons 49 Removing the saved selections from Resource Metric Viewer Selection page Configuring launch-in-context Active Event List on Resource Metric Viewer User-Defined Counters for reporting Creating user-defined counters Updating user-defined counters Viewing user-defined counters Deleting user-defined counters Importing and exporting a UDC Limitations in using UDCs in Resource Metric Viewer reports Resource Metric Viewer administration Modify the Resource Metric Viewer template.. 63 Copyright IBM Corp. 2015, 2017 iii

4 Chapter 9. Data availability reporting 65 Overview of generating data availability reports.. 65 Monitoring the key traffic tables for data availability 66 Selecting tables for data availability for a vendor neutral technology pack Selecting tables for data availability for a vendor specific technology pack Generating data availability components Data availability formulas Data availability summaries Provisioning the UDCs and summaries to Tivoli Netcool Performance Manager Wireless system. 73 Extracting and publishing daily summary model 74 Scheduling and running summaries Generating data availability reports Publishing the generated data availability reports. 79 Verifying the data availability report contents Creating data availability summary report Chapter 10. Troubleshooting Tivoli Netcool Performance Manager - Application Studio and Common reporting Data values that are displayed in the report do not match with the columns in the database Restrict the number of KPIs used in creating a report from a Tivoli Netcool Performance Manager common pack data model Reporting fails with sort key too long error from a busy hour data model Manually edit the summary name in a data availability model if the summary name exceeds 24 characters Issues with rehomed data in the parent entity level in Data Availability Reports Issues with Resource Metric Viewer report with charts and tables that is exported to PDF Data values are not displayed in a Resource Metric Viewer report for counters with different time granularity Label alarms that might not be handled properly by the Resource Metric Viewer Error with connection failure Cognos content store might stop daily Cognos Report Studio cannot be started on Internet Explorer Ignore the warning message that appears after you publish a model Ignore the error when you try to generate a model 85 Save Selections option works incorrectly on the Resource Metric Viewer Selection page Appendix. Command reference The createmodel command rmv_admin command Notices Trademarks Terms and conditions for product documentation.. 94 Glossary Index iv Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

5 About this information Intended audience Describes how to install and use IBM Tivoli Netcool Performance Manager - Application Studio on a Tivoli Netcool Performance Manager system. This publication is intended for: v Users who want to install and administer on a Tivoli Netcool Performance Manager common pack data models Tivoli Netcool Performance Manager system. Tivoli Netcool Performance Manager common pack data models enable Common Reporting for Tivoli Netcool Performance Manager. v Modelers who want to create and publish data models for Common Reporting in Tivoli Netcool Performance Manager. Readers must be familiar with the following topics: v Tivoli Netcool Performance Manager reporting concepts v Jazz for Service Management or IBM Cognos reporting v IBM Cognos Framework Manager Service Management Connect Connect, learn, and share with Service Management professionals: product support technical experts who provide their perspectives and expertise. Access Network and Service Assurance community at developerworks/servicemanagement/nsa/index.html. Use Service Management Connect in the following ways: v Become involved with transparent development, an ongoing, open engagement between other users and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code. v Connect one-on-one with the experts to collaborate and network about Tivoli and the Network and Service Assurance community. v Read blogs to benefit from the expertise and experience of others. v Use wikis and forums to collaborate with the broader user community. Related information: Tivoli Netcool Performance Manager 1.4 community on developerworks Tivoli Netcool Performance Manager technical training Support information For Tivoli Netcool Performance Manager technical training information, see the following Tivoli Netcool Performance Manager Training website at: If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Copyright IBM Corp. 2015, 2017 v

6 Online Access the IBM Software Support site at support/probsub.html. IBM Support Assistant The IBM Support Assistant is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. The Support Assistant provides quick access to support-related information and serviceability tools for problem determination. To install the Support Assistant software, go to support/isa. Troubleshooting Guide For more information about resolving problems, see the problem determination information for this product. Conventions used in this publication Several conventions are used in this publication for special terms, actions, commands, and paths that are dependent on your operating system. Typeface conventions This publication uses the following typeface conventions: Bold Italic Monospace Bold monospace v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text v Citations (examples: titles of publications, diskettes, and CDs) v Words defined in text (example: a nonswitched line is called a point-to-point line) v Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictive clause."; letters as letters example: "The LUN address must start with the letter L.") v New terms in text (except in a definition list): a view is a frame in a workspace that contains data. v Variables and values you must provide:... where myname represents... v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options v Command names, and names of macros and utilities that you can type as commands vi Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

7 v Environment variable names in text v Keywords v Parameter names in text: API structure parameters, command parameters and arguments, and configuration parameters v Process names v Registry variable names in text v Script names About this information vii

8 viii Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

9 Chapter 1. Introduction Tivoli Netcool Performance Manager common pack data model extends technology pack data model and Summary and Busy Hour data models to Tivoli Common Reporting on Tivoli Netcool Performance Manager Wireless component. After you install a technology pack, you install the corresponding Tivoli Netcool Performance Manager common pack data model to enable Tivoli Common Reporting. Tivoli Netcool Performance Manager common pack data models can be delivered in the COTS program with the corresponding technology packs, or created and customized by customers and IBM Business Partners. You can create Cognos data models that are Common Data Model (CDM ) - less models by using the Tivoli Netcool Performance Manager - Application Studio. Tivoli Netcool Performance Manager - Application Studio consists of the following features and capabilities: Consistent model generation Tivoli Netcool Performance Manager - Application Studio automates the creation of wireless data models. These models that are generated by using Tivoli Netcool Performance Manager - Application Studio are consistent and less error prone. Many Key Performance Indicators (KPIs) can be mapped automatically. Simplified model management Tivoli Netcool Performance Manager - Application Studio takes care of pack management, automatic creation of models and publish the models and reports on Dashboard Application Services Hub from Jazz for Service Management. Reusable data models Raw, busy hour and summary data models that are created on one server can be reused across all servers. Support for Compatible Query Mode Tivoli Netcool Performance Manager - Application Studio contains support for Compatible Query Mode. For IBM Cognos Business Intelligence, the query database (also known as the reporting database) is only accessed by the reporting engine that runs reports. The reporting engine is installed with Application Tier Components and is also used by Framework Manager, Metric Designer, and IBM Cognos Transformer. Support for Resource Metric Viewer Dynamically create reports by using the Resource Metric Viewer. Data availability reports generation Data availability or data coverage describes the completeness of data for a report. You can generate the data availability model that contains reports. Copyright IBM Corp. 2015,

10 Tivoli Netcool Performance Manager - Application Studio components Organization Components of Tivoli Netcool Performance Manager - Application Studio Tivoli Netcool Performance Manager - Application Studio consists of the following components: WirelessModelling A modeler tool that is required to create your own Tivoli Netcool Performance Manager data models. Tivoli Netcool Performance Manager data modelers can use WirelessModelling to browse a technology pack and extract the technology pack definition metadata, or browse a live Tivoli Netcool Performance Manager system and extract summary or busy hour metadata. The metadata extracted is converted into a Common Intermediate Format (CIF) file (.tnpmmodel) for later processing into a data model. WirelessModelling contains the following component with in it: CreateModel CreateModel is a tool that Tivoli Netcool Performance Manager data modelers use to build Tivoli Netcool Performance Manager common pack data models. CreateModel processes the Common Intermediate Format (CIF) file (.tnpmmodel) generated by WirelessModelling tool. Additional component required for creating the Tivoli Netcool Performance Manager common pack data models: TCR Time schema A mandatory schema for Tivoli Netcool Performance Manager data models, and provides a common time dimension for reporting. Read this summary information to help you find the information that you need. v Chapter 1, Introduction, on page 1 Describes the Tivoli Netcool Performance Manager - Application Studio tooling and how to use this information. v Chapter 2, Software requirements and prerequisite software, on page 5 Describes the Tivoli Netcool Performance Manager - Application Studio software requirements and prerequisite software. v Chapter 4, Installing and configuring IBM Cognos Framework Manager, on page 13 Describes how to install the Framework Manager for publishing the data models. v Chapter 5, Installing the Tivoli Netcool Performance Manager - Application Studio, on page 15 Describes how to install the Tivoli Netcool Performance Manager - Application Studio component v Chapter 6, Creating Tivoli Netcool Performance Manager common pack data models, on page 25 Describes how to create a Tivoli Netcool Performance Manager common pack data model. v Chapter 7, Getting started with Common reporting, on page 39 2 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

11 Describes the best practices in creating reports from the Tivoli Netcool Performance Manager common pack data models that are created by using Tivoli Netcool Performance Manager - Application Studio. v Chapter 8, Resource Metric Viewer, on page 41 Describes how to create dynamically create reports by using the Resource Metric Viewer. v Chapter 9, Data availability reporting, on page 65 Describes data availability or data coverage for the completeness of data for a report. v Chapter 10, Troubleshooting Tivoli Netcool Performance Manager - Application Studio and Common reporting, on page 81 Describes known issues that you might encounter when you are using Tivoli Netcool Performance Manager - Application Studio. v Command reference, on page 87 Provides a command reference for Tivoli Netcool Performance Manager - Application Studio commands. v Glossary on page 97 Includes Tivoli Netcool Performance Manager - Application Studio terms and definitions. Chapter 1. Introduction 3

12 4 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

13 Chapter 2. Software requirements and prerequisite software Supported configurations Ensure that your system meets the minimum software requirements and that all prerequisite software is installed and configured before starting the installation. Ensure that you have the following Tivoli Netcool Performance Manager configuration with the correct patch levels before you start the installation. Table 1. Supported software components Software Tivoli Netcool Performance Manager Jazz for Service Management Tivoli Common Reporting IBM Dashboard Application Services Hub IBM WebSphere Application Server IBM Cognos Framework Manager Supported versions Tivoli Netcool Performance Manager or higher- Wireless Component Jazz for Service Management consists of the following components. v Jazz for Service Management integration services Administration Services Dashboard Application Services Hub Security Services Registry Services Administration Services UI Reporting Services environment Tivoli Common Reporting Related information: Tivoli Netcool Performance Manager - Server hardware and software requirements Jazz for Service Management on IBM Knowledge Center Copyright IBM Corp. 2015,

14 Prerequisites for installing Tivoli Netcool Performance Manager - Application Studio tools Ensure that you fulfill these prerequisites before installing and configuring Tivoli Netcool Performance Manager - Application Studio on a Microsoft Windows computer. Microsoft Windows computer hardware A minimum of 4 GB RAM with a 2 GHz processor. Microsoft Windows operating system Tivoli Netcool Performance Manager - Application Studio WirelessModelling must be installed on a Microsoft Windows computer. WirelessModelling is compatible on Windows 7 and Microsoft Windows XP Professional, x86-32, Win32. IBM Cognos Framework Manager You must have IBM Cognos Framework Manager installed and configured to communicate with the Tivoli Common Reporting server. You can get the installation files from the following download images on Passport Advantage. To install Framework Manager, you must first install Framework Manager from the CognosModeling directory. Download the Framework Manager from IBM Passport Advantage. Oracle Client Framework Manager requires an ODBC connection to import and use an Oracle data source. For Oracle ODBC, the Oracle Client with the ODBC add-on is required. Oracle Instant Client You must install the Oracle libraries that are contained in the Oracle instant client package. Note: You must install both Oracle Client and Instant Client on the Jazz for Service Management server. 6 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

15 Chapter 3. Configuring the prerequisite software on the server Creating the nasaccess user Ensure that all necessary configuration steps are completed for the prerequisite software on the server. The nasaccess user must be created in the target database. The nasaccess user is responsible for creating users and for assigning access to the TCR Time schema and Tivoli Netcool Performance Manager Wireless system schema. Before you begin You must have database administrator privileges to perform this task. Ensure that Dashboard Application Services Hub is up and running. For more information about Dashboard Application Services Hub from Jazz for Service Management, see Installing Tivoli Netcool Performance Manager - Wireless Component. Ensure that the database is started. About this task If the nasaccess user does not exist, a database administrator must create the nasaccess user on the target database before you install the TCR Time schema. This task has to be performed before you start creating the Tivoli Netcool Performance Manager common pack data models. Procedure Create the main user schema nasaccess and grant permission to the user by running the following SQL statement: CREATE USER nasaccess IDENTIFIED BY nasaccess DEFAULT TABLESPACE wm_flexpm TEMPORARY TABLESPACE temp; Grant Alter Session, Create User, Alter User, Drop User, Grant Any Role, Grant Any Privilege, Analyze Any, Create Any Table, Alter Any Table, Drop Any Table, Select Any Table, Insert Any Table, Update Any Table, Delete Any Table, Create Any Index, Create Any View, Drop Any View, Create Any Synonym, Drop Any Synonym, Create Trigger, Create Sequence, Create Public Synonym, Drop Public Synonym, Create Session, Create Procedure, Create Library, Create Synonym, Create Table, Create Role, Create Type, Create View, Alter Any Trigger, Create Any Trigger, Drop Any Trigger, Alter Any Index, Drop Any Index, Lock Any Table, Comment Any Table, Alter Any Role, Drop Any Role, Alter Any Type, Create Any Type, Drop Any Type, Execute Any Type, Alter Any Sequence, Create Any Sequence, Drop Any Sequence, Select Any Sequence, Unlimited Tablespace, Create Any Procedure, Drop Any Procedure, Execute Any Procedure, Alter Any Procedure, Copyright IBM Corp. 2015,

16 Grant Any Object Privilege, Resumable, Execute Any Program, Execute Any Class, Create Job, Create Any Job, Create External Job, Analyze Any Dictionary, Select Any Dictionary, Select Any Transaction To nasaccess; Configuring Tivoli Common Reporting for Oracle database Connect the Tivoli Common Reporting to an Oracle database. Before you begin Perform this task with the support of a database administrator. Make sure that you installed the Oracle database client on the computer where Cognos based Tivoli Common Reporting engine is installed. Note: You might need to export the TNS_ADMIN environment variable before starting the Tivoli Common Reporting server. The TNS_ADMIN variable in the settcrenv.sh script must be set to point to the directory where the Oracle tnsnames.ora file is. See the Oracle documentation for details. About this task To configure the database, connect it to a client, configure calculations for Oracle functions, and activate the optional cross-database function. Procedure 1. Edit WebSphere Application Server scripts to use the settcrenv.sh script. To do this, append REPORTING_HOME/bin/setTCRenv.sh to the JazzSM_WAS_Profile/bin/ setupcmdline.sh. The default REPORTING_HOME is /opt/ibm/jazzsm/reporting. The default JazzSM_WAS_Profile is /opt/ibm/jazzsm/profile. 2. Add the following information to the settcrenv.sh file: ORACLE_HOME=/appl/oracle/product/ /db_1 export ORACLE_HOME TNS_ADMIN=$ORACLE_HOME/network/admin export TNS_ADMIN LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$LD_LIBRARY_PATH export LD_LIBRARY_PATH 3. Add the following information to startserver.sh file as root user: ORACLE_HOME=/appl/oracle/product/ /db_1 export ORACLE_HOME TNS_ADMIN=$ORACLE_HOME/network/admin export TNS_ADMIN LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$LD_LIBRARY_PATH export LD_LIBRARY_PATH 4. Ensure that Tivoli Common Reporting can find Oracle databases: a. Check if the Oracle directory that contains the libraries exists. b. If necessary, create or modify the variable to include the path to Oracle client library directory: LIBPATH LD_LIBRARY_PATH 8 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

17 For example: LD_LIBRARY_PATH = /opt/ibm/jazzsm/reporting/cognos/ bin64:/appl/oracle/product/ /db_1/lib32 c. Save your changes. 5. Connect the Oracle database client to the database server by running the Oracle Net Configuration Assistant, configuring the local net service name configuration, and restarting your system. Important: Note the name of the connection you created as it is used in one of the following steps. 6. Restart the Jazz for Service Management application server. 7. Create a database connection for Cognos. See Configuring the nasaccess data source on page 11. Related tasks: Starting Jazz for Service Management application servers on page 10 You can start any Jazz for Service Management virtualization and reporting servers by using the IBM WebSphere startserver command. You might need to restart the application server after you complete a configuration task for an integration service, or after you stop the application server for maintenance. Configuring the nasaccess data source for Oracle connection Configure the nasacess data source for connecting to Oracle Procedure Add nasaccess to the tnsnames.ora file on the server in this location: $ORACLE_HOME/network/admin/tnsnames.ora. Edit the tnsnames.ora file and add the following lines to the file: VTDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = TNPM_VIRTUO_DATABASE_HOST)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = vtdb) ) ) nasaccess = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = TNPM_VIRTUO_DATABASE_HOST)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = vtdb) ) ) Where TNPM_VIRTUO_DATABASE_HOST is the Tivoli Netcool Performance Manager - Wireless Component database server host name or IP address. Chapter 3. Configuring the prerequisite software on the server 9

18 Starting Jazz for Service Management application servers You can start any Jazz for Service Management virtualization and reporting servers by using the IBM WebSphere startserver command. You might need to restart the application server after you complete a configuration task for an integration service, or after you stop the application server for maintenance. About this task The same procedure applies to any Jazz for Service Management application server. Procedure 1. On the relevant Jazz for Service Management server, open a command window. 2. Change to the JazzSM_WAS_Profile/bin directory. The default location for <JazzSM_WAS_Profile> is /opt/ibm/jazzsm/profile. 3. Run the following command:./startserver.sh server_name Where server_name Enter the name of the application server that was specified when the application server profile was created. For example, server1. Related information: Common directory locations Stopping Jazz for Service Management application servers You can stop any Jazz for Service Management application server by using the IBM WebSphere stopserver command. You might need to restart the application server after you complete a configuration task for an integration service, or stop the application server for maintenance. To start the server again, use the startserver command. Procedure 1. On the relevant Jazz for Service Management server, open a command window. 2. Change to the <JazzSM_WAS_Profile>/bin directory. The default location for <JazzSM_WAS_Profile> is /opt/ibm/jazzsm/profile. 3. Run the following command:./stopserver.sh <server_name> -username <WAS_admin_user_name> -password <WAS_admin_password> Where server_name Enter the name of the application server that was specified when the application server profile was created. For example, server1. 10 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

19 WAS_admin_user_name The default user name is smadmin. WAS_admin_password Password that is specified at the time of installation. Example stopserver.sh server1 -username smadmin -password jazzsmpwd Related information: Common directory locations Configuring the nasaccess data source You must configure a nasaccess data source connection to connect to an Oracle database that has Tivoli Netcool Performance Manager data. Procedure 1. Log in to Dashboard Application Services Hub portal as the administration user, smadmin. For example: 2. Start the administrative console from Console Settings > Websphere Administrative Console and click Launch Websphere administrative console. a. Optional: Enter the WebSphere administrator user ID and password, and click Log in. b. In the new window from left menu, select Servers > Servers Types > WebSphere Application Server. c. Select the server that is used by Jazz for Service Management. By default, server1. d. In the Server Infrastructure section, select Java and Process Management > Process Definition. e. In the Additional Properties section, select Environment Entries. f. If necessary, create or modify the variable to include the path to Oracle client library directory: For example: LIBPATH LD_LIBRARY_PATH LD_LIBRARY_PATH=/opt/IBM/JazzSM/reporting/cognos/bin64:/appl/oracle/product/ /db_1/lib32 Add two more environment variable entries: v v ORACLE_HOME=/appl/oracle/product/ /db_1 TNS_ADMIN=/appl/oracle/product/ /db_1/network/admin g. Save your changes. 3. Restart WebSphere Application Server: Stopping Jazz for Service Management application servers on page 10 Starting Jazz for Service Management application servers on page Select the Common Reporting tab. 5. Click Launch > IBM Cognos Administration. Chapter 3. Configuring the prerequisite software on the server 11

20 6. On the Configuration tab, click the New Data Source button to add a data source. 7. Follow the New Data Source wizard and note the following steps: a. Enter nasaccess in the name field and click Next. b. Clear the Configure JDBC connection check box. c. In the Type list, select Oracle and click Next. d. In the SQL*Net connect string field, enter vtdb. e. In the Signon section, select the User ID, Password, and Create a signon that the Everyone group can use check boxes. f. Enter the user ID and password, and then click Finish. g. Test the new data source connection. Related information: Connecting to an Oracle database in Compatible mode 12 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

21 Chapter 4. Installing and configuring IBM Cognos Framework Manager Framework Manager is a modeling tool available for Windows operating systems for creating and modifying business views of data models. About this task Framework Manager is a Windows-based utility included in the Cognos Modeling product. The installation image for Cognos Modeling is on a separate installation media in the following location: \CognosModeling\win32\issetup.exe. Note: Use IBM Cognos Framework Manager Version Procedure 1. Run the installation image: \CognosModeling\win32\issetup.exe. 2. Provide all the necessary parameters. Related information: Install Framework Manager Configuring Framework Manager connection Configuring IBM Cognos Framework Manager connections You must configure the required Framework Manager connections. Configure Framework Manager connection You configure Framework Manager to point to the server on which you publish your content. If you want to publish content to another server, you must change these settings to point to the new server. Related information: Configuring Framework Manager connection (Optional) Configuring Framework Manager Oracle connection Use this information, if you need to configure the Oracle connections on Framework Manager. Procedure 1. Add Oracle to your Windows path. For example, C:\oracle\product\ \client_1\bin. 2. Add nasaccess to the tnsnames.ora file on the server in this location: C:\appl\oracle\product\ \client_1\network\admin. Edit the tnsnames.ora file and add the following lines to the file: Copyright IBM Corp. 2015,

22 VTDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = TNPM_VIRTUO_DATABASE_HOST)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = vtdb) ) ) nasaccess = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = TNPM_VIRTUO_DATABASE_HOST)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = vtdb) ) ) Where TNPM_VIRTUO_DATABASE_HOST is the Tivoli Netcool Performance Manager - Wireless Component database server host name or IP address. 14 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

23 Chapter 5. Installing the Tivoli Netcool Performance Manager - Application Studio The WirelessModelling_<version>-win32.win32.x86.zip file contains WirelessModelling and CreateModel components in it. Procedure 1. Download the WirelessModelling_<version>-win32.win32.x86.zip archive file. 2. Extract the WirelessModelling_<version>-win32.win32.x86.zip file to a location of your choice. For example, C:\npm_app_studio. Results You see the following files and folders in C:\npm_app_studio\ WirelessModelling_<version>-win32.win32.x86: v CreateModel_<version> createmodel java v WirelessModelling_<version> v install_tcrtime.zip v rmv.zip admin conf lib logs scripts sql templates TCR Time schema installation scripts The TCR Time schema is a mandatory for all Tivoli Netcool Performance Manager common pack data models, and provides a common time dimension for reporting. It must be installed before you can work with any Tivoli Netcool Performance Manager common pack data models. v Extract the install_tcrtime.zip file from the C:\npm_app_studio\ WirelessModelling_<version>-win32.win32.x86 directory. You have the scripts for installing TCR Time schema and for populating the calendar schema tables for TCR Time schema. v Copy the scripts to the server where Tivoli Netcool Performance Manager database is installed. Copyright IBM Corp. 2015,

24 Installing the TCR Time schema All data models have a dependency on the TCR Time schema. The TCR Time is a mandatory dependent schema for all Tivoli Netcool Performance Manager common pack data models, and provides a common time dimension for reporting. It must be installed before you can work with any Tivoli Netcool Performance Manager common pack data model. Data models with 5-minutes granularity are supported along with existing 15-min granularity. Before you begin Ensure that you have downloaded the TCR Time schema. Ensure that you have created the nasaccess user. See Creating the nasaccess user on page 7 Ensure that you have configured the nasaccess datasource on Dashboard Application Services Hub. See Configuring the nasaccess data source on page 11 Procedure 1. Install the TCR Time schema by running the following command as user virtuo:./pre_install.ksh The pre_install.ksh script is in the folder where you have extracted the Tivoli Netcool Performance Manager - Application Studio. For more information, see Chapter 5, Installing the Tivoli Netcool Performance Manager - Application Studio, on page Populate the calendar schema table for TCR Time by running the following command as user virtuo:./calendar_refill.ksh <Admin database NASACCESS user name> <Admin database NASACCESS user password> <SID> For example:./calendar_refill.ksh nasaccess nasaccess vtdb The calendar_refill.ksh script is in the folder where you have extracted the Tivoli Netcool Performance Manager - Application Studio. For more information, see Chapter 5, Installing the Tivoli Netcool Performance Manager - Application Studio, on page 15. Note: The calendar_refill.ksh script creates data models for 15-minutes granularity. To create data models for 5-minutes granularity, calendar schema table TIMES_5 can be created by running the following command as user virtuo:./calendar_refill_5.ksh <Admin database NASACCESS user name> The calendar_refill.ksh script adds past and future dates to the calendar schema table without clearing existing entries. Typically, you run this action each night to add the data for the day after the next day. For example, you can run the populate action on Monday to create entries for Wednesday. This example enables reporting through the midnight hour, since you have the timestamps in the calendar for the data that is arriving. The calendar-refill script clears the calendar schema table and repopulates it with past and future dates. Typically, a frequency of once a month is adequate to run the calendar-refill action. The main purpose of the calendar-refill action is to remove old timestamps. 16 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

25 WirelessModelling tool WirelessModelling is a tool that modelers can use to browse a technology pack and extract the technology pack definition metadata, or browse a live Tivoli Netcool Performance Manager system and extract the summary or busy hour metadata. The metadata that is extracted is converted into a Common Intermediate Format (CIF) file (.tnpmmodel) for later processing into a data model. You can create data models with different granularities. A new property by name MIN_TIMES_GRANULARITY is added to model properties file, which can help you decide the type of data model. If you set this property to 5, the data model can support 5-min granularity, if you set it to 15 min, the data model can support 15-min granularity. Related tasks: Creating a model properties file on page 35 You can create a model properties file from the sample file that is provided or create your own file. Name the new model properties file according to your model and update the values in the file. Opening WirelessModelling tool WirelessModelling is installed by extracting an archive file to a location of your choice. You open WirelessModelling tool by running a Windows executable file. Before you begin This procedure assumes that the WirelessModelling files are extracted in the C:\npm_app_studio\WirelessModelling_<version>-win32.win32.x86 folder. Procedure 1. Go to the folder where WirelessModelling executable file is located. For example C:\npm_app_studio\WirelessModelling_<version>-win32.win32.x86\ WirelessModelling_<version>\launcher.exe. 2. Double-click launcher.exe. 3. In the Workspace Launcher window, accept the default location C:\npm_app_studio\WirelessModelling_<version>-win32.win32.x86\ WirelessModelling_<version>\workspace, or browse to a location of your choice for the workspace where your WirelessModelling projects and files are stored and click OK. You can modify this location later if required. WirelessModelling opens in Resource perspective. Configuring WirelessModelling tool Complete the following tasks to configure the WirelessModelling tool. Configuring IBM Cognos Business Intelligence preferences Configure the Cognos preferences. You must configure the BMT Script Player location before you can publish the Cognos models. Procedure 1. Select Window > Preferences. 2. In the Preferences window, select TNPM Preferences > Cognos. 3. In the Cognos window, provide the following details: Chapter 5. Installing the Tivoli Netcool Performance Manager - Application Studio 17

26 Option BmtScriptPlayer Executable Path Cognos Dispatcher URI Username Password Namespace Description Browse to the location of the BmtScriptPlayer.exe file in your Cognos Framework Manager installation. For Cognos , the default location is C:\Program Files\cognos\c10\bin\ BmtScriptPlayer.exe. A read-only value that is read from the Dispatcher URI for external applications value in IBM Cognos Configuration. This value shows the server where Framework Manager publishes content, for example, dispatch/ext. You cannot modify this value here. If you want to publish content to a different server, you must configure Framework Manager to point to the new server by using IBM Cognos Configuration. WAS_admin_user_name. For example, smadmin. WAS_admin_password. The namespace is defined in the Security section of IBM Cognos Configuration. By default, VMMProvider. CreateModel tool Configuring the JDBC driver You must configure the JDBC driver before you can connect to a database. Procedure 1. Select Window > Preferences. 2. In the Preferences window, select TNPM Preferences > Database Configuration. 3. Browse to the location of the JDBC driver library file. For example, C:\oracle\client\product\ \client\jdbc\lib\ojdbc7.jar for Oracle 12c. 4. In the Preferences window, select TNPM Preferences > Database Details. 5. Enter the host name of the working system. For example: <myhost>.ibm.com. 6. Click Apply and click OK. CreateModel is a tool that modelers use to build Tivoli Netcool Performance Manager common pack data models. CreateModel processes the Common Intermediate Format (CIF) file (.tnpmmodel) generated by WirelessModelling tool. 18 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

27 Location of the CreateModel script file CreateModel tool is installed by extracting the WirelessModelling_<version>win32.win32.x86 archive file. About this task The createmodel command is available at the following location: C:\npm_app_studio\WirelessModelling_<version>-win32.win32.x86\ CreateModel_<version>\createModel\bin\createmodel.bat. Installing Resource Metric Viewer Resource Metric Viewer must be installed on the server where Jazz for Service Management is installed. Before you begin Extract the rmv.zip file to <JAZZSM_HOME> from the location where you have downloaded and extracted the WirelessModelling_<version>-win32.win32.x86.zip file. Where <JAZZSM_HOME> is the location where the Jazz for Service Management Components is installed. By default, /opt/ibm/jazzsm. For more information, see Chapter 5, Installing the Tivoli Netcool Performance Manager - Application Studio, on page 15. Procedure 1. Go to the admin folder and run the rmv_install.sh command by using the following commands: cd admin./rmv_install.sh Provide the following inputs. a. Enter the JDBC URL for the administrative database. Due to an Oracle limitation, the host name cannot exceed 60 characters. If the host name exceeds 60 characters, use the IP address instead. Please enter the database url:(jdbc:oracle:thin:@hostname:1521:vtdb): jdbc:oracle:thin:@<ip_address>:1521:vtdb b. Enter the directory where the Oracle client is installed. For example,/appl/oracle/product/ /db_1. Please enter the location for ORACLE_HOME:(/appl/oracle/product/ /db_1): /appl/oracle/product/ /db_1 Note: Make sure that you always provide /appl/oracle/product/ /db_1 as ORACLE_HOME. Otherwise, the installation might fail. c. Enter the name of the administrative database user nasaccess Please enter the username for database:(nasaccess): nasaccess d. Enter the password of the administrative database user nasaccess Chapter 5. Installing the Tivoli Netcool Performance Manager - Application Studio 19

28 Please enter the password for database:(nasaccess): nasaccess e. Enter the Jazz for Service Management installation directory. By default,/opt/ibm/jazzsm. Please enter the JazzSM location:(/opt/ibm/jazzsm): /opt/ibm/jazzsm f. Enter a Jazz for Service Management administrator user name. By default, smadmin. Please enter the JazzSM username:(smadmin): smadmin g. Enter a Jazz for Service Management administrator user name. By default, smadmin. h. Enter the Cognos Dispatcher port. Please enter the Dispatcher port:(16310): The installation script runs with the following output: Running sql: /opt/ibm/jazzsm/mh_rmv/rmv/sql/create_user.sql PL/SQL procedure successfully completed. Running sql: /opt/ibm/jazzsm/mh_rmv/rmv/sql/create_tables.sql Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. Grant succeeded. PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. Running sql: /opt/ibm/jazzsm/mh_rmv/rmv/sql/create_views.sql View created. View created. 20 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

29 View created. View created. View created. View created. Running sql: /opt/ibm/jazzsm/mh_rmv/rmv/sql/bi_rmv_merge.pks Package created. Running sql: /opt/ibm/jazzsm/mh_rmv/rmv/sql/bi_rmv_merge.pkb Package body created. WASX7209I: Connected to process "server1" on node JazzSMNode01 using SOAP connector; The type of process is: UnManagedProcess rmv.install.intro tools.install.configuringjdbc tools.install.getjdbcdetails tools.install.getjdbcdetails tools.install.configuringjdbcprovider tools.install.deletingjdbcprovider tools.install.createdjdbcprovider tools.install.configuringjdbcdatasource tools.install.createdjdbcdatasource WASX7209I: Connected to process "server1" on node JazzSMNode01 using SOAP connector; The type of process is: UnManagedProcess com.ibm.isclite.deploybundleactivator.start(bundlecontext context) Entry WASX7327I: Contents of was.policy file: // // Template policy file for enterprise application. // Extra permissions can be added if required by the enterprise application. // // NOTE: Syntax errors in the policy files will cause the enterprise application FAIL to start. // Extreme care should be taken when editing these policy files. It is advised to use // the policytool provided by the JDK for editing the policy files // (WAS_HOME/java/jre/bin/policytool). // grant codebase "file:${application}" { }; grant codebase "file:${jars}" { }; grant codebase "file:${connectorcomponent}" { }; grant codebase "file:${webcomponent}" { }; grant codebase "file:${ejbcomponent}" { }; ADMA5078I: Update of isc has started. ADMA5058I: Application and module versions are validated with versions of deployment targets. ADMA5009I: Extracting application archive to /opt/ibm/jazzsm/profile/wstemp/appmgmt/mbean/appmanagement_14501ead05a_1/app_ d04/ext/tnpmrmv.war. ADMA5064I: FileMergeTask completed successfully for isc. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. CWLAA10007I: Explanation: The help plug-in of the Integrated Solutions Console module was deployed successfully. User action: No user action required. CWLAA10001I: Explanation: The Integrated Solutions Console module was deployed successfully. User action: No user action required. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5113I: Activation plan created successfully. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5011I: The cleanup of the temp directory for application isc is complete. ADMA5079I: Update of isc has ended. The application or its web modules may require a restart when a save is performed. 2. Restart the Jazz for Service Management. 3. Optional: Run the db2start command to restart the database instance. cd /./home/smadmin/sqllib/adm/db2stop./home/smadmin/sqllib/adm/db2start Chapter 5. Installing the Tivoli Netcool Performance Manager - Application Studio 21

30 Related tasks: Starting Jazz for Service Management application servers You can start any Jazz for Service Management virtualization and reporting servers by using the IBM WebSphere startserver command. You might need to restart the application server after you complete a configuration task for an integration service, or after you stop the application server for maintenance. Creating a logins file with appropriate passwords You must create a logins file containing certain passwords that are required by the rmv_admin command. For your security, change the default passwords provided during installation. If you update any of the passwords, ensure that you update the credentials file, or the nasaccess data source, as appropriate. Before you begin The following password are required: smadmin The default Jazz for Service Management administrator user. nasaccess A control user that you must create on the database before running the installer. About this task The rmv_admin command automatically encrypts the passwords when creating the logins file. For instructions on changing Oracle user or schema passwords, see Oracle_database_Security_FAQ#How_does_one_change_an_Oracle_user.27s_password.3F. If you change the Oracle nasaccess user password, then you must also change the Cognos nasaccess data source. If you change the Jazz for Service Management smadmin user password, you must recreate the logins file with the new credentials. The old logins file is no longer valid. Procedure Enter the following command in one line and provide the passwords when prompted: #./rmv_admin.sh -passwordfile./logins.txt -tipuser smadmin -dbusers tnpm:nasaccess You see the following output: Please enter the password for user nasaccess: Please re-enter the password for user nasaccess: Please enter the password for user smadmin: Please re-enter the password for user smadmin: The following file was created: logins.txt CTGTRR205I The operation createloginsfile successfully performed. 22 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

31 Uninstalling Resource Metric Viewer Instructions on how to uninstall Resource Metric Viewer UI components. Procedure Uninstall the Resource Metric Viewer UI component by running the following command as root user:./rmv_uninstall.sh Enter the required information when you are prompted as follows: Please enter the database Please enter the location for ORACLE_HOME:(/appl/oracle/product/ /db_1): /appl/oracle/product/ /db_1 Please enter the username for database:(nasaccess): nasaccess Please enter the password for database:(nasaccess): nasaccess Please enter the JazzSM location:(/opt/ibm/jazzsm): /opt/ibm/jazzsm Please enter the JazzSM username:(smadmin): smadmin Please enter the JazzSM password:(smadmin): smadmin Running sql: /opt/ibm/jazzsm/mh_rmv/rmv/sql/drop_all_objects.sql Package dropped. View dropped. View dropped. Sequence dropped. Table dropped. Index dropped. Table dropped. Index dropped. Table dropped. Table dropped. Table dropped. User dropped. executed uninstallschema WASX7209I: Connected to process "server1" on node JazzSMNode01 using SOAP connector; The type of process is: UnManagedProcess bi.uninstall.intro tools.uninstall.removingjdbc bi.uninstall.complete WASX7209I: Connected to process "server1" on node JazzSMNode01 using SOAP connector; ADMA5078I: Update of isc has started. CWLAA10005I: Explanation: The Integrated Solutions Console module was removed successfully. ADMA5058I: Application and module versions are validated with versions of deployment targets. Chapter 5. Installing the Tivoli Netcool Performance Manager - Application Studio 23

32 ADMA5009I: Extracting application archive to /opt/ibm/jazzsm/profile/wstemp/appmgmt/mbean /AppManagement_14501ead05a_1/app_ d04/ext/tnpmrmv.war. ADMA5064I: FileMergeTask completed successfully for isc. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5113I: Activation plan created successfully. ADMA5005I: The application isc is configured in the WebSphere Application Server repository. ADMA5011I: The cleanup of the temp directory for application isc is complete. ADMA5079I: Update of isc has ended. The application or its web modules may require a restart when a save is performed. # 24 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

33 Chapter 6. Creating Tivoli Netcool Performance Manager common pack data models Creating a Tivoli Netcool Performance Manager common pack data model for Common Reporting on Tivoli Netcool Performance Manager requires these Tivoli Netcool Performance Manager - Application Studio components. v Use WirelessModelling tool to extract the required metadata from a technology pack or from the Tivoli Netcool Performance Manager database. WirelessModelling tool outputs the metadata in a Common Intermediate Format (CIF) file (.tnpmmodel) that serves as the input for CreateModel tool. v Use CreateModel tool to generate a Tivoli Netcool Performance Manager common pack data model built from the metadata in the CIF file, and all remaining artifacts in the required directory structure for the model contents. v Finally, use Framework Manager to browse to the model contents and publish the model in the Tivoli Common Reporting component of the Tivoli Netcool Performance Manager system. Overview of creating Tivoli Netcool Performance Manager common pack data model for Wireless pack modelers Wireless pack modelers can follow these steps to create Tivoli Netcool Performance Manager common pack data models. Each step points to other topics for more detailed information. About this task Ensure that you have an operational Tivoli Netcool Performance Manager system with all the Tivoli Netcool Performance Manager - Application Studio components installed. Procedure 1. Model the data from a technology pack or extract the summary and busy hour data from the Tivoli Netcool Performance Manager system. See the following topics: Creating a Tivoli Netcool Performance Manager common pack data model containing a raw data model on page 26 Creating a Tivoli Netcool Performance Manager common pack data model containing a summary definitions model on page 27 Creating a Tivoli Netcool Performance Manager common pack data model containing a busy hour definitions model on page Optional: Reduce the size of your data model, you can filter out metrics to include only those metrics that you want to report on. For more information, see Data model filtering on page 30 and for the procedure, see Filtering metrics from a model in an existing CIF file on page Create the model properties file. See Creating a model properties file on page Generate the Tivoli Netcool Performance Manager data model contents. See Generating the Tivoli Netcool Performance Manager common pack data model contents on page 36 Copyright IBM Corp. 2015,

34 5. Publish the data model. See Publishing a Tivoli Netcool Performance Manager common pack data model on page 37 Creating a Tivoli Netcool Performance Manager common pack data model containing a raw data model You can extract raw data counters from a technology pack. You can then create a Tivoli Netcool Performance Manager common pack data model containing a model that report authors can use to create reports by using those raw data counters. Procedure 1. In WirelessModelling tool, select File > New > Project. 2. Click General > Project, and then click Next. 3. Enter the project name. Typically, you use the name of the technology pack. 4. Click Finish. 5. In the Project Explorer, right-click the new project and select Import. The Import wizard opens. 6. On the Select page of the Import wizard, expand TNPM Pack Modeling and select Import a Wireless Pack Archive (from archive) or Import a Wireless Pack Archive (from expanded folder). 7. Optional: Select Import a Wireless Pack Archive (from expanded folder) to import a technology pack that is copied from an installed Tivoli Netcool Performance Manager system. Browse to the source folder where the pack model is available. For example: v GSM_Nokia_BSS_RG Technology Pack..\admin\techpacks\GSM_Nokia_BSS_RG20\4.0.0\ v UMTS_Nokia_UTRAN_RU40 Technology Pack..\admin\techpacks\UMTS_Nokia_UTRAN_RU40\7.0.0\ Important: For all packs that are not released by IBM as a part of Commercial Off The Shelf (COTS) program or those packs that are customized by you, you must use Import a Wireless Pack Archive (from expanded folder) option to import the models. 8. Click Next. 9. On the Database details page, specify the following connection details: v Host: Hostname where the database is installed v Username: Username of the system. By default, virtuo v Password: Password for virtuo user v Database SID: SID name to connect. By default, vtdb. 10. Click Test Connection. 11. Click Next when the connection is successful. 12. Browse to a folder that contains a technology pack and click Open. The contents of the technology pack are imported and inspected. 13. Click Next. 14. On the Select Entities page, you can see the vendor and all the entities that are associated with the pack. Select the required entities and click Next. Typically, you must select the Vendor and Neutral entities 26 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

35 15. On the Save As page, enter a name for the tnpmmodel file. A Common Intermediate Format (CIF) file (.tnpmmodel) is generated based on the name of the technology pack. Select your project folder, and then click Finish. 16. In the Project Explorer, select the CIF file to see the contents and browse through the resource set and the metric group set to check your data. 17. If you want to reduce the size of the CIF file by only including specific metrics for particular resources, filter the CIF file as described in Filtering metrics from a model in an existing CIF file on page Generate the data model contents as described in Generating the Tivoli Netcool Performance Manager common pack data model contents on page Publish the Tivoli Netcool Performance Manager common pack data model by using Framework Manager. For more information about how to publish the, see Publishing a Tivoli Netcool Performance Manager common pack data model on page 37. Creating a Tivoli Netcool Performance Manager common pack data model containing a summary definitions model On Tivoli Netcool Performance Manager - Wireless component, you can extract the summary definitions associated with a particular technology pack from the Tivoli Netcool Performance Manager database. You can then create a Tivoli Netcool Performance Manager common pack data model containing a model that report authors can use to create reports by using those summary definitions. Before you begin Ensure that you have configured the JDBC driver in WirelessModelling tool preferences so that you can connect to the database to extract the summary definitions. Procedure 1. In WirelessModelling tool, select File > New > Project. 2. Enter the project name. Typically, you use the name of the technology pack. 3. Click Next. 4. In the Project Explorer, right-click the new project and select Import. The Import wizard opens. 5. On the Select page of the Import wizard, expand TNPM Pack Modeling and select Import Summaries. 6. Click Next. 7. On the Database details page, specify the following connection details: v Host: Hostname where the database is installed. For example, server.ibm.com v Username: Username of the system. By default, For example, virtuo v Password: Database password v Database SID: SID name to connect. By default, vtdb. 8. Click Get Summaries. The database connection is tested. 9. Click Next. 10. On the Select Installed Packs page, select one or more technology packs from a list of the installed technology packs on the system. Select UDC from the Select Installed Packs page if you want to create a Tivoli Netcool Performance Chapter 6. Creating Tivoli Netcool Performance Manager common pack data models 27

36 Manager common pack data model with user-defined summaries. Make sure that the provisioned summary definition file has summary type as user. For more information about the complex summary definition and the associated entities in the XML file, see Complex summary definition in the Administering Tivoli Netcool Performance Manager - Wireless Component. Or, select the technology pack if you want to use the custom summaries. 11. Click Next. The Select Summaries page opens, showing all of the summaries that are associated with the selected technology packs. 12. Select the required summaries by vendor, entity, or summary name. 13. Select the appropriate check box to filter the selected summaries by raw, hourly, daily, weekly, or monthly intervals. Select the All summaries check box if you want all. 14. Click Next. 15. On the Model Details page, specify the following information: Option Name Version Vendor Technology Description The model name. Important: You must not use special characters in the model name. The model version. The vendor name. The model technology. Important: You must specify the correct technology for the model to be generated correctly. 16. On the Save As page, verify the name for the Common Intermediate Format (CIF) file (.tnpmmodel), select your project folder, and then click Finish. 17. In the Project Explorer, select the CIF file to see the contents. 18. Expand the Summary Definition Set to see the summary definitions in the model. 19. Select Window > Show View > View Properties to see the constituent metrics. 20. If you are satisfied with the CIF file contents, update the model properties file as described in Creating a model properties file on page Generate a Tivoli Netcool Performance Manager common pack data model as described in Generating the Tivoli Netcool Performance Manager common pack data model contents on page Publish the Tivoli Netcool Performance Manager common pack data model by using Framework Manager. For more information, see Publishing a Tivoli Netcool Performance Manager common pack data model on page Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

37 Creating a Tivoli Netcool Performance Manager common pack data model containing a busy hour definitions model On Tivoli Netcool Performance Manager - Wireless component, you can extract the busy hour definitions associated with a particular technology pack from the Tivoli Netcool Performance Manager database. You can then create a Tivoli Netcool Performance Manager common pack data model containing a model that report authors can use to create reports by using those busy hour definitions. Before you begin Ensure that you have configured the JDBC driver in WirelessModelling tool to ensure that you can connect to the database to extract the busy hour definitions Procedure 1. In WirelessModelling tool, select File > New > Project. 2. Enter the project name. Typically, you use the name of the technology pack. 3. Click Next. 4. In the Project Explorer, right-click the new project and select Import. The Import wizard opens. 5. On the Select page of the Import wizard, expand TNPM Pack Modeling and select Import Busy Hours. 6. Click Next. 7. On the Database details page, specify the following connection details: v Host: Hostname where the database is installed. For example, server.ibm.com v Username: Username of the system. By default, For example, virtuo v Password: Database password v Database SID: SID name to connect. By default, vtdb. 8. Click Get Busy Hours. The database connection is tested. 9. Click Next. 10. On the Select Installed Packs page, select one or more technology packs from a list of the installed technology packs on the system. 11. Click Next. The Select Busy Hours page opens, showing all of the busy hours that are associated with the selected technology packs organized by focal entity. 12. Select the required busy hours by vendor, entity, or busy hour name. 13. Click Next. 14. On the Model Details page, specify the following information: Option Name Version Vendor Technology Description The model name. Important: You must not use special characters in the model name. The model version. The vendor name. The model technology. Important: You must specify the correct technology for the model to be generated correctly. Chapter 6. Creating Tivoli Netcool Performance Manager common pack data models 29

38 Data model filtering 15. On the Save As page, verify the name for the Common Intermediate Format (CIF) file, select your project folder, and then click Finish. 16. In the Project Explorer, select the CIF file to see the contents. 17. Expand the Busy Hour Definition Set to see the busy hour definitions in the model. 18. Select Window > Show View > View Properties to see the constituent metrics. 19. If you are satisfied with the CIF file contents, update the model properties file as described in Creating a model properties file on page Generate the Tivoli Netcool Performance Manager common pack data model contents as described in Generating the Tivoli Netcool Performance Manager common pack data model contents on page Publish the Tivoli Netcool Performance Manager common pack data model by using Framework Manager. For more information, see Publishing a Tivoli Netcool Performance Manager common pack data model on page 37. By default, all of the performance metrics and summary and busy hour intervals for a particular technology pack are available to be included in a data model for reporting. When creating a Tivoli Netcool Performance Manager common pack data model, it is recommended to filter these metrics to ensure that only metrics that you need to report on are deployed. Large data models take longer to generate, merge and deploy and have a larger management overhead than smaller data models. It also requires much more memory to manage a larger data model. The maximum recommended size of a manageable data model is 50 MB, this equates to approximately metrics. In addition, the larger the data model, the more difficult it is to find metrics in the data model. Filtering the metrics that are included in each data model by metric group can offer much improved performance, and a targeted set of metrics for particular reporting requirements. If required, you can add additional metric groups by updating the filter and regenerating the data model for inclusion in a new Tivoli Netcool Performance Manager common pack data model. You can also reduce the model size by filtering out unwanted intervals from your summary and busy hour models. You work from the CIF file that contains the required raw metrics, busy hours, or summaries from a technology pack or Tivoli Netcool Performance Manager system. Import the CIF file and apply the required filter. 30 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

39 Filtering metrics from a model in an existing CIF file Before generating a Tivoli Netcool Performance Manager common pack data model, it is recommended that you filter each of your CIF files (.tnpmmodel) to include only the metrics that you need to report on. Before you begin You must have a filter file containing a list of the metric groups that contain the metrics that you want to include in your reports. The input file format is a simple flat file in which you specify the metric groups you want in your Cognos model. This filter file is applied to the full CIF file to give a filtered CIF file. You must have generated the CIF files for each of the raw counters, summaries, or busy hours that you plan to include in your model. Procedure 1. In WirelessModelling, select File > Import. The Import wizard opens. 2. On the Select page of the Import wizard, expand TNPM Pack Modeling and select Filter an existing Wireless model. 3. Select the filter to apply. 4. Select the tnpmmodel file that you want to filter. For example, huawei-gsm-bss-raw.tnpmmodel. 5. Click Finish. Results A filtered tnpmmodel file is created. For example, huawei-gsm-bss-rawfiltered.tnpmmodel. The console displays the number of metrics and metric groups in the filtered data model. Identifying metric groups for a filter file To create a filter file, you need to identify the metric groups that contain the metrics you want to include. You can use one of the following methods to map individual metrics to metric groups. Identifying metric groups from a CSV file: Given a list of the required metrics in a CSV file, you can use the CSV file as a filter to identify the associated metric groups. Before you begin This task requires a CSV file listing the required metrics, typically provided by the customer or user community. About this task In Tivoli Netcool Performance Manager - Wireless Component, metric (counter) expressions are typically the loadmap expression. Chapter 6. Creating Tivoli Netcool Performance Manager common pack data models 31

40 This procedure assumes a CSV file called LTE_CounterFilter.csv, with the counter IDs in column E as shown. You load this file into a temporary database table to use as a filter. Procedure 1. Log in to the wireless database. 2. Create a table to store the filtered counters by entering the following command: create table counter_list (counter_id varchar(50)); 3. Copy the CSV file to the wireless server. 4. Cut the counter IDs from the CSV file and copy them to another file, for example counterid.list. cut -d, -f5 LTE_CounterFilter.csv > counterid.list 5. Load the counter list into the counter_list table using the sqlloader. Edit the load.ctl file to create the loader instructions load data infile counterid.list into table counter_list fields terminated by "," (counter_id) 6. Load the counter list. sqlldr virtuo/virtuo01@vtdb control=load.ctl 7. Run the following SQL query to get all metric groups for the counters loaded. The query below maps into the wireless dictionary and selects all metric groups that include the counter IDs that were loaded. select metric_group from ( select e.entity_name. substr(f2.field_name,instr(f2.field_name,.,1,1)+1, (INSTR(f2.field_name,.,-1,1)) - INSTR(f2.field_name,.,1,1)-1)METRIC_GROUP from wmd_dict_table d, wmd_dict_field f, wmd_dict_field f2, wmd_col_def c, lc_loadmap lm, lc_ruleset lr, lc_datasource ld, wmd_dict_field_depend dep, wmn_entity e where f.table_id = d.table_id and f2.entity_id = e.entity_id and dep.child_field_id = f.field_id and dep.parent_field_id = f2.field_id and f.field_id = c.field_id and upper(lm.colname) = c.col_name and upper(lm.tabname) = d.table_name and lm.ruleset_id = lr.ruleset_id and ld.datasource_id = lr.datasource_id AND lm.expression in (select C counter_id from counter_list)) Metric_Filter group by metric_group order by 1 32 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

41 Results The query returns the list of metric groups, which you can use as a filter file in WirelessModelling. For example, CPU_Device.CPU_Of_Board ENodeBFunction.BBU ENodeBFunction.ENodeB EUtranCell.CQI EUtranCell.Cell_Algorithm EUtranCell.DRB PMU_Device.PMU RRU_Device.RRU Identifying resource groups from the model documentation: WirelessModelling supports the generation of a HTML document representing the contents of the tech pack. A user can take the unfiltered model and generate the HTML document. In any HTML browser, using this html representation of the data model contents the user can search for the counter ID. Before you begin You must have a list of the counter IDs or descriptions. Procedure 1. In WirelessModelling tool, select File > Export. The Export wizard opens. 2. On the Select page of the Export wizard, expand TNPM Pack Modeling and select Export HTML Documentation. 3. Click Next. 4. Open the HTML document in a browser. 5. Search for each counter ID for description to identify the metric group. Identify metric groups by using a SQL query: You can use a query on the wireless database to identify the mapping between the counter ID and the metric group. Before you begin You must have a list of the counter IDs. Procedure 1. Log in to the wireless database. 2. Enter the following command: select e.entity_name. substr(f2.field_name,instr(f2.field_name,.,1,1)+1, (INSTR(f2.field_name,.,-1,1)) - INSTR(f2.field_name,.,1,1)-1)METRIC_GROUP from wmd_dict_table d, wmd_dict_field f, wmd_dict_field f2, wmd_col_def c, lc_loadmap lm, lc_ruleset lr, lc_datasource ld, wmd_dict_field_depend dep, wmn_entity e where f.table_id = d.table_id and f2.entity_id = e.entity_id and dep.child_field_id = f.field_id and dep.parent_field_id = f2.field_id and f.field_id = c.field_id and upper(lm.colname) = c.col_name and upper(lm.tabname) = d.table_name Chapter 6. Creating Tivoli Netcool Performance Manager common pack data models 33

42 and lm.ruleset_id = lr.ruleset_id and ld.datasource_id = lr.datasource_id AND lm.expression in ( C , C , C ) Results A list of metric groups is returned, for example: METRIC_GROUP Cell.Call_drop_overview Cell.Short_message Cell.Call_drop_due_to_conn_fail Filtering intervals from existing CIF files After using a particular model, you can decide that there are summary or busy hour intervals that you do not need. You can import the CIF files and filter out these unwanted intervals at any time. Filtering an existing summary model You can filter a summary model by removing raw, hourly, daily, weekly or monthly summary intervals from the appropriate CIF file. About this task You must have a summary CIF file before you begin. Procedure 1. In the Project Explorer, right-click the new project and select Import. The Import wizard opens. 2. On the Select page of the Import wizard, expand TNPM Pack Modeling and select Filter an existing Summary Wireless model. 3. Click Next. 4. Select the summary intervals that you want to keep in the model. 5. Click Next. 6. Select the summary CIF file that you want to filter. 7. Click Finish. A new CIF file is created containing only the summary intervals that you specified. Filtering an existing busy hour model You can filter a busy hour model by removing daily, weekly or monthly busy hour intervals from the appropriate CIF file. About this task You must have a busy hour CIF file before you begin. Procedure 1. In the Project Explorer, right-click the new project and select Import. The Import wizard opens. 2. On the Select page of the Import wizard, expand TNPM Pack Modeling and select Filter an existing Busy Hour Wireless model. 3. Click Next. 4. Select the busy hour intervals that you want to keep in the model. 5. Click Next. 34 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

43 6. Select the busy hour CIF file that you want to filter. 7. Click Finish. A new CIF file is created containing only the busy hour intervals that you specified. Creating a model properties file You can create a model properties file from the sample file that is provided or create your own file. Name the new model properties file according to your model and update the values in the file. Before you begin The sample file is available in the following location: C:\npm_app_studio\WirelessModelling_<version>-win32.win32.x86\ CreateModel_<version>\createmodel\sample.properties Working from a model properties file sample is recommended but if a sample file is not available, create a file with the following properties and save it with an appropriate file name. Note: If you are using a text editor that has word wrap functionality, ensure that it is turned off. Procedure 1. Edit a new file or an existing model properties file. Save the file with the file name model_name_model.properties. Where model_name is the name of the model that the model properties file describes. 2. Update the file with the properties shown in this table. Do not put a space between the property and the value. For example PACK_VERSION= Property Description Example PACK_SYMBOLIC_NAME The user-defined name for the Tivoli Netcool Performance Manager common pack data model, it must be unique for each model. ibm.tnpm.net.mobile.lte.hua.eutran Note: Ensure that the pack name is in this format only. Use only dot separator. PACK_VERSION The model version OUTPUT_DIR DB_HOST The directory where the project is created in your local machine Host name of the system where the database is installed C:\npm_app_studio\ WirelessModelling_<version>win32.win32.x86\ CreateModel_<version>\output server.my.ibm.com Note: The other parameters that are related to database preferences like DB_PORT, DB_DATABASE_NAME, DB_USER, DB_PASSWORD, you can use the default values that are given in the sample properties file. DB_PORT Database port number The default port number is DB_DATABASE_NAME Database name The database name is vtdb NASACCESS_USER Main user schema The user schema to be configured is nasaccess NASACCESS_PASSWORD Password for nasaccess user The default password is nasaccess. Chapter 6. Creating Tivoli Netcool Performance Manager common pack data models 35

44 Property Description Example COGNOS_DIR MEASURE_DIMENSION MIN_TIMES_GRANULARITY Location of the Cognos directory. This directory contains the BmtScriptPlayer.exe file. A flag to create Measure Dimension for drill-down to target entity level. If you assign the values N the model that is created does not have the Measure Dimension section in it there by reducing the size of the model. Set the value to 5 to create data models with 5-min granularity and set the value to 15 to create the data models with 15-min granularity. C:\cognos\c10 MIN_TIMES_GRANULARITY=5 MIN_TIMES_GRANULARITY=15 3. Save the new model properties file. Generating the Tivoli Netcool Performance Manager common pack data model contents Generate the Tivoli Netcool Performance Manager common pack data model contents by running the createmodel.bat command on a model properties file, a Common Intermediate Format (CIF) file (.tnpmmodel). Before you begin To generate a model, you need a model properties file, a Common Intermediate Format (CIF) file. About this task If the path to the CIF file (.tnpmmodel), or the model properties file, contains special characters such as spaces, you must enclose the path in quotation marks. This task assumes the following file locations: v The CreateModel tool is installed in the C:\npm_app_studio\ WirelessModelling_<version>-win32.win32.x86\CreateModel_<version> directory. v A CIF file and a model properties file are stored in the C:\temp\Models directory. For more information about the createmodel command, see The createmodel command on page 87. Procedure 1. From the command line, go to the bin directory by entering the following command: cd C:\npm_app_studio\WirelessModelling_<version>-win32.win32.x86\ CreateModel_<version>\createmodel\bin 2. Enter the following command on a single line:.\createmodel.bat -generate -model C:\temp\Models\cif_file -properties C:\temp\Models\model_name_model.properties {-overwrite} Where: cif_file Name of the CIF file (.tnpmmodel). 36 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

45 Note: If you want to create a merged model with raw, summary and busy hour models that you have a created from a technology pack, you can specify the folder name where the models are available instead of the cif_file name. model_name Name of the model that the model properties file describes. If the paths contain special characters, such as spaces, you must enclose the path in quotation marks. 3. The Tivoli Netcool Performance Manager common pack data model contents are generated and placed in OUTPUT_DIR\PACK_SYMBOLIC_NAME_PACK_VERSION Where: OUTPUT_DIR Maps to the OUTPUT_DIR property in the model.properties file. PACK_SYMBOLIC_NAME Maps to the PACK_SYMBOLIC_NAME property in the model_name_model.properties file. PACK_VERSION Maps to the PACK_VERSION property in the model_name_model.properties file. Publishing a Tivoli Netcool Performance Manager common pack data model In IBM Cognos Framework Manager, you can publish a package to any folder on Tivoli Common Reporting server. Before you begin Ensure that you open the project in Framework Manager. For more information, see Opening a project in Framework Manager on page 38. Procedure 1. Select the package that you want to publish. 2. From the Actions menu, click Package > Publish Packages. 3. Specify the server to publish the package. The server where Tivoli Common Reporting is installed. 4. Optional: If you are prompted with the Log On page, enter the user name and password for the server. 5. To enable model versioning when you publish to the Tivoli Common Reporting server, select the Enable model versioning check box and type the number of model versions of the package to retain. It sets the number of model versions to retain on the server. The default value is zero for unlimited versions. 6. Optional: To delete all but the most recently published version on the server, select the Delete all previous model versions check box. 7. Click Next. 8. By default, the package is verified before it is published. If you do not want to verify your model prior to publishing, clear the Verify the package before publishing check box. To avoid problems, troubleshoot the package before Chapter 6. Creating Tivoli Netcool Performance Manager common pack data models 37

46 publishing it by using the Verify the Package Before Publishing check box in the Publish wizard to ensure that it is complete and does not contain errors. 9. Click Publish. 10. Click Finish. Note: If you have turned off the flag MEASURE_DIMENSION property in the model properties file, you might see the following message: BMT-MD-6007 The package contains only regular dimensions but no measure dimension. Results After the package is published to the server, it is available to report users. Opening a project in Framework Manager You must open a project before you can import metadata or change the existing metadata. Before you begin Ensure that you generated the Tivoli Netcool Performance Manager common pack data model contents from the file tnpmmodel file. For more information, see Generating the Tivoli Netcool Performance Manager common pack data model contents on page 36. Procedure 1. In Framework Manager, click Open from the File menu. 2. Browse to locate the project folder and click the.cpf file. 3. Click Open. 38 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

47 Chapter 7. Getting started with Common reporting This information explains how users of Tivoli Netcool Performance Manager wireless component can get started with Tivoli Common Reporting for Tivoli Netcool Performance Manager. 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 function as a common reporting platform or across the Tivoli portfolio. By using Tivoli Netcool Performance Manager - Application Studio you can extend the domain-specific reporting capabilities of technology packs to Common Reporting by deploying Tivoli Netcool Performance Manager common pack data model on your system. For best practices in creating reports by using Tivoli Netcool Performance Manager - Application Studio, see How to recipes. Copyright IBM Corp. 2015,

48 40 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

49 Chapter 8. Resource Metric Viewer You can dynamically create reports by using the Resource Metric Viewer. You can quickly create time series performance reports by using the Resource Metric Viewer. You can select an available model from the Resource Metric Viewer and from this model, you can select: Resources The set of resources to be included within the report. Metrics The set of metrics to be included in the report. Time Interval The time interval the report is to cover. Granularity The time granularity of the data that is being displayed. Alternatively, you can create a report based on an event from the Active Event List on the Resource Metric Viewer. The Resource Metric Viewer constructs the report charting the performance of the entity that is causing the event. Note: Resource Metric Viewer is available for Tivoli Netcool Performance Manager Wireless component only. Models that work with the Resource Metric Viewer Raw and combined models work with the Resource Metric Viewer. The Resource Metric Viewer can process both simple and composite models. Note: Busy Hour and Summary models have limited support with Resource Metric Viewer. Only default Busy Hour and Summary models are supported. User roles Resource Metric Viewer access is restricted to the following roles: v administrator v biserviceuser v chartadministrator v chartcreator v chartviewer Copyright IBM Corp. 2015,

50 Resource Metric Viewer setup This section covers the basic tasks required to set up the Resource Metric Viewer. For information about installing the Resource Metric Viewer, see Installing Resource Metric Viewer on page 19. Enabling the Resource Metric Viewer with existing Tivoli Netcool Performance Manager common pack data models Using the Resource Metric Viewer with legacy Tivoli Netcool Performance Manager common pack data models. Before you begin Resource Metric Viewer can be enabled only on Cognos models that have been deployed. About this task This procedure uses the rmv_admin.sh command, which can be found in <JazzSM_Home>/rmv/admin Where <JazzSM_Home> is the location where the Jazz for Service Management components are installed. By default, the JazzSM_Home for the wireless component is: /opt/ibm/jazzsm. To create or update a Resource Metric Viewer report for a model, follow these steps: Procedure v To enable Resource Metric Viewer reports for a specified pack or for all available models, run the following command: rmv_admin.sh -rmv -create -pack [pack_filename -all ] -logins password_file For example:./rmv_admin.sh -rmv -create -pack <pack_filename> -logins logins.txt You can run the rmv_admin.sh -rmv command for all models by using the -all flag. v To update Resource Metric Viewer reports based on a change to the model, run the following command: rmv_admin.sh -rmv -update_metrics -pack [pack_filename -all ] -logins password_file For example:./rmv_admin.sh -rmv -update_metrics -pack <pack_filename> -logins logins.txt You can run the rmv_admin.sh -rmv command for all packs by using the -all flag. Note: For more information about the rmv_admin.sh -rmv command, see rmv_admin command on page Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

51 Active Event List A context menu script is required to launch from the Active Event List into the Resource Metric Viewer User Interface. This script must be added to the IBM Tivoli Netcool/OMNIbus Web GUI to support launching into the Resource Metric Viewer User Interface. Note: If you have a model with both RNC and BSC, and there are RNC or BSC alarms defined. When the alarms are forwarded to OMNIbus, the alarms might not display correctly in the Resource Metric viewer. It is recommended that you label such alarms. For information about labeling these alarms, see Label alarms that might not be handled properly by the Resource Metric Viewer on page 84. AelLaunchScript file contents A IBM Tivoli Netcool/OMNIbus Web GUI menu script. A configuration script that is required to start the Resource Metric Viewer UI from the Active Event List. Copy the contents of the script in a notepad and save the file as AelLaunchScript.script.txt. dojo.require("dojo.date.stamp"); var server = +window.location.hostname+ : + window.location.port + / ; var namespace = p + {$param.portletnamespace}.replace( 0x002d, m ) + pns_ ; var alarmid = {@TNPMWAlarmId} ; var nodename = {@TNPMWHost} ; var nodeip = {@NodeAlias} ; var rmvok = alarmid > 0; if(!rmvok) { alert("sorry, this alarm can t be opened in RMV report"); } if(dojo.isie > 6) { var aelwindow = window.parent; if(!xmlhttprequest) { aelwindow.xmlhttprequest = true; } } try { EventBroker.sendEvent(namespace, { name: " NavigationNode: "rmv.ael.nav", pageinstanceref: "AELReport", switchpage: false, message: {alarmid : alarmid, nodename:nodename, nodeip:nodeip} }); } catch(e) { console.info(e); } Chapter 8. Resource Metric Viewer 43

52 Using the Resource Metric Viewer The Resource Metric Viewer allows you to create dynamic reports. About this task You can create dynamic reports by using the Resource Metric Viewer: v By selecting a subset of resources and metrics available within a model. v By selecting an event from the Active Event List, which creates a report that is based on the performance of the relevant entity. Logging in to the reporting interface Depending upon your organization s deployment of Tivoli Common Reporting, you can access the reporting interface directly or through Dashboard Application Services Hub. About this task With the Common Reporting interface, you can perform simple lightweight tasks as well as more advanced scalable reporting that is provided by IBM Cognos Business Intelligence Reporting. v Create on-demand reports. v Use the Web-based report authoring. v reports Access the reporting interface: Dashboard Application Services Hub Procedure Log in to the reporting interface from the Dashboard Application Services Hub login page. Both Dashboard Application Services Hub and Tivoli Common Reporting are installed in the same application serving environment, and the reporting interface is integrated with Dashboard Application Services Hub. Access is determined by user roles associated with user IDs. The role that you need to access Tivoli Common Reporting is tcrportaloperator. See Authentication and authorization in Tivoli Common Reporting. v Access the reporting interface from Dashboard Application Services Hub as follows: 1. Open a web browser and enter the following URL for the Jazz for Service Management UI and reporting server: For example: Where: host.domain is the fully qualified host name or IP address of the Jazz for Service Management UI and reporting server. When single sign-on (SSO) is enabled, ensure that you use the fully qualified host name in the URL of the Jazz for Service Management reporting and UI server. SSO requires that the browser pass LTPA cookies to the Jazz for Service Management application server, and these cookies contain the fully qualified host name. 44 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

53 port is the secure HTTP port number that was specified during installation. The default value is /DASH_context_root is the context root for the console that was specified during installation. The default value is /ibm/console. 2. On the Dashboard Application Services Hub login page, enter the user ID and password. Ensure that user ID has access to Tivoli Common Reporting. Click Log in. The Dashboard Application Services Hub Welcome page opens. 3. In the navigation bar, click Reporting > Common Reporting. The Common Reporting portal is displayed within a Dashboard Application Services Hub portlet page. v Access the reporting interface directly as follows: 1. Open a web browser and enter the following URL for the reporting interface: For example: Where: host.domain is the fully qualified host name or IP address of the Jazz for Service Management reporting server. Note: When single sign-on (SSO) is enabled, ensure that you use the fully qualified host name in the URL of the Jazz for Service Management reporting server. SSO requires that the browser pass LTPA cookies to the Jazz for Service Management application server, and these cookies contain the fully qualified host name. port is the non secure HTTP port number that was specified during installation. The default value is Check with your organization s Jazz for Service Management administrator if you are unsure of the URL. 2. On the Log on to IBM Cognos Software page, enter the user name and password. Click OK. The Common Reporting portal opens. Constructing a report by selecting a subset of resources and metrics By using the Resource Metric Viewer, you can create dynamic reports by distilling the resource and metric set available for a specific model. Procedure 1. Log in to Dashboard Application Services Hub as the Resource Metric Viewer user. 2. Click Performance > Resource Metric Viewer Selection to open the Resource Metric Viewer tab in the Dashboard Application Services Hub. Chapter 8. Resource Metric Viewer 45

54 3. You can select a model by using one of the following methods: a. Select a model from the Models list. b. Click an entry from the Saved Selections list to auto populate the information into the fields. c. Double-click an entry from the Saved Selections list to auto populate the fields and open the report in new window. 4. Use the Filter field to help you locate a specific model. Type the name of the model, the model name is automatically populated. 5. Click the Direct Parents Only check box if you would like the following Parent Entity and GrandParent Entity list auto-populated with the direct parents of the selected entity. If you select the Direct Parents Only check box, skip to step 8. Note: If the situation occurs that there are multiple direct parents, you must choose from the available parent entities by following steps Select a focal entity from the Focal Entity list. This entity is the main entity from which you want to view metrics. 7. Optional: Select Parent Entity and Grand Parent Entity from the list. Note: The inclusion of a Parent Entity or Grand Parent Entity selection is to allow filtering on the main entity that you are reporting against. For example, if you want to report on all cells for a particular geographical area, then you can select that region that can filter out all Cells that are not part of that region. 8. Optional: Select the Save Selections check box to save this selection to Saved Selections list. Place the cursor in the Saved Selections list and press Enter for the selection to be added to the list in the cursor location. 9. Click Open in New Window to display the results of your selection. The Open in New Window option is present so that your results are displayed in 46 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

55 a new window, and, therefore, able to use all space available in a browser window. The Resource Metric View Prompt Page is displayed, you can further distill the set of metrics to be included in your report by selecting individual resources and metrics. Note: The Resource Metric Viewer Selection settings from the previous session are saved and displayed when you log in again. 10. In the Entity Selection section of the Resource Metric View Prompt Page, choose from the set of resources made available through your GrandParent Entity, Parent Entity, and Focal Entity selection in the initial Resource Metric Viewer Selection page. The Entity Selection section displays two Choice fields followed by a Results field. The possible contents of each successive field is updated by the selection in the previous fields. To correctly distill the list of resources you require, follow these steps: a. Select the vendor from the Vendor field. b. Select the technology of the model from the Technology field. c. For each entity, use the Keywords field to filter the set of results. Use the '%' symbol, which acts as a wildcard, plus any character string to construct the filter. Click Search to implement the filter. If you want to find the children for parent entities, you can select the parent entities on the left, and then click Search on the child entity on the right. d. Select those resources that are relevant within the Choice field. If you want the KL children that are displayed in the Choice field on the right, select it and click the Search button under Region. e. Select the resources that you require from the Results field and use the Insert and Remove buttons to set the final selection of resources. Chapter 8. Resource Metric Viewer 47

56 11. In the Metric Selection section of the Resource Metric View Prompt Page, choose from the set of metrics available. a. Filter the set of metrics by using the Keywords field. Use the '%' symbol, which acts as a wildcard, plus any character string to construct the filter. Click Search to implement the filter. Note: You can select UDC from the Metric Selection list to create a report based on UDCs. b. Select the metrics that you require from the Results field and use the Insert and Remove buttons to set the final selection of metrics. 12. Set the granularity of the time series by using the Time Granularity list. 13. Set the time frame of the report by using the Date Range list, or select a custom date range by using the Start Time and End Time calendar fields. 14. Set the display format of the output by using the Options section. By using the Options selection, you can do the following: v Choose between a Linear and Logarithmic chart. Click Logarithmic if you are plotting metric sets that contain massively disparate values; for example, one metric set might cover values 0-1, and another set might cover values v Choose between Chart by entity (one entity per chart) and Chart by metric (one metric per chart). 48 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

57 v Enable or disable the display of data points on the chart. Click Show data point on chart to show the data points on the chart. By default, No data point on chart is selected to disable the display of data points on the chart. 15. Click Finish. You can view the report that is based on your selections. Results You can see the Resource Metric View report that appears as follows: What to do next If you want to revert to the prompt page to edit your selection, click the Run ( ) button on the upper right of the page. The prompt page retains the previously selected entities. Related tasks: Creating user-defined counters on page 59 To successfully create UDCs, you must understand mathematical and algebraic expressions. Constructing a report based on KPI comparisons By using the Resource Metric Viewer, you can create dynamic reports by distilling the resource and metric set available for a specific model. Procedure 1. Log in to Dashboard Application Services Hub as the Resource Metric Viewer user. 2. Click Performance > Resource Metric Viewer Selection to open the Resource Metric Viewer tab in the Dashboard Application Services Hub. Chapter 8. Resource Metric Viewer 49

58 3. You can select a model by using one of the following methods: a. Select a model from the Models list. b. Click an entry from the Saved Selections list to auto populate the information into the fields. c. Double-click an entry from the Saved Selections list to auto populate the fields and open the report in new window. 4. Use the Filter field to help you locate a specific model. Type the name of the model, the model name is automatically populated. 5. Click the Direct Parents Only check box if you would like the following Parent Entity and GrandParent Entity list auto-populated with the direct parents of the selected entity. If you select the Direct Parents Only check box, skip to step 8. Note: If the situation occurs that there are multiple direct parents, you must choose from the available parent entities by following steps Select a focal entity from the Focal Entity list. This entity is the main entity from which you want to view metrics. 7. Optional: Select Parent Entity and Grand Parent Entity from the list. Note: The inclusion of a Parent Entity or Grand Parent Entity selection is to allow filtering on the main entity that you are reporting against. For example, if you want to report on all cells for a particular geographical area, then you can select that region that can filter out all Cells that are not part of that region. 8. Optional: Select the Save Selections check box to save this selection to Saved Selections list. Place the cursor in the Saved Selections list and press Enter for the selection to be added to the list in the cursor location. 9. Click Open in New Window to display the results of your selection. The Open in New Window option is present so that your results are displayed in 50 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

59 a new window, and, therefore, able to use all space available in a browser window. The Resource Metric View Prompt Page is displayed, you can further distill the set of metrics to be included in your report by selecting individual resources and metrics. Note: The Resource Metric Viewer Selection settings from the previous session are saved and displayed when you log in again. 10. In the Entity Selection section of the Resource Metric View Prompt Page, choose from the set of resources made available through your GrandParent Entity, Parent Entity, and Focal Entity selection in the initial Resource Metric Viewer Selection page. The Entity Selection section displays two Choice fields followed by a Results field. The possible contents of each successive field is updated by the selection in the previous fields. To correctly distill the list of resources you require, follow these steps: a. Select the vendor from the Vendor field. b. Select the technology of the model from the Technology field. c. For each entity, use the Keywords field to filter the set of results. Use the '%' symbol, which acts as a wildcard, plus any character string to construct the filter. Click Search to implement the filter. If you want to find the children for parent entities, you can select the parent entities on the left, and then click Search on the child entity on the right. d. Select those resources that are relevant within the Choice field. If you want the KL children that are displayed in the Choice field on the right, select it and click the Search button under Region. e. Select the resources that you require from the Results field and use the Insert and Remove buttons to set the final selection of resources. Chapter 8. Resource Metric Viewer 51

60 11. In the Metric Selection section of the Resource Metric View Prompt Page, choose from the set of metrics available. a. Filter the set of metrics by using the Keywords field. Use the '%' symbol, which acts as a wildcard, plus any character string to construct the filter. Click Search to implement the filter. Note: You can select UDC from the Metric Selection list to create a report based on UDCs. You can select only one metric for comparison of data. Comparison of data on time basis can be done for a single metric only. b. Select the metrics that you require from the Results field and use the Insert and Remove buttons to set the final selection of metrics. 12. Set the time frame of the report by using the Date Range list. If you want to do a comparison, the following options are available: Option Compare Daily Compare Week Compare Month Description This compares data for Today, Yesterday and Same Day Last week. Time Granularity set for this option is hourly (0 to 23 hours of a day). This compares data of current week and previous week data. Time Granularity for this option is daily (1 to 7 days of a week). This will compare data of current month with last month data. Time granularity for this option is daily (1 to 28 or 29 or 30 or 31 days of a month). Note: Granularity of the time series is not available for comparison. Granularity for each option is set and shows the report by using the default granularity. This information is always displayed in a chart. 52 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

61 13. Set the display format of the output by using the Options section. By using the Options selection, you can do the following: v Choose between a Linear and Logarithmic chart. Click Logarithmic if you are plotting metric sets that contain massively disparate values; for example, one metric set might cover values 0-1, and another set might cover values v Enable or disable the display of data points on the chart. Click Show data point on chart to show the data points on the chart. By default, No data point on chart is selected to disable the display of data points on the chart. Note: If you are doing a comparison chart, Chart by entity option alone is displayed. 14. Click Finish. You can view the report that is based on your selections. Chapter 8. Resource Metric Viewer 53

62 Results You can see the Resource Metric View report that appears as follows: What to do next You can change the Date Range option and click Refresh to change the report. If you want to revert to the prompt page to edit your selections, click the Run ( ) button on the upper right of the page. The prompt page retains the previously selected entities. Related tasks: Creating user-defined counters on page 59 To successfully create UDCs, you must understand mathematical and algebraic expressions. Removing the saved selections from Resource Metric Viewer Selection page Use this information to remove the saved selections from the selection page. About this task To remove the saved selections from the selection page, follow these steps: Procedure 1. Go the following folder: cd /opt/ibm/jazzsm/rmv/rmvselection/smadmin/ 54 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

63 2. Delete the contents from the file rmvselection.xml as follows: > rmvselection.xml 3. Reopen the Resource Metric Viewer Selection page to see that all the saved selections are removed. Configuring launch-in-context Active Event List on Resource Metric Viewer Adding a menu script to start the Resource Metric Viewer UI from the Active Event List (AEL). About this task You must create a configuration script before you follow the steps in this procedure. The script content can be found in AelLaunchScript file contents on page 43. Copy the contents in a text file and save the file as AelLaunchScript.script. Procedure 1. Log in to Jazz for Service Management. For more information, see Logging in to the reporting interface on page Click Administration > Event management Tools > Tool Configuration. 3. Click the Create Tool button. 4. Enter the name of the script in the Name field. For example, RMV. If IBM Tivoli Netcool/OMNIbus Web GUI and Resource Metric Viewer are available on the same Jazz for Service Management server, follow these steps: a. Select Script in the Type list. b. Copy the contents of the AelLaunchScript configuration file contents into the Script Commands section. c. Move Netcool_OMNIbus_Admin and Netcool_OMNIbus_User options to the Selected area in the Access Criteria pane. If IBM Tivoli Netcool/OMNIbus Web GUI and Resource Metric Viewer are available on different Jazz for Service Management servers, follow these steps: a. Select CGI/URL in the Type list. b. Copy the contents of the AelLaunchScript configuration file contents into the Script Commands section. c. Move Netcool_OMNIbus_Admin and Netcool_OMNIbus_User options to the Selected area in the Access Criteria pane. Next steps 5. Click Save. 6. Click Administration > Event management Tools > Menu Configuration. 7. From the Available menus list, select alerts and click Modify. The Menus Editor window is displayed. 8. Move the script that you created from Available items to Current items and position it in your preferred location. If the Active Event List is already open, close and reopen it to see the new menu option. 9. Click Save. Chapter 8. Resource Metric Viewer 55

64 The menu is now updated in the AEL, and is added as an entry in the Available items menus list. Note: If the Active Event List is already open, you must close and reopen it to see the new menu option. Results When you right-click on an entry on the Active Event List, you see the RMV script as a selectable option in the menu. Select RMV to see a Resource Metric Viewer AEL report. Related tasks: Generating the reports To generate a Tivoli Netcool Performance Manager report, an event is selected from Active Events List. Configuring single Sign-on (SSO) settings Use these instructions to establish single sign-on support. Before you begin Prerequisite settings for enabling SSO between Tivoli Netcool Performance Manager for Wireless and Jazz for Service Management. v Tivoli Netcool Performance Manager for Wireless and Jazz for Service Management are running in same domain and LTPA SSO is enabled on Jazz for Service Management. v Ensure that Security Directory Server is configured on Tivoli Netcool Performance Manager for Wireless with pass through authentication with an LDAP repository that is used by the Dashboard Application Services Hub portal. v The LDAP user subtree in the Security Directory Server repository matches with the user tree of the common LDAP repository. v The user IDs that are added on Tivoli Netcool Performance Manager for Wireless match with the IDs on the common LDAP repository. v Dashboard Application Services Hub must be accessed with host name only. Procedure 1. Log in to Dashboard Application Services Hub portal with host name only and not with IP address. 2. Export the LTPA key for Dashboard Application Services Hub. 3. Copy the exported ltpa.key to the Tivoli Netcool Performance Manager for Wireless Server at this location: /appl/virtuo/ 4. Add the following properties in the /appl/virtuo/conf/as/ldapdefault.properties file for SSO configuration: v v v ltpa.key file path WmLdapApi.SSO.ltpa.key.filepath=/appl/virtuo/ltpa.key Configurable password for keystore file WmLdapApi.SSO.ltpa.key.password=changeit (Same as the exported the ltpa.key file in step 3.) Prefix to be used for User DN entry, as used on the common LDAP user repository 56 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

65 v v v WmLdapApi.SSO.ltpa.DNPrefix =uid= /cn= (Depends on the interacting application. ID for the admin user account that is used to bind to Security Directory Server. WmLdapApi.SSO.admin.user =sysadm Password for the admin user account that is used to bind to Security Directory Server. WmLdapApi.SSO.admin.password =Sysadm01 (Password to be set for sysadm user.) Domain name for Dashboard Application Services Hub and Tivoli Netcool Performance Manager for Wireless Server. WmLdapApi.SSO.dash.domain=ibm.com This value must be the same as the one configured in Dashboard Application Services Hub SSO settings. See Configuring SSO on the application server. v v Note: If the domain is configured as.ibm.com, then the value in WmLdapApi.SSO.dash.domain key must be also.ibm.com. LTPA cookie name used by dash application WmLdapApi.SSO.ltpa.cookie.name=LtpaToken2 This value must be the same as the one configured in Dashboard Application Services Hub SSO settings. See Configuring SSO on the application server. If value does not exist, then add LtpaToken2 value for LTPA V2 cookie name. By default, if the value does not exist it is left blank. This key is case-sensitive and must match with ldap.properties. Add the sysadm user in WmLdapApi.adminUserNames and change the values for adminuserdnsuffix with appropriate ldap tree entry values in ldap-default.properties. WmLdapApi.adminUserNames = admin,sysadm WmLdapApi.adminUserDNPrefix = uid= WmLdapApi.adminUserDNSuffix = ou=people,dc=ibm,dc=com 5. Optional: Run the following script with password as an argument as user virtuo:./conf_encode Sysadm01 Encryption of passwords can be done by using the encryption script in the Wireless product at the following location: /appl/virtuo/bin Output is an encrypted password. For Replace this encrypted password as a value for the WmLdapApi.SSO.admin.password key in ldap-default.properties. 6. Restart the Jazz for Service Management server. Generating the reports To generate a Tivoli Netcool Performance Manager report, an event is selected from Active Events List. Procedure 1. In the Dashboard Application Services Hub navigation, select Incident ( ) > Events > Active Event List (AEL). 2. Right-click an event from the IBM Tivoli Netcool/OMNIbus Web GUIActive Events List. A list menu appears that contains the new menu options TNPMforWireless Report and RMV. Chapter 8. Resource Metric Viewer 57

66 3. Select the TNPMforWireless Report option to display a new browser window. Log in to Tivoli Netcool Performance Manager. If you are not logged in to Tivoli Netcool Performance Manager server, the login screen appears. The report that is associated with the selected event is displayed. Subsequent event selections followed by selection of the TNPMforWireless Report menu option display the report that is associated with the event in the same browser window by using the Single Sign On (SSO) functionality. The same browser window is always used, if one is still displayed. The report appears as follows: Note: If a user logs out from either Wireless application that is opened in a new tab on the same browser or from the Dashboard Application Services Hub application, both the applications log out the user. 4. Select RMV to see a Resource Metric Viewer AEL report that appears as follows: 58 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

67 User-Defined Counters for reporting User-Defined Counters or User-Defined Calculations (UDCs) are performance measurements that you create. This counter is in contrast to the other performance measurements that are created at the time of system setup and not subject to modification. About this task For more information about UDCs, see User-Defined Calculations in Using Tivoli Netcool Performance Manager - Wireless Component. Creating user-defined counters To successfully create UDCs, you must understand mathematical and algebraic expressions. Procedure 1. Log in to Dashboard Application Service Hub as the Resource Metric Viewer user. See Logging in to the reporting interface on page Click Performance > Resource Metric Viewer UDC to open the Resource Metric Viewer UDC page. 3. Select a model from the Models list. 4. Select a focal entity from the Focal Entity list. This entity is the main entity from which you want to view metrics. Note: UDC must be created by using selected entity. Do not change the entity when you create the UDC. Chapter 8. Resource Metric Viewer 59

68 5. Select a metric group from the Metric Group list. 6. Select the counters for the UDC formula by using one of the following methods: a. Double-click any one of basic metric counters from the Basic Metric Counters List to insert a Tivoli Common Reporting object into the formula area. Or b. Type the Tivoli Common Reporting object name into the formula area. For example, AVE_NON_AVAIL_DUE_INT ( ave_non_avail_due_int ) TCR Object name : [Nokia GSM BSS].[NOK_BSC_TRX_AVAIL].[AVE_NON_AVAIL_DUE_INT (ave_non_avail_due_int ) ] Important: Use ( ) symbol to define the order of execution of expressions in the formula. The formula that is typed is not validated and if an error is encountered during report execution the formula must be redefined. 7. Optional: Click Filter to search for a specific basic metric counter. Click Clear to refresh the counters in Basic Metric Counter list. 8. Select the operator that is used in the calculation. Note: Currently, +,-,*, and / operators are supported. 9. Select the aggregation function that is applicable for the calculation from Aggregator list. The default aggregation function is sum. 10. Repeat step 6 to build your formula. You can see your new formula in the Create New Formula field. 11. Hover your mouse over the Example link to see a detailed example formula. 12. Enter a unique name to the new formula that you have created in the Name For New Counter field. 13. Click Save. A message appears that displays the newly created user-defined formula. 14. Click OK to confirm the new user-defined formula. The new user-defined counter name appears in the User Defined Counters field. Results All the saved UDCs are available in the Resource Metric Viewer Prompt Page under Metric Selection area. All UDCs are available under the name UDC. You can select the required UDC for reporting. What to do next Generate the Resource Metric Viewer report for the selected UDCs. Related tasks: Constructing a report by selecting a subset of resources and metrics on page 45 By using the Resource Metric Viewer, you can create dynamic reports by distilling the resource and metric set available for a specific model. 60 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

69 Updating user-defined counters Updating the existing user-defined counters. Procedure 1. Log in to Dashboard Application Service Hub as the Resource Metric Viewer user. 2. Click Performance > Resource Metric Viewer UDC to open the Resource Metric Viewer UDC page. 3. Select a model from the Models list. 4. Select a focal entity from the Focal Entity list. This is the entity for which you have created the UDC that must be modified. 5. Select a metric group UDC from the Metric Group list. The list of defined UDCs appear in User Defined Counters field. 6. Double-click on the UDC that must be modified. 7. The existing formula appears in the Create New Formula field. 8. Modify the UDC formula. Note: You can modify the metric counters that are used in the formula, operators and aggregate functions that are defined in the formula. 9. Click UPDATE. 10. Click OK to accept the changes. The modifications to the UDC are saved. Viewing user-defined counters To view the saved user-defined counters from the Resource Metric Viewer UDC page. Procedure 1. Log in to Dashboard Application Service Hub as the Resource Metric Viewer user. See Logging in to the reporting interface on page Click Performance > Resource Metric Viewer UDC to open the Resource Metric Viewer UDC page. 3. Select a model from the Models list. 4. Select a focal entity from the Focal Entity list. 5. Select UDC from the Metric Group list. A list of all the UDCs are populated in the User Defined Counters field. 6. Double-click a UDC from the User Defined Counters list to see the formula that is displayed in the Create New Formula area. Results All the saved UDCs are available in the Resource Metric Viewer Prompt Page under Metric Selection area. All UDCs are available under the name UDC. You can select the required UDC for reporting. Chapter 8. Resource Metric Viewer 61

70 Deleting user-defined counters To delete the saved user-defined counters from the Resource Metric Viewer UDC page. Procedure 1. Log in to Dashboard Application Service Hub as the Resource Metric Viewer user. See Logging in to the reporting interface on page Click Performance > Resource Metric Viewer UDC to open the Resource Metric Viewer UDC page. 3. Select a model from the Models list. 4. Select a focal entity from the Focal Entity list. 5. Select UDC from the Metric Group list. A list of all the UDCs are populated in the User Defined Counters field. 6. Select the UDC that you want to delete and click Delete. Results The deleted UDC is not available in the Resource Metric Viewer Prompt Page under Metric Selection area. Importing and exporting a UDC You can import or export an existing UDC by using the command line interface. All the Resource Metric Viewer UDCs are deleted when Resource Metric Viewer is reinstalled. If a model is republished, then the UDCs specific to that model are deleted. It is important to back up the existing UDCs before you reinstall Resource Metric Viewer or republish a model. About this task Follow these steps to export the UDCs and import after the installation or publish is complete. Procedure 1. Export ORACLE_HOME by using the following commands as root user: export ORACLE_HOME=/appl/oracle/product/ /db_1 2. Go to <JAZZSM_HOME>/rmv/admin folder. 3. To export the information about the existing UDCs, run the following command:./expimprmvudc.sh -u <DB_USERNAME> -p <PASSWORD> -e For example:./expimprmvudc.sh -u virtuo -p Virtuo01 e This command creates rmv_udc_backup table, which contains all the information of the existing UDCs. 4. To import the UDCs, use the following command:./expimprmvudc.sh -u <DB_USERNAME> -p <PASSWORD> -i -pack all <PACK_NAME> a. To import the UDCs defined for all the packs that are created after the reinstallation of Resource Metric Viewer, use the following command:./expimprmvudc.sh -u virtuo -p Virtuo01 -i -pack all 62 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

71 b. To import all the UDCs defined for a specific pack that are created after the reinstallation of Resource Metric Viewer, use following this command:./expimprmvudc.sh -u virtuo -p Virtuo01 -i -pack <nokia.gsm.bss> Limitations in using UDCs in Resource Metric Viewer reports Some limitations when you use UDCs in Resource Metric Viewer reports. v If the Resource Metric Viewer is reinstalled, all the UDCs are deleted and must be re-created manually. Note: Before you delete the model or reinstall the Resource Metric Viewer, follow the steps from Importing and exporting a UDC on page 62 to export the UDCs and import them after the model is republished or the Resource Metric Viewer is reinstalled. Resource Metric Viewer administration This section covers the administration tasks you may perform post setup of the Resource Metric Viewer. Modify the Resource Metric Viewer template The Resource Metric Viewer uses an XML Cognos report template. You can modify this report if you wish in report studio to change the prompts, Images, and operation of the Resource Metric Viewer. About this task The resource metric viewer template is located in <JazzSM_Home>/rmv/templates Where <JazzSM_Home> is the location where the Jazz for Service Management components are installed. By default, for the wireless component this is: /opt/ibm/jazzsm. The default Resource Metric Viewer report is designed so that no more than 9 resources or metrics will be shown in the chart legend. To update the model and refresh all Resource Metric Viewer reports, do either of the following, that is, use either the XML process or the Report Studio process: Procedure v Using XML: 1. Go to <JazzSM_Home>/rmv/templates. 2. Open and update the existing template. 3. Make sure to update the model path by editing the following XML: <modelpath>/content/package[@name= gsm.sbh.3 ]/model [@name= T16:19:19.587Z ]</modelpath> so that the modified report has the following XML: <modelpath>/content/package[@name= [BIPACKNAME] ]</modelpath> 4. The name of the Resource Metric Viewer template must be rmv_template.xml. 5. To update Resource Metric Viewer reports, run the following command: rmv_admin.sh -rmv -update_reports [ -pack pack_filename -all ] -logins password_file For example: Chapter 8. Resource Metric Viewer 63

72 ./rmv_admin.sh -rmv -update_reports -pack <pack_filename> -logins logins.txt You can run the rmv_admin.sh -rmv command for all packs by using the -all flag. v Using Report Studio: After Resource Metric Viewer has been enabled for at least one pack, the template will be available in common reporting in a folder named rmv. 1. Open Resource Metric Viewer template in report studio and save under a new name. 2. Update the report. 3. Using Tools > Show Specifications copy XML into new file. 4. Modify <modelpath> file to the following: <modelpath>/content/package[@name='[bipackname]']</modelpath> 5. Replace report in <JazzSM_Home>/rmv/templates with updated report template. 6. To update Resource Metric Viewer reports, run the following command: rmv_admin.sh -rmv -update_reports [ -pack pack_filename -all ] -logins password_file For example:./rmv_admin.sh -rmv -update_reports -pack <pack_filename> -logins logins.txt You can run the rmv_admin.sh -rmv command for all packs by using the -all flag. Note: For more information on the rmv_admin.sh -rmv command, see rmv_admin command on page Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

73 Chapter 9. Data availability reporting Data availability or data coverage describes the completeness of data for a report. Summaries are executed every day that are based on data availability. The summary will run if there is data that is loaded for a period, regardless of the amount of data. No percentage threshold of data availability is used. If there is no data present for the period that is being summarized, then the summary is not initiated. However, summaries can be run to ignore data availability calculations, by executing the summaries on the command line. You might want to see overall data loading performance at a high level for a few key blocks or data sources. And where there is missing data at a high level, the you must be able to drill down into the lower-level resource instances. The Tivoli Netcool Performance Manager wireless system includes the data availability feature to facilitate that the system is actually loading data. The Tivoli Netcool Performance Manager wireless system can load and store this data. However, IBM recommends that monitoring of data availability is concentrated on key resource types and metric groups, which are being used for reporting. Typically, when there is missing data, it is for a whole block or object that is set so this is reflected without monitoring many tables. After the summaries for a particular technology pack are identified, you must create a data availability Cognos model that contains these summaries and install the Cognos model on Jazz for Service Management. Overview of generating data availability reports You can follow these steps to create, publish, and view the data availability or data coverage reports. Before you begin v Ensure that you have a fully operational Tivoli Netcool Performance Manager Wireless system and Tivoli Netcool Performance Manager - Application Studio components installed. v Run the following commands to grant permission to the nasaccess user: sqlplus virtuo/<password>@vtdb grant execute on calc_table_hourly_da to nasaccess; grant select on da_hourly_tmp to nasaccess; Procedure 1. Monitoring the key traffic tables for data availability on page 66 a. Selecting tables for data availability for a vendor neutral technology pack on page 68 b. Selecting tables for data availability for a vendor specific technology pack on page Generating data availability components on page Provisioning the UDCs and summaries to Tivoli Netcool Performance Manager Wireless system on page 73 Copyright IBM Corp. 2015,

74 4. Extracting and publishing daily summary model on page Scheduling and running summaries on page Generating data availability reports on page Publishing the generated data availability reports on page Verifying the data availability report contents on page 79 Monitoring the key traffic tables for data availability IBM recommends these guidelines for monitoring the key traffic tables for different technology packs for generating the data availability reports. To select the appropriate tables to monitor for data availability, follow these guidelines: v Load the complete data. v Locate the tables that have data that is loaded by using the SQL statements that are stated in Selecting tables for data availability for a vendor neutral technology pack on page 68 and Selecting tables for data availability for a vendor specific technology pack on page 68. v From the list of tables in the result set, select the tables that are common from entities by referencing the raw input files from network elements. Check the Product Requirements Specification and Functional Specification for a technology pack for blocks in raw files that are mapping to the abbreviated KPI group name. v KPI group abbreviated names are the base for the table name without the vendor prefix. Some example tables from selected technology packs: Table 2. GSM/GPRS Huawei BSS Technology Pack Network Object Key KPI Groups Loader Block Raw Traffic Table BSC BSC.Huawei.GSM.Access_ traffic_volume B hua_bsc72018vol_tab BSC BSC.Huawei.GSM.Ps_capability B hua_bsc73217_tab M3UA SCTP_Link SCTP_Link SCTP_Link M3UA_Link.Huawei.GSM.M3UA_ link_utilisation SCTP_Link.Huawei.GSM. Link_utilisation SCTP_Link.Huawei.GSM. SCTP_IP_usage SCTP_Link.Huawei.GSM. Utilisation B B B B hua_m3ualink72118_tab hua_sctplink09468_tab hua_sctplink09469_tab hua_sctplink72217_tab Table 3. Nokia BSS Technology Pack Network Object Key KPI Groups Loader Block Raw Traffic Table BSC BSC. Nokia.GSM.Quality_ of_service P_NBSC_QOS nok_bsc_qty_of_service_tab 66 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

75 Table 3. Nokia BSS Technology Pack (continued) Network Object Key KPI Groups Loader Block Raw Traffic Table Cell DLCI PCU Cell.Nokia.GSM.Traffic P_NBSC_TRAFFIC nok_cell_traffic_tab Cell.Nokia.GSM.Resource_ Availability P_NBSC_RES_AVAIL nok_cell_res_avail_tab Cell.Nokia.GSM.Packet_ Control_Unit P_NBSC_PACKET_ CONTROL_UNIT nok_cell_pkt_ctl_unit_tab Cell.Nokia.GSM.Handovers P_NBSC_HO nok_cell_handovers_tab DLCI.Nokia.GSM. Frame_Relay PCU.Nokia.GSM.PCU_ Utilization P_NBSC_FRAME_ RELAY P_NBSC_PCU_ UTILIZATION nok_dlci_frame_relay_tab nok_pcu_util_tab Table 4. Motorola BSS Technology Pack Network Object Key KPI Groups Loader Block Raw Traffic Table BSC Performance Indicators Cell performance indicators Ethernet_link_mo performance indicators Gb performance indicators LAPD performance indicators PCU performance indicators Processor performance indicators Signalling_Link performance indicators C25 performance indicators BSC.Motorola.GSM.Cell_ based_busy_hours bsc_all mot_bsc_cell_based_bhs_tab BSC.Motorola.GSM.SCCP_ Performance_and_utolization bsc_statistics mot_bsc_sccp_prf_n_util_tab Cell.Motorola.GSM.AMR_ TCH AMR_TCH mot_cell_amr_tch_tab Ethernet_link_mo.Motorola. GSM.Ethernet_link_statistics eth_statistics mot_eth_link_stats_tab Gb.Motorola.GSM.GPRS_ Utilization gbl_statistics mot_gblink_gprs_utils_tab LAPD.Motorola.GSM.BSS_ data_transmission sdl_statistics mot_lapd_bss_dat_transm_tab PCU.Motorola.GSM.PCU_ overview pcu_statistics mot_pcu_pcu_ov_tab Processor.Motorola.GSM. GPRS_Utilization pproc_statistics mot_proc_gprs_utilizat_tab Signalling_Link.Motorola.GSM. MTP_C7_utilization mti_statistics mot_siglnk_mtp_c7_util_tab X25.Motorola.GSM.BSS_data_ transmission cbl_statistics mot_x25_bss_data_transm_tab Note: For KPI group Signalling_Link.Motorola.GSM.MTP_C7_utilization, the summary is defined at Signalling_point level, instead of Signalling_Link object. As the Signalling_point level is connected, there can be too much detail at Signalling_Link level for data availability. Table 5. GPRS_Huawei_CN_SGSN Technology Pack Network Object Key KPI Group Loader Block Raw Traffic Table SGSN SGSN.Huawei.GPRS.SGSN_LLC M hua_sgsn_lls_tab Routing_Area M3UA_LinkSet Routing_Area.Huawei.GPRS.Iu_ Mode_Attach_with_RAI M hua_iu_mode_attach_rai_tab M3UA_LinkSet.Huawei.GPRS. M3UA_link_set M hua_m3ua_link_set_tab Chapter 9. Data availability reporting 67

76 Selecting tables for data availability for a vendor neutral technology pack Select a set of key tables that you are using to report on statistics. This means mapping the KPI groups. For example, Cell.Neutral.TCH, Cell.Neutral.SDCCH back to the traffic tables where their data is stored. Additionally, in a cross vendor environment, vendor neutral tables can provide a view of loading data availability by vendor. For optimal result, it is essential to select a vendor neutral traffic table that is populated by all the available vendor loadmaps. About this task Use the following SQL query sample to select all the vendor neutral cell tables that you are loading. This query lists all vendor neutral cell tables that are loaded by both Nokia GSM BSS loadmap and Motorola GSM BSS loadmaps. Example select unique(t.table_name) from da_loaded_tables da, wmd_dict_table t where t.table_name like `VNL_%` and t.entity_id = (select entity_id from wmn_entity where entity_name = `Cell`) and da.start_date = to_date(` :00:00`, `YYYY-MM-DD HH24:MI:SS`) and t.table_name in (select upper(lc.tabname) from lc_loadmap lc, lc_ruleset r, lc_datasource d where lc.ruleset_id = r.ruleset_id and d.datasource_id = r.datasource_id and d.datasource_name = `Nokia BSS` and r.type = `Neutral` union select upper(lc.tabname) from lc_loadmap lc, lc_ruleset r, lc_datasource d where lc.ruleset_id = r.ruleset_id and d.datasource_id = r.datasource_id and d.datasource_name = `Motorola BSS` and r.type = `Neutral`) order by 1; Note: Union is used to include all the vendor specific technology packs that are loaded to the common vendor neutral tables. What to do next Save this list of tables to a properties file. For example, nokia_gsm_bss_tables.properties file. Selecting tables for data availability for a vendor specific technology pack In this example, reporting is done by using a vendor neutral loadmap such as GSM Huawei BSS VNLM that is merged with GSM Huawei BSS vendor specific technology pack. About this task When a vendor neutral technology pack is used, raw counters may be mapped to two storage locations: 68 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

77 v The vendor neutral table. Typically, these tables are named as VNL_. v A vendor specific table that is named after the vendor. For example, HUA_. Only a subset of the metrics from the vendor specific data source is loaded into the vendor specific tables. Apply the following logic to find the vendor specific tables that are loaded with data and with vendor neutral loadmaps merged together with vendor specific loadmap: v For the data source, find the blocks that are loaded to the vendor neutral tables. v Identify the vendor specific tables that are also loaded from the same block. This is to limit the number of tables to monitor. v Filter this list to include tables that are actively loaded. For example, the Tivoli Netcool Performance Manager system may have mappings for certain blocks but these blocks are not activated on the Operation And Maintenance Center (OMC). In the query below, this information is filtered for a particular day that is 10th October, where the data loaded is good. This query lists all vendor specific tables that have data loaded for a specific time interval and whose associated blocks are loaded into some corresponding vendor neutral tables. This example is based on Huawei GSM BSS Technology Pack. Example select unique(l.tabname) from lc_loadmap l, lc_ruleset r, lc_datasource d, wmd_dict_table t, da_loaded_tables da where t.table_id = da.table_id AND upper(t.table_name) = upper(l.tabname) AND trunc(da.start_date) = to_date(` :00:00`, `YYYY-MM-DD HH24:MI:SS`) AND l.ruleset_id = r.ruleset_id and d.datasource_id = r.datasource_id and d.datasource_name = `Huawei GSM BSS` and r.type = `Vendor` and l.tabname not like `nc%` and l.blockname in ( select l.blockname from lc_loadmap l, lc_ruleset r, lc_datasource d where l.ruleset_id = r.ruleset_id and d.datasource_id = r.datasource_id and d.datasource_name = `Huawei GSM BSS` and r.type = `Neutral` and l.tabname not like `nc%` group by l.blockname) group by l.tabname; This SQL query returns a list of tables that drive the data availability definition and summary definition generation. Note: If the vendor neutral loadmap is not merged with a vendor specific technology pack, use the following SQL query to extract the vendor specific tables alone: Chapter 9. Data availability reporting 69

78 select unique(l.tabname) from lc_loadmap l, lc_ruleset r, lc_datasource d, wmd_dict_table t, da_loaded_tables da where t.table_id = da.table_id AND upper(t.table_name) = upper(l.tabname) AND trunc(da.start_date) = to_date( :00:00, YYYY-MM-DD HH24:MI:SS ) AND l.ruleset_id = r.ruleset_id and d.datasource_id = r.datasource_id and d.datasource_name = Huawei GSM BSS and r.type = Vendor and l.tabname not like nc% What to do next Save this list of tables to a properties file. For example, huawei_gsm_bss_tables.properties file. Generating data availability components Using the properties file that has a list of tables, you can now generate the data availability formulas and the summaries in data availability model. Before you begin Ensure that the following prerequisites are complete: v Ensure that you have configured the JDBC driver in WirelessModelling tool preferences so that you can connect to the database to extract the summary definitions. v Ensure that you have the properties file that contains the list of tables as described in Selecting tables for data availability for a vendor specific technology pack on page 68. v Ensure that you have created the Tivoli Netcool Performance Manager common pack data model that contains a raw model as described in Creating a Tivoli Netcool Performance Manager common pack data model containing a raw data model on page 26. Procedure 1. In WirelessModelling tool, open the tnpmmodel file that you have created from the raw model. 2. Right-click TNPM Package and select Data Coverage Utilities > Generate Data Coverage components. 3. Click Browse in the Filter file field to locate the properties file you have created earlier. This file is the output file that contains the list of table names. 4. Select Table in the Metric names based on list. 5. Select the number of tables from Number of tables for each summary definition between 10 to 25. Note: If the number selected is not between 10 to 25, the generated da_summary.xml and da_udcs.xml files will be empty. 6. Click Next. 7. Select File System and locate the output directory where you want to generate the user defined calculations (UDCs) and summary XML files. 70 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

79 8. Click Finish. If the console is open, you can see the execution. To see the console view, select Window > Show view > other > General > Console. If you receive an error message that is related to summary name that exceeds 24 characters, see the workaround in Manually edit the summary name in a data availability model if the summary name exceeds 24 characters on page 82. Results You can find the da_summary.xml and da_udcs.xml files in the output directory. da_udcs.xml This file contains the generated data availability UDCs. da_summary.xml This file contains the summaries that include these UDCs at the appropriate resource type level. These UDCs and summaries must be provisioned to the Tivoli Netcool Performance Manager Wireless system. Data availability formulas The formulas for data availability are in da_udcs.xml file. For each resource type, the following user formulas are generated: Resource type data availability formula This formula gives an overview of the data availability across all the tables that are being monitored. For example, if 10 tables have been selected at Cell level then these 10 tables are included in a single formula called DA_Neutral_GSM_Cell. This formula provides the overview of the data availability at Cell level. Per table or metric group data availability formula For each table that is monitored, a single table (either named based on the table name or the metric group name) is created. For example, a metric called VNL_CELL_TCH_TAB is created. This is data availability for this table. Count metric Most data availability reports are built at a higher aggregation level that is viewing the data availability across all Cells. A count metric called DA_Neutral_GSM_Cell_count is included. This metric allows a count of Cells (or any other resource type) to be included in a summary report. Resource type data availability formulas To see a summarized view of data availability across a number of tables, a formula that combines the availability across a number of tables is required. For example, for ATM_VCC, there are 7 tables that are being monitored. This results in a UDC called DA_Nokia_ATM_VCC that monitors all ATM_VCC tables. Chapter 9. Data availability reporting 71

80 <udc-data> <uuid>dad1f5adee</uuid> <header1>da_nokia_atm_vcc</header1> <aggregator>a</aggregator> <complex>false</complex> <entity-name>atm_vcc</entity-name> <data-type>f</data-type> <field-name>da_nokia_umts_atm_vcc</field-name> <expression> (DataAvailKPI("raw", "percentile", [ATM_VCC]![{Nokia.cac_resource.measurement_seconds}]) + DataAvailKPI("raw", "percentile", [ATM_VCC]![{Nokia.aal2_packet_queue.measurement_seconds}]) + DataAvailKPI("raw", "percentile", [ATM_VCC]![{Nokia.resource_reservation.measurement_seconds}]) + DataAvailKPI("raw", "percentile", [ATM_VCC]![{Nokia.aal2_signalling.measurement_seconds}]) + DataAvailKPI("raw", "percentile", [ATM_VCC]![{Nokia.saal.measurement_seconds}]) + DataAvailKPI("raw", "percentile", [ATM_VCC]![{Nokia.vcc_measurement.measurement_seconds}]) + DataAvailKPI("raw", "percentile", [ATM_VCC]![{Nokia.RAN_Usage.Transport_Network.measurement_seconds}]))/7 </expression> </udc-data> In Tivoli Common Reporting, this is shown across a number of tables the data availability or data loading at Cell level. One of these formulas is included for each resource type that is being monitored. Traffic table data availability formulas Apart from the cross table formula above, individual per table level formulas are also generated. <udc-data> <uuid>dae2b31d7b</uuid> <header1>da_nok_nk_iproute_tab</header1> <aggregator>a</aggregator> <complex>false</complex> <field-desc>data availability for metric group ip_route_measurements table NOK_NK_IPROUTE_TAB</field-desc> <expression>dataavailkpi("raw", "percentile", [IP_Route_BTS]![{Nokia.ip_route_measurements.measurement_seconds}]) </expression> <entity-name>ip_route_bts</entity-name> <data-type>f</data-type> <field-name>nok_nk_iproute_tab</field-name> </udc-data> Data availability summaries A set of summaries is generated in da_summary.xml file. A summary is created at specific entity level. This optimization ensures that only the required summary for optimal calculation is created. This summary has the daily intervals configured. In Tivoli Common Reporting, the user can see the data availability at daily and hourly level. 72 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

81 <summary> <name>da_nokia_gsm_tru_equipment</name> <source> <entity>tru_equipment</entity> <field-list> <field> <source-field> <entity>tru_equipment</entity> <field-name>nok_tru_equip_tru_bie_tab</field-name> </source-field> <dest-field> </dest-field> </field> <field> <source-field> <entity>tru_equipment</entity> <field-name>da_nokia_gsm_tru_equipment</field-name> </source-field> <dest-field> </dest-field> </field> <field> <source-field> <entity>tru_equipment</entity> <field-name>da_nokia_gsm_tru_equipment_count</field-name> </source-field> <dest-field> </dest-field> </field> </field-list> </source> <summary-attributes> <intervals-required> <interval type="daily" source="raw"/> </intervals-required> <calculate-late-data>true</calculate-late-data> <summary-type>user</summary-type> </summary-attributes> <enabled>true</enabled> </summary> Provisioning the UDCs and summaries to Tivoli Netcool Performance Manager Wireless system Instructions on how to provision or import UDCs and summary XML files. Procedure v To import the da_udcs.xml file into the wireless system, run the kpicache_admin script by using the following syntax: kpicache_admin -u <user> -p <password> -l <filename> <dsname> Table 6. Parameters for importing the UDC Option Description -u <user> User name. Typically, sysadm. -p <password> Password -l <filename><dsname> Loads the file <filename> for the datasource <dsname>. The path to where the file is located must be specified or the script must be executed where the file is located. The name of the server must be used when you specify the <dsname>, and not the IP address. For example, kpicache_admin -u sysadm -p Sysadm01 -l da_udcs.xml Chapter 9. Data availability reporting 73

82 <server_name>.ibm.com For more information about the kpicache_admin script, see Administering Tivoli Netcool Performance Manager - Wireless Component. v To provision the da_summary.xml file on the wireless system, run the summary_admin CLI command by using the following syntax: summary_admin -c -f <filename> [-ignoreaggr <yes no>] Table 7. Parameters for importing the summaries Option Description -c Mandatory. Use this switch that is used to create a summary. -f <filename> Mandatory. The file name and path of an XML file to use for creating the summary. [-ignoreaggr <yes no>] An optional flag to ignore the average of average check. For example, summary_admin -c -f da_summary.xml For more information about the summary_admin command, see Administering Tivoli Netcool Performance Manager - Wireless Component. Extracting and publishing daily summary model Extract the summary definitions that are associated with a technology pack from the Tivoli Netcool Performance Manager database. You can then create a Tivoli Netcool Performance Manager common pack data model that has a model that report authors can use to create reports by using those summary definitions. Before you begin Ensure that you have configured the JDBC driver in WirelessModelling tool preferences so that you can connect to the database to extract the summary definitions. Procedure 1. In WirelessModelling tool, open the tnpmmodel file that you have created from the raw model. 2. In the Project Explorer, right-click the new project and select Import. 3. On the Select page of the Import wizard, expand TNPM Pack Modeling and select Import Summaries. 4. Click Next. 5. On the Database detail page, specify the following database details: Option Host Username Password Description The host server name, for example, server.ibm.com. The database user name, for example, virtuo. The database password. 6. Click Get Summaries. The database connection is tested. 7. Click Next. 8. On the Select Installed Packs page, select UDC. 74 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

83 9. Click Next. You can see all the summaries that you have provisioned previously. 10. Select all the summaries that are relevant to the technology pack for which you are creating data availability model. 11. Select the appropriate check box to filter the selected summaries by raw, hourly, daily, weekly, or monthly intervals. Click All Summaries if you want summaries for all intervals. CAUTION: Do not select all the summary definitions. Select only the definitions that you want to generate the model for. 12. Select the Update Viewer check box to update the view on the Select Summaries page. If you select individual options such as Raw, Hourly from Select Summaries area, then it displays those individual summaries. 13. Click Next. 14. Enter the name vendor and technology of the summary model A CIF file with summary model is generated. 15. Create the model properties file. For more information, see Creating a model properties file on page Generate the model. For more information, see Generating the Tivoli Netcool Performance Manager common pack data model contents on page For a data availability model, select the summary model. Chapter 9. Data availability reporting 75

84 Important: It is recommended to give the same name as the pack name with.da as the extension in uppercase to create the data availability model in the Symbolic Name field in the Deploy CIF files page. For example, nokia.gsm.bss.da. 18. Publish the summary model by using Framework Manager. For more information, see Publishing a Tivoli Netcool Performance Manager common pack data model on page 37. Scheduling and running summaries The data availability report is based on daily summary and hourly drill-down result is calculated during reporting. It is important that these summaries are executed periodically. A cron job can be set up to run the summaries as required. For performance reasons, the frequency of this run must be monitored. Procedure Note: Create the script DA_summary_cron and copy it to /appl/virtuo/admin/ common/cron location. Daily summaries can be run via the scheduler. Alternatively, the daily summary can be included in a script that is executed from crontab if the current day data availability is needed. The following line is added to the crontab: 05 * * * * WMCROOT=/appl/virtuo;export WMCROOT;/appl/virtuo/admin/common/cron/DA_summary_cron > /dev/null 2>&1 #Example Script - DA_summary_cron ########################################################### #!/bin/sh # sdate: A Bourne shell script that # prints the date n days ago. # Set the current month day and year. month=`date +%m` day=`date +%d` year=`date +%Y` daysbefore=0 # Add 0 to month. This is a # trick to make month an unpadded integer. month=`expr $month + 0` # Subtrace n from the current day. day=`expr $day - $daysbefore` # While the day is less than or equal to # 0, deincrement the month. while [ $day -le 0 ] do month=`expr $month - 1` # If month is 0 then it is Dec of last year. if [ $month -eq 0 ]; then year=`expr $year - 1` month=12 fi # Add the number of days appropriate to the # month. case $month in ) day=`expr $day + 31`;; ) day=`expr $day + 30`;; 2) if [ `expr $year % 4` -eq 0 ]; then if [ `expr $year % 400` -eq 0 ]; then day=`expr $day + 29` elif [ `expr $year % 100` -eq 0 ]; then day=`expr $day + 28` else day=`expr $day + 29` fi else day=`expr $day + 28` fi ;; esac done # Print the month day and year. 76 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

85 #echo $month $day $year DAY_S=$day-$month-$year DAY_E=$day-$month-$year #echo $DAYS #echo $DAYE #Uncomment the next two lines to force a date #DAYS=" " #DAYE=" " echo `date` ### Run summaries # Motorola BSS Summaries /appl/virtuo/bin/summary_admin -r BSC_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r Cell_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r Ethernet_link_mo_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r Gb_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r LAPD_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r PCU_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r Processor_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r Signalling_Link_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r X25_DA -ir daily -fr $DAY_S -er $DAY_E # Huawei BSS Summaries /appl/virtuo/bin/summary_admin -r BSC_DA_Huawei -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r M3UA_link_utilisation_DA -ir daily -fr $DAY_S -er $DAY_E /appl/virtuo/bin/summary_admin -r SCTP_Link_DA -ir daily -fr $DAY_S -er $DAY_E DB_USERNAME=`$WMCROOT/bin/conf_read dbconnection vtdb grep \.user= sed -e 's/.*=//g'` export DB_USERNAME ORACLE_SID=`$WMCROOT/bin/conf_read dbconnection vtdb grep \.sid= sed -e 's/.*=//g'` export ORACLE_SID DB_PASSWORD=`$WMCROOT/bin/conf_read dbconnection vtdb grep \.password= sed -e 's/.*=//g'` export DB_PASSWORD Note: You do not have to run the summary_admin part from the script if you do not need daily summaries. You can comment this part from the script. Generating data availability reports Generates the seven data availability reports based on the data availability model that is created. Procedure 1. In WirelessModelling tool, open the tnpmmodel file that you have created from the data availability model. 2. Right-click TNPM Package, and then select Data Coverage Utilities > Generate Data Availability Reporting. 3. On the Client details page, specify the following information: Option Description Database Host The Tivoli Netcool Performance Manager - Wireless Component database server host name or IP address. Database username Database User(virtuo) Password Cognos Dispatcher URI Username Password By default, virtuo. The virtuo user password. This is the Jazz for Service Management server URI. This URI must be the same as the Gateway URI that you have set in Framework Manager configuration from Chapter 4, Installing and configuring IBM Cognos Framework Manager, on page 13. Jazz for Service Management server username. By default smadmin The smadmin password. Chapter 9. Data availability reporting 77

86 Option Namespace Report Output Dir Description By default, VMMProvider. Location where the generated reports are available. For example, C:/DA_reports/tmp. 4. Click Get Model Details. 5. Click Next. 6. On the Model details page, specify the following information: Option Data Availability Summary Model Focal Entity Parent Entity Description Data Availability model that you have created. For example, NOKIA_GSM_FAbis_BSC.DA. Provisioned entities to be selected from the list. This entity is the main entity from which we want to view metrics. Parent entity for the selected focal entity. 7. Click Generate Reports. After the data availability reports are generated in the Report Output Directory. The location is as follows: C:/DA_reports/tmp/NOKIA_GSM_FAbis_BSC.DA. These reports are a set of seven XML files. For NOKIA_GSM_FAbis_BSC.DA model with BSC and Abis as selected parent and focal entities, the seven reports are as follows: v v v v v v v NOKIA_GSM_FAbis_BSC_20Worst_DDA NOKIA_GSM_FAbis_BSC_DDA NOKIA_GSM_FAbis_BSC_HDA NOKIA_GSM_FAbis_BSC_TABLE_DDA NOKIA_GSM_FAbis_BSC_TABLE_HDA NOKIA_GSM_FAbis_BSC2_DDA NOKIA_GSM_PBSC_Abis_DDA Note: The format of the XML file is as follows: <Vendor>_<Technology>_<P/F><entity_name>_<H/D>DA Where: P is parent entity, F is focal entity H is hourly, D is daily 78 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

87 Publishing the generated data availability reports Publish the data availability reports to Jazz for Service Management content store. Procedure 1. Start WirelessModelling tool. 2. Right-click TNPM Package, and then select Data Coverage Utilities > Publish Data Availability Reports from a Directory. Publishes all the data availability reports that are available in the C:/DA_reports/tmp/<Pack_DA_Model> directory. 3. Optional: Right-click TNPM Package, and then select Data Coverage Utilities > Publish Data Availability Report. Note: You must select this option only if you do not want to publish all data availability report from the directory. You can select the report that you want to publish from the default C:/DA_reports/tmp/<Pack_DA_Model> directory. 4. Enter the name of the folder for the report to be published. 5. Click Finish. Verifying the data availability report contents View the published data availability reports from Jazz for Service Management. Procedure 1. Log in to Jazz for Service Management as the administration user, smadmin. 2. Expand Reporting and select the Common Reporting tab. 3. Click Public Folders > Data Availability > Contents > <FAbis_PBSC_DA_Reports>. You can see the seven data availability reports that are published. 4. Double-click the report to view. Note: It is recommended that you drill down to the daily and hourly reports from the parent daily report or drill down to the table hourly report from the table daily report. Creating data availability summary report This is a one-time task. About this task For more information about this task, see Creating the TCR Data Availability Summary Report. Chapter 9. Data availability reporting 79

88 80 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide

89 Chapter 10. Troubleshooting Tivoli Netcool Performance Manager - Application Studio and Common reporting When you encounter a problem with using Tivoli Netcool Performance Manager - Application Studio components, the first thing to do is to check the detailed log files for that component. Most issues can be solved by referring to the log files. Read the following known issues if you are experiencing problems with Common Reporting on Tivoli Netcool Performance Manager. Data values that are displayed in the report do not match with the columns in the database This issue is due to certain lapses in creating reports. When you create a report, follow the best practices that are described in Application Studio 1.4 (Wireless Modelling) - Common Reporting. Restrict the number of KPIs used in creating a report from a Tivoli Netcool Performance Manager common pack data model Symptoms When you create a report from a model that has many key performance indicators (KPIs), the report might not show all the KPIs that are selected from a single table. You might see the following error message: ORA-01792: maximum number of columns in a table or view is 1000 Causes This is an Oracle limitation. An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view, which pushes it over the maximum allowable limit of The unused columns in the table are also counted toward the 1000-column limit. Resolving the problem To avoid this issue, plan and create a report with only those KPIs that are needed. Rather than using all the KPIs from a table. Reporting fails with sort key too long error from a busy hour data model This issue occurs when you are creating a report from the busy hour data models. Symptoms When you are generating a report from a data model that has too many KPIs, you might see the following error message: ORA-01467: sort key too long Causes A DISTINCT, GROUP BY, ORDER BY, or SET operations require a sort key longer than that supported by Oracle. Either too many columns or too many group functions are specified in the SELECT statement that is used to pull the KPIs from a Stored Busy Hour definition of a data model. Copyright IBM Corp. 2015,

90 Resolving the problem To avoid this issue, plan and create a report with only the required KPIs alone and not use all the KPIs for creating the report. Manually edit the summary name in a data availability model if the summary name exceeds 24 characters An error when you generate the data availability model. Symptoms When you generate the data availability components, you might receive an error message: Causes You receive this error message when the summary name is longer than 24 characters. Resolving the problem Manually edit the summary name in the generated da_summary.xml file to reduce the number of characters to less than 24. For example, the name appears as follows: DA_HUAWEI_GSM_M3UA_LINKSET. When you edit the name, make sure that you do not remove the DA_<Vendor>_<Technology> part from the name. For example, do not remove or change DA_HUAWEI_GSM. For more information, see Generating data availability components on page 70. Issues with rehomed data in the parent entity level in Data Availability Reports Symptoms 82 Tivoli Netcool Performance Manager - Application Studio Installation and User Guide