IBM. Installing and Configuring Operations and Engineering Dashboards

Transcription

1 IBM Tivoli Netcool Performance Manager Operations and Engineering Dashboards Document Revision 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 35. Copyright IBM Corporation US Government 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..... v Intended audience v Organization v Service Management Connect v Tivoli Netcool Performance Manager technical training vi Support information vi Conventions used in this publication vi Typeface conventions vi Chapter 1. Introduction Operations and Engineering Dashboards application architecture Chapter 2. Requirements Hardware requirements Software requirements Prerequisite Technology Packs Chapter 3. Preparing your environment 7 Installation scenarios Downloading and extracting the software Provisioning user-defined counters (UDCs) and summaries Obtaining the Network ID Adding Region and sysname properties Contents of tnpmoedconfig.ini file High-level installation tasks Running the Operations and Engineering Dashboards installer Chapter 5. Postinstallation tasks Integrating Operations and Engineering Dashboards on Dashboard Application Services Hub Updating the Network ID Enabling Java 1.7 on WebSphere Application Server 27 Chapter 6. Uninstalling Operations and Engineering Dashboards Uninstalling Operations and Engineering Dashboards application Uninstalling summaries and UDCs Chapter 7. Troubleshooting and support Log files in Operations and Engineering Dashboards 33 Setting the retention period for log files Known problems and solutions Notices Trademarks Terms and conditions for product documentation.. 38 Chapter 4. Installing Operations and Engineering Dashboards application.. 15 Editing the tnpmoedconfig.ini file Copyright IBM Corp iii

4 iv Installing and Configuring Operations and Engineering Dashboards

5 Installing and configuring Operations and Engineering Dashboards Intended audience Organization Describes how to install and configure IBM Tivoli Netcool Performance Manager - Operations and Engineering Dashboards on a Tivoli Netcool Performance Manager system. This information is intended for: v Users who want to install and configure Operations and Engineering Dashboards on a Tivoli Netcool Performance Manager system. Readers must be familiar with the following topics: v Tivoli Netcool Performance Manager Wireline and Wireless concepts v Tivoli Netcool Performance Manager reporting concepts v Tivoli Netcool Performance Manager technology packs This information is organized as follows: v Chapter 1, Introduction, on page 1 v Chapter 2, Requirements, on page 5 Service Management Connect v Chapter 3, Preparing your environment, on page 7 v Chapter 4, Installing Operations and Engineering Dashboards application, on page 15 v Chapter 5, Postinstallation tasks, on page 25 v Chapter 6, Uninstalling Operations and Engineering Dashboards, on page 29 Connect, learn, and share with Service Management professionals: product support technical experts who provide their perspectives and expertise. Access Network and Service Assurance community at developerworks/servicemanagement/nsa/index.html. Use Service Management Connect in the following ways: v Become involved with transparent development, an ongoing, open engagement between other users and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code. v Connect one-on-one with the experts to collaborate and network about Tivoli and the Network and Service Assurance community. v Read blogs to benefit from the expertise and experience of others. v Use wikis and forums to collaborate with the broader user community. Related information: Tivoli Netcool Performance Manager 1.4 community on developerworks Copyright IBM Corp v

6 Tivoli Netcool Performance Manager technical training Support information For Tivoli Netcool Performance Manager technical training information, see the following Tivoli Netcool Performance Manager Training website at: If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Online Access the IBM Software Support site at support/probsub.html. IBM Support Assistant The IBM Support Assistant is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. The Support Assistant provides quick access to support-related information and serviceability tools for problem determination. To install the Support Assistant software, go to support/isa. Troubleshooting Guide For more information about resolving problems, see the problem determination information for this product. Conventions used in this publication Several conventions are used in this publication for special terms, actions, commands, and paths that are dependent on your operating system. Typeface conventions This publication uses the following typeface conventions: Bold Italic Monospace v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text v Citations (examples: titles of publications, diskettes, and CDs) v Words defined in text (example: a nonswitched line is called a point-to-point line) v Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictive clause."; letters as letters example: "The LUN address must start with the letter L.") v New terms in text (except in a definition list): a view is a frame in a workspace that contains data. v Variables and values you must provide:... where myname represents... vi Installing and Configuring Operations and Engineering Dashboards

