IBM. Installing and Configuring Operations and Engineering Dashboards

Transcription

1 IBM Tioli Netcool Performance Manager Operations and Engineering Dashboards Document Reision R2E2 Installing and Configuring Operations and Engineering Dashboards IBM

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

3 Contents Installing and configuring Operations and Engineering Dashboards..... Intended audience Organization Serice Management Connect Tioli Netcool Performance Manager technical training i Support information i Conentions used in this publication i Typeface conentions i Chapter 1. Introduction Operations and Engineering Dashboards application architecture Chapter 2. Requirements Hardware requirements Software requirements Prerequisite Technology Packs Chapter 3. Preparing your enironment 9 Installation scenarios Downloading and extracting the software Copying the use case files Copying the wireless use cases files Copying the Geographic Eent Performance System use case files Copying wireline use case files Editing the tnpmoedconfig.ini file Contents of tnpmoedconfig.ini file Proisioning user-defined counters (UDCs) and summaries Obtaining the Network ID Adding Region and sysname properties Running the Operations and Engineering Dashboards installer Configuring the Wireline web serice on WebSphere Application Serer Chapter 5. Installing Geographic Eent Performance System dashboard Installing the MongoDB database Installing the Geographic Eent Performance System package Configuring the Geographic Eent Performance System web serice on WebSphere Application Serer Loading the data files Mapping the Alarm Summary dashboard JSON files 39 Chapter 6. Postinstallation tasks Integrating Operations and Engineering Dashboards on Dashboard Application Serices Hub (Optional) Updating the Network ID Enabling Jaa 1.7 on WebSphere Application Serer 43 Chapter 7. Uninstalling Operations and Engineering Dashboards Uninstalling Operations and Engineering Dashboards application Uninstalling summaries and UDCs Notices Trademarks Terms and conditions for product documentation.. 52 Chapter 4. Installing Operations and Engineering Dashboards application.. 25 High-leel installation tasks Copyright IBM Corp. 2016, 2017 iii

4 i Installing and Configuring Operations and Engineering Dashboards

5 Installing and configuring Operations and Engineering Dashboards Intended audience Organization Use this information to install and configure IBM Tioli Netcool Performance Manager - Operations and Engineering Dashboards on a Tioli Netcool Performance Manager system. This information is intended for: Users who want to install and configure Operations and Engineering Dashboards on a Tioli Netcool Performance Manager system. Readers must be familiar with the following topics: Tioli Netcool Performance Manager Wireline and Wireless concepts Tioli Netcool Performance Manager reporting concepts Tioli Netcool Performance Manager technology packs This information is organized as follows: Chapter 1, Introduction, on page 1 Chapter 2, Requirements, on page 5 Serice Management Connect Chapter 3, Preparing your enironment, on page 9 Chapter 4, Installing Operations and Engineering Dashboards application, on page 25 Chapter 6, Postinstallation tasks, on page 41 Chapter 7, Uninstalling Operations and Engineering Dashboards, on page 45 Connect, learn, and share with Serice Management professionals: product support technical experts who proide their perspecties and expertise. Access Network and Serice Assurance community at deeloperworks/sericemanagement/nsa/index.html. Use Serice Management Connect in the following ways: Become inoled with transparent deelopment, an ongoing, open engagement between other users and IBM deelopers of Tioli 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 Tioli and the Network and Serice Assurance community. Read blogs to benefit from the expertise and experience of others. Use wikis and forums to collaborate with the broader user community. Related information: Tioli Netcool Performance Manager 1.4 community on deeloperworks Copyright IBM Corp. 2016, 2017

6 Tioli Netcool Performance Manager technical training Support information For Tioli Netcool Performance Manager technical training information, see the following Tioli Netcool Performance Manager Training website at: If you hae a problem with your IBM software, you want to resole it quickly. IBM proides the following ways for you to obtain the support you need: Online Access the IBM Software Support site at support/probsub.html. IBM Support Assistant The IBM Support Assistant is a free local software sericeability workbench that helps you resole questions and problems with IBM software products. The Support Assistant proides quick access to support-related information and sericeability tools for problem determination. To install the Support Assistant software, go to support/isa. Troubleshooting Guide For more information about resoling problems, see the problem determination information for this product. Conentions used in this publication Seeral conentions are used in this publication for special terms, actions, commands, and paths that are dependent on your operating system. Typeface conentions This publication uses the following typeface conentions: Bold Italic Monospace 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) Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictie clause."; letters as letters example: "The LUN address must start with the letter L.") New terms in text (except in a definition list): a iew is a frame in a workspace that contains data. Variables and alues you must proide:... where myname represents... i Installing and Configuring Operations and Engineering Dashboards

7 Examples and code examples Bold monospace File names, programming keywords, and other elements that are difficult to distinguish from surrounding text Message text and prompts addressed to the user Text that the user must type Values for arguments or command options Command names, and names of macros and utilities that you can type as commands Enironment ariable names in text Keywords Parameter names in text: API structure parameters, command parameters and arguments, and configuration parameters Process names Registry ariable names in text Script names Installing and configuring Operations and Engineering Dashboards ii

8 iii Installing and Configuring Operations and Engineering Dashboards

