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

Transkript

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

2 Note Before using this information and the product it supports, read the information in Notices on page 67. 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 v Intended audience v Network and Service Assurance community on Service Management Connect v Tivoli technical training v Support information v Conventions used in this publication vi Typeface conventions vi Chapter 1. Introduction Model Maker components Enhancements to Model Maker, Version 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. 7 Configuring Tivoli Common Reporting for DB2 connections Configuring the Tivoli Common Reporting data source Creating the required table spaces on DB2 database Configuring the prerequisite software on the Windows computer Verifying the Java version and PATH Preinstallation tasks Transferring installation files by using the FTP protocol Changing permissions on the executable file... 9 Creating the bicontrol user Running the installer The logins file Verifying the Common Pack Service installation.. 15 Troubleshooting the installation Uninstalling the Common Pack Service 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 wireline database preferences.. 22 Configuring automatic updates and notifications 23 Configuring the software update site Configuring the Cognos preferences Chapter 5. The Base Common Pack Suite Chapter 6. Installing common packs.. 29 Overview of installing common packs for pack administrators Adding a common pack to the repository Adding multiple common packs to the repository 30 Adding common packs by using the CLI Activating common packs in the repository Activating common packs by using the CLI.. 32 Populating the calendar schema table for TCR Time 32 Downloading common packs Publishing a common pack Listing common packs in the repository Uninstalling common packs Removing common packs from the repository.. 35 Removing downloaded common packs from the Windows computer Chapter 7. Troubleshooting Model Maker and Common Reporting Data modeling and Model Maker issues Errors when you run the pack_admin command for calendar refill Common Pack Service installation fails on Tivoli Netcool Performance Manager server that is installed with non-default path Always use the HTTP protocol for the update site Slow download of common packs CTGTRR1104E Cannot open an administrative database connection (Wireline) Issue when extending a model by using the pm.inventory.getresources DAL query. 39 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 Copyright IBM Corp. 2011, 2013 iii

