IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E2. Model Maker Installation and User Guide

Størrelse: px
Begynne med side:

Download "IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E2. Model Maker Installation and User Guide"

Transkript

1 IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E2 Model Maker Installation and User Guide

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

3 Contents About this information vii Intended audience vii Service Management Connect vii Tivoli Netcool Performance Manager technical training vii Support information vii Conventions used in this publication..... viii Typeface conventions viii Chapter 1. Introduction Model Maker components Enhancements in Model Maker, Version (Wireless only in this release) Organization Planning for your data requirements Chapter 2. Software requirements and prerequisite software Supported Tivoli Netcool Performance Manager configurations Prerequisites for installing the Common Pack Service on the server Required user names Prerequisites for installing Model Maker tools on the Microsoft Windows computer Chapter 3. Installing and configuring the Common Pack Service Configuring the prerequisite software on the server 11 Configuring Tivoli Common Reporting for Oracle connections Configuring the Tivoli Common Reporting data source Adding Oracle sessions settings Creating the required table spaces on the wireline database Configuring the prerequisite software on the Windows computer Configuring Framework Manager connections.. 16 Verifying the Java version and PATH Preinstallation tasks Transferring installation files by using the FTP protocol Changing permissions on the executable file.. 17 Creating the bicontrol user Running the installer The logins file Verifying the Common Pack Service installation.. 26 Troubleshooting the installation Uninstalling the Common Pack Service Uninstalling Resource Metric Viewer UI components Running the uninstaller Chapter 4. Installing and configuring Model Maker Manager Installing Model Maker Manager Configuring Model Maker Manager Opening Model Maker Manager Configuring the Common Pack Service preferences Configuring the wireless database preferences.. 32 Configuring the wireline database preferences.. 33 Configuring automatic updates and notifications 34 Configuring the software update site Configuring the Cognos preferences Chapter 5. The Base Common Pack Suite Installing a Base Common Pack Adding a base common pack to the repository.. 38 Adding multiple base common packs to the repository Adding base common packs by using the CLI.. 39 Activating base common packs in the repository.. 39 Activating base common packs by using the CLI 40 Populating the calendar schema table for TCR Time 40 Adding the calendar indexes Chapter 6. Installing and configuring Model Maker Extractor (Wireless only). 43 Installing Model Maker Extractor Configuring Model Maker Extractor Opening Model Maker Extractor Configuring the JDBC driver Chapter 7. Upgrading Model Maker.. 45 Chapter 8. Creating common packs (Wireless only) Overview of creating common packs for Wireless pack modelers Identifying the appropriate dependent packs Data model filtering Creating a common pack containing a raw data model Creating a common pack containing a summary definitions model Creating a common pack containing a busy hour definitions model Filtering metrics from a model in an existing CIF file Identifying metric groups for a filter file Filtering intervals from existing CIF files Filtering an existing summary model Filtering an existing busy hour model Copyright IBM Corp. 2011, 2014 iii

4 Chapter 9. Updating and extending common packs (Wireless only) Updating common packs Creating a new version of a common pack Considerations when modifying models Decomposing composite common packs for addition to the repository Downloading common packs Combining multiple common packs Combining common pack models Adding reports to a common pack Chapter 10. Installing common packs 63 Overview of installing common packs for pack administrators Wireless Component only: Populating the database schema tables Listing common packs in the repository Adding multiple CIF (.tnpmmodel) files to deploy 65 Deploying a common pack (Wireless only) Uninstalling common packs Removing common packs from the repository.. 69 Chapter 11. Resource Metric Viewer (Wireless only) Resource Metric Viewer setup List packs Active Event List Using the Resource Metric Viewer Constructing a report by selecting a subset of resources and metrics Constructing a report by selecting an event in the Active Event List Resource Metric Viewer administration Modify the Resource Metric Viewer template.. 78 Chapter 12. Data availability reporting 81 Overview of generating data availability reports.. 81 Monitoring the key traffic tables for data availability 82 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. 89 Extracting and deploying daily summary model 90 Downloading the data availability model Scheduling and running summaries Generating data availability reports Publishing the generated data availability reports. 95 Verifying the data availability report contents Creating data availability summary report Chapter 13. Troubleshooting Model Maker and Common Reporting Data modeling and Model Maker issues Error while uninstalling Common Pack Service 99 Always use the HTTP protocol for the update site Slow download of common packs CTGTRR1104E Cannot open an administrative database connection Updating earlier pre-ga common packs Resolving Cognos connection errors Resolving Cognos connection errors on Windows 7 environment Supporting help buttons in Model Maker Extractor HTML pack documentation is slow to open in Internet Explorer (Wireless) Combining models might hang on "Creating new Framework Manager project" (Wireless) Missing formulae in metrics groups after generating the CIF file (Wireless) Do not use special characters in the model name when creating Summary and Busy Hour models (Wireline) Issue when extending a model by using the pm.inventory.getresources DAL query 105 Label alarms that may not be handled properly by the Resource Metric Viewer When you deploy a common pack on Tivoli Integrated Portal, the common pack is not installed The WIRELESS_HOST parameter does not reflect correctly in the global.properties file SQL query string length for monitoring the tables for hourly data availability must be limited to 4000 characters Use either deploy or publish method for both raw and summary models for data availability report generation Issues when you have multiple technology pack data availability models deployed on the server. 110 Manually edit the summary name in a data availability model if the summary name exceeds 24 characters Rollup report cannot be generated if there is missing information for the entities in the hierarchy selection Unlock the bicontrol user manually Reporting issues Intermittent problems logging on to Tivoli Common Reporting Logging in when your session times out Problems running reports if you have logged in to multiple sessions Page number is not shown at the bottom of a HTML report Problems with Report Studio in Internet Explorer Customizing reports in Report Studio using Internet Explorer Cannot resize the Common Reporting window in Internet Explorer Infinitely expanding resources in the Report Studio hierarchy iv IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

5 CSV export is not supported for reports containing multiple tables The CSV file extension is.xls instead of.csv Common Reporting page resets when you select another task Limitations on formatting charts in Microsoft Excel Unreadable text error message in Excel Delays when running scheduled reports Data from wireless and wireline databases in reports is not linked Null aggregation is not supported in Common Reporting PDS-PPE-0104 error message Errors while stopping and starting Tivoli Common Reporting on a Linux server (Wireless) Null aggregation is not supported in Common Reporting - Wireless implications (Wireless) KPIs that are stored in IP format in the database are displayed incorrectly in reports. 118 (Wireline) PRS-CSE-1258 error message (Wireline) Report titles and labels are displayed in ASCII format (Wireline) Differentiating duplicate resources with the same resourcealias (Wireline) Table cells with no data are blank (Wireline) Modifying timestamps in custom charts to round up to minutes instead of milliseconds (Wireline) Raw data is not returned for a KPI when all resources for a non-leaf group are selected (Wireline) Bar graph in microchart does not follow the sequence of KPIs in the summary table, as per the graph in HTML or PDF format. 121 (Wireline) Exporting a PDF returns an error when the report has no data charts Appendix A. Configuring communications between the Common Pack Service and the Common Pack Service Client Configuring nonsecure communications Configuring secure communication with the trusting option Configuring secure communication with the strict option Exporting the Tivoli Common Reporting digital certificate Importing the digital certificate to the client runtime truststore Appendix B. Command reference The pack_admin command The password file pack_admin -activate pack_admin -add pack_admin -execute pack_admin -list pack_admin -passwordfile pack_admin -remove pack_admin -reset pack_admin -set pack_admin -rmv pack_admin -deploy Appendix C. Installing the Resource Metric Viewer as a separate installation Appendix D. Overriding Common Pack Service installer options Enabling reduced data model for a common pack containing raw data Enabling inner join Enabling counter ID instead of counter name in loadmap expressions Appendix E. Creating a logins file with the appropriate passwords Notices Glossary Index Contents v

6 vi IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

7 About this information Intended audience The Installing and Using Model Maker describes how to install Model Maker on a IBM Tivoli Netcool Performance Manager system. This information is intended for: v Users who want to install and administer common packs on a Tivoli Netcool Performance Manager system. Common packs enable Common Reporting for Tivoli Netcool Performance Manager. v Modelers who want to create and deploy 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 IBM Tivoli Common Reporting 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. 2011, 2014 vii

8 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 v v v v v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text 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:) Keywords and parameters in text Citations (examples: titles of publications, diskettes, and CDs) 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... Monospace 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 Bold monospace v Command names, and names of macros and utilities that you can type as commands viii IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

9 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 ix

10 x IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

11 Chapter 1. Introduction Model Maker components Common packs extend technology pack data models and Summary and Busy Hour data models to Tivoli Common Reporting on Tivoli Netcool Performance Manager. After you install a technology pack, you install the corresponding common pack to enable Tivoli Common Reporting. Common packs can be delivered in the COTS program with the corresponding technology packs, or created and customized by customers and IBM Business Partners. Model Maker consists of the following features and capabilities: Consistent model generation Model Maker automates the creation of wireless data models, and their inclusion in common packs. These models that are generated by using Model Maker are consistent and less error prone. Many Key Performance Indicators (KPIs) can be mapped automatically. Note: Wireline data models are manually created, and then packaged in common packs by using Model Maker Manager. Simplified model management Model Maker takes care of pack management, automatic merging of models and deploy the models and reports on Tivoli Integrated Portal. Consistent look and feel All generated common packs use the same Base Common Packs. The TCR Time Base Common Pack (BCP) provides a common time dimension for reporting. Components of Model Maker Model Maker consists of the following components: v Model Maker Manager. v Model Maker Extractor (supports wireless only in this release). v The Common Pack Service. v The Base Common Pack Suite. The latest Base Common Pack Suite ( TIV-TNPM-BCPSUITE ) is available as a separate download from Passport Advantage. v A set of Wireless CIF files. The Common Pack Service A mandatory server-side component that is installed on the Tivoli Common Reporting server and provides a host service for managing common packs for Common Reporting function on the Tivoli Netcool Performance Manager system. You can install and manage common packs by using the Model Maker Manager GUI on a Windows computer, and the Common Pack Service CLI on the Tivoli Common Reporting Server. Copyright IBM Corp. 2011,

12 You can download common packs from the Common Pack Service to a Windows computer for modification or for deploying to the Tivoli Common Reporting Content Store. Model Maker Manager A mandatory common pack administrator and modeler tool, Model Maker Manager is an Eclipse-based Client GUI for the Common Pack Service. You use Model Maker Manager to perform the following tasks: v v Install and manage wireless and wireline common packs on Tivoli Netcool Performance Manager systems. Create and deploy wireless common pack report packages to the Tivoli Common Reporting Content Store for report authoring. Note: Currently, the deploy function in Model Maker Manager supports only the wireless common packs and not the wireline common packs. v Create common packs from the wireless common pack contents that are generated by Model Maker Extractor. v Combine common pack data models and extend common packs. Model Maker Extractor (Wireless only in this release) An optional common pack modeler tool that is required if you must create your own Tivoli Netcool Performance Manager common packs. Common pack modelers can use Model Maker Extractor 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 that is extracted is converted into a Common Intermediate Format (CIF) file (.tnpmmodel) for later processing into a data model. Wireless CIF files A set of Common Intermediate Format (CIF) files are the dependent common packs that are packaged with Model Maker. These CIF files are required to process each of the supported Wireless GOM and GOMlet base common packs that are provided with each release. The Base Common Pack Suite The Base Common Pack Suite is a set of Base Common Packs (BCPs). Base Common Packs (BCPs) are common packs that can be used as building blocks for other Tivoli Netcool Performance Manager common packs. BCPs typically contain items such as time dimensions from the TCR Time Base Common Pack, or network resources that are related to specific technologies. v The TCR Time BCP is a dependent pack for all common packs, both for the Tivoli Netcool Performance Manager Wireless and Wireline Components. v The Wireline Common BCP is a dependent pack for all wireline common packs. v Typically, a number of Wireless BCPs are dependent packs for a wireless common pack. Wireless BCPs support a number of Global Object Model (GOM) and GOMlet Technology Packs. Refer to individual wireless common pack release notes to see the list of dependent packs for a particular pack. 2 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

13 Enhancements in Model Maker, Version (Wireless only in this release) Enhancements to Model Maker, Version Model Maker, Version has the following enhancements: Improved performance after the option USE_LOADMAP_IN_COUNTER_NAME property is enabled For more information, see Enabling counter ID instead of counter name in loadmap expressions on page 145. Improved performance in the Model Maker Extractor when you import summaries The default selection for all summaries is disabled so that you can select your preference by raw, hourly, daily, weekly, or monthly intervals there by reducing the time that is taken for import. Resolved the inconsistencies in summary table names in some Cognos models You can notice the distinct summary and pcal table names in the Cognos model that is opened in the Framework Manager as shown in the following figure: Chapter 1. Introduction 3

14 To avoid this problem in your customized summary, append #_ to display as PCals and to display as Extra Aggr to the summary table names before provisioning. Performance improvement in Resource Metric Viewer The Resource Metric Viewer reports are faster and the selected entries are filled in faster. 4 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

15 Organization Read this summary information to help you find the information that you need. v Chapter 1, Introduction, on page 1 For all users, this chapter describes the Model Maker tooling and how to use this information. v Chapter 2, Software requirements and prerequisite software, on page 7 For all users, this chapter describes the Model Maker software requirements and prerequisite software. v Chapter 3, Installing and configuring the Common Pack Service, on page 11 For all users, this chapter describes how to install and configure the Common Pack Service on the Tivoli Common Reporting server. v Chapter 4, Installing and configuring Model Maker Manager, on page 31 For all users, this chapter describes how to install and configure Model Maker Manager on a Windows computer. v Chapter 5, The Base Common Pack Suite, on page 37 For all users, this chapter describes the Base Common Packs and how to install the Base Common Packs. v Chapter 6, Installing and configuring Model Maker Extractor (Wireless only), on page 43 For wireless users only, this chapter describes how to install and configure Model Maker Extractor on a Windows computer. v Chapter 7, Upgrading Model Maker, on page 45 For all users, this chapter describes upgrade consideration for Model Maker components. v Chapter 8, Creating common packs (Wireless only), on page 47 For wireless users only, this chapter describes how to create a common pack containing Cognos data models. v Chapter 9, Updating and extending common packs (Wireless only), on page 57 For wireless users only, this chapter describes how to update and extend common packs. v Chapter 10, Installing common packs, on page 63 For all users, this chapter describes how to install a common pack on a Tivoli Netcool Performance Manager wireline or wireless system. v Chapter 11, Resource Metric Viewer (Wireless only), on page 71 For all users, this chapter describes how to dynamically create reports by using the Resource Metric Viewer. v Enabling reduced data model for a common pack containing raw data on page 143 For all users, this chapter describes how to enable reduced data model for a common pack. v Chapter 12, Data availability reporting, on page 81 For all users, this chapter describes how to create data availability reports from a data availability model. v Enabling inner join on page 144 For all users, this chapter describes how to enable inner join for performance enhancement on reports. v Enabling counter ID instead of counter name in loadmap expressions on page 145 Chapter 1. Introduction 5

16 v For all users, this chapter describes how to enable the loadmap counter ID in expressions and improvements there by. Chapter 13, Troubleshooting Model Maker and Common Reporting, on page 99 For all users, this chapter describes known issues that you might encounter when using Model Maker Edition. v Appendix A, Configuring communications between the Common Pack Service and the Common Pack Service Client, on page 123 For all users, this chapter provides information about how to configure communications between the Common Pack Service and the Common Pack Service Client. v Appendix B, Command reference, on page 129 For all users, this chapter provides a command reference for Model Maker commands. v Appendix C, Installing the Resource Metric Viewer as a separate installation, on page 141 For wireless users, this chapter provides information about how to install the Resource Metric Viewer separately and not as a part of running the installer. v Glossary on page 153 For all users, this chapter includes Model Maker terms and definitions. Planning for your data requirements Before installing the Common Pack Service, you must decide if you need to access wireless data, wireline data, or both wireless and wireline data. The installation steps are different depending on which of the following installation options you chose: Wireless data For wireless data, you use the wireless database. You modify the tnsnames.ora file as directed when configuring Tivoli Common Reporting for Oracle connections. Then you install the Common Pack Service on the Tivoli Common Reporting server in your wireless installation. Point to the wireless database when prompted for a database during installation. Wireline data For wireline data, you use the wireline database. You create the required table spaces on the wireline database. Then you install the Common Pack Service on the Tivoli Common Reporting server (DataView server) in your wireline installation. Point to the wireline database when prompted for a database during installation. Wireless and wireline data For both wireless and wireline data, you use the wireless database. You modify the tnsnames.ora file as directed when configuring Tivoli Common Reporting for Oracle connections. Then you install the Common Pack Service on the Tivoli Common Reporting server (DataView server) in your wireline installation. Point to the wireless database when prompted for a database during installation. 6 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

17 Chapter 2. Software requirements and prerequisite software Ensure that your system meets the minimum software requirements and that all prerequisite software is installed and configured before starting the installation. Supported Tivoli Netcool Performance Manager configurations Ensure that you have one of the following Tivoli Netcool Performance Manager configurations with the correct patch levels before starting the installation. Table 1. Supported Tivoli Netcool Performance Manager environments Tivoli Netcool Performance Manager version Supported Tivoli Integrated Portal versions Wireless Component Tivoli Integrated Portal 2.2 or Wireline Component Tivoli Integrated Portal 2.2 or Wireline Component Tivoli Integrated Portal 2.2 or 2.1 and Wireless Component Prerequisites for installing the Common Pack Service on the server Ensure that the system is ready and you have all the required information before starting the Common Pack Service installation on the Tivoli Common Reporting server. The Oracle client version and above must be installed and running on the Tivoli Common Reporting server where you want to install the Common Pack Service. The Tivoli Common Reporting server must be running before you start the installation. Ensure that you have the following information before starting the installation: v The login details of the Tivoli Common Reporting installation user. You must install the Common Pack Service as the same user that installed Tivoli Common Reporting, typically the root user. v The connection details for the appropriate Tivoli Netcool Performance Manager database. Copyright IBM Corp. 2011,

18 Required user names The common pack service installation creates a number of required users with the appropriate permissions. Database users The common pack service installation creates a number of required database users with the appropriate permissions. The following database users are created during the installation: v tcraccess v bicontrol v birefresh Prerequisites for installing Model Maker tools on the Microsoft Windows computer Ensure that you fulfill these prerequisites before installing and configuring Model Maker on a Microsoft Windows computer. The Common Pack Service must be installed and running on the Tivoli Common Reporting server before you start the installation. Microsoft Windows computer hardware A minimum of 4 GB RAM with a 2 GHz processor. Microsoft Windows operating system Model Maker Manager must be installed on a Microsoft Windows computer. Model Maker Manager is tested on 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: Note: The previous version of Framework Manager (TCR13-win ) provided with Tivoli Common Reporting 1.3 is not supported. Ensure that you install the version of Framework Manager (TCR21-win ) provided with Tivoli Common Reporting 2.1. To identify which version is installed, look in the Help > About IBM Cognos 8 Framework Manager option in Framework Manager. The unsupported version TCR13-win shows version IBM Cognos Framework Manager , while the supported version TCR21-win shows IBM Cognos Framework Manager v IBM Tivoli Common Reporting V2.1 Windows Multilingual (CZQ7ZML). If you have installed the Windows version of Tivoli Common Reporting Version 2.1, the files are already available in the installation directories. v Cognos Framework Manager for IBM Tivoli Common Reporting Version 2.1 Window Multilingual (CZUR5ML). To install Framework Manager, you must first install Framework Manager from the CognosModeling directory, and then install the security patch from the CognosModelingFix directory. 8 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

19 For more information, see the Tivoli Common Reporting documentation at com.ibm.tivoli.tcr.doc_21/ttcr_installing_fm.html. 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. Java Runtime Environment You can use the correct JRE that is bundled with the Model Maker Manager component. For Model Maker Extractor, you must ensure that Java 1.6 is installed on the PC. Chapter 2. Software requirements and prerequisite software 9

20 10 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

21 Chapter 3. Installing and configuring the Common Pack Service Complete the following tasks to install and configure the Common Pack Service. Before you begin If you have an existing version of Resource Metric Viewer on your system, you must uninstall the Resource Metric Viewer UI component before installing a new version of the Common Pack Service. For more information on uninstalling the Resource Metric Viewer UI component, see Uninstalling Resource Metric Viewer UI components on page 28. Configuring the prerequisite software on the server Ensure that all necessary configuration steps are completed for the prerequisite software on the server. Configuring Tivoli Common Reporting for Oracle connections You must configure Tivoli Common Reporting for Oracle database connections by exporting the TNS_ADMIN environment variable. Depending on your configuration, you might also have to add tcraccess details to the tnsnames.ora file. Before you begin Check if the $ORACLE_HOME/network/admin/sqlnet.ora file on the Tivoli Common Reporting server contains the NAMES.DEFAULT_DOMAIN=WORLD entry. If so, in the following procedure, you must append.world to the tcraccess entry in the tnsnames.ora file, giving tcraccess.world =. About this task The configuration steps are different depending on what data you need to access; wireless data, wireline data, or wireless and wireline data. For more information, see Planning for your data requirements on page 6. Procedure 1. Log on to the Tivoli Common Reporting server. 2. Wireless data only: Complete this step if you need wireless data only and are installing in a Tivoli Netcool Performance Manager Wireless Component environment. Edit the $<ORACLE_HOME>/network/admin/tnsnames.ora file as oracle user. Where <ORACLE_HOME> is/appl/oracle/product/11.2.0/db_1. a. Add the following lines to the file. tcraccess = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = TNPM_WIRELESS_DATABASE_HOST)(PORT = 1521)) ) Copyright IBM Corp. 2011,

22 (CONNECT_DATA = (SERVICE_NAME = vtdb) ) ) Where TNPM_WIRELESS_DATABASE_HOST is the Tivoli Netcool Performance Manager - Wireless Component database server host name or IP address. Important: The connection name must be tcraccess. b. Save the tnsnames.ora file. 3. Wireline data only: Complete this step if you need wireline data only and are installing in a Tivoli Netcool Performance Manager Wireline Component environment. By default, the Oracle connection for wireline is configured after installing Tivoli Netcool Performance Manager and the Oracle Database. You do not need to create an Oracle connection for tcraccess as you can use the existing Oracle client configuration. a. Check that the following lines are in the tnsnames.ora file. PV.WORLD = (DESCRIPTION = (ENABLE=BROKEN) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = TNPM_WIRELINE_DATABASE_HOST) (PORT = 1521) ) ) (CONNECT_DATA = (SERVICE_NAME = PV.WORLD) (INSTANCE_NAME = PV) ) ) Where TNPM_WIRELINE_DATABASE_HOST is the Tivoli Netcool Performance Manager - Wireless Component database server host name or IP address. 4. Both Wireless and Wireline data: Complete this step if you need both wireless and wireline data and are installing in an environment containing both the Tivoli Netcool Performance Manager Wireless and Wireline Components. Edit the tnsnames.ora file on each component and add the following lines to the file: a. On the wireline server where Tivoli Common Reporting is installed. VTDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = TNPM_WIRELESS_DATABASE_HOST)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = vtdb) ) ) Where TNPM_WIRELESS_DATABASE_HOST is the Tivoli Netcool Performance Manager - Wireless Component database server host name or IP address. b. On the wireless database server. tcraccess = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = TNPM_WIRELESS_DATABASE_HOST)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = vtdb) ) ) 12 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

23 Where TNPM_WIRELESS_DATABASE_HOST is the Tivoli Netcool Performance Manager - Wireless Component database server host name or IP address. 5. After updating the tnsnames.ora file, go to the $ORACLE_HOME/bin directory and run the tnsping command to check for a successful database connection. According to your configuration, enter the appropriate command: v Wireless data only: #./tnsping tcraccess v Wireline data only: #./tnsping pv.world v Both Wireless and Wireline data: #./tnsping vtdb #./tnsping tcraccess TNS Ping Utility for Linux: Version Production on 01-JUN :26:50 Copyright (c) 1997, 2007, Oracle. All rights reserved. Used parameter files: /appl/oracle/product/11.2.0/network/admin/sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = vtdb))) OK (0 msec) An OK message at the end shows that the connection is working. 6. Edit the starttcrserver.sh script as root user. For example, by using the vi editor, enter: $vi TIP_COMPONENTS_LOCATION/TCRComponent/bin/startTCRserver.sh Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components were installed. By default, /opt/ibm/tivoli/ tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. 7. Add the following lines to the start of the script, depending on the server operating system. Note: The LIBPATH and LD_LIBRARY_PATH values depend on your Oracle installation and the values shown reflect those of a default Oracle installation. ORACLE_HOME=ORACLE_HOME export ORACLE_HOME TNS_ADMIN="$ORACLE_HOME/network/admin/tnsnames.ora" export TNS_ADMIN LIBPATH=$ORACLE_HOME/lib32:$LIBPATH export LIBPATH ORACLE_HOME=ORACLE_HOME export ORACLE_HOME TNS_ADMIN="$ORACLE_HOME/network/admin/tnsnames.ora" export TNS_ADMIN LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$LD_LIBRARY_PATH export LD_LIBRARY_PATH Chapter 3. Installing and configuring the Common Pack Service 13