9 Chapter 1. Introduction Operations and Engineering Dashboards proide enhanced isualization features for Tioli Netcool Performance Manager. Operations and Engineering Dashboards offer the following benefits: Contain modern, flexible platform with an interactie widget library capable of integrating with any data source. In Tioli Netcool Performance Manager scenario, both Wireline and Wireless data sources are supported. Proide more operational alue when compared to the existing Tioli Netcool Performance Manager reports. Proide lower cost of ownership when compared to Cognos-based reports. These dashboards do not require Tioli Common Reporting deployment and are easy to handle. Help to troubleshoot the network issues in three clicks; detect, isolate, and diagnose. Data flow architecture for Wireline component Wireline component uses the DataAccess API to retriee data from database and sends it to the DataStore Query. The JSON files take the information from the query for isualization as shown in the figure: Presentation Layer (JSON Files) Copyright IBM Corp. 2016,

10 Data flow architecture for Wireless component Wireless component uses JDBC to retriee data from database and sends it to the DataStore Query. The JSON files take the information from the query for isualization as shown in the figure: Operations and Engineering Dashboards application architecture The arious components and the data flow across all components is shown in the diagram. Planning and Optimization user Operations and Maintenance user Operations and Maintenance user JDBC 2 Installing and Configuring Operations and Engineering Dashboards

11 The Operations and Engineering Dashboards application is deployed on WebSphere Application Serer that is aailable on Dashboard Application Serices Hub. The Operations and Engineering Dashboards application proides the framework for the solution that is supported and supplemented by Wireline and Wireless technology packs in the use cases. These dashboards are accessed by the Operations and Maintenance users. The configuration of the dashboards is handled by technology-neutral JSON files. Business users can create new dashboards and customized widgets. In Wireless component, the data retrieal is through JDBC and in Wireline component, the data retrieal is with the help of DataAccess API. The H2 database stores the dashboards data. Some of the information that is stored in H2 database; the list of dashboards, users, roles, page-role mapping information, dashboard state, database queries (stores) used for dashboard pages, and so on. The information on Operations and Engineering Dashboards is rendered with the help of a serlet that takes input from the built-in JSON files. When the wireline and wireless JSON files are modified, the changes are communicated with the respectie databases to render the data based on the modified content. Chapter 1. Introduction 3

12 4 Installing and Configuring Operations and Engineering Dashboards

13 Chapter 2. Requirements Hardware requirements A complete set of requirements for Operations and Engineering Dashboards. Lists the configurations and the supported platforms and components of Operations and Engineering Dashboards on Tioli Netcool Performance Manager For requirements of Wireline and Wireless components, see the related product documentation. Hardware specifications for Operations and Engineering Dashboards. Desktop Resolution 1366 x 768 Note: For best rendering of your dashboards, iew them in maximized window mode. Related information: Software requirements Wireline requirements Wireless requirements Jazz for Serice Management Detailed System Requirements Software specifications for Operations and Engineering Dashboards. Operating system Version Wireless component 7.x Wireline component lsof utility package Supported ersion for your Operating system. Web browsers Version Mozilla Firefox ESR Google Chrome 50 Internet Explorer 11 Other supported software Version Jazz for Serice Management Copyright IBM Corp. 2016,

14 Other supported software Version WebSphere Application Serer IBM Jaa 1.8 Bundled software H2 Note: H2 database is required to store the core database tables from Operations and Engineering Dashboards. IBM Dojo Toolkit Version Port requirements Number H2 database 9408 Prerequisite Technology Packs Wireless and Wireline Technology Packs that are required to use with Operations and Engineering Dashboards. Wireline Technology Packs Cisco Deice MIB-II Cisco IP SLA Table 1. Use case-wise distribution of technology packs Use case Technology Pack Network Performance Monitoring - Deices Cisco Deice and MIB-II Network Performance Monitoring - Interfaces MIB-II Network Performance Monitoring - Links Cisco IP SLA Wireless Technology Packs GSMGPRS Huawei BSS V900R017C UMTS Huawei UTRAN V900R LTE Huawei EUTRAN V100R008C Table 2. Use case-wise distribution of technology packs Use cases Call Drop Rate (2G) Handoer Outgoing (3G) Call Drop Rate (3G) Inter RAT Success Rate (4G) Cell Aailability (4G) Call Setup Success Rate (4G) Handoer Out Success Rate (4G) Technology Pack GSMGPRS Huawei BSS V900R017C UMTS Huawei UTRAN V900R UMTS Huawei UTRAN V900R LTE Huawei EUTRAN V100R008C LTE Huawei EUTRAN V100R008C LTE Huawei EUTRAN V100R008C LTE Huawei EUTRAN V100R008C Installing and Configuring Operations and Engineering Dashboards

15 Table 2. Use case-wise distribution of technology packs (continued) Use cases Technology Pack Handoer Incoming Success Rate (4G) LTE Huawei EUTRAN V100R008C For more information about the Wireline and Wireless use cases, see Administering and Using Operations and Engineering Dashboards. Chapter 2. Requirements 7

16 8 Installing and Configuring Operations and Engineering Dashboards