7 v Examples and code examples Bold monospace v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options v Command names, and names of macros and utilities that you can type as commands 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 Installing and configuring Operations and Engineering Dashboards vii

8 viii Installing and Configuring Operations and Engineering Dashboards

9 Chapter 1. Introduction Operations and Engineering Dashboards provide enhanced visualization features for Tivoli Netcool Performance Manager. Operations and Engineering Dashboards offer the following benefits: v Contain modern, flexible platform with an interactive widget library capable of integrating with any data source. In Tivoli Netcool Performance Manager scenario, both Wireline and Wireless data sources are supported. v Provide more operational value when compared to the existing Tivoli Netcool Performance Manager reports. v Provide lower cost of ownership when compared to Cognos-based reports. These dashboards do not require Tivoli Common Reporting deployment and are easy to handle. v 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 retrieve data from database and sends it to the DataStore Query. The JSON files take the information from the query for visualization as shown in the figure: Presentation Layer (JSON Files) Copyright IBM Corp

10 Data flow architecture for Wireless component Wireless component uses JDBC to retrieve data from database and sends it to the DataStore Query. The JSON files take the information from the query for visualization as shown in the figure: Operations and Engineering Dashboards application architecture The various 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 Server that is available on Dashboard Application Services Hub. The Operations and Engineering Dashboards application provides 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 retrieval is through JDBC and in Wireline component, the data retrieval 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 servlet that takes input from the built-in JSON files. When the wireline and wireless JSON files are modified, the changes are communicated with the respective 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 Tivoli 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 Related information: Software requirements Wireline requirements Wireless requirements Jazz for Service Management Detailed System Requirements Software specifications for Operations and Engineering Dashboards. Operating system Version 6.x package lsof utility 7.x Note: RHEL 7.x is supported only for Wireless component. 7.1 Supported version for your Operating system. Web browsers Version Mozilla Firefox ESR 31, 38 Google Chrome 50 Internet Explorer 11 Other supported software Version Jazz for Service Management WebSphere Application Server IBM Java 1.7 Copyright IBM Corp

14 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 Related information: Wireline component requirements Wireless component requirements Prerequisite Technology Packs Jazz for Service Management Detailed System Requirements Wireless and Wireline Technology Packs that are required to use with Operations and Engineering Dashboards. Wireline Technology Packs v Cisco Device v MIB-II v Cisco IP SLA Table 1. Use case-wise distribution of technology packs Use case Technology Pack Network Performance Monitoring - Devices Cisco Device and MIB-II Network Performance Monitoring - Interfaces MIB-II Network Performance Monitoring - Links Cisco IP SLA Wireless Technology Packs v UMTS Huawei UTRAN V900R015 v v LTE Huawei EUTRAN V100R008C00 v Table 2. Use case-wise distribution of technology packs Use cases Handover Outgoing (3G) Call Drop Rate (3G) Inter RAT Success Rate (4G) Cell Availability (4G) Call Setup Success Rate (4G) Technology Pack UMTS Huawei UTRAN V900R015 v UMTS Huawei UTRAN V900R015 v LTE Huawei EUTRAN V100R008C00 v LTE Huawei EUTRAN V100R008C00 v LTE Huawei EUTRAN V100R008C00 v For more information about the Wireline and Wireless use cases, see Administering and Using Operations and Engineering Dashboards. 6 Installing and Configuring Operations and Engineering Dashboards

15 Chapter 3. Preparing your environment Installation scenarios Before you run the installation, prepare your target environments. You can use different installation scenarios to help you plan and deploy Operations and Engineering Dashboards. The three installation modes are as follows: v WirelessOnly v WirelineOnly v WirelessWireline Installation options that are available 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 respective documentation. WirelessOnly mode v Wireless component that is deployed on a separate server as Dashboard Application Services Hub v Wireless component that is deployed on the same server as Dashboard Application Services Hub Copyright IBM Corp