4 Cannot resize the Common Reporting window in Internet Explorer Infinitely expanding resources in the Report Studio hierarchy CSV export is not supported for reports containing multiple tables The CSV file extension is.xls instead of.csv.. 43 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 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 (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.. 47 (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. 48 (Wireline) Exporting a PDF returns an error when the report has no data charts 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 Appendix C. Creating a logins file with the appropriate passwords Notices Glossary Index Appendix A. Configuring communications between the Common Pack Service and the Common Pack Service Client Configuring nonsecure communications iv IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

5 About this information Intended audience The IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide describes how to install and use Model Maker on a IBM Tivoli Netcool Performance Manager system with IBM DB2 as the database support. This publication 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 v IBM DB2 database Network and Service Assurance community on Service Management Connect Tivoli technical training Connect, learn, and share with Service Management professionals: product support technical experts who provide their perspectives and expertise. Access Service Management Connect at servicemanagement/nsa/index.html. Use Service Management Connect in the following ways: v v v v Support information 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. Connect one-on-one with the experts to collaborate and network about Tivoli and the Network and Service Assurance community. Read blogs to benefit from the expertise and experience of others. Use wikis and forums to collaborate with the broader user community. For Tivoli technical training information, see the following IBM Tivoli Education 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, 2013 v

6 Online Access the IBM Software Support site at support/probsub.html. IBM Support Assistant The IBM Support Assistant is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. The Support Assistant provides quick access to support-related information and serviceability tools for problem determination. To install the Support Assistant software, go to support/isa. Troubleshooting Guide For more information about resolving problems, see the problem determination information for this product. Conventions used in this publication Several conventions are used in this publication for special terms, actions, commands, and paths that are dependent on your operating system Typeface conventions This publication uses the following typeface conventions: Bold Italic 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 vi IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

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

8 viii IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

9 Chapter 1. Introduction Model Maker components Common packs extend technology pack 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 wireline 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 The Common Pack Service v The Base Common Packs (BCP). The Tivoli Netcool Performance Manager requires two BCPs; Wireline Common and TCR Time The TCR Time is packaged with the distribution media. Wireline Common can be downloaded form the latest Base Common Pack Suite ( TIV-TNPM- BCPSUITE-FP0001) that is available as a separate download from IBM Fix Central from here: 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 functionality 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,

10 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. The Common Pack Service in this release is modified to support DB2 as the database for Tivoli Netcool Performance Manager system. 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 Install and manage wireline common packs on Tivoli Netcool Performance Manager systems. 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 related to specific technologies. v v The TCR Time BCP is a dependent pack for all common packs, both for the Tivoli Netcool Performance Manager Wireless and Wireline Components. The Wireline Common BCP is a dependent pack for all wireline common packs. Enhancements to Model Maker, Version Organization Enhancements to Model Maker, Version IBM Tivoli Netcool Performance Manager Model Maker, Version has the following enhancements: Support for DB2 as the database Model Maker has support for DB2 as the database that was released with Tivoli Netcool Performance Manager for wireline component only. 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 5 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 7 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 21 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 27 2 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

11 For all users, this chapter describes the Base Common Packs and how to install the Base Common Packs. v Chapter 6, Installing common packs, on page 29 For all users, this chapter describes how to install a common pack on a Tivoli Netcool Performance Manager wireline or wireless system. v Chapter 7, Troubleshooting Model Maker and Common Reporting, on page 37 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 49 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 55 For all users, this chapter provides a command reference for Model Maker commands. v Glossary on page 71 For all users, this chapter includes Model Maker terms and definitions. Planning for your data requirements The installation steps are different depending on which of the following installation options you chose: 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. Chapter 1. Introduction 3

12 4 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

13 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 Wireline Component Tivoli Integrated Portal 2.2 or 2.1 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 IBM DB2 Data Server 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. 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 for DB2 support. The following database users are created during the installation: v tcraccess v bicontrol v birefresh Copyright IBM Corp. 2011,

14 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. For more information, see the Tivoli Common Reporting documentation at com.ibm.tivoli.tcr.doc_21/ttcr_installing_fm.html. DB2 Client Framework Manager requires an ODBC connection to import and use an DB2 data source. For DB2 ODBC, the DB2 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. 6 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

15 Chapter 3. Installing and configuring the Common Pack Service Complete the following tasks to install and configure the Common Pack Service. 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 DB2 connections About this task The configuration steps are different depending on what data you must access; wireline data, or wireless and wireline data. For more information, see Planning for your data requirements on page 3. Procedure 1. Log in to the Tivoli Common Reporting server. 2. Edit the starttcrserver.sh script. 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, and /opt/ibm/tivoli/ tip21components for wireline. 3. 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 DB2 installation and the values that are shown reflect those of a default DB2 installation. # # Setup for Cognos DB2 Environment # LIBPATH=/opt/IBM/tivoli/tip21Components/TCRComponent/cognos/bin:$LIBPATH export LIBPATH PATH=$PATH:/opt/IBM/tivoli/tip21Components/TCRComponent/cognos/bin export PATH. /opt/db2/sqllib/db2profile 4. 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 Copyright IBM Corp. 2011,

16 Configuring the Tivoli Common Reporting data source You must configure a Tivoli Common Reporting data source connection to connect to a DB2 database that contains Tivoli Netcool Performance Manager data. Procedure 1. Log on to the Tivoli Common Reporting server. For example: 2. Click Reporting > Common Reporting. 3. Click Launch > Administration. 4. On the Configuration tab, add a 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 DB2 and click Next. c. In the Specify the DB2 connection string page, enter PV as the DB2 database name. d. In the DB2 connect string filed, enter jdbc:db2://<hostname>:50000/pv. Where: Parameter db2 hostname Description Default database instance name. Tivoli Integrated Portal server hostname or IP address Default port number used for DB2. PV Default database name for Tivoli Netcool Performance Manager. e. In the Signons section, enter tcraccess/tcraccess for the user ID and password. f. Select the Password check box and click Finish. g. Test the new data source after the Common Pack Service is installed. Creating the required table spaces on DB2 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 DB2 database server as the db2 user. 2. Connect to the database as the PV_ADMIN user by entering the following command: db2 connect to pv user pv_admin using PV 3. Create a bufferpool bp_8k with page size 8Kbyusing the following command: db2 create bufferpool bp_8k pagesize 8k 4. Create the wm_flexpm table space by entering the following command in one line: db2 create tablespace WM_FLEXPM pagesize 8k bufferpool bp_8k 5. Create the temp table space by entering the following command on one line: db2 create tablespace temp pagesize 8k bufferpool bp_8k 8 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

17 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. 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>_lin_db2.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 9

18 Procedure 1. Create the bicontrol user by using the following command as the database administrator. db2 "call db2auth.add_user_pl( bicontrol, bicontrol,?,?,?)"; 2. Assign privileges to user bicontrol by using the following command db2 GRANT CONNECT,CREATETAB,DBADM,SECADM,ACCESSCTRL,DATAACCESS, EXPLAIN,SQLADM ON DATABASE TO USER bicontrol; 3. Connect to database as bicontrol user by running the following command: db2 connect to PV user bicontrol using bicontrol 4. Create the default schema for bicontrol user by using the following command: db2 CREATE SCHEMA bicontrol AUTHORIZATION bicontrol; 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 3. 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./commonpackserviceinstall-<version>_lin_db2.sh The installer starts and the license agreement is displayed: 10 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

19 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/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/tipv21 TIP Administrator User Name (DEFAULT: tipadmin): tipadmin TIP Administrator Password:********* 8. Enter the directory where the Tivoli Integrated Portal components are installed. By default, /opt/ibm/tivoli/tip21components for wireline. TIP Components Installation Directory (DEFAULT: /opt/ibm/tivoli/tip21components): /opt/ibm/tivoli/tip21components The Common Pack Service is installed at $TIP_COMPONENTS_LOCATION/ TCRComponent/commonpackservice. Chapter 3. Installing and configuring the Common Pack Service 11

20 9. Enter the directory where the DB2 client is installed. For example, /opt/db2/product/10.1.0/java. Note: If you do not have DB2 installed, then the database client directory must be path to the folder that contains DB2 JDBC driver library that is db2jcc4.jar. 10. Enter the JDBC URL for the administrative database. 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.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. ----Database Connection---- Database Client Directory: /opt/db2/product/10.1.0/java Administrative Database JDBC URL (jdbc:db2://<hostname>:50000/pv): jdbc:db2://<hostname>:50000/pv Administrative Database BICONTROL User Name (DEFAULT: BICONTROL): bicontrol Administrative Database BICONTROL User Password: Administrative Database Objects TableSpace Name (DEFAULT: wm_flexpm):wm_flexpm 14. Enter N to enable outer join or enter Y 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)? (Y/N): N Note: This feature is applicable for Wireless component only. On successful connection to the database, the Preinstallation Summary is displayed as follows assuming a wireline installation. 12 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

21 =============================================================================== Preinstallation Summary Please Review the Following Before Continuing: Product Name: Common Pack Service Installation Folder /opt/ibm/tivoli/tip21components/tcrcomponent TIP Installation Directory /opt/ibm/tivoli/tip21 TIP Version Installed TIP Administrator User Name tipadmin Database Client Directory /opt/db2/product/10.1.0/java Administrative Database JDBC URL jdbc:db2://<hostname>:50000/pv Administrative Database BICONTROL User Name bicontrol Administrative Database Objects TableSpace Name wm_flexpm Target Database JDBC URL jdbc:db2://<hostname>:50000/pv Disk Space Information (for Installation Target): Required: 32,988,559 bytes Available: 96,234,831,872 bytes 15. 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/tip21components/tcrcomponent PRESS <ENTER> TO EXIT THE INSTALLER: Chapter 3. Installing and configuring the Common Pack Service 13

22 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: 16. 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 15. 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 Test the datasource connection as described in Configuring the Tivoli Common Reporting data source on page 8. If the installation is unsuccessful, see the Troubleshooting the installation on page 16 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. 14 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

23 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. If you change the DB2 tcraccess user password, then you must also change the Cognos tcraccess data source. If you change the DB2 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. For more information about creating a logins file, see Appendix C, Creating a logins file with the appropriate passwords, on page 65. 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. Chapter 3. Installing and configuring the Common Pack Service 15

24 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 technical note in the Support knowledge base at 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/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_COMPONENTS_LOCATION>/TCRComponent/ Common_Pack_Service_InstallLog.log file for Common Pack Service installation failures. By default, <TIP_COMPONENTS_LOCATION> is /opt/ibm/tivoli/ tip21components. 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 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

25 Uninstalling the Common Pack Service Complete the following tasks to uninstall the Common Pack Service. 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/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. Chapter 3. Installing and configuring the Common Pack Service 17

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

27 =============================================================================== 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. Chapter 3. Installing and configuring the Common Pack Service 19

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

29 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,

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

31 Option JDBC Driver Path Description The full path to the database driver implementation used to connect to the database instance. For example, db2 library db2jcc4.jar path. 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 name, typically PV. A database user, typically the pv_admin user. 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. Chapter 4. Installing and configuring Model Maker Manager 23

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

33 Option Password Namespace Description 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 25

34 26 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

35 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. 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 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. For current version information about the Base Common Pack Suite, see the Known issues with Tivoli Netcool Performance Manager technical note in the Support Knowledge Base. Copyright IBM Corp. 2011,

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

37 Chapter 6. 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. About this task 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. 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 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 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. 3. Add the TCR Time BCP. See Adding a common pack to the repository on page Activate the TCR Time BCP. See Activating 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. See Populating the calendar schema table for TCR Time on page Add and activate any dependent packs. If there are multiple dependent packs, you must activate them in a particular sequence as directed in the pack documentation. 7. Add and activate the common pack. Copyright IBM Corp. 2011,

38 8. Download the activated common pack into Model Maker Manager. See Downloading common packs on page Publish the common pack by using Model Maker Manager to a Report Package available for reporting. The contents of the common pack are published as a report package to the Content Store on the Tivoli Common Reporting server. See Publishing a common pack on page 34. Adding a common pack to the repository You can add a common pack to the common pack repository by using the Add Common Packs command. Adding a common pack adds the common pack to the administrative database and registers that version of the common pack with the system. That version of the 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. Copy the file back to your PC before starting 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 common packs to the repository You can add multiple common packs to the repository by using the Add Common Packs from a Directory command. This service loads all 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. 30 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

39 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. 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 common packs by using the CLI You can also use the pack_admin command to add common packs to the common pack repository. Procedure Add a common pack or multiple common packs by completing the following steps: 1. Add a common pack. For example, add the ibm.tcr.time common pack by entering the following command:./pack_admin.sh -add -pack ibm.tcr.time jar -logins./logins.txt CTGTRR232I The operation add successfully performed. 2. Optional: Add multiple 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 common packs in the repository You can activate a common pack or composite 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. 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 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 common pack to activate. 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. Chapter 6. Installing common packs 31

40 Activating common packs by using the CLI You can also use the pack_admin command to activate common packs to update the database schemas. Procedure Activate the common pack to create the associated database schema. For example, activate the ibm.tcr.time 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. 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: TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default, /opt/ibm/tivoli/tip21components for wireline. 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 32 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

41 Downloading common packs 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. To publish common packs, download the common pack models from the Common Pack Service to your local instance of the Model Maker Manager. About this task When publishing common packs, download each pack from the Common Pack Service before publishing to ensure that only the correctly activated common packs are published. 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. 6. Click Finish. Chapter 6. Installing common packs 33

42 Publishing a common pack You must publish a common pack to the Tivoli Common Reporting server to make a Report Package available for reporting. Any data sources defined in the common pack are also made available in Tivoli Common Reporting. Before you begin Download each pack from the Common Pack Service before publishing. If the Cognos Framework Manager BMT Script Player has not already been configured, you must configure it during this task. Procedure 1. Select one or more common packs from the Common Pack Models tab. 2. Right-click on your selection. 3. From the menu, select the Publish to default package option. If the BMT Script Player was not previously configured, the Preferences window opens for you to enter the required details. 4. When prompted, enter the database user password. A window is displayed showing that the pack is being published. If the wireline database was not previously configured, the Preferences window opens for you to enter the required details. 5. A Report Package is created and published to the Tivoli Common Reporting server. On completion, a summary window is displayed with a completion message and the number of artifacts published, if any. 6. Optional: Log on to the Tivoli Common Reporting server to see your published model and reports. Results The package is now available on the Tivoli Common Reporting server and accessible from the Common Reporting UI. Any data sources defined in the common pack are also available in Tivoli Common Reporting. 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. 34 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

43 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. Removing downloaded common packs from the Windows computer Downloaded common packs are stored on the Windows computer and managed by Model Maker Manager. To remove common packs from Manager and your computer, you must uninstall and reinstall Manager, and download the packs again. 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. Procedure 1. Make a note of the common packs you have installed. 2. Uninstall Manager by deleting the folder containing the Manager files. 3. Reinstall Manager. 4. Download each of the common packs you need. Chapter 6. Installing common packs 35

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

45 Chapter 7. 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. Errors when you run the pack_admin command for calendar refill When you populate the calendar schema table for TCR Time by using the pack_admin command, you might encounter some errors. Symptoms When you populate the calendar schema table for TCR Time by using the pack_admin command, you might encounter some errors. Resolving the problem To resolve this issue, follow these steps: 1. Log in to DB2 server as user db2. 2. Connect to database PV by using the following command: db2 connect to PV 3. Check logging configuration by using command, db2 get db cfg for pv grep -i log 4. Check value of LOGFILSIZ. By default the log file size is 8192 KB. To resolve, you need to reconfigure these properties. 5. Set the log file size (LOGFILSIZ) to 9126 KB by using the following command: db2 update db cfg for pv using LOGFILSIZ Stop the DB2 server by using the following command: db2stop force 7. Restart the DB2 server by using the following command: db2start 8. Backup the DB2 server to resolve pending update status by using the following command: Copyright IBM Corp. 2011,

46 db2 backup database PV to <Backup location path> compress 9. Stop and start the Tivoli Common Reporting. 10. Rerun calender refill command. For more information about populating the calendar schema table for TCR Time, see Populating the calendar schema table for TCR Time on page 32. Common Pack Service installation fails on Tivoli Netcool Performance Manager server that is installed with non-default path Symptoms Common Pack Service installation fails on Tivoli Netcool Performance Manager server that is installed with non-default path. Resolving the problem To resolve this issue, follow these steps: 1. If DB2 is installed in non-default location, then user needs to create a soft link to point the non-default path to the default directory. For example, if you install DB2 in /ibm/db2/product/ path instead of the default /opt/db2/product/ path, then create a soft link by using the following command: ln -s /ibm/db2 /opt/db2 2. If Tivoli Integrated Portal or Tivoli Common Reporting is installed in non-default location, then create a soft link to point the non-default path as the default directory. For example, Tivoli Integrated Portal ortivoli Common Reporting is installed in /ibm/tivoli/ path instead of the default opt/ibm/tivoli path, create a soft link by using the following command: ln -s /ibm/tivoli /opt/ibm/tivoli 3. Perform both Step 1 and Step 2, if DB2 and Tivoli Integrated Portal or Tivoli Common Reporting are installed into non-default locations. 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. 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: 38 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

47 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>./starttcrserver.sh Where TIP_COMPONENTS_LOCATION is the location where the Tivoli Integrated Portal Components are installed, by default for wireless and /opt/ibm/tivoli/ tip21components for wireline. (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: Chapter 7. Troubleshooting Model Maker and Common Reporting 39

48 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>'))+' 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??)} # 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. Resolving the problem Contact your DBA to unlock the user. 40 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

49 Reporting issues 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: 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 Chapter 7. Troubleshooting Model Maker and Common Reporting 41

50 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. Resolving the problem If you need to resize the Common Reporting window, consider using Mozilla Firefox. 42 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

51 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. 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 Chapter 7. Troubleshooting Model Maker and Common Reporting 43

52 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. Null aggregation is not supported in Common Reporting Null aggregation is not supported in Common Reporting on Tivoli Netcool Performance Manager. 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 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

53 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 You can ignore these errors as these errors do not interrupt the start and stop scripts. (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. Chapter 7. Troubleshooting Model Maker and Common Reporting 45

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

55 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 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 Chapter 7. Troubleshooting Model Maker and Common Reporting 47

56 v NOC Reporting~Devices~Interfaces 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. 48 IBM Tivoli Netcool Performance Manager: Model Maker Installation and User Guide

57 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,

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

59 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 51

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