17 Chapter 3. Preparing your enironment Installation scenarios Before you run the installation, prepare your target enironments. You can use different installation scenarios to help you plan and deploy Operations and Engineering Dashboards. The three installation modes are as follows: WirelessOnly WirelineOnly WirelessWireline Installation options that are aailable for different installation modes are as shown: Note: All these installation scenarios show the components that are required for Operations and Engineering Dashboards application alone. For other Wireline and Wireless component distribution, see the respectie documentation. WirelessOnly mode Wireless component that is deployed on a separate serer as Dashboard Application Serices Hub Wireless component that is deployed on the same serer as Dashboard Application Serices Hub Copyright IBM Corp. 2016,

18 WirelineOnly mode Operations and Engineering Dashboards is always installed on the serer where DataView is installed on Dashboard Application Serices Hub. WirelessWireline mode Wireline and Wireless components deployed on separate serers 10 Installing and Configuring Operations and Engineering Dashboards

19 Downloading and extracting the software Complete these tasks to install Tioli Netcool Performance Manager Operations and Engineering Dashboards application. Procedure 1. Download the CNI6GEN.tar.gz file from IBM Passport Adantage. 2. Extract the CNI6GEN.tar.gz file to a location of your choice by using this command: gzip -dc CNI6GEN.tar.gz.tar.gz tar xf - For example, /opt/ibm that is referred to as <DIST_DIR>. You can find the following archied files: oed <build_number>.tar.gz oed_geps_ <build_number>.tar.gz oed_wireless_ <build_number>.tar.gz oed_wireline_ <build_number>.tar.gz 3. Extract the oed <build_number>.tar.gz file to find the following contents: oed <build_number> directory is generated that has the following subdirectories: json This directory is where you must copy all the use case JSON files for upload. By default, this directory is empty. When you upload the custom dashboards, the following directories are generated: bad Contains the JSON files that failed the upload process. processing A temporary directory that contains the JSON files that are under process. good Contains the JSON files that succeeded the upload process. properties This directory is where you must copy all the use case properties files. tnpmoed Chapter 3. Preparing your enironment 11

20 This directory contains the following Operations and Engineering Dashboards frame work related directories and files: bin conf fonts lib Contains executable files for installing and uninstalling Operations and Engineering Dashboards application. Contains the tnpmoedconfig.ini configuration file that has the settings for silent installation, uninstallation of the application. Contains all the font files that are used in the dashboards. Contains the drier JAR files for H2 database. prereq Contains the following directories inside directory: contents Contains the Operations and Engineering Dashboards application WAR file. For example, oed <build_number>.war. wireless Contains summaries and udc directories that contain the summaries and UDCs that are needed for wireless use case. wireline Contains tp_enrichment directory that has the importformulasandnoctree.rmg script and other dependent files for adding the Region property for Wireline use case. queries Contains all the SQL queries for populating the Wireline, Wireless, and core Operations and Engineering Dashboards framework-related data into H2 database. scripts Contains all the scripts that are needed to work with Wireline and Wireless use cases. logs This directory is generated after the installation of Operations and Engineering Dashboards framework is complete and contains the log files. 4. Extract the oed_geps_ <build_number>.tar.gz file. oed_geps <build_number> directory is generated that has the following sub directories: json Contains 4 different leels of hierarchy folders with each of the folder haing the GEPS related JSON files. properties Contains 4 different leels of hierarchy folders with each of the folder haing the GEPS related properties files. geps_ _<build_number>.tar.gz mongodb-linux-x86_64-rhel tar.gz Extract this package to install and use the MongoDB database. 5. Extract the oed_wireless_ <build_number>.tar.gz file. oed_wireless <build_number> directory is generated that has the following sub directories: json 12 Installing and Configuring Operations and Engineering Dashboards

21 Contains the JSON files that are associated with the dashboards for Wireless use cases. properties Contains properties files that are associated with the dashboards for Wireless use cases. oed <build_number>_usecases_prereq summaries Summaries of all use cases that are released in the current ersion of Tioli Netcool Performance Manager. udc UDCs of all of all use cases that are released in the current ersion of Tioli Netcool Performance Manager. tnpmoed <build_number>_usecases_prereq summaries Summaries of all use cases that are released in Tioli Netcool Performance Manager udc UDCs of all use cases that are released in Tioli Netcool Performance Manager Extract the oed_wireline_ <build_number>.tar.gz file. oed_wireline <build_number> directory is generated that has the following sub directories: json Contains the JSON files that are associated with the dashboards for Wireline use cases. properties Contains properties files that are associated with the dashboards for Wireline use cases. What to do next Copying the use case files Important: Copy the Oracle JDBC drier file (ojdbc7.jar) that is needed for wireless dashboards to the lib directory. The default location for ojdbc7.jar from the database serer is <ORACLE_HOME>/jdbc/lib where <ORACLE_HOME> is /appl/oracle/product/ /db_1. Copy the required use case files from Wireline, Wireless and Geographic Eent Performance System folders to Operations and Engineering Dashboards frame work directories. Chapter 3. Preparing your enironment 13