16 WirelineOnly mode v Operations and Engineering Dashboards is always installed on the server where DataView is installed on Dashboard Application Services Hub. WirelessWireline mode v Wireline and Wireless components deployed on separate servers 8 Installing and Configuring Operations and Engineering Dashboards

17 Downloading and extracting the software Complete these tasks to install Tivoli Netcool Performance Manager Operations and Engineering Dashboards application. Procedure 1. Download the tnpmoed <build_number>.tar.gz file from Tivoli Netcool Performance Manager distribution. 2. Extract the tnpmoed <build_number>.tar.gz file to a location of your choice. You find the tnpmoed <build_number>.tar file. 3. Extract the tnpmoed <build_number>.tar file to a location of your choice: For example, /opt/ibm that is referred to as <DIST_DIR>. tnpmoed <build_number> folder is generated that has the following subdirectories: bin conf 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 the driver JAR files for H2 database. prereq Contains the following folders inside folder: v contents Contains the Operations and Engineering Dashboards application WAR file. For example, tnpmoed <build_number>.war. v wireless Contains summaries and udc folders that contain the summaries and UDCs that are needed for wireless use case. v wireline Contains tp_enrichment folder that has the importformulasandnoctree.rmg script and other dependent files for adding the Region property for Wireline use case. Chapter 3. Preparing your environment 9

18 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. 4. Give execute permission to the tnpmoed <build_number> folder by using the following command: chmod R 755 tnpmoed <build_number> What to do next Important: Copy the Oracle JDBC driver file (ojdbc6.jar) that is needed for wireless dashboards to the lib folder. The default location for ojdbc6.jar from the database server is <ORACLE_HOME>/jdbc/lib where <ORACLE_HOME> is /appl/oracle/product/ /db_1. Provisioning user-defined counters (UDCs) and summaries The wirelessusecase.sh file provisions 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 tnpmoed <build_number>.tar.gz file on Tivoli Netcool Performance Manager Wireless application server. About this task This script is needed for WirelessOnly and WirelessWireline modes of installation and needs to be run on the server where Tivoli Netcool Performance Manager Wireless application server is available. Attention: This step creates scheduled jobs to run summaries and UDCs on the Tivoli Netcool Performance Manager Wireless system and might result in extra processing load to the application and database servers. Procedure 1. Go to <DIST_DIR>/tnpmoed <build_number>/scripts directory and run the wirelessusecase.sh with virtuo user as follows:./wirelessusecase.sh -username sysadm -password Sysadm01 -properties wireless_properties.txt Where: v v username is the user name to log in to the Tivoli Netcool Performance Manager wireless system. For example, sysadm. password is the password used to log in to the system. 10 Installing and Configuring Operations and Engineering Dashboards

19 v properties is the properties file that must be updated with details needed for the wirelessusecase.sh script to run. For example, wireless_properties.txt file contains the following details: servername=<myserver.ibm.com> Note: Add the host name where Tivoli Netcool Performance Manager application server is installed. Rest of properties can be used with specified defaults values. cronscript=cronscript.sh cronscript parameter takes the value cronscript.sh file. Provide 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 available 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 available in the <DIST_DIR>/tnpmoed <build_number>/ scripts folder. The wireless_techpack_details.txt file contains the following information: - List of technology packs and their versions - 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 available. summarydirectory=../prereq/1.1.0/wireless/summaries The path to the folder where the summaries are available. crontabminute=30 The value in which minute of every hour the cronscript needs to run. For example, if you provide crontabminute value as 30, the cronscript is scheduled to be run in every 30th minute of every hour. Note: This value must be set based on the loader performance in your environment. After you run the script, you can observe the following: v v 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_visible_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 previous executions. 2. 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. Chapter 3. Preparing your environment 11