24 ORACLE_HOME=ORACLE_HOME export ORACLE_HOME TNS_ADMIN="$ORACLE_HOME/network/admin/tnsnames.ora" export TNS_ADMIN LD_LIBRARY_PATH=$ORACLE_HOME/lib32:$LD_LIBRARY_PATH export LD_LIBRARY_PATH Where ORACLE_HOME is the location where the Oracle client is installed. For example, the path is /appl/oracle/product/11.2.0/db_1 for Oracle 11g if you are installing on Tivoli Netcool Performance Manager Wireless For example, the path is /opt/oracle/product/ client32/ for Oracle 11g if you are installing on Tivoli Netcool Performance Manager Wireline Note: When installing on Tivoli Netcool Performance Manager Wireline the LD_LIBRARY_PATH= will refer to $ORACLE_HOME/lib and not $ORACLE_HOME/lib32 as it does for wireless. 8. Restart the Tivoli Common Reporting server: a. Stop the server by entering the following command on one line: $TIP_COMPONENTS_LOCATION/TCRComponent/bin/stopTCRserver.sh tipadmin tipadmin_password b. Start the server by entering the following command on one line: $TIP_COMPONENTS_LOCATION/TCRComponent/bin/startTCRserver.sh tipadmin tipadmin_password Configuring the Tivoli Common Reporting data source You must configure a Tivoli Common Reporting data source connection to connect to an Oracle database that has Tivoli Netcool Performance Manager data. Procedure 1. Log in to Tivoli Integrated Portal as the Tivoli Integrated Portal administration user, tipadmin. For example: 2. Expand Reporting and select the Common Reporting tab. 3. Click Launch > Administration. 4. On the Configuration tab, add new data source by clicking the New Data Source button. 5. Follow the New Data Source wizard as required noting the following steps: a. Enter tcraccess in the name field and click Next. b. In the Type list, select Oracle and click Next. c. In the SQL*Net connect string field, enter PV for wireline data only, enter tcraccess for wireless data only, or enter tcraccess for wireless and wireline data. d. In the Signon section, select the User ID, Password, and Create a signon that the Everyone group can use check boxes. e. Enter tcraccess/tcraccess for the user ID and password, and then click Finish. f. Test the new data source after the Common Pack Service is installed. 14 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

25 Adding Oracle sessions settings Complete the following steps in the appropriate Tivoli Integrated Portal instance for your system. About this task For more information about open session command blocks, see com.ibm.swg.im.cognos.ug_cra doc/ug_cra_i_commandblockexamples.html Procedure 1. Log in to Tivoli Integrated Portal as the Tivoli Integrated Portal administration user, tipadmin. 2. Expand Reporting and select the Common Reporting tab. 3. Click Launch > Administration. 4. Select the Configuration tab and then Data Source Connections. 5. Find tcraccess in the list and click it. It drills down to yet another tcraccess. Click the tcraccess again, which displays another tcraccess. 6. Click the Set properties - tcraccess button ( ) on the upper right. 7. In the Set properties page, click the Connection tab. 8. Find and expand Open session commands in the list and click the Set parameter button (). 9. Enter the following SQL: <commandblock> <commands> <sqlcommand> <sql> ALTER SESSION SET "_optimizer_native_full_outer_join"=force</sql> </sqlcommand> <sqlcommand> <sql> alter session set star_transformation_enabled=true</sql> </sqlcommand> </commands> </commandblock> 10. Click OK. IntheConnection tab, click OK. Creating the required table spaces on the wireline database If you are using the wireline database, you must create the wm_flexpm and temp table spaces on the wireline database. This task is only required if you are planning to use the wireline database when installing the Common Pack Service. Procedure 1. Log in to the server as the oracle user. 2. Log on as the oracle user without connecting to the database by entering the following command: sqlplus /nolog 3. Connect to the wireline database as the sysdba user by entering the following command: sqlplus "/ as sysdba" Where password is the appropriate password. Chapter 3. Installing and configuring the Common Pack Service 15