22 Copying the wireless use cases files Use this information to copy all the files in wireless use case package. About this task Copy the following files from wireless use case files to Operations and Engineering Dashboards frame work directories: JSON files Properties files UDC definition files Summary definition files Procedure 1. Copy all the JSON files from oed_wireless <build_number>/json directory to oed <build_number>/json folder. 2. Copy all the properties files from oed_wireless <build_number> folder to oed <build_number>/properties folder. 3. Create udc and summaries folders in your /oed <build_number>/ prereq/1.1.0/wireless folder. 4. Copy all the summary definition files from the following folders to /oed <build_number>/prereq/1.1.0/wireless/summaries: tnpmoed <build_number>_usecases_prereq/summaries oed <build_number>_usecases_prereq/summaries 5. Copy the UDC definition files from the following folders to /oed <build_number>/prereq/1.1.0/wireless/udc: tnpmoed <build_number>_usecases_prereq/udc oed <build_number>_usecases_prereq/udc Copying the Geographic Eent Performance System use case files Use this information to copy all the files in Geographic Eent Performance System package. About this task Copy the following files from Geographic Eent Performance System directories to Operations and Engineering Dashboards frame work directories: JSON files Properties files Procedure 1. Copy all the JSON files from oed_geps <build_number>/json/ Hierarchy<#> directory to oed <build_number>/json folder. 14 Installing and Configuring Operations and Engineering Dashboards

23 Copy the JSON files based on your network leel. Consider the following scenarios: If your network has 4 hierarchy leels: Region -> State -> Cluster -> District Copy the following JSON files from oed_geps <build_number>/json/ Hierarchy4 to oed <build_number>/json. AlarmSummary.json AffectedSites.json SiteView.json 2. Copy all the properties files from oed_geps <build_number>/ properties/hierarchy<#> folder to oed <build_number>/properties folder. Consider the following scenarios: If your network has 4 hierarchy leels: Region -> State -> Cluster -> District Copy the following properties files from oed_geps <build_number>/ properties/hierarchy4 to oed <build_number>/properties. AlarmSummary_en.properties AffectedSites_en.properties SiteView_en.properties Copying wireline use case files Use this information to copy all the JSON and properties files in wireline use case package to Operations and Engineering Dashboards frame work directories. About this task Copy the following files: JSON files Properties files Procedure 1. Copy all the JSON files from oed_wireline <build_number>/json directory to oed <build_number>/json folder. 2. Copy all the properties files from oed_wireline <build_number> folder to oed <build_number>/properties folder. Chapter 3. Preparing your enironment 15

24 Editing the tnpmoedconfig.ini file You must edit the tnpmoedconfig.ini file that is located in <DIST_DIR>/ oed <build_number>/conf before you run the installer. About this task The install.sh script uses the configuration settings that are specified in the file and runs the installation. Contents of tnpmoedconfig.ini file Use this information to edit the tnpmoedconfig.ini file with appropriate alues to install, uninstall your Operations and Engineering Dashboards application without user interention. It contains parameters and alues that are required to set up and configure the installation silently. The tnpmoedconfig.ini file contains the following sections to edit: Installation Property Description Recommended alue mode Proide the installation mode. Aailable Installation modes: WirelessOnly WirelineOnly WirelessWireline <installation_mode> Jazz for Serice Management Property Description Recommended alue JazzSM_location ibm_jaa_path Proide the path where Jazz for Serice Management is installed. Point the Operations and Engineering Dashboards application to IBM Jaa 7 path. IBM Jaa 7 is aailable with WebSphere Application Serer installation. /opt/ibm/jazzsm /opt/ibm/websphere/ AppSerer/jaa_1.7_64 WebSphere Application Serer Property Description Recommended alue nodename Proide the node name. JazzSMNode01 cellname Proide the cell name. JazzSMNode01Cell serer Proide the serer name. serer1 H2 16 Installing and Configuring Operations and Engineering Dashboards

25 Property Description Recommended alue drierjarpath sererip h2storage h2port Proide the path to the folder that contains H2 database drier JAR file (h jar). The h jar file is aailable in the Operations and Engineering Dashboards build in the lib folder. IP address of the serer where H2 database is created. H2 database storage location. Note: The path that is proided here is appended to the user's home directory. If user is root and the location is set as /H2/tnpmoed, then the H2 storage is created at /root/h2/ and the file that is created is tnpmoedh2.db. Port number of where H2 database is running. <DIST_DIR>/oed <build_number>/lib <IP_Address> /tnpmoedh Oracle Note: These settings are required for WirelessOnly and WirelessWireline modes of installation. The alues for the properties in this section must point to Wireless Oracle database. Chapter 3. Preparing your enironment 17

26 Property Description Recommended alue oracledrierjarpath oracle_jndi_name oracle_database_url network_id Proide the path to the folder that contains Oracle drier JAR file (ojdbc7.jar). Proide the Jaa Naming and Directory Interface (JNDI) name for the Oracle data source. Proide database connection string alue. Proide the network ID for Wireless Network Oeriew. For more information, see Obtaining the Network ID in Installing and Configuring Operations and Engineering Dashboards.. <DIST_DIR>/oed <build_number>/lib jdbc/wirelessone <Network_ID> Mail Session Property Description Recommended alue mail_proider mail_transport_host mail_transport_port mail_transport_protocol mail_from Proide the mail serer to connect to send mails. Proide the mail serer name for your organization to connect for sending s. Proide the SMTP port number. Proide the mail transport protocol. Proide the address of the mail originator. <Built-in Mail Proider> <serer_name> 25 smtp Application Property Description Recommended alue war_file_path contextroot war_file_name Proide the path to the Operations and Engineering Dashboards application that is oed <build_number>.war file location. Proide the context root for the Operations and Engineering Dashboards application. Context root can be any user-defined name, and must start with /. Operations and Engineering Dashboards application WAR file. <DIT_DIR> /oed <build_number> /prereq/1.1.0/contents /tnpmoed Note: The context root must be PV in case of oed <build_number>.war DataView context root 18 Installing and Configuring Operations and Engineering Dashboards