20 3. Copy the following files to the server where Operations and Engineering Dashboards is installed in this location: <DIST_DIR>/tnpmoed <build_number>/queries v v Wireless_all_pages.txt wireless_visible_pages.txt Note: These files contain a list of JSON files for rendering the wireless dashboards. Related tasks: Uninstalling summaries and UDCs on page 30 Use these steps to remove all the existing summaries after you uninstall the Operations and Engineering Dashboards application. Related information: Run a provisioned summary Crontab setup Obtaining the Network ID You need the Network ID to allow Network level report scoping. About this task This step is needed for WirelessOnly and WirelessWireline modes of installation. Procedure 1. Log in to Tivoli Netcool Performance Manager Web client. 2. Click the Reporting tab to open the Reporting page. 3. Click the KPI Browser tab. 4. Select the correct vendor. For example, Huawei 5. Select the correct vendor. 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 Overview 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 values to install, uninstall your Operations and Engineering Dashboards application without user intervention. It contains parameters and values that are required to set up and configure the installation silently. 12 Installing and Configuring Operations and Engineering Dashboards

21 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 tnpmoed <build_number>.tar.gz file on the server where DataMart is installed as pvuser. 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 server as pvuser. Attention: This step introduces an independent report grouping with in the NOC reporting tree. Procedure 1. Source the DataMart environment with the following command:. /opt/datamart/datamart.env 2. Go to <DIST_DIR>/tnpmoed <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: v v v 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 versions. This parameter takes the wireline_techpack_details.txt file that is available in the <DIST_DIR>/tnpmoed <build_number>/scripts folder. enrichmentdirectory is the path to the location of importformulasandnoctree.rmg script. For example, <DIST_DIR>/tnpmoed <build_number>/prereq/1.1.0/ wireline/tp_enrichment 3. Run all the inventory profiles that are related to the technology packs needed for wireline use case to see the sysname added to the new discovery formulas. The sysname property is updated with double quotation marks in all the previously existing discovery formulas as well. Chapter 3. Preparing your environment 13

22 CAUTION: This change might impact Cisco IPSLA Technology Pack that does not have sysname property in double quotation marks. If you have 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> 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 Tivoli Netcool Performance Manager database by using the following command: resmgr -import "elt" -colnames "dbindex name eprp.name eprp.value eprp.datatype" -filter "profil(= <profile_name> )" -file <enrichment_file.txt> 5. Run all the inventory 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: 9981 _ ~NOC Reporting~Infrastructure _ 9982 _ ~NOC Reporting~Infrastructure~%(Element.Region) _ 9983 _ ~NOC Reporting~Infrastructure~%(Element.Region)~%(sysName) _ Related information: Exporting and importing objects Run inventory profile Opening DataMart GUI 14 Installing and Configuring Operations and Engineering Dashboards

23 Chapter 4. Installing Operations and Engineering Dashboards application Describes how to install the Operations and Engineering Dashboards on Tivoli Netcool Performance Manager system. Before you begin v Ensure that you installed Tivoli Netcool Performance Manager Wireline and Wireless components according to your mode of installation of Operations and Engineering Dashboards application. v Ensure that you installed the required Wireline and Wireless Technology Packs according to your mode of installation of Operations and Engineering Dashboards application. v Ensure that WebSphere Application Server is up and running. v Ensure that the following files are copied to the <DIST_DIR>/tnpmoed <build_number>/queries folder: wireless_all_pages.txt wireless_visible_pages.txt See Provisioning user-defined counters (UDCs) and summaries on page 10 Note: This step is needed for WirelessOnly and WirelessWireline modes of installation. v Ensure that the following roles are available on Dashboard Application Services Hub and assigned to the dashboard users: Wireline Wireless tnpmuser tnpmadministrator chartadministrator chartviewer Related concepts: chartcreator Prerequisite Technology Packs on page 6 Wireless and Wireline Technology Packs that are required to use with Operations and Engineering Dashboards. Related information: Installing IBM Tivoli Netcool Performance Manager - Wireline component Installing IBM Tivoli Netcool Performance Manager - Wireless component Installing Wireline Technology Packs Copyright IBM Corp