26 4. Create the wm_flexpm table space by entering the following command on one line: CREATE TABLESPACE wm_flexpm DATAFILE /raid_3/oradata/pv/wm_flexpm.dbf SIZE 200M AUTOEXTEND ON MAXSIZE UNLIMITED; where /raid_3/oradata/ is a mount point for Oracle data. 5. Create the temp table space by entering the following command on one line: CREATE TEMPORARY TABLESPACE temp TEMPFILE /raid_3/oradata/pv/temp.dbf SIZE 50M AUTOEXTEND ON MAXSIZE UNLIMITED; Configuring the prerequisite software on the Windows computer Wireline users who intend to create their own Cognos models and common packs must ensure that all necessary configuration steps are completed on the prerequisite software. These steps do not apply to Wireline administrators who only require Model Maker Manager to install and manage packs. Configuring 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 deploy your content. If you want to deploy content to another server, you must change these settings to point to the new server. For information about configuring Framework Manager connections, see com.ibm.tivoli.tcr.doc_21/ttcr_configure_frameworkmgr.html. Configure Framework Manager Oracle connection To configure the Framework Manager Oracle connection: v Add Oracle to your Windows path. For example, C:\oracle\product\11.2.0\ client_1\bin. v Wireless users must add tcraccess to the tnsnames.ora file. Edit the tnsnames.ora file and add the following lines to the file: tcraccess = (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. 16 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

27 Verifying the Java version and PATH Model Maker Extractor requires that the correct version of Java is included in the PATH on your Windows PC. v v Preinstallation tasks Ensure that you have Java 1.6 or later. Ensure that Java 1.6 is present on the PATH of your Windows computer. Perform the following preinstallation tasks before installing the software. Transferring installation files by using the FTP protocol If you are transferring the Common Pack Service installation files from the Model Maker package to the Tivoli Common Reporting Server by using the FTP protocol, transfer the files in binary format to avoid errors during installation. Changing permissions on the executable file Change the permissions on the platform-specific executable file before running the installer. Procedure 1. Change to the directory containing the executable file. 2. Run the appropriate command for your operating system: chmod +x CommonPackServiceInstall-<version>_sol.sh chmod +x CommonPackServiceInstall-<version>_aix.sh chmod +x CommonPackServiceInstall-<version>_lin.sh Creating the bicontrol user The bicontrol user is a user that must be created in the target database. The bicontrol user is responsible for creating users and for assigning access to the various common packs. Before you begin You must have database administrator privileges to perform this task. About this task If the bicontrol user does not exist, a database administrator must create the bicontrol user on the target database before installing the Common Pack Service. The installer prompts for a JDBC connection string during installation; the bicontrol user is validated against this connection. The installer prompts for a JDBC URL twice during the installation, you can point to the same computer each time. Chapter 3. Installing and configuring the Common Pack Service 17

28 Procedure 1. To check if the bicontrol user exists, run the following SQL as the database administrator. SELECT * FROM all_users WHERE username = BICONTROL ; 2. If the bicontrol user is not present, run the following SQL as the database administrator. 18 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

29 CREATE USER bicontrol IDENTIFIED BY bicontrol 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, 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 bicontrol; Chapter 3. Installing and configuring the Common Pack Service 19

30 Running the installer Explains how to run the installer and select the appropriate installation options. Before you begin You must have decided what configuration you are going to install and completed the prerequisite tasks. For more information, see Planning for your data requirements on page 6. You cannot complete the installation without entering valid details at each of the prompts. Before you begin, read the procedure and ensure that you have all the required details. In particular, ensure that you have the login details of the Tivoli Common Reporting installation user, typically the root user. About this task The administrative database acts as a repository for the common packs. The target database is where the common pack contents are installed. You can use the same database for both. Procedure 1. Log in to the target server as the Tivoli Common Reporting installation user. 2. Go to the directory that has the platform-specific installation file. 3. Run the installer by entering the appropriate command for your operating system: v v v./commonpackserviceinstall-<version>_sol.sh./commonpackserviceinstall-<version>_aix.sh./commonpackserviceinstall-<version>_lin.sh The installer starts and the license agreement is displayed: 20 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

31 Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... Configuring the installer for this system s environment... Launching installer... =============================================================================== Common Pack Service (created with InstallAnywhere) Preparing CONSOLE Mode Installation... =============================================================================== End User License Agreement Part 1 - General Terms BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, CLICKING ON AN "ACCEPT" BUTTON, OR OTHERWISE USING THE PROGRAM, LICENSEE AGREES TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF LICENSEE, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND LICENSEE TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN "ACCEPT" BUTTON, OR USE THE PROGRAM; AND PROMPTLY RETURN THE UNUSED MEDIA, DOCUMENTATION, AND PROOF OF ENTITLEMENT TO THE PARTY FROM WHOM IT WAS OBTAINED FOR A REFUND OF THE AMOUNT PAID. IF THE PROGRAM WAS DOWNLOADED, DESTROY ALL COPIES OF THE PROGRAM. 4. Press Enter on each page of the agreement to continue and on the last page, enter "1" to accept. Press Enter to continue viewing the license agreement, or enter "1" to accept the agreement, "2" to decline it, "3" to print it, "4" to read non-ibm terms, or "99" to go back to the previous screen. 5. Enter the Tivoli Integrated Portal installation directory. By default, /opt/ibm/tivoli/tipv2 for wireless and /opt/ibm/tivoli/tip21 for wireline. 6. Enter a Tivoli Integrated Portal administrator user name. By default, tipadmin. 7. Enter a Tivoli Integrated Portal administrator user password. ----TIP Information---- TIP Installation Directory: /opt/ibm/tivoli/tipv2 TIP Administrator User Name (DEFAULT: tipadmin): TIP Administrator Password: ********* 8. Enter the directory where the Tivoli Integrated Portal components are installed. By default, /opt/ibm/tivoli/tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. TIP Components Installation Directory (DEFAULT: /opt/ibm/tivoli/tipv2components): Chapter 3. Installing and configuring the Common Pack Service 21

32 The Common Pack Service is installed at $TIP_COMPONENTS_LOCATION/ TCRComponent/commonpackservice. 9. Enter the directory where the Oracle client is installed. For example, /appl/oracle/product/11.2.0/db_1 for wireless and /opt/oracle/product/ client32/ for wireline. Note: For wireline, a softlink must be created for lib32 in /opt/oracle/product/ client32/lib directory. For example, in the default Oracle client directory /opt/oracle/product/ client32/lib, create a softlink to /opt/oracle/product/ client32/lib Database Connection---- Database Client Directory: /opt/oracle/product/11.2.0/db_1 10. 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. ----Database Connection---- Database Client Directory: /appl/oracle/product/11.2.0/db_1 Administrative Database JDBC URL ( jdbc:oracle:thin:@hostname:1521:vtdb ): For Oracle, the URL format is as follows: jdbc:oracle:thin:@hostname:port:sid For example: Wireless Component jdbc:oracle:thin:@server.ibm.com:1521:vtdb jdbc:oracle:thin:@ :1521:vtdb Wireline Component jdbc:oracle:thin:@server.ibm.com:1521:pv jdbc:oracle:thin:@ :1521:pv Wireless and Wireline Component jdbc:oracle:thin:@server.ibm.com:1521:vtdb jdbc:oracle:thin:@ :1521:vtdb 11. Enter the name of the administrative database user bicontrol. 12. Enter the password of the administrative database user bicontrol. For example, the password, bicontrol. ----Database Connection---- Database Client Directory: /opt/oracle/product/11.2.0/db_1 Administrative Database JDBC URL ( jdbc:oracle:thin:@hostname:1521:vtdb ): jdbc:oracle:thin:@server@ibm.com:1521:vtdb Administrative Database BICONTROL User Name (DEFAULT: bicontrol): bicontrol Administrative Database BICONTROL User Password: The installer attempts to connect to the database by using the URL, user name, and password. You must enter valid details or the installation cannot continue. 13. Enter the name of the administrative database objects table space. By default, wm_flexpm. 22 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

33 ----Database Connection---- Database Client Directory: /opt/oracle/product/11.2.0/db_1 Administrative Database JDBC URL ( jdbc:oracle:thin:@hostname:1521:vtdb ): jdbc:oracle:thin:@server.ibm.com:1521:vtdb Administrative Database BICONTROL User Name (DEFAULT: bicontrol): bicontrol Administrative Database BICONTROL User Password: Administrative Database Objects TableSpace Name (DEFAULT: wm_flexpm): 14. Enter "Y" to install the Resource Metric Viewer, otherwise enter "N". Resource Metric Viewer can be installed for the wireless component only. ----Resource Metric Viewer Installation---- Do you want to install the Resource Metric Viewer (Wireless Component only)(default: Y)? (Y/N): Y Note: If you do not want to install the Resource Metric Viewer at this stage, you can install later. For instructions on installing the Resource Metric Viewer as a separate installation, see Appendix C, Installing the Resource Metric Viewer as a separate installation, on page Enter "Y" to enable the reduced data model, otherwise enter "N". Reduced data model can be enabled for the wireless component only. ----Reduce Data Model---- Do you want to enable Reduce Data Model (Wireless Component only)(default: Y)? (Y/N): Y Note: If you enter N, you can enable this option later. For more information, see Enabling reduced data model for a common pack containing raw data on page Enter "Y" to use the loadmap expression in the counter name. ----Use Loadmap in Counter Name---- Do you want to use Loadmap Counter Name (Wireless Component only)(default: N)? (Y/N): Y If you enter "N", it results in a counter name as: FAIL_RES_ALLOC_DUE_TO_INS_BW. If you enter "Y", it results in a counter name as: C ( FAIL_RES_ALLOC_DUE_TO_INS_BW ). This is applicable for raw, summary, and busy hour packs. Note: If you enter N, you can enable this option later. For more information, see Enabling counter ID instead of counter name in loadmap expressions on page Enter "Y" to enable outer join or enter "N" to enable inner join. ----Time Dimension Outer Join---- Do you want to use Outer Join or Inner Join for time dimension (For Outer Join enter Y, For Inner Join enter N)(DEFAULT: N)? (Y/N): N Note: If you enter Y to enable outer join, you can enable the inner join option later. For more information, see Enabling inner join on page 144. On successful connection to the database, the Preinstallation Summary is displayed as follows assuming a wireless installation. Chapter 3. Installing and configuring the Common Pack Service 23

34 =============================================================================== Preinstallation Summary Please Review the Following Before Continuing: Product Name: Common Pack Service Installation Folder /opt/ibm/tivoli/tipv2components/tcrcomponent TIP Installation Directory /opt/ibm/tivoli/tipv2 TIP Version Installed TIP Administrator User Name tipadmin Database Client Directory /opt/oracle/product/11.2.0/db_1 Administrative Database JDBC URL Administrative Database BICONTROL User Name bicontrol Administrative Database Objects TableSpace Name wm_flexpm Target Database JDBC URL Disk Space Information (for Installation Target): Required: 8,418,696 bytes Available: 6,824,201,216 bytes 18. Review the Preinstallation Summary and press Enter to continue. After you have started the installation, do not end the process. The installer verifies that the Tivoli Integrated Portal server is at version 2.1 and that the server is running. The installation starts and the installation progress bar is displayed. ============================================================================== Installing [================== ================== ================== ==================] [--Custom code execution Started Custom code execution Completed ] v The Installation Complete screen is displayed when the installation is finished. The Common Pack Service is now installed. =============================================================================== Installation Complete Congratulations. The Common Pack Service has been successfully installed in the following location: /opt/ibm/tivoli/tipv2components/tcrcomponent PRESS <ENTER> TO EXIT THE INSTALLER: 24 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

35 v If there is a problem during installation, the changes that are made to the system are undone and you are prompted to exit the installer. =============================================================================== Installing [================== ================== ================== ==================] [--Custom code execution Started... Fatal error occurred during installation, Rolling back the installation......* * ************************* ************************* ************************* ************************...* * ************************* ************************* ************************* ************************* The installation of Common Pack Service has been rolled back. Please see the installation log for details. PRESS <ENTER> TO EXIT THE INSTALLER: 19. Press Enter to exit the installer. Results Common Pack Service runs the postinstall.sh script, and the following tasks are automatically performed on the server side: v Restarts the Tivoli Common Reporting server. v v v Assigns the SystemPackAdmin and CustomPackAdmin roles to the Tivoli Common Reporting administrative user, tipadmin. Creates a logins file with the appropriate passwords. For more information about the logins file, see The logins file on page 26. Sets the database connection profile. The database connection profile is updated to use the values that you specified during installation. These values are stored in the profile.properties file. What to do next v v v v Test the datasource connection as described in Configuring the Tivoli Common Reporting data source on page 14. If the installation is unsuccessful, see the Troubleshooting the installation on page 27 topic. FTP the logins file from <TIP_COMPONENTS_LOCATION>/TCRComponent/ commonpackservice/bin directory to your computer. Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components were installed. If you have set up Tivoli Common Reporting and the administrative database on different servers, the WIRELESS_HOST parameter does not reflect correctly in the global.properties file. For a workaround to this issue, see The WIRELESS_HOST parameter does not reflect correctly in the global.properties file on page 107. Chapter 3. Installing and configuring the Common Pack Service 25

36 The logins file The logins file contains certain passwords that are required by the pack_admin command and Model Maker Manager for authentication purposes. 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 tcraccess data source, as appropriate. The following passwords are required: tipadmin The default Tivoli Integrated Portal administrator user. bicontrol A control user that you must create on the database before running the installer. birefresh The birefresh user is created by the Common Pack Service Installer and has a default password of birefresh. The pack_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 tcraccess user password, then you must also change the Cognos tcraccess data source. If you change the Oracle bicontrol or birefresh user passwords, or the Tivoli Integrated Portal tipadmin user password, you must recreate the logins file with the new credentials. The old logins file is no longer valid. Verifying the Common Pack Service installation Complete the following steps to verify the Common Pack Service installation. Procedure Open your browser and enter the URL of the update site, <hostname>:<port>/ibm/commonservice/site. Use the host name and port that you use to log on to the Tivoli Common Reporting console in your system. The port number can vary depending on your installation. For example, A page similar to the following page is displayed, depending on your browser. 26 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

37 Troubleshooting the installation Tivoli Integrated Portal logs might help you identify the problem if the installation fails. Before you begin Known issues are documented in the Known Issues with Tivoli Netcool Performance Manager technote in the Support knowledge base at 01.ibm.com/support/docview.wss?uid=swg This technote contains known issues with Model Maker and Common Reporting on Tivoli Netcool Performance Manager, including Model Maker installation and user issues, and Common Reporting issues. About this task Check each of the following logs if you encounter a problem. Procedure 1. Check the last lines of the Tivoli Integrated Portal server output log file. <tip_location>/profiles/tipprofile/logs/server1/systemout.log Where <tip_location> is the Tivoli Integrated Portal installation directory. By default, /opt/ibm/tivoli/tipv2 for wireless and /opt/ibm/tivoli/tip21 for wireline. 2. Check the following file for errors that might be caused by the Common Pack Service WAR file deployment failing: <tip_location>/profiles/tipprofile/logs/wsadmin.traceout. 3. Look for exceptions in the Tivoli Integrated Portal server exception log file. <tip_location>/profiles/tipprofile/logs/ffdc/server1_exception.log 4. Check the <tip_location>/tcrcomponent/common_pack_service_installlog.log file for Common Pack Service installation failures. Example In this extract from a server1_exception.log file, you can see that the installation failed because the Tivoli Integrated Portal administrator password was incorrect. PasswordCheckFailedException com.ibm.ws.security.ltpa.ltpaserverobject.authenticate... Chapter 3. Installing and configuring the Common Pack Service 27

38 Uninstalling the Common Pack Service Complete the following tasks to uninstall the Common Pack Service. Uninstalling Resource Metric Viewer UI components How to uninstall Resource Metric Viewer UI components. About this task This task should only be completed if the Resource Metric Viewer is installed in the current version of the Common Pack Service. Procedure Uninstall the Resource Metric Viewer UI component by running the following command as root user: cd <TCRcomponent_dir>/commonpackservice/rmv/scripts./uninstall_rmv.sh <TIP install dir> <Tip user> <Tip password> 28 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

39 Running the uninstaller Run the uninstaller to remove the Common Pack Service. Files that were created after the installation are not removed. Procedure 1. Log in to the target server as the root user. 2. Go to the $TIP_COMPONENTS_LOCATION/TCRComponent directory. Where: TIP_COMPONENTS_LOCATION Is the location where the Tivoli Integrated Portal components are installed. By default, /opt/ibm/tivoli/tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. 3. Change permissions on the uninstallation files by entering the command: chmod +x./commonpackservice/uninstall/uninstall 4. Run the Uninstaller script by entering the command:./commonpackservice/uninstall/uninstall The Uninstall Common Pack Service screen is displayed. =============================================================================== Common Pack Service (created with InstallAnywhere) Preparing CONSOLE Mode Uninstallation... =============================================================================== Uninstall Common Pack Service Ready to uninstall... Common Pack Service The installation removes the features installed by InstallAnywhere only. The installation does not remove any files or folders created after installation. PRESS <ENTER> TO CONTINUE: 5. Press Enter to continue the uninstallation. The Uninstall Complete screen is displayed. Chapter 3. Installing and configuring the Common Pack Service 29

40 =============================================================================== Uninstall Common Pack Service Ready to uninstall... Common Pack Service The installation removes the features installed by InstallAnywhere only. The installation does not remove any files or folders created after installation. PRESS <ENTER> TO CONTINUE: =============================================================================== Uninstalling * drop user tcrtime--> completed.. drop user cdmnet--> completed uninstall all database tables uninstall all database tables --> completed uninstall commonservice uninstall commonservice --> completed * ************************* ************************* ************************* ************************...* * ************************* ************************* ************************* ************************* =============================================================================== Uninstall Complete All items were successfully uninstalled. SHUTDOWN REQUESTED (X) commiting registry (X) shutting down service manager (X) cleaning up temporary directories cleanup() calling cleanupunix() Results The Common Pack Service is uninstalled. Files created by users or created by using UNIX shell scripts are not removed. What to do next If you do not need any of the files in the repository, you can remove the $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice folder. 30 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

41 Chapter 4. Installing and configuring Model Maker Manager Model Maker Manager is a mandatory tool for Tivoli Common Reporting enablement, as it is needed during the common pack installation process. Tivoli Netcool Performance Manager administrators use Manager to manage common packs and deploy common packs to the Content Store. Common pack modelers use Manager to create common packs or to modify common pack contents. Installing Model Maker Manager Model Maker Manager is based on Eclipse and is installed by downloading and extracting the archived files to a location of your choice. Procedure 1. Download the Model Maker Manager compressed file Managerversion_number-win32.win32.x86.zip. 2. Extract the compressed file in a location of your choice. Note: Do not extract the compressed file into a folder path that contains spaces, for example, C:/Program Files/ModelMaker. 3. Assuming an extraction location of C:\Manager-version_numberwin32.win32.x86, the Model Maker Manager executable file is now available at C:\Manager-version_number-win32.win32.x86\Manager\manager.exe. Configuring Model Maker Manager Complete the following tasks to configure Model Maker Manager. Opening Model Maker Manager You open Model Maker Manager by running a Windows executable file. About this task This procedure assumes that the files are in the C:\Manager folder. During installation, you can extract Model Maker Manager files to a location of your choice. Procedure 1. Navigate to the C:\Manager folder. 2. Double-click the manager.exe file. The Model Maker Manager opens showing the Common Pack Models tab, where downloaded packs are displayed. Copyright IBM Corp. 2011,

42 Configuring the Common Pack Service preferences Configure the Common Pack Service preferences by using the Common Pack Service preference page. You must specify only the service host and the service port, the other fields can be left at their default values. Procedure 1. Select Window > Preferences. 2. In the Preferences window, select Common Pack Services. The Common Pack Service preferences window opens. 3. Enter the host server and the port details. 4. In the Credentials File Path field, select the credentials file that is logins.txt. The logins.txt file is available in $<TIP_COMPONENTS_LOCATION>/TCRComponent/ commonpackservice/bin directory. Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components were installed. FTP the logins.txt file to your computer. This information is used by the Common Pack Service Deploy Wizard to start the remote server method. 5. Click Apply to accept the remaining default values. 6. Click OK. The Preferences window closes. Configuring the wireless database preferences Configure the wireless database preferences to allow connections to the wireless database. Procedure 1. Select Window > Preferences. 2. In the Preferences window, select Database and configure the JDBC driver path. 32 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

43 Option JDBC Driver Path Description The full path to the database driver implementation used to connect to the database instance. For example, C:\oracle\instantclient_11_2\ojdbc6.jar. 3. Click Apply. 4. Expand Database and select Wireless Database. The Wireless Database window opens. 5. Enter the required details and click Apply. Option Host Port Database Name User Description The hostname or IP address of the computer where the database instance is running. The port used to connect to the database instance, typically The name of the database instance, typically vtdb. A database user, typically the virtuo user. 6. Click OK. The Preferences window closes. Configuring the wireline database preferences Configure the wireline database preferences to allow connections to the wireline database. Procedure 1. Select Window > Preferences. 2. In the Preferences window, select Database and configure the JDBC driver path. Option JDBC Driver Path Description The full path to the database driver implementation used to connect to the database instance. For example, C:\oracle\instantclient_11_2\ojdbc6.jar. 3. Click Apply. 4. Expand Database and select Wireline Database. The Wireline Database window opens. 5. Enter the required details and click Apply. Option Host Port Database Name User Description The hostname or IP address of the computer where the database instance is running. The port used to connect to the database instance, typically The name of the database instance, typically pv. A database user, typically the pv_admin user. Chapter 4. Installing and configuring Model Maker Manager 33

44 6. Click OK. The Preferences window closes. Configuring automatic updates and notifications You can configure Model Maker Manager for automatic updates and to be notified when updates are available. Procedure 1. Select Window > Preferences. 2. In the Preferences window, expand Install/Update, and select Automatic Updates. 3. Select the check box next to the Automatically find new updates and notify me option. 4. Select the appropriate preferences and click Apply. 5. Click OK. The Preferences window closes. Configuring the software update site You must configure the location of the Common Pack Service update site to install updates and to work with common packs in the repository. About this task The Common Pack Service update site is located on the Tivoli Common Reporting server with the URL: where: <host> is the server where Tivoli Common Reporting is installed. <port> is the HTTP port of the Tivoli Common Reporting installation. Note: Because of known issues with the Eclipse Update Manager, do not use the HTTPS protocol. Note: When you have multiple software sites in the list, a check box is supposed to enable you to perform actions, such as Remove, on multiple entries. However, this functionality is not currently supported. Procedure 1. Select Window > Preferences. 2. In the Preferences window, expand Install/Update, and select Available Software Sites. 3. Click Add. 4. On the Add Site window, enter a name and the URL of the site and click OK. Ensure that you use the HTTP protocol ( rather than secure HTTP ( for the update site. The Eclipse Update Manager does not work well with the HTTPS protocol. 5. Click OK. The Preferences window closes. 34 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

45 Configuring the Cognos preferences Configure the Cognos preferences. You must configure the BMT Script Player location before you can combine common pack models or deploy common packs. About this task Note: The Cognos Dispatcher URI field is automatically populated from IBM Cognos Configuration when you navigate to the executable file in the BmtScriptPlayer Executable Path field. However, to pick up subsequent changes to the Reporting Engine URL made in IBM Cognos Configuration, you must return to this Cognos Preferences page and navigate to the executable file again. Procedure 1. Select Window > Preferences. 2. Enter the following details and click Apply. 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 8.4.1, the default location is C:\Program Files\cognos\c8\bin\ BmtScriptPlayer.exe. A read-only value 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, tarf/servlet/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 using IBM Cognos Configuration. Tivoli Common Reporting user name, for example tipadmin. Tivoli Common Reporting user password. The namespace is defined in the Security section of IBM Cognos Configuration, by default VMMProvider. 3. Click OK. The Preferences window closes. Chapter 4. Installing and configuring Model Maker Manager 35

46 36 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

47 Chapter 5. The Base Common Pack Suite The Base Common Pack Suite is a set of generic Base Common Packs (BCPs), some of which are mandatory requirements for working with common packs. All common packs have a dependency on at least one BCP, the TCR Time BCP. For Wireless users, BCPs provide the cross-vendor technology support provided by GOMs and GOMlets for technology packs. The Base Common Pack Suite consists of an archive file containing a set of common pack JAR files, which you must download and extract before installing. v v v The TCR Time BCP is a mandatory dependent pack for all wireless and wireline common packs, and provides a common time dimension for reporting. It must be installed before you can work with any common packs. The Wireline Common BCP is a mandatory dependent pack for all wireline common packs. It must be installed before you can work with wireline common packs. Typically, a number of Wireless BCPs are dependent packs for a wireless common pack. Wireless BCPs support a number of Global Object Model (GOM) and GOMlet technology packs. Refer to individual wireless common pack release notes to see the list of dependent packs for a particular pack. For current version information about the Base Common Pack Suite, see the Known issues with Tivoli Netcool Performance Manager 1.3.2Known issues with Tivoli Netcool Performance Manager technical note in the Support Knowledge Base. Installing a Base Common Pack The Base Common Pack Suite is updated periodically with the latest versions of the BCPs. Before you install or create common packs, you must download the latest version of the Base Common Pack Suite, and install the BCPs you require. Procedure 1. Download and extract the Base Common Pack Suite to a location of your choice. See Chapter 5, The Base Common Pack Suite. 2. Locate the required dependent common packs for the pack you are installing: v The TCR Time BCP is a dependent pack for all common packs; wireless or wireline. v The Wireline Common BCP is the dependent pack for all wireline common packs. v Typically, a number of wireless BCPs are dependent packs for wireless common packs. See the release notes for the common pack you are installing for a list of dependent packs. 3. Add the TCR Time BCP. See Adding a base common pack to the repository on page Activate the TCR Time BCP. See Activating base common packs in the repository on page Populate the database calendar schema table for the TCR Time base common pack by using the Common Pack Service pack_admin calendar-refill action. See Populating the calendar schema table for TCR Time on page 40. Copyright IBM Corp. 2011,

48 Adding a base common pack to the repository You can add a base common pack to the common pack repository by using the Add Common Packs command. Adding a base common pack adds the pack to the administrative database and registers that version of the base common pack with the system. That version of the base common pack shows on the common pack list of the system, but that version is not used until it is activated. Before you begin You need a logins file for this procedure. If a logins file does not exist, you can create a logins file on the server by using the pack_admin command. For more information, see Appendix E, Creating a logins file with the appropriate passwords, on page 147. Copy the file back to your PC before you start this procedure. About this task To ensure that you see the latest common packs on the system after adding common packs, always refresh your view by restarting Model Maker Manager. Procedure 1. In Model Maker Manager, click the Common Pack Service button ( ) onthe toolbar. The Common Pack Service Selection Wizard opens. 2. Select Add Common Packs from the list of commands. 3. Click Next. The Add Common Packs Wizard opens. 4. On the Login page, browse to a logins file. 5. Click Next. 6. On the Add Common Packs page, browse to a directory containing common pack JAR files. 7. Select the required JAR files and click Open. The selected common packs are listed in the wizard. 8. Click Finish. If the operation is successful, the wizard closes. If the operation fails, a message is displayed. Adding multiple base common packs to the repository You can add multiple base common packs to the repository by using the Add Common Packs from a Directory command. This service loads all base common packs found in the directory to the repository. About this task To ensure that you see the packs on the system after adding packs, always refresh your view by restarting Model Maker Manager. Procedure 1. In Model Maker Manager, click the Common Pack Service button ( ) onthe toolbar. The Common Pack Service Selection Wizard opens. 2. Select Add Common Packs from a Directory from the list of commands. 3. Click Next. The Add Common Packs from a Directory Wizard opens. 4. On the Login page, browse to a logins file. 5. Click Next. 38 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

49 6. On the Add Common Packs page, browse to the location of the common pack JAR files. 7. Click OK. 8. Click Finish. If the operation is successful, the wizard closes. If the operation fails, a message is displayed. Adding base common packs by using the CLI You can also use the pack_admin command to add base common packs to the common pack repository. Procedure Add a base common pack or multiple base common packs by completing the following steps: 1. Add a base common pack. For example, add the ibm.tcr.time common pack by running the following command as root user:./pack_admin.sh -add -pack /demo/commonpacks/ibm.tcr.time jar -logins./logins.txt CTGTRR232I The operation add successfully performed. For more information on the pack_admin -add command, see pack_admin -add on page Optional: Add multiple base common packs from a directory by entering the following command. The packs are automatically added in the correct sequence../pack_admin.sh -add -dir /demo/commonpacks -logins./logins.txt CTGTRR232I The operation add successfully performed. Activating base common packs in the repository You can activate a base common pack or composite base common pack in the repository by using the Activate Common Packs command. Database schemas are installed and the active version of the common pack is updated. If the pack was previously activated, the database schemas are updated. Before you begin You need a logins file for this procedure. If a logins file does not exist, you can create a logins file on the server by using the pack_admin command. For more information, see Appendix E, Creating a logins file with the appropriate passwords, on page 147. Copy the file back to your computer before you start this procedure. Procedure 1. In Model Maker Manager, click the Common Pack Service button ( ) onthe toolbar. The Common Pack Service Selection Wizard opens. 2. Select Activate common pack from the list of commands. 3. Click Next. The Activate Common Packs Wizard opens. 4. On the Login page, browse to a logins file. 5. Click Next. The Activate common pack page displays a list of installed packs. 6. Select a base common pack to activate. Chapter 5. The Base Common Pack Suite 39

50 7. Click Finish to activate the pack in the repository. If the operation is successful, the wizard closes. If the operation fails, a message is displayed. Activating base common packs by using the CLI You can also use the pack_admin command to activate base common packs to update the database schemas. Procedure Activate the base common pack to create the associated database schema. For example, activate the ibm.tcr.time base common pack by entering the following command:./pack_admin.sh -activate -pack ibm.tcr.time -version logins./logins.txt CTGTRR231I The operation activate successfully performed. For more information on the pack_admin -activate command, see pack_admin -activate on page 130. Populating the calendar schema table for TCR Time You must populate the database calendar schema table for the TCR Time base common pack by using the Common Pack Service pack_admin command. Before you begin The TCR Time base common pack must have been added to the repository and activated before you begin this procedure. When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. About this task You use the following actions to populate the database calendar schema table. Actions defined in the tcr.time common pack. populate 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 we have the timestamps in the calendar for the data arriving. calendar-refill 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. Procedure 1. Log in to the Tivoli Common Reporting server. 2. Change to the following directory: $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where: 40 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

51 TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default, /opt/ibm/tivoli/tip21components for wireline and /opt/ibm/tivoli/tipv2components for wireless. 3. Set properties for the population of the calendar table. For example, you can populate the time dimension with 366 days of 15 minute timestamps (past and future) by running the following command as root user:./pack_admin.sh -set -property retention:366, buffer:366, granularity:15 -pack ibm.tcr.time -logins./logins.txt where: v retention:366 populates the calendar table with intervals 366 days before the current date. v buffer:366 populates the calendar table with intervals 366 days from the current date. v granularity:15 specifies that the lowest interval in the calendar table is 15 minute intervals. v logins.txt is the file that is created when you install the Common Pack Service. 4. Populate calendar schema tables for the ibm.tcr.time common pack by running the following command as root user:./pack_admin.sh -execute -action calendar-refill -logins./logins.txt Common Pack Service is processing request. CTGTRQ005I The operation executeaction successfully performed. When you issue the command to execute an action, it executes the action on all common packs that define that action. The calendar-refill action is defined in the tcr.time common pack only. Adding the calendar indexes If you are using the latest TCR Time v1.0.8, you do not need to perform these steps. Before you begin Confirm that you have tcr.time installed: 1. Run the command as root user:./pack_admin.sh -list -packs -logins logins.txt Note: Replace logins.txt with the name of your logins file. 2. Check that the output corresponds to the following: Name:ibm.tcr.time Symbolic name:ibm.tcr.time Version:1.0.8 Creation date:3/20/12 8:56 AM Active?:true Procedure 1. Navigate to the directory that contains the Model Maker package. 2. FTP the add_times_indexes.sql script to a temporary directory on the target server (for example, /tmp/). 3. Telnet to the target server. 4. Navigate to the directory into which you saved the script. 5. Run the script by using the following command: Chapter 5. The Base Common Pack Suite 41

52 42 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

53 Chapter 6. Installing and configuring Model Maker Extractor (Wireless only) Extractor is an optional tool that common pack 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 extracted is converted into a Common Intermediate Format (CIF) file (.tnpmmodel) for later processing into a data model. Installing Model Maker Extractor Model Maker Extractor is installed by extracting an archive file to a location of your choice. Procedure 1. Download the Model Maker Extractor archive file Extractor_versionwin32.win32.x86.zip. 2. Extract the Extractor_version-win32.win32.x86.zip file to a location of your choice. For example, C:\Extractor_version-win32.win32.x86. Results The Model Maker Extractor executable file is now available at Extractor_version-win32.win32.x86\Extractor_version\launcher.exe. Configuring Model Maker Extractor Complete the following tasks to configure Model Maker Extractor. Opening Model Maker Extractor You open Model Maker Extractor by running a Windows executable file. Before you begin This procedure assumes that the Model Maker Extractor files are in the Extractor_version-win32.win32.x86.zip\Extractor_version folder. During installation, you can extract Model Maker Extractor files to a location of your choice. Procedure 1. Go to the folder where Model Maker Extractor executable file is located, for example Extractor_version-win32.win32.x86.zip\Extractor_version\ launcher.exe. 2. Double-click launcher.exe. Model Maker Extractor opens showing the Resource perspective. 3. In the Workspace Launcher window, accept the default location C:\Extractor_version-win32.win32.x86.zip\Extractor_version\workspace, or browse to a location of your choice for the workspace where your Model Maker Extractor projects and files are stored. You can modify this location later if required. Copyright IBM Corp. 2011,

54 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\instant\ojdbc6.jar for Oracle 11g. 4. Click OK. 44 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

55 Chapter 7. Upgrading Model Maker Model Maker is upgraded by installing the newer versions of each of the Model Maker components that you are using. About this task To upgrade Model Maker components, first remove the existing components of Model Maker, and then install the newer versions. Configure them by following the instructions in the IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide. Procedure 1. Ensure that no users are logged in to Tivoli Integrated Portal. 2. Copy all the common packs and BCPs from the existing Common Pack Service folder for backup from <TIP_COMPONENTS_LOCATION>/TCRComponent/ commonpackservice/dbcache to a temporary location For example, demo/commonpacks. 3. Copy all the CIF files from<tip_components_location>/tcrcomponent/ commonpackservice/cifs/users to a temporary location. For example, demo/cifs. You require the CIF files for deploying them later. 4. Uninstall the Common Pack Service. For more information, see Uninstalling the Common Pack Service on page Delete the existing Common Pack Service folder in <TIP_COMPONENTS_LOCATION>/TCRComponent/. 6. Log in to the database as SYSDBA and check that all the common pack schemas and users are dropped by using the following commands: SELECT * FROM dba_users WHERE DEFAULT_TABLESPACE = WM_FLEXPM ; Note: Ensure that no rows are returned. 7. Install the latest Common Pack Service starting from Preinstallation tasks on page Add all the BCPs that were installed before. For more information, see Adding multiple base common packs to the repository on page Activate the BCPs. For more information, see Activating base common packs in the repository on page 39. You can activate the BCPs and common packs by using the following command: pack_admin.sh -activate -pack <pack_name> -version <version_number> -logins <logins_file> Note: The order of activation of the packs is important as most packs are dependent. 10. Deploy the common packs by using the pack_admin -deploy command. For more information, see pack_admin -deploy on page 138. Or, use Model Maker Manager to deploy. You must FTP the CIF files from demo/cifs folder to your computer, and then deploy. For more in formation, see Deploying a common pack (Wireless only) on page Populate the calendar schema table for TCR Time BCP. For more information, see Populating the calendar schema table for TCR Time on page 40. Copyright IBM Corp. 2011,

56 46 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

57 Chapter 8. Creating common packs (Wireless only) Creating a common pack for Common Reporting on Tivoli Netcool Performance Manager requires all Model Maker components. You use Model Maker Extractor to extract the required metadata from a technology pack or from the Tivoli Netcool Performance Manager database.extractor outputs the metadata in a Common Intermediate Format (CIF) file (.tnpmmodel) that serves as the input for Model Maker Manager. You then use Model Maker Manger to generate a Cognos model built from the metadata in the CIF file, and all remaining artifacts in the required directory structure for common pack contents. Finally, you use Model Maker Manager to browse to the common pack contents and create a common pack JAR file that is ready to add to the Common Pack Repository in the Tivoli Common Reporting component of the Tivoli Netcool Performance Manager system. Overview of creating common packs for Wireless pack modelers Wireless pack modelers can follow these steps to create common packs or to extend existing common packs. Each step points to other topics for more detailed information. About this task These steps assume that you have a fully operational Tivoli Netcool Performance Manager system with all of the Model Maker components installed. Before you can begin to create common packs, you must install a number of Base Common Packs (BCPs) from the Base Common Pack Suite. Base Common Packs (BCPs) are themselves common packs and you install them exactly as you install any other common packs. Procedure 1. Download and extract the Base Common Pack Suite to a location of your choice. See Chapter 5, The Base Common Pack Suite, on page Install the TCR Time BCP. See Installing a Base Common Pack on page You can model the raw data from a technology pack or directly from the Tivoli Netcool Performance Manager system. See Creating a common pack containing a raw data model on page You can extract and model Summary data from the Tivoli Netcool Performance Manager system. See Creating a common pack containing a summary definitions model on page You can extract and model busy hour data from the Tivoli Netcool Performance Manager system. See Creating a common pack containing a busy hour definitions model on page To 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 Copyright IBM Corp. 2011,

58 model filtering on page 49 and for the procedure, see Filtering metrics from a model in an existing CIF file on page 52. Identifying the appropriate dependent packs Use these guidelines to help you choose the appropriate dependent packs. Wireless You can use the following table to map wireless Global Object Model (GOM) and GOMlet technology packs to base common packs. You can then include the appropriate base common packs as dependents for your common pack. Additionally, if you want to include resources from specific Vendor Specific packs, you must list these packs as dependents for your common pack. GOMs and GOMlets vallent-vt-neutral_core_gom-1.0.tar.gz vallent-vt-neutral_gsm_bss_nss_gom-1.0.tar.gz Base Common Packs ibm.cdm.net ibm.tnpm.net ibm.cdm.net.mobile ibm.tnpm.net.mobile ibm.cdm.net.mobile.gsm vallent-vt-neutral_gprs_bss_gom-1.0.tar.gz vallent-vt-neutral_gprs_umts_cn_gom-1.0.tar.gz vallent-vt-neutral_umts_utran_gom-1.0.tar.gz * vallent-vt-neutral_lte_eps_gom-2.0.tar.gz vallent-vt-hua_gomlet-2.4.tar.gz vallent-vt-nok_gomlet-2.1.tar.gz vallent-vt-vnl_gomlet-2.4.tar.gz vallent-vt-pgm_gomlet-2.0.tar.gz vallent-vt-eri_gomlet-2.5.tar.gz ibm.tnpm.net.mobile.gsm ibm.cdm.net.mobile.gprs ibm.tnpm.net.mobile.gprs ibm.cdm.net.mobile.umts ibm.tnpm.net.mobile.umts ibm.cdm.net.mobile.lte ibm.tnpm.net.mobile.lte ibm.cdm.net.mobile.huawei ibm.tnpm.net.mobile.huawei ibm.cdm.net.mobile.nokia ibm.tnpm.net.mobile.nokia ibm.cdm.net.mobile.neutral ibm.tnpm.net.mobile.neutral ibm.cdm.net.mobile.pgm ibm.tnpm.net.mobile.pgm ibm.cdm.net.mobile.ericsson ibm.tnpm.net.mobile.ericsson * Pack extensions, such as Neutral UMTS UTRAN Ext GOM 1.0, can be ignored when setting up the dependent packs. 48 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

59 Data model filtering 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 common pack, 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 or updated common pack. 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. Creating a common pack containing a raw data model You can extract raw data counters from a technology pack. You can then create a common pack containing a model that report authors can use to create reports by using those raw data counters. Procedure 1. In Model Maker Extractor, 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 a Wireless Pack Archive. 6. Click Next. 7. On the Select Datasource page, select from one of the following sources: v Import from ZIP or TAR.GZ archive: Import from a downloaded package from Extreme Leverage. v Import from expanded folder: Import a technology pack copied from an installed Tivoli Netcool Performance Manager system. 8. Click Next. 9. Browse to a folder containing a technology pack and click Open. The contents of the technology pack are imported and inspected. 10. Click Next. 11. 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. Chapter 8. Creating common packs (Wireless only) 49

60 12. On the Save As page, a name for the Common Intermediate Format (CIF) file (.tnpmmodel) is generated based on the name of the technology pack. Select your project folder, and then click Finish. 13. 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. 14. Deploy the CIF (.tnpmmodel) by using Model Maker Manager. For more information, see Deploying a common pack (Wireless only) on page 66. Creating a common pack containing a summary definitions model On Tivoli Netcool Performance Manager - Wireless component, you can extract the summary definitions that are associated with a particular technology pack from the Tivoli Netcool Performance Manager database. You can then create a common pack that contains a model that report authors can use to create reports by using those summary definitions. Before you begin Ensure that you configured the JDBC driver in Model Maker Extractor preferences so that you can connect to the database to extract the summary definitions.. Procedure 1. In Model Maker Extractor, 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. 5. On the Select page of the Import wizard, expand TNPM Pack Modeling and select Import Summaries. 6. Click Next. 7. On the Database detail page, specify the database details. v Host: The host server name, for example, server.ibm.com. v Username: The database user name, for example, virtuo. v Password: The database password. 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 common pack 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 IBM Tivoli Netcool Performance Manager: Administration Guide - Wireless Component. 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: 50 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

61 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. Deploy the CIF (.tnpmmodel) by using Model Maker Manager. For more information, see Deploying a common pack (Wireless only) on page 66. Creating a common pack 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 common pack 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 Model Maker Extractor to ensure that you can connect to the database to extract the busy hour definitions Procedure 1. In Model Maker Extractor, 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. 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 detail page, specify the database details. v Host: The host server name, for example, server.ibm.com. v Username: The database user name, for example, virtuo. v Password: The database password. 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. Chapter 8. Creating common packs (Wireless only) 51

62 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. 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. Deploy the CIF (.tnpmmodel) by using Model Maker Manager. For more information, see Deploying a common pack (Wireless only) on page 66. Filtering metrics from a model in an existing CIF file Before generating a 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 Model Maker Extractor, 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. 52 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

63 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. 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. Chapter 8. Creating common packs (Wireless only) 53

64 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 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,0,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 Results The query returns the list of metric groups, which you can use as a filter file in Model Maker Extractor. For example, CPU_Device.Huawei.CPU_Of_Board ENodeBFunction.Huawei.BBU ENodeBFunction.Huawei.ENodeB EUtranCell.Huawei.CQI EUtranCell.Huawei.Cell_Algorithm EUtranCell.Huawei.DRB PMU_Device.Huawei.PMU RRU_Device.Huawei.RRU Identifying resource groups from the model documentation Model Maker Extractor 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 pack 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 Model Maker Manager, 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. 54 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

65 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,0,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 ( C , C , C ) Results A list of metric groups is returned, for example: METRIC_GROUP Cell.Huawei.Call_drop_overview Cell.Huawei.Short_message Cell.Huawei.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. Chapter 8. Creating common packs (Wireless only) 55

66 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. 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. 56 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

67 Chapter 9. Updating and extending common packs (Wireless only) Updating common packs Use the following information to update and extend common packs in the common pack repository and to work with common packs on your computer. You can update the version of a common pack by creating another version of the common pack and updating the version number. You can update the Cognos model, the database schema, or the reports in a common pack. You update a common pack in the repository by deploying a new version of that common pack. Updating a common pack on the repository requires the following steps: v Use Model Maker Manager to create a composite version of the pack by using the combining pack option. v Using Framework Manager, or by manual changes, update the composite pack contents. For example, you can update the database schema, the Cognos model or reports. Common pack developers are responsible for verifying any changes made to a common pack. v Use Model Maker Manager to decompose the updated composite pack into a JAR file for deployment. v In Model Maker Manager, deploy the updated common pack to the Common Pack Repository by using the Common Pack Service Wizard. v You can then download the deployed common pack and open it in Framework Manager. For information about how to download a deployed common pack, see Downloading common packs on page 59. Creating a new version of a common pack To update a common pack to a new version, create a composite common pack with a new version number. Before you begin If the Cognos Framework Manager BMT Script Player has not already been configured in Model Maker Manager, you must configure it during this task. Procedure 1. In the Common Pack Models view, select the check box next to the common pack that you want to update. The Combine Models button ( ) becomes available. 2. Click the Combine Models button. The Composite Model Output window opens. If the BMT Script Player location was not previously configured, the Cognos preferences window opens for you to enter the required details. For the configuration options, see Configuring the Cognos preferences on page Enter an output directory. Copyright IBM Corp. 2011,

68 4. Enter the new version number. There is a certain range of acceptable version numbers and you must increment the number. For example, for a version number 1.0.0, you must choose a number from up to and including For a version number of 2.1.2, you must choose a number from up to and including Click OK. A progress bar is displayed. On completion, the resulting model output directory is displayed. Considerations when modifying models Pack developers can update a common pack model by adding custom extensions to model certain aspects of the database not already captured in the current pack version. You can update common pack models by using Framework Manager. v v v Any new namespaces added to the model must not clash with existing common pack namespaces. You must follow these conventions when adding new namespaces: Namespace names must end with (Database), (Consolidation), (Dimensional) or (Presentation). Do not change model content belonging to other common packs. Any changes to model content that is part of another common pack is lost during the decompose operation. New namespaces must be placed in the appropriate parent namespace: Model, Database Views, Consolidation Views or Dimensional Views. Any new package created must not have the same name as the common pack. This name is reserved for the Default Package name created by Model Maker Manager at run time. Any new Query Subjects must be in the database being modeled, and new database schema must be added to the common pack if required. A manual step is required to update the bipack.xml file for any database schema added to the common pack. You must export any reports required in the common pack from Report Studio. A manual step is required to update the bipack.xml file for any new reports added to the common pack. After creating a composite pack, as outlined above, a user might extend the model by adding custom namespaces. These namespaces must follow the common pack model convention. Decomposing composite common packs for addition to the repository To add a composite common pack to the repository, you must first decompose the common pack to separate the composite model into its individual constituent models. About this task To support version control for common pack models, the integrity of each model must be maintained. Decomposing a composite pack separates the composite model into the correct versions of its constituent models. Individual models can then be updated to new versions as normal, which would not be possible if the model was added as a composite model. When you select a composite pack in the Common Pack Wizard, the default action is to decompose the composite pack. Decomposing a composite pack creates a JAR 58 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

69 file that you can deploy to the repository by using the Common Pack Wizard. Procedure 1. In Model Maker Manager, click the New common pack button ( ). The Common Pack Wizard is displayed. 2. In the Common Pack Directory field, click Browse to go to a folder containing the composite common pack. All common packs in the folder are displayed. 3. In the Output Directory field, click Browse to go to a folder where you want the JAR files to be created. The folder must exist, create a folder in Windows Explorer if required. 4. Select the composite common pack and click Finish. A JAR file is created for the selected common pack. What to do next You can deploy (add and activate) the composite common pack to the common pack repository by using the Common Pack Service Wizard to select the JAR file. Downloading common packs Download the common pack models from the Common Pack Service to your local instance of the Model Maker Manager. About this task Note: You must not try to uninstall common packs by using Model Maker Manager Help > Install New Software option. This generic Eclipse uninstallation option is not supported in Model Maker Manager. Using this option just deletes a common pack artifact maintained by Model Maker Manager and does not uninstall a common pack from the Common Pack Service. Procedure 1. Select Help > Install New Software. 2. Select a site or enter the location of a site. 3. Select common packs to download. When you select a common pack to download, its dependent packs are automatically downloaded. 4. Click Next. 5. The downloaded common packs are listed in the Common Pack Models pane. Combining multiple common packs You can extend the scope of available data by combining a number of common packs that contain required resources. If you have installed the Common Pack Service appropriately in an environment containing both the wireless and wireline components, you can combine wireless and wireline common packs. Procedure 1. In Model Maker Manager, identify the common packs that contain the resources you need. 2. Combine the common pack models as described in Combining common pack models on page 60. Chapter 9. Updating and extending common packs (Wireless only) 59

70 3. To enable the composite pack to be added to the common pack repository, decompose the composite pack as described in Decomposing composite common packs for addition to the repository on page 58. Combining common pack models You can combine a number of common pack models into a composite model. This composite model is then converted to a single package when you deploy a common pack. In Common Reporting, you cannot report across multiple packages. By creating a package containing objects from multiple common packs, you can effectively report across multiple packages in Tivoli Netcool Performance Manager. Before you begin You must configure the Cognos Framework Manager BMT Script Player in Model Maker Manager preferences. If the BMT Script Player has not already been configured in preferences, you must configure it during this task. Procedure 1. In the Common Pack Models view, select the check box next to two or more models that you want to combine. The Combine Models button ( ) becomes available. 2. Click the Combine Models button. The Composite Model Output window opens. If the BMT Script Player location was not previously configured in Model Maker Manager preferences, the Cognos preferences window opens for you to enter the required details. For the configuration options, see Configuring the Cognos preferences on page Enter an output directory. 4. Enter the common pack definition: Option Name Symbolic Name Version Vendor Description A project name. A unique name for the common pack. A version number of the format major.minor.service, for example Enter your company name. 5. Choose whether to create a default package for the model or not. The default package displays all Presentation Views that are part of the model. The package is given the same name as the name you enter for the project name. 6. Click OK. A progress bar is displayed. On completion, the resulting model output directory is displayed. 7. Open the new model in Framework Manager and validate that the contents are as expected. What to do next Before you can deploy the composite pack, you must decompose the composite pack as described in Decomposing composite common packs for addition to the repository on page IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

71 Adding reports to a common pack You can add reports created in Report Studio to a common pack to be deployed for Common Reporting users. About this task v A common pack directory containing reports must contain the directories localization and report. v The localization directory must contain a.properties file to support globalization for report names, and so on. This file is currently unused. v The report directory contains the report definition.xml files exported from Report Studio. Procedure 1. Deploy a common pack. 2. Create a report from the deployed common pack. 3. In Report Studio, export the report definition XML by clicking Tools > Copy Report to Clipboard and saving the report as a.xml file. 4. Add the report specification.xml file directly to the report directory of the common pack. The report directory does not support nested directories 5. Update the bipack.xml file for the common pack by referring to the following example: <?xml version="1.0" encoding="utf-8"?> <bipack>... <reports> <translation file="localization" prefix="trans"/> <report> <name>device Raw Report</name> <file>report/device_raw_report.xml</file> </report> <report> <name>interface Raw Report</name> <file>report/interface_raw_report.xml</file> </report> <report> <name>mib2 Summary Report</name> <file>report/rfc_mib2_summary_report.xml</file> </report> </reports> </bipack> v The reports section in the bipack.xml file lists the reports in the common pack. v The file attribute of the translation element points to the common pack localization directory. v The prefix attribute of the translation element is the name of the.properties file in the localization directory. v Each report has a name and a file element. 6. Create an updated version of the common pack. Chapter 9. Updating and extending common packs (Wireless only) 61

72 62 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

73 Chapter 10. Installing common packs You must install each common pack, and its dependent common packs, on the Tivoli Common Reporting component of the Tivoli Netcool Performance Manager system. After you have installed the common pack for a particular technology, the common pack contents are available in the Common Reporting user interface. Report authors can then access the common pack contents, such as data models or reports, from the Common Reporting user interface in the Tivoli Integrated Portal. Overview of installing common packs for pack administrators Wireline and Wireless Pack Administrators can follow these steps to install existing common packs. Each step points to other topics for more detailed information. Before you begin This procedure assumes that you have a fully operational Tivoli Netcool Performance Manager system with the Common Pack Service and Model Maker Manager installed. As part of the procedure, you install a number of Base Common Packs (BCPs) from the Base Common Pack Suite. Base Common Packs (BCPs) are themselves common packs and you install them exactly as you install any other common packs. Ensure that you have performed the following actions, before you deploy a common pack: 1. Download and extract the Base Common Pack Suite to a location of your choice. See Chapter 5, The Base Common Pack Suite, on page Locate the required dependent common packs for the pack you are installing: v v The TCR Time BCP is a dependent pack for all common packs; wireless or wireline. The Wireline Common BCP is the dependent pack for all wireline common packs. v Typically, a number of wireless BCPs are dependent packs for wireless common packs. See the release notes for the common pack you are installing for a list of dependent packs. 3. Create a logins file. See Appendix E, Creating a logins file with the appropriate passwords, on page Add the TCR Time BCP. See Adding a base common pack to the repository on page Activate the TCR Time BCP. See Activating base common packs in the repository on page Populate the database calender schema table for the TCR Time base common pack by using the Common Pack Service pack_admin calendar-refill action. 7. Wireless Component only: Populate the database schema tables by using the Common Pack Service pack_admin data-refill action. See Wireless Component only: Populating the database schema tables on page 64. Copyright IBM Corp. 2011,

74 About this task This general procedure illustrates the separate steps involved in installing a common pack, so is not necessarily the most efficient procedure. For example, you can add the common pack and all its dependent packs in one step. When you get more familiar with Model Maker, try these other options. Procedure Deploy the common pack by using Model Maker Manager to a Report Package available for reporting. The contents of the common pack are deployed as a report package to the Content Store on the Tivoli Common Reporting server. See Deploying a common pack (Wireless only) on page 66. Wireless Component only: Populating the database schema tables Wireless users must populate the database schema tables by using the Common Pack Service pack_admin command. Before you begin When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. About this task Typically, the data-refill action is run once when you deploy a pack. You use the data-refill action to populate the database schema tables. The data-refill action is defined in all common packs except tcr.time. The data-refill action populates the hierarchy tables on which the Cognos data models depend. The data-refill action cleans out and fully populates the DM tables. Procedure 1. Log in to the Tivoli Common Reporting server. 2. Change to the following directory: $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where: TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed. By default, /opt/ibm/tivoli/tipv2components. 3. Populate schema tables in all Base Common Pack (BCP) and Vendor-Specific common packs by entering the following command:./pack_admin.sh -execute -action data-refill -logins./logins.txt Where: logins.txt is the logins file that you created in a previous task, see Appendix E, Creating a logins file with the appropriate passwords, on page 147 Common Pack Service is processing request. CTGTRQ005I The operation executeaction successfully performed. The data-refill action is defined in all Base Common Pack (BCP) and vendor-specific common packs. 64 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

75 Listing common packs in the repository You can list the common packs in the repository by using the List Common Packs command. Before you begin You need a logins file for this procedure. If a logins file does not exist, you can create a logins file on the server by using the pack_admin command. Copy the file back to your Windows computer before starting this procedure. Procedure 1. In Model Maker Manager, click the Common Pack Service button ( ) onthe toolbar. The Common Pack Service Selection Wizard opens. 2. Select List Common Packs from the list of commands. 3. Click Next. The List Common Packs Wizard opens. 4. On the Login page, browse to a logins file. 5. Click Next. The common packs in the repository are listed. Adding multiple CIF (.tnpmmodel) files to deploy You can add multiple common packs to the repository to create a combined model. You can load all CIF files found in the directory to the repository. Ensure that the combined model size is not more than 50 MB. Procedure 1. In Model Maker Manager, click File > Deploy. Or, click the Deploy ( opens as shown: ) button. The Common Pack Service Deploy Wizard 2. Click Add and select multiple CIF files from the local folder, and then click Open. The CIF files can be a combination as follows: Chapter 10. Installing common packs 65

76 v v v v v Raw and Busy Hour Raw and Summary Raw, Busy Hour and Summary Busy Hour and Summary CIF files from different technology packs Note: If the selected CIF files do not include the corresponding raw CIF file, you must set the dependent raw common packs that are deployed. To set the dependent raw common packs, select the CIF files, and click Config. 3. Enter the name for the combined model in the Symbolic Name field and the version in the Version field. 4. Click Finish. If the operation is successful, the wizard closes. If the operation fails, a message is displayed. The combined pack is deployed. What to do next To ensure that you see the packs on the system after you add the packs, always refresh your view by restarting Model Maker Manager. Deploying a common pack (Wireless only) You must deploy a common pack to the Tivoli Common Reporting server to make a report package available for reporting. Any data sources that are defined in the common pack are also made available in Tivoli Common Reporting. Before you begin Ensure that all Base Common Packs are added, activated. Ensure that the Manager Preferences page is configured completely. Procedure 1. Start Model Maker Manager. 2. Click File > Deploy. Or, click the Deploy ( Deploy Wizard opens: ) button on the toolbar. The Common Pack Service 66 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

77 3. In the Common Pack Service Deploy Wizard window, enter the required details and click Finish: Option Add Remove Config Symbolic Name Version Description Browse to select one or more CIF (.tnpmmodel) files that you created from the file system. Remove one or more rows from CIF Files list. Select the dependent packs that are required for the current deployment. Note: You must configure this only for common packs that contain summary definitions and busy hour definitions. Name of the common pack that is generated by the server. Note: This field accepts only characters in the range A-z, 0-9, "_", ".", "-".We recommend that you give the same name as the common pack that you selected to install on Tivoli Integrated Portal. If you selected multiple files, the symbolic name must be the name of the first CIF file in the "CIF Files (.tnpmmodel) Selection" area. Version of the common pack that is generated by the server. This field accepts only strings that represent major.minor.service numbers. These numbers must be positive integer numbers. Chapter 10. Installing common packs 67

78 Results The selected CIF (.tnpmmodel) files are compressed and deployed to the server. You can monitor the progress by observing the Progress Monitor bar in the Deploy Monitor window. Click Run in background to minimize the monitor window. If you click Cancel to cancel this operation for any reason, you might see Cancel Requested message on the screen, but the monitoring will continue with no consequences. This is a limitation. The common pack that is deployed to the server is automatically enabled for the Resource Metric Viewer at the end of the Deploy process. After the deploy operation is complete, click the Progress tab and then click the button as shown in the figure to download the log file: Or, you can see the logs in the <TIP_COMPONENTS_LOCATION>/TCRComponent/ commonpackservice/logs folder. You can view error or warning messages in the log file after the deploy operation is complete. You can also see if a pack is enabled for Resource Metric Viewer in the logs. 68 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

79 Uninstalling common packs To uninstall a common pack from the Tivoli Netcool Performance Manager system, you remove it by using Model Maker Manager or the pack_admin command. To remove a common pack from Model Maker Manager, you must currently uninstall and reinstall Manager. Removing common packs from the repository In Model Maker Manager, you remove a common pack from the common pack repository with the Remove Common Packs command. Before you begin You need a logins file for this procedure. If a logins file does not exist, you can create a logins file on the server by using the pack_admin command. Copy the file back to your Windows computer before starting this procedure. About this task To ensure that you only see the packs that are on the system after removing packs, always refresh your view by restarting Model Maker Manager. Procedure 1. In Model Maker Manager, click the Common Pack Service button ( ) onthe toolbar. The Common Pack Service Selection Wizard opens. 2. Select Remove Common Packs from the list of commands. 3. Click Next. The Remove Common Packs Wizard opens. 4. On the Login page, browse to a logins file. 5. Click Next. The Installed Common Packs page displays a list of installed packs. 6. Select a common pack to remove. 7. Click Finish to delete the pack from the repository. If the operation is successful, the wizard closes. If the operation fails, a message is displayed. Chapter 10. Installing common packs 69

80 70 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

81 Chapter 11. Resource Metric Viewer (Wireless only) 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 Only raw models work with the Resource Metric Viewer. The Resource Metric Viewer can process both simple and composite models. 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. 2011,

82 Resource Metric Viewer setup This section covers the basic tasks required to set up the Resource Metric Viewer. Installation of the Resource Metric Viewer is performed when installing the Common Pack Service. The Common Pack Service installation is covered in the section Running the installer on page 20. List packs The pack_admin -list command must be run once after installation of the Resource Metric Viewer. Procedure Run the pack_admin -list command as root user. For example: pack_admin.sh -list -packs -logins logins_file Note: For more information about the pack_admin.sh -list command, see pack_admin -list on page 132 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 WebGUI 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 may not be handled properly by the Resource Metric Viewer on page 106. Adding the Active Event List script Adding a menu script to start the Resource Metric Viewer UI from the Active Event List. Before you begin You must create a configuration script before you follow the steps in this procedure. A WebGUI menu script, AelLaunchScript.script, can be found in the directory <TIP_COMPONENTS_LOCATION>/TCRComponent/commonpackservice/rmv/scripts, for example, /opt/ibm/tivoli/tipv2components/tcrcomponent/commonpackservice/ rmv/scripts. Integration with systems other than WebGUI requires similar scripts. Contact IBM Services if integration with other IBM products is required. 72 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

83 Procedure 1. Log in to Tivoli Integrated Portal as the administrator. For example: 2. Click Administration > Event management Tools > Tool Creation. 3. Click Create Tool. 4. Enter the name for the script in the Name field. For example, RMV. 5. Select script in the type field. 6. Copy the contents of the configuration script into the Script Commands section 7. Under Access Criteria, move the Netcool_OMNIbus_Admin and Netcool_OMNIbus_User options into the Selected field. 8. Click Save. 9. Click Administration > Event management Tools > Menu Configuration. 10. Select alerts and click Modify. 11. Move the script that you created from the left side to the right and position it in your preferred location. 12. Click Save. 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 script as a selectable option in the menu. Using the Resource Metric Viewer The Resource Metric Viewer allows you to create dynamic reports. If you are using the deploy operation for a Cognos model, the model is automatically enabled for Resource Metric Viewer. About this task You can create dynamic reports by using the Resource Metric Viewer in two ways: v By selecting an event from the Active Event List, which will create a report based on the performance of the relevant entity. v By selecting a subset of resources and metrics available within a model. Chapter 11. Resource Metric Viewer (Wireless only) 73

84 Constructing a report by selecting a subset of resources and metrics By using the Resource Metric Viewer, you can create dynamic reports by filtering the resource and metric set available for a specific model and hierarchy. The Resource Metric Viewer automatically shows all the entities that are based on a specific hierarchy that is set by the user. Procedure 1. Log in to Tivoli Integrated Portal as the Resource Metric Viewer user. 2. Click Performance > Resource Metric Viewer Selection to open the Resource Metric Viewer tab in the Tivoli Integrated Portal. 3. Select a model from the Models list. 4. 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. 6. Select a parent entity from the Parent Entity list. Note: Skip this step if you do not need to filter by the Parent Entity. 7. Select a grand parent entity from the Grand Parent Entity list. Note: Skip this step if you do not need to filter by the Grand Parent Entity. Note: Focal entity is not retrieved if the selected hierarchy is wrong or there is no data on the parent and grand parent entities. Note: The inclusion of a Parent Entity or Grand Parent Entity selection is to allow filtering on the main entity 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 to filter all the Cells, which are part of that region. 74 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

85 8. Click Open in Tip or 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 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. 9. 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. Note: GrandParent Entity and Parent Entity are not be displayed if they are not selected in the 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. 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. c. 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 with mouse and click the Search button under Region. d. Select the resources that you require from the Results field and use the Insert and Remove buttons to set the final selection of resources. 10. 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. Chapter 11. Resource Metric Viewer (Wireless only) 75

86 The '%' symbol represents the wildcard plus any character string to construct the filter. Click Search to implement the filter. 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. 11. Set the granularity of the time series by using the Time Granularity list. 12. 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. 13. Set the display format of the output by using the Options section. By using the Options section, you can 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, andanother set might cover values By using the Options section, you can choose between Chart by entity (one entity per chart) and Chart by metric (one metric per chart). By using the Options section, you can 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. 14. Click Finish. You can view the report that is based on your selections. Results When you click the Run button from the Resource Metric Viewer report, you are redirected to the Resource Metric View Prompt Page. 76 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

87 Constructing a report by selecting an event in the Active Event List By using the Resource Metric Viewer, you can select an event in the Active Event List and create a report based on the performance of the relevant entity. Procedure 1. Log in to your event management system (for example, OMNIbus) that is in the same Tivoli Integrated Portal instance as your Tivoli Netcool Performance Manager user interface. 2. Select the Active Event List. This will display the list of detected anomalies. 3. Right-click on the event you would like to examine and select the name you assigned to the Resource Metric Viewer script within the Active Event List menu, for example, RMV. Note: When an RMV report is opened up from the AEL, you may see the following error:. This error may occur when opening the RMV report for the first time. The error is caused by Tivoli Integrated Portal launching the AEL event before the Resource Metric Viewer page is compiled and initialized. A reload of the page (open from AEL) will resolve this problem. The Resource Metric View AEL Prompt Page is displayed, which displays details of the entity you selected within the Active Event List. 4. Set the granularity of the time series by using the Time Granularity list. 5. Set the time frame of the report by using the Date Range list, or select a date range by using the From and To calendar fields. 6. Set the display format of the output by using the Options section. In the Options section, among other things, you can choose between a Linear and Logarithmic chart. The Logarithmic option must be chosen if you are plotting metric sets that contain massively disparate values; for example, one metric set might cover values 0-1,andanother set might cover values Click Finish. Chapter 11. Resource Metric Viewer (Wireless only) 77

88 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 <TIP_COMPONENTS_LOCATION>/ TCRComponent/commonpackservice/rmv/templates Where <TIP_COMPONENTS_LOCATION> is the location where the Tivoli Integrated Portal components are installed. By default, for the wireless component this is: /opt/ibm/tivoli/tipv2components. 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. Navigate to <TIP_COMPONENTS_LOCATION>/TCRComponent/commonpackservice/ rmv/templates. 2. Open and update the existing template. 3. Make sure to update the model path by editing the following XML: v <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, the name of the Active Event List template must be ael_template.xml 5. To update RMV reports, run the following command: pack_admin.sh -rmv -update_reports [ -pack pack_filename -all ] -logins password_file For example:./pack_admin.sh -rmv -update_reports -pack <pack_filename> -logins../conf/logins You can run the pack_admin.sh -rmv command for all packs by using the -all flag. 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 or Activate Event List template in report studio and save under a new name. 2. Update the report. 3. Using Tools > Show Specifications copy XML into new file. 78 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

89 4. Modify <modelpath> file to the following: 5. Replace report in <TIP_COMPONENTS_LOCATION>/TCRComponent/ commonpackservice/rmv/templates with updated report template. 6. To update Resource Metric Viewer reports, run the following command: pack_admin.sh -rmv -update_reports [ -pack pack_filename -all ] -logins password_file For example:./pack_admin.sh -rmv -update_reports -pack <pack_filename> -logins../conf/logins You can run the pack_admin.sh -rmv command for all packs by using the -all flag. Note: For more information on the pack_admin.sh -rmv command, see pack_admin -rmv on page 137. Chapter 11. Resource Metric Viewer (Wireless only) 79

90 80 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

91 Chapter 12. Data availability reporting Data availability or data coverage describes the completeness of data for a report. Summaries are executed every day that is 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. Customers 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 customer 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 pack are identified, you must create a data availability Cognos model that contains these summaries and install the Cognos model on Tivoli Integrated Portal. 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 with the Common Pack Service, Model Maker Manager, and Model Maker Extractor installed. v Ensure that you grant permission to the tcraccess user by running the da_grant.ksh script that is available with the Tivoli Netcool Performance Manager Wireless software. This script runs the following commands: sqlplus virtuo/<password>@vtdb grant execute on calc_table_hourly_da to tcraccess; grant select on da_hourly_tmp to tcraccess; Procedure 1. Monitoring the key traffic tables for data availability on page 82 a. Selecting tables for data availability for a vendor neutral technology pack on page 84 b. Selecting tables for data availability for a vendor specific technology pack on page Generating data availability components on page 86 Copyright IBM Corp. 2011,

92 3. Provisioning the UDCs and summaries to Tivoli Netcool Performance Manager Wireless system on page Extracting and deploying daily summary model on page Downloading the data availability 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 96 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 v 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 84 and Selecting tables for data availability for a vendor specific technology pack on page 84. 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. 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 82 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

93 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 12. Data availability reporting 83

94 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: 84 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

95 v v The vendor neutral table. Typically, these tables are named as VNL_. 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 v Identify the vendor specific tables that are also loaded from the same block. This is to limit the number of tables to monitor. 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 12. Data availability reporting 85

96 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 You configured the JDBC driver in Model Maker Extractor preferences so that you can connect to the database to extract the summary definitions. v 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 84. v You created the common pack that contains a raw model as described in Creating a common pack containing a raw data model on page 49. Procedure 1. In Model Maker Extractor, 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. Click Next. 6. Select File System and locate the output directory where you want to generate the user-defined calculations (UDCs) and summary XML files. 7. 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 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

97 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 the UDCs at the appropriate resource type level. The 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. <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> Chapter 12. Data availability reporting 87

98 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. 88 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

99 <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 12. Data availability reporting 89

100 v <server_name>.ibm.com For more information about the kpicache_admin script, see IBM Tivoli Netcool Performance Manager: Administration Guide - Wireless Component. 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 IBM Tivoli Netcool Performance Manager: Administration Guide - Wireless Component. Extracting and deploying 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 common pack 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 Model Maker Extractor preferences so that you can connect to the database to extract the summary definitions. Procedure 1. In Model Maker Extractor, 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. 90 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

101 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. Optional: By default, summaries for all intervals are selected. Select the appropriate check box to filter the selected summaries by raw, hourly, daily, weekly, or monthly intervals. Clear the All summaries check box to clear your previous selection. 12. Select the Update Viewer check box to update the view on the Select Summaries page. That is, if you select individual options such as Raw, Hourly from Select Summaries area, then it displays those individual summaries. 13. Click Next. A CIF file with summary model is generated. 14. Deploy the summary model CIF (.tnpmmodel file) by using Model Maker Manager. 15. If a data availability model, select the summary model CIF first, and then click Config to select the dependent raw model CIF. For more information about deploy operation, see Deploying a common pack (Wireless only) on page 66. Note: You cannot select multiple CIF files as described in Adding multiple CIF (.tnpmmodel) files to deploy on page 65 to generate the data availability reports. Chapter 12. Data availability reporting 91

102 Results 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. Downloading the data availability model After the data availability model is deployed, download the common pack model from the Common Pack Service to your local instance of the Model Maker Manager. You will find the raw and the data availability models that you created in the Model Maker Manager/plugins directory. Procedure 1. Select Help > Install New Software. 2. Select a site or enter the location of a site. 3. Select the data availability model to download. When you select the data availability model, the dependent packs are automatically downloaded. 4. Click Next. The downloaded common packs are listed in the Common Pack Models pane and are available in the local Model Maker Manager instance. 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. However, the vendor_cleanup.ksh must remain in the script to filter the data availability result to a specific vendor and technology. 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 92 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

103 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. #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 # Need to call the vendor_cleanup for EACH summary. # Parameters: # 1. Do not filter for vendor neutral data coverage summary tables # 2. The vendor you want to KEEP. All other vendors entities will be removed # 3. The name of the DSM table # 4. The identifier field that is being removed # 5. The nc table to use # e.g: /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Huawei Gb_DA gb_id nc_gb /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Huawei GSM BSC_DA_HUAWEI_DSM BSC_ID nc_bsc /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM BSC_DA_DSM BSC_ID nc_bsc /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM Cell_DA_DSM CELL_ID nc_cell /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM Ethernet_link_mo_DA_DSM ETHERNET_LINK_ID nc_ethernet_link_mo /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM Gb_DA_DSM GB_ID nc_gb /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM LAPD_DA_DSM LAPD_ID nc_lapd /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM PCU_DA_DSM PCU_ID nc_pcu /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM Processor_DA_DSM Processor_ID nc_processor /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM GSM Signalling_Link_DA_DSM ss7_point_id nc_ss7_point /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Motorola GSM X25_DA_DSM X25_ID nc_x25 /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Huawei GSM M3UA_link_utilisation_DA_DSM M3UA_LINK_ID nc_m3ua_link /appl/virtuo/admin/common/cron/vendor_cleanup.ksh Huawei GSM SCTP_Link_DA_DSM SCTP_LINK_ID nc_sctp_link echo `date` Chapter 12. Data availability reporting 93

104 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 six data availability reports based on the data availability model that is created. Before you begin Ensure that you have installed all the latest fix packs. For more information about the stored procedure, see the readme file that comes with the Interim Feature. Procedure 1. In Model Maker Extractor, open the tnpmmodel file that you have created from the data availability model. 2. Right-click TNPM Package > 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 User(bicontrol) Password Manager Plugins Dir The bicontrol user password The plugins directory in Model Maker Manager installation directory. By default, Manager\plugins 4. Click Get Model Details. 5. Click Next. 94 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

105 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.bss.da Provisioned entities to be selected from the list. This entity is the main entity from which you want to view metrics. Parent entity for the selected focal entity. 7. Click Generate Reports. After the data availability reports are generated, you can see the path in the local instance of Model Maker Manager. The location is as follows: Manager/plugins/tmp/<nokia.gsm.bss.DA> These reports are a set of six XML files. For nokia.gsm.bss.da model with BSC and LAPD as selected parent and focal entities, the six reports are as follows: v Nokia_GSM_FOSI_Channel_Region_HDA: An hourly report for focal entity v Nokia_GSM_FOSI_Channel_Region_DDA: A daily report for focal entity v Nokia_GSM_FOSI_Channel_Region_TABLE_HDA: An hourly report for table v Nokia_GSM_FOSI_Channel_Region_TABLE_DDA: A daily report for table v Nokia_GSM_PRegion_OSI_Channel_HDA: An hourly report for parent entity v Nokia_GSM_PRegion_OSI_Channel_DDA: A daily report for parent entity Note: The format of the XML file is as follows: <Vendor>_<Technology>_<P/F><entity_name>_<H/D>DA Where: P indicates parent entity F indicates focal entity H indicates hourly D indicates daily Publishing the generated data availability reports Publish the data availability reports to Tivoli Integrated Portal. Procedure 1. Start Model Maker Manager. 2. Click File > Common Pack Service Or, click the Common Pack Service ( ) button on the toolbar. 3. In the Common Pack Service page, select Publish Data Availability Reports from a Directory. Publishes all the data availability reports that are available in the Manager/plugins/tmp/<Pack_DA_Model> directory. 4. Optional: In the Common Pack Service page, select Publish Data Availability Reports. 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 Manager/plugins/tmp/<Pack_DA_Model> directory. 5. Click Next. Chapter 12. Data availability reporting 95

106 6. On the Login page, browse to the logins file. 7. Click Next. 8. On the Add Data Availability Reports page, click Browse and select the directory where the Data Availability reports are generated. For example, Manager/plugins/tmp/<nokia.gsm.bss.DA>. You can see the reports in the text area that are to be published. 9. Type the name of the directory in the text field to publish the reports on the Tivoli Integrated Portal. Typically, specify the name of the common pack model as the directory name. For example, Osi_channel_DA_Reports. In common reporting section of Tivoli Integrated Portal, a folder named Osi_channel_DA_Reports that contains the Data Availability reports is created in the following path: Public Folders/Data Availability/Contents/ 10. Click Finish. Verifying the data availability report contents View the published data availability reports from Tivoli Integrated Portal. Procedure 1. Log in to Tivoli Integrated Portal as the Tivoli Integrated Portal administration user, tipadmin. 2. Expand Reporting and select the Common Reporting tab. 3. Click Public Folders > Data Availability > Contents > <Osi_channel_DA_Reports>. You can see the six data availability reports that are published. 4. Double-click each report to view. 96 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

107 Creating data availability summary report This is a one-time task. About this task For more information about this task, see model_maker_1_2_3_tnpm_1_3_2_creating_the_summary_report_on_data_availability_da?lang=en Chapter 12. Data availability reporting 97

108 98 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

109 Chapter 13. Troubleshooting Model Maker and Common Reporting When you encounter a problem with using Model Maker 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. Known issues are documented in the Known issues with Tivoli Netcool Performance Manager technote in the Support knowledge base. You can also check the following links in the Tivoli Common Reporting documentation for known issues with Tivoli Common Reporting and IBM Cognos: v v com.ibm.tivoli.tcr.doc_21/ctcr_troubleshooting.html com.ibm.tivoli.tcr_cog.doc/ctcr_cog_knownlimitations.html Data modeling and Model Maker issues Read the following known issues if you are experiencing problems when creating, updating, or installing Tivoli Netcool Performance Manager common packs. Error while uninstalling Common Pack Service Symptoms When you try to uninstall the Common Pack Service, you might see the following error message: Copyright IBM Corp. 2011,

110 java.lang.unsupportedclassversionerror: Bad version number in.class file at java.lang.classloader.defineclass1(native Method) at java.lang.classloader.defineclass(classloader.java:621) at java.security.secureclassloader.defineclass(secureclassloader.java:124) at java.net.urlclassloader.defineclass(urlclassloader.java:260) at java.net.urlclassloader.access$100(urlclassloader.java:56) at java.net.urlclassloader$1.run(urlclassloader.java:195) at java.security.accesscontroller.doprivileged(native Method) at java.net.urlclassloader.findclass(urlclassloader.java:188) at java.lang.classloader.loadclass(classloader.java:307) at java.lang.classloader.loadclass(classloader.java:252) at com.ibm.tivoli.tnpm.biservice.install.oracle.getdriver(oracle.java:68) at com.ibm.tivoli.tnpm.biservice.install.database.getconnection(database.java:144) at com.ibm.tivoli.tnpm.biservice.install.database.isvalidconnectioninfo(database.java:158) at com.ibm.tivoli.tnpm.biservice.install.action.installbiserviceaction. checkoracle(installbiserviceaction.java:681) at com.ibm.tivoli.tnpm.biservice.install.action.installbiserviceaction. uninstall(installbiserviceaction.java:149) at com.zerog.ia.installer.actions.customaction.j(dashoa10*..) at com.zerog.ia.installer.actions.customaction.uninstall(dashoa10*..) at ZeroGbw.a(DashoA10*..) at com.zerog.ia.installer.actions.executeuninstallaction.a(dashoa10*..) at com.zerog.ia.installer.actions.executeuninstallaction.b(dashoa10*..) at com.zerog.ia.installer.actions.executeuninstallaction.a(dashoa10*..) at com.zerog.ia.installer.uninstaller.b(dashoa10*..) at com.zerog.ia.installer.uninstaller.b(dashoa10*..) at com.zerog.ia.installer.uninstaller.a(dashoa10*..) at com.zerog.ia.installer.consoles.uninstallprogressactionconsoleui. executeconsoleaction(dashoa10*..) at com.zerog.ia.installer.consolebasedaamgr.b(dashoa10*..) at com.zerog.ia.installer.consolebasedaamgr.a(dashoa10*..) at com.zerog.ia.installer.aamgrbase.e(dashoa10*..) at com.zerog.ia.installer.aamgrbase.n(dashoa10*..) at com.zerog.ia.installer.consolebasedaamgr.a(dashoa10*..) at com.zerog.ia.installer.aamgrbase.m(dashoa10*..) at com.zerog.ia.installer.lifecyclemanager.b(dashoa10*..) at com.zerog.ia.installer.lifecyclemanager.a(dashoa10*..) at com.zerog.ia.installer.main.main(dashoa10*..) at sun.reflect.nativemethodaccessorimpl.invoke0(native Method) at sun.reflect.nativemethodaccessorimpl.invoke(nativemethodaccessorimpl.java:39) at sun.reflect.delegatingmethodaccessorimpl.invoke(delegatingmethodaccessorimpl.java:25) at java.lang.reflect.method.invoke(method.java:592) at com.zerog.lax.lax.launch(dashoa10*..) at com.zerog.lax.lax.main(dashoa10*..) Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX) Resolving the problem To resolve this problem, run the following commands: On AIX and Solaris machines: 1. bash export PATH=/usr/ibm/common/acsi/jre/bin:$PATH (To set java JRE path) 2. Run the Uninstaller script by entering the command:./commonpackservice/uninstall/uninstall On Linux machines: 1. PATH=/usr/ibm/common/acsi/jre/bin:$PATH //(To set java jre path) 2. Run the uninstall script by entering the command:./commonpackservice/uninstall/uninstall Always use the HTTP protocol for the update site Always use the HTTP protocol for the update site as the Eclipse update Manager does not perform effectively with the HTTPS protocol. 100 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

111 Symptoms You get an error during a common pack download or update. Diagnosing the problem User response: Check for the following issues: v Check that you are using and not for the update site. v Check that you are using the correct port number for the protocol. Resolving the problem Ensure that you are using and not and the correct port number for the update site. Slow download of common packs Symptoms When downloading common packs by using the Help > Install New Software option, an error similar to the following is displayed: Unable to read repository at You can directly access the common service site mentioned, but it is slow to respond. Resolving the problem User response: If you encounter this problem: 1. Navigate to the /<tip_install_dir>/products/tcr/bin/ directory. By default, /opt/ibm/tivoli/tip21components/tcrcomponent/bin. 2. Restart Tivoli Common Reporting by running the following scripts: v stoptcrserver.sh <username> <password> v starttcrserver.sh CTGTRR1104E Cannot open an administrative database connection pack_admin commands fails with an error. Symptoms When using the pack_admin commands, you see an error like the following error: CTGTRR1104E Cannot open an administrative database connection. Check the database details and connectivity and try again. Causes This issue can caused by an unresponsive Tivoli Common Reporting installation. Diagnosing the problem Try to log in to Tivoli Common Reporting to see if the Tivoli Common Reporting home page loads in your browser. If the home page fails to load, then Tivoli Common Reporting is unresponsive. Resolving the problem Restart the Tivoli Common Reporting server by going to the$tip_components_location/tcrcomponent/bin directory and entering the commands:./stoptcrserver.sh <username> <password> Chapter 13. Troubleshooting Model Maker and Common Reporting 101

112 ./starttcrserver.sh Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default /opt/ibm/tivoli/tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. Updating earlier pre-ga common packs Due to known issues in Eclipse, earlier IBM generated common packs specified exact versions of their dependent packs, whereas current common packs specify a version range. Some common packs need to be updated to make them compliant with the latest versions of common packs and the GA version of the Common Pack Service, which accepts a version range. About this task There are two ways of specifying the version information of dependent packs in a common pack: v v A simple version string the common pack will only install if that exact version of the dependent common pack is installed. For example, the version set to means that this common pack requires version of the dependent pack. A version range The common pack will install if the version of the dependent common pack that is installed is in a defined range. The minimum version is set to the minimum required level, such as 1.0.1, while the maximum version is set to a very large constant value meaning that the maximum value is not important, allowing for updates. The following procedure shows how to update all dependent common pack references from exact versions to a version range, and how to recreate the pack. Procedure 1. Extract the common pack jar file to a folder of your choice. 2. Open the bipack.xml file in any text editor. 3. Change each instance of the <version> markup to the <version-range> markup. For example, change <pack> <pack-symbolic-name>ibm.tcr.time</pack-symbolic-name> <version>1.0.1</version> </pack> to <pack> <pack-symbolic-name>ibm.tcr.time</pack-symbolic-name> <version-range> <min-version>1.0.1</min-version> <include-min>true</include-min> <max-version> </max-version> <include-max>false</include-max> </version-range> </pack> 4. Save the bipack.xml file. 5. Recreate the common pack by using Model Maker Manager. Resolving Cognos connection errors You might encounter messages like the following messages when using or creating an Oracle connection from Tivoli Common Reporting or within Framework Manager. 102 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

113 Symptoms In a Windows Environment: QE-DEF-0285 Logon failure. QE-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: testdatasourceconnection UDA-SQL-0432 Unable to locate the gateway "cogudaor". In a UNIX environment: QE-DEF-0285 Logon failure. QE-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: testdatasourceconnection UDA-SQL-0432 Unable to locate the gateway "libcogudaor" Causes Incomplete configuration of the Oracle client. Resolving the problem Ensure that you have configured your Oracle library environment variable correctly, as described in the topic Configuring Tivoli Common Reporting for Oracle connections on page 11. If that does not solve the problem, see the following IBM technote for further troubleshooting steps, docview.wss?uid=swg Resolving Cognos connection errors on Windows 7 environment When using or creating an Oracle connection from Tivoli Common Reporting or within Framework Manager, you might encounter messages like the following messages: Symptoms QE-DEF-0285 Logon failure. QE-DEF-0325 logon fialed for the following reason: RQP-DEF-0068 Unable to connect to atleast one database during a multi-database attach to 1 database(s) in: tcraccess UDA-SQL-0031 Unable to access the "tcraccess" database. UDA-SQL-0107 A general exception has occured during the operation attach. Causes You will encounter these errors if you install Oracle Client 10g on Windows 7. Resolving the problem User response: To resolve this issue, install Oracle Client 11g for Microsoft Windows (32-bit) on your Windows 7 environment. Supporting help buttons in Model Maker Extractor Model Maker Extractor is based on Eclipse and supports most, but not all, of the default Eclipse functionality visible in the user interface. In this release, the default Eclipse help buttons found at the lower left of wizard pages are not supported. Chapter 13. Troubleshooting Model Maker and Common Reporting 103

114 HTML pack documentation is slow to open in Internet Explorer Issue when opening pack documentation provide in HTML format in Internet Explorer. Symptoms The following error is displayed: Stop running this script? A script on this page is causing Internet Explorer to run-slowly. If it continues to run, your computer might become unresponsive. Causes The error occurs because the files can contain many resources. Resolving the problem You can ignore the error and continue. The HTML document will open after a period of time. (Wireless) Combining models might hang on "Creating new Framework Manager project" Model Maker Manager can sometimes hang when combining models. Symptoms When using the Combine Models option, Model Maker Manager hangs on the Creating new Framework Manager project step. Causes This issue is caused by an unresponsive Tivoli Common Reporting Version 2.1 installation. The Framework Manager BmtScriptPlayer attempts to communicate with Tivoli Common Reporting through the BmtScriptPlayer.exe -c projectpath command, which hangs when it receives no response. Environment The Model Maker Manager and a server running Tivoli Common Reporting Version 2.1. Diagnosing the problem Try to log in to Tivoli Common Reporting to see if the Tivoli Common Reporting home page loads in your browser. If the home page fails to load, then Tivoli Common Reporting is unresponsive. Resolving the problem Restart the Tivoli Common Reporting server by going to the$tip_components_location/tcrcomponent/bin directory and entering the commands:./stoptcrserver.sh server1 -user <username> -password <password>./starttcrserver.sh server1 -user <username> -password <password> Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default /opt/ibm/tivoli/tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. 104 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

115 (Wireless) Missing formulae in metrics groups after generating the CIF file There are missing formulae in the metrics groups after generating the Common Intermediate Format (CIF) file using the expanded folder option for GSM and UMTS technology packs. (Wireless) Do not use special characters in the model name when creating Summary and Busy Hour models In Model Maker Extractor, do not use special characters when entering a name for the model on the Model Details page of the Import Summaries or Import Busy Hours wizards. (Wireline) Issue when extending a model by using the pm.inventory.getresources DAL query If you create or modify a data source with the pm.inventory.getresources DAL query and want to import this data source into Framework Manager, you need to manually modify the data source to avoid an error. Symptoms If you do not manually modify the data source, the database objects cannot be created in Framework Manager when importing the modified data sources. An error like the following error is displayed: RQP-DEF-0177 An error occurred when performing operation sqlscrollbulkfetch status UDA-SQL-0528 The XML parser returned the following message: An exception occurred!...could not open file: Causes The??group?? parameter cannot be understood when obtaining database information needed to create the model objects. Environment This issue applies if you are adding a custom model extension to a wireline data model that retrieves Resource Attributes (Properties) by using the pm.inventory.getresources DAL query. Resolving the problem When creating the model objects, create or modify data sources for loading into Framework Manager to create the database objects. The new or modified data sources must be manually configured in Tivoli Common Reporting to change the group ID to a static group ID instead of the default??group?? parameter. User response: 1. Log on to Tivoli Integrated Portal. 2. Expand Reporting > Common Reporting. 3. On the toolbar, click Launch > Administration. 4. Navigate to the Configuration tab and click Data source Connection. 5. Left-click on a data source and click the Set Properties button. 6. In the Set Properties window, navigate to the Connection tab and click the edit the connection string icon to configure the data source. 7. Locate??group?? in the connection string and change the group to '+dq(prompt('enter%20group%20id','integer','<group id>'))+' Chapter 13. Troubleshooting Model Maker and Common Reporting 105

116 Where <group id> is the path to the NOC Reporting group where list of resources are grouped. Example The default data source installed in Tivoli Common Reporting is: +CAMPassport()+ &query= {call%20pm.inventory.getresources("??group??",[??resources??], ["location","ipdevice"],??endtime??)} # This data source has had the group ID changed so that the data source can be loaded in Framework Manager to create new database objects: +CAMPassport()+ &query= {call%20pm.inventory.getresources( +dq(prompt( enter%20group %20id, integer, ))+, [??resources??],["location","ipdevice"],??endtime??)} # Label alarms that may not be handled properly by the Resource Metric Viewer As part of setup for the Resource Metric Viewer it is recommended that you label those alarms that may not display properly in the Resource Metric Viewer. About this task If you have a model with both RNC and BSC in it, and there are RNC or BSC alarms defined, and those alarms are forwarded to OMNIbus, perform the following step: Procedure Add to the RNC/BSC alarm Description "Do not open this in RMV from AEL". Where: v RMV is the Resource Metric Viewer. v AEL is the Active Event List. Note: For information on how to change the description of an alarm, see the section "Update an Alarm Definition" in chapter 14 of the IBM Tivoli Netcool Performance Manager: User Guide - Wireless When you deploy a common pack on Tivoli Integrated Portal, the common pack is not installed Sometimes, you might not be able to deploy a common pack on Tivoli Integrated Portal successfully. Symptoms After you deploy the common pack as described in the section Deploying a common pack (Wireless only) on page 66, sometimes a common pack might not be deployed successfully on Tivoli Integrated Portal. This is an intermittent issue. In the deployment logs, you might see the following errors: Sep 13, :21:24 AM INFO : Publishing Package glengarriff8.usa.huawei.lte.mme.raw.non.rdm.test in project /var/tmp/glengarriff8.usa.huawei.lte.mme.raw.non.rdm.test/model/glengarriff8.usa. huawei.lte.mme.raw.non.rdm.test.cpf Sep 13, :21:25 AM INFO : Executing command: "/opt/ibm/tivoli/tipv2components/tcrcomponent/cognos/bin/bmtscriptplayer" -m "/var/tmp/glengarriff8.usa.huawei.lte.mme.raw.non.rdm.test/model/glengarriff8.usa. huawei.lte.mme.raw.non.rdm.test.cpf" -a "/tmp/cognos /actionlog xml" -u 106 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

117 "tipadmin" -p "tipadmin" -s "VMMProvider" Sep 13, :21:26 AM INFO : BmtScriptPlayer output: An existing project is being opened. /var/tmp/glengarriff8.usa.huawei.lte.mme.raw.non.rdm.test/model/glengarriff8.usa. huawei.lte.mme.raw.non.rdm.test.cpf BME-SP-0012 Unable to open a model document. Check messages to determine which errors occurred. Sep 13, :21:27 AM INFO : [JOB f37afe24-be6e-453c-baf9-fd7ed36d9281]: LIMBS@GenerateAndDeployTask end publishmodel... Sep 13, :21:27 AM INFO : [JOB f37afe24-be6e-453c-baf9-fd7ed36d9281]: LIMBS@END PUBLISH COMMON PACK... Sep 13, :21:27 AM INFO : [JOB f37afe24-be6e-453c-baf9-fd7ed36d9281]: Publishing completed Sep 13, :21:27 AM INFO : [JOB f37afe24-be6e-453c-baf9-fd7ed36d9281]: Job completed Causes This issue might arise when the server resources are running slow. Resolving the problem When you complete the deploy operation, the common pack is added and activated on the server. To resolve this issue, manually install the common pack by using Model Maker Manager. To do this, follow these steps: User response: 1. In Model Maker Manager, click Help > Install New Software. 2. Select the common pack and install. 3. Publish the installed common pack. For more information about publishing a common pack, see topic/com.ibm.tnpm.doc/modmaker/ttnpm_mm_publish_packs.html The common pack is now listed under Common Reporting in Tivoli Integrated Portal. The WIRELESS_HOST parameter does not reflect correctly in the global.properties file Symptoms When Tivoli Common Reporting and the administrative database are set up on different servers, WIRELESS_HOST parameter does not reflect correctly in the global.properties file. When you are running the installer, you will be prompted for administrative database only. If you enter the VTDB host name or host IP address, it does not reflect correctly in the global.properties file. You no longer receive the prompt for target database. Resolving the problem To resolve this issue, follow these steps as root user: 1. Copy the global.properties file to a temporary directory for backup by using the following command: cp <TIP_LOCATION>/profiles/TIPProfile/installedApps/TIPCell/isc.ear/ bi-pack-service.war/global.properties /tmp/global.properties where <TIP_LOCATION> is the Tivoli Integrated Portal installation directory. By default, /opt/ibm/tivoli/tipv2 for wireless and /opt/ibm/tivoli/tip21 for wireline. 2. Copy the biservice.properties file to a temporary directory for backup by using the following command: Chapter 13. Troubleshooting Model Maker and Common Reporting 107

118 cp <TIP_LOCATION>/profiles/TIPProfile/installedApps/TIPCell/isc.ear/ bi-pack-service.war/biservice.properties /tmp/biservice.properties 3. Update the backup copy of the global.properties file as follows: TCR_HOST=<TCR host IP address> WIRELESS_HOST=<IP address of the host where VTDB database is located> 4. Run the following command to restart the Common Pack Service: <TIP_COMPONENTS_LOCATION>/TCRComponent/commonpackservice/bin/install.sh <TIP_LOCATION> tipadmin tipadmin_password /ibm/commonservice <Database_client_directory> bicontrol bicontrol_password By default, the <Database_client_directory> isopt/oracle/product/11.2.0/db_1 for Oracle 11g. For example: /opt/ibm/tivoli/tipv2components/tcrcomponent/commonpackservice/bin/install.sh /opt/ibm/tivoli/tipv2 tipadmin tipadmin /ibm/commonservice /opt/oracle/product/11.2.0/db_1 bicontrol bicontrol 5. Copy the global.properties and the biservice.properties files from the temporary directory to their original location by using the following commands: cp /tmp/global.properties <TIP_LOCATION>/profiles/TIPProfile/installedApps/TIPCell/ isc.ear/bi-pack-service.war/global.properties cp /tmp/biservice.properties <TIP_LOCATION>/profiles/TIPProfile/installedApps/TIPCell/ isc.ear/bi-pack-service.war/biservice.properties 6. Restart the Tivoli Common Reporting server by entering the following commands: $<TIP_COMPONENTS_LOCATION>/TCRComponent/bin/stopTCRserver.sh tipadmin tipadmin_password $<TIP_COMPONENTS_LOCATION>/TCRComponent/bin/startTCRserver.sh tipadmin tipadmin_password where <TIP_COMPONENTS_LOCATION> is the location where the Tivoli Integrated Portal Components are installed. By default, /opt/ibm/tivoli/ tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. For more information about running the Common Pack Service installer, see Running the installer on page 20. SQL query string length for monitoring the tables for hourly data availability must be limited to 4000 characters Symptoms If the number of tables for a particular focal entity is very high and the SQL query string that retrieves the tables for monitoring the data availability exceeds 4000 characters, the query may fail. The following error message is displayed: ORA-01704: string literal too long "string literal too long" 108 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

119 *Cause: The string literal is longer than 4000 characters. *Action: Use a string literal of at most 4000 characters. Longer values may only be entered using bind variables. Error at Line: 3 Column: 28 Resolving the problem Ensure that the SQL string length that retrieves the tables for a focal entity does not exceed 4000 characters or 100 tables. This is an Oracle limitation. Use either deploy or publish method for both raw and summary models for data availability report generation You cannot use both publish and deploy methods for raw and summary packs while generating data availability reports. Symptoms If you use both deploy and publish methods for a summary pack and the dependent raw pack, entities in the selection list for data availability report generation does not include vendor specific entities. Only vendor neutral entities appear. Note: The publish method is replaced with deploy method in Model Maker v1.2.1 onwards as a part of usability enhancements. Causes When you deploy a raw common pack, the input is a CIF file that is sent to the server. When you try to publish the summary pack, the summary pack is unable to find the dependent raw CIF in the CIF directory. Resolving the problem You must use either deploy or publish for both raw and summary packs. For example, you cannot use publish method on raw model and deploy method on summary model for data availability report generation. To know whether you have used deploy or publish for a pack: v Check whether the raw CIF file exists in the CIF directory then deploy method is used. The CIF directory is: <commonpackservice_installation_directory>/commonpackservice/cifs/users. You can also check this from the log file that is generated after the deploy process. v After the deploy operation is complete, click the Progress tab, and then click the button as shown in the figure to download the log file: Chapter 13. Troubleshooting Model Maker and Common Reporting 109

120 You may see warning messages as shown if both deploy and publish methods are used for the summary pack and its dependent pack models: Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : Interface_Pool Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : ARP Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : BSC_PW Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : TRU_Equipment Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : SONET_SDH Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : STM1 Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : BSC_Ethernet_Port Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : Radio_Relay Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : Cell_Connection_Type Dec 21, :20:06 PM WARNING : The following resource will not be modelled as no definitions were found in the CIF directory : Cell_TRX_Type Issues when you have multiple technology pack data availability models deployed on the server Symptoms Consider the following scenarios: You have multiple technology packs with the same vendor and same technology Issue: For a common entity that is shared by both the technology packs, if the same physical entity is named differently in both technology packs, the results are monitored as two separate instances for the same physical entity. The data availability for vendor specific hourly and daily tables might be incorrect as summary for the vendor specific traffic tables in both 110 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

121 technology packs include both instances. You cannot filter out the instances since they have the same vendor and same technology. Daily and hourly entities would be correct except that the instance from the other technology pack is listed although it is not relevant and it would give a data availability of zero. Additionally, due to the default naming convention, the data availability summary ( Data availability summaries on page 88), resource type data availability formula and count metric ( Data availability formulas on page 87) for a common entity in both technology packs will have the same name. One of the two sets of data availability summary name, resource type data availability formula and count metric name must be modified so that they are unique before they are provisioned to the Tivoli Netcool Performance Manager Wireless system. For example: Components Original name Change to Summary name DA_Nokia_GSM_CELL DA_Nokia_GSM_NSS_CELL (da_summary.xml) Resource type data availability formula name (da_udcs.xml) DA_Nokia_GSM_CELL DA_Nokia_GSM_NSS_CELL Count metric name (da_udcs.xml) DA_Nokia_GSM_CELL_Count DA_Nokia_GSM_CELL_NSS_Count Note: "DA_ must precede all the components and the count metric name must end with _Count. You have multiple loadmaps for a vendor neutral technology pack Issue: For example, you have two loadmaps for vendor A and B. If both instances only either of vendor A and B instances is available in the selected vendor neutral traffic table, then the data availability in hourly and daily table might be incorrect since the summary for the vendor neutral traffic tables include both instances. The data availability for hourly and daily entities are incorrect because the average might include the instance that is not populating in the table. Note: You might notice these issues for vendor neutral tables and entities also. 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: Chapter 13. Troubleshooting Model Maker and Common Reporting 111

122 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 86. Rollup report cannot be generated if there is missing information for the entities in the hierarchy selection You cannot generate a rollup report if there is incomplete information for the entities in the hierarchy selection from the dependent BCP. Symptoms There has to be a defined hierarchy for all entities in a dependent BCP. If any of the intermediate level entities do not have data, the report cannot be rolled up. For example, if the entity hierarchy is like this:cell ->BTS ->BCS and if any of the following conditions are true: v There is no data on BTS. v BTS has data but does not have mapping to its defined parent. In this situation, you cannot generate a rollup report. Causes This is a BCP design and implementation limitation. Resolving the problem 112 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

123 Ensure that the hierarchical information is present for all entities in a dependent BCP. Unlock the bicontrol user manually Symptoms When you use a wrong bicontrol user password, the user might be locked after a certain number of consecutive failed login attempts and you cannot access the database. Reporting issues Resolving the problem Contact your DBA to unlock the user. Read the following known issues if you are experiencing problems with Common Reporting on Tivoli Netcool Performance Manager. Intermittent problems logging on to Tivoli Common Reporting You can experience problems intermittently when logging in to Tivoli Common Reporting. Symptoms You get a message like this message: The user or password you provided is not valid. Provide valid credentials. Causes This is a known issue in Tivoli Common Reporting. Resolving the problem If you are sure that you have the correct credentials, restart the browser. If that does not work, clear the cache and try again. Logging in when your session times out This is a known problem with logins on Tivoli Common Reporting. Symptoms If your login session times out, you get a message requesting you to log in again. If you click Logout and try to log in again, the login fails. Resolving the problem Close the browser and open a new browser session before logging in again. Problems running reports if you have logged in to multiple sessions Multiple login sessions to Tivoli Common Reporting are not supported. Symptoms You cannot run reports if you have previously logged in to another Tivoli Common Reporting environment within the same browser session. Causes The issue is a known issue and is documented in the following IBM support technote: Chapter 13. Troubleshooting Model Maker and Common Reporting 113

124 Page number is not shown at the bottom of a HTML report In HTML reports pages are not counted and the final page number shows as a question mark (?). Symptoms The final page number shows as a question mark (?). Causes When Report Studio renders a page as HTML, it renders each page only when required. This makes a HTML report quicker to render than a PDF report. However, this means that the pages are not counted and that the final page number shows as a question mark (?). Resolving the problem To see the number of pages in your report, you have two options: v v In an HTML report, go to each page sequentially; the total number of pages is then shown. Render the report in PDF. The complete dataset always renders for the PDF option, and the total number of pages shown. Problems with Report Studio in Internet Explorer 8 If you have problems opening Report Studio in Internet Explorer 8, refer to the following Tivoli Common Reporting known issue. Symptoms You see delays or an error message when opening Report Studio. Resolving the problem %2Fcom.ibm.tivoli.tcr.doc_21%2Ftstcr_report_studio.html Customizing reports in Report Studio using Internet Explorer Report Studio in Firefox has some limitations with dragging and dropping objects into templates. Symptoms Some drag and drop operations do not succeed. Resolving the problem Always use Internet Explorer when creating or editing custom reports in Report Studio. Cannot resize the Common Reporting window in Internet Explorer 8 Symptoms When using Internet Explorer 8, resizing the browser window does not resize the Common Reporting window. Causes The issue is caused by a known issue with Internet Explorer 8 in Tivoli Common Reporting. 114 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

125 Resolving the problem If you need to resize the Common Reporting window, consider using Mozilla Firefox. Infinitely expanding resources in the Report Studio hierarchy Under certain conditions, resources in the hierarchy dimension can be expanded infinitely in the Report Studio presentation view. Expanding resources in the Report Studio presentation view does not affect the use of the dimension in reports. Symptoms If the hierarchy is not populated correctly, drill ups and drill downs do not work. Causes The error is caused by the default behavior of Cognos dimensions. If there is no data for certain objects, then an infinite loop is displayed in Report Studio. CSV export is not supported for reports containing multiple tables When there is more than one tabular chart in a report, the CSV exported only contains the data from the first tabular chart. The data for the other tabular charts is not exported to CSV. The CSV file extension is.xls instead of.csv The default file extension for a report exported to CSV format report is.xls instead of.csv. Symptoms When you export a report, the file extension is not.csv as expected and you get errors when opening the file. Causes The.xls file extension is default behavior for Tivoli Common Reporting. Resolving the problem Manually change the file extension to avoid errors when opening the file. Common Reporting page resets when you select another task Symptoms The Common Reporting page, including any reports you are viewing, resets to its default values if you switch to another task in the Tivoli Integrated Portal. Causes The issue is a known issue with Tivoli Common Reporting. Resolving the problem This behavior can be modified by changing the page persistence settings for the Common Reporting portlet. Chapter 13. Troubleshooting Model Maker and Common Reporting 115

126 Limitations on formatting charts in Microsoft Excel For best results when exporting reports to Excel, always select Microsoft Excel Due to formatting limitations in older versions of Excel, exporting in versions such as 2000 or 2002 can produce incompatible charts. Symptoms In Microsoft Excel 2007, wireline users can still experience some formatting problems with charts that have a decimal number on the y-axis. Causes Again, this is due to formatting limitations in Microsoft Excel. Resolving the problem If this problem occurs, use Report Studio to modify the chart and change the data format property of the y-axis to the Number with 2 decimal places option. Unreadable text error message in Excel 2007 Problem when running a report. Symptoms You might encounter an unreadable text error message when running a report in Excel 2007 format. Resolving the problem User response: The issue is a known issue. For more details and the workaround, see Delays when running scheduled reports Symptoms You find that scheduled reports take longer to run than interactive reports. Causes This is because a scheduled report generates the whole report before displaying the report, while an interactive report responds with the first page as soon as it is complete. Therefore, when scheduling reports with large numbers of resources, be aware that the run time will be longer than that of the equivalent interactive report. Diagnosing the problem When scheduling reports with large numbers of resources, be aware that the run time is longer than the equivalent interactive report. Data from wireless and wireline databases in reports is not linked You can install the Common Pack Service so that you can include data from both the wireless and wireline databases in reports. While you can include both wireless and wireline data in the same report, there is currently no relationship between the data. Null aggregation is not supported in Common Reporting Null aggregation is not supported in Common Reporting on Tivoli Netcool Performance Manager. 116 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

127 PDS-PPE-0104 error message You might encounter the following message while running reports containing charts. Symptoms PDS-PPE A record was rejected. An arithmetic overflow occurred. PDS-PPE-0104 A record was rejected. An arithmetic overflow occurred. (Data) Resolving the problem For more information, see the IBM technote at support/docview.wss?uid=swg1pm Errors while stopping and starting Tivoli Common Reporting on a Linux server These errors can be ingnored. Symptoms When you try to start or stop Tivoli Common Reporting on a Linux server, you might see the following errors: Stopping the Tivoli Common Reporting by using the following command: [root@coachford bin]#./stoptcrserver.sh <user_name> <password> The following errors are seen: Detected Linux RedHat 5 Applying LD_PRELOAD workaround. Ignore any subsequent errors referencing libfreetype.so ERROR: ld.so: object /usr/lib/libfreetype.so from LD_PRELOAD cannot be preloaded: ignored. Using /opt/ibm/tivoli/tipv2/java/jre/bin/java ERROR: ld.so: object /usr/lib/libfreetype.so from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object /usr/lib/libfreetype.so from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object /usr/lib/libfreetype.so from LD_PRELOAD cannot be preloaded: ignored. ADMU0116I: Tool information is being logged in file /opt/ibm/tivoli/tipv2/profiles/tipprofile/logs/server1/stopserver.log ADMU0128I: Starting tool with the TIPProfile profile ADMU3100I: Reading configuration for server: server1 ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server server1 stop completed. Starting the Tivoli Common Reporting by using the following command: [root@coachford bin]#./starttcrserver.sh <user_name> <password> The following errors are seen: Detected Linux RedHat 5 Applying LD_PRELOAD workaround. Ignore any subsequent errors referencing libfreetype.so ERROR: ld.so: object /usr/lib/libfreetype.so from LD_PRELOAD cannot be preloaded: ignored. Using /opt/ibm/tivoli/tipv2/java/jre/bin/java ERROR: ld.so: object /usr/lib/libfreetype.so from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object /usr/lib/libfreetype.so from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object /usr/lib/libfreetype.so from LD_PRELOAD cannot be preloaded: ignored. ADMU0116I: Tool information is being logged in file /opt/ibm/tivoli/tipv2/profiles/tipprofile/logs/server1/startserver.log ADMU0128I: Starting tool with the TIPProfile profile ADMU3100I: Reading configuration for server: server1 ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server server1 open for e-business; process id is Resolving the problem Chapter 13. Troubleshooting Model Maker and Common Reporting 117

128 You can ignore these errors as these errors do not interrupt the start and stop scripts. (Wireless) Null aggregation is not supported in Common Reporting - Wireless implications Tivoli Netcool Performance Manager KPIs with Null aggregation have their aggregation set to SUM in Common Reporting. In Common Reporting, this is most noticeable in ranking reports. Symptoms In ranking reports where drilling up (aggregating) the values of KPIs is used, ranked values are summed and not ranked. For Stored Busy Hours with a RANK measure, the rank value is summed when it is drilled up to its parent entity. This also happens for values rolled up over time. For example: Time Rank Value Day1 13: Day1 14: Day1 22: Day1 03: Day1 11: Day1 14: On a roll up to a week, the values appear as: Time Rank Value Week Causes Busy hour ranking is a type of null aggregator. It is recommended that the BH RANK measure is not used in rolled up reports. Resolving the problem When you are defining a summary, you can set the aggregation of a summary KPI to null. This means when this KPI is rolled up, the value after the rollup is null. Common Reporting is unable to roll up by null so attempts to sum the results, thus giving a different value than Tivoli Netcool Performance Manager - Wireless Component would give for the same KPI summary. (Wireless) KPIs that are stored in IP format in the database are displayed incorrectly in reports This issue occurs when you work with reports that have some KPIs stored in IP format (for example, ) in the wireless database. Symptoms The values for those KPIs are displayed incorrectly in the rendered report. Resolving the problem To work around this issue, set the aggregate function in the column properties of the KPI to None instead of Automatic, since the default aggregator in a technology pack is always Null. 118 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

129 (Wireline) PRS-CSE-1258 error message You might encounter an error message while running reports. Symptoms The following error message is displayed: PRS-CSE Problem encountered during verification of session capability information com.cognos.accman.jcam.crypto.camcryptoexception : CAM-CRP-1346 Failed to get the HMAC value to verify the package capability trust token. Invalid digest of the common symmetric key. Unable to find an appropriate common symmetric key to decrypt the data. Causes See the following IBM technote for further information: (Wireline) Report titles and labels are displayed in ASCII format Certain technology packs do not automatically convert the resourcealias attribute from ASCII format to text. Symptoms If you are working with reports on one of these packs, titles and labels are displayed as a long ASCII string. Resolving the problem If the error occurs, open Report Studio and modify the affected titles or labels to use resourcename instead of resourcealias. (Wireline) Differentiating duplicate resources with the same resourcealias. You must add the resourceid into lists and crosstabs to differentiate duplicate resources having the same resourcealias. Symptoms You can get incorrect data if a number of resources use the same resourcealias. This scenario is unusual but can occur in some situations. Causes In Common Reporting, metrics are aggregated based on the uniqueness of resource attributes such as the resourceid, resourcename, and resourcealias. For example, consider five resources each with a different resourceid, but sharing the same resourcealias. By default, when the report is process, only one row is returned because the aggregation and grouping are based on resourcealias. Resolving the problem When designing reports that contain resources that share the same resourcealias, you must add extra data items to lists, crosstabs, or charts. Adding the resourceid can differentiate different resources having the same resourcealias. Set the resourceid to hidden so that it is not displayed in the report. User response: Procedure for list (table) 1. From the Insertable Objects pane, drag a resourceid data item into the list. 2. Select the resourceid column. Chapter 13. Troubleshooting Model Maker and Common Reporting 119

130 3. In the Properties pane, under Box, set Box Type to None. User response: Procedure for crosstab 1. From the Insertable Objects pane, drag a resourceid data item into the crosstab. 2. In the Properties pane, under Miscellaneous, remove the Crosstab member cell class. 3. Unlock the report by using the lock icon on the toolbar. 4. In the crosstab, click each of the resourceid text items and delete them. User response: Procedure for chart 1. Click the repeater object that contains the chart. 2. In the Properties pane, to modify the Repeater properties click Data -> Group & Sorting. The Group & Sorting window opens. 3. Insert resourceid data items into Groups. 4. Insert ResourceAlias data items into Sort List under resourceid. (Wireline) Table cells with no data are blank Users of previous wireline versions expect to see a dash (-) in table cells where there is no data. However, to conform to the Cognos reporting guidelines, table cells with no data are left blank. (Wireline) Modifying timestamps in custom charts to round up to minutes instead of milliseconds By default, timestamps in reports created by using the wireline data models are rounded up to milliseconds. Symptoms Certain reports are difficult to read. Resolving the problem Change the report to round the timestamps up to minutes instead. User response: This procedure assumes that time data item found on the Source is inserted into the chart or table in Report Studio as shown. Repeat these steps as required while creating custom charts or tables. 1. Double-click the time data items. The Data Item Expression window opens. 2. In the Expression Definition window, enter the following expression. This expression removes seconds and milliseconds, resulting in the display of year-month-day hour:minute only.substring(cast( data_item_path,varchar(30)),1,16) where ata_item_paths the path of the selected data item. 3. Save the expression by clicking OK. (Wireline) Raw data is not returned for a KPI when all resources for a non-leaf group are selected Raw data only returns if you select all resources for a leaf report group, or select a subset of resources for a non-leaf group. Symptoms 120 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

131 A raw KPI (time-series) returns empty data when all resources for a non-leaf group are selected in the prompt pages for the report. The same report returns data when a subset of the available resources is selected. Causes For Common Reporting reports, there is a design limitation on how the DAL handles all resources being selected for a non-leaf group. Resolving the problem User response: If you have selected a non-leaf report group and require raw data, do not select all resources for the group. v Examples of non-leaf groups: NOC Reporting NOC Reporting~Devices NOC Reporting~Devices~Interfaces v Example of a leaf group: NOC Reporting~Devices~Interfaces~ (Wireline) Bar graph in microchart does not follow the sequence of KPIs in the summary table, as per the graph in HTML or PDF format The sequence of the KPIs in the bar graph in the microchart in some reports, for example Cisco CBQoS reports, does not follow the sequence of the KPIs in the summary table column. The graph is displayed correctly in HTML or PDF format. Symptoms The bar graph in a microchart can be different that you expect. Resolving the problem Be aware of this discrepancy when deciding the appropriate format to share your reports. (Wireline) Exporting a PDF returns an error when the report has no data charts Symptoms When a report has no data charts, the export PDF will fail and return an error. Resolving the problem Be aware of this issue when generating your PDF reports. Chapter 13. Troubleshooting Model Maker and Common Reporting 121

132 122 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

133 Appendix A. Configuring communications between the Common Pack Service and the Common Pack Service Client The Common Pack Service supports secure communication over the HTTP protocol between the Common Pack Service and the Common Pack Service Client. If needed, you can optionally configure secure communications. This release of the Common Pack Service Client Secure Communication supports Microsoft Windows and UNIX. The CLI client for the Common Pack Service has three options for communication between the Common Pack Service and the Common Pack Service Client: v Nonsecure communications. v Secure communications with the trusting option. v Secure communications with the strict option. Configuring nonsecure communications You can configure the client to use a nonsecure communication channel (HTTP) protocol between the Common Pack Service and the Client. Procedure 1. On the computer where Tivoli Common Reporting is installed, go to the $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/conf directory. Where: TIP_COMPONENTS_LOCATION Is the location where the Tivoli Integrated Portal components are installed. By default, /opt/ibm/tivoli/tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. 2. Open the biserviceclient.properties file in edit mode. 3. Ensure that the bi.pack.service.ssl property is set to false as shown: bi.pack.service.ssl=false 4. Ensure that the port value property in the biserviceclient.properties file uses the HTTP port and not the HTTPS port. 5. Save the biserviceclient.properties file. Results The client and the service now communicate over a nonsecure connection. Configuring secure communication with the trusting option You can configure the client to use secure communication channel SSL over the HTTP protocol with the trusting option between the Common Pack Service and the Client. This option must be used with a self-signed digital certificate, and you must trust the certificate used by Tivoli Common Reporting. Copyright IBM Corp. 2011,

134 Procedure 1. On the computer where Tivoli Common Reporting is installed, go to the $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/conf directory. Where: TIP_COMPONENTS_LOCATION Is the location where the Tivoli Integrated Portal components are installed. By default, /opt/ibm/tivoli/tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. 2. Open the biserviceclient.properties file in edit mode. 3. Ensure that the bi.pack.service.ssl property is set to true as shown: bi.pack.service.ssl=true 4. Ensure that the bi.pack.service.ssl.mode property is set to trusting as shown: bi.pack.service.ssl.mode=trusting 5. Ensure that the port value uses the HTTPS port and not the HTTP port. 6. Ensure that the host value matches the same value as Common Name CN on the Certificate. 7. Save the biserviceclient.properties file. Results The client and the service now communicate over a secure connection with the trusting option. Configuring secure communication with the strict option You can configure the client to use secure communication channel SSL over the HTTP protocol with the strict option between the Common Pack Service and the Client. The Tivoli Common Reporting Digital Certificate is imported to the client runtime truststore. This option is the most secure. Procedure 1. On the computer where Tivoli Common Reporting is installed, go to the $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/conf directory. Where: TIP_COMPONENTS_LOCATION Is the location where the Tivoli Integrated Portal components are installed By default, /opt/ibm/tivoli/tipv2components for wireless and /opt/ibm/tivoli/tip21components for wireline. 2. Open the biserviceclient.properties file in edit mode. 3. Ensure that the bi.pack.service.ssl property is set to true as shown: bi.pack.service.ssl=true 4. Ensure that the bi.pack.service.ssl.mode is set to strict as shown: bi.pack.service.ssl.mode=strict 5. Ensure that the port value property uses the HTTPS port rather than the HTTP port. 6. Save the biserviceclient.properties file. 124 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

135 What to do next You must export the digital certificate from Tivoli Common Reporting and import it into the Common Pack Service Client JVM runtime truststore. Exporting the Tivoli Common Reporting digital certificate You can export the Tivoli Common Reporting digital certificate. Procedure 1. Log in to the Tivoli Integrated Portal. 2. In the Tivoli Integrated Portal, expand Settings > WebSphere Administrative Console. 3. Select Launch WebSphere Administrative Console. 4. Log in to the Administrative Console. 5. Expand Security and select SSL certificate and key management. 6. Under the Configuration settings section select Manage endpoint security configurations link. 7. Select the SSL certificate as shown. 8. Select Manage Certificates as shown. Appendix A. Configuring communications between the Common Pack Service and the Common Pack Service Client 125

136 9. Select the certificate you want to manage and then extract it, as shown. 10. Enter the name of the file for the certificate. Usually the file name extension is cer. For example server_id.cer. Then click OK as shown. For example, the extracted certificate can be found in the following folder: /appl/ibm/ivoli/ tipv2/profiles/tipprofile/etc/ for wireless and /appl/ibm/ivoli/tip21/ profiles/tipprofile/etc/ 126 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

137 Importing the digital certificate to the client runtime truststore You can import the Tivoli Common Reporting certificate to the Common Pack Service Client JVM runtime truststore. Procedure 1. Go to <java-home>/jre/bin to verify which JVM you are using. 2. Use the ikeycmd tool to import the digital certificate. The following command imports the aquila_cert that was already exported from the Tivoli Common Reporting server: For the Wireless Component, enter the following command on one line: ikeycmd -cert -add -db /appl/ibm/tivoli/tipv2/java/jre/lib/security/cacerts -file /appl/ibm/tivoli/tipv2/profiles/tipprofile/etc/server_id.cer -type jks -label server_id_label For Wireline Component, enter the following command on one line: ikeycmd -cert -add -db /appl/ibm/tivoli/tip21/java/jre/lib/security/cacerts -file /appl/ibm/tivoli/tip21/profiles/tipprofile/etc/server_id.cer -type jks -label server_id_label 3. Enter the password for cacerts keystore database.. 4. Once the certificate is imported, the client can communicate securely with the service. Appendix A. Configuring communications between the Common Pack Service and the Common Pack Service Client 127

138 128 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

139 Appendix B. Command reference The pack_admin command A list of commands available for common pack administrators and modelers. The following commands are available: v The pack_admin command Use the Common Pack Service pack_admin command as root user to work with common packs and the common pack repository from the command line. For example, you can display the contents of the repository and add, activate, and remove common packs in the repository. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components The password file A password file is used to pass encrypted Tivoli Common Reporting and target database credentials to the pack_admin commands. The pack_admin -passwordfile option generates the encrypted logins file. The logins file is then passed into pack_admin commands and actions by using the -logins option. The password file must contain credentials for the Tivoli Integrated Portal, and for the target database user accounts, bicontrol, and birefresh. These "accounts" represent users on the target database with a known minimum set of privileges. They do not literally have to be users named bicontrol, and birefresh. Each account is used to perform different tasks, and the actions themselves are configured to look for a particular account they must use to perform their operation. Each action looks up the user name of the account they need to use, as defined in the connection profile specified for the pack, and compares this name to the user names they receive in the password file. Example Here is an example password file. TARGET tnpm bicontrol TARGET tnpm birefresh TIPUSER - tipadmin Copyright IBM Corp. 2011,

140 pack_admin -activate The -activate command flag for the pack_admin command activates a common pack in the Pack Repository by applying the specified version of a pack to the system. Database schemas are installed (upon first-time activation of a given pack) or upgraded (upon activation of subsequent versions of the pack) and the active version of the pack is updated. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components Syntax pack_admin.sh -activate -pack pack_name -version version_number -logins logins_file Parameters When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. pack_name The name of a common pack in the Pack Repository. version_number The version number of the common pack. logins_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. The logins file must contain the username of the bicontrol account for the connection profile. pack_admin -add The -add command flag for the pack_admin command adds the specified common packs to the common pack repository by registering pack versions with the system. The version of the pack appears on the pack list of the repository, but that version is not used until it is activated. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed: Wireless Component /opt/ibm/tivoli/tipv2components 130 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

141 Wireline Component /opt/ibm/tivoli/tip21components Syntax pack_admin.sh -add [ -pack pack_filename -dir directory_path ] -logins logins_file Use this syntax to add a specified pack to the repository. This pack must be a new pack that does not exist in the repository. pack_admin.sh -add -pack pack_filename -logins logins_file Use this syntax to add all the packs in the specified directory to the repository. Useful for adding a particular pack and its set of dependent packs in one command. The directory is searched and the list of files found is passed to the Common Pack Service for processing. The Common Pack Service determines the correct dependencies and adds the files in the correct order. pack_admin.sh -add -dir directory_path -logins logins_file Parameters When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. pack_filename The file name and full path to one or more pack JAR files. directory_path The path to a directory containing pack JAR files. logins_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. pack_admin -execute The -execute command flag for the pack_admin command runs a particular action associated with a pack. The success or failure of the action is displayed after the command runs. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components Syntax pack_admin.sh -execute -action action_name -logins logins_file Appendix B. Command reference 131

142 Parameters When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. action_name The name of an action that can be performed on a common pack in the Pack Repository. When you issue the command to execute an action, it executes the action on all common packs that define that action. Actions defined in all common packs except tcr.time data-refill populates the hierarchy tables on which the Cognos Models depend. The data-refill option cleans out and fully populates the DM tables. Typically, the data-refill option is run once when you deploy a pack. Actions defined in the tcr.time common pack. populate 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 option on Monday to create entries for Wednesday. This example enables reporting through the midnight hour, since we have the timestamps in the calendar for the data arriving. calendar-refill 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 option, as the main purpose of the command is to clear out the old timestamps. logins_file A credentials file containing a Tivoli Integrated Portal administrative user name and password, and a database user name and password. The password file must contain the username of the birefresh account for the connection profile pack_admin -list The -list command flag for the pack_admin command lists actions, pack actions, packs, pack properties, variables, and pack variables for common packs installed on the system. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components 132 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

143 Syntax Use this syntax to list the actions for all packs currently installed on the system. pack_admin.sh -list -actions -all -logins logins_file Use this syntax to list the actions for a specified pack. pack_admin.sh -list -actions -pack pack_name -logins logins_file Use this syntax to list the packs currently installed on the system, with details such as the pack name, the pack version, and the pack installation time. pack_admin.sh -list -packs -logins logins_file Use this syntax to list the properties for all packs currently installed on the system. pack_admin.sh -list -property -all -logins logins_file Use this syntax to list the properties and their values for a specified pack. pack_admin.sh -list -pack pack_name -property -all -logins logins_file Use this syntax to list the values of particular properties in a pack. pack_admin.sh -list -pack pack_name -property <property_name>... <property_namen> -logins logins_file Use this syntax to list the variables and their values for a specified pack. pack_admin.sh -list -pack pack_name -variable -all -logins logins_file Use this syntax to list the values of particular variables in a pack. pack_admin.sh -list -pack pack_name -variable <variable_name>... <variable_namen> -logins logins_file Parameters When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. pack_name The name of a common pack in the Pack Repository. When listing multiple packs leave a space between each pack name. logins_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. property_name A common pack property. variable_name A common pack variable. Appendix B. Command reference 133

144 variable_value A common pack variable value. pack_admin -passwordfile The -passwordfile command flag for the pack_admin command updates the common pack password file. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components Syntax Use this syntax to add a Tivoli Integrated Portal user to the password file. pack_admin.sh -passwordfile logins_file -tipuser tip_user_name Use this syntax to add database users to a particular profile in the database file. pack_admin.sh -passwordfile logins_file -tipuser tip_user_name -dbusers profile_name:database_user_name1... profile_name:database_user_namen Use this syntax to add a Tivoli Integrated Portal user and to add database users to a particular profile in the database file. pack_admin.sh -passwordfile logins_file -tipuser tip_user_name -dbusers profile_name:database_user_name1... profile_name:database_user_namen Parameters logins_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. tip_user_name The name of a valid Tivoli Integrated Portal user with all required permissions. profile_name A valid profile. database_user_name The name of a valid database user with all required permissions. 134 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

145 pack_admin -remove The -remove command flag for the pack_admin command removes a specified pack from the common pack repository. You can remove only a common pack that has no dependencies for other packs. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components Syntax If you want to uninstall a common pack that acts as a dependency for another pack, then you must first uninstall the dependent common pack. pack_admin.sh -remove -pack pack_name -logins logins_file Parameters When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. pack_name The name of a common pack in the Pack Repository. logins_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. The password file must contain the username of the bicontrol account for the connection profile. pack_admin -reset The -reset command flag for the pack_admin command resets the user-defined override values of common pack properties and variables to the default values from the common pack. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components Appendix B. Command reference 135

146 Syntax Use this syntax to reset user-defined override values of common pack properties to the default values from the common pack. pack_admin.sh -reset -pack pack_name -property [property_name1... property_namen -all ] -logins logins_file Use this syntax to reset user-defined override values of common pack variables to the default values from the common pack. pack_admin.sh -reset -pack pack_name -variable [variable_name1... variable_namen -all ] -logins logins_file Parameters When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. pack_name The name of a common pack in the Pack Repository. When listing multiple packs leave a space between each pack name. logins_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. property_name A common pack property. variable_name A common pack variable. pack_admin -set The -set command flag for the pack_admin command sets properties, variables, schemas, schema logins, and connection profiles. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components Syntax Use this syntax to set pack properties. pack_admin.sh -set -pack pack_name -property property_name1:property_value1,...,property_namen:property_valuen -logins logins_file 136 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

147 Use this syntax to set pack variables. pack_admin.sh -set -pack pack_name -variable variable_name1:variable_value1,...,variable_namen:variable_valuen -logins logins_file Use this syntax to set the connection profile. pack_admin.sh -set -profile profile_name -logins logins_file Use this syntax to set the stored encrypted password for a specific database schema, with an interactive prompt for the password. Include the -app flag to indicate that the supplied schema credentials are for an application schema. pack_admin.sh -set -schema schema_name -profile profile_name [ -app ] -logins logins_file Parameters When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. pack_name The name of a common pack in the Pack Repository. When listing multiple packs leave a space between each pack name. logins_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. property_name A common pack property. variable_name A common pack variable. variable_value A common pack variable value. profile_name The name of a specific profile. schema_name The name of a specific schema. The password file must contain the username of the schema_name account for the connection profile. pack_admin -rmv Use the -rmv command flag with the pack_admin command to create and refresh resource metric viewer reports. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: Wireless Component /opt/ibm/tivoli/tipv2components Appendix B. Command reference 137

148 Wireline Component /opt/ibm/tivoli/tip21components Syntax Use this syntax to create Resource Metric Viewer reports for a specified pack or for all available packs. The pack has to be deployed before a Resource Metric Viewer report can be created. pack_admin.sh -rmv -create [ -pack pack_filename -all ] -logins password_file Use this syntax to refresh Resource Metric Viewer reports following a change in the underlying model, for example when new model version deployed to th eserver. pack_admin.sh -rmv -update_metrics [ -pack pack_filename -all ] -logins password_file Use this syntax to refresh Resource Metric Viewer reports following a change in the model templates, for example to create custom Resource Metric Viewer report templates. pack_admin.sh -rmv -update_reports [ -pack pack_filename -all ] -logins password_file Use this syntax to remove all obsolete Resource Metric Viewer reports from the system. pack_admin.sh -rmv -cleanup Parameters When a parameter includes spaces, enclose the complete parameter in double quotation marks or escape the parameter. pack_name The name of a common pack in the Pack Repository. When listing multiple packs leave a space between each pack name. password_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. pack_admin -deploy The -deploy command flag for the pack_admin command deploys a common pack to the Tivoli Common Reporting server to make a report package available for reporting. Location $TIP_COMPONENTS_LOCATION/TCRComponent/commonpackservice/bin Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default: 138 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

149 Wireless Component /opt/ibm/tivoli/tipv2components Wireline Component /opt/ibm/tivoli/tip21components Syntax Use this syntax to deploy a common pack containing raw data. pack_admin.sh -deploy -cifs tnpmmodel_file_path -name pack_name -version version_number -logins logins_file -overwrite Use this syntax to deploy a common pack containing Vendor Specific summary and GOM summary. pack_admin.sh -deploy -cifs tnpmmodel_file_path -name pack_name -version version_number -logins logins_file -overwrite -deps dependent_packs Parameters tnpmmodel_file_path The path to a directory containing the CIF (tnpmmodel) file. pack_name The name of a common pack in the Pack Repository. version_number The version number of the common pack. logins_file An encrypted credentials file containing a Tivoli Integrated Portal administrative user name and password, and database user names and passwords. The logins file must contain the username of the bicontrol account for the connection profile. dependent_packs Dependent packs that are required for the current deployment Appendix B. Command reference 139

150 140 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

151 Appendix C. Installing the Resource Metric Viewer as a separate installation Currently, you can run the Common Pack Service installer without installing the Resource Metric Viewer. If you want to install the Resource Metric Viewer later as a separate installation, follow these steps. Procedure 1. Change to the following directory as the root user: <commonpackservice_installation_directory>/rmv/scripts By default, the commonpackservice_installation_directory is /opt/ibm/tivoli/ tipv2components/tcrcomponent/commonpackservice. 2. Install the Resource Metric Viewer by running the install_rmv.sh script as follows: install_rmv.sh <TIP_installation_directory> <tipadmin_user_name> <tipadmin_password> By default, the TIP_installation_directory is /opt/ibm/tivoli/tipv2, and is not the same directory as the tipv2components path. 3. Install the Resource Metric Viewer schema by running the following command: rmv_db_schema.sh jdbc:oracle:thin:@<database_hostname>:1521:vtdb <oracle_client_directory> bicontrol <bicontrol_user_password> By default, the oracle_client_directory is /opt/oracle/product/11.2.0/db_1 and the bicontrol_user_password is bicontrol. For example, rmv_db_schema.sh jdbc:oracle:thin:@ :1521:vtdb /opt/oracle/product/11.2.0/db_1 bicontrol bicontrol Results Resource Metric Viewer is installed and ready for use. Copyright IBM Corp. 2011,

152 142 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

153 Appendix D. Overriding Common Pack Service installer options If you want to change the Common Pack Service installer options after the Common Pack Service is installed, you can manually change the properties in the global.properties file. Some of the changes that can be done in the global.properties file are described in the following sections. Enabling reduced data model for a common pack containing raw data The reduced data model feature removes the database view from the generated model and saves approximately 40-50% on model size. The reduced data model contains only the consolidation view. The Database view is removed from the model. Procedure v Change the following property in the global.properties file to Y to enable the reduced model option. Or, change to N to disable the option: MINIMUM_MODEL_SIZE=Y The global.properties file is available in the following location: /opt/ibm/tivoli/tipv2/profiles/tipprofile/installedapps/tipcell/isc.ear/ bi-pack-service.war/global.properties v Note: When you install the Common Pack Service, you can enable the reduced data model for a common pack that contains raw data as shown in Step 15 of the Common Pack Service installation as described in Running the installer on page 20. The global.properties file is automatically updated. Restart the Tivoli Common Reporting server for the change to take effect. Results When you enable the reduced data model option, the model looks as follows in Framework manager: Copyright IBM Corp. 2011,

154 Enabling inner join Note: You can create reduced data models for common packs that contain busy hour and summary definitions by using the same procedure. Currently, the outer join between time dimension and metrics results in a report that contains all the timestamps, even if the traffic data is not available. Using the outer join causes performance degradation, when you run a Cognos report. You can enable inner join option to retrieve only the timestamps where the data is available there by improving the performance of the reports. About this task An inner join returns row only when there is a match between two tables that are based on the join predicate. In this case, when there is common time between 144 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E1. Model Maker Installation and User Guide

IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E1. Model Maker Installation and User Guide IBM Tivoli Netcool Performance Manager Model Maker 1.2.3 Document Revision R2E1 Model Maker Installation and User Guide Note Before using this information and the product it supports, read the information

Detaljer

IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E1. Model Maker Installation and User Guide

IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E1. Model Maker Installation and User Guide IBM Tivoli Netcool Performance Manager Model Maker 1.2.1 Document Revision R2E1 Model Maker Installation and User Guide Note Before using this information and the product it supports, read the information

Detaljer

IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E1. Model Maker Installation and User Guide

IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E1. Model Maker Installation and User Guide IBM Tivoli Netcool Performance Manager Model Maker 1.2.4 Document Revision R2E1 Model Maker Installation and User Guide Note Before using this information and the product it supports, read the information

Detaljer

GLOBALCOMSERVER HP 9100C DIGITAL SENDER GATEWAY ADMINISTRATOR S GUIDE 1998 AVM INFORMATIQUE (UPDATED: AUGUST 22, 2006)

GLOBALCOMSERVER HP 9100C DIGITAL SENDER GATEWAY ADMINISTRATOR S GUIDE 1998 AVM INFORMATIQUE (UPDATED: AUGUST 22, 2006) PAGE 1 / 13 GLOBALCOMSERVER HP 9100C DIGITAL SENDER GATEWAY ADMINISTRATOR S GUIDE 1998 AVM INFORMATIQUE (UPDATED: AUGUST 22, 2006) PAGE 2 / 13 LICENSE LICENSE Information in this document is subject to

Detaljer

Windows Server 2008 Hyper-V, Windows Server 2008 Server Core Installation Notes

Windows Server 2008 Hyper-V, Windows Server 2008 Server Core Installation Notes Windows Server 2008 Hyper-V, Hyper-V Server 2008, and Windows Server 2008 Server Core Installation Notes Installing Dell UPS Management Software on a Hypervisor-Based Server Environment w w w. d e l l.

Detaljer

IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E1. Model Maker Installation and User Guide

IBM Tivoli Netcool Performance Manager Model Maker Document Revision R2E1. Model Maker Installation and User Guide IBM Tivoli Netcool Performance Manager 1.3.3 Model Maker 1.3.0 Document Revision R2E1 Model Maker Installation and User Guide Note Before using this information and the product it supports, read the information

Detaljer

Information search for the research protocol in IIC/IID

Information search for the research protocol in IIC/IID Information search for the research protocol in IIC/IID 1 Medical Library, 2013 Library services for students working with the research protocol and thesis (hovedoppgaven) Open library courses: http://www.ntnu.no/ub/fagside/medisin/medbiblkurs

Detaljer

Sascha Schubert Product Manager Data Mining SAS International Copyright 2006, SAS Institute Inc. All rights reserved.

Sascha Schubert Product Manager Data Mining SAS International Copyright 2006, SAS Institute Inc. All rights reserved. Extending SAS Enterprise Miner Sascha Schubert Product Manager Data Mining SAS International Agenda Architecture of SAS Enterprise Miner 5.2 Access to SAS Data Mining Functionality The Flexibility of the

Detaljer

Hvordan føre reiseregninger i Unit4 Business World Forfatter:

Hvordan føre reiseregninger i Unit4 Business World Forfatter: Hvordan føre reiseregninger i Unit4 Business World Forfatter: dag.syversen@unit4.com Denne e-guiden beskriver hvordan du registrerer en reiseregning med ulike typer utlegg. 1. Introduksjon 2. Åpne vinduet

Detaljer

Trådløsnett med Windows XP. Wireless network with Windows XP

Trådløsnett med Windows XP. Wireless network with Windows XP Trådløsnett med Windows XP Wireless network with Windows XP Mai 2013 Hvordan koble til trådløsnettet eduroam med Windows XP Service Pack 3? How to connect to the wireless network eduroam with Windows XP

Detaljer

Unit Relational Algebra 1 1. Relational Algebra 1. Unit 3.3

Unit Relational Algebra 1 1. Relational Algebra 1. Unit 3.3 Relational Algebra 1 Unit 3.3 Unit 3.3 - Relational Algebra 1 1 Relational Algebra Relational Algebra is : the formal description of how a relational database operates the mathematics which underpin SQL

Detaljer

Hybrid Cloud and Datacenter Monitoring with Operations Management Suite (OMS)

Hybrid Cloud and Datacenter Monitoring with Operations Management Suite (OMS) Hybrid Cloud and Datacenter Monitoring with Operations Management Suite (OMS) Varighet: 5 Days Kurskode: M10996 Version: A Opplæringsmetoder: Virtuell opplæring Beskrivelse: This five-day course will provide

Detaljer

INF2120 Tools at your fingertips

INF2120 Tools at your fingertips INF2120 Tools at your fingertips Version 070124 23-Jan-07 INF2120 Prosjekt i modellering 1 Eclipse og RSM en god IDE? med foiler også av Andreas Limyr og Gøran K. Olsen før begge Ifi, nå begge Sintef 23-Jan-07

Detaljer

Start Here USB *CC * *CC * USB USB

Start Here USB *CC * *CC * USB USB 1 USB Start Here USB 11 USB WARNING: To ensure that the software is installed correctly, do not connect the USB cable until step 11. 11 USB 2 a. b. Lower both the paper tray and the print cartridge door.

Detaljer

Slope-Intercept Formula

Slope-Intercept Formula LESSON 7 Slope Intercept Formula LESSON 7 Slope-Intercept Formula Here are two new words that describe lines slope and intercept. The slope is given by m (a mountain has slope and starts with m), and intercept

Detaljer

Trådløsnett med Windows Vista. Wireless network with Windows Vista

Trådløsnett med Windows Vista. Wireless network with Windows Vista Trådløsnett med Windows Vista Wireless network with Windows Vista Mai 2013 Hvordan koble til trådløst nettverk eduroam med Windows Vista? How to connect to the wireless networkeduroam with Windows Vista?

Detaljer

Trådløsnett med. Wireless network. MacOSX 10.5 Leopard. with MacOSX 10.5 Leopard

Trådløsnett med. Wireless network. MacOSX 10.5 Leopard. with MacOSX 10.5 Leopard Trådløsnett med MacOSX 10.5 Leopard Wireless network with MacOSX 10.5 Leopard April 2010 Slå på Airport ved å velge symbolet for trådløst nettverk øverst til høyre på skjermen. Hvis symbolet mangler må

Detaljer

Quantitative Spectroscopy Chapter 3 Software

Quantitative Spectroscopy Chapter 3 Software Quantitative Spectroscopy Chapter 3 Software Copyright 2006 Mettler-Toledo AutoChem, Inc. 1 Chapter 3 Outline P-matrix P-matrix with automatic frequency select PLS: Choosing a region PLS: Selecting the

Detaljer

SmartPass Mini User Manual BBNORGE.NO

SmartPass Mini User Manual BBNORGE.NO SmartPass Mini User Manual BBNORGE.NO Intro Welcome to the usermanual for your SmartPass Mini system. The first time you start the SmartPass you have to request a License. This is to regiser your license

Detaljer

Elektronisk innlevering/electronic solution for submission:

Elektronisk innlevering/electronic solution for submission: VIKINGTIDSMUSEET Plan- og designkonkurranse/design competition Elektronisk innlevering/electronic solution for submission: Det benyttes en egen elektronisk løsning for innlevering (Byggeweb Anbud). Dette

Detaljer

SAS FANS NYTT & NYTTIG FRA VERKTØYKASSA TIL SAS 4. MARS 2014, MIKKEL SØRHEIM

SAS FANS NYTT & NYTTIG FRA VERKTØYKASSA TIL SAS 4. MARS 2014, MIKKEL SØRHEIM SAS FANS NYTT & NYTTIG FRA VERKTØYKASSA TIL SAS 4. MARS 2014, MIKKEL SØRHEIM 2 TEMA 1 MULTIPROSESSERING MED DATASTEGET Multiprosessering har lenge vært et tema i SAS Stadig ny funksjonalitet er med på

Detaljer

Compello Fakturagodkjenning Versjon 10.5 As a Service. Tilgang til Compello Desktop - Regnskapsføring og Dokument import

Compello Fakturagodkjenning Versjon 10.5 As a Service. Tilgang til Compello Desktop - Regnskapsføring og Dokument import Compello Fakturagodkjenning Versjon 10.5 As a Service Tilgang til Compello Desktop - Regnskapsføring og Dokument import Dokumentopplysninger 2018 Compello AS. Med enerett. Microsoft, MS-DOS og Windows

Detaljer

1. Installasjon av SharePoint 2013

1. Installasjon av SharePoint 2013 Avdeling for informatikk og e-læring, Høgskolen i Sør-Trøndelag Installasjon av SharePoint 2013 Stein Meisingseth 02.09.2013 Lærestoffet er utviklet for faget LO205D Microsoft SharePoint 1. Installasjon

Detaljer

Compello Fakturagodkjenning Versjon 10 Software as a service. Tilgang til ny modulen Regnskapsføring

Compello Fakturagodkjenning Versjon 10 Software as a service. Tilgang til ny modulen Regnskapsføring Compello Fakturagodkjenning Versjon 10 Software as a service Tilgang til ny modulen Regnskapsføring Dokumentopplysninger 2018 Compello AS. Med enerett. Microsoft, MS-DOS og Windows er registrerte varemerker

Detaljer

Server-Side Eclipse. Bernd Kolb Martin Lippert it-agile GmbH

Server-Side Eclipse. Bernd Kolb Martin Lippert it-agile GmbH Server-Side Eclipse Bernd Kolb b.kolb@kolbware.de Martin Lippert it-agile GmbH lippert@acm.org 2006 by Martin Lippert, lippert@acm.org; made available under the EPL v1.0 Outline Introduction Why Eclipse?

Detaljer

Server-Side Eclipse. Martin Lippert akquinet agile GmbH

Server-Side Eclipse. Martin Lippert akquinet agile GmbH Server-Side Eclipse Martin Lippert akquinet agile GmbH martin.lippert@akquinet.de 2006 by Martin Lippert, martin.lippert@akquinet.de; made available under the EPL v1.0 Outline Introduction Why Eclipse?

Detaljer

E-Learning Design. Speaker Duy Hai Nguyen, HUE Online Lecture

E-Learning Design. Speaker Duy Hai Nguyen, HUE Online Lecture E-Learning Design Speaker Duy Hai Nguyen, HUE Online Lecture Design Educational Design Navigation Design Educational Design Some Important Considerations: 1. Authentic learning environment: For effective

Detaljer

HONSEL process monitoring

HONSEL process monitoring 6 DMSD has stood for process monitoring in fastening technology for more than 25 years. HONSEL re- rivet processing back in 990. DMSD 2G has been continuously improved and optimised since this time. All

Detaljer

AKENEOPIM User Guide Version 1.6. Catalog settings USER GUIDE CATALOG SETTINGS. Version 1.6. Copyright AKENEO SAS The Open Source PIM

AKENEOPIM User Guide Version 1.6. Catalog settings USER GUIDE CATALOG SETTINGS. Version 1.6. Copyright AKENEO SAS The Open Source PIM USER GUIDE CATALOG SETTINGS CONTENTS Manage Attributes 5 View Attributes 5 Page numbering 5 The filters 6 Screening product attributes 7 Shortcut actions on each attribute 7 Create an attribute 8 Edit

Detaljer

Trådløst nett UiT Feilsøking. Wireless network UiT Problem solving

Trådløst nett UiT Feilsøking. Wireless network UiT Problem solving Trådløst nett UiT Feilsøking Wireless network UiT Problem solving April 2015 Hvorfor får jeg ikke koblet meg opp mot trådløst nettverk med Windows 7? Why can t I connect to the wireless network with Windows

Detaljer

WWW.CERT.DK. Introduction to DK- CERT Vulnerability Database

WWW.CERT.DK. Introduction to DK- CERT Vulnerability Database Introduction to DK- CERT Vulnerability Database By Peter Rickers and Mikael Stamm 1 Fundamental Idea Securing of networks, in-house and externally Savings for the costumers Making admission to the correct

Detaljer

Den europeiske byggenæringen blir digital. hva skjer i Europa? Steen Sunesen Oslo,

Den europeiske byggenæringen blir digital. hva skjer i Europa? Steen Sunesen Oslo, Den europeiske byggenæringen blir digital hva skjer i Europa? Steen Sunesen Oslo, 30.04.2019 Agenda 1. 2. CEN-veileder til ISO 19650 del 1 og 2 3. EFCA Guide Oppdragsgivers krav til BIMleveranser og prosess.

Detaljer

EMPIC MEDICAL. Etterutdanningskurs flyleger 21. april Lars (Lasse) Holm Prosjektleder Telefon: E-post:

EMPIC MEDICAL. Etterutdanningskurs flyleger 21. april Lars (Lasse) Holm Prosjektleder Telefon: E-post: EMPIC MEDICAL Etterutdanningskurs flyleger 21. april 2017 Lars (Lasse) Holm Prosjektleder Telefon: +47 976 90 799 E-post: Lrh@caa.no it-vakt@caa.no Luftfartstilsynet T: +47 75 58 50 00 F: +47 75 58 50

Detaljer

CSR Harvesting Final Meeting September, 2015 Brest, France. Anne Che-Bohnenstengel & Matthias Pramme, BSH

CSR Harvesting Final Meeting September, 2015 Brest, France. Anne Che-Bohnenstengel & Matthias Pramme, BSH CSR Harvesting Final Meeting 16. 17. September, 2015 Brest, France Anne Che-Bohnenstengel & Matthias Pramme, BSH Topics Introduction Harvesting Workflow CSR-Harvesting Report Monitoring portal for harvesting

Detaljer

of color printers at university); helps in learning GIS.

of color printers at university); helps in learning GIS. Making a Home Page Why a Web Page? Easier to submit labs electronically (lack of color printers at university); Easier to grade many labs; Provides additional computer experience that helps in learning

Detaljer

Den som gjør godt, er av Gud (Multilingual Edition)

Den som gjør godt, er av Gud (Multilingual Edition) Den som gjør godt, er av Gud (Multilingual Edition) Arne Jordly Click here if your download doesn"t start automatically Den som gjør godt, er av Gud (Multilingual Edition) Arne Jordly Den som gjør godt,

Detaljer

REMOVE CONTENTS FROM BOX. VERIFY ALL PARTS ARE PRESENT READ INSTRUCTIONS CAREFULLY BEFORE STARTING INSTALLATION

REMOVE CONTENTS FROM BOX. VERIFY ALL PARTS ARE PRESENT READ INSTRUCTIONS CAREFULLY BEFORE STARTING INSTALLATION 2011-2014 FORD EXPLORER PARTS LIST Qty Part Description Qty Part Description 1 Bull Bar 2 12mm x 35mm Bolt Plates 1 Passenger/Right Mounting Bracket 2 12mm Nut Plate 1 Driver/Left Mounting Bracket 2 12mm

Detaljer

HP LaserJet MFP. Analog Fax Accessory 300

HP LaserJet MFP. Analog Fax Accessory 300 HP LaserJet MFP Analog Fax Accessory 300 Send Fax Driver Guide Send Fax Driver Vejledning Faksinlähetysohjaimen käyttöopas Håndbok for Send faks-driveren Drivrutinsguide för att skicka fax 12234 HP LaserJet

Detaljer

Oppgave 1a Definer følgende begreper: Nøkkel, supernøkkel og funksjonell avhengighet.

Oppgave 1a Definer følgende begreper: Nøkkel, supernøkkel og funksjonell avhengighet. TDT445 Øving 4 Oppgave a Definer følgende begreper: Nøkkel, supernøkkel og funksjonell avhengighet. Nøkkel: Supernøkkel: Funksjonell avhengighet: Data i en database som kan unikt identifisere (et sett

Detaljer

The regulation requires that everyone at NTNU shall have fire drills and fire prevention courses.

The regulation requires that everyone at NTNU shall have fire drills and fire prevention courses. 1 The law The regulation requires that everyone at NTNU shall have fire drills and fire prevention courses. 2. 3 Make your self familiar with: Evacuation routes Manual fire alarms Location of fire extinguishers

Detaljer

Vedlegg 2 Dokumentasjon fra TVM leverandør

Vedlegg 2 Dokumentasjon fra TVM leverandør (Step 7) Payment selection or date modification state This screen is displayed after validation of a date in the calendar screen. The customer can: - Modify again the date by pressing the Validity begin:

Detaljer

Databases 1. Extended Relational Algebra

Databases 1. Extended Relational Algebra Databases 1 Extended Relational Algebra Relational Algebra What is an Algebra? Mathematical system consisting of: Operands --- variables or values from which new values can be constructed. Operators ---

Detaljer

Smart High-Side Power Switch BTS730

Smart High-Side Power Switch BTS730 PG-DSO20 RoHS compliant (green product) AEC qualified 1 Ω Ω µ Data Sheet 1 V1.0, 2007-12-17 Data Sheet 2 V1.0, 2007-12-17 Ω µ µ Data Sheet 3 V1.0, 2007-12-17 µ µ Data Sheet 4 V1.0, 2007-12-17 Data Sheet

Detaljer

Endringer i neste revisjon av EHF / Changes in the next revision of EHF 1. October 2015

Endringer i neste revisjon av EHF / Changes in the next revision of EHF 1. October 2015 Endringer i neste revisjon av / Changes in the next revision of 1. October 2015 INFORMASJON PÅ NORSK 2 INTRODUKSJON 2 ENDRINGER FOR KATALOG 1.0.3 OG PAKKSEDDEL 1.0.2 3 ENDRINGER FOR ORDRE 1.0.3 4 ENDRINGER

Detaljer

Han Ola of Han Per: A Norwegian-American Comic Strip/En Norsk-amerikansk tegneserie (Skrifter. Serie B, LXIX)

Han Ola of Han Per: A Norwegian-American Comic Strip/En Norsk-amerikansk tegneserie (Skrifter. Serie B, LXIX) Han Ola of Han Per: A Norwegian-American Comic Strip/En Norsk-amerikansk tegneserie (Skrifter. Serie B, LXIX) Peter J. Rosendahl Click here if your download doesn"t start automatically Han Ola of Han Per:

Detaljer

Rom-Linker Software User s Manual

Rom-Linker Software User s Manual Rom-Linker Software User s Manual Tel.: +886-2-2274-1347 Fax. +886-2-2273-3014 Http://www.hmt.com.tw e-mail: hmtsales@hmt.com.tw Contents Catalogue Page (1) Rom-Linker Starting Screen... 01 (2) Rom-Linker

Detaljer

Improving Customer Relationships

Improving Customer Relationships Plain Language Association International s 11 th conference Improving Customer Relationships September 21-23, 2017 University of Graz, Austria hosted by Klarsprache.at Copyright of this presentation belongs

Detaljer

buildingsmart Norge seminar Gardermoen 2. september 2010 IFD sett i sammenheng med BIM og varedata

buildingsmart Norge seminar Gardermoen 2. september 2010 IFD sett i sammenheng med BIM og varedata buildingsmart Norge seminar Gardermoen 2. september 2010 IFD sett i sammenheng med BIM og varedata IFD International Framework for Dictionaries Hvordan bygges en BIM? Hva kan hentes ut av BIM? Hvordan

Detaljer

SQL Server guide til e-lector

SQL Server guide til e-lector LES LETTERE, LES RASKERE, FÅ LESELYST! SQL Server guide til e-lector Innhold 1 Innledning... 2 2 SQL Express 2008 R2 installasjon... 2 3 Etter installasjon... 4 3.1 SQL Express... 4 3.1.1 Nettverksoppsett

Detaljer

2018 ANNUAL SPONSORSHIP OPPORTUNITIES

2018 ANNUAL SPONSORSHIP OPPORTUNITIES ANNUAL SPONSORSHIP OPPORTUNITIES MVP SPONSORSHIP PROGRAM CALLING ALL VENDORS! Here is your chance to gain company exposure while strengthening your dealer Association at the same time. Annual Sponsorship

Detaljer

PSi Apollo. Technical Presentation

PSi Apollo. Technical Presentation PSi Apollo Spreader Control & Mapping System Technical Presentation Part 1 System Architecture PSi Apollo System Architecture PSi Customer label On/Off switch Integral SD card reader/writer MENU key Typical

Detaljer

Eclipse og RSM en god IDE?

Eclipse og RSM en god IDE? Eclipse og RSM en god IDE? Versjon 060208 med foiler også av Andreas Limyr og Gøran K. Olsen 6-Feb-06 INF2120 Prosjekt i modellering 1 Eclipse plattformen Eclipse is a kind of universal tool platform -

Detaljer

Trådløst nett UiT. Feilsøking. Wireless network UiT Problem solving

Trådløst nett UiT. Feilsøking. Wireless network UiT Problem solving Trådløst nett UiT Feilsøking Wireless network UiT Problem solving April 2016 Problemer med tilkobling til trådløsnettet Eduroam kan enten løses ved å laste ned en installasjonfil fra https://cat.eduroam.org

Detaljer

Microsoft Dynamics C5 Version 2008 Oversigt over Microsoft Reporting Services rapporter

Microsoft Dynamics C5 Version 2008 Oversigt over Microsoft Reporting Services rapporter Reporting Services - oversigt Microsoft Dynamics C5 Version 2008 Oversigt over Microsoft Reporting Services rapporter Summary Efterfølgende vises en oversigt over de rapporter som er indeholdt i Microsoft

Detaljer

Invitation to Tender FSP FLO-IKT /2013/001 MILS OS

Invitation to Tender FSP FLO-IKT /2013/001 MILS OS Invitation to Tender FSP FLO-IKT /2013/001 MILS OS April 15th 2013 Forfatter Prosjektittel 19.04.2013 19.04.2013 1 Introduction AGENDA Important aspects regarding the competition and Invitation to tender

Detaljer

Migrere fra XA 5.0 til XA 6.0

Migrere fra XA 5.0 til XA 6.0 Migrere fra XA 5.0 til XA 6.0 Stian A. Petersen Løsnings arkitekt Stian@commaxx.no Commaxx 1 Hva er forskjellen mellom oppgradering og migrering? Oppgradering Installere en nyere versjon eller utgivelse

Detaljer

Public roadmap for information management, governance and exchange. 2015-09-15 SINTEF david.norheim@brreg.no

Public roadmap for information management, governance and exchange. 2015-09-15 SINTEF david.norheim@brreg.no Public roadmap for information management, governance and exchange 2015-09-15 SINTEF david.norheim@brreg.no Skate Skate (governance and coordination of services in egovernment) is a strategic cooperation

Detaljer

BKAD-1923-BKAD-Avtalemottak-OCR Rest WS. BKAD-Avtalemottak-OCR Rest Web Service Specification Document

BKAD-1923-BKAD-Avtalemottak-OCR Rest WS. BKAD-Avtalemottak-OCR Rest Web Service Specification Document BKAD-Avtalemottak-OCR Rest Web Service Specification Document Revision Log Date Version Change Reference Author 08-12-2014 1.0 Initial document. Amit Kumar 09-12-2014 1.01 Incorporated comments of Leikny

Detaljer

Viktig informasjon om omlegging til Windows 10

Viktig informasjon om omlegging til Windows 10 ENGLISH VERSION please see page 7. Viktig informasjon om omlegging til Windows 10 IT-avdelingen 1. Meld deg på workshop her 2. Husk å fylle ut dette skjemaet i tillegg (først skriv inn brukernavn@uia.no,

Detaljer

Software applications developed for the maritime service at the Danish Meteorological Institute

Software applications developed for the maritime service at the Danish Meteorological Institute Software applications developed for the maritime service at the Danish Meteorological Institute Anne Marie Munk Jørgensen (ammj@dmi.dk), Ove Kjær, Knud E. Christensen & Morten L. Mortensen Danish Meteorological

Detaljer

Dynamic Programming Longest Common Subsequence. Class 27

Dynamic Programming Longest Common Subsequence. Class 27 Dynamic Programming Longest Common Subsequence Class 27 Protein a protein is a complex molecule composed of long single-strand chains of amino acid molecules there are 20 amino acids that make up proteins

Detaljer

Endelig ikke-røyker for Kvinner! (Norwegian Edition)

Endelig ikke-røyker for Kvinner! (Norwegian Edition) Endelig ikke-røyker for Kvinner! (Norwegian Edition) Allen Carr Click here if your download doesn"t start automatically Endelig ikke-røyker for Kvinner! (Norwegian Edition) Allen Carr Endelig ikke-røyker

Detaljer

Prosjektet Digital kontaktinformasjon og fullmakter for virksomheter Digital contact information and mandates for entities

Prosjektet Digital kontaktinformasjon og fullmakter for virksomheter Digital contact information and mandates for entities Prosjektet Digital kontaktinformasjon og fullmakter for virksomheter Digital contact information and mandates for entities Nordisk Adressemøte / Nordic Address Forum, Stockholm 9-10 May 2017 Elin Strandheim,

Detaljer

EN Skriving for kommunikasjon og tenkning

EN Skriving for kommunikasjon og tenkning EN-435 1 Skriving for kommunikasjon og tenkning Oppgaver Oppgavetype Vurdering 1 EN-435 16/12-15 Introduction Flervalg Automatisk poengsum 2 EN-435 16/12-15 Task 1 Skriveoppgave Manuell poengsum 3 EN-435

Detaljer

IBM Endpoint Manager. OS Deployment V3.8 User's Guide - Draft for Beta V1.1 (Do not distribute)

IBM Endpoint Manager. OS Deployment V3.8 User's Guide - Draft for Beta V1.1 (Do not distribute) IBM Endpoint Manager OS Deployment V3.8 User's Guide - Draft for Beta V1.1 (Do not distribute) IBM Endpoint Manager OS Deployment V3.8 User's Guide - Draft for Beta V1.1 (Do not distribute) Note Before

Detaljer

Tilpasning av Windows 2000 server til Skolelinux tynnklienttjener

Tilpasning av Windows 2000 server til Skolelinux tynnklienttjener Tilpasning av Windows 2000 server til Skolelinux tynnklienttjener Bernt Johnsen, Ski videregående skole Ragnar Wisløff, LinuxLabs AS November 2004 Innholdsliste Innledning...2 Ansvarsfraskrivelse...2 Endringer

Detaljer

Brukers Arbeidsflate. Tjeneste Katalog. Hva vi leverer... Presentasjon Administrasjon Automatisering

Brukers Arbeidsflate. Tjeneste Katalog. Hva vi leverer... Presentasjon Administrasjon Automatisering Tjeneste Katalog Kunde Sluttbruker Hva vi leverer... Kjøkken IT Avdeling Presentasjon Administrasjon Automatisering Brukers Arbeidsflate Fast tidsramme Prosjektutfordringer + Fast budsjett Dårlig kvalitet

Detaljer

EXAM TTM4128 SERVICE AND RESOURCE MANAGEMENT EKSAM I TTM4128 TJENESTE- OG RESSURSADMINISTRASJON

EXAM TTM4128 SERVICE AND RESOURCE MANAGEMENT EKSAM I TTM4128 TJENESTE- OG RESSURSADMINISTRASJON Side 1 av 5 NTNU Norges teknisk-naturvitenskapelige universitet Institutt for telematikk EXAM TTM4128 SERVICE AND RESOURCE MANAGEMENT EKSAM I TTM4128 TJENESTE- OG RESSURSADMINISTRASJON Contact person /

Detaljer

Brukerdokumentasjon Brukerdokumentasjon

Brukerdokumentasjon Brukerdokumentasjon Brukerdokumentasjon Brukerdokumentasjon 2 Brukerveiledning For en som skal ta en test: For den som skal ta en test er det mening at en bruksanvisning skal være unødvendig. De få informasjonene som en bruker

Detaljer

En praktisk anvendelse av ITIL rammeverket

En praktisk anvendelse av ITIL rammeverket NIRF 17. april 2012 En praktisk anvendelse av ITIL rammeverket Haakon Faanes, CIA,CISA, CISM Internrevisjonen NAV NAVs ITIL-tilnærming - SMILI NAV, 18.04.2012 Side 2 Styring av tjenestenivå Prosessen omfatter

Detaljer

INSTALLATION GUIDE FTR Cargo Rack Regular Ford Transit 130" Wheelbase ( Aluminum )

INSTALLATION GUIDE FTR Cargo Rack Regular Ford Transit 130 Wheelbase ( Aluminum ) INSTALLATION GUIDE 1505-FTR Cargo Rack Regular Ford Transit 130" Wheelbase ( Aluminum ) QUICK START GUIDE Phase 1 - Assembly q 1.1 Setup... q 1.2 Cargo Rack Assembly... 3-4 5-6 Phase 2 - Installation q

Detaljer

6105 Windows Server og datanett

6105 Windows Server og datanett 6105 Windows Server og datanett Labøving: Deling av mapper, filer og skrivere i arbeidsgruppe Oppgavebeskrivelse Her forklares kort hva øvingen går ut på for de som ønsker å finne løsningen selv. Hvis

Detaljer

Innholdsfortegnelse... 1 Endringslogg UD BETALINGSTERMINAL NETS NEW DRIVERS FULL SUPPORT WINDOWS

Innholdsfortegnelse... 1 Endringslogg UD BETALINGSTERMINAL NETS NEW DRIVERS FULL SUPPORT WINDOWS ENDRINGSLOGG INNHOLDSFORTEGNELSE Innholdsfortegnelse... 1 Endringslogg 2017.151.1... 3 UD-17.136 BETALINGSTERMINAL NETS NEW DRIVERS FULL SUPPORT WINDOWS 10... 3 UD-17.137 UTESTÅENDE NOT SHOWIN CROSSED

Detaljer

Moving Objects. We need to move our objects in 3D space.

Moving Objects. We need to move our objects in 3D space. Transformations Moving Objects We need to move our objects in 3D space. Moving Objects We need to move our objects in 3D space. An object/model (box, car, building, character,... ) is defined in one position

Detaljer

1 User guide for the uioletter package

1 User guide for the uioletter package 1 User guide for the uioletter package The uioletter is used almost like the standard LATEX document classes. The main differences are: The letter is placed in a \begin{letter}... \end{letter} environment;

Detaljer

Trigonometric Substitution

Trigonometric Substitution Trigonometric Substitution Alvin Lin Calculus II: August 06 - December 06 Trigonometric Substitution sin 4 (x) cos (x) dx When you have a product of sin and cos of different powers, you have three different

Detaljer

XML enabled database. support for XML in Microsoft SQL Server 2000 & Martin Malý

XML enabled database. support for XML in Microsoft SQL Server 2000 & Martin Malý XML enabled database support for XML in Microsoft SQL Server 2000 & 2005 Martin Malý martin@php-compiler.net Agenda Three ways of approach Microsoft SQL 2000 Storing XML as text SQLXML FOR XML command

Detaljer

User Guide

User Guide User Guide Micro USB port Back up new data Restore previously backed up data More settings Enable or disable a SIM card Select 4G/3G SIM Select default SIM for data services Configure SIM

Detaljer

INSTALLATION GUIDE FTR Cargo Rack Regular Ford Transit 130" Wheelbase ( Aluminum )

INSTALLATION GUIDE FTR Cargo Rack Regular Ford Transit 130 Wheelbase ( Aluminum ) INSTALLATION GUIDE 1505-FTR Cargo Rack Regular Ford Transit 130" Wheelbase ( Aluminum ) QUICK START GUIDE Phase 1 - Assembly q 1.1 Setup... q 1.2 Cargo Rack Assembly... 3-4 5-6 Phase 2 - Installation q

Detaljer

TB-615 / TB-617 Wireless slim keyboard. EN User guide SE Användarhandledning FI Käyttöohje DK Brugervejledning NO Bruksanvisning

TB-615 / TB-617 Wireless slim keyboard. EN User guide SE Användarhandledning FI Käyttöohje DK Brugervejledning NO Bruksanvisning TB-615 / TB-617 Wireless slim keyboard EN User guide SE Användarhandledning FI Käyttöohje DK Brugervejledning NO Bruksanvisning EN User guide You have bought a wireless keyboard to use with Windows XP,

Detaljer

Advanced Technologies of Microsoft SharePoint 2016

Advanced Technologies of Microsoft SharePoint 2016 Advanced Technologies of Microsoft SharePoint 2016 Varighet: 5 Days Kurskode: M20339-2 Opplæringsmetoder: Virtuell opplæring Beskrivelse: In this course, you will learn how to plan, configure, and manage

Detaljer

Call function of two parameters

Call function of two parameters Call function of two parameters APPLYUSER USER x fµ 1 x 2 eµ x 1 x 2 distinct e 1 0 0 v 1 1 1 e 2 1 1 v 2 2 2 2 e x 1 v 1 x 2 v 2 v APPLY f e 1 e 2 0 v 2 0 µ Evaluating function application The math demands

Detaljer

GeWare: A data warehouse for gene expression analysis

GeWare: A data warehouse for gene expression analysis GeWare: A data warehouse for gene expression analysis T. Kirsten, H.-H. Do, E. Rahm WG 1, IZBI, University of Leipzig www.izbi.de, dbs.uni-leipzig.de Outline Motivation GeWare Architecture Annotation Integration

Detaljer

Neural Network. Sensors Sorter

Neural Network. Sensors Sorter CSC 302 1.5 Neural Networks Simple Neural Nets for Pattern Recognition 1 Apple-Banana Sorter Neural Network Sensors Sorter Apples Bananas 2 Prototype Vectors Measurement vector p = [shape, texture, weight]

Detaljer

Om Samba/fildeling. Hans Nordhaug Institutt for informatikk Høgskolen i Molde

Om Samba/fildeling. Hans Nordhaug Institutt for informatikk Høgskolen i Molde Om Samba/fildeling Hans Nordhaug Institutt for informatikk Høgskolen i Molde 13.09.2016 Tema 1 Introduksjon Om SMB/CIFS Om Samba Hvorfor Samba? 2 Generelt Delte ressurser Om protokollen SMB (CIFS) SMB

Detaljer

Diet Tracking Software Guide. Simon Lovell. Lunchbox Diet Online - Getting Started Guide

Diet Tracking Software Guide. Simon Lovell. Lunchbox Diet Online - Getting Started Guide Diet Tracking Software Guide Simon Lovell 1 WELCOME 2 SIGNING IN TO YOUR ACCOUNT 3 PROFILE INFORMATION 3.1 Please Update Your Profile Wizard 3.2 Setup and Preferences 3.3 Manage Body Statistics 3.4 Manage

Detaljer

DecisionMaker Frequent error codes (valid from version 7.x and up)

DecisionMaker Frequent error codes (valid from version 7.x and up) DecisionMaker Frequent error codes (valid from version 7.x and up) DM Frequent Error Codes Bisnode Credit IT 03.02.2014 1 (5) CONTENTS 1 Target... 3 2 About this document... 3 3 Error codes an messages...

Detaljer

Feilmelding Årsak Løsning

Feilmelding Årsak Løsning Request for the permission of type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed Feil oppstod i Window.DialogWindow:

Detaljer

SJEKKESKOLEN: EN STEG-FOR-STEG GUIDE TIL TILTREKNING AV FANTASTISKE JENTER (NORWEGIAN EDITION) BY ANDREAS GODE VIBBER

SJEKKESKOLEN: EN STEG-FOR-STEG GUIDE TIL TILTREKNING AV FANTASTISKE JENTER (NORWEGIAN EDITION) BY ANDREAS GODE VIBBER Read Online and Download Ebook SJEKKESKOLEN: EN STEG-FOR-STEG GUIDE TIL TILTREKNING AV FANTASTISKE JENTER (NORWEGIAN EDITION) BY ANDREAS GODE VIBBER DOWNLOAD EBOOK : SJEKKESKOLEN: EN STEG-FOR-STEG GUIDE

Detaljer

Om Samba/fildeling. Hans Nordhaug 17.09.2013. Institutt for informatikk Høgskolen i Molde

Om Samba/fildeling. Hans Nordhaug 17.09.2013. Institutt for informatikk Høgskolen i Molde Om Samba/fildeling Hans Nordhaug Institutt for informatikk Høgskolen i Molde 17.09.2013 Tema 1 Introduksjon Om SMB Om Samba Hvorfor Samba? 2 Generelt Delte ressurser Server Message Block En protokoll for

Detaljer

20.01.2012. Brukerkrav og use case diagrammer og -tekst 19. januar 2012. Agenda. Brukerkrav og use case. Diagrammer Tekst.

20.01.2012. Brukerkrav og use case diagrammer og -tekst 19. januar 2012. Agenda. Brukerkrav og use case. Diagrammer Tekst. Brukerkrav og use case diagrammer og -tekst 19. januar 2012 Agenda Brukerkrav og use case Diagrammer Tekst Praktisk eksempel 1 OOAD i livsløpsperspektiv Krav Design Konstruksjon Her er vi i nå Testing

Detaljer

E-learning opportunities for JSEC prototype 1

E-learning opportunities for JSEC prototype 1 E-learning opportunities for JSEC prototype 1 Katerina Zdravkova Vangel Ajanovski Characteristics of the prototype Based on.net Framework Enables dynamic exchange of the contents Maintainable Extendable

Detaljer

Innovasjonsvennlig anskaffelse

Innovasjonsvennlig anskaffelse UNIVERSITETET I BERGEN Universitetet i Bergen Innovasjonsvennlig anskaffelse Fredrikstad, 20 april 2016 Kjetil Skog 1 Universitetet i Bergen 2 Universitetet i Bergen Driftsinntekter på 4 milliarder kr

Detaljer

IBM Tivoli zenterprise Monitoring Agent Version User s Guide SC

IBM Tivoli zenterprise Monitoring Agent Version User s Guide SC IBM Tivoli zenterprise Monitoring Agent Version 6.2.3 User s Guide SC14-7359-00 IBM Tivoli zenterprise Monitoring Agent Version 6.2.3 User s Guide SC14-7359-00 Note Before using this information and the

Detaljer

Start MATLAB. Start NUnet Applications Statistical and Computational packages MATLAB Release 13 MATLAB 6.5

Start MATLAB. Start NUnet Applications Statistical and Computational packages MATLAB Release 13 MATLAB 6.5 Start MATLAB Start NUnet Applications Statistical and Computational packages MATLAB Release 13 MATLAB 6.5 Prompt >> will appear in the command window Today: MATLAB overview In-class HW: Chapter 1, Problems

Detaljer

Citation and reference tools for your master thesis

Citation and reference tools for your master thesis Citation and reference tools for your master thesis Verktøy for å håndtere siteringer og referanser i masteroppgaven 1 Citations and references The citation goes into the body text and points to the full

Detaljer

Norsk (English below): Guide til anbefalt måte å printe gjennom plotter (Akropolis)

Norsk (English below): Guide til anbefalt måte å printe gjennom plotter (Akropolis) Norsk (English below): Guide til anbefalt måte å printe gjennom plotter (Akropolis) 1. Gå til print i dokumentet deres (Det anbefales å bruke InDesign til forberedning for print) 2. Velg deretter print

Detaljer

Øystein Haugen, Professor, Computer Science MASTER THESES Professor Øystein Haugen, room D

Øystein Haugen, Professor, Computer Science MASTER THESES Professor Øystein Haugen, room D Øystein Haugen, Professor, Computer Science MASTER THESES 2015 Professor Øystein Haugen, room D1-011 1 Hvem er jeg? Øystein Haugen, nytilsatt professor i anvendt informatikk på Høyskolen i Østfold, avdeling

Detaljer

Grunnlag: 11 år med erfaring og tilbakemeldinger

Grunnlag: 11 år med erfaring og tilbakemeldinger Antenor Management System v5 Grunnlag: 11 år med erfaring og tilbakemeldinger Antenor Management System v5 AMS v5 første versjon lanseres 13. november 100% uavhengig plattform 100% dedikert til Quality

Detaljer

IBM. Advanced Settings Utility, v9.63 User's Guide

IBM. Advanced Settings Utility, v9.63 User's Guide IBM Advanced Settings Utility, v9.63 User's Guide Version 9.63 IBM Advanced Settings Utility, v9.63 User's Guide Version 9.63 Note Before using this information and the product it supports, read the information

Detaljer