27 Property Description Recommended alue context_root Proide the context root for Dashboard Application Serices Hub where the DataView application is installed. Note: This setting is required for WirelineOnly and WirelessWireline modes of installation. PV Dashboard upload properties Property Description Recommended alue period source_directory properties_directory GISAPIKEY Proide the polling period in minutes. Proide the source directory path that contains the JSON files to upload. Proide the directory path that contains the properties files to upload. Proide a alid Google Map API Key. Note: This setting is only required for GIS Alarm Summary dashboard. If you fail to proide a alid Google Maps API Key, the GIS Alarm Summary dashboard map widget will fail to load. 1 <DIST_DIR>/oed <build_number>/<json> <DIST_DIR>/oed <build_number>/ <properties> <Google_Map_API_Key> Proisioning user-defined counters (UDCs) and summaries The wirelessusecase.sh file proisions the UDCs and summaries that are associated with wireless technology packs and adds the UDCs and summary execution to the cronscript for scheduling. Before you begin Copy and extract the oed <build_number>.tar.gz file on Tioli Netcool Performance Manager Wireless application serer. Chapter 3. Preparing your enironment 19

28 About this task This script is needed for WirelessOnly and WirelessWireline modes of installation and needs to be run on the serer where Tioli Netcool Performance Manager Wireless application serer is aailable. Attention: This step creates scheduled jobs to run summaries and UDCs on the Tioli Netcool Performance Manager Wireless system and might result in extra processing load to the application and database serers. Procedure 1. Edit the wireless_properties.txt file that is aailable in <DIST_DIR>/ oed <build_number>/scripts The wireless_properties.txt file contains the following details: serername=<myserer.ibm.com> Note: Add the host name where Tioli Netcool Performance Manager application serer is installed. Rest of properties can be used with specified defaults alues. cronscript=cronscript.sh cronscript parameter takes the alue cronscript.sh file. Proide the path to the file. Each technology pack has a set of UDCs and summaries. Only if all the UDCs and summaries for a particular technology pack are created successfully, the entries are aailable in the crontab. If any of the UDCs or summaries fail, then you see no entry in crontab for that technology pack. To check whether the cronscript.sh file is considered for scheduling or not, use crontab l command to list all cronjobs. techpackproperties=wireless_techpack_details.txt techpackproperties parameter takes the wireless_techpack_details.txt file that is aailable in the <DIST_DIR>/oed <build_number>/scripts folder. The wireless_techpack_details.txt file contains the following information: List of technology packs and their ersions UDCs and summaries names for each technology pack Names of the pages that are displayed in the accordion for each technology pack udcdirectory=../prereq/1.1.0/wireless/udc The path to the folder where the UDCs are aailable. summarydirectory=../prereq/1.1.0/wireless/summaries The path to the folder where the summaries are aailable. crontabminute=30 The alue in which minute of eery hour the cronscript needs to run. For example, if you proide crontabminute alue as 30, the cronscript is scheduled to be run in eery 30th minute of eery hour. Note: This alue must be set based on the loader performance in your enironment. 2. Go to <DIST_DIR>/oed <build_number>/scripts directory and run the wirelessusecase.sh with irtuo user as follows:./wirelessusecase.sh -username sysadm -password Sysadm01 -properties wireless_properties.txt 20 Installing and Configuring Operations and Engineering Dashboards

29 Where: username is the user name to log in to the Tioli Netcool Performance Manager wireless system. For example, sysadm. password is the password used to log in to the system. properties is the properties file that must be updated with details needed for the wirelessusecase.sh script to run. After you run the script, you can obsere the following: log_file.txt file is generated in the working directory where the script is run. The following files are generated in the working directory: Wireless_all_pages.txt wireless_isible_pages.txt wireless_summaries_installed.txt This file contains a list of all summary names that are successfully installed with this script in current and preious executions. 3. Verify the log_file.txt file for any errors in the execution of the script. The log_file.txt file also contains help related to execution of the wirelessusecaseexeuction.sh script. 4. Copy the following files to the serer where Operations and Engineering Dashboards is installed in this location: <DIST_DIR>/oed <build_number>/queries Wireless_all_pages.txt wireless_isible_pages.txt Note: These files contain a list of JSON files for rendering the wireless dashboards. Related tasks: Uninstalling summaries and UDCs on page 46 Use these steps to remoe all the existing summaries after you uninstall the Operations and Engineering Dashboards application. Related information: Run a proisioned summary Crontab setup Obtaining the Network ID You need the Network ID to allow Network leel report scoping. About this task This step is needed for WirelessOnly and WirelessWireline modes of installation. Procedure 1. Log in to Tioli Netcool Performance Manager Web client. 2. Click the Reporting tab to open the Reporting page. 3. Click the KPI Browser tab. Chapter 3. Preparing your enironment 21