24 Editing the tnpmoedconfig.ini file You must edit the tnpmoedconfig.ini file that is located in <DIST_DIR>/ tnpmoed <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 values to install, uninstall your Operations and Engineering Dashboards application without user intervention. It contains parameters and values 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 value mode Provide the installation mode. Installation modes: v v v WirelessOnly WirelineOnly WirelessWireline <installation_mode> Jazz for Service Management Property Description Recommended value JazzSM_location ibm_java_path Provide the path where Jazz for Service Management is installed. Point the Operations and Engineering Dashboards application to IBM Java 7 path. IBM Java 7 is available with WebSphere Application Server installation. /opt/ibm/jazzsm /opt/ibm/websphere/ AppServer/java_1.7_64 WebSphere Application Server Property Description Recommended value nodename Provide the node name. JazzSMNode01 cellname Provide the cell name. JazzSMNode01Cell server Provide the server name. server1 H2 16 Installing and Configuring Operations and Engineering Dashboards

25 Property Description Recommended value driverjarpath serverip h2storage h2port Provide the path to the folder that contains H2 database driver JAR file (h jar). The h jar file is available in the Operations and Engineering Dashboards build in the lib folder. IP address of the server where H2 database is created. H2 database storage location. Note: The path that is provided 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>/tnpmoed <build_number>/lib <IP_Address> /tnpmoedh Oracle Note: These settings are required for WirelessOnly and WirelessWireline modes of installation. The values for the properties in this section must point to Wireless Oracle database. Chapter 4. Installing Operations and Engineering Dashboards application 17

26 Property Description Recommended value oracledriverjarpath oracle_jndi_name oracle_database_url network_id Provide the path to the folder that contains Oracle driver JAR file (ojdbc6.jar). Provide the Java Naming and Directory Interface (JNDI) name for the Oracle data source. Provide database connection string value. Provide the network ID for Wireless Network Overview. Network ID that you set in Obtaining the Network ID on page 12. <DIST_DIR>/ tnpmoed <build_number>/lib jdbc/wirelessone <Network_ID> Mail Session Property Description Recommended value mail_provider mail_transport_host mail_transport_port mail_transport_protocol mail_from Provide the mail server to connect to send mails. Provide the mail server name for your organization to connect for sending s. Provide the SMTP port number. Provide the mail transport protocol. Provide the address of the mail originator. <Built-in Mail Provider> <server_name> 25 smtp Application Property Description Recommended value war_file_path contextroot war_file_name Provide the path to the Operations and Engineering Dashboards application that is tnpmoed <build_number>.war file location. Provide 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> /tnpmoed <build_number> /prereq/1.1.0/contents /tnpmoed tnpmoed <build_number>.war 18 Installing and Configuring Operations and Engineering Dashboards

27 High-level installation tasks 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: v Prompts for the following inputs from the user: User name and password for Jazz for Service Management server User name and password for the user for H2 database access 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 v Creates the following resources on WebSphere Application Server: 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 provided in properties file JDBC data providers for H2 (for all the modes of installation) and Oracle data provider (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) v Starts H2 database server on the port that is provided in the properties file. v Populates the H2 database based on the mode of installation. v Retrieves the users who have the roles chartadministrator, chartcreator, chartviewer, tnpmuser, and tnpmadministrator from WebSphere Application Server. v Installs the Operations and Engineering Dashboards application WAR file on WebSphere Application Server. v Maps the authenticated users to the application installed on WebSphere Application Server. v Adds the authenticated users to H2 database. v Starts the Operations and Engineering Dashboards application. v Starts the WebSphere Application Server. v Enables the server to Java 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 ojdbc6.jar file to <DIST_DIR>/tnpmoed <build_number>/lib folder Chapter 4. Installing Operations and Engineering Dashboards application 19

28 About this task The installation script uses tnpmoedconfig.ini and silently installs the application on WebSphere Application Server and also creates the required resources such as data sources and mail session. Procedure 1. Go to the <DIST_DIR>/tnpmoed <build_number>/bin folder where the installation script is available. 2. Run the installation script on the Jazz for Service Management server with the same user that installed Jazz for Service Management:./install.sh The installation script checks for the dependencies and reports errors if any. For example, install the lsof utility for your respective operating system, if you see the following message: Checking dependencies... lsof utility not available. Please install package for lsof utility. Provide the following inputs at the prompt: 3. Enter the installation mode. The three installation modes you can provide are WirelessOnly, WirelineOnly, and WirelessWireline. 4. Enter the Jazz for Service Management administrator user name. By default, smadmin. Please enter the JazzSM username: smadmin 5. Enter a Jazz for Service Management administrator password. Please enter the JazzSM password: 6. Enter the user name to access the H2 database. Please enter H2 database username oeddb 7. 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. 8. Enter the user name to access the Oracle database. Please enter oracle database username virtuo This step is needed only for WirelessOnly and WirelessWireline mode of installation. 9. Enter the password to access the Oracle database. 20 Installing and Configuring Operations and Engineering Dashboards

29 Please enter oracle database password 10. Enter the ID of the mail account for configuring the outgoing mail. Please enter the mail account user to configure outgoing mail 11. Enter the password for the user account. Please enter the password for the user 12. Restart the WebSphere Application Server. WebSphere Application Server restart is required. Enter Y to restart WebSphere Application Server now. Enter N to exit. 13. Enable Java 1.7 if you are using WirelessOnly mode of installation. Java 1.7 is recommended for WirelessOnly mode of installation. Do you want to upgrade to Java 1.7 now? [Y / N]: Y Results The installation script runs with the following output for WirelineOnly mode of installation: Chapter 4. Installing Operations and Engineering Dashboards application 21

30 ./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 Server restart is required. Enter Y to restart WebSphere Application Server now. Enter N to exit. Please restart the WebSphere Application Server before you access the application. Y Stopping WebSphere Application Server ADMU0116I: Tool information is being logged in file /opt/ibm/jazzsm/profile/logs/server1/stopserver.log ADMU0128I: Starting tool with the JazzSMProfile profile ADMU3100I: Reading configuration for server: server1 ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server server1 stop completed. Starting WebSphere Application Server ADMU0116I: Tool information is being logged in file /opt/ibm/jazzsm/profile/logs/server1/startserver.log ADMU0128I: Starting tool with the JazzSMProfile profile ADMU3100I: Reading configuration for server: server1 ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server server1 open for e-business; process id is server1 started successfully The installation script runs with the following output for WirelessOnly mode of installation: 22 Installing and Configuring Operations and Engineering Dashboards

31 ./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) virtuo 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 Server restart is required. Enter Y to restart WebSphere Application Server now. Enter N to exit. Please restart the WebSphere Application Server before you access the application. Y Stopping WebSphere Application Server ADMU0116I: Tool information is being logged in file /opt/ibm/jazzsm/profile/logs/server1/stopserver.log ADMU0128I: Starting tool with the JazzSMProfile profile ADMU3100I: Reading configuration for server: server1 Realm/Cell Name: <default> Username: smadmin Password: ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server server1 stop completed. Java 1.7 is recommended for WirelessOnly mode of installation. Do you want to upgrade to Java 1.7 now? [Y / N]: Y Upgrading to Java 1.7 Starting WebSphere Application Server ADMU0116I: Tool information is being logged in file /opt/ibm/jazzsm/profile/logs/server1/startserver.log ADMU0128I: Starting tool with the JazzSMProfile profile ADMU3100I: Reading configuration for server: server1 ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server server1 open for e-business; process id is server1 started successfully Chapter 4. Installing Operations and Engineering Dashboards application 23