30 4. Select the correct endor. For example, Huawei 5. Select the correct endor. For example, Generic 6. Select Network from the Entity list. 7. Select Network_ID from the KPI Selection pane and type * in the Resource Selection pane. All the Network_IDs are returned. 8. Copy the Network ID that you want to monitor in Network Oeriew dashboards into the network_id property of tnpmoedconfig.ini file that is used for installing the Operations and Engineering Dashboards application. Related concepts: Contents of tnpmoedconfig.ini file on page 16 Use this information to edit the tnpmoedconfig.ini file with appropriate alues to install, uninstall your Operations and Engineering Dashboards application without user interention. It contains parameters and alues that are required to set up and configure the installation silently. Adding Region and sysname properties A new Region property must be added to support the Region filter in Wireline dashboards. The sysname property is needed for correlating resources among the three wireline technology packs in the use case. Before you begin Copy and extract the oed <build_number>.tar.gz file on the serer where DataMart is installed as puser. About this task For WirelineOnly and WirelessWireline modes of installation, run the wirelineusecase.sh script that checks for the required wireline technology packs. If the technology packs are present, the script calls importformulasandnoctree.rmg script. Run these steps on the DataMart serer as puser. Attention: This step introduces an independent report grouping with in the NOC reporting tree. Procedure 1. Source the DataMart enironment with the following command:. /opt/datamart/datamart.en 2. Go to <DIST_DIR>/oed <build_number>/scripts directory and run the wirelineusecase.sh as follows:./wirelineusecase.sh -datamartpath /opt/datamart -techpackproperties wireline_techpack_details.txt enrichmentdirectory../prereq/1.1.0/wireline/tp_enrichment Where: 22 Installing and Configuring Operations and Engineering Dashboards

31 datamartpath is the location where DataMart is installed. By default, /opt/datamart techpackproperties is the properties file that contains a list of technology packs and their ersions. This parameter takes the wireline_techpack_details.txt file that is aailable in the <DIST_DIR>/oed <build_number>/scripts folder. enrichmentdirectory is the path to the location of importformulasandnoctree.rmg script. For example, <DIST_DIR>/oed <build_number>/prereq/1.1.0/wireline/ tp_enrichment. 3. Run all the inentory profiles that are related to the technology packs needed for wireline use case to see the sysname added to the new discoery formulas. The sysname property is updated with double quotation marks in all the preiously existing discoery formulas as well. CAUTION: This change might impact Cisco IPSLA Technology Pack that does not hae sysname property in double quotation marks. If you hae a customized NOC Reporting tree that uses sysname, your old reports might not render correctly. 4. Run the following steps for element enrichment for Region property for all the technology packs that are needed for Operations and Engineering Dashboards: a. Export the elements into a text file by using the following command: resmgr -export "elt" -colnames "dbindex name" -filter "profil(= <profile_name> )" -file <enrichment_file.txt> Where, <enrichment_file.txt> is the file into which all the elements that are aailable in the technology pack are exported. Note: A template file by name sample_enrichment_file.txt is aailable in oed <build_number>/tnpmoed/prereq/1.1.0/wireline/ tp_enrichment folder. b. Append the following text to the existing content in <enrichment_file.txt> file for each element: Region _ <Region_Name> _ string _ c. Import the updated file into the Tioli Netcool Performance Manager database by using the following command: resmgr -import "elt" -colnames "dbindex name eprp.name eprp.alue eprp.datatype" -filter "profil(= <profile_name> )" -file <enrichment_file.txt> 5. Run all the inentory profiles again. 6. Perform the report grouping. 7. Perform AutoGrouping by following these steps: a. Click the Report SE Group tab from Resource Editor. b. Right-click the NOC Reporting tree and select AutoGrouping from the list. A confirmation prompt opens. 8. Click Yes to confirm. Results You can see that the NOC reporting tree is updated with new report grouping as follows: Chapter 3. Preparing your enironment 23

32 9981 _ ~NOC Reporting~Infrastructure _ 9982 _ ~NOC Reporting~Infrastructure~%(Element.Region) _ 9983 _ ~NOC Reporting~Infrastructure~%(Element.Region)~%(sysName) _ Related information: Exporting and importing objects Run inentory profile Opening DataMart GUI 24 Installing and Configuring Operations and Engineering Dashboards

33 Chapter 4. Installing Operations and Engineering Dashboards application Describes how to install the Operations and Engineering Dashboards on Tioli Netcool Performance Manager system. Before you begin Ensure that you installed Tioli Netcool Performance Manager Wireline and Wireless components according to your mode of installation of Operations and Engineering Dashboards application. Ensure that you installed the required Wireline and Wireless Technology Packs according to your mode of installation of Operations and Engineering Dashboards application. Ensure that WebSphere Application Serer is up and running. Ensure that the following files are copied to the <DIST_DIR>/oed <build_number>/queries folder: wireless_all_pages.txt wireless_isible_pages.txt See Proisioning user-defined counters (UDCs) and summaries on page 19 Note: This step is needed for WirelessOnly and WirelessWireline modes of installation. Ensure that the following roles are aailable on Dashboard Application Serices Hub and assigned to the dashboard users: Wireline Wireless tnpmuser tnpmadministrator chartadministrator chartviewer Related concepts: chartcreator High-leel installation tasks Prerequisite Technology Packs on page 6 Wireless and Wireline Technology Packs that are required to use with Operations and Engineering Dashboards. The installation script reads the configuration details from tnpmoedconfig.ini file and automates the tasks required for installing and using the Operations and Engineering Dashboards application. Installation script performs the following tasks: Prompts for the following inputs from the user: User name and password for Jazz for Serice Management serer User name and password for the user for H2 database access Copyright IBM Corp. 2016,