32 The Operations and Engineering Dashboards application is installed at the following location: /opt/ibm/jazzsm/profile/installedapps/jazzsmnode01cell/tnpmoed.ear/ tnpmoed <build_number>.war A folder by name logs is created in <DIST_DIR>/tnpmoed <build_number> that contains some log files for troubleshooting installation and uninstallation of Operations and Engineering Dashboards application. WebSphere Application Server and Operations and Engineering Dashboards database server are started. What to do next After the application file installs successfully, do the following tasks: v Check the installation.log file that is located in <DIST_DIR>/tnpmoed <build_number>/logs folder for any installation errors. Related tasks: Enabling Java 1.7 on WebSphere Application Server on page 27 Ensure that you configure the IBM WebSphere Application Server to run with Java 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 Service Management application servers 24 Installing and Configuring Operations and Engineering Dashboards

33 Chapter 5. Postinstallation tasks Perform these postinstallation tasks after the installation of Operations and Engineering Dashboards is complete. Logging in to the Dashboard Application Services Hub portal Information about how to access the wireline or wireless network performance dashboards and reports from Dashboard Application Services Hub. Procedure 1. Open a web browser and enter the following URL for the Jazz for Service Management UI and reporting server: For example: Where: v v v host.domain is the fully qualified host name or IP address of the Jazz for Service Management UI and reporting server. When single sign-on (SSO) is enabled, ensure that you use the fully qualified host name in the URL of the Jazz for Service Management reporting and UI server. SSO requires that the browser pass LTPA cookies to the Jazz for Service Management application server, and these cookies contain the fully qualified host name. port is the secure HTTP port number that was specified during installation. The default value is /DASH_context_root is the context root for the console that was specified during installation. The default value is /ibm/console. 2. Enter the user ID and password in the login page. Click Log in. The Dashboard Application Services Hub Welcome page opens. Integrating Operations and Engineering Dashboards on Dashboard Application Services Hub Use this information to add the Operations and Engineering Dashboards application on Dashboard Application Services Hub portal. All dashboards that are created in the console have a resource type of Custom. About this task Create a page in Dashboard Application Services Hub to display the deployed Operations and Engineering Dashboards. Procedure 1. Log in to the Dashboard Application Services Hub portal. 2. Click + (Create New Page) icon in the taskbar. Or, click > Pages > New Page. A Page Settings page is displayed. Copyright IBM Corp

34 3. In the Page name field, provide a descriptive name for the dashboard and in the Page location field indicate where you want the dashboard to be displayed in the navigation pane. The example page location is console/default/. 4. Select the Proportional option for the dashboard layout. 5. Optional: Click the Optional Setting label and associate one or more roles with the new dashboard and set the level of access for each role. Note: The default role is iscadmins role. Make sure that the users who can access the dashboards are assigned iscadmins role as well. 6. Click OK. The taskbar tab is updated with the name of the new dashboard and a window is displayed that includes a widget palette from which you can select widgets for your new dashboard. 7. Type Web Widget in the Search field and drag the widget from the content palette to the content area below the palette, by using the grid lines to assist you in positioning each widget. As you add items, you can configure display settings through the (Edit options) icon, for example, you can change skin and a widget's position on the dashboard, that is, whether it is displayed in front of or behind other content. You can also resize a widget. 8. Click (Edit options) icon and select Edit. Or, click Widget in the taskbar and select Edit. 9. Specify the following details: v In the Widget title field, provide a brief descriptive name. For example, TNPM OED. When you select a title, consider the purpose of the web widget, its home page, and that the title is used in the navigation pane to access the widget. Where the context-root is /tnpmoed. v In the Home page field, provide a valid web address. The web address of the page that displays by default when a user accesses the widget from the navigation pane. For example, the landing page URL is as follows: Accordion.jsp Note: The <context_root> must be same as in the tnpmoedconfig.ini file. 10. Clear the Show a browser control toolbar check box to provide users with a web navigation toolbar, that is, standard web navigation buttons and a web address entry field. 11. Click Save to commit your changes. 12. Click Widget > Fill Work Page on the taskbar. 13. Click Save and Exit. What to do next Click Default ( ) on the navigation bar and click TNPM OED to open the Operations and Engineering Dashboards. 26 Installing and Configuring Operations and Engineering Dashboards

35 Updating the Network ID For WirelessOnly and WirelessWireline modes of installation, run the UpdateNetwork_Wireless.sh script to update the Network ID that is provided in the tnpmoedconfig.ini configuration file at the time of installation. About this task It is an optional task performed only when you want to update the Network ID that is provided in the conf/tnpmoedconfig.ini file. Procedure Go to <DIST_DIR>/tnpmoed <build_number>/scripts directory and run the UpdateNetwork_Wireless.sh as follows:./updatenetwork_wireless.sh <server_ip> <h2_storage> <user_name> <password> <New_Network_ID> <h2_port> Where: v server IP is IP address of the server where the database is installed. v h2_storage is the directory where the database is installed that is provided in conf/tnpmoedconfig.ini file. For example, H2database. v h2_user_name is the H2 database user name that is provided during installation. v h2_password is the H2 database user password that is provided during installation. v h2_port is the port number on which H2 database is running that is provided in conf/tnpmoedconfig.ini file. For example, 9408 Enabling Java 1.7 on WebSphere Application Server Ensure that you configure the IBM WebSphere Application Server to run with Java 1.7 after the installation of Operations and Engineering Dashboards application. This step is required for WirelessOnly mode of installation. About this task Note: The IBM WebSphere Application Server must be running with Java 1.7 before you proceed to use the Operations and Engineering Dashboards application. Run this manual step only if you did not upgrade to Java 1.7 during the installation of the Operations and Engineering Dashboards application. Procedure 1. On the relevant Jazz for Service Management server, open a command window. 2. Run the following command to configure IBM WebSphere Application Server to run with Java 1.7: Chapter 5. Postinstallation tasks 27

36 <WAS_Home>/bin/managesdk.sh -enableprofile -profilename JazzSMProfile -sdkname 1.7_64 -enableservers The default WAS_Home is /opt/ibm/websphere/appserver. The output is as follows: CWSDK1017I: Profile JazzSMProfile now enabled to use SDK 1.7_64. CWSDK1001I: Successfully performed the requested managesdk task. What to do next Restart Jazz for Service Management application server. 28 Installing and Configuring Operations and Engineering Dashboards

37 Chapter 6. Uninstalling Operations and Engineering Dashboards Uninstall Operations and Engineering Dashboards and its related information from the system. About this task Uninstallation includes the following tasks: v Uninstall the Operations and Engineering Dashboards application. v Remove the data sources that are added during configuration of the Operations and Engineering Dashboards on Dashboard Application Services Hub. v Remove the JDBC providers that are added during configuration of the Operations and Engineering Dashboards on Dashboard Application Services Hub. Uninstalling Operations and Engineering Dashboards application When Operations and Engineering Dashboards application is no longer needed, you can uninstall it. Uninstalling an application deletes the application from the product configuration repository and deletes the application binary files from the file system of all nodes where the application modules are installed. Before you begin v Ensure that the WebSphere Application Server is running. v Back up your old custom dashboard JSON files if any from your previous installations. v Stop the H2 database by using the following commands: cd <DIST_DIR>/tnpmoed <build_number>/bin./stopH2.sh <server_ip> <port> Where: <server_ip> is the IP address of the server that is specified in the tnpmoedconfig.ini file to install H2 database. <port> is port number that is specified in the tnpmoedconfig.ini file where H2 database is running. About this task The uninstallation script uses tnpmoedconfig.ini and performs the silent uninstallation of the application on WebSphere Application Server and also deletes the required resources like data sources and mail session. Procedure 1. Go to the <DIST_DIR>/tnpmoed <build_number>/bin folder where the uninstallation script is available. 2. Run the script by using the following command:./uninstall.sh Copyright IBM Corp