34 User name and password for Oracle database access This step is needed for WirelessOnly and WirelessWireline installation modes. address and password of the mail account for configuring the outgoing mail Creates the following resources on WebSphere Application Serer: Authentication alias for H2 (for all the modes of installation) and Oracle database (for WirelessOnly and WirelessWireline modes of installation) Mail session based on configuration details proided in properties file JDBC data proiders for H2 (for all the modes of installation) and Oracle data proider (for WirelessOnly and WirelessWireline modes of installation) H2 data source (for all the modes of installation) Oracle data source database (for WirelessOnly and WirelessWireline modes of installation) Starts H2 database serer on the port that is proided in the properties file. Populates the H2 database based on the mode of installation. Retriees the users who hae the roles chartadministrator, chartcreator, chartviewer, tnpmuser, and tnpmadministrator from WebSphere Application Serer. Installs the Operations and Engineering Dashboards application WAR file on WebSphere Application Serer. Maps the authenticated users to the application installed on WebSphere Application Serer. Adds the authenticated users to H2 database. Starts the Operations and Engineering Dashboards application. Starts the WebSphere Application Serer. Enables the serer to Jaa 1.7 for WirelessOnly mode of installation. Running the Operations and Engineering Dashboards installer Ensure that you are installing the Operations and Engineering Dashboards application based on your installation scenario. Installed application that starts and runs correctly is considered deployed. Before you begin If your installation mode is WirelessOnly or WirelessWireline, make sure that you copied the ojdbc7.jar file to <DIST_DIR>/oed <build_number>/tnpmoed/lib folder About this task The installation script uses tnpmoedconfig.ini and silently installs the application on WebSphere Application Serer and also creates the required resources such as data sources and mail session. Procedure 1. Set the ownership of the oed <build_number> directory to irtuo user by using the following command: chown -R irtuo:irtuo oed <build_number> 26 Installing and Configuring Operations and Engineering Dashboards

35 2. Gie execute permission to the oed <build_number> directory by using the following command: chmod R 755 oed <build_number> 3. Go to the <DIST_DIR>/oed <build_number>/tnpmoed/bin folder where the installation script is aailable. 4. Run the installation script on the Jazz for Serice Management serer with the same user that installed Jazz for Serice Management:./install.sh The installation script checks for the dependencies and reports errors if any. For example, install the lsof utility for your respectie operating system, if you see the following message: Checking dependencies... lsof utility not aailable. Please install package for lsof utility. Proide the following inputs at the prompt: 5. Enter the installation mode. The three installation modes you can proide are WirelessOnly, WirelineOnly, and WirelessWireline. 6. Enter the Jazz for Serice Management administrator user name. By default, smadmin. Please enter the JazzSM username: smadmin 7. Enter a Jazz for Serice Management administrator password. Please enter the JazzSM password: 8. Enter the user name to access the H2 database. Please enter H2 database username oeddb 9. Enter the password to access the H2 database. Please enter H2 database password This step is needed only for WirelessOnly and WirelessWireline mode of installation. 10. Enter the user name to access the Oracle database. Please enter oracle database username irtuo This step is needed only for WirelessOnly and WirelessWireline mode of installation. 11. Enter the password to access the Oracle database. Please enter oracle database password 12. Enter the ID of the mail account for configuring the outgoing mail. Chapter 4. Installing Operations and Engineering Dashboards application 27

36 Please enter the mail account user to configure outgoing mail 13. Enter the password for the user account. Please enter the password for the user 14. Restart the WebSphere Application Serer. WebSphere Application Serer restart is required. Enter Y to restart WebSphere Application Serer now. Enter N to exit. 15. Enable Jaa 1.7 if you are using WirelessOnly mode of installation. Jaa 1.7 is recommended for WirelessOnly mode of installation. Do you want to upgrade to Jaa 1.7 now? [Y / N]: Y Results The installation script runs with the following output for WirelineOnly mode of installation: 28 Installing and Configuring Operations and Engineering Dashboards

37 ./install.sh Checking dependencies... Installation mode: wirelineonly Please enter the JazzSM username: smadmin Please enter the JazzSM password: Trying to connect to WAS admin Checking whether application is already installed... Application installation not found Please enter the H2 database username oeddb Please enter the H2 database password Please enter the mail account user to configure outgoing mail Please enter the password for the Checking if the application is running... Creating user for H2 database Populating database... Running queries against < > on port Executing - FrameworkTables.sql Executing - ConfigPageAccessQueries.sql Executing - ColorRanges.sql Executing - Querytable.sql Executing - ConfigTables.sql Populating database for wireline... Running queries against < > on port Executing - WirelineDomainCategory.sql Executing - WirelinePageAccessQueries.sql Executing - WirelineQuerytable.sql Populated database Fetching authenticated users information Installing application... Installation completed successfully.. Adding users data to database... Restarting the application... Application started successfully WebSphere Application Serer restart is required. Enter Y to restart WebSphere Application Serer now. Enter N to exit. Please restart the WebSphere Application Serer before you access the application. Y Stopping WebSphere Application Serer ADMU0116I: Tool information is being logged in file /opt/ibm/jazzsm/profile/logs/serer1/stopserer.log ADMU0128I: Starting tool with the JazzSMProfile profile ADMU3100I: Reading configuration for serer: serer1 ADMU3201I: Serer stop request issued. Waiting for stop status. ADMU4000I: Serer serer1 stop completed. Starting WebSphere Application Serer ADMU0116I: Tool information is being logged in file /opt/ibm/jazzsm/profile/logs/serer1/startserer.log ADMU0128I: Starting tool with the JazzSMProfile profile ADMU3100I: Reading configuration for serer: serer1 ADMU3200I: Serer launched. Waiting for initialization status. ADMU3000I: Serer serer1 open for e-business; process id is serer1 started successfully The installation script runs with the following output for WirelessOnly mode of installation: Chapter 4. Installing Operations and Engineering Dashboards application 29

38 ./install.sh Checking dependencies... Installation mode: wirelessonly Please enter the JazzSM username: smadmin Please enter the JazzSM password: Trying to connect to WAS admin Checking whether application is already installed... Application installation not found Please enter the H2 database username oed Please enter the H2 database password Please enter Oracle database username (For WirelessOnly and WirelessWireline modes only) irtuo Please enter the Oracle database password Please enter the mail account user to configure outgoing mail Please enter the password for the Checking if the application is running... Creating user for H2 database Populating database... Running queries against < > on port Executing - FrameworkTables.sql Executing - ConfigPageAccessQueries.sql Executing - ColorRanges.sql Executing - Querytable.sql Executing - ConfigTables.sql Populating database for wireless... Running queries against < > on port Executing - WirelessDomainCategory.sql Executing - WirelessPageAccessQueries.sql Executing - WirelessQuerytable.sql Running wireless use case specific queries against < > on port Executing - WirelessPageRoleMapping.sql Updating Network ID Network ID updated successfully Populated database Fetching authenticated users information Installing application... Installation completed successfully.. Adding users data to database... Restarting the application... Application started successfully WebSphere Application Serer restart is required. Enter Y to restart WebSphere Application Serer now. Enter N to exit. Please restart the WebSphere Application Serer before you access the application. Y Stopping WebSphere Application Serer ADMU0116I: Tool information is being logged in file /opt/ibm/jazzsm/profile/logs/serer1/stopserer.log ADMU0128I: Starting tool with the JazzSMProfile profile ADMU3100I: Reading configuration for serer: serer1 Realm/Cell Name: <default> Username: smadmin Password: ADMU3201I: Serer stop request issued. Waiting for stop status. ADMU4000I: Serer serer1 stop completed. Jaa 1.7 is recommended for WirelessOnly mode of installation. Do you want to upgrade to Jaa 1.7 now? [Y / N]: Y Upgrading to Jaa 1.7 Starting WebSphere Application Serer ADMU0116I: Tool information is being logged in file /opt/ibm/jazzsm/profile/logs/serer1/startserer.log ADMU0128I: Starting tool with the JazzSMProfile profile ADMU3100I: Reading configuration for serer: serer1 ADMU3200I: Serer launched. Waiting for initialization status. ADMU3000I: Serer serer1 open for e-business; process id is serer1 started successfully 30 Installing and Configuring Operations and Engineering Dashboards

39 The Operations and Engineering Dashboards application is installed at the following location: /opt/ibm/jazzsm/profile/installedapps/jazzsmnode01cell/tnpmoed.ear/ oed <build_number>.war A folder by name logs is created in <DIST_DIR>/oed <build_number> that contains some log files for troubleshooting installation and uninstallation of Operations and Engineering Dashboards application. WebSphere Application Serer and Operations and Engineering Dashboards database serer are started. What to do next After the application file installs successfully, do the following tasks: Check the installation.log file that is located in <DIST_DIR>/oed <build_number>/logs folder for any installation errors. Related tasks: Enabling Jaa 1.7 on WebSphere Application Serer on page 43 Ensure that you configure the IBM WebSphere Application Serer to run with Jaa 1.7 after the installation of Operations and Engineering Dashboards application. This step is required for WirelessOnly mode of installation. Related information: Restarting Jazz for Serice Management application serers Configuring the Wireline web serice on WebSphere Application Serer Configuration steps that are required to add the Wireline web serice on WebSphere Application Serer. Procedure 1. Select Console Settings > General > WebSphere Administratie Console in the console naigation. Setting Resource Enironment Proiders 2. Click Launch WebSphere administratie console. 3. In the WebSphere Integrated Solutions Console, click Resources > Resource Enironment > Resource Enironment Proiders 4. Click New and enter the following information: Name Name of the resource proider. For example, WirelineResource Description A description of the resource proider. 5. Click OK. WirelineResource resource proider is created. 6. Click WirelineResource. 7. From the Additional Properties pane, click Referenceables. 8. Click New and specify the following information: Chapter 4. Installing Operations and Engineering Dashboards application 31