with IBM Corp. · 2017-04-28 · Installa tion Guide IBM. Note Befor e using this information and...

IBM Tivoli Netcool Performance Manager 1.4.3Wireline ComponentDocument Revision R2E1

Installation Guide

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 307.

© Copyright IBM Corporation 2006, 2017.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . . . viiIntended audience . . . . . . . . . . . . viiWhat this publication contains . . . . . . . . viiTivoli Netcool Performance Manager - WirelineComponent . . . . . . . . . . . . . . ixThe Default UNIX Shell . . . . . . . . . . xService Management Connect. . . . . . . . . xTivoli Netcool Performance Manager technicaltraining . . . . . . . . . . . . . . . . xSupport information . . . . . . . . . . . . xConventions used in this publication . . . . . . xi

Typeface conventions . . . . . . . . . . xi

Chapter 1. Introduction . . . . . . . . 1Tivoli Netcool Performance Manager architecture . . 1

Co-location rules . . . . . . . . . . . . 3Inheritance . . . . . . . . . . . . . . 4ServerTime synchronization . . . . . . . . 5Disk Usage Server . . . . . . . . . . . 5Notable subcomponents and features . . . . . 7

Typical installation topology . . . . . . . . . 26Basic topology scenario . . . . . . . . . 27Intermediate topology scenario . . . . . . . 28Advanced topology scenario. . . . . . . . 29High Availability . . . . . . . . . . . 30

Chapter 2. Requirements . . . . . . . 33IBM Prerequisite Scanner . . . . . . . . . . 33Plan your installation . . . . . . . . . . . 34Minimum requirements for installation . . . . . 36

Solaris hardware requirements . . . . . . . 36AIX hardware requirements . . . . . . . . 36Linux hardware requirements . . . . . . . 37Oracle and DB2 deployment space requirements 37Screen resolution . . . . . . . . . . . 42

Minimum requirements for a proof of conceptinstallation . . . . . . . . . . . . . . 42

Solaris hardware requirements (POC). . . . . 42AIX hardware requirements (POC) . . . . . 42Linux hardware requirements (POC) . . . . . 43Screen resolution . . . . . . . . . . . 43

Supported operating systems and modules . . . . 43Solaris 10 for SPARC platforms . . . . . . . 44AIX platforms . . . . . . . . . . . . 47Linux platforms . . . . . . . . . . . . 50

Required user names . . . . . . . . . . . 55pvuser . . . . . . . . . . . . . . . 55oracle . . . . . . . . . . . . . . . 55db2 . . . . . . . . . . . . . . . . 56

Ancillary software requirements . . . . . . . 56FTP support . . . . . . . . . . . . . 56OpenSSH and SFTP . . . . . . . . . . 56File compression. . . . . . . . . . . . 58DataView load balancing . . . . . . . . . 58Databases . . . . . . . . . . . . . . 58

Jazz for Service Management . . . . . . . 59Java Runtime Environment (JRE) . . . . . . 60Web browsers and settings for DataView reports 60X Emulation . . . . . . . . . . . . . 61IBM Tivoli Netcool/OMNIbus Web GUIintegration. . . . . . . . . . . . . . 61Microsoft Office Version . . . . . . . . . 62

Chapter 3. Installing and configuringthe prerequisite software . . . . . . . 63Overview . . . . . . . . . . . . . . . 63

Oracle . . . . . . . . . . . . . . . 63IBM DB2 . . . . . . . . . . . . . . 64Supported platforms . . . . . . . . . . 65

Pre-Installation setup tasks . . . . . . . . . 65Setting up a remote X Window display . . . . 65Changing the ethernet characteristics . . . . . 66Adding the pvuser login name . . . . . . . 69Setting the resource limits . . . . . . . . 71Setting the shell limits (Linux only) . . . . . 72Setting the shell limits (Solaris only) . . . . . 72Set the system parameters . . . . . . . . 73Enable FTP on Linux systems . . . . . . . 75Disable SELinux (Linux only) . . . . . . . 75Set the kernel parameters . . . . . . . . . 75Replace the native taring utility with gnu tar . . 80Installing libcrypto.so . . . . . . . . . . 80

Deployer pre-requisites . . . . . . . . . . 81Operating system check . . . . . . . . . 81Mount points check . . . . . . . . . . 82Authentication between distributed servers . . . 82

Tivoli Netcool Performance Manager distribution. . 82Downloading the Tivoli Netcool PerformanceManager distribution to disk . . . . . . . 83

General database setup tasks . . . . . . . . 83Specifying a basename for DB_USER_ROOT . . 84Specifying login passwords . . . . . . . . 85Assumed values . . . . . . . . . . . . 86Creating group and user ID for a DB2 serverinstallation . . . . . . . . . . . . . 87Creating group and user IDs for Data ServerClient installation . . . . . . . . . . . 89

Chapter 4. Installing Jazz for ServiceManagement . . . . . . . . . . . . 91Hardware and software requirements for installingJazz for Service Management . . . . . . . . 92Quick reference to Jazz for Service Managementinstallation . . . . . . . . . . . . . . 92

Starting Jazz for Service Management applicationservers . . . . . . . . . . . . . . . 96Stopping Jazz for Service Managementapplication servers . . . . . . . . . . . 96

Upgrading Java . . . . . . . . . . . . . 97

© Copyright IBM Corp. 2006, 2017 iii

Chapter 5. Installing database . . . . . 99Installing Oracle 12.1.0.2 server (64-bit) . . . . . 99

Download the Oracle distribution to disk . . . 99Verify the required operating system packages 100Running the Oracle server configuration script 100Setting a password for the Oracle login name 104Run the preinstallation script . . . . . . . 104Running the rootpre.sh script (AIX only) . . . 105Verifying PATH and Environment for the Oraclelogin name . . . . . . . . . . . . . 106Set the ORACLE_SID variable . . . . . . . 106Installing Oracle by using the menu-based script 107Run the root.sh script . . . . . . . . . 109Set automatic startup of the database instance 110Configure the Oracle listener . . . . . . . 111Configure the Oracle net client . . . . . . 112

Installing Oracle 12.1.0.2 client 32-bit . . . . . 114Download the Oracle distribution to disk . . . 115Run the Oracle client configuration script . . . 115Setting a password for the Oracle login name 118Run the preinstallation script . . . . . . . 118Verifying PATH and Environment for the Oraclelogin name . . . . . . . . . . . . . 119Installing the Oracle client (32-bit) . . . . . 120Run the root.sh script . . . . . . . . . 122Updating the Oracle user's .profile . . . . . 123Configuring the Oracle Net client . . . . . 123

Installing DB2 11.1.1.1 (64-bit) . . . . . . . . 127Installing DB2 Server 11.1.1.1 (64-bit) . . . . 128Installing IBM Data Server Client 11.1.1.1, Linux64-bit (64-bit) . . . . . . . . . . . . 135

Chapter 6. Installing in a distributedenvironment . . . . . . . . . . . . 141Distributed installation process . . . . . . . 141Starting the Launchpad . . . . . . . . . . 143Installing the Topology Editor . . . . . . . . 144Starting the Topology Editor . . . . . . . . 146Creating a new topology . . . . . . . . . 146Adding and configuring the Tivoli NetcoolPerformance Manager components . . . . . . 147

Adding the hosts . . . . . . . . . . . 147Adding a database configurations component 149Adding a DataMart . . . . . . . . . . 150Adding a Discovery Server . . . . . . . . 152Discovering existing Dashboard ApplicationServices Hub . . . . . . . . . . . . 153Adding a DataView . . . . . . . . . . 154Adding the DataChannel administrativecomponents . . . . . . . . . . . . . 155Adding a DataChannel . . . . . . . . . 155Adding a Collector . . . . . . . . . . 158Add a Cross Collector CME . . . . . . . 162

Saving the topology . . . . . . . . . . . 163Opening an existing topology file . . . . . 164

Starting the Deployer. . . . . . . . . . . 164Primary Deployer . . . . . . . . . . . 165Secondary Deployers . . . . . . . . . . 165Pre-deployment check . . . . . . . . . 166

Deploying the topology . . . . . . . . . . 166

Next steps . . . . . . . . . . . . . . 168Resuming a partially successful first-timeinstallation . . . . . . . . . . . . . . 169

Chapter 7. Installing as a minimaldeployment . . . . . . . . . . . . 171Overview. . . . . . . . . . . . . . . 171Before you begin . . . . . . . . . . . . 171

Special consideration . . . . . . . . . . 172Overriding default values . . . . . . . . 172

Installing a minimal deployment . . . . . . . 173Starting the Launchpad . . . . . . . . . 173Start the installation . . . . . . . . . . 174

The post-installation script . . . . . . . . . 176Next steps . . . . . . . . . . . . . 176

Chapter 8. Modifying the currentdeployment . . . . . . . . . . . . 179Opening a deployed topology . . . . . . . . 179Adding a new component . . . . . . . . . 180Changing configuration parameters of existingTivoli Netcool Performance Manager components . 182Moving components to a different host . . . . . 182Moving a deployed collector to a different host . . 183

Moving a deployed SNMP collector (scenario 1) 183Moving a deployed UBA bulk collector. . . . 186

Changing the port for a collector . . . . . . . 189Modifying Dashboard Application Services Huband Tivoli Common Reporting ports . . . . . 190

Changing ports for the Dashboard ApplicationServices Hub . . . . . . . . . . . . 190Port assignments . . . . . . . . . . . 191Viewing the application server profile . . . . 191

Chapter 9. Using the High AvailabilityManager . . . . . . . . . . . . . 193Overview. . . . . . . . . . . . . . . 193HAM basics . . . . . . . . . . . . . . 194

The parts of a collector . . . . . . . . . 194Clusters . . . . . . . . . . . . . . 195

HAM cluster configuration . . . . . . . . . 195Types of spare hosts . . . . . . . . . . 196Types of HAM clusters . . . . . . . . . 196Example HAM clusters . . . . . . . . . 197

High Availability Manager configuration changesto accommodate multiple collector . . . . . . 202Resource pools . . . . . . . . . . . . . 203How the SNMP collector works . . . . . . . 203

How failover works with the HAM and theSNMP collector . . . . . . . . . . . . 204Obtaining collector status . . . . . . . . 205

Creating a HAM environment . . . . . . . . 206Topology prerequisites . . . . . . . . . 207Procedures . . . . . . . . . . . . . 207Create the HAM and a HAM cluster . . . . 207Adding the designated spare . . . . . . . 208Add the managed definitions . . . . . . . 209Define the resource pools . . . . . . . . 210Save and start the HAM. . . . . . . . . 212Creating an additional HAM environment. . . 213

iv IBM Tivoli Netcool Performance Manager: Installation Guide

Modifying a HAM environment . . . . . . . 213Removing HAM components . . . . . . . 213Stopping and restarting modified components 214

Viewing the current configuration . . . . . . 215Show Collector Process... dialog . . . . . . 215Show Managed Definition... dialog . . . . . 216

Chapter 10. Uninstalling components 217Removing a component from the topology . . . 217

Restrictions and behavior . . . . . . . . 217Removing a component . . . . . . . . . 219Removing multiple collectors . . . . . . . 220

Uninstalling the entire Tivoli Netcool PerformanceManager system . . . . . . . . . . . . 220

Order of uninstall . . . . . . . . . . . 220Restrictions and behavior . . . . . . . . 221Performing the uninstall. . . . . . . . . 221

Uninstalling the Topology Editor . . . . . . . 222Removing residual files . . . . . . . . . . 223

Appendix A. Remote installationissues . . . . . . . . . . . . . . 227When remote install is not possible . . . . . . 227

FTP is possible, but REXEC or RSH are not . . 227Neither FTP nor REXEC/RSH are possible . . 228

Installing on a remote host by using a secondarydeployer . . . . . . . . . . . . . . . 228

Appendix B. DataChannel architecture 231Data collection . . . . . . . . . . . . . 231

Data aggregation . . . . . . . . . . . 231Management programs and watchdog scripts 232DataChannel application programs . . . . . 233

Starting the DataLoad SNMP collector . . . . . 235DataChannel management components in adistributed configuration . . . . . . . . . 236

Manually starting the Channel Managerprograms . . . . . . . . . . . . . . 236

Adding DataChannels to an existing system . . . 237DataChannel terminology . . . . . . . . . 238

Appendix C. Aggregation sets . . . . 241Overview. . . . . . . . . . . . . . . 241Configuring aggregation sets . . . . . . . . 241Installing aggregation sets . . . . . . . . . 245

Start the Tivoli Netcool Performance Managersetup program . . . . . . . . . . . . 245Set aggregation set installation parameters . . 245Edit aggregation set parameters file . . . . . 248

Linking DataView groups to timezones. . . . . 249

Appendix D. Deployer CLI options 251Using the -DTarget option . . . . . . . . . 253

Appendix E. Secure file transferinstallation . . . . . . . . . . . . 255Overview. . . . . . . . . . . . . . . 255Enabling SFTP . . . . . . . . . . . . . 255Installing OpenSSH . . . . . . . . . . . 256

AIX systems . . . . . . . . . . . . . 256Solaris systems . . . . . . . . . . . . 258Linux systems . . . . . . . . . . . . 260

Configuring OpenSSH . . . . . . . . . . 260Configuring the OpenSSH server . . . . . . 260Configuring OpenSSH client . . . . . . . 261Generating public and private keys . . . . . 261

Testing OpenSSH and SFTP . . . . . . . . 264Troubleshooting . . . . . . . . . . . . 265Tivoli Netcool Performance Manager SFTP errors 265

Appendix F. LDAP integration . . . . 267Supported LDAP servers . . . . . . . . . 267LDAP configuration . . . . . . . . . . . 267

Enable LDAP configuration . . . . . . . 267Verifying the DataView installation . . . . . 268Assigning Tivoli Netcool Performance Managerroles to LDAP users . . . . . . . . . . 269

Appendix G. Installing an interim fix 271Overview. . . . . . . . . . . . . . . 271

Installation rules . . . . . . . . . . . 271Behavior and restrictions . . . . . . . . 271

Before you begin . . . . . . . . . . . . 272Installing a patch . . . . . . . . . . . . 272

Appendix H. Error codes and log files 275Error codes . . . . . . . . . . . . . . 275

Deployer messages . . . . . . . . . . 275Topology Editor messages . . . . . . . . 288InstallAnywhere messages . . . . . . . . 292

Log files . . . . . . . . . . . . . . . 294COI log files. . . . . . . . . . . . . 294Deployer log file . . . . . . . . . . . 294Eclipse log file . . . . . . . . . . . . 295Trace log file . . . . . . . . . . . . 295

Appendix I. Troubleshooting . . . . . 297Deployment problems . . . . . . . . . . 297

Saving installation configuration files . . . . 299Tivoli Netcool Performance Manager componentproblems . . . . . . . . . . . . . . . 300Topology Editor problems . . . . . . . . . 300Tivoli Netcool Performance Manager DB2 databaseschema fails . . . . . . . . . . . . . . 300Telnet problems . . . . . . . . . . . . 301Java problems . . . . . . . . . . . . . 301Testing connectivity to the database . . . . . . 302Testing external procedure call access . . . . . 302

Appendix J. Moving DataView contentbetween Dashboard ApplicationServices Hub servers . . . . . . . . 305The synchronize command . . . . . . . . . 305

Notices . . . . . . . . . . . . . . 307Trademarks . . . . . . . . . . . . . . 309Terms and conditions for product documentation 310

Contents v

vi IBM Tivoli Netcool Performance Manager: Installation Guide

About this publication

IBM® Tivoli® Netcool® Performance Manager, Version 1.4.3 is a bundled productconsisting of two main components. A wireline component (formerly TivoliNetcool/Proviso), and a wireless component (formerly Tivoli Netcool PerformanceManager for Wireless).

The Installing Tivoli Netcool Performance Manager - Wireline Component tells youhow to install and configure Tivoli Netcool Performance Manager by using Oracleand DB2® databases.

Note: If you are upgrading Tivoli Netcool Performance Manager, see the IBMTivoli Netcool Performance Manager Upgrade Guide - Wireline component.

Important: Before installing Tivoli Netcool Performance Manager, you are advisedto read the Installing Tivoli Netcool Performance Manager - Wireline Component.Release notes can contain information specific to your installation that is notcontained in this guide. Failure to consult the release notes might result in acorrupted, incomplete, or failed installation.

Intended audienceThis information is intended for:

The audience who are network administrator or operations specialist responsiblefor installing the Tivoli Netcool Performance Manager product suite on anenterprise network.

To install Tivoli Netcool Performance Manager successfully, you must have athorough understanding of the following subjects:v Basic principles of TCP/IP networks and network managementv SNMP conceptsv Administration of the Linux, Solaris, or AIX operating environmentv Administration of the Oracle database management systemv Administration of the IBM DB2 database management systemv Tivoli Netcool Performance Manager

What this publication containsThis publication contains the following sections:v Chapter 1, “Introduction,” on page 1 this chapter provides an overview of the

Tivoli Netcool Performance Manager product suite and provides importantpre-installation setup information.

v Chapter 2, “Requirements,” on page 33 this chapter describes the complete set ofrequirements for Tivoli Netcool Performance Manager 1.4.3

v Chapter 3, “Installing and configuring the prerequisite software,” on page 63this chapter describes how to install and configure the Tivoli NetcoolPerformance Manager 1.4.3

© Copyright IBM Corp. 2006, 2017 vii

v Chapter 4, “Installing Jazz for Service Management,” on page 91 this chapterdescribes the Dashboard Application Services Hub administration tasks thatinclude setting up the console, managing users, exporting and importing data.

v Chapter 5, “Installing database,” on page 99 this chapter to install the Oracle andDB2 database for Tivoli Netcool Performance Manager.

v Chapter 6, “Installing in a distributed environment,” on page 141this chapter describes installation of Tivoli Netcool Performance Manager for thefirst time in a fresh, distributed environment.

v Chapter 7, “Installing as a minimal deployment,” on page 171this chapter describes the install Tivoli Netcool Performance Manager as aminimal deployment.

v Chapter 8, “Modifying the current deployment,” on page 179For this chapter describes how to modify an installation of Tivoli NetcoolPerformance Manager.

v Chapter 9, “Using the High Availability Manager,” on page 193this chapter describes the optional Tivoli Netcool Performance Manager. HighAvailability Manager (HAM), including how to set up a HAM environment.

v Chapter 10, “Uninstalling components,” on page 217this section provides information on how to uninstall components.

v Appendix A, “Remote installation issues,” on page 227 this chapter describes thesupport for remote installation of all Tivoli Netcool Performance Managercomponents.

v Appendix B, “DataChannel architecture,” on page 231 this chapter providesdetailed information about the DataChannel architecture.

v Appendix C, “Aggregation sets,” on page 241 this chapter describes theconfiguration and installation of aggregation sets.

v Appendix D, “Deployer CLI options,” on page 251 this chapter describes aboutthe CLI options and their description.

v Appendix E, “Secure file transfer installation,” on page 255 this chapter describesthe OpenSSH installation, configuration, and testing process in detail for eachplatform.

v Appendix F, “LDAP integration,” on page 267 this chapter describes in detail onhow to configure LDAP (Lightweight Directory Access Protocol) as a defaultauthentication/authorization mechanism for Tivoli Netcool PerformanceManager.

v Appendix G, “Installing an interim fix,” on page 271 this appendix describeshow to install an interim fix (or patch) release of Tivoli Netcool PerformanceManager.

v Appendix H, “Error codes and log files,” on page 275 this appendix lists theTivoli Netcool Performance Manager error messages and log files.

v Appendix I, “Troubleshooting,” on page 297 this appendix lists the problems thatmight occur during an installation and how to resolve them.

v Appendix J, “Moving DataView content between Dashboard Application ServicesHub servers,” on page 305

viii IBM Tivoli Netcool Performance Manager: Installation Guide

Tivoli Netcool Performance Manager - Wireline ComponentIBM Tivoli Netcool Performance Manager consists of a wireline component(formerly Netcool/Proviso) and a wireless component (formerly Tivoli NetcoolPerformance Manager for Wireless).

Tivoli Netcool Performance Manager - Wireline Component consists of thefollowing subcomponents:v DataMart is a set of management, configuration, and troubleshooting GUIs. The

Tivoli Netcool Performance Manager System Administrator uses the GUIs todefine policies and configuration, and to verify and troubleshoot operations.

v DataLoad provides flexible, distributed data collection and data import of SNMPand non-SNMP data to a centralized database.

v DataChannel aggregates the data collected through Tivoli Netcool PerformanceManager DataLoad for use by the Tivoli Netcool Performance ManagerDataView reporting functions. It also processes online calculations and detectsreal-time threshold violations.

v DataView is a reliable application server for on-demand, web-based networkreports.

v Technology Packs extend the Tivoli Netcool Performance Manager system withservice-ready reports for network operations, business development, andcustomer viewing.

The following figure shows the different Tivoli Netcool Performance Managermodules.

Tivoli Netcool Performance Manager documentation consists of the following:v Release notesv Installation and upgrade informationv User guidesv Technical notesv Online help

The documentation is available for viewing and downloading on the informationcenter at http://www-01.ibm.com/support/knowledgecenter/SSBNJ7/welcome.

About this publication ix

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7/welcome

The Default UNIX ShellThe installation scripts and procedures in this manual generally presume, but donot require, the use of the Korn or Bash shells, and only Korn shell syntax isshown in examples.

If you are a user of the C shell or Tcsh, make the necessary adjustments in thecommands shown as examples throughout this manual.

This guide uses the following shell prompts in the examples:v # (pound sign) indicates commands you perform when logged in as root.v $ (dollar sign) indicates commands you perform when logged in as oracle for

Oracle database or db2 for IBM DB2 database or pvuser.v SQL> indicates commands you perform SQL*Plus prompt.v clpplus indicates the command line processor plus that provides a

command-line user interface that you can use to connect databases and todefine, edit, and run statements, scripts, and commands.

Service Management ConnectConnect, learn, and share with Service Management professionals: product supporttechnical experts who provide their perspectives and expertise.

Access Network and Service Assurance community at https://www.ibm.com/developerworks/servicemanagement/nsa/index.html. Use Service ManagementConnect 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 earlydesigns, sprint demonstrations, product roadmaps, and prerelease code.

v Connect one-on-one with the experts to collaborate and network about Tivoliand the Network and Service Assurance community.

v Read blogs to benefit from the expertise and experience of others.v Use wikis and forums to collaborate with the broader user community.Related information:

Tivoli Netcool Performance Manager 1.4 community on developerWorks

Tivoli Netcool Performance Manager technical trainingFor Tivoli Netcool Performance Manager technical training information, see thefollowing Tivoli Netcool Performance Manager Training website at:https://tnpmsupport.persistentsys.com/training.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineAccess the IBM Software Support site at http://www.ibm.com/software/support/probsub.html .

IBM Support AssistantThe IBM Support Assistant is a free local software serviceability workbench

x IBM Tivoli Netcool Performance Manager: Installation Guide

https://www.ibm.com/developerworks/servicemanagement/nsa/index.html

https://www.ibm.com/developerworks/servicemanagement/nsa/index.html

https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=d4b565fd-04e5-47c2-965a-943ccdfabdb9

https://tnpmsupport.persistentsys.com/training

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/probsub.html

that helps you resolve questions and problems with IBM softwareproducts. The Support Assistant provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe Support Assistant software, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the problemdetermination information for this product.

Conventions used in this publicationSeveral conventions are used in this publication for special terms, actions,commands, and paths that are dependent on your operating system.

Typeface conventionsThis publication uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip:, and Operating system considerations:)

v Keywords and parameters in text

Italic

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: "TheLUN address must start with the letter L.")

v New terms in text (except in a definition list): a view is a frame in aworkspace that contains data.

v Variables and values you must provide: ... where myname represents....

Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Bold monospace

v Command names, and names of macros and utilities that you can typeas commands

v Environment variable names in textv Keywordsv Parameter names in text: API structure parameters, command

parameters and arguments, and configuration parameters

About this publication xi

http://www.ibm.com/software/support/isa

http://www.ibm.com/software/support/isa

v Process namesv Registry variable names in textv Script names

xii IBM Tivoli Netcool Performance Manager: Installation Guide

Chapter 1. Introduction

Introduction to Tivoli Netcool Performance Manager installation.

This information provides an overview of the Tivoli Netcool Performance Managerproduct suite and provides important pre-installation setup information. Inaddition, this information provides an overview of the installation interfaceintroduced in version 1.4.3.

Tivoli Netcool Performance Manager 1.4.3 supports both Oracle and DB2databases.

Attention: DB2 is supported on Linux only. Whereas, Oracle is supported onSolaris, AIX®, and Linux systems.

Tivoli Netcool Performance Manager architectureTivoli Netcool Performance Manager system components.

The Tivoli Netcool Performance Manager components run on:

v SPARC-based servers from Oracle that run the Solaris operatingsystem

v servers from IBM

v servers

Exact, release-specific requirements, prerequisites, and recommendations forhardware and software are described in detail in the Requirements topic.

You can work with Professional Services to plan and size the deployment of TivoliNetcool Performance Manager components in your environment.

The following diagram provides a high-level overview of the Tivoli NetcoolPerformance Manager architecture.

© Copyright IBM Corp. 2006, 2017 1

The Tivoli Netcool Performance Manager system components are as follows:v Tivoli Netcool Performance Manager database - The Tivoli Netcool

Performance Manager database is hosted on Oracle or IBM DB2.v Tivoli Netcool Performance Manager DataMart - Tivoli Netcool Performance

Manager DataMart is the user and administrative interface to the Tivoli NetcoolPerformance Manager database and to other Tivoli Netcool PerformanceManager components.

v Tivoli Netcool Performance Manager DataLoad - Tivoli Netcool PerformanceManager DataLoad consists of one or more components that collect networkstatistical raw data from network devices and from network managementsystems.

v Tivoli Netcool Performance Manager DataChannel - Tivoli NetcoolPerformance Manager DataChannel is a collection of components that collectdata from DataLoad collectors, aggregate and process the data, and load thedata into the Tivoli Netcool Performance Manager database. DataChannelcomponents also serve as the escalation point for collected data that isdetermined to be over threshold limits.

v Tivoli Netcool Performance Manager DataView - Tivoli Netcool PerformanceManager DataView is the web server that hosts and analyzes platform. Thisplatform is used to display web-based management reports based on networkdata that is aggregated and placed in the Tivoli Netcool Performance Managerdatabase.

v Tivoli Netcool Performance Manager Technology Packs - Each technology packis a set of components that describes the format and structure of networkstatistical data that is generated by network devices. Each technology pack isspecific for a particular device, or class of devices; or for a particular company'sdevices; or for a protocol (such as standard SNMP values) common to manydevices.

v Dashboard Application Services Hub - The Dashboard Application ServicesHub application provides a database-aware web server foundation for theweb-based management reports displayed by Dashboard Application ServicesHub DataView.

2 IBM Tivoli Netcool Performance Manager: Installation Guide

Platform support

All subcomponents of the Tivoli Netcool Performance Manager - WirelineComponent can be installed on a mix of AIX, Linux, and Solaris operating systems;that is, the operating systems on which the DataChannel, DataView, DataLoad, andDataMart subcomponents are installed do not have to be of the same type.

Note: Dataview cannot be installed on a Solaris system as Jazz™ for ServiceManagement 1.1.3.0 is not supported on Solaris.

Co-location rulesAllowed component deployment numbers and co-location rules.

Table 1 lists how many of each component can be deployed per Tivoli NetcoolPerformance Manager system and whether multiple instances can be installed onthe same server.

In this table:v N - Depends on how many subchannels there are per channel, and how many

channels there are per system. For example, if there are 40 subchannels perchannel and 8 channels, theoretically N=320. However, the practical limit isprobably much lower.

v System - The entire Tivoli Netcool Performance Manager system.v Per host - A single physical host can be partitioned using zones, which

effectively gives you multiple hosts.

Note: All CME, DLDR, FTE, and LDR components within a channel must sharethe same filesystem.

Table 1. Co-location rules

ComponentNumber of Instances

AllowedCo-LocationConstraints

Co-LocationConstraints

Supported byDeployer?

AMGR One per host thatsupportsDataChannelcomponents

Yes

BCOL v N per system

v One percorrespondingsubchannel

Yes

CME One per subchannel Filesystem Yes

CMGR One per system Yes

Database One per system Yes

Database channel One perDataChannel;maximum of 8

Yes

Chapter 1. Introduction 3

Table 1. Co-location rules (continued)

ComponentNumber of Instances

AllowedCo-LocationConstraints

Co-LocationConstraints

Supported byDeployer?

DataLoad (SNMPcollector)

v N per system


v One per host

Yes

DataMart v N per system

v One per host

Yes

DataView v N per system

v One per host

One per system.

Discovery Server v N per system

v One per host

Co-locate withcorrespondingDataMart

Yes

DLDR One per channel Filesystem Yes

FTE One per subchannel Filesystem Yes

HAM N +M per system,where N is thenumber of collectorsthat HAM ismonitoring, and M isthe number ofstandby collectors

Yes

LDR One per channel Filesystem Yes

Log One per system Yes

UBA (simple) v N per system


Yes

UBA (complex) Pack-dependent Pack-dependent Pack-dependent

v In the Logical view of the Topology Editor, the DataChannel component containsthe subchannels, LDR, and DLDR components, with a maximum of 8 channelsper system. The subchannel contains the collector, FTE, and CME, with amaximum of 40 subchannels per channel.

InheritanceInheritance is the method by which a parent object propagates its property valuesto a child component.

The following rules should be kept in mind when dealing with these properties.v A Child Property can be read only, but is not always.v If the Child Property is not read only, then it can be changed to a value different

from the Parent Property.v If the Parent Property changes, and the Child and Parent properties were the

same before the change, then the child property will be changed to reflect thenew Parent Property value


v If the Child Property changes, the Parent Property value will not be updatedv The Default Value of the Child Property is always the current Parent Property

value

Note: When performing an installation that uses non-default values, that is,non-default usernames, passwords and locations, it is recommended that youcheck both the Logical view and Physical view to ensure that they both contain thecorrect values before proceeding with the installation.

Example

As an example of how a new component inherits property values:

The Disk Usage Server (DUS) is a child component of the Host object. The DUSRemote User property inherits its value from the Host PV User Property oncreation of the DUS. The DUS property value will be taken from the Host propertyvalue.

Child properties that have been inherited are marked as inherited.

As an example of what happens when you change inherited property values:

If we change the Host PV User Property value, it gets pushed down to the DUSRemote User property value, updating it. The associated Default Value is alsoupdated.

If we change the DUS Remote User property value, that is the child value, it doesnot propagate up to the host; the parent Host PV User Property value remainsunchanged.

Now the child and parent properties are out of sync, and if we change the parentproperty value it is not reflected in the child property, though the default valuecontinues to be updated.

ServerTime synchronizationSever synchronization requirements.

Tivoli Netcool Performance Manager requires that the clocks on all Solaris serversrunning Tivoli Netcool Performance Manager modules be synchronized. IBMrecommends using NTP (or equivalent) to keep all Tivoli Netcool PerformanceManager synchronized to within 500 milliseconds.

Disk Usage ServerThis Disk Usage Server component is responsible for maintaining the propertiesnecessary for quota management (flow control) of DataChannel.

The DataChannel component requires a Disk Usage Server. This component isresponsible for maintaining the properties necessary for quota management (flowcontrol) of DataChannel. DataChannel components can only be added to hosts thatinclude a Disk Usage Server.

Multiple Disk Usage Servers can be configured per host; therefore, allowingmultiple DataChannel directories to exist on a single host. There are two majorreasons why a user may want to configure multiple Disk Usage Servers:


Disk space is running lowDisk space may be impacted by the addition of a new DataChannelcomponent. In which case, the user may want to add a new file systemmanaged by a new Disk Usage Server

Separate disk quota managementThe user may want to separately manage the quotas assigned to discreteDataChannel components. For more information, see “Disk quotamanagement.”

The user can assign the management of a new file system to a Disk Usage Serverby editing the local_root_directory property of that Disk Usage Server using theTopology Editor. The user can then add DataChannel components to the host, andcan assign the component to a Disk Usage Server, either in the creation wizard orby editing the DUS_NUMBER property inside the component.

Disk quota managementDisk Quota Management description.

The addition of a Disk Usage Server endeavors to make the process of assigningspace to a component much easier than it has been previously. No longer is a userrequired to calculate the requirements of each component and assign that spaceindividually, but components now work together to more effectively utilize thespace they have under the Disk Usage Server. Also, the user is relieved of trying tofigure out which component needs extra space and then changing the quota forthat component. Now, the user can just change the quota of the DUS and allcomponents on that Disk Usage Server will get the update and share the space onan as needed basis.

Good judgement of space requirements is still needed. However, the estimating ofspace requirements is being made at a higher level; and if an estimate is incorrect,only one number needs to be changed instead of potentially updating the quota foreach component separately.

Flow controlFlow Control description.

Optimized flow control further eliminates problems with component level quotas.Each component holds on to only a five hours of input and output, and once it hasreached this limit, it stops processing until the downstream component picks upsome of the data. This avoids the cascading scenario where one component stopsprocessing and the components feeding it begin to stockpile files, which results inthe quota being filled and causes all components to shut down because they haverun out of file space.

Installation or topology considerationsInstallation or Topology considerations for flow control.

DataChannel components can only be added to hosts that include a Disk UsageServer.


Notable subcomponents and featuresThe following sections describe a subset of the Tivoli Netcool PerformanceManager that should be considered before deciding on your topologyconfiguration.

DataLoadThe following sections provide information on the supported architectureconfigurations of DataLoad.

Collectors:

Collectors description.

The DataLoad collector takes in the unrefined network data and stores it in a filethat Tivoli Netcool Performance Manager can read. This file is known as a binaryobject format file (BOF).

The following processes are employed in the DataLoad module:v SNMP Collector - The DataLoad SNMP Collector sends SNMP requests to

network objects. Only the data requested by the configuration that was definedfor those network objects is retrieved.

v Bulk Collector - The Bulk Collector uses a Bulk Adaptor, which is individuallywritten for specific network resources, to format the unrefined data into a file,called a PVline file, which is passed to the Bulk Collector.

Multiple SNMP DataLoad collectors:

You can install multiple SNMP DataLoad collectors on the same host

In Tivoli Netcool Performance Manager 1.4.3, you can have multiple collectors perhost. This helps in reducing the server resources required. In certain customer sites,they have up to 40 SNMP collectors that required 40 hosts (any of which might bevirtual hosts). In the current scenario multiple collectors are allowed on a singlehost, which reduces the number of servers (physical or virtualized) but does notchange the disk or CPU requirements. A maximum of 16 collectors can beconfigured on a single host. However, each multiple collector that is addedrequires 4 GB RAM for efficient functioning.

This makes the solution cost-effective with minimum changes to the topology toaccommodate this for service providers with their current network and also forservice providers with growing networks.

CPU improvements came in the form of faster cores but now come as multiplecores. This change in computer hardware architecture drives changes in how TivoliNetcool Performance Manager scales. Tivoli Netcool Performance Manager used toscale by adding “commodity hardware” so you did not frequently encounter thescenario where it was not necessary to put multiple SNMP DataLoad collectors ona single box but now the “commodity hardware” is frequently a 4-16 core machine.So this change adds value to Tivoli Netcool Performance Manager scalability.

This scenario results in:v Reduction in number of operating system instancesv Reduction in related licensing, support, and maintenance costsv Ease in handling the upgrade process


Installation or topology considerations:

Installation and topology considerations for collectors.

The DataLoad modules can be loaded on lightweight servers and placed as close tothe network as possible (often inside the network firewall). Because a DataLoadmodule does not contain a database, the hardware can be relatively inexpensiveand can still reliably handle high volumes of data. The number of collectors is inturn driven by the number of required Technology Packs.

Up to 320 DataLoad modules can be supported per Tivoli Netcool PerformanceManager installation.

The number of collectors in your system affect the topology configuration. You canhave multiple BULK collectors, UBA or BCOL, on a single host. Starting fromTivoli Netcool Performance Manager 1.4.3, you can add and configure multipleSNMP collectors on the same host. Following is the server deployment for multipleSNMP DataLoad collectors.

Two servers with four DataChannels and four SNMP Collectors Topology.


DataChannelThe following sections provide information on the supported architectureconfigurations of DataChannel.

DataChannel subchannels:

Subchannel support.

Datachannel limit is increased from 8 to 16 in Tivoli Netcool Performance Manager1.4. Tivoli Netcool Performance Manager supports up to 40 subchannels perdatabase channel.

DataChannel remote:

Supported DataChannel deployment types.

Tivoli Netcool Performance Manager supports two deployment types forDataChannel:v DataChannel Standard, usually deployed on the central site. This requires the

standard DataChannel module.v DataChannel Remote Channel option, where the Sub-Channel component (also

called CME) is split from the rest of the central DataChannel and deployed onthe remote DataLoad server (usually on a remote site, behind a fire-wall).

This option is primarily intended for Managed Network Service Providers whoneed to place the DataChannel component at an end-user site, co-located with thedata collector. The benefits of the DataChannel Remote option are:v Allows Managed Network Service Providers to better align costs with revenues

as they scale their systems to support more end customers.v Improves distributed Fault managementv Closer to alarm receiver and correlationv Threshold detection resistant to disconnectionv Reduces hardware costsv Leverages available CPU if remote DataLoad under loaded (unused CPU can be

used by DataChannel remote - CME)

Please refer to “SNMP version support” on page 26 for more information aboutthis option.

The following sections describe both deployment types in more detail.

DataChannel "Standard":

Standard DataChannel installation.

DataChannel "Standard", usually deployed on the central site. This requires thestandard DataChannel module.

DataChannel Standard Installation


For firewall configuration recommendations, see “Firewall configuration” on page16.

DataChannel “Remote Channel Option”:

DataChannel remote installation.

In this mode, Tivoli Netcool Performance Manager allows the CME to be installedon a remote system away from the rest of the DataChannel components (such ascustomer premise equipment).

The DataChannel Remote system is composed of the following elements and obeysthe stated execution order:1. Collector2. File Transfer Engine3. Complex Metric Engine

All DataChannel Remote elements must be installed on the same server and filesystem.

Multiple DataChannel Remote systems can plug into the DataChannel system,which is composed of the following elements and obeys the following order ofexecution:

Loader Staging, which inovlves either of the following:v Daily Loader: interacts with the Database Serverv Hourly Loader: interacts with the Database Server

Tivoli Netcool Performance Manager on Solaris 10:

Options when deploying Tivoli Netcool Performance Manager on Solaris.

This section describes some basic scenarios for introducing Tivoli NetcoolPerformance Manager into the Solaris 10 operating environment, and options fordeploying Tivoli Netcool Performance Manager modules within Solaris 10containers. It is not an attempt to describe all possible deployment options.


Multiple SNMP collectors are supported on the same Solaris 10 server, as long aseach collector is isolated in a separate Solaris 10 container.

Note: Do not install more than one DataLoad SNMP collector in any given Solaris10 container. Installing two or more collectors in a container will causeperformance to degrade due to those collectors competing for CPU resources.

With the one exception noted above, all deployments of Tivoli NetcoolPerformance Manager modules within Solaris 10 containers are possible - forexample:v All modules can be installed within a single container on the same Solaris 10

server.v Each module can be installed in a separate container on separate Solaris 10

servers.v Any combination of module deployments in between the above deployments is

also possible (with the exception of the SNMP collector restriction noted above).

Note: In configuring Solaris containers for each Tivoli Netcool PerformanceManager component, follow the limitations for server CPU, disk, and memorydocumented for those components.

New installs on Solaris 10:

A scenario, which describes a possible deployment of Tivoli Netcool PerformanceManager.

In this scenario, a customer is installing Tivoli Netcool Performance Manager attheir site for the first time, and chooses to do so on a Solaris 10 server.

The possible deployment of Tivoli Netcool Performance Manager modules on asingle Solaris 10 server is:v DataLoad (DL)v DataChannel (DC)v DataMart (DM)v Database (DB)

Note: DataView (DV) installation is only supported on RHEL and AIX.

Tivoli Netcool Performance Manager inventory deployment:

Tivoli Netcool Performance Manager supports an architecture for the Inventoryprocess.

Tivoli Netcool Performance Manager supports an architecture for the Inventoryprocess, which is especially evident at the SNMP Discovery level. The SNMPDiscovery portion of inventory collection is implemented as a permanentlyrunning process (a daemon).

The new Inventory architecture provides several benefits:v The logic for defining Element uniqueness rules, as well as Element "correlation"

(when the same network Element is discovered several times from several of itsinterfaces) is now exposed (in the file inventory_elements.txt). This enables


you to adapt the rules for Elements that do not support the expected MIBvariables (the one Tivoli Netcool Performance Manager uses to implement theuniqueness and correlation rules).

v The Inventory GUI supports several features, typically implemented with hookscripts. The new architecture makes the hook scripts simpler and moremaintainable.

v Log messages issued by the Discovery process now comply with the centralizedLOG mechanism (that is, support has been added for logging to syslog).

The following sections explain the supported Inventory deployments (BULK andSNMP) and help you making deployment choices related to the SNMP Discoveryserver.

Tivoli Netcool Performance Manager Inventory is made up of Discovery,Synchronization, and Grouping phases.

Content of the SNMP inventory component:

Requirements of the SNMP Inventory Component.

The SNMP Inventory component is made up of the following:v Inventory CLI and Inventory GUI (profile management, as in 3.x)v 4.0 SNMP Discovery serverv Hook scripts

The SNMP Inventory component is installed by the DataMart installation - exceptthe new 4.0 SNMP Discovery server, which is part of the DataChannel installation.

The SNMP Inventory component (especially the SNMP Discovery process) isusually unique for the entire Tivoli Netcool Performance Manager system, and canserve multiple SNMP Collectors.

However, if several SNMP Inventory components must be installed, they cannot beinstalled on the same machine. In this case, you must install the entire DataMartcomponent on each machine.

For performance reasons. This configuration is unlikely given the low impact ofthe Inventory process on the overall system.

Content of the BULK inventory component:

Requirements of the BULK Inventory Component.

The BULK Inventory process is made up of:v Inventory CLI and Inventory GUI (profile management, as in 3.x)v Cron'ed CLI pollinvv Cron'ed CLI pollprofilev Hook scripts

The BULK Inventory component is installed by the DataMart installation.

As will be explained in the following deployment scenarios, there cannot beconnectivity issues between Bulk Collector and BULK Inventory. Therefore, IBMrecommends the following approach:


v Bulk Collector and BULK Inventory should never be separated by a WANand/or firewall, NAT, or any component that may hinder the connection.

Note: These configurations (WAN, Firewall, or NAT) are not supported.v For a critical use of the Bulk collector (for example, expected service levels,

billing, and so on), IBM recommends that you install a Bulk Inventory on thesame machine. In this case, you must run the DataMart installation as manytimes as there are Bulk collectors.

v For a standard use of the Bulk collector, IBM recommends that you install aunique Bulk Inventory on the DataMart machine. In this case, there should be avery reliable connection between the Bulk Inventory and the Database, andbetween the Bulk Inventory and the Bulk Collector (LAN).

DataChannel Central and Bulk Collector central:

Deployment configurations.

The deployment shown in the following figure is characterized by:v DataChannel deployed centrally (Standard)v BULK deployed centrally for critical usage

DataChannel Central and Bulk Collector Central (Critical)

The deployment shown in the following figure is characterized by:v DataChannel deployed centrally (Standard)v BULK deployed centrally for standard usage

DataChannel Central and Bulk Collector Central (Standard)


DataChannel Remote and Bulk Collector remote:


DataChannel Remote and Bulk Collector Remote

When DataChannel Remote is deployed (remotely), in order to process data flowgenerated by a bulk collector, the same machine needs to support:v Remote Sub-channelv Remote Bulk Collectorv Remote Bulk Inventory

DataChannel Central and Bulk Collector remote:


The deployment shown in the following figure is characterized by:v DataChannel deployed centrally (Standard)v BULK deployed remotely

DataChannel Central and Bulk Collector Remote


Tivoli Netcool Performance Manager does not support Bulk Inventory processesbeing on the other side of the firewall or though a WAN, compared to BulkCollector, as shown in the following figure:

Figure 6: Unsupported Firewall Configuration

DataChannel Central, SNMP Collector remote, and SNMP inventory central:


The deployment shown in the following figure is characterized by:v DataChannel deployed centrally (Standard)v SNMP collector deployed remotelyv SNMP Inventory deployed centrally

DataChannel Central, SNMP Collector Remote, and SNMP Inventory Central


DataChannel and SNMP Collector remote, and SNMP inventory central:


This deployment is characterized by:v DataChannel deployed remotelyv SNMP collector deployed remotelyv SNMP Inventory deployed centrally

Figure 8: DataChannel and SNMP Collector Remote, and SNMP Inventory Central

Related information:

Links to further information.v For more information on collectors and inventory deployments, see the

"Configuring the Discovery Server" section in the Installing Tivoli NetcoolPerformance Manager - Wireline Component

v For firewall recommendation related to the SNMP Discovery Server, see “SNMPinventory” on page 24.

Firewall configuration:

Firewall Configuration.

The following sections explain firewall configurations.

DataChannel standard:

Firewall support for a DataChannel standard configuration.

This section explains Tivoli Netcool Performance Manager firewall support, andthe protocols to open through them. The direction of the connection opening isshown by the following arrows.

Note: Modules are also centrally managed, so the management protocols also needto open through the firewalls.

As shown in the following figure, aside from file transfer and databaseconnectivity, management protocols need to pass through the firewalls. DataMart,using the internal 3002 protocol, manages SNMP Collectors. The ChannelManagement modules, through CORBA, manage the Bulk Collectors and theDataChannel modules. Additionally, these modules log through UDP to a remotelogger.

Note: You can use a different port other than port 3002.

Protocols Through Firewalls - DataChannel Standard


Channel management overview:

Channel management module communication.

The Channel Management modules communicate between machines supportingthe DataChannels, and these modules are the components that need static ports.The set of management modules for all DataChannels includes a Channel Manager,a Channel Name Server, a Log Server, and one Application Manager for eachmachine supporting the DataChannels, Bulk Collectors, and the Discovery server.For restrictive firewalls, the protocols used by these components need to be setstatically and the firewalls must be configured to allow these protocols through.

The Topology Editor can be used to statically set many of these ports.

Important: The Topology Editor can set the CORBA port for the managementcomponents (except the log server, which does not use CORBA), but not for theregular components (CMEs and FTEs, for example). Normally, the CORBA portsfor regular components are dynamic, because they communicate only with theAMGR, which is on the same machine and not affected by firewalls.

Configuring a static port:

Configuring static ports by using the Topology Editor.

About this task

When you upgrade from an existing installation or installing for the first time, youcan configure the static ports by using the Topology Editor.

Note: If you have an installation configuration file, you can use it when you runthe Topology Editor. Or, you can re-enter all relevant information and save theinstallation configuration file and use it for the next time you upgrade.

To configure static ports, follow these steps:

Procedure

1. Determine which ports you can set statically. For more information,see.“Choosing static ports” on page 18. Open these ports in the appropriatefirewalls.

2. Set the ports for the following protocols in the Topology Editor:v Log Server portv IOR Server port


v Name service portv Channel Manager CORBA portv For each host: the Application Manager CORBA portv For each Sub-Channel component: the trap port

Note: There are other protocols that you must open in the firewall that is notconfigured here.

3. Install the DataChannel. Save the installer configuration file.4. For each Bulk Collector that is running in DISCOVERY_MODE==noinventory,

manually edit the topology and add 3002_SERVICE_PORT for each Collector. Forexample, BCOL.2.36.3002_SERVICE_PORT=4003

5. Restart the channel management and the channels.DataView and DataMart also need ports that are opened in the firewallsee,“Standard Deployment of DataChannel” on page 19. See the DataView andDataMart documentation for information about configuring ports, if necessary.

What to do next

For information on assigning static ports to some DataChannel components, seeAssigning static port to some DataChannel components on remote server

Assigning static port to some DataChannel components on remote server:

When the FTE and CME components are on remote DataChannel server, a staticport must be configured. Then, the FTE is able to communicate with PBL from thelocal DataChannel.

Each component listens for inbound CORBA communications. By default, arandom port is selected and the port gets registered in the CNS shortly afterstartup. You can override the default port by using the following configurationsetting:PBL.CORBA_PORT = <port_number>

For example: PBL.CORBA_PORT = 9007

Note: This configured port must be allowed to access through the firewall.

Choosing static ports:

Choosing Static Ports.

About this task

You need to choose which ports to use. Ask your Network Administrator for theseports or choose the ports yourself, based on “Standard Deployment ofDataChannel” on page 19. Some ports used by Tivoli Netcool PerformanceManager are standard ports, like FTP. Other ports you need to choose. You can usethe same port on different machines. For example, you can assign the same port toall Application Managers.

There are several places you can look to see if a given port is already in use. Firstchoose the range, then check to see if it is in use.

When selecting ports, follow these guidelines:


v Choose your ports from the range 1024 to 32767. The other ranges are reserved(or sometimes used) for other applications. Ports 1 to 1023 are reserved portsand ports 32768 to 65535 are ephemeral ports.

v Check the file /etc/services on each machine and see if any of these ports arebeing used by a different application

v As a fail-safe, run netstat -a to see if this port is in use by other applications.Make sure the DataChannels and Channel Management are not running whenyou check.

Active and Passive FTP (Alcatel-Lucent 5620 SAM technology pack only):

Alcatel-Lucent 5620 SAM Technology Pack support.

The Alcatel-Lucent 5620 SAM Technology Pack supports both active and passiveFTP through the firewall.

Use the following guidelines when specifying passive or active data transfer modein URI (Universal Resource Identifier) specifications:v By default, the Alcatel-Lucent 5620 SAM uses active connections (traditional FTP

mode). You can, however, explicitly specify active data transfer mode byappending ;mode=active to the end of the FTP (File Transfer Protocol) URI(Universal Resource Identifier) as in the following example:

ftp://loginname:password@hostname//full/path/to/resource;mode=active

v To use passive data transfer mode, you must explicitly specify passive mode byappending ;mode=passive to the end of the FTP URL as in ther followingexample:

ftp://loginname:password@hostname//full/path/to/resource;mode=passive

For information on recommended ports, see the following URL:http://slacksite.com/other/ftp.html

Standard Deployment of DataChannel:

Describes the standard deployment of Datachannel.

The following table lists the module-to-protocol mappings for the standarddeployment of DataChannel.

Note the following:v The cells marked with an "X" identify the modules that are communicating with

one another.v FM represents the TRAP receiver of the Fault Management external station. This

is not a Tivoli Netcool Performance Manager module.

Module-to-Protocol Mapping For DataChannel Standard Deployment

Dev DL DC DM DB DV WEB FM Module/ Pair ProtocolPort Type /

Port # Dir. Property Setting in Topology Editor

X X SNMP Device- SNMPDataLoad

SNMP forcollection

Static UDP 161 ◄ ►

X X Bulk Device -Bulk DataLoad

FTP or TFTPor otherprotocol

Devicedependent

►


http://slacksite.com/other/ftp.html

http://slacksite.com/other/ftp.html



X X SNMPDataLoad -DataChannel

FTP forcollection

Static,non-configurableTCP 20, 21 orsFTP/TCP 22

◄

X X SNMPDataLoad -DataChannel

ChannelManageraccess toSNMP Coll.For Real Time

Static,configurableTCP 3002

◄ For each SNMP Collector:PVM_SNMP_COLL_SSDPORT=3002PVM_SSDPORT=3002 (These areentered using SERVICE_PORT in theTopology Editor: DataChannel >Admin Components > ChannelManager and DataChannel > AdminComponents > CORBA NamingServer Host)

X X Bulk DataLoad- DataChannel

FTP metriccollection OrSFTP

Static,non-configurableTCP 20, 21SFTP 22

◄ See the Technical Note TivoliNetcool Performance ManagerDataChannel Secure File TransferInstallation in the file tech note -sftp.pdf on the CD.

X X LOG UDP Static,configurableUDP 25000

► DC configuration:GLOBAL.LOG_PORT

X X CNS foracquiring thename service


► DC configuration:GLOBAL.ORB_NAMESERVICE_PORT

X X Channel NameService ORB


► DC configuration:CNS.CORBA_PORT

X X ChannelManager ORB


► DC configuration:CMGR.CORBA_PORT

X X ApplicationManager ORB


◄ DC configuration:AMGR.<hostname>. CORBA_PORT(AMGR.<hostname> is a property istaken from the location chosen forthe Disk Usage Server host.)

X X Trapd service Static,configurableTCP 162

► DC configuration:CME.x.y.TRAPD_PORT

X X SNMPDataLoad -DataMart

AutomaticDiscovery


◄ On each SNMP Collector:PVM_SNMP_COLL_ SSDPORT=3002PVM_SSDPORT=3002 (These areentered using SERVICE_PORT in theTopology Editor: DataChannel >Admin Components > ChannelManager and DataChannel > AdminComponents > CORBA NamingServer Host)

X X TCP forconfigurationreload trigger


◄

X X Bulk DataLoad-DataMart

FTP inventoryOr SFTP

Static,non-configurableTCP 20, 21SFTP 22

► ► See the Technical Note TivoliNetcool Performance ManagerDataChannel Secure File TransferInstallation in the file tech note -sftp.pdf on the CD.

X X TCP forconfigurationreload trigger


◄ DC configuration:BCOL.x.x.3002_SERVICE_PORT




X X SNMPDataLoad -database

NET 8 reloads Static,configurableTCP 1521

► listener.ora on Oracle server:

LISTENER =(DESCRIPTION_LIST=(DESCRIPTION =(ADDRESS =(PROTOCOL =IPC)(KEY =EXTPROC)))(DESCRIPTION =(ADDRESS =(PROTOCOL =TCP)(HOST =pl2dbs1)(PORT = 1521))))tnsnames.ora on Oracleserver and all clients:PV =(DESCRIPTION =(ADDRESS_LIST =(ADDRESS =(PROTOCOL =TCP)(HOST =pl2dbs1)(PORT = 1521)))(CONNECT_DATA =(SERVICE_NAME =PV.world)))

X X Bulk DataLoad- database


►

X X DataChannel -database


►

X X Database -DataView

NET 8 forqueries


◄


Static,ConfigurableTCP 9005

◄ DC configuration:CNS.CORBA_PORT

X X ChannelManager ORBfor NearReal-Time andReal Timeaccess.


◄ DC configuration:CMGR.CORBA_PORT

The following sections describe additional device-specific protocol mappings,including:v “Alcatel 5620 NM mappings”v “Alcatel-Lucent 5620 SAM mappings” on page 22v “Cisco CWM mappings” on page 22v “Nortel CS2000 mappings” on page 22v “Radcom Probe” on page 23

Alcatel 5620 NM mappings:

Alcatel 5620 NM Mappings.

The following table lists the module-to-protocol mappings for integrating with theAlcatel 5620 NM.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 19, if a firewall sits betweenTivoli Netcool Performance Manager and the Alcatel 5620 NM servers.

Module-to-Protocol Mappings for Integrating with Alcatel 5620 NM

5620 NM DL DC DM DB DV WEB Module Pair Protocol Port Type /Port #

Direction

X X 5620 -DataLoadQCIF

CORBAconnection to5620 NMevent bus

Static,configurable8248

◄


X X 5620 -DataLoadBulk LoadBalancer(BLB)

FTP and FTPData forbinarytransferduringremoteinstallation

Static, non-configurableTCP 20, 21

◄

Alcatel-Lucent 5620 SAM mappings:

Alcatel-Lucent 5620 SAM Mappings.

The following table lists the module to protocol mappings for integrating with theAlcatel-Lucent 5620 SAM.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 19, if a firewall sits betweenTivoli Netcool Performance Manager and the Alcatel-Lucent 5620 SAM servers.

Module-to-Protocol Mappings for Integrating with Alcatel-Lucent 5620 SAM

5620 SAM DL DC DM DB DV WEB Module Pair Protocol Port Type /Port #

Direction

X X 5620 -DataLoadSAMIF

SOAP/XMLJMS

Static,configurable8080 Staticconfigurable1099

◄ ◄

X X 5620 -DataLoadBulk LoadBalancer(BLB)

FTP and FTPData forbinarytransferduringremoteinstallation

Static, non-configurableTCP 20, 21

◄

Cisco CWM mappings:

Cisco CWM Mappings.

The following table lists the module-to-protocol mappings for integrating with theCisco CWM.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 19, if a firewall sits betweenTivoli Netcool Performance Manager and the Cisco CWM servers.

Module-to-Protocol Mappings for Integrating with the Cisco CWM

CWM DL DC DM DB DV WEB Module Pair Protocol Port Type /Port #

Direction

X X CWM -DataLoadBulk

Issue GETsand SETs tothe CWMReceiveInventoryevent TRAPs

Static UDP161 StaticUDP 162

◄ ►

X X CWM -DataLoadBulk

Connectionto Informixfor gettingdata files


◄

Nortel CS2000 mappings:

Nortel CS2000 Mappings.


The following table lists module-to-protocol mappings for integrating with theNortel CS2000.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 19, if a firewall sits betweenTivoli Netcool Performance Manager and the Nortel CS2000 servers.

Module-to-Protocol Mappings for Integrating with the Nortel CS2000

CS2K DL DC DM DB DV WEB Module Pair Protocol Port Type /Port #

Direction

X X CS2K -DataLoadBulk

FTP transferbetweenDataLoadand NortelEMS.


►

Radcom Probe:

Radcom Probe.

The following table lists the module-to-protocol mappings for integrating with theRadcom Probe.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 19, if a firewall sits betweenTivoli Netcool Performance Manager and the Radcom Probe servers.

Module-to-Protocol Mappings for Integrating with the Radcom Probe

RadcomProbe

DL DC DM DB DV WEB Module Pair Protocol Port Type / Port # Direction

X X Radcom Probe -DataLoad Bulk

Bulk SQL betweenDataLoad andRadcom QManagerOracle DB.

Oracle SQL*Netdefault TCP 1521

►

DataChannel "Remote Channel Option":

Additional ports to open for the DataChannel "Remote Channel Option."

This section describes the additional ports to open for the DataChannel "RemoteChannel Option."

DataChannel "Remote Channel Option" Deployment


The following table lists the module to protocol for the DataChannel remoteoption. For more information, see “SNMP version support” on page 26.

Module to Protocol Mappings for DataChannel Remote Option (Outside Firewall)

Dev DCR DCL DM DB DV WEB FM Module Pair Protocol Port Type /Port #

Direction Config Setting

X X DC Remote(DCR) - DCLoader (DCL)

FTP metriccollection OrSFTP

Static, NonConfigurableTCP 20, 21SFTP 22

◄ ◄ See document "Tivoli NetcoolPerformance Manager DataChannelSecure File Transfer Installation-Technical Note " in file "tech note -sftp.pdf" from the CD

X X LOG UDP Static,ConfigurableUDP 25000

► DC config GLOBAL.LOG_PORT

X X CNS foracquiring thename service


► DC config:GLOBAL.ORB_NAMESERVICE_PORT



► DC config: CNS.CORBA_PORT

X X ChannelManager ORB


► DC config: CMGR.CORBA_PORT

X X ApplicationManager ORB


◄ DC config:AMGR.<hostname>.CORBA_PORT(AMGR.<hostname> is a property istaken from the location chosen forthe Disk Usage Server host.)

X X Trapd service Static,ConfigurableUDP 162

► DC config: CME.x.y.TRAPD_PORT

X X CME ORB forNear RealTime

StaticConfigurationTCP 9006

◄ DC config: CME.x.y.CORBA_PORT

X X DC Remote(DCR) -database (DB)

NET 8 forqueries


► listener.ora and tnsnames.ora onOracle server. Port 1521 is supposedto be already configured by standardports settings - see table above.

v DCR represents the Remote server supporting DataLoad and the Sub-Channelcomponent of DataChannel.

v DCL represents the other modules of the DataChannel (Loader), deployedLocally.

v Fault Management external station - This is not a Tivoli Netcool PerformanceManager module.

v There is no default line created in the configuration file by the installer, but willbe leveraged if configured.

DataMartThe following sections provide information on the supported architectureconfigurations of DataMart.

SNMP inventory:

This section highlights the various protocol exchanged between Tivoli NetcoolPerformance Manager components. It can be used to figure out the relevantfirewall configuration depending on where the various components reside (SNMPDiscovery process, DataChannel).

As described previously, in most cases the SNMP Discovery process is deployed onthe DataMart server and does not require you to open specific ports throughfirewalls. In very specific cases, the SNMP Discovery process needs to be deployedremotely, and requires you to open additional firewall ports.

“SNMP inventory” shows the protocols through firewalls deployment.


The following figure shows the most common deployment for Protocols ThroughFirewalls - Central SNMP Discovery Process.

In Module-to-Protocol Mappings for the Tivoli Netcool Performance Manager SNMPDiscovery Process:v DISC is the SNMP Discovery process, deployed on the DataLoad server.v FM represents the Fault Management external station. This is not a Tivoli

Netcool Performance Manager module.

Module-to-Protocol Mappings for the Tivoli Netcool Performance Manager SNMPDiscovery Process

Dev DL DC DISC DM DB DV WEB FM Module Pair Protocol Port Type /Port #

Dir. Property Setting in Topology Editor

X X Discoveryserver -database

NET 8reloads


► Listener.ora on server side,tnsnames.ora on client side.

X X SNMPDataLoad -Discoveryserver

Disc server,fordiscoveryformulaexecutions

Static,non-configurableTCP 3002

◄

X X DataChannel(CME notinvolved) -Discoveryserver

LOG UDP Static,configurableUDP 25000

◄ DC configuration: GLOBAL.LOG_PORT

X X CNS foracquiringthe nameservice


◄ DC configuration:GLOBAL.ORB_NAMESERVICE_PORT

X X Disc server'sAMGRtalking totheDataChannel

ChannelNameService ORB


◄ DC configuration: CNS.CORBA_PORT

X X ChannelManagerORB


◄ DC configuration:CMGR.CORBA_PORT

X X ApplicationManagerORB


► DC configuration: AMGR.<hostname>. CORBA_PORT

X X Discoveryserver -DataMartinventory

Discoveryserver ORB

Dynamic,configurable

◄ DC configuration: DISC.<hostname>.1. CORBA_PORT (isinherited from the DataMart hostCORBA_PORT property.)

X X DataChannel(CME notinvolved) -DataMartinventory

CNS foracquiringthe nameservice


◄ DC configuration:GLOBAL.ORB_NAMESERVICE_PORT

Note: For most deployments, where the Discovery server is on the central site,these ports do not have to be opened, except the one described in the second rowof

“SNMP inventory” on page 24

(if DataLoad is behind the firewall).

See Professional Services for more information.


SNMP version support:

Tivoli Netcool Performance Manager can automatically detect the SNMP versionsupported by each element on the network, between SNMP Versions 1, 2c, and 3.

Tivoli Netcool Performance Manager supports the following PDU sets for thefollowing SNMP versions:v SNMP Version 1 - Get / GetNext / Setv SNMP Version 2c - Get / GetNext / GetBulk / Setv SNMP Version 3 - Get / GetNext / GetBulk / Set, MD5 and SHA-1

authentication (with AES and DES private encryption)

Note: For more information about SNMPv3 support, see Installing libcrypto.so inInstalling Tivoli Netcool Performance Manager - Wireline Component.

Technology packsTechnology packs description.

Tivoli Netcool Performance Manager Technology Packs are custom designedcollections of MIBs, discovery formulas, collection formulas, complex formulas,grouping rules, reporters, and other functions. Technology packs provide all TivoliNetcool Performance Manager needs to gather data for targeted devices.Technology packs make it possible for Tivoli Netcool Performance Manager toreport on technology from multiple vendors.

Installation or topology considerations:

Installation and topology considerations for technology packs.

If you are creating a UBA collector, you must associate it with a specific technologypack.

Note: General installation information for technology packs can be found in theInstalling and Configuring Technology Packs, pack-specific installation information isalso provided. Consult both sets of documentation for important installation ortopology information.

Note: To enable Cognos 10 common reporting in wireline technology packs, installthe JDBC Driver. For more information, see Installing and Using JDBC Driver. Youcan find the tnpm-jdbc.tar file in this location: /<JazzSM_HOME>/products/tnpm/dataview/misc/jdbc. By default, <JazzSM_HOME> is /opt/IBM/JazzSM.

Typical installation topologyExample topology scenarios.

Table 2 provides an example of where to install Tivoli Netcool PerformanceManager components, using four servers. Use this example as a guide to help youdetermine where to install the Tivoli Netcool Performance Manager components inyour environment.


Basic topology scenarioA basic example topology.

Table 2. Tivoli Netcool Performance Manager basic topology scenario

Server Name

Tivoli Netcool PerformanceManager Components

Hosted Notes

delphi v Oracle/DB2 server

v Tivoli NetcoolPerformance ManagerDatabase

v Tivoli NetcoolPerformance ManagerDataMart

v Tivoli NetcoolPerformance ManagerDiscovery Server

Install the Topology Editorand primary deployer on thissystem.

corinth v Oracle/DB2 client

v Tivoli NetcoolPerformance ManagerDataLoad, SNMP collector

v Tivoli NetcoolPerformance ManagerDataLoad, Bulk Loadcollector

You could install TivoliNetcool PerformanceManager componentsremotely on this system.

sparta v Oracle/DB2 client

v Tivoli NetcoolPerformance ManagerDataChannel

You could install TivoliNetcool PerformanceManager componentsremotely on this system

athens v Oracle/DB2 client

v Jazz for ServiceManagement

v Tivoli NetcoolPerformance ManagerDataView

You could install TivoliNetcool PerformanceManager componentsremotely on this system.Your configuration can use apre-existing Jazz for ServiceManagement, or install andinclude a new instance.


Intermediate topology scenarioAn intermediate example topology scenario.

Table 3. Tivoli Netcool Performance Manager intermediate topology scenario

Server Name


Hosted Notes













thessaloniki v Oracle/DB2 client


Also running the ChannelManager.



v High Availability Manager


This server contains aduplicate set of collectors toallow for high availability.






This scenario has an added copy of both collectors on corinth to a secondmachine, thessaloniki, for the purposes of failover. HAM only manages SNMPcollectors; therefore, the HAM in this scenario will manage availability of theDataLoad SNMP collector and not the Bulk Load collector. The HAM must be puton the same machine as the channel manager.

Advanced topology scenarioAn advanced example topology scenario.

Table 4. Tivoli Netcool Performance Manager advanced topology scenario

Server Name


Hosted Notes













thessaloniki v Oracle/DB2 client


Also running the ChannelManager.



v High Availability Manager



Table 4. Tivoli Netcool Performance Manager advanced topology scenario (continued)

Server Name


Hosted Notes





rhodes v Oracle/DB2 client




High AvailabilityHigh Availability description.

High availability can be implemented for Tivoli Netcool Performance Manager intwo forms:

High Availability Manager (HAM)A DataChannel component that can be configured to handle availability ofSNMP collectors.

For information on High Availability for DB2 database, see High Availabilityand Disaster Recovery Options for DB2 for Linux, UNIX, and Windows fromthe following location:http://www.redbooks.ibm.com/redbooks/pdfs/sg247363.pdf.

To know more about Tivoli Netcool Performance Manager wireline on RedHat Enterprise Linux (RHEL) in a High Availability (HA) configurationwith High Availability Disaster Recovery feature (HADR), seehttps://www.ibm.com/developerworks/community/wikis/form/api/wiki/2eed5677-1246-4b21-9e6a-3b0866204ca4/page/807bc74b-e4c1-4c18-ab69-d8b9da5dfea8/attachment/d5c45034-a140-465b-a11a-f4052ac3a094/media/High%20Availability%20for%20Tivoli%20Netcool%20Performance%20Manager%20133-v12.docx

Veritas Cluster or Sun Cluster (referred to as HA within the documentation)This method of implementing high availability has a much broader scopeand can cover all or a combination of the database, DataChannel, DataMartand DataView components.

The following High Availability (HA) documents are available for download fromthe Integrated Service Management Library (ISML), https://www-304.ibm.com/software/brandcatalog/ismlibrary/.

Tivoli Netcool Performance Manager Wireline Cluster Operations Guide 1.4.3Describes an example system that was configured to provide highavailability.


http://www.redbooks.ibm.com/redbooks/pdfs/sg247363.pdf

https://www.ibm.com/developerworks/community/wikis/form/api/wiki/2eed5677-1246-4b21-9e6a-3b0866204ca4/page/807bc74b-e4c1-4c18-ab69-d8b9da5dfea8/attachment/d5c45034-a140-465b-a11a-f4052ac3a094/media/High%20Availability%20for%20Tivoli%20Netcool%20Performance%20Manager%20133-v12.docx





https://www-304.ibm.com/software/brandcatalog/ismlibrary/

https://www-304.ibm.com/software/brandcatalog/ismlibrary/

Tivoli Netcool Performance Manager Wireline High Availability Installation andConfiguration 1.3

Describes the steps necessary to install and configure components of TivoliNetcool Performance Manager in a highly available configuration.

Tivoli Netcool Performance Manager Wireline High Availability Overview 1.3Describes high availability solutions for the Tivoli Netcool PerformanceManager product.

Sun Cluster Tivoli Netcool Performance Manager Wireline Agent Guide 1.1Describes how Sun Clusters can be used with Tivoli Netcool PerformanceManager to create a high availability Tivoli Netcool Performance Managersystem.

For more information about High Availability Manager, see Chapter 9, “Using theHigh Availability Manager,” on page 193.

Installation or topology considerationsInstallation and topology considerations for the High Availability Manager.

The HAM must be put on the same machine as the channel manager.



Chapter 2. Requirements

Details of all Tivoli Netcool Performance Manager requirements.

A complete set of requirements for Tivoli Netcool Performance Manager 1.4.3.

IBM Prerequisite ScannerIBM Prerequisite Scanner is a stand-alone prerequisite checking tool that analyzessystem environments before the installation or upgrade of a Tivoli product or IBMsolution.

The IBM Prerequisite Scanner can be used to check for the presence of TivoliNetcool Performance Manager requirements.

Important: The compatible version of Prerequisite scanner for Tivoli NetcoolPerformance Manager 1.4.3 is v1.2.0.18.

Product codes that are used to support Tivoli Netcool Performance Manager are asfollows:

Product code Platform Description

TND UNIX IBM Tivoli NetcoolPerformance Manager withIBM DB2

TNO UNIX IBM Tivoli NetcoolPerformance Manager withOracle

This table shows the environment variables that must be set forTivoli Netcool Performance Manager after the Oracle database is installed to verifythat the installation is successful:

Product version Installation option Environment variable

IBM Tivoli NetcoolPerformance ManagerVersion 1.4.2 and 1.4.3

Impact Oracle serverinstallation only

TNPM_ORACLE_SERVER

Impact Oracle clientinstallation only

TNPM_ORACLE_CLIENT

Standalone installation forOracle database

TNPM_STAND_ALONE

To use the IBM Prerequisite Scanner on Tivoli Netcool Performance Manager 1.4.3,you must install the 1.4.3.0-TIV-TNPM-IF0001 interim fix from IBM Fix Central.

Note: You must run the IBM Prerequisite Scanner tool as db2 user. If you are usinga non-default DB2 username, you must use the same name to run this tool.


https://www-945.ibm.com/support/fixcentral/swg/selectFix?product=ibm%2FTivoli%2FNetcool+Performance+Manager&fixids=1.4.3.0-TIV-TNPM-IF0001&source=SAR&function=fixId&parent=ibm/Tivoli

Plan your installationYou can choose to install a full installation of Tivoli Netcool Performance Manager1.4.3 in a stand-alone environment or in a distributed environment.

Pre-requisite software

Table 5. Pre-requisite software

Product Version

Operating system 64-bit only v Red Hat Enterprise Linux (RHEL) 7.2 if you are doinga fresh installation

v Red Hat Enterprise Linux (RHEL) 7.2 for TivoliNetcool Performance Manager upgrade

Important: Ensure that RHEL operating system isupgraded to 7.2 before you proceed to Tivoli NetcoolPerformance Manager upgrade.

v IBM AIX 7.1

v Oracle Solaris 10 update 10 or higher

Note: Based on your Tivoli Netcool PerformanceManager environment setup, ensure that the Globalzone and its corresponding Virtual Machines (VM)has the recommended Solaris version.

Note: For the required packages, see“Supported operating systems and modules” on page43.


Table 5. Pre-requisite software (continued)

Product Version

Databases

v Oracle Database 12c support (12.1.0.2)

v Support for 64-bit Oracle 12c (12.1.0.2)

v Enterprise Edition on Solaris (SPARC), Linux, and AIX

v Oracle 12c Enterprise Edition must include thepartitioning option.

v IBM DB2 Advanced Workgroup Server Edition11.1.1.1, Linux 64-bit only

v IBM Data Server Client 11.1.1.1, Linux 64-bit only

Attention: If your IBM DB2 new or upgradedeployment exceeds 16 core processors and 128 GBmemory, you must purchase the DB2 OEM HighCapacity Add-on. For more information, contact yourIBM representative or IBM reseller and specify this partnumber:

v D1MWLLL

IBM DB2 OEM High Capacity Add-on per VirtualProcessor Core License and SW Subscription andSupport 12 Months

Note: You must install the IBM Data Server Client(64-bit) in a distributed environment only. It is notrequired in a standalone environment. In a distributedenvironment, install the DB2 client software on eachserver where you plan to install a Tivoli NetcoolPerformance Manager component, except for where youinstalled the DB2 server.

Java v Java Runtime Environment (JRE) 1.8, 32-bit for allbrowsers

v IBM-JRE 1.7, 64-bit is required for DataView that runson Dashboard Application Services Hub that isinstalled together with the Jazz for ServiceManagement 1.1.3.0

Tivoli Common Reporting Tivoli Common Reporting 3.1.3.0

Jazz for Service Management Jazz for Service Management 1.1.3.0Note: See Jazz for Service Management 1.1.3.0 at IBMKnowledge Center.

Web browsers v Internet Explorer 11.0

v Mozilla Firefox ESR 38, 45

v Google Chrome (most recent version)

Note: Enable JavaScript and cookies

Note: Jazz for Service Management includes installation media for Jazz for ServiceManagement, IBM DB2, IBM WebSphere Application Server, and the Quick StartGuide. Jazz for Service Management has a number of integration services:v Administration Services UIv IBM Dashboard Application Services Hub

Chapter 2. Requirements 35

http://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/psc_ic-homepage.html

v Jazz for Service Management extension for IBM WebSpherev IBM Tivoli Common Reporting

Minimum requirements for installationThe minimum required host specifications for a Tivoli Netcool PerformanceManager deployment.

Solaris hardware requirements

Tivoli Netcool Performance Manager hardware requirements for the Solarisenvironment.

Tivoli Netcool Performance Manager has the following minimum hardwarerequirements for the Solaris environment.v 4 x SPARC64 VI (dual-core) 2.4 GHz or 3 x SPARC64 VII (quad-core) 2.88 GHz

processorv 16 GB Memoryv 2 x 146 GB HDD

If you are deploying in a distributed environment, each server/zone requires:

1 x SPARC64 VI (dual-core) 2.4 GHz or 1 x SPARC64 VII, (quad-core) 2.88 GHzprocessor, 4 GB RAM, 146 GB disk space.

AIX hardware requirements

Tivoli Netcool Performance Manager hardware requirements for the AIXenvironment.

Tivoli Netcool Performance Manager has the following minimum requirements forthe AIX environment:v 3 x POWER7 (Quad Core) 3.0 GHz processor or or 2 x POWER8 (Octo Core)

2.32 GHz processorv 16 GB Memoryv 2-x-146 GB HDD

If you are deploying in a distributed environment, each server/LPAR requires:v 1 x POWER7 (Quad Core) 3.0 GHz processor or 0.5 x POWER8 (Octo Core) 2.32

GHz processorv 4-GB RAM; 146 GB disk space.

Other deployment configurations must be sized by IBM Professional Services.


Linux hardware requirements

Tivoli Netcool Performance Manager has a minimal deployment space requirementon Linux.

Tivoli Netcool Performance Manager has the following minimum requirements forthe Linux environment:v 3 x Intel Xeon 5500/5600 series processors (quad-core), 2.4 GHz or greater.v 16 GB memoryv 2 x 300 GB HDD

If you are deploying in a distributed environment, each server/Virtual Machinerequires:v 1 x Intel Xeon 5500/5600 series processor (quad-core) 2.4 GHzv 4 GB RAMv 300 GB disk space

Other deployment configurations must be sized by IBM Professional Services.

Oracle and DB2 deployment space requirementsTivoli Netcool Performance Manager has a minimal deployment space requirementfor Oracle servers.

When you install Oracle, the following host must confirm the

previously stated hardware requirements for AIX, Solaris, and Linux. However, thedatabase may experience problems if sufficient swap space is not provided.v The same amount of Swap as RAM must be present on the Oracle server host in

a distributed Tivoli Netcool Performance Manager system.v Twice as much Swap as RAM must be present on the Oracle server host for a

Tivoli Netcool Performance Manager proof of concept install.

Table 6. RAM Swap Space

RAM Swap Space

Between 1 GB and 2 GB 1.5 times the size of RAM

Between 2 GB and 16 GB Equal to the size of RAM

More than 16 GB 16 GB

Physical database design

A high-quality physical database design is an important factor in a successfuldatabase deployment. The choices and decisions that are made during physicaldatabase design have a long lasting effect and far reaching impact in terms ofoverall database health and day-to-day administrative overhead that is incurred ina data center. Understanding DB2 features and how it can be applied to meet thebusiness needs is crucial to come up with a high-quality physical database designthat can adapt to evolving business requirements over time.

A high-quality physical database design must consider the following items:


v Business service level agreement (SLA)v I/O bandwidthv Performance objectives such as response time and throughputv Recovery timev Maintenance windowv Administrative overheadv Reliability, availability, and serviceability (RAS)v Data (lifecycle) management

As your business requirements change, you must reassess your physical databasedesign. This reassessment must include periodic revisions of the design. Ifnecessary, make configuration and data layout changes to meet your businessrequirements.v Minimize I/O traffic.v Balance design features that optimize query performance concurrently with

transaction performance and maintenance operations.v Improve the performance of administration tasks such as index creation or

backup and recovery processing.v Reduce the time database administrators spend in regular maintenance tasks.v Minimize backup and recovery elapsed time.v Reassess overall database design as business requirements change.

Use the following design best practices for RAS:v Design your business infrastructure with a solid sizing and capacity planning for

current and future needs as the business grows.v Identify and eliminate single point of failures (SPOF) in the business

infrastructure.v Implement redundancy in your infrastructure such as networks and mirrored

disks.v Implement high availability and disaster recovery solutions in all layers of

business infrastructure such as, database, application, and middleware.v For DB2 databases:

– Use separate high performing disks for data, transaction logs, and archivedlogs.

– Use mirrored logs for redundancy.– Create a backup and restore plan for backing up databases, table paces, and

transactional logs.

For more information about DB2 product configurations and best practices, seehttps://ibm.biz/Bdx2ew.

Disk and memory requirements

Ensure that an appropriate amount of disk space is available for your DB2environment, and allocate memory accordingly.


https://ibm.biz/Bdx2ew

Disk requirements

The disk space that is required for your product depends on the type ofinstallation you choose and the type of file system you have. The DB2 Setupwizard provides dynamic size estimates based on the components that are selectedduring a typical, compact, or custom installation.

Remember to include disk space for required databases, software, andcommunication products. Ensure that the file system is not mounted withconcurrent I/O (CIO) option.

On Linux and UNIX operating systems, 2 GB of free space in the /tmp directory isrecommended, and at least 512 MB of free space in the directory is required.

Note: On Linux and UNIX operating systems, you must install your DB2 productin an empty directory. If the directory that you have specified as the install pathcontains subdirectories or files, your DB2 installation might fail.

Memory requirements

Memory requirements are affected by the size and complexity of your databasesystem, the extent of database activity, and the number of clients accessing yoursystem. At a minimum, a DB2 database system requires 256 MB of RAM. For asystem running just a DB2 product and the DB2 GUI tools, a minimum of 512 MBof RAM is required. However, 1 GB of RAM is recommended for improvedperformance. These requirements do not include any additional memoryrequirements for other software that is running on your system. For IBM dataserver client support, these memory requirements are for a base of five concurrentclient connections. For every additional five client connections, an extra 16 MB ofRAM is required.

For DB2 server products, the self-tuning memory manager (STMM) simplifies thetask of memory configuration by automatically setting values for several memoryconfiguration parameters. When enabled, the memory tuner dynamicallydistributes available memory resources among several memory consumersincluding sort, the package cache, the lock list, and buffer pools.

Paging space requirements

DB2 requires paging, also called swap to be enabled. This configuration is requiredto support various functions in DB2, which monitor or depend on knowledge ofswap/paging space utilization. The actual amount of swap/paging space that isrequired varies across systems and is not solely based on memory utilization byapplication software.

A reasonable minimum swap/paging space configuration for most systems is25-50% of RAM. These higher requirements are due to virtual memorypre-allocated per database instance, and retained virtual memory in the case ofSTMM tuning multiple databases. More swap/paging space might be wanted toprovision for unanticipated memory overcommitment on a system.

For more information about Prerequisites for a DB2 database server installation (Linuxand UNIX), see http://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/c0059823.html


http://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/c0059823.html


Some DB2 configuration parameters settings

When a DB2 database instance or a database is created, a correspondingconfiguration file is created with default parameter values. You can modify theseparameter values to improve performance and other characteristics of the instanceor database. It is recommended that the two parameters; instance_memory anddatabase_memory are set to the default values in Tivoli Netcool PerformanceManager 1.4.3.

The disk space and memory that is allocated by the database manager that isbased on default values of the parameters might be sufficient to meet your needs.In some situations, however, you might not be able to achieve maximumperformance by using these default values.

Each transaction processing environment is unique in one or more aspects. Thesedifferences can have a profound impact on the performance of the databasemanager when using the default configuration. For this reason, you might berequired to tune your configuration for your environment.

Configuration files contain parameters that define values such as the resourcesallocated to the DB2 database products and to individual databases, and thediagnostic level. There are two types of configuration files:

The database manager configuration file for each DB2 instance

The database manager configuration file is created when a DB2 instance iscreated. The parameters that it contains affect system resources at theinstance level, independent of any one database that is part of thatinstance. Values for many of these parameters can be changed from thesystem default values to improve performance or increase capacity,depending on your system's configuration.

Database manager configuration parameters are stored in a file nameddb2systm. This file is created when the instance of the database manager iscreated. In Linux and UNIX environments, this file can be found in thesqllib subdirectory for the instance of the database manager.

The database configuration file for each individual database

A database configuration file is created when a database is created, and islocated where that database exists. There is one configuration file perdatabase. Its parameters specify, among other things, the amount ofresource to be allocated to that database. Values for many of theparameters can be changed to improve performance or increase capacity.Different changes might be required, depending on the type of activity in aspecific database.

All database configuration parameters are stored in a file namedSQLDBCONF. These files cannot be directly edited, and can be changed orviewed via a supplied API or by a tool, which calls that API.

To change the database manager configuration parameters, use UPDATEDATABASE MANAGER CONFIGURATION command. Database configurationparameters can be changed by using UPDATE DATABASE CONFIGURATIONcommand.


Attention: If you edit db2systm, SQLDBCON, or SQLDBCONF by using amethod other than those provided by the database manager, you mightmake the database unusable. Do not change these files by using methodsother than those documented and supported by the database manager.

instance_memoryThe instance_memory is the database manager instance memoryconfiguration parameter. This parameter specifies the maximum amount ofmemory that can be allocated for a database partition if you are using DB2database products with memory usage restrictions or if you set it to aspecific value. In Tivoli Netcool Performance Manager 1.4.3, set thisparameter to AUTOMATIC. This setting allows instance memory to grow asneeded.

database_memoryThe database_memory is configuration parameter specifies the size of thedatabase memory set. The database memory size counts towards anyinstance memory limit in effect. The setting must be large enough toaccommodate the following configurable memory pools: bufferpools, thedatabase heap, the locklist, the utility heap, the package cache, the catalogcache, the shared sort heap, and an additional minimum overflow area of5%. In Tivoli Netcool Performance Manager 1.4.3, set this parameter toAUTOMATIC. The initial database memory size is calculated based on theunderlying configuration requirements.

logprimaryNumber of primary log files configuration parameter.

This parameter allows you to specify the number of primary log files to bepreallocated. The primary log files establish a fixed amount of storage thatis allocated to the recovery log files.

logsecond

Number of secondary log files configuration parameter.

This parameter specifies the number of secondary log files that are createdand used for recovery log files. The secondary log files are created only asneeded.

Following database configuration parameter values are set in the DB2 database forIBM Tivoli Netcool Performance Manager 1.4.3.

Log file size (4 KB) (LOGFILSIZ) = 8192This parameter defines the size of each primary and secondary log file. Thesize of these log files limits the number of log records that can be writtento them before they become full and a new log file is required.v Number of primary log files (LOGPRIMARY) = 50v Number of secondary log files (LOGSECOND) = -1

For more information about these and other parameters, see http://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.config.doc/doc/c0004555.html


http://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.config.doc/doc/c0004555.html



Screen resolutionRecommended screen resolution details.

A screen resolution of 1024 x 768 pixels or higher is recommended when you runthe deployer.

Minimum requirements for a proof of concept installationTivoli Netcool Performance Manager has minimum required host specifications forProof of Concept (POC) deployments.

Note: The minimum requirements do not account for extra functions such as TivoliNetcool/OMNIbus Web GUI, IBM Cognos and MDE, each have extra memory andCPU impacts.

Solaris hardware requirements (POC)

The minimum system requirements for a proof of concept installation on Solaris.v 2 x SPARC64 VI (dual-core) 2.4 GHz or 2 x SPARC64 VII (quad-core) 2.88 GHz

processor.v 16 GB Memoryv 1 x 146 GB HDD

To support:v SNMP data only.v All Tivoli Netcool Performance Manager components that are deployed on a

single server.v Number of resources that are supported up to 20,000.v 3 SNMP Technology Packs based on MIB II, Cisco Device, and IPSLA.v 15-minute pollingv Number of DataView users who are limited to less than three.

AIX hardware requirements (POC)

The minimum system requirements for a proof of concept installation on AIX.v 2 x POWER7 (Quad Core) 3.0 GHz processor or 1 x POWER8 (Octo Core) 2.32

GHz processorv 16 GB Memoryv 1 x 146 GB HDD

To support:v SNMP data only.v All Tivoli Netcool Performance Manager components that are deployed on a

single server.v Number of resources that are supported up to 20,000.v 3 SNMP Technology Packs based on MIB-II, Cisco Device, and IPSLA.v 15-minute polling


v Number of DataView users who are limited to less than three.

Note: Extra features such as Tivoli Netcool/OMNIbus Web GUI and Mass DataExtraction (MDE) are not accounted for in this spec. They have extra memory andCPU impacts.

Linux hardware requirements (POC)

The minimum system requirements for a proof of concept installation on Linux.v 2 x Intel Xeon 5500/5600 series processors (quad-core), 2.4 GHz or greaterv 16 GB memoryv 1 x 300 GB HDD

To support:v SNMP data onlyv All Tivoli Netcool Performance Manager components that are deployed on a

single serverv Number of resources that are supported up to 20,000v 3 SNMP Technology Packs based on MIB-II, Cisco Device, and IPSLAv 15-minute pollingv Number of DataView users who are limited to less than three


A screen resolution of 1024 x 768 pixels or higher is recommended when you runthe deployer.

Supported operating systems and modulesThe supported operating systems, modules, and third-party applications for IBMTivoli Netcool Performance Manager, Version 1.4.3.

The following sections list the supported operating systems, modules, andthird-party applications for IBM Tivoli Netcool Performance Manager, Version1.4.3.

All subcomponents of the Tivoli Netcool Performance Manager - WirelineComponent can be installed on a mix of AIX, Linux, and Solaris operating systems;that is, the operating systems on which the DataChannel, DataView, DataLoad andDataMart subcomponents are installed do not have to be of the same type. Thesupported versions of AIX, Linux and Solaris operating systems are discussed inthis document.

For more information, see the Release notes - IBM Tivoli Netcool Performance Manager,Version 1.4.3, which contains the version numbers for each Tivoli NetcoolPerformance Manager module in Version 1.4.3.

Attention: DB2 is supported on Linux only. Whereas, Oracle is supported onSolaris, AIX, and Linux systems.


Important: DataView can be installed on the server which has Jazz for ServiceManagement 1.1.3.0 installed. Jazz for Service Management 1.1.3.0 is supportedonly on AIX and Linux. Thus, in Tivoli Netcool Performance Manager 1.4.3,DataView can be installed on AIX or Linux platform only.

Solaris 10 for SPARC platforms

Supported Solaris systems.

Operating systems and kernelSupported operating system and kernel version.

Solaris 10 update 10 (released in August 2011) or higher.

Note: Based on your Tivoli Netcool Performance Manager environment setup,ensure that the Global zone and its corresponding Virtual Machines (VM) has therecommended Solaris version.

Update level can be checked from /etc/release file.

Applying a kernel patch or a Solaris patch bundle is not the equivalent toinstalling the specific Solaris 10 "update 10" image.

Kernel Parameters

Solaris 10 uses the resource control facility to implement the System V IPC.However, Oracle recommends that you set both resource control and /etc/system/parameters. Operating system parameters that are not replaced by resourcecontrols continue to affect performance and security on Solaris 10 systems.Parameter Replaced by Resource Control Minimum Valuenoexec_user_stack NA (can be set in /etc/system only) 1semsys:seminfo_semmni project.max-sem-ids 100semsys:seminfo_semmsl process.max-sem-nsems 256shmsys:shminfo_shmmax project.max-shm-memory 4294967295shmsys:shminfo_shmmni project.max-shm-ids 100

Note: project.max-shm-memory represent the maximum shared memory availablefor a project, so the value for this parameter must be greater than sum of all SGAsize.

Refer to the following document for checking/setting kernel parameter values byusing resource control: Note 429191.1 Kernel setup for Solaris 10 using project files.v The 'umask' setting for the oracle user must be 022.v Hostname command must return the fully qualified hostname as either %

hostname or % hostname.domainname.

Solaris 10 requirements

Required packages and patches for the Solaris 10 system.

Tivoli Netcool Performance Manager requires at a minimum the End-Userdistribution of Solaris 10.


Required packages:

Required packages for the Solaris 10 system.

Before you install the Oracle server, ensure that the following Solaris packages areinstalled on your system:v SUNWarcv SUNWbtoolv SUNWcslv SUNWheav SUNWi15csv SUNWi1csv SUNWi1ofv SUNWlibCv SUNWlibmv SUNWlibmsv SUNWsprotv SUNWtoov SUNWxwfnt

To verify that the required Solaris packages are installed:1. Enter the following command at the shell prompt:

# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprotSUNWtoo SUNWuiu8

The following output confirms that the specified Solaris packages are installedcorrectly:

system SUNWarc Archive Librariessystem SUNWbtool CCS tools bundled with SunOSsystem SUNWhea SunOS Header Filessystem SUNWlibm Forte Developer Bundled libmsystem SUNWlibms Forte Developer Bundled shared libmsystem SUNWsprot Solaris Bundled toolssystem SUNWtoo Programming Tools

...

2. If these packages are not on your system, see the Solaris Installation Guide forinstructions on installing supplementary package software.

Required patches:

Required patches for the Solaris 10 system.

To determine the patch level on your system, enter the following command:uname -v

Note: All Tivoli Netcool Performance Manager modules are tested to run on anEnd-User distribution of Solaris 10.

The following list of minimum Solaris patches is required:v For all Installations:

– 120753-06: SunOS 5.10: Microtasking libraries (libmtsk) patch


– 139574-03: SunOS 5.10: file crle ldd stings elfdump patch– 141444-09– 141414-02

To determine whether an operating system patch is installed, enter a commandsimilar to the following:1. Enter the command:

/usr/sbin/patchadd -p | grep patch_number(without version number)

For example, to determine whether any version of the 120753-06 patch isinstalled, use the following command:/usr/sbin/patchadd -p | grep 120753

Solaris 10 virtualized containersIf you are using Solaris 10 virtualized containers, you must create containers with"whole root" partitions.

If you are using Solaris 10 virtualized containers, you must create containers with"whole root" partitions. Tivoli Netcool Performance Manager does not work incontainers with “sparse root” partitions.

Note: The Tivoli Netcool Performance Manager Self Monitoring Pack and SSMpacks do not report data correctly in virtualized environments, due tocompatibility issues of the underlying SSM agents in these configurations. TheMIB-II pack can also have difficulties discovering resources in virtualized serverenvironments.

DataMartDataMart requirements if you are using Solaris 10.

Configure the default language of Solaris to English.

IBM Java Runtime Environment (JRE) 1.7.

DataLoadDataLoad requirements if you are using Solaris 10.


DataChannelDataChannel requirements if you are using Solaris 10.


The DataChannel components require X libraries to be installed. The graphicaltools in DataChannel also require a running X server, which can be on a differenthost.

Technology packsTechnology pack requirements if you are using Solaris 10.

Installation of technology packs on Solaris 10 requires JRE 1.7 (32-bit). The correctversion is installed with the Topology Editor in the following default location:/opt/IBM/proviso/topologyEditor/jre/bin


AIX platforms

Supported AIX systems.

Tivoli Netcool Performance Manager can be installed and operated in a virtualizedAIX environment.

Note: Tivoli Netcool Performance Manager on AIX does not support connection toa Solaris-based Oracle database.

Note: The Tivoli Netcool Performance Manager Self Monitoring Pack and SSMpacks do not report data correctly in virtualized environments, due tocompatibility issues of the underlying SSM agents in these configurations. TheMIB-II pack can also have difficulties discovering resources in virtualized serverenvironments.

Operating system

Supported operating system and kernel version.

IBM Tivoli Netcool Performance Manager, Version 1.4.3 supports:v AIX 7.1 POWER7 TL 0 SP3 (7100-00-03), 64-bit kernelv AIX 7.1 POWER8 TL 03 SP3 (7100-03-03), 64-bit kernel

To verify your AIX release level:

As root, enter the following command at the shell prompt:# oslevel -r

This command returns a string that represents the maintenance level for your AIXsystem.

For AIX 7.1: If the operating system version is lower than AIX 7.1 POWER7Technology Level 0 plus SP 3, or POWER8 Technology Level 3 plus SP 3 thenupgrade your operating system to this or a later level. AIX maintenance packagesare available from the following website: http://www-933.ibm.com/support/fixcentral/

Required files and fixes

Files and fixes that are required by Oracle and Tivoli Netcool PerformanceManager for the AIX system.

AIX 7.1

The following operating system file sets are required for AIX 7.1:v bos.adt.basev bos.adt.libv bos.adt.libmv bos.perf.libperfstat


http://www-933.ibm.com/support/fixcentral/


v bos.perf.perfstatv bos.perf.proctoolsv xlC.aix61.rte:10.1.0.0 or laterv xlC.rte:10.1.0.0 or later

If you are using the minimum operating system TL level for AIX 7.1 listed above,then install all AIX 7L 7.1 Authorized Problem Analysis Reports (APARs) for AIX7.1 TL 0 SP1, and the following AIX fixes:v IZ87216v IZ87564v IZ89165v IZ97035

Note: See Oracle Metalink Note: 1264074.1 and Note: 1379753.1 for other AIX 7.1patches that might be required.

Determining installed file sets

To determine whether the required file sets are installed and committed, enter acommand similar to the following:# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.perfstat \bos.perf.libperfstat bos.perf.proctools

To determine the supported kernel mode, enter a command similar to thefollowing:# getconf KERNEL_BITMODE

Determining installed APAR fixes

To determine whether an APAR is installed, enter a command similar to thefollowing:# /usr/sbin/instfix -i -k "IZ42940 IZ49516 IZ52331 IZ41855 IZ52319"

If an APAR is not installed, then download it from the following website andinstall it: http://www-933.ibm.com/support/fixcentral/

Set resource limitsThe default user process limits are not adequate and must be reset.

On AIX systems, the default user process limits are not adequate for Tivoli NetcoolPerformance Manager. For detailed information on setting the correct user processlimits, see set Resource Limits in the Installing Tivoli Netcool Performance Manager -Wireline Component.

DataMart

DataMart requirements if you are using AIX.

Java Runtime Environment (JRE) 1.7 or higher (for the Database Informationmodule).



DataLoad

DataLoad requirements if you are using AIX.

No special requirements.

DataChannel

DataChannel requirements if you are using AIX.

The following DataChannel components require X libraries to be installed:v Bulk Collectorv CMEv DLDRv FTEv FED (also requires that an X Server is running)v LDRv The showVersion utility.

Technology packs

Technology pack requirements if you are using AIX.

Installation of technology packs on AIX 7.1 requires JRE 1.7 (32-bit). The correctversion is installed with the Topology Editor in the following default location:/opt/IBM/proviso/topologyEditor/jre/bin

Viewing the documentation on AIX systems

Viewing the documentation requires that you can run Adobe Acrobat Reader.

To run on AIX systems, Adobe Acrobat Reader requires GIMP Toolkit (GTK+)Version 2.2.2 or higher. You can download the toolkit from the following URL:

http://www-03.ibm.com/servers/aix/products/aixos/linux/download.html

In addition, you must install all the dependent packages for GTK+. You can installGTK+ and its dependent packages either before or after the installation of AcrobatReader.

At the time of publication, the latest version of GTK+ is gtk2-2.8.3-9, and thelatest versions of the dependent packages are as follows:v libpng-1.2.8-5

v libtiff-3.6.1-4

v libjpeg-6b-6

v gettext-0.10.40-6

v glib2-2.8.1-3

v atk-1.10.3-2


v freetype2-2.1.7-5

v xrender-0.8.4-7

v expat-1.95.7-4

v fontconfig-2.2.2-5

v xft-2.1.6-5

v cairo-1.0.2-6

v pango-1.10.0-2

v xcursor-1.0.2-3

v gtk2-2.8.3-9

To fulfill dependency requirements, you must install these Red Hat PackageManagers (RPMs) in the order specified.

Installing an RPM:1. To install an RPM, use the following syntax:

rpm -i rpm_filename

2. To see a list of the RPMs that are installed, enter the following command:rpm -qa

Acrobat Reader and LDAP:

By default, AIX systems do not have LDAP installed.

By default, AIX systems do not have LDAP installed. If the AIX system does nothave LDAP installed and you run Acrobat Reader, a warning message is displayed.Click OK to have Acrobat Reader proceed normally.

To remove the error message, delete or rename /opt/acrobat/Reader/rs6000aix/plug_ins/PPKLite.api, where /opt/acrobat is the installation path.

Linux platforms

Supported Linux Systems

IBM Tivoli Netcool Performance Manager, Version 1.4.3 can be installed andoperated in an environment that is using VMware partitions. Here are the detailsthe Linux environment prerequisites for Tivoli Netcool Performance Manager.

Operating systemSupported operating system and kernel versions.

Table 7. Tivoli Netcool Performance Manager supports the following Linux systems.

v Linux hosts running 64-bit Red HatEnterprise Linux Version 7.2 with Oracle12c for fresh install and upgrade options.

v Linux hosts running 64-bit Red HatEnterprise Linux Version 7.2 with DB2Version DB2 11.1.1.1 for fresh install andupgrade options.


Table 7. Tivoli Netcool Performance Manager supports the following Linuxsystems. (continued)

To check the version of your operatingsystem, enter:

# cat /etc/redhat-release

This command must return the outputsimilar to:

Red Hat Enterprise Linux Serverrelease 7.2

To check the version of your operatingsystem, enter:

# cat /etc/redhat-release

This command must return the outputsimilar to:

Red Hat Enterprise Linux Serverrelease 7.2

To verify the processor type, run thefollowing command:

uname -p

To verify the processor type, run thefollowing command:

uname -p

To verify the machine type, run thefollowing command:

uname -m

To verify the machine type, run thefollowing command:

uname -m

To verify the hardware platform, run thefollowing command:

uname -i

To verify the hardware platform, run thefollowing command:

uname -i

All results should contain the output:

x86_64

All results should contain the output:

x86_64

Database

Database requirements if you are using Linux.

It is recommended that you consult Metalink Note 880989.1, Requirements ForInstalling Oracle, which has a full list of Oracle requirements for RHEL. Oraclekeeps this list up to date.

Note: See Note 225710.1 for supported kernels and Note 265262.1 for "Things toknow about Linux." https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=265262.1

Required packages for Oracle on Red Hat Enterprise Linux 7.2

Required packages if you are using Linux.

The following is a list of packages for Red Hat Enterprise Linux 7.2 distribution:

adwaita-gtk2-theme.i686

atk.i686

binutils.x86_64

cairo.i686

compat-libcap1.x86_64


https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=880989.1




compat-libstdc++-33.i686

compat-libstdc++-33.x86_64

elfutils-libelf-devel.x86_64

gcc.x86_64

gcc-c++.x86_64

glibc.i686

glibc.x86_64

glibc-common.x86_64

glibc-devel.i686

glibc-devel.x86_64

glibc-headers.x86_64

gtk2.i686

ksh.x86_64

libaio.i686

libaio.x86_64

libaio-devel.i686

libaio-devel.x86_64

libcanberra.i686

libcanberra-devel.*

libgcc.i686

libgcc.x86_64

libstdc++.i686

libstdc++.x86_64

libstdc++-devel.i686

libstdc++-devel.x86_64

libX11.i686

libX11.x86_64

libXau.i686

libXau.x86_64

libxcb.i686

libxcb.x86_64

libXext.i686

libXext.x86_64

libXi.i686

libXi.x86_64

libXp.i686

libXp.x86_64

libXpm.x86_64

libXtst.i686

libXtst.x86_64

make.x86_64

motif.i686


motif.x86_64

openssl.x86_64

openssl098e.i686

PackageKit-gtk3-module.i686

pam.i686

pam.x86_64

sysstat.x86_64

unixODBC.x86_64

unixODBC-devel.x86_64

vsftpd.x86_64

xterm.x86_64

zlib-devel.i686

zlib-devel.x86_64

Note: These are minimum required versions. Also, for some architectures both ofthe i686 and x86_64 package versions must be verified.

For example, both the i686 and the x86_64 architectures for glibc-2.5-24 must beinstalled.

Required packages for IBM DB2 on Red Hat Enterprise Linux 7.2

Required packages if you are using Linux 7.2.

The following is a list of packages for Red Hat Enterprise Linux 7.2 distribution:

adwaita-gtk2-theme.i686

binutils.x86_64

compat-libstdc++-33.i686

compat-libstdc++-33.x86_64

elfutils-libelf.x86_64

elfutils-libelf-devel.x86_64

gcc.x86_64

gcc-c++.x86_64

glibc.i686

glibc.x86_64

glibc-common.x86_64

glibc-devel.i686

glibc-devel.x86_64

glibc-headers.x86_64

ksh.x86_64

libaio.i686

libaio.x86_64

libcanberra.i686


libcanberra-devel.*

libgcc.i686

libgcc.x86_64

libstdc++.i686

libstdc++-devel.x86_64

libXp.i686

libXp.x86_64

libXpm.x86_64

make.x86_64

motif.i686

motif.x86_64

nfs-utils.x86_64

openssl.x86_64

openssl098e.i686

PackageKit-gtk3-module.i686

pam.x86_64

vsftpd.x86_64

All required packages must be installed and configured before you continue withthe DB2 database system setup. For general Linux information, see your Linuxdistribution documentation.

Note: These are minimum required versions. Also, for some architectures both ofthe i686 and x86_64 package versions must be verified. For example, both the i686and the x86_64 architectures for glibc-2.5-24 must be installed.

Run the db2prereqcheck command to check if your system meets the prerequisitesfor the installation of a specific version of DB2 for Linux, UNIX, and Windows. Forexample, run the following commands:./db2prereqcheck -v 11.1.0 -s

DBT3533I The db2prereqcheck utility has confirmed that all installation prerequisiteswere met for DB2 database "server " "". Version: "11.1.0"DBT3533I The db2prereqcheck utility has confirmed that all installation prerequisiteswere met for DB2 database "server " "with DB2 pureScale feature ". Version: "11.1.0"

DataMart

DataMart requirements if you are using Linux.

Java Runtime Environment (JRE) 1.7 or higher (for the Database Informationmodule).

DataLoad

DataLoad requirements if you are using Linux.



DataChannel

DataChannel requirements if you are using Linux.


Required user namesThere are two user names that must be created when installing Tivoli NetcoolPerformance Manager.

Two specific user names are required on any server hosting Tivoli NetcoolPerformance Manager components, they are:

pvuserA dedicated Tivoli Netcool Performance Manager Unix user.

oracle A dedicated Oracle user.

db2 A dedicated DB2 user.

pvuserThe pvuser user name.

The Tivoli Netcool Performance Manager UNIX user pvuser must be added to eachserver that is hosting a Tivoli Netcool Performance Manager component. The TivoliNetcool Performance Manager UNIX user, which is referred to as pvuserthroughout the documentation, can be named by using any string as required byyour organizations naming standards.

oracle

The oracle user name.

The Oracle user is added to each server that is hosting a Tivoli NetcoolPerformance Manager component. This user is added during Oracle client orserver installation. The default username that is used is oracle.

However, this Oracle username can be named by using any string as required byyour organizations naming standards.

If you are installing Oracle by using a non-default username, then the non-defaultuser must be created with Korn shell as its login shell.# useradd -g <group> -G <group_2> -m -d <home_dir>/<username> -k /etc/skel -s /bin/ksh <username>

Where:v <group> is the name of the primary group to be assigned to the new user.v <group_2> is the name of the subsequent group to be assigned to the new user.v <home_dir> is the home directory for the new user.v <username> is the name of the new user, which can be set to any string.


For example:useradd -g dba -G oinstall -m -d /export/home/oracle2 -k /etc/skel -s /bin/ksh oracle2

Note: If you choose a non-default Oracle username, you must use the same nameacross all instances of Oracle Client and Server throughout your Tivoli NetcoolPerformance Manager system.

db2

The db2 user name.

The DB2 user db2 is added to each server hosting a Tivoli Netcool PerformanceManager component. The default username used is db2; however, this DB2username can be named using any string as required by your organizationsnaming standards.

Note: If you want to select a non-default DB2 username, you must use the samename across all instances of DB2 client and server throughout your Tivoli NetcoolPerformance Manager system.

Ancillary software requirementsExtra and third-party software requirements.

Extra software packages required by Tivoli Netcool Performance Manager.

FTP supportTivoli Netcool Performance Manager requires FTP support.

The FTP (File Transfer Protocol) version that is used to transfer files between TivoliNetcool Performance Manager components is delivered with Solaris 10.

AIX also uses FTP to transfer files between Tivoli Netcool Performance Managercomponents.

Tivoli Netcool Performance Manager supports the following file transport protocolsbetween Tivoli Netcool Performance Manager components and third-partyequipment (for example, EMS):v FTP Solaris 10v Microsoft Internet Information Services (IIS) FTP server

OpenSSH and SFTPTivoli Netcool Performance Manager requires OpenSSH and SFTP support.

Tivoli Netcool Performance Manager supports encrypted Secure File Transfer(SFTP) and FTP to move data files from DataLoad to DataChannel, or fromDataChannel Remote to the DataChannel Loader.

Tivoli Netcool Performance Manager SFTP is compatible only with OpenSSHserver and client version 3.1p 1 and above. OpenSSH is freely downloadable anddistributable (http://www.openssh.org). OpenSSH is supported on Solaris, AIX,


http://www.openssh.org

and Linux. Other SSH versions such as F-Secure, the SSH bundled in Solaris 10and the SSH bundled with AIX is not compatible.

If you use the SFTP capability, you must obtain, install, generate keys for, maintain,and support OpenSSH and any packages that are required by OpenSSH.

See Tivoli Netcool Performance Manager Technical Note: DataChannel Secure File TransferInstallation for more information about installing and configuring OpenSSH.

AIX requirements

AIX requirements in order to use OpenSSH and SFTP.

The following table lists additional prerequisites that must be installed on an AIXsystem, and where these packages can be found:

Table 8. Additional Prerequisites

Package Location

openssl-0.9.7g-1.aix5.1.ppc.rpm https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=aixtbx

openssh-4.1p1_53.tar.Z https://sourceforge.net/projects/openssh-aix/

bos.adt.libm AIX installation CD.

Solaris requirements

Solaris requirements in order to use OpenSSH and SFTP.

The following are additional prerequisites that must be installed on an Solarissystems:v openssh- SSH client (openssh-4.5p1-sol-sparc-local.gz or higher).v zlib - zlib compression and decompression library (zlib-1.2.3-sol9-sparc-

local.gz or higher).

Linux requirements

Linux requirements in order to use OpenSSH and SFTP.

OpenSSH is required for VSFTP to work with Tivoli Netcool Performance Manager.OpenSSH is installed by default on any RHEL system.

By default, FTP is not enabled on Linux systems. You must enable FTP on yourLinux host to carry out the installation of Tivoli Netcool Performance Manager.

To enable FTP on your Linux host, run the following command as root:

systemctl start vsftpd.service


https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=aixtbx

https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=aixtbx

https://sourceforge.net/projects/openssh-aix/

https://sourceforge.net/projects/openssh-aix/

File compressionFile compression support.

Archives that are delivered as part of the IBM Tivoli Netcool Performance Managerdistribution are created by using GNU TAR. This program must be used for thedecompression of archives.

DataView load balancingLoad balancing support.

IBM Tivoli Netcool Performance Manager supports the use of an external loadbalancer to optimize the use of available DataView instances.

The load balancer must support the following basic features:v Basic IP-based load balancingv Sticky sessions based on incoming IPv Up/down status based on checking for a listening port

Link to CSS Basic Configuration Guide: http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v7.20/configuration/basic/guide/bsccfggd.html

DatabasesTivoli Netcool Performance Manager 1.4.3 supports both the databases, Oracle andIBM DB2.

Oracle support

Oracle server support and hidden Oracle parameters.

License recommendations

When purchasing a license from Oracle, IBM recommends a Processor licenserather than a Named User Plus license.

Oracle defines a Named User in such a way that it includes not only actual humanusers, but also non-human-operated devices. In other words, you would require aNamed User Plus license for every resource that Tivoli Netcool PerformanceManager polls, which would be very expensive.

http://www.oracle.com .

Oracle server support

Oracle 12c Enterprise Edition for Solaris (SPARC) and Linux AIX are 64-bitonly. Oracle 12c Enterprise Edition must include the partitioning option.The database no longer provides 32-bit libraries, therefore you must installthe Oracle client on every host of the Tivoli Netcool Performance Manager.

Note: Tivoli Netcool Performance Manager must be installed and run as astandalone database. It must not be placed on a server that already has adatabase as the installation program will likely to interfere. The co-hosting


http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v7.20/configuration/basic/guide/bsccfggd.html



http://www.oracle.com

of Tivoli Netcool Performance Manager also affects performance inunknown ways. If a co-host is required then the Customer should seek outProfessional Services for support.

Hidden Oracle parameters

This section lists all of the Oracle '_', or hidden parameters, used by TivoliNetcool Performance Manager:v _partition_view_enabled = TRUEv _unnest_subquery = FALSEv _gby_hash_aggregation_enabled = FALSE

DB2 servers and IBM Data Server clients

DB2 server and client support.

DB2 server support

IBM DB2 Advanced Workgroup Server Edition 11.1.1.1, Linux 64-bit only.

Note: Tivoli Netcool Performance Manager must be installed and run as astandalone database. It must not be placed on a server that already has adatabase as the installation program will likely to interfere. The co-hostingof Tivoli Netcool Performance Manager also affects performance inunknown ways. If a co-host is required then the Customer must seek IBMProfessional Services for support.

DB2 client support

IBM Data Server Client 11.1.1.1, Linux 64-bit Linux 64-bit only.

Note: Tivoli Netcool Performance Manager must be installed and run as astandalone database. It must not be placed on a server that already has adatabase as the installation program will likely to interfere. The co-hostingof Tivoli Netcool Performance Manager also affects performance inunknown ways. If a co-host is required then the Customer must seek IBMProfessional Services for support.

For more information about DB2 servers, see http://www.ibm.com/software/data/db2/.

Jazz for Service ManagementDashboard Application Services Hub is replacing the Tivoli Integrated Portal.

Jazz for Service Management contains the following components:v Dashboard Application Services Hubv Reporting Services environmentv Tivoli Common Reporting

Note: The supported Tivoli Common Reporting is 3.1.3.0.Related information:

New features in Jazz for Service Management Version 1.1.3.0


http://www.ibm.com/software/data/db2/

http://www.ibm.com/software/data/db2/

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/psc_new_113_mod.html

Java Runtime Environment (JRE)Required Java support.

Java Runtime Environment (JRE) 1.7 (32-bit) is required for all servers hostingTivoli Netcool Performance Manager components.

Web browsers and settings for DataView reportsSupported browsers.

The following browsers are required to support the web client and provide accessto DataView reports:

Important: No other browser types are supported.

Table 9. Windows Clients

Windows 7

v Microsoft Internet Explorer 11.0

v Mozilla Firefox ESR 38 and 45

v Google Chrome (most recent version)

Note: When you are using Windows Internet Explorer, IBM recommends that youhave available at least 1 GB of memory

Table 10. UNIX Clients

AIX RHEL Solaris 10

Mozilla Firefox 3.6 Mozilla Firefox ESR 38 and45

Mozilla Firefox ESR 38 and45

The following are required browser settings:v Enable JavaScriptv Enable cookies

Browser requirements for the LaunchpadWeb browser requirements for the Launchpad.

The new Launchpad has been tested on the following browsers:

v Mozilla Firefox ESR 38 and 45

v Mozilla Firefox 3.6

v Red Hat Enterprise Linux (RHEL) 7.2– Mozilla Firefox ESR 38 and 45

For information about downloading and installing these browsers, see thefollowing web sites:


v http://www.mozilla.org/v http://www-03.ibm.com/systems/p/os/aix/browsers/index.html

Note: You must be a registered user to use this site.


A screen resolution of 1152 x 864 pixels or higher is recommended for the displayof DataView reports. Some reports may experience rendering issues at lowerresolutions.

Report Studio - CognosReport Studio support.

Report Studio is only supported by Microsoft Internet Explorer.

X EmulationRemote desktop support.

For DataMart GUI access, Tivoli Netcool Performance Manager supports thefollowing:v Native X Terminalsv Exceed V 6.x

The following libraries are required for Exceed to work with Eclipse:v libgtk 2.10.1v libgib 2.12.1v libfreetype 2.1.10v libatk 1.12.1v libcairo 1.2.6v libxft 2.1.6v libpango 1.14.0v Real VNC server 4.0

IBM Tivoli Netcool/OMNIbus Web GUI integrationIBM Tivoli Netcool/OMNIbus Web GUI, Version 8.1 support.

The IBM Tivoli Netcool/OMNIbus Web GUI Integration Guide for Wireline describeshow to integrate IBM Tivoli Netcool/OMNIbus Web GUI and Jazz for ServiceManagement 1.1.3.0 with the wireline component of Tivoli Netcool PerformanceManager.

Tivoli Netcool Performance Manager 1.4.3 supports:

Jazz for Service Management 1.1.3.0 and IBM Tivoli Netcool/OMNIbus Web GUI8.1.

The web browsers supported by IBM Tivoli Netcool/OMNIbus Web GUI andTivoli Netcool Performance Manager are listed in the following table.


http://www.mozilla.org/

http://www-03.ibm.com/systems/p/os/aix/browsers/index.html

Table 11. Web clients browsers supported by IBM Tivoli Netcool/OMNIbus Web GUI

Browser Version Operating system

Internet Explorer 11.0 Windows 7

Mozilla Firefox ESR 3845

Windows 7

Red Hat

Enterprise Linux (RHEL) 7.2

Google Chrome Most recent version

Windows 7

Red Hat

Enterprise Linux (RHEL) 7.2

Note: When you are using Internet Explorer, IBM recommends that you have atleast 1 GB of memory available.

Microsoft Office VersionMicrosoft Office support.

The Tivoli Netcool Performance Manager DataView Scheduled Report optiongenerates files compatible with Microsoft Office Word 2002 or higher.


Chapter 3. Installing and configuring the prerequisite software

Installing and configuring the prerequisite software required by Tivoli NetcoolPerformance Manager.

OverviewBefore you begin the Tivoli Netcool Performance Manager installation, you mustinstall the prerequisite software that is listed in the Requirements chapter.

You need the following software for database of your choice.

Oracle

Software required if you are using Oracle as your database.

Oracle serverYou must install the 64-bit Oracle server. To use Oracle with Tivoli NetcoolPerformance Manager, you must install Oracle as described in this chapter- do not use a separate Oracle installation method provided by OracleCorporation.

Oracle clientYou must install the 32-bit Oracle client. You must have at least onecomputer where you install:v Tivoli Netcool Performance Managerv 64-bit Oracle serverv 32-bit Oracle client

This computer is the Oracle Database server. You must install the Oracleserver at /opt/oracle/product/12.1.0 and the Oracle client at/opt/oracle/product/12.1.0-client32.

When you complete the steps that are given, the Oracle server and client areinstalled and running, with table spaces sized and ready to accept the installationof a Tivoli Netcool Performance Manager DataMart database. You cancommunicate with Oracle by using the SQLPlus command-line utility.

Use IBM-provided installation scripts to install and configure the Oracle databasefrom the Oracle distribution. For use with Tivoli Netcool Performance Manager,you must install Oracle as described. Do not use a separate Oracle installationmethod that is provided by Oracle Corporation. You must obtain the official Oracledistribution from your delivery site (after purchase of an Oracle license). See theRequirements for recommendations when you purchase a license from Oracle.

Note: The Tivoli Netcool Performance Manager script that is used to install Oracleis platform-independent and can be used to install on Solaris, AIX, or Linux,regardless of the operating system distribution media.


OpenSSHYou must install and configure OpenSSH before you install Tivoli NetcoolPerformance Manager. For details, see Appendix E, “Secure file transferinstallation,” on page 255. Linux systems require the installation of VSFTP(Very Secure FTP).

Web browserThe launchpad requires a web browser. IBM suggests you to use Mozillawith the launchpad. For the complete list of supported browsers, see theRequirements.

Java Java is used by DataMart, DataLoad, and the technology packs. You mustensure that you are using the IBM JRE and not the RHEL JRE. The IBMJRE is supplied with the Topology Editor. To ensure that you are using theright JRE you can either: Set the JRE path to conform the one that is usedby the Topology Editor, you can do it by using the following commands(by using the default location for the primary deployer):

PATH=/opt/IBM/proviso/topologyEditor/jre/bin:$PATHexport $PATH

For a remote server that does not host the primary deployer, you mustdownload and install the required JRE, and set the correct JRE path. SeeRequirements for JRE download details.

Note: See Requirements for the complete list of prerequisite software and theirsupported versions.

IBM DB2

Software required if you are using DB2 as your database.

IBM DB2 Advanced Workgroup Server Edition 11.1.1.1, Linux 64-bitYou must install DB2 Server software on a system where you plan toinstall a Tivoli Netcool Performance Manager database component. Formore information about installing DB2 11.1.1.1 Server, seehttp://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/c0060076.html

IBM Data Server Client 11.1.1.1, Linux 64-bit, Linux 64-bitYou must install DB2 client software on each system where you plan toinstall a Tivoli Netcool Performance Manager component, except for thesystem where you installed the DB2 server.

When you complete the steps here, the DB2 server and client is installedand running, with table spaces sized and ready to accept the installation ofa Tivoli Netcool Performance Manager DataMart database. You cancommunicate with DB2 by using the clpplus command-line utility.

Other software:

OpenSSHYou must install and configure OpenSSH before you install Tivoli NetcoolPerformance Manager. For details, see Appendix E, “Secure file transferinstallation,” on page 255. Linux systems require the installation of VSFTP(Very Secure FTP).

Web browserThe launchpad requires a web browser. IBM suggests you to use Mozilla




with the launchpad. For the complete list of supported browsers, see theChapter 2, “Requirements,” on page 33.

Java Java is used by DataMart, DataLoad, and the technology packs. You mustensure that you are using the IBM JRE and not the Red Hat EnterpriseLinux JRE. The IBM JRE is supplied with the Topology Editor. To ensurethat you are using the right JRE you can either: Set the JRE path toconform the one that is used by the Topology Editor, you can do it byusing the following commands (by using the default location for theprimary deployer):

PATH=/opt/IBM/proviso/topologyEditor/jre/bin:$PATHexport $PATH

For a remote server that does not host the primary deployer, you mustdownload and install the required JRE, and set the correct JRE path. Seethe Chapter 2, “Requirements,” on page 33 for JRE download details.

Note: See the Chapter 2, “Requirements,” on page 33 for the complete list ofprerequisite software and their supported versions.

Supported platformsThe platforms supported by Tivoli Netcool Performance Manager.

Refer to the following table for platform requirement information.

Tivoli Netcool Performance ManagerComponent Required Operating Systems

All Tivoli Netcool Performance ManagerComponents:

v Database

v DataView

v DataChannel

v DataLoad

v DataMart

v Solaris 10 Update 10 (released in August,2011)

v AIX 7.1 POWER7 TL 0 SP3 ("7100-00-03")64-bit kernel

AIX 7.1 TL 03 SP3 ("7100-03-03") 64-bitkernel

v Red Hat Enterprise Linux Server release7.2 for fresh installation and upgradeoption

Pre-Installation setup tasksBefore installing the prerequisite software, perform the tasks outlined in thissection.

Setting up a remote X Window displaySetting Up a Remote X Window Display.

About this task

For most installations, it does not matter whether you use a Telnet, rlogin, Xterm,or Terminal window to get to a shell prompt.

Some installation steps must be performed from a window that supports the XWindow server protocols. This means that the steps described in later chaptersmust be run from an Xterm window on a remote system or from a terminalwindow on the target system's graphical display.

Chapter 3. Installing and configuring the prerequisite software 65

Note: See the Chapter 2, “Requirements,” on page 33 document for the list ofsupported X emulators.

Specifying the DISPLAY environment variableIf you use an X Window System shell window such as Xterm, you must set theDISPLAY environment variable to point to the IP address and screen number ofthe system you are using.

About this task

Command sequences in this manual do not remind you at every stage to set thisvariable.

If you use the su command to become different users, be especially vigilant to setDISPLAY before running X Window System-compliant programs.

Procedure

In general, set DISPLAY as follows:$ DISPLAY=Host_IP_Address:0.0 $ export DISPLAY

To make sure the DISPLAY environment variable is set, use the echo command:$ echo $DISPLAY

Disabling access control to the displayIf you encounter error messages when trying to run X Window System-basedprograms, you might need to temporarily disable X Window System access controlso an installation step can proceed.

About this task

To disable access control:

Procedure1. Set the DISPLAY environment variable.2. Enter the following command when logged in as root:

# /usr/openwin/bin/xhost +

Note: Disabling access control is what enables access to the current machinefrom X clients on other machines.

Changing the ethernet characteristicsBefore installing Tivoli Netcool Performance Manager, you must force both theethernet adapter and the port on the switch to 100 full duplex mode -autonegotiate settings are not enough.

AIX systemsChanging ethernet characteristics on AIX.

About this task

To change the setting to full duplex:

Note: If the AIX node is a virtual partition, you must perform these steps on thevirtual I/O server (including the reboot).


Procedure1. Using the System Management Interface Tool (SMIT), navigate to Devices >

Communication > Ethernet Adapter > Adapter > Change/ShowCharacteristics of an Ethernet Adapter.

2. Select your ethernet adapter (the default is ent0).3. Change the setting Apply change to DATABASE only to yes.4. Set the port on the switch or router that the AIX node is plugged into to

100_Full_Duplex.5. Reboot your system.

Solaris systemsThis section describes how to set a network interface card (NIC) and a BGEnetwork driver to full duplex mode.

NIC:

Change the NIC to full duplex mode on Solaris systems

About this task

To change the NIC to full duplex mode:

Procedure

1. Determine which type of adapter you have by running the following command:ifconfig -a

2. To determine the current settings of the NIC, run the command ndd -get/dev/hme with one of the following parameters:

Command Parameter Description

link_status Determines whether the link is up

v 1 - Up

v 0 - Down

link_speed Determines the link speed

v 0 - 10Mb/sec

v 1 - 100Mb/sec

link_mode Determines the duplex mode

v 0 - Half duplex

v 1 - Full duplex

adv_autoneg_cap Determines whether auto negotiation is on

v 0 - Off

v 1 - On

For example:ndd -get /dev/hme link_status

In these commands, /dev/hme is your NIC; you might need to substitute yourown /dev/xxx.

3. To set your NIC to 100Mb/s with full duplex for the current session, run thefollowing commands:

ndd -set /dev/hme adv_100hdx_cap 0ndd -set /dev/hme adv_100fdx_cap 1ndd -set /dev/hme adv_autoneg_cap 0


However, these commands change the NIC settings for the current session only.If you reboot, the settings will be lost. To make the settings permanent, edit the/etc/system file and add the following entries:

set hme:hme_adv_autoneg_cap=0set hme:hme_adv_100hdx_cap=0set hme:hme_adv_100fdx_cap=1

4. Verify that your NIC is functioning as required by rerunning the commandslisted in Step 2.

BGE network driver:

Change a BGE network driver to full duplex mode.

About this task

To change a BGE network driver to full duplex mode.

Procedure

1. To determine the link speed and current duplex setting, run the followingcommand:

% kstat bge:0 | egrep ’speed|duplex’

The output is similar to the following:duplex fullifspeed 100000000link_duplex 2link_speed 100

The parameters are as follows:

Parameter Description

link_duplex Determines the duplex setting

v 1 - Half-duplex

v 2 - Full duplex

link_speed Determines the link speed

v 10 - 10 Mb/sec

v 100 - 100 Mb/sec

v 1000 - 1 Gb/sec

2. Create a file namedbge.conf in the /platform/uname -i/kernel/drv directory(for example, /platform/SUNW,Sun-Fire-V210/kernel/drv/bge.conf).

3. Add the following lines to the file:speed=100;full duplex=1;

4. Reboot the machine to have your changes take effect.

Linux systemsEnabling 100 full duplex mode on Linux systems.

About this task

Use your primary network interface to enable 100 full duplex mode.

To check if full duplex is enabled:


Procedure1. Enter the following command:

# dmesg | grep -i duplex

This should result in output similar to the following:eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

2. Confirm the output contains the words:Full Duplex

If this is not contained within the output, you must enable full duplex mode.The example output resulting from the command executed in step 1:eth0: link up, 100Mbps, full-duplex, lpa 0x45E1indicate that the primary network interface is eth0.The actions specified in the following process presume that your primarynetwork interface is eth0.

Enabling full duplex mode on Linux:

To enable full duplex mode.

Procedure

1. Open the file ifcfg-eth0, which is contained in:/etc/sysconfig/network-scripts/

2. Add the ETHTOOL_OPTS setting by adding the following text:ETHTOOL_OPTS="speed 100 duplex full autoneg off"

Note: The ETHTOOL_OPTS speed setting can be set to either 100 or 1000depending on speed of connection available 100Mbit/s or 1000Mbit/s(1Gbit/s).

Adding the pvuser login namepvuser is the default name used within this document to describe the requiredTivoli Netcool Performance Manager UNIX user.

The required user can be given any name of your choosing. However, for theremainder of this document this user is referred to as "pvuser".

Decide in advance where to place the home directory of the pvuser loginusername. Use a standard home directory mounted on /home or /export/home, asavailable.

Note: Do not place the home directory in the same location as the Tivoli NetcoolPerformance Manager program files. That is, do not use /opt/proviso or any otherdirectory in /opt for the home directory.

Add the pvuser login name to every system on which you install a Tivoli NetcoolPerformance Manager component, including the system hosting the Oracle or DB2server.

Adding pvuser to a Standalone ComputerUse the steps in this section to add the pvuser login name to each standalonecomputer.


About this task

These steps add the login name only to the local system files on each computer(that is, to the local /etc/passwd and /etc/shadow files). If your network uses anetwork-wide database of login names such as Yellow Pages or NetworkInformation Services (NIS or NIS+), see “Adding pvuser on an NIS-managednetwork” on page 71.

To add pvuser:

Procedure1. Log in as root.2. Set and export the DISPLAY environment variable. (see“Setting up a remote X

Window display” on page 65.)3. If one does not already exist, create a group to which you can add pvuser. You

can create a group with the name of your choice using the following command:groupadd <group>

where:v <group> is the name of the new group, for example, staff.

4. At a shell prompt, run the following command:# useradd -g <group> -m -d <home_dir>/<username> -k /etc/skel -s /bin/ksh <username>

Where:v <group> is the name of the group to which you want to add pvuser.v <home_dir> is the home directory for the new user, for example,

/export/home/ can be used as the example home directory.v <username> is the name of the new user. This can be set to any string.

Note: For the remainder of this information this user will be referred to aspvuser.

5. Set a password for pvuser:# passwd pvuser

The system prompts you to specify a new password twice. The default pvuserpassword assumed by the Tivoli Netcool Performance Manager installer is PV.This can be set to a password conforming to your organization's standards.

6. Test logging in as pvuser, either by logging out and back in, or with the sucommand, such as:# su - pvuser

Confirm that you are logged in as pvuser with the id command:$ id

These instructions create a pvuser login name with the following attributes:

Attribute Value

login name pvuser

member of group staff

home directory /export/home/pvuser

login shell Korn shell (/bin/ksh)


Attribute Value

copy skeleton setup files (.profile, and so on)from this directory

/etc/skel

Note: The pvuser account must have write access to the /tmp directory.

Multiple computer considerationsIf you are creating the pvuser login name on more than one computer in yournetwork, avoid confusion by specifying the same user ID number for each pvuserlogin name on each computer.

When you create the first pvuser login name, log in as pvuser and run the idcommand. The system responds with the user name and user ID number (and thegroup name and group ID number). For example:

$ id uid=1001(pvuser) gid=10(staff)

When you create the pvuser login name on the next computer, add the -u option tothe useradd command to specify the same user ID number:

# useradd -g <group> -m -d <home_dir>/pvuser -k /etc/skel -s /bin/ksh -u 1001 pvuser

Where:v <group> is the name of the group to which you want to add pvuser.v <home_dir> is the home directory for the new user, for example, /export/home/

can be used as the example home directory.v <username> is the name of the new user. This can be set to any string.

Adding pvuser on an NIS-managed networkAdding pvuser on an NIS-Managed Network.

If your site's network uses NIS or NIS+ to manage a distributed set of login names,see your network administrator to determine whether pvuser must be added toeach Tivoli Netcool Performance Manager computer's local setup files, or to thenetwork login name database.

Setting the resource limitsOn AIX systems, it is possible that the default user process limits are not adequatefor Tivoli Netcool Performance Manager.

About this task

If the default user process limits are not adequate for Tivoli Netcool PerformanceManager, do the following.

To set the user process limits on AIX systems:

Procedure1. Log in as root.2. Change your working directory to /etc/security by entering the following

command:# cd /etc/security

3. Make a backup copy of the limits file by entering the following command:# cp limits limits.ORIG


4. Using a text editor, open the limits file and set the following values:default: fsize = -1 core = -1 cpu = -1 data = -1 rss = 65536 stack = 65536 nofiles = 2000totalProcesses = 800

Note: Apply these settings to every AIX system running a Tivoli NetcoolPerformance Manager program: the database server, DataLoad servers,DataChannel servers, and DataMart servers.

5. Write and quit the file.6. After modifying the settings, log off every Tivoli Netcool Performance Manager

user and then log in again for the changes to take effect.

Setting the shell limits (Linux only)

Set the shell limits for the oracle user.

About this task

On Linux systems, it is possible that the default user process limits are notadequate for Tivoli Netcool Performance Manager. To improve the performance ofthe software, you must increase the shell limits for the Oracle user.

Procedure

Add the following settings to the /etc/security/limits.conf file:<Oracle username> soft nproc 2047<Oracle username> hard nproc 16384<Oracle username> soft nofile 1024<Oracle username> hard nofile 65536<Oracle username> soft stack 10240

Note: Use tabs between the fields instead of spaces for the settings to workeffectively.

Important: The default Oracle username is oracle. If you are installing Oracle byusing a non-default Oracle username, use the non-default username in the/etc/security/limits.conf.

Setting the shell limits (Solaris only)

Set the shell limits for the oracle user.

About this task

On Solaris systems, it is possible that the default user process limits are notadequate for Tivoli Netcool Performance Manager. To improve the performance ofthe software, you must increase the shell limits for the oracle user.

Procedure1. Run the following command:

# plimit –n soft_limit,hard_limit $$# plimit -n 2048,65536 $$

2. To verify that the limits was updated correctly, run the following command:# prctl -n process.max-file-descriptor $$


Set the system parameters

Before you install the Oracle server, you must set the Solaris shared memory andsemaphore parameters.

About this task

If using Solaris 10 containers, typically the variable in /etc/system is set only inthe root container, and project variables are set for each container. Refer to Solaris10 container documentation for further information.

When you install Tivoli Netcool Performance Manager, you specify the size of thedeployment - small, medium, or large. The value you select affects the OraclePROCESSES parameter. You must set the appropriate kernel parameter level inorder for the deployment to work properly.

Note: These entries are only for the system running the Oracle server, not theOracle client.

To set Solaris system parameters:

Procedure1. Set the NOEXEC_USER_STACK parameter in the system file:

a. Log in as root.b. Change to the /etc directory:

# cd /etc

c. Create a backup of the file named system, and open the file with a texteditor.

d. Set the parameter NOEXEC_USER_STACK to 1, by adding the following line atthe bottom of the file:set NOEXEC_USER_STACK=1

e. Save and exit the system file.2. Set resource controls correctly.

The parameters affected by the deployment size are project.max-sem-ids,process.max-sem-nsems, project.max-shm-memory, and project.max-shm-ids.These parameters define the maximum size of a semaphore set and themaximum number of semaphores in the system.a. In Solaris 10, kernel parameters are replaced by resource controls. ), section

2.6: Configuring Kernel Parameters. See also Oracle Metalink ID 169706.1,Oracle Database on Unix AIX, HP-UX, Linux, Mac OS X, Solaris, Tru64 UnixOperating Systems Installation and Configuration Requirements QuickReference (8.0.5 to 11.2), which lists Solaris requirements.

b. Oracle recommends the following values, noting that they are guidelinesand should be tuned for production database systems. If you use a customconfiguration, you must change the values of the parameters to theappropriate level.

Resource Control Recommended Value

project.max-sem-ids 100

process.max-sem-nsems 256


Resource Control Recommended Value

project.max-shm-memory 429496725

project.max-shm-ids 100

c. Log in as the Oracle user (for example, oracle).d. To find the current kernel parameter settings, check the project id, and then

check the resource control settings for that project id:

$ id -puid=4074(oracle) gid=9999(dba) projid=3(default)$ prctl -n project.max-shm-memory -i project 3project: 3: defaultNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-memory

privileged 1.95GB - deny -system 16.0EB max deny -

$ prctl -n project.max-sem-ids -i project 3project: 1: user.rootNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-sem-ids

privileged 128 - deny -system 16.8M max deny -

$ prctl -n project.max-shm-ids -i project 3project: 3: defaultNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-ids


$ prctl -n process.max-sem-nsems $$process: 12134: bashNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTprocess.max-sem-nsems


e. To change values, check the Solaris documentation for complete informationon projects. Here is one example, which sets the value ofproject.max-shm-memory to 4GB. Log in as root and add a project, attachedto the dba group (assuming the oracle user is part of the dba group), andset the value:

# projadd -p 100 -G dba -c "Oracle Project" \-K "project.max-shm-memory=(privileged,4G,deny)" group.dba

f. Check by logging back in as oracle, checking with id -p that the projid isnow the new project number 100, and run prctl again to check that themax-shm-memory value has been updated.

$ id -puid=4074(oracle) gid=9999(dba) projid=100(group.dba)bash-3.00$ prctl -n project.max-shm-memory -i project 100

project: 100: group.dbaNAME PRIVILEGE VALUE FLAG ACTION RECIPIENT

project.max-shm-memoryprivileged 4.00GB - deny -system 16.0EB max deny -

3. Reboot your system before continuing to the next step.


Enable FTP on Linux systems

By default, FTP is not enabled on Linux systems.

About this task

To enable FTP on your Linux host:

Procedure1. Log in as root:2. Run the following command:

# systemctl start vsftpd.service

Disable SELinux (Linux only)Tivoli Netcool Performance Manager is not installed properly if the SELinuxsecurity policy is set to "enforcing".

About this task

To change the SELinux security policy is set to "enforcing", you must:

Procedure1. Log in as root.2. Open the SELinux config file for editing:

$ cat /etc/selinux/config

3. Change the line in the file.SELINUX=enforcing

To:SELINUX=disabled

Note: You can also set the SELINUX setting to permissive. Setting SELINUX topermissive results in a number of warnings at installation time, but it allowsthe installation code to run.

4. To effect the changes, reboot the system with the following command:$ reboot

Set the kernel parameters

Required changes to Linux kernel parameters.

About this task

The following steps have been taken from the Metalink Note 421308, which isavailable from the Oracle website.

Procedure1. Add the following the lines in the file /etc/sysctl.conf


v kernel.shmall = physical RAM size / pagesize For most systems, this will bethe value 2097152.See Note 301830.1, which is available from the Oracle website, for moreinformation.

v kernel.shmmax = 1/2 of physical RAM, but not greater than 4GB.This would be the value 2147483648 for a system with 4Gb of physical RAM.

v kernel.shmmni = 4096v kernel.sem = 250 32000 100 128v fs.file-max = 6815744v net.ipv4.ip_local_port_range =9000 65500v net.core.rmem_default = 262144v net.core.rmem_max = 4194304v net.core.wmem_default = 262144v net.core.wmem_max = 1048576v fs.aio-max-nr = 1048576

2. To effect these changes, execute the command:# sysctl -p

Kernel parameters for DB2 database server installation (Linux)

The configuration or modification of kernel parameters for DB2 database serverinstallation depends on your operating system.

Kernel parameter requirements (Linux)

The database manager uses a formula to automatically adjust kernel parametersettings and eliminate the need for manual updates to these settings.

Interprocess communication kernel parameters

When instances are started, if an interprocess communication (IPC)kernel parameter is below the enforced minimum value, the database managerupdates it to enforced minimum value. The IPC kernel parameter values changedwhen a DB2 instance is started do not persist when the system is rebooted. After areboot, kernel settings might be lower than the enforced values until a DB2instance is started. By adjusting any kernel parameter settings, the databasemanger prevents unnecessary resource errors. For the information about supportedLinux distributions, see http://www-01.ibm.com/software/data/db2/linux-unix-windows.

Table 12. Enforced minimum settings for Linux interprocess communication kernelparameters

IPC kernel parameter Enforced minimum setting

kernel.shmmni (SHMMNI) 256 * <size of RAM in GB>

kernel.shmmax (SHMMAX) <size of RAM in bytes>1

kernel.shmall (SHMALL) 2 * <size of RAM in the default system pagesize> 2

kernel.sem (SEMMNI) 256 * <size of RAM in GB>

kernel.sem (SEMMSL) 250


http://www-01.ibm.com/software/data/db2/linux-unix-windows

http://www-01.ibm.com/software/data/db2/linux-unix-windows

Table 12. Enforced minimum settings for Linux interprocess communication kernelparameters (continued)

IPC kernel parameter Enforced minimum setting

kernel.sem (SEMMNS) 256 000

kernel.sem (SEMOPM) 32

kernel.msgmni (MSGMNI) 1 024 * <size of RAM in GB>

kernel.msgmax (MSGMAX) 65 536

kernel.msgmnb (MSGMNB) 65 536 3

1. On 32-bit Linux operating systems, the enforced minimum setting for SHMMAX is limitedto 4 294 967 295 bytes.

2. SHMALL limits the total amount of virtual shared memory that can be allocated on asystem. Each DB2 data server efficiently manages the amount of system memory itconsumes, also know as committed memory. The DB2 data server allocates more virtualmemory than it commits to support memory preallocation and dynamic memorymanagement. Memory preallocation benefits performance. Dynamic memory managementis the process of growing and shrinking real memory usage within separate virtual sharedmemory areas. To support memory preallocation and dynamic memory managementeffectively data servers frequently have to allocate more virtual shared memory on asystem than the amount of physical RAM. The kernel requires this value as a number ofpages.

3. Load performance might benefit from a larger message queue size limit, specified inbytes by MSGMNB. You can view message queue usage can by running the ipcs -qcommand. If the message queues are at capacity, or reaching capacity, during loadoperations, consider increasing the number of bytes the message queue size limit.

Other recommended kernel parameter settings

Other recommended kernel parameter settings are listed in thefollowing table.

Table 13. Configuring other Linux kernel parameters

Recommended kernel parameter settingConfiguring the kernel parameters for DB2data server

vm.swappiness=0 This parameter defines how prone the kernelis to swapping application memory out ofphysical random access memory (RAM). Thedefault setting is vm.swappiness=60. Therecommended kernel parameter setting,vm.swappiness=0, configures the kernel togive preference to keeping applicationmemory in RAM instead of assigning morememory for file caching. This setting avoidsunnecessary paging and excessive use ofswap space. This setting is especiallyimportant for data servers configured to usethe self-tuning memory manager (STMM).


Table 13. Configuring other Linux kernel parameters (continued)

Recommended kernel parameter settingConfiguring the kernel parameters for DB2data server

vm.overcommit_memory=0 This parameter influences how much virtualmemory the kernel permits allocating. Thedefault setting, vm.overcommit_memory=0, setsthe kernel to disallow individual processesfrom making excessively large allocations,however the total allocated virtual memoryis unlimited. Having unlimited virtualmemory is important for DB2 data servers,which retain additional unused virtualmemory allocations for dynamic memorymanagement. Unreferenced allocatedmemory is not backed by RAM or pagingspace on Linux systems. Avoid settingvm.overcommit_memory=2, as this settinglimits the total amount of virtual memorythat can be allocated, which can result inunexpected errors.

Modifying kernel parameters (Linux):

The database manager uses a formula to automatically adjust kernel parametersettings and eliminate the need for manual updates to these settings.

Before you begin

You must have root authority to modify kernel parameters.

Procedure

To update kernel parameters on Red Hat and SUSE Linux, follow these steps:1. Run the ipcs -l command to list the current kernel parameter settings.2. Analyze the command output to determine whether you have to change kernel

settings or not by comparing the current values with the enforced minimumsettings at http://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/c0057140.html. Thefollowing text is an example of the ipcs command output with commentsadded after // to show what the parameter names are:

# ipcs -l------ Shared Memory Limits --------max number of segments = 4096 // SHMMNImax seg size (kbytes) = 32768 // SHMMAXmax total shared memory (kbytes) = 8388608 // SHMALLmin seg size (bytes) = 1------ Semaphore Limits --------max number of arrays = 1024 // SEMMNImax semaphores per array = 250 // SEMMSLmax semaphores system wide = 256000 // SEMMNSmax ops per semop call = 32 // SEMOPMsemaphore max value = 32767------ Messages: Limits --------max queues system wide = 1024 // MSGMNImax size of message (bytes) = 65536 // MSGMAXdefault max size of queue (bytes) = 65536 // MSGMNB


http://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/c0057140.html

http://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/c0057140.html

v Beginning with the first section on Shared Memory Limits, the SHMMAXlimit is the maximum size of a shared memory segment on a Linux system.The SHMALL limit is the maximum allocation of shared memory pages on asystem.– It is recommended to set the SHMMAX value to be equal to the amount

of physical memory on your system. However, the minimum required onx86 systems is 268435456 (256 MB) and for 64-bit systems, it is 1073741824(1 GB).

– The SHMALL parameter is set to 8 GB by default (8388608 KB = 8 GB). Ifyou have more physical memory than 8 GB, and it is to be used for DB2,then this parameter increases to approximately 90% of your computer'sphysical memory. For instance, if you have a computer system with 16 GBof memory to be used primarily for DB2, then SHMALL should be set to3774873 (90% of 16 GB is 14.4 GB; 14.4 GB is then divided by 4 KB, whichis the base page size). The ipcs output converted SHMALL into kilobytes.The kernel requires this value as a number of pages. If you are upgradingto DB2 Version 10.1 and you are not using the default SHMALL setting,you must increase the SHMALL setting by an additional 4 GB. Thisincrease in memory is required by the fast communication manager (FCM)for additional buffers or channels.

v The next section covers the amount of semaphores available to the operatingsystem. The kernel parameter sem consists of four tokens, SEMMSL,SEMMNS, SEMOPM and SEMMNI. SEMMNS is the result of SEMMSLmultiplied by SEMMNI. The database manager requires that the number ofarrays (SEMMNI) be increased as necessary. Typically, SEMMNI should betwice the maximum number of agents expected on the system multiplied bythe number of logical partitions on the database server computer plus thenumber of local application connections on the database server computer.

v The third section covers messages on the system.– The MSGMNI parameter affects the number of agents that can be started; the

MSGMAX parameter affects the size of the message that can be sent in aqueue, and the MSGMNB parameter affects the size of the queue.

– The MSGMAX parameter should be changed to 64 KB (that is, 65536 bytes),and the MSGMNB parameter should be increased to 65536.

3. Modify the kernel parameters that you have to adjust by editing the/etc/sysctl.conf file. If this file does not exist, create it. The following lines areexamples of what should be placed into the file:

#Example for a computer with 16GB of RAM:kernel.shmmni=4096kernel.shmmax=17179869184kernel.shmall=8388608#kernel.sem=<SEMMSL> <SEMMNS> <SEMOPM> <SEMMNI>kernel.sem=250 1024000 32 4096kernel.msgmni=16384kernel.msgmax=65536kernel.msgmnb=65536

4. Run sysctl with -p parameter to load in sysctl settings from the default file/etc/sysctl.conf:sysctl -p

5. Optional: Have the changes persist after every reboot:v (SUSE Linux) Make boot.sysctl active.v (Red Hat) The rc.sysinit initialization script reads the /etc/sysctl.conf file

automatically.



IBM DB2 11.1 for Linux, UNIX, and Windows documentation on IBMKnowledge Center

Replace the native taring utility with gnu tarReplace the native taring utility with GNU tar.

Before you begin

Check the version of tar command you have at present by entering the followingcommand:#tar --version

For a GNU tar utility the output would conform to the following:tar (GNU tar) 1.14Copyright (C) 2004 Free Software Foundation, Inc.This program comes with NO WARRANTY, to the extent permitted by law.You may redistribute it under the terms of the GNU General Public License;see the file named COPYING for details.Written by John Gilmore and Jay Fenlason.

If the resulting output does not indicate a GNU tar utility then perform thefollowing steps.

Procedure1. Find the native tar location.

#which tar/usr/bin/tar

2. Move the native binary tar command:#cd /usr/bin#mv tar tar_

3. Install the GNU tar, which can be obtained from the toolbox site:For example, refer the following toolbox site for AIX http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.htmlSet the install location to be something similar to /opt/freeware/bin/tar

4. Create a gnu tar soft link:ln -s /opt/freeware/bin/tar /usr/bin/tar

5. Validate that the tar command is gnu tar:#tar --version

Resulting output should be as stated in prerequisite step.

Installing libcrypto.soFor starting up DataLoad process correctly upon installation and for full SNMPv3support, SNMP DataLoad must have access to the libcrypto.so.

About this task

Note: If you are running on a Linux platform, please start with step3 onwards. The libcrypto.so file is delivered as standard on Linux platforms,hence step 1 and 2 are not required.

For each new and existing SNMP DataLoad, you must perform the following steps.


http://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.welcome.doc/doc/welcome.html

http://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.welcome.doc/doc/welcome.html

http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html

http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html

Procedure1. Install the OpenSSL package. This package can be downloaded from

http://www.openssl.org/.2. As root, extract and install the libcrypto.so file by using the following code:

# cd /usr/lib# ar -xv ./libcrypto.a# ln -s libcrypto.so.0.9.8 libcrypto.so

3. Remove the existing link for libcrypto.so if any by using the following code:# cd /usr/lib# rm -rf libcrypto.so

4. Create a link for libcrypto.so which links to libcrypto.so.0.9.8e using thefollowing code:# cd /usr/lib# ln -s libcrypto.so.0.9.8e libcrypto.so

5. Update the dataload.env file so that the LD_LIBRARY_PATH (on Solaris & Linux)or LIBPATH (on AIX) environment variables include the path:/usr/lib

What to do next

Check the variable is set by doing the following steps:1. Open a fresh shell.2. Verify that the environment variables are set correctly in dataload.env file.3. Source the dataload.env file.4. Bounce the SNMP DataLoad process.

Upon DataLoad process startup with a valid library, the collector logs thefollowing log messages:INFO:CRYPTOLIB_LOADED Library ’libcrypto.so’ (OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008, 0x90802f)has been loaded.INFO:SNMPV3_SUPPORT_OK Full SNMPv3 support Auth(None,MD5,SHA-1) x Priv(None,DES,AES) is available.

Deployer pre-requisitesMinimum filesystem specification and pre-requisites for the Deployer script.

The Deployer will check the for the items described under the following headings.You should ensure that all elements are installed before running the deployer.

Operating system checkThe Deployer will fail if the required patches listed in this file are not installed.

The Deployer performs a check on the operating system versions and that theminimum required packages are installed.

For more information on the complete set of requirements for installation on Linux,AIX and Solaris, consult the Requirements chapter.


http://www.openssl.org/

Mount points checkThe Deployer assesses the available filesystem space for the defined mount pointlocations.

The space requirements are calculated based on:v The defined topology: The more components added to a single server the more

space is required on that server.v The component install location: Any directory set as the install location for a

component requires sufficient space to store that component. The default installdirectory is /opt. You do not have to use the default. This can be set to anydirectory location that has sufficient space.

v Remote installation of components: If components are being installed remotely,sufficient space must be assigned in the /tmp directory to store the softwarebefore it can be transferred to the remote servers.

For a statement of minimum space requirements per server in a distributed installor for a single server in a proof of concept install, see Chapter 2, “Requirements,”on page 33.

Authentication between distributed serversWhy you must authenticate between distributed servers.

If you are performing an installation that has a topology covering a set ofdistributed servers, ensure that RSA keys have been cached between servers forroot and pvuser prior to installation. If there are new servers that form part ofinstallation topology which have not been authenticated, the installation will fail.

Note: pvuser is the required Tivoli Netcool Performance Manager Unix user.Adding this user to your system is described in “Adding the pvuser login name”on page 69.

Tivoli Netcool Performance Manager distributionHow to get the product distribution.

The Tivoli Netcool Performance Manager distribution is available as an electronicimage. These instructions assume that you are installing from an electronic image.

If you install the product from an electronic image, be sure to keep a copy of thedistribution image in a well-known directory because you will need this image inthe future to make changes to the environment, including uninstalling TivoliNetcool Performance Manager.

The Tivoli Netcool Performance Manager distribution contains the softwarerequired to install Tivoli Netcool Performance Manager 1.4.3.


Downloading the Tivoli Netcool Performance Managerdistribution to disk

To download the Tivoli Netcool Performance Manager distribution to a directoryon a target server's hard disk:

About this task

Whether you are installing the product from an electronic image, you must copythe distribution to a writeable location on the local filesystem before beginning theinstallation.

To download the Tivoli Netcool Performance Manager distribution to a directoryon the host from which you intend to run the Topology Editor:

Procedure1. On the target host, log in as the Tivoli Netcool Performance Manager user, such

as pvuser.2. Create a directory to hold the contents of your Tivoli Netcool Performance

Manager distribution. For example:$ mkdir /var/tmp/cdproviso

Note: Any further references to this directory within the install are made byusing the token <DIST_DIR>.You can run a variety of scripts and programs from directories residing in thedirectory created on the hard drive, including:v Oracle server configuration scriptv Pre-installation scriptv Installation scriptv Tivoli Netcool Performance Manager setup program

3. Download the Tivoli Netcool Performance Manager distribution to the hostdirectory created in the previous step and expand the contents of thedistribution package.

General database setup tasksHow to install a database for use with Tivoli Netcool Performance Manager.

To install database you need:v An appropriately sized server with the operating system installed and running

(for the database server).

Note: For a basic overview of the minimum CPU speed, memory size, and diskconfiguration requirements for your Tivoli Netcool Performance Managerinstallation, see the Requirements. For more detailed information you cancontact IBM Professional Services.

v The current version of Tivoli Netcool Performance Manager software.v The downloaded files for the database installation.

Before installing database, read the setup and password information.

Note: Tivoli Netcool Performance Manager should be installed and run as astandalone database. It should not be placed on a server that already has a


database as the installation program will likely interfere. The co-hosting of TivoliNetcool Performance Manager also affects performance in unknown ways. If aco-host is required then the you must contact IBM Professional Services forsupport.

Specifying a basename for DB_USER_ROOT

and Tivoli Netcool Performance Manager components use distinct login names so thatdatabase access can be controlled separately by component, and for databasetroubleshooting clarity.

About this task

The Tivoli Netcool Performance Manager installation generates the appropriatelogin names for each Tivoli Netcool Performance Manager subsystem.

Procedure

Provide a basename, which the installation retains as the variableDB_USER_ROOT.

Note: This is not an operating system environment variable, but a variable usedinternally by the installer.The default DB_USER_ROOT value is PV. IBM recommends you to retain the defaultvalue.

Important: Avoid changing default values of DB_USER_ROOT (PV) andDB_ROOT_NAME (pv).

Restriction: DB_USER_PASSWD is restricted to alpha numeric characters only.Ensure that DB_USER_PASSWD does not contain any spaces or special characters,otherwise Proviso Database installation will fail.

Results

Login names are generated from the DB_USER_ROOT basename by appending afunction or subsystem identifier to the basename, as in the following examples:v PV_ADMIN

v PV_INSTALL

v PV_LDR

v PV_CHANNEL

v PV_COLL

v PV_CHNL_MANAGER

v PV_GUI

In addition, separate login names are generated for each Tivoli NetcoolPerformance Manager DataChannel and subsystem, identified by an appendedchannel number, as in the following examples:v PV_CHANNEL_01

v PV_CHANNEL_02

v PV_LDR_01

v PV_LDR_02


Specifying login passwords

and For each component that requires a database login name, you must provide apassword for that login name.

About this task

In every case, the installer uses the default password, PV.

Passwords are case-sensitive, so PV and pv is not the same password.

Procedure

You can retain the default password, or enter passwords of your own according toyour site password standards.You should use the same password for all Tivoli Netcool Performance Managersubsystem login names. If you use different passwords for each login name, keep arecord of the passwords you assign to each login name.

Important: Avoid using any special characters in any password field, (forexample, @, \, /) while installing Tivoli Netcool Performance Manager with DB2.

Results

The Tivoli Netcool Performance Manager installer uses PV for three default values,as described in Table 5.

Table 5: Uses of PV as Default Values

Installer Default Value Used As Recommendation

PV Default value of theDB_USER_ROOT variable, thebasename on which loginnames are generated

In all instances, use thedefault value PV, unless yoursite has an explicit namingstandard or an explicitpassword policy.PV Default password for all

login names

PV Default database name, alsocalled the TNS name forOracle.

What to do next

Note: If you use a non-default value, you must remember to use the same value inall installation stages. For example, in Oracle, if you set your TNS name to PROVinstead of PV, you must override the default PV entry in all subsequent steps thatcall for the TNS name.


Assumed valuesThe steps in this information assume the following default values:

Setting Assumed Value

Hostname of the

and

server

delphi

Server program files installed inv -/opt/oracle

v -/opt/db2

v _BASE

v _BASE

v /opt/oracle

v /opt/db2Note: DB2_BASE directory should besame as home directory of DB2 instanceuser.Important: If you are using non-defaultpath for DB2 installation directory, youmust modify the DB2_BASE parameter inTopology Editor also.

Operating system login name for:

v user

v user

v oracle

v db2

Note: The default name created is oracleand db2 for Oracle and IBM DB2 databasesrespectively. However, you can set anothername for the DB2 or Oracle user.

Password for:

v user

v user

v oracle

v db2Important: Avoid using any specialcharacters in any password field, (forexample, @, \, /) while installing TivoliNetcool Performance Manager with DB2.

v _NAME

v _NAME

PV

TNS name for Tivoli Netcool PerformanceManager database instance

PV

v installed inORACLE_HOME

v installed inDATABASE_HOME

v /opt/oracle/product/ 12.1.0

v /opt/db2/product/11.1.0

Note: The value of ORACLE_HOME orDATABASE_HOME cannot contain soft linksto other directories or file systems. Be sureto specify the entire absolute path to Oracleor DB2.Tivoli Netcool Performance Managerexpects an Optimal Flexible Architecture(OFA) structure where DATABASE_HOMEor ORACLE_HOME is a sub-directory toDB2_BASE or ORACLE_BASE.Important: If you are using non-defaultpath for DB2 installation directory, you mustmodify DB2_BASE parameter in TopologyEditor also.


Setting Assumed Value

Oracle login name for databaseadministrator (DBA)

system

Password for Oracle DBA login name

manager

DB_USER_ROOT

PV

Path for Oracle data, mount point 1

Path for DB2 data, mount point 1

v /raid_2/oradata

v /raid_2/db2data

Path for Oracle data, mount point 2

Path for DB2 data, mount point 2

v /raid_3/oradata

v /raid_3/db2data

Note: If your site has established naming or password conventions, you cansubstitute site-specific values for these settings. However, IBM stronglyrecommends using the default values the first time you install Tivoli NetcoolPerformance Manager. See “Specifying a basename for DB_USER_ROOT” on page84 for more information.

Creating group and user ID for a DB2 server installation

You can use the DB2 Setup wizard to create the users and groups during theinstallation process. If you want, you can create them ahead of time.

Before you begin

To perform this task, you must have root user authority to create users andgroups.

About this task

Two users and groups are required.

The user and group names that are used in the following instructions aredocumented in the following table. You can specify your own user and groupnames if they adhere to system naming rules and DB2 naming rules.

The user IDs you create are required to complete subsequent setup tasks.


Table 14. Default users and groups

User Description Example user name Example group name

Instance owner The DB2 instance iscreated in theinstance owner homedirectory. This userID controls all DB2processes and ownsall file systems anddevices that are usedby the databases thatare contained withinthe instance. Thedefault user is db2and the defaultgroup is db2iadm.

db2 db2iadm

Fenced user The fenced user isused to runuser-definedfunctions (UDFs) andstored proceduresoutside of theaddress space that isused by the DB2database. The defaultuser is db2fenc andthe default group isdb2fadm. If you donot need this level ofsecurity, for examplein a testenvironment, you canuse your instanceowner as your fenceduser.

db2fenc db2fadm

User ID restrictions

User IDs have the following restrictions and requirements:v Must have a primary group other than guests, admins, users, and local.v Can include lowercase letters (a-z), numbers (0-9), and the underscore character

(_).v Cannot be longer than eight charactersv Cannot begin with IBM, SYS, SQL, or a number.v Cannot be a DB2 reserved word (USERS, ADMINS, GUESTS, PUBLIC, or

LOCAL), or an SQL reserved word.v Cannot use any user IDs with root privilege for the DB2 instance ID, DAS ID, or

fenced ID.v Cannot include accented characters.

Procedure

To create the required groups and user IDs for DB2 database systems, follow thesesteps:1. Log in as root user.


2. To create groups on Linux operating systems, enter the following commands:

Note: These command line examples do not contain passwords. You can usethe passwd username command from the command line to set the password.groupadd db2iadmgroupadd db2fadm

3. Create users for each group by using the following commands:useradd -g db2iadm -m -d /opt/db2 db2useradd -g db2fadm -m -d /home/db2fenc db2fenc

4. Set initial password by using the following commands:passwd db2Changing password for user db2.New UNIX password: db2BAD PASSWORD: it is WAY too shortRetype new UNIX password: db2passwd: all authentication tokens updated successfully.

passwd db2fencChanging password for user db2fenc.New UNIX password: db2fencBAD PASSWORD: it is based on a dictionaryRetype new UNIX password: db2fencpasswd: all authentication tokens updated successfully.

5. Relax the permission on home directory of db2 user as you want to install DB2inside it by using the following command:chmod 707 /opt/db2

Creating group and user IDs for Data Server Client installation

One user and one group are required.

About this task

You require only the Instance owner. For more information about the Instanceowner and user ID restrictions, see “Creating group and user ID for a DB2 serverinstallation” on page 87.

Procedure

To create the required groups and user IDs for Data Server Client installation,follow these steps:1. Log in as a user with root user authority.2. To create groups on Linux operating systems, enter the following commands:

Note: These command line examples do not contain passwords. They areexamples only. You can use the passwd username command from thecommand line to set the password.groupadd db2iadm

3. Create users for each group by using the following commands:useradd -g db2iadm -m -d /opt/db2 db2

4. Set initial password by using the following commands:passwd db2Changing password for user db2.New UNIX password: db2


BAD PASSWORD: it is WAY too shortRetype new UNIX password: db2passwd: all authentication tokens updated successfully.

5. Relax the permission on home directory of db2 user as we want to install theData Server Client inside it by using the following command:chmod 707 /opt/db2


Chapter 4. Installing Jazz for Service Management

The Jazz for Service Management installation supports different installationscenarios, user types, installation modes, and server topologies according to yourorganization needs and target server environments. You can use either a launchpador IBM Installation Manager to install and configure Jazz for Service Management.You can install and configure one or more integration services on a one, two, orthree servers.

About this task

To plan the Jazz™ for Service Management installation, you must choose yourinstallation scenario. This choice depends on the following factors:v Number of integration services to installv Reuse the existing database and application server middlewarev Installation modev User type

These factors determine your installation scenario that you use to install Jazz forService Management. You can also use the decision maps. See Installation decisionmaps.

Important:

v Do not install Jazz for Service Management 1.1.3.0 on a Solaris machine in adistributed or a stand-alone environment.

v For minimal installation of Tivoli Netcool Performance Manager, use onlysmadmin as the administration user name and smadmin1 as the administrationpassword for Jazz for Service Management. The default administration username is smadmin.

v To start or stop the server, you must log in with the same user that you used toinstall Jazz for Service Management. If Jazz for Service Management is installedwith non-root user, never restart Jazz for Service Management applicationservers with root user, or else the Dashboard Application Services Hub becomesunusable.


Jazz for Service Management Version 1.1.3.0 Readme

Jazz for Service Management on IBM Knowledge Center

Installing Jazz for Service Management

Common directory locations


https://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_c_install_plan_maps.html

https://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_c_install_plan_maps.html

http://www-01.ibm.com/support/docview.wss?uid=swg24042190

https://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/psc_ic-homepage.html

https://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_c_install.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/ref/psc_r_pathnames.html

Hardware and software requirements for installing Jazz for ServiceManagement

Jazz for Service Management and its integration services have hardware andsoftware requirements, including supported middleware and installationtechnologies.

Important: Jazz for Service Management installation is not supported on Solarisplatform.

Important: You must add the following list of Linux libraries, which areprerequisite when you install Jazz for Service Management. If you do not includethese libraries, it can cause failure of prerequisite scanner or the installation of Jazzfor Service Management.os.lib.libSM.so.6_32os.lib.libICE.so.6_32os.lib.libfreetype.so.6_32os.lib.libuuid.so.1_32os.lib.libfontconfig.so.1_32os.lib.libjpeg.so.62_32os.lib.libpng12.so.0_32os.lib.libz.so.1_32os.lib.libstdc.so.5_32os.lib.libstdc.so.6_32


Jazz for Service Management Detailed System Requirements

Quick reference to Jazz for Service Management installationUse this information to download and install Jazz for Service Management 1.1.3.0.Jazz for Service Management Version 1.1.3.0 is a full refresh of Jazz for ServiceManagement Version 1.1 Base with Modification 3.

This table summarizes the steps to plan and install Jazz for Service Management.1. This table summarizes the steps to plan and install Jazz for Service

Management.



Task Description

Download and extract the softwareDownload and extract the Jazz for ServiceManagement Version 1.1.3.0 and otherrequired components from IBM PassportAdvantage.

v 1.1.3.0-TIV-JazzSM-multi.zip: 64-bit,multiplatform IBM Installation Managersoftware package repository for thefollowing Jazz for Service Managementintegration services and components:

– IBM Dashboard Application ServicesHub 3.1.3.0

– Jazz for Service Management extensionfor IBM WebSphere Version 1.1.3.0

– IBM Tivoli Common Reporting 3.1.3.0

v IBM-was-8.5.5.9-platform.zip:Platform-specific WebSphere ApplicationServer Version 8.5.5.9

v 3.1.3.0-TIV-JazzSM-TCR-COGNOS-platform.tar.gz|.zip: Platform-specificIBM Cognos Business IntelligenceReporting for Tivoli Common ReportingVersion 3.1.3.0.

System requirementsAssess the hardware and softwarerequirements. See Hardware and softwarerequirements.

Plan your installationYou can choose to perform a full or custominstallation of Jazz for Service Management.Different factors determine whichinstallation scenario you must choose, forexample, the integration services to install,business and security policies, your targetenvironments, and user types. See Planningyour deployment.

Prepare your environmentPrepare your environment whether youperform a fresh or upgrade. See Preparingyour environment.

Chapter 4. Installing Jazz for Service Management 93

https://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_c_install_prereqs.html

https://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_c_install_prereqs.html

https://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_c_install_plan.html?view=kc

https://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_c_install_plan.html?view=kc

https://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_ctr_install_prep_env.html?view=kc

https://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_ctr_install_prep_env.html?view=kc

Task Description

Perform a fresh installation20 GB of free disk space is required for afresh installation. Follow these steps:

v Download and extract1.1.3.0-TIV-JazzSM-multi.zip and otherrequired software to a local directory, forexample, <JazzSM_FP_Home>.

v Add the JazzSM_FP_Home/1.1.3.0-TIV-JazzSM-multi/JazzSMFPRepository/disk1/diskTag.inf file along with the repositorylocations for any other earlier Jazz forService Management versions toInstallation Manager > File > Preferences> Add Repository.

v Follow the installation instructions. SeePerforming a full installation.

Important: Jazz for Service Management1.1.3.0 installation fails on RHEL 7.2 usingFull Installation option.

To troubleshoot, see Issues with Jazz forService Management 1.1.3.0 Full Installationmode on RHEL 7.2 in Troubleshooting TivoliNetcool Performance Manager guide.

Perform an upgradeJazz for Service Management Version 1.1.3.0can be installed on top of earlier Jazz forService Management releases (1.1, 1.1.0.1,1.1.0.2, 1.1.0.3, 1.1.1.0, 1.1.2.0, 1.1.2.1). UseIBM Installation Manager in GUI or silentmodes to first update the Jazz for ServiceManagement extension for IBM WebSphereand then install Jazz for ServiceManagement Version 1.1.3.0 for DashboardApplication Services Hub installation. SeeApplying fix pack by using InstallationManager GUI mode.

Perform post-installation tasksVerify the installation. See Post-installationtasks.

Configuring Jazz for Service Management

2. This table summarizes the steps to configure Jazz for Service Management.


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_t_install_typical.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_t_update_im_fp3.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_t_update_im_fp3.html

https://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_ctr_install_post_install.html?view=kc

https://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/install/psc_ctr_install_post_install.html?view=kc

Task Description

Cross-serviceYou can configure a central user registry,such as a Lightweight Directory AccessProtocol (LDAP) registry, for Jazz for ServiceManagement user management andauthentication.

Configure WebSphere Application Server touse a central federated repository with anLDAP user registry. After configuration, youcan add users to the federated repository.

You can configure the integration servicesfor single sign-on, so that users can accessJazz for Service Management applications bylogging in only once.

During installation, the global securityconfiguration is enabled that applies to thesecurity policy for all administrativefunctions in each Jazz for ServiceManagement application server. Theconfiguration is also used as a defaultsecurity policy for user applications.

See Configuring Jazz for ServiceManagement.

Dashboard Application Services HubFor installations of Dashboard ApplicationServices Hub with large user populations,you can set up a load balancing cluster ofconsole nodes with identical configurationsto evenly distribute user sessions.

You can choose to configure DashboardApplication Services Hub to use TivoliAccess Manager WebSEAL Version tomanage authentication.

You can also configure the Context MenuService (CMS) to use a remote database,which can be used by products to shareinformation outside of the DashboardApplication Services Hub environment.

See Configuring Dashboard ApplicationServices Hub.

Tivoli Common ReportingAfter you install Tivoli Common Reporting,prepare your report packages to be able togenerate, publish, and edit your reports.

You can configure database connectiondetails to a data source other than DB2.

See Configuring Tivoli Common Reporting.


Download Jazz for Service Management Version 1.1.3.0


http://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/config/psc_c_config.html

http://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/config/psc_c_config.html

http://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/config/tip_c_config.html

http://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/config/tip_c_config.html

http://www.ibm.com/support/knowledgecenter/en/SSEKCU_1.1.3.0/com.ibm.psc.doc/config/tcr_c_config.html


Getting started with Jazz for Service Management

Starting Jazz for Service Management application serversYou can start any Jazz for Service Management virtualization and reporting serversby using the IBM WebSphere startServer command. You might need to restart theapplication server after you complete a configuration task for an integrationservice, or after you stop the application server for maintenance.

About this task

The same procedure applies to any Jazz for Service Management applicationserver.

Procedure1. On the relevant Jazz for Service Management server, open a command window.2. Change to the JazzSM_WAS_Profile/bin directory.

The default location for <JazzSM_WAS_Profile> is /opt/IBM/JazzSM/profile.3. Run the following command:

./startServer.sh server_name

Where

server_nameEnter the name of the application server that was specified when theapplication server profile was created.

For example, server1.Related information:


Stopping Jazz for Service Management application serversYou can stop any Jazz for Service Management application server by using the IBMWebSphere stopServer command. You might need to restart the application serverafter you complete a configuration task for an integration service, or stop theapplication server for maintenance. To start the server again, use the startServercommand.

Procedure1. On the relevant Jazz for Service Management server, open a command window.2. Change to the <JazzSM_WAS_Profile>/bin directory. The default location for

<JazzSM_WAS_Profile> is /opt/IBM/JazzSM/profile.3. Run the following command:

./stopServer.sh <server_name> -username <WAS_admin_user_name> -password <WAS_admin_password>

Where

server_nameEnter the name of the application server that was specified when theapplication server profile was created. For example, server1.


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/oview/psc_c_oview_getting_started.html


WAS_admin_user_nameThe default user name is smadmin.

WAS_admin_passwordPassword that is specified at the time of installation.

Example

stopServer.sh server1 -username smadmin -password jazzsmpwd



Upgrading JavaEnsure that you configure the IBM WebSphere® Application Server to run withJava 7 after successfully installing Jazz for Service Management 1.1.3.0

About this task

Important: The IBM WebSphere Application Server must be running with Java 7before you proceed to upgrade Tivoli Netcool Performance Manager DataViewcomponent.

To upgrade to Java 7, follow these steps:

Procedure1. On the relevant Jazz for Service Management server, open a command window.2. Move the Java 6 file and create a soft link to Java 7 by using the following

commands:$ cd /opt/IBM/WebSphere/AppServer$ mv java java_1.6$ ln -s java_1.7_64 java

3. To find the Java processes related to WebSphere Application Server, run thefollowing command:For example:$ ps –ef|grep java |grep WebSroot 12742 1 0 Jan05 ? 00:37:07/opt/IBM/WebSphere/AppServer/java_1.7_64/bin/java -Declipse.security-Dwas.status.socket=32111 -Dosgi.install.area=/opt/IBM/WebSphere/AppServer-Dosgi.configuration.area=/opt/IBM/JazzSM/profile/servers/server1/configuration-Djava.awt.headless=true-Dosgi.framework.extensions=com.ibm.cds,com.ibm.ws.eclipse.adaptors-Xshareclasses:name=webspherev85_1.7_64_%g,nonFatal-Dcom.ibm.xtq.processor.overrideSecureProcessing=true -Xcheck:dump-Xbootclasspath/p:/opt/IBM/WebSphere/AppServer/java_1.7_64/jre/lib/ibmorb.jar -classpath........

4. Kill all Java processes related to WebSphere Application Server by using thefollowing command: kill -9 <process_id>For example:$ kill -9 12742



What to do next

You must restart Jazz for Service Management 1.1.3.0 application server after youcomplete the Java upgrade step.


Chapter 5. Installing database

Instructions on how to install the Oracle and DB2 database for Tivoli NetcoolPerformance Manager.

The following topics mention in detail about:v “Installing Oracle 12.1.0.2 server (64-bit)”v “Installing Oracle 12.1.0.2 client 32-bit” on page 114v “Installing DB2 Server 11.1.1.1 (64-bit)” on page 128v “Installing IBM Data Server Client 11.1.1.1, Linux 64-bit (64-bit)” on page 135

Note: You need to regularly purge the metric data either by manually purging orby using cron job. For more information, see Purging metric data topic underAdministering Database guide.

Installing Oracle 12.1.0.2 server (64-bit)

Instructions on how to install the Oracle 12.1.0.2 server (64-bit).

To install Oracle 12.1.0.2 server (64-bit), you can use the scripts provided as part ofTivoli Netcool Performance Manager.

Download the Oracle distribution to diskThe Oracle installation files must be in place before you can begin the installationof Oracle.

About this task

Note: Oracle 12.1.0.2 client (32-bit) must be installed into a new ORACLE_HOME.

Procedure1. Log in as root.2. Set the DISPLAY environment variable.3. Create a directory to hold the contents of the Oracle distribution. For example:

# mkdir /var/tmp/oracle12102

4. Download the Oracle files to the /var/tmp/oracle12102 directory.5. Extract the Oracle distribution files that now exist in the /var/tmp/oracle12102

directory.

Results

The directory created and to which the Oracle 12.1.0.2 distribution is downloadedfrom now on be referred to by using <ORA_DIST_DIR>.


Before beginning this task, make sure that you have:v Downloaded the Tivoli Netcool Performance Manager distribution to disk.

The directory that is created and to which the Tivoli Netcool PerformanceManager distribution is downloaded from now on be referred to by using<DIST_DIR>.

What to do next

Before you proceed to the next step, make sure that you obtain the upgradeinstructions provided by Oracle. The instructions contain information onperforming steps that are required for the upgrade that are not documented in thisguide.

See your database administrator to determine whether there are anycompany-specific requirements for installing Oracle in your environment.

Verify the required operating system packagesBefore installing the Oracle server, make sure the all required packages areinstalled on your system.

Procedure1. Make sure all the required Solaris packages and patches are installed on your

system. All required packages and patches are specified in the Chapter 2,“Requirements,” on page 33.

2. If these packages are not on your system, see the relevant operating systemInstallation Guide for instructions on installing supplementary packagesoftware.

Running the Oracle server configuration scriptIn this step, you set up the Oracle environment by using the script that is providedwith the Tivoli Netcool Performance Manager DataMart files on the Tivoli NetcoolPerformance Manager distribution.

About this task

This script automatically creates the following configuration:v Adds the dba and install groups to /etc/groupv Adds the login name oracle, whose primary group membership is dba and

secondary group membership is oinstall.

Note: You must use the same Oracle username across all instances of OracleClient and Server throughout your Tivoli Netcool Performance Manager system.

v Creates the Oracle directory structurev Creates startup and shutdown scripts for Oracle server processes

Note: If the oracle user is not created, the script creates this user for you, andORACLE_BASE is set as the user home directory. If you would prefer to use adifferent home directory for the oracle user, create the oracle user before you runthe script. The script does not create an oracle user if one exists.

Note: It is likely that you have create the dba and install groups and the oracleuser. However, this script must still be run to create the required Oracle directorystructure.


To configure the Oracle installation environment by using the script:

Procedure1. As root, set the ORACLE_BASE and ORACLE_HOME environment variables.

For example:# export ORACLE_BASE=/opt/oracle/# export ORACLE_HOME=/opt/oracle/product/12.1.0

Note: The script places this variable into the oracle login account's .profilefile.To check that the variable is set correctly, enter the following command:# env | grep ORA

2. Change to the following directory:

systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/oracle/instance

systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX<version_num>/oracle/instance

systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL<version_num>/oracle/instance

where:<DIST_DIR> is the directory on the hard disk drive where you copied thecontents of the Tivoli Netcool Performance Manager distribution in “Downloadthe Oracle distribution to disk” on page 115.

3. Run the Oracle configuration script by entering the following command:# ./configure_ora

Important: If permission to the $ORACLE_BASE directory is not granted, theinstall database step fails during deployment. During Oracle installation, the/opt/oracle folder that is created by configure_ora script has no permissionthat is granted to any other users. Therefore, after you run the configure_orascript, assign the following permission to the $ORACLE_BASE directory (forexample, /opt/oracle):a. Log in as oracle user.b. Run the following command:

chmod 755 /opt/oracle

The following screen is displayed:

Chapter 5. Installing database 101

--------------------------------------------------Setting the Oracle environment<Current Date>--------------------------------------------------OS ........... : [ Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 ]Host ......... : [ <Hostname> ]Logname ...... : [ root ]ORACLE_BASE .. : [ /opt/oracle ]ORACLE_HOME .. : [ /opt/oracle/product/12.1.0 ]

DBA group ................. : [ dba ]OUI inventory group ....... : [ oinstall ]Oracle software owner ..... : [ oracle ]

Configure Oracle release .. : [ 12.1.0 ]

Menu :1. Modify Oracle software owner.2. Next supported release.3. Check environment.0. Exit

Choice :

4. Type 3 at the Choice prompt and press Enter.The script creates the dba and oinstall groups and the ORACLE_BASE directory,unless they exist:

Checking environment...Checking for group [ dba ] --> Created.Checking for group [ oinstall ] --> Created.Checking ORACLE_BASE** WARNING** ORACLE_BASE directory does not exist.** [ /opt/oracle ]**** Create it ? (n/y) y

5. Type y and press Enter.The script creates the /opt/oracle directory and continues as follows:

Checking for user [ oracle ]** WARNING** User [ oracle ] does not exist.**** Create it locally ? (n/y) y

6. Type y and press Enter.The script creates the oracle user and continues as follows:


--> Created.Checking for oracle directory tree :[ /opt/oracle/product ] --> Created.[ /opt/oracle/product/12.1.0 ] --> Created.[ /opt/oracle/product/12.1.0/dbs ] --> Created.[ /opt/oracle/admin ] --> Created.[ /opt/oracle/admin/skeleton ] --> Created.[ /opt/oracle/admin/skeleton/lib ] --> Ok.[ /opt/oracle/admin/skeleton/lib/libpvmextc.so ] --> Created.[ /opt/oracle/admin/skeleton/lib/libmultiTask.so ] --> Created.[ /opt/oracle/admin/skeleton/lib/libcmu.so ] --> Created.[ /opt/oracle/admin/skeleton/bin ] --> Ok.[ /opt/oracle/admin/skeleton/bin/snmptrap ] --> Created.[ /opt/oracle/local ] --> Created.Checking for oracle .profile file --> Created.Checking for dbora file --> Created./etc/rc0.d/K10dbora link --> Created./etc/rc1.d/K10dbora link --> Created./etc/rc2.d/S99dbora link --> Created.Checking for dbora configuration files :/var/opt/oracle/oratab --> Created./var/opt/oracle/lsnrtab --> Created.Press Enter to continue...

7. Press the Enter key to continue. The main screen is refreshed.8. Type 0 and press Enter to exit the script.

Note: You must set a password for the oracle login name.

Structure created by the configure_ora scriptThe configure_ora script creates the Oracle directory structure.

The following example shows the directory structure that is created for Oracle,where ORACLE_BASE was set to /opt/oracle:/opt/oracle/product12.1.012.1.0/dbs/opt/oracle/admin/opt/oracle/admin/skeleton/opt/oracle/admin/skeleton/bin/opt/oracle/local

The script creates the following setup files:

Specific files:

v /etc/init.d/dbora, which starts the Oracle Listener and database serverautomatically on each system restart

v Symbolic links to /etc/init.d/dbora in /etc/rc0.d, /etc/rc1.d, and /etc/rc2.dv Oracle configuration files /var/opt/oracle/oratab and lsnrtab.

Specific files:v /etc/inittab is modified to contain the dbstart and lsnrctlstartup calls.v /etc/rc.shutdown is modified to contain the dbshut and lsnrctl stop

commands.v Oracle configuration files /etc/oratab and /etc/lsnrtab.

Note: AIX does not use init.d.

Common files:


v A .profile file for the oracle user that contains the following lines:

# -- Begin Oracle Settings --umask 022ORACLE_BASE=/opt/oracleORACLE_HOME=$ORACLE_BASE/product/12.1.0NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/dataLD_LIBRARY_PATH=$ORACLE_HOME/libTNS_ADMIN=$ORACLE_HOME/network/adminPATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/binEXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.soexport PATH ORACLE_BASE ORACLE_HOME NLS_LANGexport ORA_NLS33 LD_LIBRARY_PATH TNS_ADMINexport EXTPROC_DLLS# -- End Oracle Settings --

Note:

v The value of ORACLE_HOME cannot contain soft links to other directories orfile systems. Be sure to specify the entire absolute path to Oracle.

v You must add the ORACLE_SID variable to this file later, in “Set theORACLE_SID variable” on page 106.

Setting a password for the Oracle login nameYou must assign a password for the oracle login name to maintain systemsecurity.

About this task

The configure_ora script that you ran in the previous section creates the oraclelogin name. You must assign a password for the oracle login name to maintainsystem security, and because subsequent installation steps expect the password tobe already set.

To set a password:

Procedure1. Log in as root.2. Enter the following command:

# passwd oracle

3. Enter and reenter the password (oracle, by default) as prompted. Thepassword is set.

Run the preinstallation scriptRun the preinstallation script to verify your readiness to install Oracle.

Procedure1. As root, change directory using the following command:

systems:

# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/oracle/instance/ora_installer

systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX<version_num>/oracle/instance/ora_installer

systems:


# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL<version_num>/oracle/instance/ora_installer

where:<DIST_DIR> is the directory on the hard drive where you copied the contents ofthe Tivoli Netcool Performance Manager distribution in “Download the Oracledistribution to disk” on page 115.

2. Set the ORACLE_BASE environment variable. For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE

Note: You must use the same ORACLE_BASE setting that you specified in“Run the Oracle server configuration script”.

3. Enter the following command:# ./pre_install_as_root

The following messages indicate success:

Checking that you are logged in as root --> Ok.Checking ORACLE_BASE --> Ok.Checking oraInst.loc file --> Ok.

If the script shows an error, correct the situation causing the error beforeproceeding to the next step.

Running the rootpre.sh script (AIX only)

To run the rootpre.sh script.

Procedure1. Log in as root or as a superuser.2. Set the DISPLAY environment variable.3. Change to the directory <ORA_DIST_DIR>/database.

Note: The Oracle server (64-bit) distribution is downloaded to <ORA_DIST_DIR>as per the instructions in the section “Download the Oracle distribution todisk” on page 115.

4. Run the following command:./rootpre.sh

rootpre.sh may return an error like the following:

Configuring Asynchronous I/O....Asynchronous I/O is not installed on this system.

This error can safely be ignored.

Note: For more information on this Oracle error, see Oracle Metalink Article282036.1.


Verifying PATH and Environment for the Oracle login nameBefore proceeding to install Oracle files, make sure the /usr/ccs/bin directory is inthe PATH environment variable for the oracle login name.

About this task

To verify the PATH and environment:

Procedure1. Log in as oracle. Set and export the DISPLAY environment variable.

If you are using the su command to become oracle, use a hyphen as the secondargument so the oracle user login environment is loaded:# su - oracle

2. Verify that the environment variable ORACLE_BASE has been set by enteringthe following command:$ env | grep ORA

If the response does not include ORACLE_BASE=/opt/oracle, stop and make surethe .profile file was set for the oracle user, as described in “Run the Oracleclient configuration script” on page 115.

3. To verify the path, enter the following command:$ echo $PATH

The output must show that /usr/ccs/bin is part of the search path. Forexample:

/usr/bin:/opt/oracle/product/12.1.0/bin:/usr/ccs/bin

a. If this directory is not in the path, add it by entering the followingcommands:$ PATH=$PATH:/usr/ccs/bin$ export PATH

Set the ORACLE_SID variableA system identifier (SID) identifies each Oracle database instance for internalconnectivity on the Oracle server itself. (Connectivity from Oracle Clients to theserver is controlled by the TNS names system configured later.) The environmentvariable for the system identifier is ORACLE_SID.

About this task

Decide on an SID to use for your Tivoli Netcool Performance Manager databaseinstance. The assumed default for the Tivoli Netcool Performance Managerinstallation is PV. IBM recommends using this default SID unless your site hasestablished Oracle SID naming conventions.

To set the ORACLE_SID environment variable:

Procedure1. Log in as oracle.2. Open the .profile file with a text editor.3. Add the following line anywhere between the Begin and End Oracle Settings

comment lines:ORACLE_SID=PV; export ORACLE_SID


For example:# -- Begin Oracle Settings --umask 022ORACLE_BASE=/opt/oracleORACLE_HOME=/opt/oracle/product/12.1.0ORACLE_SID=PV; export ORACLE_SIDNLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/dataLD_LIBRARY_PATH=$ORACLE_HOME/libTNS_ADMIN=$ORACLE_HOME/network/adminPATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/delphi/binEXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.soexport PATH ORACLE_BASE ORACLE_HOME NLS_LANGexport ORA_NLS33 LD_LIBRARY_PATH TNS_ADMINexport EXTPROC_DLLS# -- End Oracle Settings --

4. Save and exit the .profile file.5. Enter the following shell command to activate the change to your profile:

$ . ./.profile

6. Make sure the variable was set by entering the following command:$ env | grep ORACLE_SID

Installing Oracle by using the menu-based scriptTo install the Oracle database files by using a menu-based system.

Before you begin

Add the following group to the oraInst.loc file.

From /etc/oraInst.loc, add:

inst_group=oinstall

From /etc/oraInst.loc, add:inst_group=oinstall

From /var/opt/oracle/oraInst.loc, add:inst_group=oinstall

About this task

It is recommended that you use the menu-based script method.

Note: The Oracle installation script that is provided by IBM is used to installOracle server, Oracle client, and upgrade patches to an existing Oracle server orClient installation.

To install the Oracle server (64-bit) using the menu-based script:

Procedure1. As Oracle, change directory by using the following command:

systems:


systems:


# cd <DIST_DIR>/proviso/AIX/DataBase/AIX<version_num>/oracle/instance/ora_installer

systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL<version_num>/oracle/instance/ora_installer

where:<DIST_DIR> is the directory on the hard disk drive where you copied thecontents of the Tivoli Netcool Performance Manager distribution in“Download the Oracle distribution to disk” on page 115.

2. Enter the following command to start the installer:$ ./perform_oracle_inst

The installation menu is displayed:

--------------------------------------------------perform_oracle_instInstallation of oracle binaries<Current Date>--------------------------------------------------OS ........... : [ Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 ]Host ......... : [ tnpmuslnx0110.myhost.example.com ]Logname ...... : [ oracle ]Install Oracle release .... : [ 12.1.0 ]Installation type.......... : [ Server ]Enter the appropriate letter to modify the entries below:a) ORACLE_BASE .. : [ /opt/oracle ]b) ORACLE_HOME .. : [ /opt/oracle/product/12.1.0 ]c) DBA group ..................... : [ dba ]d) OUI Inventory group ........... : [ oinstall ]e) Oracle Software owner ......... : [ oracle ]f) Directory where CDs were copied:[ <ORA_DIST_DIR> ]Menu :1. Next supported release2. Set install type to: Client3. Perform install0. ExitChoice :

3. Verify the following settings:v The Oracle release number is 12.1.0.v The Installation type field is Server.This field cycles between three settings: Server, Client, and Patch. Type 2 atthe Choice prompt and press Enter until Server is displayed.

4. Type f at the Choice prompt and press Enter.5. At the Choice prompt, enter the full path to the directory that contains the

installation files, <ORA_DIST_DIR>. For example:

Choice: fEnter new value for CD directory: /var/tmp/oracle12102

6. Type a at the Choice prompt and press Enter.7. At the Choice prompt, enter the full path to the oracle base directory created

for Oracle 12.1.0.2. The default is /opt/oracle.8. Type b at the Choice prompt and press Enter.9. At the Choice prompt, enter the full path to the oracle home directory created

for Oracle 12.1.0.2. The default is /opt/oracle/product/12.1.0.10. Edit other menu settings as required. For example, if you used non-default

values for ORACLE_BASE or ORACLE_HOME, enter your settings until the menushows that they correctly point to the directories created for Oracle 12.1.0.2.


11. To begin the Oracle installation, type 3 at the Choice prompt and press Enter.The installation script checks the environment, then asks if you want toperform the installation.

12. Type Y at the Choice prompt and press Enter. The installation script startsinstalling Oracle and displays a series of status messages.

Note: You can safely ignore any font.properties not found messages in theoutput.When the installation reaches the In Summary Page stage, the installationslows down significantly while Oracle files are copied and linked.

13. The following message is displayed when the installation completes:

In End of Installation PageThe installation of Oracle12c Database was successful.Check /opt/oracle/oraInventory/logs/silentInstall2011-09-28_04-23-53PM.logfor more details.The Oracle installation has completed. Check themessages above to determine if the install completedsuccessfully. If you do not see successful completionmessages, consult the install log at:/opt/oracle/oraInventory/logsPress C to continue...

Note: For any installation error, write down the log file location to aid introubleshooting.

14. Type C and press Enter to return to the installation menu.15. Type 0 and press Enter to exit the installation menu.

What to do next

Note: Review the Oracle installation logs at $ORACLE_BASE/oraInventory/logs forerrors as some fatal errors might be reported in the log, but the native Oracleinstaller reports success in standard output.

Run the root.sh scriptAfter successfully running an Oracle client or server installation, you must run theroot.sh script.

About this task

This step is also required after an Oracle patch installation. See “Verify the requiredoperating system packages” on page 100.

To run the root.sh script:

Procedure1. Log in as root or become superuser. Set the DISPLAY environment variable.2. Change to the directory where Oracle server files were installed. (This is the

directory as set in the ORACLE_HOME environment variable.) For example:# cd /opt/oracle/product/12.1.0

3. Run the following command:./root.sh

Messages like the following are displayed:


Running Oracle12c root.sh script...# ./root.shCheck /opt/oracle/product/12.1.0/install/root_<server_hostname>_2014-03-18_13-45-04.log for the output of root script

File contents:Performing root user operation for Oracle 12c

The following environment variables are set as:ORACLE_OWNER= oracleORACLE_HOME= /opt/oracle/product/12.1.0

Entries will be added to the /etc/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root script.Now product-specific root actions will be performed.Finished product-specific root actions.

Set automatic startup of the database instanceYou must configure your Oracle host to automatically start the Tivoli NetcoolPerformance Manager database instance at system startup time.

About this task

To set up automatic startup:

Procedure1. Log in as oracle.2. Depending on your operating system, change to the following directory:

systems:

$ cd /var/opt/oracle

systems:$ cd /etc

systems:$ cd /etc

3. Edit the oratab file with a text editor. The last line of this file looks like thisexample:

*:/opt/oracle/product/12.1.0:N

4. Make the following edits to this line:v Replace * with $ ORACLE_SID (PV by default).v Replace N with Y.The last line must now be:

PV:/opt/oracle/product/12.1.0:Y

5. Save and close the oratab file.


Configure the Oracle listenerHow to configure the Oracle Listener.

About this task

Note: Instead of creating the listener.ora file manually, as described in the stepsthat follow, you can create it by running the Oracle Net Configuration Assistantutility. See the Oracle Corporation documentation for information about NetConfiguration Assistant.

The Oracle Listener process manages database connection requests from Oracleclients to an Oracle server.

To configure the Oracle Listener:

Procedure1. Log in as oracle.2. Change to one of the following directories:

$ cd $TNS_ADMIN

or$ cd /opt/oracle/product/12.1.0/network/admin

3. Copy the sample listener.ora contained in the /opt/oracle/admin/skeleton/bin directory:

$ cp /opt/oracle/admin/skeleton/bin/template.example_tnpm.listener.ora listener.ora

Note: By Oracle convention, the keywords in this file are in uppercase butuppercase is not required.# listener.ora network configuration file in directory# /opt/oracle/product/12.1.0/network/admin

LISTENER =(DESCRIPTION_LIST =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP) (HOST = {HOST}) (PORT = 1521))

)(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC)))

))

SID_LIST_LISTENER =(SID_LIST =(SID_DESC =

(SID_NAME = PLSExtProc)(ORACLE_HOME = /opt/oracle/product/12.1.0)(PROGRAM = extproc)

)(SID_DESC =

(GLOBAL_DBNAME = PV.WORLD)(SID_NAME = PV)(ORACLE_HOME = /opt/oracle/product/12.1.0)

))

4. Using a text editor, change the following:a. Replace the string yourhost in the line (HOST = yourhost) with the name of

your Oracle server.


Note: Specify the host using the hostname only, do not use the IP address.b. You also need to edit the file with SID and Oracle Home directory.c. (optional) Replace the default port number 1521 in the line (PORT =1521 )

with your required port number.d. Write and quit the file.

5. Depending on your operating system, change to the following directory:

systems:$ cd /var/opt/oracle

systems:$ cd /etc

systems:$ cd /etc

6. Edit the lsnrtab file and add a line in the following format to the end of thefile (after the initial comments):LISTENER:value_of_ORACLE-HOME:Y

For example:LISTENER:/opt/oracle/product/12.1.0:Y

In this syntax, LISTENER is the name of the listener process.7. Write and quit the file.8. Test that the listener process works correctly by starting it manually using the

following command:lsnrctl start

(The lsnrctl command also accepts the stop and status arguments.) Look fora successful completion message.

Configure the Oracle net clientYou must configure an Oracle Net client by setting up the TNS (Transport NetworkSubstrate) service names for your Tivoli Netcool Performance Manager databaseinstance.

About this task

To set up the TNS service names

Procedure1. Log in as oracle.2. Change to one of the following directories:

$ cd $TNS_ADMIN

or$ cd /opt/oracle/product/12.1.0/network/admin

3. Create the sqlnet.ora file, which will manage Oracle network operations. Youmust create an sqlnet.ora file for both Oracle server and Oracle clientinstallations. Follow these steps:a. Copy the sample sqlnet.ora file, template.example_tnpm.sqlnet.ora,

contained in the opt/oracle/admin/skeleton/bin/ directory:$ cp /opt/oracle/admin/skeleton/bin/template.example_tnpm.sqlnet.ora sqlnet.ora

b. Add the following lines to this file:


NAMES.DIRECTORY_PATH=(TNSNAMES)NAMES.DEFAULT_DOMAIN=WORLDSQLNET.ALLOWED_LOGON_VERSION_CLIENT=8SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

For example:# sqlnet.ora network configuration file in# /opt/oracle/product/12.1.0/network/adminNAMES.DIRECTORY_PATH=(TNSNAMES)NAMES.DEFAULT_DOMAIN=WORLDSQLNET.ALLOWED_LOGON_VERSION_CLIENT=8SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

Note: If you do not use WORLD as the DEFAULT_DOMAIN value, makesure you enter the same value for DEFAULT_DOMAIN in both sqlnet.oraand tnsnames.ora.

c. Write and quit the sqlnet.ora file.d. Restart the listener process using the following command:

lsnrctl stop

lsnrctl start

Look for a successful completion message.4. Create the tnsnames.ora file, which maintains the relationships between logical

node names and physical locations of Oracle Servers in the network. You cando this by copying the existing sample file:cp /opt/oracle/admin/skeleton/bin/template.example_tnpm.tnsnames.ora tnsnames.ora

Follow these steps:a. Enter lines similar to the following example, using the actual name of your

Oracle server in the HOST=delphi line and replacing {SID} with PV or yourOracle SID.# tnsnames.ora network configuration file in# /opt/oracle/product/12.1.0/network/admin## The EXTPROC entry only needs to exist in the# tnsnames.ora file on the Oracle server.# For Oracle client installations, tnsnames.ora# only needs the PV.WORLD entry.EXTPROC_CONNECTION_DATA.WORLD =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS =(PROTOCOL = IPC)(KEY = EXTPROC)

))(CONNECT_DATA = (SID = PLSExtProc)(PRESENTATION = RO)

))

PV.WORLD =(DESCRIPTION =(ENABLE=BROKEN)(ADDRESS_LIST =

(ADDRESS =(PROTOCOL = TCP)(HOST = delphi)

(PORT = 1521))

)(CONNECT_DATA =


(SERVICE_NAME = PV.WORLD)(INSTANCE_NAME = PV)

))

Note: Indents in this file must be preserved.Note the following:v You can use the value in the INSTANCE_NAME field as the TNS entry

when installing Tivoli Netcool Performance Manager DataMart.v IBM strongly recommends that you include the line (ENABLE=BROKEN)

in the PV.WORLD entry, as shown in the example. This parameter settingprevents CME processes from hanging in the event that the CME isdisconnected from the database before results are returned to the CME.

v If configuring tnsnames.ora for a server installation, be sure to appendthe same domain suffix to all entries including EXTPROC_CONNECTION_DATAthat you specified for the NAMES.DEFAULT_DOMAIN entry in thesqlnet.orafile. That is, append.WORLD to each entry.

b. Write and quit the file.5. Test the Oracle Net configuration by entering a command with the following

syntax:tnsping Net_service_name.domain 10

For example:$ tnsping PV.WORLD 10

Look for successful completion messages (OK).To test without using the domain suffix, enter a command with the followingsyntax:tnsping Net_service_name 10

For example:$ tnsping PV 10

Note: If either test is not successful, check your configuration and retest.

Installing Oracle 12.1.0.2 client 32-bit

Instructions on how to install the Oracle 12.1.0.2 client (32-bit).

The deployer and Topology Editor use Oracle 12.1.0.2 client (32-bit). The deployermust run on the Host DB server. Therefore, in the Tivoli Netcool PerformanceManager, Oracle 12.1.0.2 client (32-bit) must be installed.

You must specify a different directory path for the Oracle 12.1.0.2 client (32-bit)from the directory specified when installing the Oracle 12.1.0.2 server. For example,assuming that Oracle 12.1.0.2 server is installed in /opt/oracle/product/12.1.0then you must install the Oracle 12.1.0.2 client (32-bit) in /opt/oracle/product/12.1.0-client32.

You must install Oracle client 32-bit on all machines except for the server thathosts the Tivoli Netcool Performance Manager database server. Should there beanother Tivoli Netcool Performance Manager component on the server hosting theTivoli Netcool Performance Manager database server, the client must also beinstalled on that server, having a separate ORACLE_HOME for both Oracle clientand server.


Download the Oracle distribution to diskThe Oracle installation files must be in place before you can begin the installationof Oracle.

About this task

Note: Oracle 12.1.0.2 client (32-bit) must be installed into a new ORACLE_HOME.

Procedure1. Log in as root.2. Set the DISPLAY environment variable.3. Create a directory to hold the contents of the Oracle distribution. For example:

# mkdir /var/tmp/oracle12102

4. Download the Oracle files to the /var/tmp/oracle12102 directory.5. Extract the Oracle distribution files that now exist in the /var/tmp/oracle12102

directory.

6. Create a soft link for the client32 folder from theOracle distribution files directory:# cd /var/tmp/oracle12102# ln -s client32 client

Results

The directory created and to which the Oracle 12.1.0.2 distribution is downloadedfrom now on be referred to by using <ORA_DIST_DIR>.

Before beginning this task, make sure that you have:v Downloaded the Tivoli Netcool Performance Manager distribution to disk.

The directory that is created and to which the Tivoli Netcool PerformanceManager distribution is downloaded from now on be referred to by using<DIST_DIR>.

What to do next

Before you proceed to the next step, make sure that you obtain the upgradeinstructions provided by Oracle. The instructions contain information onperforming steps that are required for the upgrade that are not documented in thisguide.

See your database administrator to determine whether there are anycompany-specific requirements for installing Oracle in your environment.

Run the Oracle client configuration scriptThe Oracle client configuration shell script creates the environment for the clientsoftware installation on the local system.

About this task

This script is named configure_client and is located with the Tivoli NetcoolPerformance Manager files downloaded as part of the Tivoli Netcool PerformanceManager distribution. If you are performing this step as part of an upgrade


procedure, make sure that you run the configuration script provided with thetarget version of Tivoli Netcool Performance Manager.

The client configuration script makes the following changes to the local system:v Adds the dba and oinstall groups to /etc/group.v Adds the Solaris login name oracle, whose primary group membership is dba,

and secondary group membership is oinstall.

Note: You must use the same Oracle username across all instances of OracleClient and Server throughout your Tivoli Netcool Performance Manager system.

v Creates the Oracle client directory structure. When you create the environmentfor Oracle 12.1.0.2, the default location for this directory structure is/opt/oracle/product/12.1.0-client32. You specify this directory as the targetlocation when you install the Oracle client.

Note: None of the above changes are made if the changes are already in place.

To configure the Oracle installation environment:

Procedure1. Log in as root.2. Set the ORACLE_BASE environment variable to point to the top-level directory

where you want the Oracle client files installed. The default installationdirectory is /opt/oracle.For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE

Note: The configure_client script places this variable into the oracle loginname's .profile file.To check that the variable is set correctly, enter the following command:# env | grep ORA

3. Set the ORACLE_HOME environment variable. For example:# ORACLE_HOME=/opt/oracle/product/12.1.0-client32# export ORACLE_HOME

Note: The value defined in the configure_client script for ORACLE_HOME is thevalue needed in the Topology Editor for Oracle Home on the host level.

4. Change to the following directory:

systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/oracle/instance

systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX<version_num>/oracle/instance

systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL<version_num>/oracle/instance


5. Run the Oracle configuration script using the following command:


# ./configure_client

The following screen is displayed:

--------------------------------------------------configure_client

Setting the Oracle client environmentTue Dec 6 14:51:23 CST 2011

--------------------------------------------------OS ........... : [ SunOS 5.10 Generic_141444-09 ]Host ......... : [ l3provsol1z3 ]Logname ...... : [ root ]

ORACLE_BASE .. : [ /opt/oracle ]ORACLE_HOME .. : [ /opt/oracle/product/12.1.0-client32]DBA group ................. : [ dba ]OUI Inventory group ....... : [ oinstall ]Oracle Software owner ..... : [ oracle ]

Configure Oracle release .. : [12.1.0]

Menu :1. Modify Oracle software owner.2. Next supported release.3. Check environment.0. Exit

Choice :

6. Type 3 at the Choice prompt and press Enter.The script creates the dba and oinstall groups, and the ORACLE_BASE directory,unless they already exist.

Checking environment...Checking for group [ dba ] --> Created.Checking for group [ oinstall ] --> Created.Checking ORACLE_BASE

** WARNING** ORACLE_BASE directory does not exist.** [ /opt/oracle ]**** Create it ? (n/y) y

If prompted, type y and press Enter.The script creates the /opt/oracle directory and continues as follows:

Checking for user [ oracle ]** WARNING** User [ oracle ] does not exist.**** Create it locally ? (n/y) y

If prompted, type y to create the oracle user and press Enter.The script creates the oracle user and continues as follows:

--> Created.Checking for oracle directory tree :

[ /opt/oracle/product ] --> Created.[ /opt/oracle/product ] --> Created.[ /opt/oracle/product/12.1.0 ] --> Created.

Checking for oracle .profile file --> Created.

Press Enter to continue...

7. Press Enter to continue. The configure_client main screen is displayed.8. Type 0 and press Enter to exit the script.


What to do next

Note: Install database step fails during deployment if permission to the$ORACLE_BASE directory is not granted. During Oracle installation, the /opt/oraclefolder that is created by configure_client script has no permission that is grantedto any other users. Therefore, after you run the configure_client script, assign thefollowing permission to the $ORACLE_BASE directory (for example, /opt/oracle):1. Log in as oracle user.2. Run the following command:

chmod 755 /opt/oracle

Setting a password for the Oracle login nameYou must assign a password for the oracle login name to maintain systemsecurity.

About this task

The configure_ora script that you ran in the previous section creates the oraclelogin name. You must assign a password for the oracle login name to maintainsystem security, and because subsequent installation steps expect the password tobe already set.

To set a password:

Procedure1. Log in as root.2. Enter the following command:

# passwd oracle

3. Enter and reenter the password (oracle, by default) as prompted. Thepassword is set.

Run the preinstallation scriptRun the preinstallation script to verify your readiness to install Oracle.

Procedure1. As root, change directory using the following command:

systems:





2. Set the ORACLE_BASE environment variable. For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE


Note: You must use the same ORACLE_BASE setting that you specified in“Run the Oracle server configuration script”.

3. Enter the following command:# ./pre_install_as_root

The following messages indicate success:

Checking that you are logged in as root --> Ok.Checking ORACLE_BASE --> Ok.Checking oraInst.loc file --> Ok.

If the script shows an error, correct the situation causing the error beforeproceeding to the next step.

Verifying PATH and Environment for the Oracle login nameBefore proceeding to install Oracle files, make sure the /usr/ccs/bin directory is inthe PATH environment variable for the oracle login name.

About this task

To verify the PATH and environment:

Procedure1. Log in as oracle. Set and export the DISPLAY environment variable.

If you are using the su command to become oracle, use a hyphen as the secondargument so the oracle user login environment is loaded:# su - oracle

2. Verify that the environment variable ORACLE_BASE has been set by enteringthe following command:$ env | grep ORA

If the response does not include ORACLE_BASE=/opt/oracle, stop and make surethe .profile file was set for the oracle user, as described in “Run the Oracleclient configuration script” on page 115.

3. To verify the path, enter the following command:$ echo $PATH

The output must show that /usr/ccs/bin is part of the search path. Forexample:

/usr/bin:/opt/oracle/product/12.1.0/bin:/usr/ccs/bin

a. If this directory is not in the path, add it by entering the followingcommands:$ PATH=$PATH:/usr/ccs/bin$ export PATH


Installing the Oracle client (32-bit)The Oracle installation script is a shell script that you can use to install the Oracleserver, Oracle client software, or patches to existing installations of the Oracleserver and client.

Before you begin

Add the following group to the oraInst.loc file.

From /etc/oraInst.loc, add:

inst_group=oinstall

From /etc/oraInst.loc, add:inst_group=oinstall

From /var/opt/oracle/oraInst.loc, add:inst_group=oinstall

About this task

This script is named perform_oracle_inst and is located with the Tivoli NetcoolPerformance Manager files that you obtained in “Download the Oracle distributionto disk” on page 115. This script is provided by IBM as part of the Tivoli NetcoolPerformance Manager installation package.

An Oracle client installation is not usable until the following Net configurationfiles are configured and installed:v tnsnames.ora

v sqlnet.ora

These files are configured in later steps.

To install the Oracle client:

Procedure1. Log in as oracle.2. Change to the following directory:

systems:




Where:v <DIST_DIR> is the directory on the hard disk drive where you copied the

contents of the Tivoli Netcool Performance Manager distribution in“Download the Oracle distribution to disk” on page 115.

3. Enter the following command to start the installer:


$ ./perform_oracle_inst

The installation menu is displayed:

--------------------------------------------------perform_oracle_instInstallation of oracle binariesTue Jun 18 10:42:54 PDT 2013

--------------------------------------------------OS ........... : [ Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 ]Host ......... : [ tnpmuslnx0110.persistent.co.in ]Logname ...... : [ oracle ]

Install Oracle release .... : [ 12.1.0]Installation type.......... : [ Client ]

Enter the appropriate letter to modify the entries below:

a) ORACLE_BASE .. : [ /opt/oracle ]b) ORACLE_HOME .. : [ /opt/oracle/product/12.1.0-client32 ]c) DBA group ..................... : [ dba ]d) OUI Inventory group ........... : [ oinstall ]e) Oracle Software owner ......... : [ oracle ]f) Directory where CDs were copied:

[ ]Menu :

1. Next supported release2. Set install type to: Client3. Perform install0. Exit

Choice :

Note:

a. The ORACLE_HOME must match the ORACLE_HOME set in the deployer for theserver on which the client is being installed.

b. Make sure the listener process is down before you start installing Oracle12.1.0.2 client (32-bit).

4. Enter f at the Choice prompt and press Enter.5. Enter the full path to the <ORA_DIST_DIR>, as created in “Download the

Oracle distribution to disk” on page 115. For example:

Choice: fEnter new value for CD directory: /var/tmp/oracle12102

6. Edit any other menu settings as necessary. Make sure that the values forORACLE_BASE and ORACLE_HOME correspond to the locations you specified whenyou ran the Oracle client configuration script.

7. To start the Oracle installation, type 3 at the Choice prompt and press Enter.8. The installation script checks the environment, then asks whether you want to

perform the installation. Type Y at the Choice prompt and press Enter. Theinstallation script starts installing Oracle and displays a series of statusmessages.

Note: You can safely ignore any font.properties not foundmessages in theoutput.When the installation reaches the In Summary Page stage, the installationslows down significantly while Oracle files are copied and linked.

9. On AIX, you are asked if the script named rootpre.sh is run.To run this script:a. Open another window.


b. Log in as root.c. cd to /var/tmp/oracle12102/database/rootpred. run rootpre.she. Then, answer Y to the installation script.

10. When the installation process is finished, the installation displays a successmessage. Write down the log file location to aid in troubleshooting if there isan installation error.

11. Type C and press Enter to return to the installation menu.12. Type 0 and press Enter to exit the installation menu.13. Perform the steps in “Run the root.sh script” on page 109.

Run the root.sh scriptAfter successfully running an Oracle client or server installation, you must run theroot.sh script.

About this task

This step is also required after an Oracle patch installation. See “Verify the requiredoperating system packages” on page 100.

To run the root.sh script:

Procedure1. Log in as root or become superuser. Set the DISPLAY environment variable.2. Change to the directory where Oracle client files were installed. (This is the

directory as set in the ORACLE_HOME environment variable.) For example:# cd /opt/oracle/product/12.1.0-client32

3. Run the following command:./root.sh

Messages like the following are displayed:

Running Oracle12c root.sh script...# ./root.shCheck /opt/oracle/product/12.1.0-client32/install/root_<server_hostname>_2014-03-18_13-45-04.log for the output of root script

File contents:Performing root user operation for Oracle 12c

The following environment variables are set as:ORACLE_OWNER= oracleORACLE_HOME= /opt/oracle/product/12.1.0-client32

Entries will be added to the /etc/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root script.Now product-specific root actions will be performed.Finished product-specific root actions.


Updating the Oracle user's .profileModify the oracle user's .profile file.

Procedure1. On the primary host server that hosts the Tivoli Netcool Performance Manager

database server, make sure that ORACLE_HOME points to $ORACLE_BASE/product/12.1.0.

2. On the secondary host servers, that hosts any of the Tivoli Netcool PerformanceManager components, make sure that ORACLE_HOME points to$ORACLE_BASE/product/12.1.0-client32.

3. If there is not already an entry for TNS_ADMIN, add one.TNS_ADMIN=$ORACLE_HOME/network/admin

When complete, the .profile must look similar to:

# -- Begin Oracle Settings --

umask 022

ORACLE_BASE=/opt/oracleORACLE_HOME=$ORACLE_BASE/product/12.1.0NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/dataLD_LIBRARY_PATH=$ORACLE_HOME/libTNS_ADMIN=$ORACLE_HOME/network/adminPATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/local/binEXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.so

export PATH ORACLE_BASE ORACLE_HOME NLS_LANGexport ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN EXTPROC_DLLS

ORACLE_SID=PVExport ORACLE_SID

# -- End Oracle Settings --

4. Source the .profile file to apply the changes by using the following command:$ cd /opt/oracle.$ ./.profile

Configuring the Oracle Net clientYou must configure the Oracle Net client by setting up the TNS (TransportNetwork Substrate) service names for your Tivoli Netcool Performance Managerdatabase instance.

About this task

Next, you configure the Oracle Net client by setting up the TNS (TransportNetwork Substrate) service names for your Tivoli Netcool Performance Managerdatabase instance. You must perform this step for each instance of the Oracle clientsoftware that you installed on the system.

Procedurev You must configure sqlnet.ora and tnsnames.ora files for both Oracle server

and Oracle client installations. However, the tnsnames.ora file for clientinstallations must not have the EXTPROC_CONNECTION_DATA section.

v If you are installing DataView and one or more other Tivoli NetcoolPerformance Manager components on the same system, you must make surethat the tnsnames.ora and sqlnet.ora files for each set of client software are


identical. The easiest way to do this is to create these files when you areconfiguring the first client instance for Net and then to copy it to thecorresponding directory when you configure the second instance.

Creating the sqlnet.ora fileThe sqlnet.ora file manages Oracle network operations. You can create a newsqlnet.ora file, or FTP the file from your Oracle server.

About this task

To set up the TNS service names:

Procedure1. Log in as oracle.2. Change the directory to Oracle 12.1.0.2 client (32-bit):

$ cd /opt/oracle/product/12.1.0-client32/network/admin

3. Create the sqlnet.ora file, which manages Oracle network operations. Youmust create an sqlnet.ora file for both Oracle server and Oracle clientinstallations. Follow these steps:a. Copy the sqlnet.ora file that was created earlier during the configuration

of oracle server net client, from /opt/oracle/product/12.1.0/network/admindirectory.$ cp /opt/oracle/product/12.1.0/network/admin/sqlnet.ora .

b. Add the following lines to this file:NAMES.DIRECTORY_PATH=(TNSNAMES)NAMES.DEFAULT_DOMAIN=WORLDSQLNET.ALLOWED_LOGON_VERSION_CLIENT=8SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

For example:# sqlnet.ora network configuration file in# /opt/oracle/product/12.1.0/network/adminNAMES.DIRECTORY_PATH=(TNSNAMES)NAMES.DEFAULT_DOMAIN=WORLDSQLNET.ALLOWED_LOGON_VERSION_CLIENT=8SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

Note: If you do not use WORLD as the DEFAULT_DOMAIN value, make sure thatyou enter the same value for DEFAULT_DOMAIN in both sqlnet.ora andtnsnames.ora.

c. Write and quit the sqlnet.ora file.d. Restart the listener process by using the following commands:

lsnrctl stop

lsnrctl start

Look for a successful completion message.

Creating the tnsnames.ora fileThe tnsnames.ora file maintains the relationships between logical node names andphysical locations of Oracle servers in the network.


About this task

You can create a new tnsnames.ora file, or FTP the file from your Oracle server.

To create the tnsnames.ora file:

Procedure1. FTP the following file from your Oracle server:

/opt/oracle/admin/skeleton/bin/template.example_tnpm.tnsnames.ora

2. Add the following lines:# tnsnames.ora network configuration file in# /opt/oracle/product/12.1.0/network/admin## For Oracle client installations, tnsnames.ora# only needs the PV.WORLD entry.PV.WORLD =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS =(PROTOCOL = TCP)(HOST = yourhost)(PORT = 1521)

))(CONNECT_DATA =

(SERVICE_NAME = PV.WORLD)(INSTANCE_NAME = PV)

))

Note: Indents in this file must be preserved.3. Replace the string yourhost in the line (HOST = yourhost) with the name of

your Oracle server.Note the following:v You can use the value in the INSTANCE_NAME field as the TNS entry

when installing DataMart.v If you reconfigure the Oracle client to connect to a different Oracle database

in another Tivoli Netcool Performance Manager installation, be sure that youupdate the HOST entry in the tnsnames.ora file, then restart the Oracleclient.

v Specify the host by using the hostname only, do not use the IP address.4. (optional) Replace the default port number 1521 in the line (PORT = 1521) with

your required port number.5. Write and quit the file.Tivoli Netcool Performance Manager non-default installation6. For a non-default Tivoli Netcool Performance Manager installation, where

oracle is installed with a non-default parameter, add the following lines.For example, ORACLE_SID is set to PVR during oracle installation. Thetnsnames.ora file must have the following entries.

# tnsnames.ora network configuration file in# /opt/oracle/product/12.1.0/network/admin

PV.WORLD =(DESCRIPTION =(ENABLE=BROKEN)(ADDRESS_LIST =(ADDRESS =


(PROTOCOL = TCP)(HOST = yourhost)(PORT = 1521)))(CONNECT_DATA =(SERVICE_NAME = PVR.WORLD)(INSTANCE_NAME = PVR)))

PVR.WORLD =(DESCRIPTION =(ENABLE=BROKEN)(ADDRESS_LIST =(ADDRESS =(PROTOCOL = TCP)(HOST = yourhost)(PORT = 1521))

)(CONNECT_DATA =(SERVICE_NAME = PVR.WORLD)(INSTANCE_NAME = PVR)

))

7. Write and quit the file.

Testing the Oracle net configurationThe steps required to test the Oracle Net configuration.

About this task

To test the Oracle Net configuration:

Procedure1. Log in as oracle.2. Enter a command with the following syntax:

tnsping Net_service_name 10

For example: tnsping PV.WORLD 103. Test again, using the same Net instance name without the domain suffix:

tnsping PV 10

Look for successful completion messages (OK).

Testing the 32-bit SQLPlusMemory fault might cause proviso database installation to fail. Run the followingsteps to test the Oracle client 32-bit SQLPlus.

About this task

To avoid the memory fault issue, run the following steps:

Procedure1. Log in as root.2. Set the environment variable to # ORACLE_HOME=/opt/oracle/product/12.1.0-

client32

3. Run the SQLPlus by using the sqlplus from the Oracle 32-bit client version. Forexample:


/opt/oracle/product/12.1.0-client32/bin/sqlplus

If the SQL login prompt returns, it should not cause any memory fault issueduring proviso database installation.

4. If a segmentation or memory fault occurs, create a zero length file under thefollowing path: /etc/sysconfigFor example:touch /etc/sysconfig/64bit_strstr_via_64bit_strstr_sse2_unaligned

5. Rerun step 3 to ensure that you are not hitting any memory fault issues.

Installing DB2® 11.1.1.1 (64-bit)The DB2® Server 11.1.0 (64-bit) provides both 64-bit and 32-bit libraries.

To install IBM DB2 Advanced Workgroup Server Edition 11.1.1.1, Linux 64-bit,youfirst will need to install DB2 11.1.0 and update your database to DB2 11.1 Fix pack1.

Note: You need not install the DB2 client on Tivoli Netcool Performance ManagerDatabase server. However, DB2 client is required on every other host where youwant to install the Tivoli Netcool Performance Manager components.

Overview of IBM DB2 Advanced Workgroup Server Edition11.1.1.1, Linux 64-bit installation

The following steps gives you an overview of a typical scenario of DB2 databaseinstallation on a stand-alone environment.1. Download the following installation files to your local directory according to

your environment setup.v IBM DB2 Advanced Workgroup Server Edition 11.1.0.0, Linux 64-bitv Special Build 36118 for IBM DB2 11.1.1 Fix Pack 1 for Linux/x86-64v IBM Data Server Client V11.1.1 Fix Pack 1

2. Ensure that your system meets the necessary operating system, hardware,software, communications, disk and memory requirements for DB2 AdvancedWorkgroup Server Edition 11.1.0.0.

3. Install DB2 Advanced Workgroup Server Edition 11.1.0.0.a. Perform post DB2 Advanced Workgroup Server Edition 11.1.0.0 installation

configurations.b. Apply the Special Build 36118 for IBM DB2 11.1.1 Fix Pack 1 for

Linux/x86-64 (special_36118_DB2-linuxx64-universal_fixpack-11.1.1.1-FP001).

c. Perform post DB2 Server 11.1.1.1 installation configurations.4. Install DB2 11.1.1.1 Client.

a. Perform post DB2 11.1.1.1 Client installation configurations.Related information:

Fix Central


https://www-945.ibm.com/support/fixcentral

Installing DB2 Server 11.1.1.1 (64-bit)

About this task

Instructions on how to install the DB2 Server 11.1.1.1 (64-bit).Related information:

DB2 database product documentation

Download the IBM® DB2® 11.1.0 distribution to diskThe DB2 installation files must be in place before you begin the installation of DB2.

Procedure1. Log in as root.2. Set the DISPLAY environment variable.3. Create a directory to hold the contents of the DB2 distribution. For example:

# mkdir /var/tmp/db2setup1110

4. Download the DB2 files to the /var/tmp/db2setup1110 directory.5. Extract the DB2 distribution files that now exist in the /var/tmp/db2setup1110

directory.

What to do next

See your database administrator to determine whether there are anycompany-specific requirements for installing DB2 in your environment. Thedirectory created and to which the DB2 distribution is downloaded from now on isreferred as <DB2_DIST_DIR>.Related information:

DB2 Version 11.1 for Linux, UNIX, and Windows

Verifying the required operating system packagesBefore you install the DB2 server, make sure that all required packages areinstalled on your system.

Procedure1. Make sure all the required Linux packages are installed on your system. All

packages and patches are specified in the Requirements.2. If these packages are not on your system, see the relevant operating system

Installation Guide for instructions on installing supplementary packagesoftware.

Installing DB2 Advanced Workgroup Server Edition 11.1.0.0To start the DB2 Setup wizard, use these steps.

Procedure1. Change to the directory where the DB2 database product distribution is copied

by entering the following command:cd <DB2_DIST_DIR>

2. If you have downloaded the DB2 database product image, extract the productfile by using the following commands:




gunzip <product>.tar.gztar -xvf product.tar

Where product is the name of the product that you downloaded.3. Change directory to <DB2_DIST_DIR>/server.4. As a root user, start the DB2 installation by entering the following command:

./db2_install

Important: The db2_install command is deprecated and might be removed ina future release. In this release it works as expected.You see the following output:

./db2_install

Default directory for installation of products - /opt/ibm/db2/V11.1

***********************************************************Install into default directory (/opt/ibm/db2/V11.1) ? [yes/no]noEnter the full path of the base installation directory:

------------------------------------------------/opt/db2/product/11.1.0

Specify one of the following keywords to install DB2 products.

SERVERCONSVCLIENTRTCL

Enter "help" to redisplay product names.

Enter "quit" to exit.

***********************************************************SERVER******************************************************Do you want to install the DB2 pureScale Feature? [yes/no]no

DB2 installation is being initialized.

Total number of tasks to be performed: 58Total estimated time for all tasks to be performed: 1383 second(s)

Task #1 startDescription: Checking license agreement acceptanceEstimated time 1 second(s)Task #1 end

Task #2 startDescription: Base Client Support for installation with root privilegesEstimated time 3 second(s)Task #2 end......The execution completed successfully.

For more information see the DB2 installation log at"/tmp/db2_install.log.20295".

Note:


v You might see the following warning message in the DB2 install log after theDB2 installation completes. This warning message can be ignored.WARNING: DBI20105E An error occurred while installing the following file set:"TSAMP". Because these files were not successfully installed, functionalitythat depends on these files might not work as expected.

v The output above shows that the total number of tasks to be performed are58. But the installation log shows 59 tasks. This is a known limitation.

Results

DB2 Advanced Workgroup Server Edition 11.1.0.0 server is installed in/opt/db2/product/11.1.0 directory.

Setting up a DB2 instanceA DB2 instance is an environment in which you store data and run applications.

Before you begin

You must have root user authority.

Procedure

Use the db2icrt command to create an instance by using the following steps:

Run the following commands:cd /opt/db2/product/11.1.0/instance./db2icrt -u db2fenc db2

Updating /etc/services filePort usage is specified in the /etc/services file

Procedure

Ensure that the DB2_db2 service-name is using port 60000. If not, update thefollowing line in /etc/services file:DB2_db2 60000/tcp

Note: Here the DB2 port is hardcoded to use 60000 since the default DB2 portnumber 50000 is preoccupied by the DB2 that is installed with Jazz for ServiceManagement.

DB2 instance variable registry settingsProcedure1. Log in as db2 (instance user).2. Run the following commands to set listening port and communication protocol:

[db2@tnpminlnx0119 ~]$ db2 update dbm cfg using svcename 60000DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completedsuccessfully.[db2@tnpminlnx0119 ~]$ db2set db2comm=TCPIP


Starting the DB2 instance

Procedure1. Log in as db2 (instance user).2. Run the following commands to start the instance if it is not already running:

db2start

If instance is not running, then the command will start the instance. If it isalready running, then you may receive following message:The database manager is already active

3. Verify the installation of DB2 Advanced Workgroup Server Edition 11.1.0.0 issuccessful by running the command:

$ db2 connect to PV user PV_ADMIN using PVDatabase Connection Information

Database server = DB2/LINUXX8664 11.1.0.0SQL authorization ID = PV_ADMINLocal database alias = PV

4. Verify the DB2 server level by running the following command:$ db2levelDB21085I This instance or install (instance name, where applicable: "db2")uses "64" bits and DB2 code release "SQL11010" with level identifier "0201010F".Informational tokens are "DB2 v11.1.0.0", "special_35722","DYN1606081100AMD64_35722", and Fix Pack "0".

Product is installed at "/opt/db2/product/11.1.0".

Applying DB2 11.1 Fix pack 1IBM Tivoli Netcool Performance Manager, Version 1.4.3 requires your DB2®

database environment running at Fix pack1 level (DB2 11.1.1.1).

Before you beginv Ensure that you have installed DB2 Advanced Workgroup Server Edition

11.1.0.0, before proceeding to apply the fix pack.v Download the Special Build 36118 for IBM DB2 11.1.1 Fix Pack 1 for

Linux/x86-64 from Fix Central installation files to your local directory.For example, download the DB2 files to /var/tmp/db2setup1111_fp directory.The directory created and to which the DB2 Fix pack distribution is downloadedfrom now on is referred as <DB2_FP_DIST_DIR>.

About this task

Follow the instructions to apply a new fix pack level, Fix pack1, to your existingDB2 database product, DB2 Advanced Workgroup Server Edition 11.1.0.0. TheinstallFixPack command is used to install the fix pack.

Procedure1. Log in as root user.2. Run the db2prereqcheck command to check your system meets the

prerequisites for the installation of DB2 Server 11.1.1.1. For example, run thefollowing command:./db2prereqcheck -v 11.1.1.1 -s

DBT3533I The db2prereqcheck utility has confirmed that all installation prerequisiteswere met for DB2 database "server " "". Version: "11.1.1.1"


https://www-945.ibm.com/support/fixcentral

Stopping all DB2 processes3. Run the following command db2ilist, to determine which instance is

associated with the Tivoli Netcool Performance Manager DB2:$ /opt/db2/product/11.1.0/instance/db2ilistdb2

4. Log in as db2 instance user and run the following commands.

Note: There are daemons or applications which start automatically after issuingdb2 force application all command. To avoid any problem during DB2backup process, execute the backup command immediately after db2 forceapplication all command, as backup requires no application or daemon to berunning during the backup procedure.a. The following command is to stop any applications that are running for the

instance.For example:

$ su - db2

$ db2 list applicationAuth Id Application Appl. Application Id DB # of

Name Handle Name Agents--------- ------------------------ --------------- -------------------DB2 db2authDaemon 18 *LOCAL.db2.150415102229 PV 1DB2 db2authDaemon 8 *LOCAL.db2.150415102158 PV 1PV_COLL pvmd_3002 2909 *LOCAL.db2.150416095117 PV 1

$ db2 force applications allDB20000I The FORCE APPLICATION command completed successfully.DB21024I This command is asynchronous and may not be effective immediately.

b. Run the following command to back up the DB2 database: db2 backup db<DATABASE_NAME> to <PATH>.For example:$ db2 backup db PV to /tmp/

c. Run the following command to stop any applications that are running forthe instance.

$ db2 terminateDB20000I The TERMINATE command completed successfully.

$ db2stop force04/17/2015 14:47:37 0 0 SQL1064N DB2STOP processing was successful.SQL1064N DB2STOP processing was successful.

$ db2licd -end$ exit

5. On a new command prompt, log in as root and run the following commandsto disable and stop the Fault Monitor processes..Execute the following command to check if the Fault Monitor Daemon is upand running.$ ps -ef |grep db2fm

Execute the following commands to disable the Fault Monitor Coordinator(FMC), only if you see the entries for Tivoli Netcool Performance Manager DB2instance user. For example:$ /opt/db2/product/11.1.0/bin/db2fmcu -d

$/opt/db2/product/11.1.0/bin/db2fm -i db2 -D


6. Set the auto-start to off for the DB2 instance as db2 instance user. For example:

$ su - db2

$ /opt/db2/product/11.1.0/instance/db2iset -i db2 -allDB2_DEFERRED_PREPARE_SEMANTICS=YESDB2_COMPATIBILITY_VECTOR=ORADB2COMM=TCPIPDB2AUTOSTART=YES

$ /opt/db2/product/11.1.0/instance/db2iauto -off db2

7. Run the ipclean command to remove DB2 engine and client IPC resources fordb2.$ ipclean

Applying the fix pack8. Log in as root or the user that was used for the previous version of DB2

installation and run the installFixPack command to update the existinginstallation.For example:$ cd /var/tmp/db2setup1111_fp$ ./installFixPack -b /opt/db2/product/11.1.0

Note: Ensure that you specify /opt/db2/product/11.1.0 as your installationdirectory during the prompt.


Make sure that all the tasks are completed without any issues. After theinstallation completes, you will see “The execution completed succefully.”message.Check the installation log at /tmp/installFixPack.log.29417 for possibleerrors.

Note:

You might see the following warning message in the install fix pack log afterthe DB2 fix pack installation completes. This warning message can be ignored.WARNING: DBI20105E An error occurred while installing the following file set:"TSAMP". Because these files were not successfully installed, functionalitythat depends on these files might not work as expected.

Post-installation tasks for DB2 11.1 Fix pack 1:

As part the DB2 11.1.1.1 fix pack installation, you need to update the DB2 instancesand restart the DB2 instances.


About this task

Perform the following steps:

Procedure

1. Log in as root.2. Run the following command db2ilist, to determine which instance is

associated with the Tivoli Netcool Performance Manager DB2:$ /opt/db2/product/11.1.0/instance/db2ilistdb2

3. Run the following command db2iupdt, to update the instances.

Note: If you made any changes to the db2profile or db2cshrc scripts, eitherback up the scripts or copy the changes into the userprofile and usercshrcscripts, respectively.

$ /opt/db2/product/11.1.0/instance/db2iupdt db2DBI1446I The db2iupdt command is running.DB2 installation is being initialized.......The execution completed successfully.

4. Log in as the db2 instance owner and start the database by running thefollowing command.

$ db2start$ db2iauto -on db2

5. Verify the upgrade of DB2 11.1.1.1 is successful by running the db2levelcommand.

$ db2level

DB21085I This instance or install (instance name, where applicable: "db2")uses "64" bits and DB2 code release "SQL11011" with level identifier "0202010F".

Informational tokens are "DB2 v11.1.1.1", "special_36118","DYN1612051900AMD64_36118", and Fix Pack "1".Product is installed at "/opt/db2/product/11.1.1".

Installing IBM Data Server Client 11.1.1.1, Linux 64-bit (64-bit)

In a Tivoli Netcool Performance Manager system, you must install the Data ServerClient (64-bit) in a distributed environment only. It is not required in a stand-aloneenvironment. In a distributed environment, install the DB2 client software on eachserver where you plan to install a Tivoli Netcool Performance Manager component,except for the system where you installed the DB2 server.

About this task

Instructions on how to install the IBM Data Server Client 11.1.1.1, Linux 64-bit(64-bit).

Downloading the IBM Data Server Client 11.1.1.1, Linux 64-bitdistribution to diskThe DB2 installation files must be in place before you can begin the installation ofDB2.


About this task

DB2 client installation is performed on distributed environment only.

Procedure1. Log in as root.2. Create a directory to hold the contents of the Data Server Client distribution.

For example:# mkdir /var/tmp/db2setup1110

3. Download the Data Server Client files to the /var/tmp/db2setup1110 directory.4. Extract the Data Server Client distribution files that now exist in the

/var/tmp/db2setup1110 directory. The directory to which the IBM Data ServerClient 11.1.1.1, Linux 64-bit distribution is downloaded is referred to as<DB2_DIST_DIR>.


IBM Data Server Client V11.1.1 Fix Pack 1

Installing IBM Data Server Client (64-bit)To start the DB2 Setup wizard, use these steps.

Procedure1. Run the db2prereqcheck command to check your system meets the

prerequisites for the installation of DB2 Server 11.1.1.1. For example, run thefollowing command:./db2prereqcheck -v 11.1.1.1 -s

DBT3533I The db2prereqcheck utility has confirmed that all installation prerequisiteswere met.

2. Change to the directory where the DB2 Client database product distribution iscopied by entering the following command:cd <DB2_DIST_DIR>

3. If you have downloaded the DB2 database product image, extract the productfile by using the following commands:gzip <product>.tar.gztar -xvf product.tar

Where product is the name of the product that you downloaded.4. Change directory to <DB2_DIST_DIR>/client.5. Start DB2 installation by entering the following command:

./db2_install

You see the following output:


https://www-945.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FInformation+Management%2FIBM+Data+Server+Client+Packages&fixids=DSClients-linuxx64-dsdriver-11.1.1.1-FP001&source=dbluesearch&function=fixId&parent=ibm/Information%20Management


Note: The output above shows that the total number of tasks to be performedare 29. But the installation log shows 30 tasks. This is a known limitation.

Results

DB2 Data Server Client client is installed in /opt/db2/product/11.1.0 directory.

Setting up a DB2 instance:

A DB2 instance is an environment in which you store data and run applications.

Before you begin

You must have root user authority.


Procedure

Use the db2iupgrade command to create an instance by using the following steps:1. Run the following commands:

$ cd /opt/db2/product/11.1.0/instance$ ./db2iupgrade db2

2. Verify the DB2 instance is successfully upgraded by running the followingcommand:$ db2levelDB21085I This instance or install (instance name, where applicable: "db2")uses "64" bits and DB2 code release "SQL11011" with level identifier"0202010F".Informational tokens are "DB2 v11.1.1.1", "s1612051900", "DYN1612051900AMD64",and Fix Pack "1".Product is installed at "/opt/db2/product/11.1.0".

3. Log in with the instance user that is db2.4. Ensure the catalog settings is pointing to DB2 server host by running the

following commands: For example:$ db2 list db directory

System Database DirectoryNumber of entries in the directory = 1Database 1 entry:Database alias = PVDBDatabase name = PVDBNode name = NODE1Database release level = f.00Comment =Directory entry type = RemoteCatalog database partition number = -1Alternate server hostname =Alternate server port number =

$ db2 list node directoryNode DirectoryNumber of entries in the directory = 1

Node 1 entry:Node name = NODE1Comment =Directory entry type = LOCALProtocol = TCPIPHostname = <DB2_Server_Host>Service name = 40000

You can replace the database name (by default, PV) and <node name> in thecommand with any string of your choice. For example, NodeA.

Next stepsThe steps that follow installation of the prerequisite software.

Once you have installed the prerequisite software, you are ready to begin theactual installation of Tivoli Netcool Performance Manager. Depending on the typeof installation you require, follow the directions in the appropriate chapter:v If you are planning on Installing Tivoli Netcool Performance Manager as a

distributed environment that uses clustering for high availability, review theTivoli Netcool Performance Manager High Availability documentation, which isavailable for download by going to https://www-304.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10NP54 and searching for"Netcool Proviso High Availability Documentation".


https://www-304.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10NP54

https://www-304.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10NP54


Chapter 6. Installing in a distributed environment

This section describes how to install Tivoli Netcool Performance Manager for thefirst time in a fresh, distributed environment.

Note:

v Before installing Tivoli Netcool Performance Manager, ensure if JRE 1.7 isinstalled. If this prerequisite is not installed, the Dataview installation actuallyfails and the install DataView step incorrectly shows as passed.

For information about installing the Tivoli Netcool Performance Managercomponents using a minimal deployment, see Chapter 7, “Installing as a minimaldeployment,” on page 171.

Distributed installation processThe main steps involved in a distributed installation.

A production Tivoli Netcool Performance Manager system that generates andproduces management reports for a real-world network is likely to be installed onseveral servers. Tivoli Netcool Performance Manager components can be installedto run on as few as two or three servers, up to dozens of servers.

The following figure shows the installation flow.


Before installing Tivoli Netcool Performance Manager, you must have installed theprerequisite software. For detailed information, see Chapter 3, “Installing andconfiguring the prerequisite software,” on page 63.

Important: If you are using a Solaris platform for installing Tivoli NetcoolPerformance Manager, ensure that Jazz™ for Service Management is either installedon Linux or AIX systems. Jazz™ for Service Management installation is notsupported on Solaris platform.

In addition, you must have decided how you want to configure your system. Referto the following sections:v “Co-location rules” on page 3v “Typical installation topology” on page 26v Appendix A, “Remote installation issues,” on page 227


The general steps used to install Tivoli Netcool Performance Manager are asfollows:v Start the launchpad.v Install the Topology Editor.v Start the Topology Editor.v Create the topology.v Add the Tivoli Netcool Performance Manager components.v Save the topology to an XML file.v Start the deployer.v Install Tivoli Netcool Performance Manager using the deployer.

The following sections describe each of these steps in detail.

Note: Before you start the installation, verify that all the database tests have beenperformed. Otherwise, the installation might fail. See Chapter 3, “Installing andconfiguring the prerequisite software,” on page 63 for information about tnsping.

Starting the LaunchpadThe steps required to start the Launchpad.

About this task

To start the Launchpad:

Procedure1. Log in as root.2. Set and export the DISPLAY variable.

See “Setting up a remote X Window display” on page 65.3. Set and export the BROWSER variable to point to your Web browser. For

example:

systems:# BROWSER=/usr/bin/firefox# export BROWSER

systems:# BROWSER=/usr/mozilla/firefox/firefox# export BROWSER


Note: The BROWSER command cannot include any spaces around the equalsign.

4. Change directory to the directory where the launchpad resides.

systems:# cd <DIST_DIR>/ proviso/SOLARIS

systems:# cd <DIST_DIR>/proviso/AIX

Chapter 6. Installing in a distributed environment 143

systems:# cd <DIST_DIR>/proviso/RHEL

<DIST_DIR> is the directory on the hard drive where you copied the contents ofthe Tivoli Netcool Performance Manager distribution.For more information see “Downloading the Tivoli Netcool PerformanceManager distribution to disk” on page 83.

5. Enter the following command to start the Launchpad:# ./launchpad.sh

Installing the Topology EditorThe steps that are required to install the Topology Editor.

About this task

Only one instance of the Topology Editor can exist in the Tivoli NetcoolPerformance Manager environment. Install the Topology Editor on the samesystem that hosts database server.

You can install the Topology Editor from the launchpad or from the command line.

To install the Topology Editor:

Procedure1. You can begin the Topology Editor installation procedure from the command

line or from the Launchpad.From the launchpad:a. On the launchpad, click the Install Topology Editor option in the list of

tasks.b. On the Install Topology Editor page, click the Install Topology Editor link.

From the command line:a. Log in as root.b. Change directory to the directory that contains the Topology Editor

installation script:

systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/topologyEditor/Disk1/InstData/VM

systems:# cd <DIST_DIR>/proviso/AIX/Install/topologyEditor/Disk1/InstData/VM

systems:# cd <DIST_DIR>/proviso/RHEL/Install/topologyEditor/Disk1/InstData/VM

<DIST_DIR> is the directory on the hard disk where you copied thecontents of the Tivoli Netcool Performance Manager distribution.For more information, see “Downloading the Tivoli Netcool PerformanceManager distribution to disk” on page 83.

c. Enter the following command:# ./installer.bin

2. The installation wizard opens in a separate window, displaying a welcomepage. Click Next.


3. Review and accept the license agreement, then click Next.4. Confirm that the wizard is pointing to the correct directory. The default is

/opt/IBM/proviso. If you have installed the Topology Editor on this system,the installer does not prompt you for an installation directory and insteaduses the directory where you last installed the application.

5. Select the database from DBMS Selection window.6. Click Next to continue.7. Confirm that the wizard is pointing to the correct base installation directory,

or click Choose to browse to another directory. Following are the installationdirectories: JDBC driver:

v/opt/oracle/product/12.1.0-client32/jdbc/lib

v/opt/db2/product/11.1.0/java

8. Click Next to continue.9. Review the installation information, then click Install.

10. When the installation is complete, click Done to close the wizard.The installation wizard installs the Topology Editor and an instance of thedeployer in the following directories:

Interface Directory

Topology Editor install_dir/topologyEditor

For example:

/opt/IBM/proviso/topologyEditor

Deployer install_dir/deployer

For example:

/opt/IBM/proviso/deployer

Results

The combination of the Topology Editor and the deployer is referred to as theprimary deployer.

For more information, see “Resuming a partially successful first-time installation”on page 169.

Note: To uninstall the Topology Editor, follow the instructions in “Uninstalling theTopology Editor” on page 222. Do not delete the /opt/IBM directory. Doing so cancause problems when you try to reinstall the Topology Editor.

If the /opt/IBM directory is accidentally deleted, do the following steps:1. Change to the /var directory.2. Rename the hidden file .com.zerog.registry.xml (for example, rename it to

.com.zerog.registry.xml backup).3. Reinstall the Topology Editor.4. Rename the backup file to the original name (.com.zerog.registry.xml).


What to do next

Once you have installed Topology Editor, you need to extract the<DIST_DIR>/license.tar to <install_dir>/license manually.

For example:$ cp <DIST_DIR>/license.tar /opt/IBM/proviso/license$ tar -xvf license.tar

Starting the Topology EditorAfter you install the Topology Editor, you can start it from either the launchpad orfrom the command line.

Procedurev To start the Topology Editor from the launchpad:

1. If the Install Topology Editor page is not already open, click the InstallTopology Editor option in the list of tasks to open it.

2. On the Install Topology Editor page, click the Start Topology Editor link.

Note: For a non-default installation, you are prompt to enter the path to thelocation where the Topology Editor is installed.

v To start the Topology Editor from the command line:1. Log in as root.2. Change directory to the directory in which you installed the Topology Editor.

For example:# cd /opt/IBM/proviso/topologyEditor

3. Enter the following command:# ./topologyEditor

Note: If your DISPLAY environment variable is not set, the Topology Editorfails with a Java assertion message (core memory dump).If you are running the Topology Editor for an AIX 6.1 or AIX 7.1environment, use the command:# ./topologyEditor -vm /opt/IBM/proviso/topologyEditor/jre/bin/java

Creating a new topologyThe steps that are required to create a new topology.

Procedure1. In the Topology Editor, select Topology > Create new topology.

The New Topology window is displayed.2. Enter the Number of resources to be managed by Tivoli Netcool Performance

Manager.

Note: Topology size is calculated depending upon the number of resources tobe managed. The default value is 10000. The size of your deployment affectsthe database sizing.

Important: Do not change the default DataView property value ofDV_CONTEXT_ROOT. The default DV_CONTEXT_ROOT value is PV.


3. Click Finish.The Topology Editor creates the following entities:v In the Logical view, five items are listed: Tivoli Netcool Performance

Manager Topology, Cross Collector CMEs, DataChannels, DataMarts, andDashboard Application Services Hub.

v In the Physical view, there is a new Hosts folder.

Adding and configuring the Tivoli Netcool Performance Managercomponents

Your next step is to add and configure the individual Tivoli Netcool PerformanceManager components.

Note: When you install with non-default values, that is, non-default user names,passwords and locations, it is adviced that you check both the Logical view andPhysical view to ensure that they both contain the correct values before youproceed with the installation.

Adding the hostsThe first step is to specify all the servers that host Tivoli Netcool PerformanceManager components.

About this task

Each host that you define has an associated property named PV User. PV User isthe default operating system for all Tivoli Netcool Performance Managercomponents.

You can override this setting in the Advanced Properties tab when you set thedeployment properties for individual components (for example, DataMart andDataView). You can install and run different components on the same system asdifferent users.

Note: DataChannel components always use the default user that is associated withthe host.

The user account that is used to transfer files that are used FTP or SCP/SFTP duringinstallation is always the PV User that is defined at the host level, rather thancomponent level.

To add a single host to the topology:

Procedure1. In the Physical view, right-click the Hosts folder and select Add Host from the

menu. The Add Host window opens.2. Specify the details for the host computer.

The fields are as follows:v HOSTNAME - Enter the name of the host (for example, delphi).v Operating System - Specifies the operating system (for example, SOLARIS).

This field is completed for you.v Database Home - Specifies the default Oracle or DB2 database home

directory for all Tivoli Netcool Performance Manager components that areinstalled on the system:


– The default directory for ORACLE_HOME is /opt/oracle/product/12.1.0-client32

– The default directory for DB2_HOME is /opt/db2/product/11.1.0v PV User - Specifies the default Tivoli Netcool Performance Manager UNIX

user (for example, pvuser) for all Tivoli Netcool Performance Managercomponents that are installed on the system.

v PV User Password - Specifies the password for the default Tivoli NetcoolPerformance Manager user (for example, PV).

v Create Disk Usage Server for this Host? - Selecting this check box creates aDataChannel subcomponent to handle disk quota and flow control.

If you do not choose to create a Disk Usage Server, click Finish to create thehost. The Topology Editor adds the host under the Hosts folder in the Physicalview. If you choose to create a Disk Usage Server, click Next and the Add Hostwindow is displayed where you can add details for your Disk Usage Server.

3. Specify the details for the Disk Usage Server.The fields are as follows:v Local Root Directory - The local DataChannel root directory. With Local Root

Directory, you can differentiate between a local directory and a remotedirectory that is mounted to allow for FTP access.

v Remote Root Directory - Remote directory that is mounted for FTP access.With Remote Root Directory, you can differentiate between a local directoryand a remote directory that is mounted to allow for FTP access.

v FC FSLL - FC FSLL is the Flow Control Free Space Low Limit property.When this set limit is reached the Disk Usage Server contacts all componentswho reside in this root directory and tell them to free up all space possible.

v FC QUOTA - FC QUOTA is the Flow Control Quota property. This propertyallows you to set the amount of disk space in bytes available to TivoliNetcool Performance Manager components on this file system.

v Remote User - User account is used when you attempt to access this DiskUsage Server remotely.

v Remote User Password - User account password is used when you attemptto access this Disk Usage Server remotely.

v Secure file transfer to be used - Boolean indicator that identifies if ssh mustbe used when you attempt to access this directory remotely.

v Port Number - Port number to use for remote access (sftp) in case it is anon-default port.

Click Finish to create the host. The Topology Editor adds the host under theHosts folder in the Physical view.

Note: The DataChannel properties are completed automatically at a later stage.

Adding multiple hostsYou can add multiple hosts at one time.

About this task

To add multiple hosts to the topology:

Procedure1. In the Physical view, right-click the Hosts folder and select Add Multiple Host

from the menu. The Add Multiple Hosts window opens.


2. Add new hosts by typing their names into the Host Name field as acomma-separated list.

3. Click Next.4. Configure all added hosts.

With Configure hosts dialog you can enter configuration settings and applythese settings to one or more of the specified hosts set.To apply configuration settings to one or more of the specified host sets:a. Enter the appropriate host configuration values. All configuration options

are described in Steps 2, and 3 of the previous process, “Adding the hosts”on page 147.

b. Select the check box opposite each of the hosts to which you want to applythe entered values.

c. Click Next. The hosts for which all configuration settings that are specifieddisappear from the set of selectable hosts.

d. Repeat steps a, b, and c until all hosts are configured.5. Click Finish.

Adding a database configurations componentThe Database Configurations component hosts all the database-specific parameters.

About this task

You define the parameters once, and their values are propagated as needed to theunderlying installation scripts.

To add a Database Configurations component:

Procedure1. In the Logical view, right-click the Tivoli Netcool Performance Manager

Topology component and select Add Database Configurations from the menu.The host selection window opens.

2. You must add the Database Configuration component to the same server thathosts the database server (for example, delphi). Select the appropriate hostusing the drop-down list.

3. Click Next to configure the mount points for the database.4. Add the correct number of mount points.

To add a new mount point, click Add Mount Point. A new, blank row is addedto the window. Fill in the fields as appropriate for the new mount point.

5. Enter the required configuration information for each mount point.a. Enter the mount point location:v Mount Point Directory Name, for example:

– /raid_2/oradata

– /raid_2/db2data

Note: The mount point directories can be named using any string asrequired by your organizations naming standards.

v Used for Metadata Tablespaces? (A check mark indicates True.)v Used for Temporary Tablespaces? (A check mark indicates True.)v Used for Metric Tablespaces? (A check mark indicates True.)


v Used for System Tablespaces and Redo? (A check mark indicates True.)b. Click Back to return to the original page.c. Click Finish to create the component.The Topology Editor adds the new Database Configurations component to theLogical view.

6. Highlight the Database Configurations component to display its properties.Review the property values to make sure they are valid. For the complete listof properties for this component, see the Properties Reference.The Database Configurations component has the following subelements:v Channel tablespace configurationsv Database Channelsv Database Clients configurationsv Tablespace configurationsv Temporary tablespace configurations

Note: Before you install Tivoli Netcool Performance Manager, verify that thefollowing directory structures are created:

v raid_2/oradata and raid_3/oradata

v raid_2/db2data and raid_3/db2data

Adding a DataMartThe steps required to add a DataMart component to your topology.

About this task

Tivoli Netcool Performance Manager DataMart is normally installed on the sameserver on which you installed database server and the Tivoli Netcool PerformanceManager database configuration. However, there is no requirement that forcesDataMart to reside on the database server.

Note the following:v If you are installing DataMart on an AIX system or any remote AIX, Linux or

Solaris system, you must add the IBM JRE to the PATH environment variable forthe Tivoli Netcool Performance Manager UNIX user, pvuser.

v You must ensure you are using the IBM JRE and not the RHEL JRE. The IBMJRE is supplied with the Topology Editor. To ensure you are using the right JREyou can either:– Set the JRE path to conform to that used by the Topology Editor, do this

using the following commands (using the default location for the primarydeployer):PATH=/opt/IBM/proviso/topologyEditor/jre/bin:$PATHexport $PATH

– For a remote server, that is one that does not host the primary deployer, youmust download and install the required JRE, and set the correct JRE path. SeeRequirements chapter for JRE download details.

To add a DataMart component:


Procedure1. In the Logical view, right-click the DataMarts folder and select Add DataMart

from the menu. The host selection host window is displayed.2. Using the drop-down list of available hosts, select the machine on which

DataMart must be installed (for example, delphi).3. Click Finish.

The Topology Editor adds the new DataMart x component (for example,DataMart 1) under the DataMarts folder in the Logical view.

4. Highlight the DataMart x component to display its properties. Review theproperty values to make sure they are valid. You can specify an alternateinstallation user for the DataMart component by changing the values of theUSER_LOGIN and USER_PASSWORDproperties in the Advanced Properties tab. Forthe complete list of properties for this component, see the Database propertiesin Properties Reference.

Event notification scriptsWhen you install the DataMart component, two event notification scripts areinstalled.

The scripts are called as needed by tablespace size checking routines in Oracle orDB2 and in Tivoli Netcool Performance Manager, if either routine detects low diskspace conditions on a disk partition hosting a portion of the Tivoli NetcoolPerformance Manager database. Both scripts by default send their notifications bye-mail to a local login name.

The two files and their installation locations for the two databases are as follows:

v The script installed as $ORACLE_BASE/admin/$ORACLE_SID/bin/notifyDBSpacenotifies the login name oracle by e-mail of impending database space problems.This script is called as needed by an Oracle routine that periodically checks foravailable disk space.

v The script installed as /opt/datamart/bin/notifyDBSpace notifies the login namepvuser of the same condition. This script is called as needed by the HourlyLoader component of Tivoli Netcool Performance Manager DataChannel. Theloader checks for available disk space before attempting its hourly upload ofdata to the database.

v The script that is installed as $DB2_BASE/tnpm_dbadmin/db2/bin notifies the loginname db2 by email of impending database space problems. This script is calledas needed by a DB2 routine that periodically checks for available disk space.

v The script that is installed as /opt/datamart/bin/notifyDBSpace notifies thelogin name pvuser of the same condition. This script is called as needed by theHourly Loader component of Tivoli Netcool Performance Manager DataChannel.The loader checks for available disk space before attempting its hourly upload ofdata to the database.

Either file for both databases can be customized to send its warnings to a differente-mail address on the local machine, to an SMTP server for transmission to aremote machine, or to send the notices to the local network's SNMP faultmanagement system (that is, to an SNMP trap manager). You can modify eitherscript to send notifications to an SNMP trap, instead of, or in addition to its


default e-mail notification.

Adding a Discovery ServerThe Discovery Server is the Tivoli Netcool Performance Manager componentresponsible for SNMP discovery.

About this task

You can add a discovery server for each DataMart defined in the topology.

To add a Discovery Server:

Procedure

In the Logical view, right-click the DataMart x folder and select Add Discoveryserver from the menu.The Topology Editor displays the new Discovery Server under the DataMart nfolder in the Logical view.

Adding multiple Discovery ServersThe steps required to add multiple Discovery servers.

About this task

If you want to run multiple Discovery servers on multiple hosts in yourenvironment, you must perform additional steps at deployment to make sure thateach host system contains identical inventory files and identical copies of theinventory hook script. IBM recommends that you only use identically-configuredinstances of the Discovery Server.

The inventory files used by the Discovery Server are configuration files namedinventory_elements.txt and inventory_subelements.txt. These files are located inthe $PVMHOME/conf directory of the system where you install the DataMartcomponent. Some technology packs provide custom sub-elements inventory fileswith names different from inventory_subelements.txt that are also used by theDiscovery Server.

To add multiple Discovery Servers, do the following:

Procedurev Install the primary instance of DataMart and the Discovery Server on one target

host system.v Install and configure any required technology packs on the primary host. You

modify the contents of the inventory files during this step.v Install secondary instances of DataMart and the Discovery Server on

corresponding target host systems.v Replicate the inventory files from the system where the primary instance of

DataMart is running to the $PVMHOME/conf directory on the secondary hosts. Youmust also replicate the InventoryHook.sh script that is located in the$PVMHOME/bin directory and any other files that this script requires.


Discovering existing Dashboard Application Services HubHow to update your topology so it sees existing Dashboard Application ServicesHub (DASH) instances on your system.

About this task

To discover existing Dashboard Application Services Hub:

This step runs an asynchronous check for existing Dashboard Application ServicesHub on each selected DataView host. If a Dashboard Application Services Hub isdiscovered on a host, the discovered Dashboard Application Services Hub detail isadded to the topology.

Procedure1. In the Physical view, right-click the Hosts folder and select Add Host from the

menu. Add the host that has an existing Dashboard Application Services Hubyou want to discover.

2. Go to the Logical view, right-click on the DASHs folder and select Importexisting Dashboard Application Services Hubs from host from the menu. TheRun Dashboard Application Services Hub Discovery Wizard Page isdisplayed.

3. Select the check box for each host on which you want the DashboardApplication Services Hub discovery.

4. Enter the value for DASH Installation User and DASH Installation Password.You can modify this value if you want to do the Dashboard ApplicationServices Hub installation with non-root user. For example,DASH_INSTALLATION_USER = ncadmin. For more information about, see Installingas a root user or non-root user.

5. Click Import DASH.If the discovered Dashboard Application Services Hub is an old version, it isflagged within the topology for upgrade.The deployer takes the appropriate action when run. You find that thediscovered DASH status as "[DASH found on: <host name>]".

6. Click Next.7. Configure Dashboard Application Services Hub properties.

a. Enter the appropriate host configuration values.

TCR_INSTALLATION_DIRECTORYThe directory in which Tivoli Common Reporting is installed.

DASH_INSTALLATION_DIRECTORYThe directory in which DASH is installed.

Note: The directory that is displayed during installation is a defaultdirectory. Ensure if the directory is correct and modify it accordingly.

WAS_USER_NAMEThe WAS user name.

Note: WAS_USER_NAME is the administrator user property. Bydefault, the value of this property is smadmin. If you change thevalue, you must specifically mention it in Configure properties formultiple DASHs window.


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install_root_nonroot.html

http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.1.0/com.ibm.psc.doc_1.1.1.0/install/psc_c_install_root_nonroot.html

WAS_PASSWORDThe WAS password.

Note: WAS_PASSWORD should be the same as the administrationpassword set for Jazz for Service Management.

If you would like to configure LDAP for DASH, see Appendix F, “LDAPintegration,” on page 267.

b. Select the check box opposite each of the DASH hosts to which you want toapply the entered values.

c. Click Next.The hosts for which all configuration settings are specified disappear fromthe set of selectable hosts.

d. Repeat steps a, b, and c until all hosts are configured.8. Click Next to add the discovered DASHs to the topology.

Note: The Tivoli Netcool Performance Manager user or Proviso user (forexample, pvuser). In a non-root DASH orTivoli Common Reporting andDataView installation, the value of Tivoli Netcool Performance Manager user orProviso user must be the non-root user (for example, ncadmin). For moreinformation about the Technology Pack/App Pack, refer to Installing andConfiguring Technology Packs.

Adding a DataViewThe steps that are required to add DataView components.

About this task

Note: To display DataView real-time charts, you must have the Java runtimeenvironment (JRE) installed on the browser where the charts are to be displayed.You can download the JRE from the Oracle and Sun Microsystems download pageat http://www.oracle.com/technetwork/java/javase/downloads/index.html

Note: If you are reusing an existing DASH that was installed by a user other thanroot, the default deployment of DataView will encounter problems. To avoid theseproblems, you must remove the offending DASH from your topology and addboth the DASH and DataView as a separate post deployment step.

To add a DataView component:

Procedure

In the Logical view, right-click on a DASH and select Add DataView from themenu. The DataView is automatically added inheriting its properties from theDASH instance.

Note:

v When you install non-root DataView on remote host, it asks the password ofnon-root user.

v Tivoli Netcool Performance Manager Data Provider is installed as part of TivoliNetcool Performance Manager 1.4.3 DataView component installation. After youcomplete the installation of Tivoli Netcool Performance Manager, see Using TivoliNetcool Performance Manager Data Provider 1.4.3 guide to start using the DataProvider.


http://www.oracle.com/technetwork/java/javase/downloads/index.html

Adding the DataChannel administrative componentsThe steps required to add DataChannel Administrative components.

Procedure1. In the Logical view, right-click the DataChannels folder and select Add

Administrative Components from the menu. The host selection window opens.2. Using the drop-down list of available hosts, select the machine that you want

to be the Channel Manager host for your DataChannel configuration (forexample, corinth).

3. Click Finish.The Topology Editor adds a set of new components to the Logical view:

Channel ManagerEnables you to start and stop individual DataChannels and monitor thestate of various DataChannel programs. There is one Channel Managerfor the entire DataChannel configuration. The Channel Managercomponents are installed on the first host you specify.

CORBA Naming ServerProvides near real-time data to DataView.

High Availability ManagersThis is mainly used for large installations that want to use redundantSNMP collection paths. The HAM constantly monitors the availabilityof one or more SNMP collection hosts, and switches collection to abackup host (called a spare) if a primary host becomes unavailable.

Log ServerUsed to store user, debug, and error information.

Plan BuilderCreates the metric data routing and processing plan for the othercomponents in the DataChannel.

Custom DataChannel propertiesThese are the custom property values that apply to all DataChannelcomponents.

Global DataChannel propertiesThese are the global property values that apply to all DataChannelcomponents.

Adding a DataChannelA DataChannel is a software module that receives and processes network statisticalinformation from both SNMP and non-SNMP (BULK) sources.

About this task

This statistical information is then loaded into a database where it can be queriedby SQL applications and captured as raw data or displayed on a portal in a varietyof reports.

Typically, collectors are associated with technology packs, a suite of Tivoli NetcoolPerformance Manager programs specific to a particular network device ortechnology. A technology pack tells the collector what kind of data to collect ontarget devices and how to process that data. See the Technology Pack InstallationGuide for detailed information about technology packs.


To add a DataChannel:

Procedure1. In the Logical view, right-click the DataChannels folder and select Add

DataChannel from the menu. The Configure the DataChannel window isdisplayed.

2. Using the drop-down list of available hosts, select the machine that will hostthe DataChannel (for example, corinth).

3. Accept the default channel number (for example, 1).4. Click Finish.

The Topology Editor adds the new DataChannel (for example, DataChannel 1)to the Logical view.

5. Highlight the DataChannel to display its properties. Note that the DataChannelalways installs and runs as the default user for the host (the Tivoli NetcoolPerformance Manager UNIX username, pvuser). Review the other propertyvalues to make sure they are valid. For the complete list of properties for thiscomponent, see the Properties Reference Guide.The DataChannel has the following subelements:

Daily Loader xProcesses 24 hours of raw data every day, merges it together, then loadsit into the database. The loader process provides statistics on metricchannel tables and metric tablespaces.

Hourly Loader xReads files output by the Complex Metric Engine (CME) and loads thedata into the database every hour. The loader process provides statisticson metric channel tables and metric tablespaces.

The Topology Editor includes the channel number in the element names. Forexample, DataChannel 1 would have Daily Loader 1 and File Transfer Engine 1.

Note: When you add DataChannel x, the Problems view shows that theInput_Components property for the Hourly Loader is blank. This missing valuewill automatically be filled in when you add a DataLoad collector (as describedin the next section) and the error will be resolved.

Separating the data and executable directoriesYou can separate the data and executable directories for your DataChannel

About this task

Note: Separating the data and executable directories is only possible during thefirst installation activity. After the installation, you cannot modify the topology toseparate the data and the executable directories.

Do the following, if you want to separate the data and executable directories foryour DataChannel:

Procedure1. Create two directories on the DataChannel host, for example, DATA_DIR to hold

the data and EXE_DIR to hold the executable.2. Change the LOCAL_ROOT_DIRECTORY value on that host 's Disk Usage Server to

the data root folder DATA_DIR.


In the Host advanced properties, you see the DATA_DIR value that is propagatedto all DC folder values for the host.

3. Change DC_ROOT_EXE_DIRECTORY to the executable directory EXE_DIR.This change propagates to the DC configuration directory, the DataChannel BinDirectory, and the Datachannel executable file name.

Note: For advanced information about DataChannels, see Appendix B,“DataChannel architecture,” on page 231.

Adding a DataChannel Remote (DCR)A DataChannel is a software module that receives and processes network statisticalinformation from both SNMP and non-SNMP (BULK) sources. A DataChannelremote is A DataChannel installation configuration in which the subchannel, CMEand FTE components are installed and run on one host, while the Loadercomponents are installed and run on another host.

About this task

In a DataChannel remote configuration, the subchannel hosts can continueprocessing data and detecting threshold violations, even while disconnected fromthe Channel Manager server.

The following task assumes that we are placing the LDR and DLDR on the currenthost, called, for example, hostname1; and that we are placing the subchannel, CMEand FTE, on another host, called, for example, hostname2.

To add a remote DataChannel:

Procedure1. If it is not already open, open the Topology Editor (see “Starting the Topology

Editor” on page 146).2. In the Topology Editor, select Topology > Open existing topology. The Open

Topology window is displayed.3. For the topology source, select From database and click Next.4. In the Physical View. Add a new host, hostname2, to the downloaded topology.5. In the Logical view, right-click the DataChannels folder and select Add

DataChannel from the menu. The Configure the DataChannel window isdisplayed.

6. Using the drop-down list of available hosts, select the computer that hosts theDataChannel, hostname1.

7. Accept the default channel number (for example, 1).8. Click Finish.

The Topology Editor adds the new DataChannel (for example, DataChannel2)to the Logical view.

9. Right-click on the new DataChannel, DataChannel2, and select Add SNMPCollector.

10. Select server hostname2 as the host.The Collector 2.2 is added.

11. Right-click on the Complex Metric Engine.2.2 and choose Change Host.12. Select server hostname2 as the host.

The File Transfer Engine 2.2 is added to hostname2.


Results

The setup must look as follows:v DataChannel 2 - hostname1v Collector 2.2 - hostname1v Collector SNMP - hostname2v Complex Metric Engine.2.2 - hostname2v File Transfer Engine 2.2 - hostname2v Daily Loader 2 - hostname1v Hourly Loader 2 - hostname1

This accomplishes FTE and CME to be on one server and LDR and DLDR to be onanother server.

Adding a CollectorCollectors collect and process raw statistical data about network devices obtainedfrom various network resources.

The collectors send the received data through a DataChannel for loading into theTivoli Netcool Performance Manager database. Note that collectors do not need tobe on the same machine as the database server and DataMart.

Collector typesCollector types and their description, plus the steps required to associate acollector with a Technology Pack.

About this task

There are two basic types of collectors:

SNMP collectorCollects data using SNMP polling directly to network services. Specify thiscollector type if you plan to install a Tivoli Netcool Performance ManagerSNMP technology pack. These technology packs operate in networkingenvironments where the associated devices on which they operate use anSNMP protocol.

Bulk DataLoad collectorImports data from files. The files can have multiple origins, including logfiles generated by network devices, files generated by SNMP collectors onremote networks, or files generated by a non-Tivoli Netcool PerformanceManager network management database

There are two types of bulk collectors:

UBA A Universal Bulk Adapter (UBA) Collector that handles bulk input filesgenerated by non-SNMP devices. Specify this collector type if you plan toinstall a Tivoli Netcool Performance Manager UBA technology pack,including Alcatel 5620 NM, Alcatel 5620 SAM, and Cisco CWM.

BCOL A bulk Collector that retrieves and interprets the flat file output of networkdevices or network management systems. This collector type is notrecommended for Tivoli Netcool Performance Manager UBA technologypacks, and is used in custom technology packs.


If you are creating a UBA collector, you must associate it with a specific technologypack. For this reason, IBM recommends that you install the relevant technologypack before creating the UBA collector. Therefore, you would perform thefollowing sequence of steps:

Procedure1. Install Tivoli Netcool Performance Manager, without creating the UBA collector.2. Download and install the technology pack.3. Open the deployed topology file to load the technology pack and add the UBA

collector for it.

Note: For detailed information about UBA technology packs and theinstallation process, see the Installing and Configuring Technology Packs.Configure the installed pack by following the instructions in the pack-specificuser's guide.

RestrictionsThere are a number of collector restrictions that must be noted.

Note the following restrictions:v The maximum collector identification number is 999.v There is no relationship between the channel number and the collector number

(that is, there is no predefined range for collector numbers based on channelnumber). Therefore, collector 555 could be attached to DataChannel 7.

v Each database channel can have a maximum of 40 subchannels (and therefore,40 collectors).

v In Tivoli Netcool Performance Manager, Version 1.4.3 the maximum number ofDataChannels that can be created is increased to 16. In previous version thisnumber was 8.

v Memory required for each collector is 4 GB.v The range of port numbers that can be used for the collectors is 3002 to 3999. All

the collectors’ numbers must be unique.

Viewing the list of collectorsDescribes the procedure to view the list of collectors.

Procedure1. Launch DataMart.2. Click Collector Information from the Monitor tab. This window lists all the

collectors that are loaded from the database.3. Select a collector from the list, and then click the other tabs to review specific

collector information. The following collector information is available:

Table 15. List of collectors

Column Description

Number Indicates the collector identifier number.

Status Indicates the collector status. For example,"Running" or "Not Running."

Server Indicates the host name or IP address of thesystem on which the collector is installed.

Port Indicates the communication port numberfor the collector.


Table 15. List of collectors (continued)

Column Description

Type Indicates the collector type.

Installation Directory Indicates the directory where the collector isinstalled.

To view collector information:4. Click Collector Information from the Monitor tab.5. Select a collector from the list.6. Click the Collector Information tab. The State and theActions groups display

all the information about that particular collector.

Creating and adding multiple SNMP collectorsHow to create an SNMP collector.

About this task

To add an SNMP collector:

Procedure1. In the Logical view, right-click the DataChannel x folder.

The pop-up menu lists the following options:v Add Collector SNMP - Creates an SNMP collector.v Add Collector UBA - Creates a UBA collector.v Add Collector BCOL - Creates a BCOL collector. This collector type is used in

custom technology packs. DataMart must be added to the topology before aBCOL collector can be added.

Select Add Collector SNMP. The Configure Collector window is displayed.2. Using the drop-down list of available hosts on the Configure Collector window,

select the computer that hosts the collector . (for example, corinth)3. Accept the default collector number (for example, 1).

The default collector number is seen in the collector number property.However, you need not accept the collector number. You can edit the collectornumber and port number as per your requirement. The collector numberranges from 1-999 of which 500 and 501 are restricted for other purpose. Theport number ranges from 3002 to 3999 and 3003 by default is the watchedprocess.

4. Repeat the steps from 2 to 4 for as many SNMP collectors you want to add.Ensure that the collector number and port number should be unique for all theSNMP Collectors.

5. Click Finish.The maximum number of SNMP components (SNMP Collector and SNMPSpare) on a host is 16.The Topology Editor displays the new collector under the DataChannel x folderin the Logical view.

Note: The port number property is not editable in the Topology Editor once itis selected in the Configure Collector Window. If you want to change the portnumber, you must remove the collector from the topology by right-clicking onit and choosing remove. Then add the collector back and edit the port in theConfigure Collector Window.


6. Highlight the collector to view its properties. The Topology Editor displaysboth the SNMP collector core parameters and the SNMP technologypack-specific parameters. The core parameters are configured with all SNMPtechnology packs. You can specify an alternate installation user for the SNMPcollector by changing the values of the pv_user, pv_user_group andpv_user_password properties in the Advanced Properties tab. Review thevalues for the parameters to make sure they are valid.

Important: Irrespective of the number of collectors that you add, the directoryis created only on /opt/dataload.

Note: For information about the core parameters, see Properties Reference.

Results

The collector has two components:v Complex Metric Engine x - Perform calculations on the collected data.v File Transfer Engine (FTE) x - Transfers files from the collector's output

directories and places them in the input directory of the CME.

The FTE writes data to the file /var/adm/wtmpx on each system that hosts acollector. As part of routine maintenance, check the size of this file to prevent itfrom growing too large.

Note: Your Solaris version can be configured with strict access default settings forsecure environments. Strict FTP access settings might interfere with automatictransfers between a DataChannel subchannel and the DataLoad server. Check forFTP lockouts in /etc/ftpd/ftpusers, and check for strict FTP rules in/etc/ftpd/ftpaccess.

Note: The Topology Editor includes the channel and collector numbers in theelement names. For example, DataChannel 1 could have Collector SNMP 1.1, withComplex Metric Engine 1.1. and File Transfer Engine 1.1.

Starting the DataLoad SNMP collectorAfter you have started the DataChannel components, check every server that hostsa DataLoad SNMP collector to make sure the collectors are running.

About this task

To check whether a collector is running, run the following command:

ps -ef | grep -i pvmd

If the collector is running, you will see output similar to the following:pvuser 27118 1 15 10:03:27 pts/4 0:06 /opt/dataload/bin/pvmd –nologo -noherald/opt/dataload/bin/dc.im -headless -a S

If a collector is not running, perform the following steps:

Procedure1. Log in to the server that is running Tivoli Netcool Performance Manager SNMP

DataLoad by entering the username and password you specified wheninstalling SNMP DataLoad..


2. Source the DataLoad environment file by entering the following command:./$DLHOME/dataLoad.env.Where $DLHOME is the location where SNMP DataLoad is installed on the system(/opt/dataload, by default).

Note: If DataLoad shares the same server as DataMart, make sure you unsetthe environment variable by issuing the following command from a BASH shellcommand line:unset PV_PRODUCT.

3. Change to the DataLoad bin directory by entering the following command:cd $PVMHOME/bin.

4. Start a DataLoad SNMP collector using the following command:pvmdmgr start -i <instance_no>.To stop the DataLoad SNMP collector, use the following command:pvmdmgr stop -i <instance_no>.

Note: You will not be able to start or stop the remote collector by using thePVM user interface. You can use the command line interface instead.

Add a Cross Collector CMEThe steps required to add a Cross Collector CME.

Procedure1. In the Logical view, right-click the Cross Collector CME folder and select Add

Cross Collector CME from the menu. The Specify the Cross Collector CMEdetails window is displayed.

2. Using the drop-down list of available hosts, select the machine that hosts theCross-Collector CME . (for example, corinth)

3. Select the desired Disk Usage Server on the selected host.4. Select the desired channel number (for example, 1).5. Click Finish.

The Topology Editor adds the new Cross-Collector CME (for example,Cross-Collector CME 2000) to the Logical view.

6. Highlight the Cross-Collector CME to display its properties.

Note: The Cross-Collector CME always installs and runs as the default user forthe host (the Tivoli Netcool Performance Manager UNIX username, pvuser).

7. Review the other property values to make sure they are valid. For the completelist of properties for this component, see the Properties Reference

8. After running the deployer to install the Cross-Collector CME you will need torestart the CMGR process.

Note: You notice that dccmd start all does not start the Cross-Collector CME atthis point.

9. You must first deploy a formula against the Cross-Collector CME using theDataChannel frmi tool.Run the frmi tool. The following is an example command:

frmi ecma_formula.js -labels formula_labels.txt

Where:v The format of formula_labels.txt is 2 columns separated by an "=" sign.v First column is Full Path to formula.


v Second is the number of the Cross-Collector CME.v The file formula_labels.txt is of the format:

Path_to_ECMA_formulas~Formula1Name=2000Path_to_ECMA_formulas~Formula2Name=2001

Note: When a Cross-Collector CME (CC-CME) is installed on the system andformulas are applied against it, the removal of collectors that the CC-CMEdepends on is not supported. This is an exceptional case, that is, if you havenot installed a CC-CME, collectors can be removed.

Adding multiple Cross CollectorsAbout this task

To add multiple Cross Collectors:

Procedure1. In the Logical view, right-click the Cross Collector CME folder and select Add

multiple Cross Collectors from the menu. The Add Cross Collector CMEwindow is displayed.

2. (Optional) Click Add Hosts to add to the set of Cross Collector hosts. Onlyhosts that have a DUS can be added.

Note: It is recommended that you have 20 Cross Collector CMEs spread acrossthe set of topology hosts.

3. Set the number of Cross Collector CMEs for the set of hosts, there are two waysyou can do this:v Click Calculate Defaults to use the wizard to calculate the recommended

spread across the added hosts. This sets the number of Cross Collector CMEsto the default value.

v To manually set the number of cross collector for each host, use thedrop-down menu opposite each host name.

4. Click Finish.

Saving the topologyWhen you are satisfied with the infrastructure, verify that all the property valuesare correct and that any problems have been resolved, then save the topology to anXML file.

About this task

To save the topology as an XML file:

Procedure1. In the Topology Editor, select Topology then either Save Topology As or Save

Topology.Click Browse to navigate to the directory in which to save the file. By default,the topology is saved as topology.xml file in the topologyEditor directory.

2. Accept the default value or choose another name or location, then click OK toclose the file browser window.

3. The file name and path is displayed in the original window. Click Finish tosave the file and close the window.


You are now ready to deploy the topology file (see “Starting the Deployer”).

Note: Until you actually deploy the topology file, you can continue makingchanges to it as needed by following the directions in “Opening an existingtopology file.”See Chapter 8, “Modifying the current deployment,” on page 179 for moreinformation about making changes to a deployed topology file.

Note: Only when you begin the process of deploying a topology is it saved tothe database. For more information, see “Deploying the topology” on page 166.

Opening an existing topology fileAs you create the topology, you can save the file and update it as needed.

About this task

To open a topology file that exists but that has not yet been deployed:



Topology window is displayed.3. For the topology source, click local then use Browse to navigate to the correct

directory and file. Once you have selected the file, click OK. The selected file isdisplayed in the Open Topology window.Click Finish.The topology is displayed in the Topology Editor.

4. Change the topology as needed.

Starting the DeployerThe primary deployer is installed on the same machine as the Topology Editor. Youfirst run the topology file on the primary deployer, and then run secondaryinstallers on the other machines in the distributed environment.

See “Resuming a partially successful first-time installation” on page 169 for moreinformation about the difference between primary and secondary deployers.

Note: Before you start the deployer, verify that all the database tests have beenperformed. Otherwise, the installation might fail. See Chapter 3, “Installing andconfiguring the prerequisite software,” on page 63 for more information.


Primary DeployerThe steps that are required to run the primary deployer from the Topology Editor

Procedure

Click Run > Run Deployer for Installation.

Note: When you use the Run menu options (install or uninstall), the deployer usesthe last saved topology file, not the current one. Be sure to save the topology filebefore you use a Run command.

Secondary DeployersA secondary deployer is only required if remote installation using the primarydeployer is not possible.

About this task

For more information on why you may need to use a secondary deployer, seeAppendix A, “Remote installation issues,” on page 227.

To run a secondary deployer:

Procedurev To run a secondary deployer from the launchpad:

1. On the launchpad, click Start the Deployer.2. On the Start Deployer page, click the Start Deployer link.

v To run a secondary deployer from the command line:1. Log in as root.2. Change to the directory containing the deployer within the downloaded

Tivoli Netcool Performance Manager distribution:

systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/deployer/

systems:# cd <DIST_DIR>/proviso/AIX/Install/deployer/

systems:# cd <DIST_DIR>/proviso/RHEL/Install/deployer/

<DIST_DIR> is the directory on the hard drive where you copied the contentsof the Tivoli Netcool Performance Manager distribution in “Downloading theTivoli Netcool Performance Manager distribution to disk” on page 83.

3. Enter the following command:# ./deployer.bin

Note: See Appendix D, “Deployer CLI options,” on page 251 for the list ofsupported command-line options.


Pre-deployment checkThe Deployer fails if the required patches listed in this file are not installed.

About this task

The Deployer performs a check on the operating system versions and that theminimum required packages are installed. The Deployer checks for the files aslisted in the relevant check_os.ini file.

The check_os.ini can be found at:

v The check_os.ini file detailing Solaris requirements can be foundat:

/SOLARIS/Install/SOL10/deployer/proviso/bin/Check/check_os.ini

v The check_os.ini file detailing AIX requirements can be found at:/AIX/Install/deployer/proviso/bin/Check/check_os.ini

v The check_os.ini file detailing Linux requirements can be foundat:/RHEL/Install/deployer/proviso/bin/Check/check_os.ini

Procedurev To check if the required packages are installed:

1. Click Run > Run Deployer for Installation to start the Deployer.2. Select the Check prerequisites check box.3. Click Next.

The check returns a failure if any of the required files are missing.v To repair a failure:

1. Log in as root.2. Install the packages listed as missing.3. (Linux only) If any motif package is listed as missing:

Install the missing motif package and update the package DB using thecommand:# updatedb

4. Rerun the check prerequisites step.

Deploying the topologyHow to deploy your defined topology.

About this task

The deployer displays a series of pages to guide you through the Tivoli NetcoolPerformance Manager installation. The installation steps are displayed in a table,you can run each step individually or to run all the steps at a time. For moreinformation about the deployer interface, see “Primary Deployer” on page 165.

Important: By default, Tivoli Netcool Performance Manager uses Monday todetermine when a new week begins. If you want to specify a different day, youmust change the FIRST_WEEK_DAY parameter in the Database Registry using thedbRegEdit utility. This parameter can be changed only when you first deploy thetopology that installs your Tivoli Netcool Performance Manager environment, and


it must be changed BEFORE the Database Channel is installed. For moreinformation, see the Tivoli Netcool Performance Manager Registry and SpaceManagement Tech Note. If you must stop the installation, you can resume it later.For more information, see “Resuming a partially successful first-time installation”on page 169.

To deploy the Tivoli Netcool Performance Manager topology:

Procedure1. The deployer opens, displaying a welcome page. Click Next to continue.2. If you started the deployer from the launchpad or from the command line,

enter the full path to your topology file, or click Choose to navigate to thecorrect location. Click Next to continue.

Note: If you start the deployer from within the Topology Editor, this step isskipped.The database access window prompts for the security credentials.

3. Enter the host name (for example, delphi) and database administratorpassword (for example, PV), and verify the other values (port number, SID, anduser name). If the database does not yet exist, these parameters must match thevalues you specified when you created the database configuration component(see “Adding a database configurations component” on page 149). Click Nextto continue.

4. The node selection window shows the target systems and how the files aretransferred (see “Secondary Deployers” on page 165 for an explanation of thiswindow). The table has one row for each computer where at least one TivoliNetcool Performance Manager component is installed.The default settings are as follows:v The Enable check box is selected. If this option is not selected, no actions are

performed on that computer.v If selected scripts are run to verify that the prerequisite software is installed,

the Check prerequisites check box is not selected.v Remote execution is enabled, by using both RSH and SSH.

If remote execution cannot be enabled due to a particular customer 'ssecurity protocols, see Appendix A, “Remote installation issues,” on page 227and “Resuming a partially successful first-time installation” on page 169.

v File transfer by using FTP is enabled.If wanted, reset the values as appropriate for your deployment.Click Next to continue.

5. Provide media location details.The Tivoli Netcool Performance Manager Media Location for componentswindow is displayed, listing component and component platform.a. Click Choose the Proviso Media. You are asked to provide location of the

media for each component.b. Enter the base directory in which your media is located. If any of the

component media is not within the directory that is specified, you are askedto provide media location detail for that component.

6. Click Run All to run all the steps in sequence.7. The deployer prompts you for the location of the setup files. Use the file

selection window to navigate to the top-level directory for your operatingsystem to avoid further prompts.


For example:<DIST_DIR>/RHEL/

<DIST_DIR> is the directory on the hard drive where you copied the contents ofthe Tivoli Netcool Performance Manager distribution in “Downloading theTivoli Netcool Performance Manager distribution to disk” on page 83.

Note: This assumes that the Tivoli Netcool Performance Manager distributionwas downloaded to the folder /var/tmp/cdproviso as per the instructions in“Downloading the Tivoli Netcool Performance Manager distribution to disk” onpage 83.If Dataview is configured to install on a remote host, the Run Remote DASHInstall step is included. This step prompts the user to enter the root password.The deployer requires this information in order to run as root on the remotehost and perform the Dataview installation.

8. When all the steps are completed successfully, click Done to close the wizard.

Note: During Tivoli Netcool Performance Manager installation process, DASHpassword will be added into /tmp/ProvisoConsumer/log.txt. For best practice,please remove the /tmp/ProvisoConsumer directory or keep a backup of thisdirectory for reference purposes but make sure this backup folder is secured.

Next stepsThe steps to perform after deployment.

Installing and configuring a technology pack and other postinstallation tasks

The next step is to install the technology packs, as described in Installing andconfiguring a technology pack.

Once you have created the topology and installed Tivoli Netcool PerformanceManager, it is very easy to make changes to the environment. Simply open thedeployed topology file (loading it from the database), make your changes, and runthe deployer with the updated topology file as input. For more information aboutperforming incremental installations, see Chapter 8, “Modifying the currentdeployment,” on page 179.

Note: After your initial deployment, always load the topology file from thedatabase to make any additional changes (such as adding or removing acomponent), because it reflects the current status of your environment. Once youhave made your changes, you must deploy the updated topology so that it ispropagated to the database. To make any subsequent changes following thisdeployment, you must load the topology file from the database again.

To improve performance, IBM recommends that you regularly compute thestatistics on metadata tables. You can compute these statistics by creating a cronentry that executes the dbMgr (Database Manager Utility) analyzeMetaDataTablescommand at intervals.

The following example shows a cron entry that checks statistics every hour at 30minutes past the hour. Note that the ForceCollection option is set to N, so thatstatistics will only be calculated when the internal calendar determines that it isnecessary, and not every hour:


0 5 * * * [ -f /opt/DM/dataMart.env ] && [ -x /opt/DM/bin/dbMgr ] && ./opt/DM/dataMart.env && dbMgr analyzeMetaDataTables A N

For more information on dbMgr and the analyzeMetaDataTables command, see theTivoli Netcool Performance Manager IBM Tivoli Netcool Performance Manager:Database Administration Guide.

For each new SNMP DataLoad, change the env file of the Tivoli NetcoolPerformance Manager user to add the directory with the openssh libcrypto so tothe LD_LIBRARY_PATH (or LIBPATH).

Resuming a partially successful first-time installationIf your installation fails due to some reason, you can resume the installationprocess.

About this task

In this scenario, you try deploying a Tivoli Netcool Performance Manager topologyfor the first time. You define the topology and start the installation. Although someof the components of the Tivoli Netcool Performance Manager topology areinstalled successfully, the overall installation does not complete successfully.

It addition, it is possible to skip a section of the installation. For example, a remotenode might not be accessible for some reason. After you skip this portion of theinstallation, resume the installation to continue with the remaining steps. Thedeployer lists only those steps that are needed to complete the installation on themissing node.

For example, suppose that during the first installation, database is not running, sothe database check failed. Stop the installation and start the database, then resumethe installation.

To resume a partial installation:

Procedure1. After you have corrected the problem, restart the deployer by using the

following command:a. Log in as root.b. Change directory to the directory that contains the deployer. For example:

# cd /opt/IBM/proviso/deployer

c. Enter the following command:# ./deployer.bin -Daction=resume

If you use the resume option, you can resume the installation exactly where youleft off.

Note: If you are asked to select a topology file to resume your installation,select the topology file that you saved before you begin the installation.

2. The deployer opens, displaying a welcome page. Click Next to continue.3. Accept the default location of the base installation directory of database JDBC

driver:

Oracle /opt/oracle/product/12.1.0-client32

DB2 /jdbc/lib, /opt/db2/product/11.1.0.


Or, click Choose to navigate to another directory. Click Next to continue.4. The steps page shows the installation steps in the same state they were in when

you stopped the installation (with the completed steps marked Success, thefailed step marked Error, and the remaining steps marked Held).

5. Select the step that previously failed, reset it to Ready, then click Run Next.Verify that this installation step now completes successfully.

6. Run any remaining installation steps, verifying that they complete successfully.7. At the end of the installation, the deployer loads the updated topology

information into the database.


Chapter 7. Installing as a minimal deployment

Describes how to install Tivoli Netcool Performance Manager as a minimaldeployment.

OverviewA minimal deployment installation is used primarily for demonstration orevaluation purposes, and installs the product on the smallest number of machinespossible, with minimal user input.

When you perform a minimal deployment installation, the Tivoli NetcoolPerformance Manager components are installed on the server you are running thedeployer from.

Before you beginBefore installing Tivoli Netcool Performance Manager, you must have installed theprerequisite software.

For detailed information, see Chapter 3, “Installing and configuring the prerequisitesoftware,” on page 63.

Note: Before you start the installation, verify that all the database tests have beenperformed. Otherwise, the installation might fail. See Chapter 3, “Installing andconfiguring the prerequisite software,” on page 63 for information about tnsping.

If you are setting up a demonstration or evaluation system, it is possible to installall Tivoli Netcool Performance Manager components on a single server for Linux,Solaris or AIX systems. In this case your installation process will go as follows:


Special considerationBy default, Tivoli Netcool Performance Manager uses Monday to determine whena new week begins.

If you wish to specify a different day, you must change the FIRST_WEEK_DAYparameter in the Database Registry using the dbRegEdit utility. This parameter canonly be changed when you first deploy the topology that installs your TivoliNetcool Performance Manager environment, and it must be changed BEFORE theDatabase Channel is installed. For more information, see the Tivoli NetcoolPerformance Manager Database Administration Guide.

No resume of partial install availableThere is no resume functionality available to a minimal deployment installation.

As a result a minimal deployment installation must be carried out in full if it is tobe attempted.

Overriding default valuesWhen performing a minimal deployment installation you must accept all defaultvalues. The exceptions are listed in this section.

The exceptions to this are:v Location of the database jdbc driver.

The default is /opt/oracle/product/12.1.0/jdbc/lib

The default is /opt/db2/product/11.1.0/javav Tivoli Netcool Performance Manager installation destination folder.

The default is /opt/proviso

v server parameters. The defaults are:– Oracle Base: /opt/oracle– Oracle home: /opt/oracle/product/12.1.0-client32– Oracle Port: 1521

v server parameters. The defaults are:– DB2 Base:/opt/db2– Database Home:/opt/db2/product/11.1.0– DB2 Port: 60000


Installing a minimal deploymentThis section provides step-by-step instructions for installing Tivoli NetcoolPerformance Manager on a single Solaris, AIX or Linux server.

Starting the LaunchpadThe steps required to start the Launchpad.

About this task

To start the Launchpad:

Procedure1. Log in as root.2. Set and export the DISPLAY variable.

See “Setting up a remote X Window display” on page 65.3. Set and export the BROWSER variable to point to your Web browser. For

example:


systems:# BROWSER=/usr/mozilla/firefox/firefox# export BROWSER


Note: The BROWSER command cannot include any spaces around the equalsign.

4. Change directory to the directory where the launchpad resides.

systems:# cd <DIST_DIR>/ proviso/SOLARIS

systems:# cd <DIST_DIR>/proviso/AIX

systems:# cd <DIST_DIR>/proviso/RHEL

<DIST_DIR> is the directory on the hard drive where you copied the contents ofthe Tivoli Netcool Performance Manager distribution.For more information see “Downloading the Tivoli Netcool PerformanceManager distribution to disk” on page 83.

5. Enter the following command to start the Launchpad:# ./launchpad.sh

Chapter 7. Installing as a minimal deployment 173

Start the installationSteps required to install.

About this task

A minimal deployment installation uses a predefined topology file.

To start the installation:

Procedure1. On the launchpad, click the Install Tivoli Netcool Performance Manager for

Minimal Deployment option in the list of tasks, then click the Install TivoliNetcool Performance Manager 1.4.3 for Minimal Deployment link to start thedeployer.Alternatively, you can start the deployer from the command line, as follows:a. Log in as root.b. Set and export your DISPLAY variable (see “Setting up a remote X

Window display” on page 65).c. Change directory to the directory that contains the deployer:

systems:

# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/deployer

systems:# cd <DIST_DIR>/proviso/AIX/Install/deployer

systems:# cd <DIST_DIR>/proviso/RHEL/Install/deployer

d. Enter the following command:# ./deployer.bin -Daction=poc -DPrimary=true

2. The deployer opens, displaying a welcome page. Click Next to continue.3. Accept the terms of the license agreement, then click Next.4. Accept the default location of the base installation directory of the JDBC

driver:

/opt/oracle/product/12.1.0-client32/jdbc/lib)

/opt/db2/product/11.1.0/java

or click Choose to navigate to another directory. Click Next to continue.5. The deployer prompts for the directory in which to install Tivoli Netcool

Performance Manager. Accept the default value (/opt/proviso) or clickChoose to navigate to another directory. Click Next to continue.

6. Verify the following additional information about the database:

BaseThe base directory for the Oracle installation (for example,/opt/oracle). Accept the provided path or click Choose to navigate toanother directory.


BaseThe base directory for the DB2 installation (for example, /opt/db2).Accept the provided path or click Choose to go to another directory.

Database HomeThe root directory of the database /opt/oracle/product/12.1.0-client32)

The root directory of the database /opt/db2/product/11.1.0v Accept the provided path or click Choose to navigate to another directory.

v Port: The port used for Oracle communications. The defaultvalue is 1521.

v Port: The port that is used for DB2 communications. Thevalue is 60000.

Click Next to continue.7. The node selection window shows the target system and how the files will be

transferred. These settings are ignored for a minimal deployment installationbecause all the components are installed on a single server.Click Next to continue.

8. Provide media location details. The Tivoli Netcool Performance ManagerMedia Location for components window is displayed, listing component andcomponent platform.a. Click Choose the Proviso Media. You will be asked to provide location of

the media for each component.b. Enter the base directory in which your media is located. If any of the

component media is not within the directory specified, you will be askedto provide media location detail for that component.

9. The deployer displays summary information about the installation. Review theinformation, then click Next to begin the installation.The deployer displays the table of installation steps (see “Pre-deploymentcheck” on page 166 for an overview of the steps table). Note the following:v If an installation step fails, see Appendix H, “Error codes and log files,” on

page 275 for debugging information. Continue the installation by followingthe instructions in “Resuming a partially successful first-time installation”on page 169

v Some of the installation steps can take a long time to complete. However, ifan installation step fails, it will fail in a short amount of time.

10. Click Run All to run all the steps in sequence.11. When all the steps have completed successfully, click Done to close the

wizard.12. Run chmod -R 777 on /opt/IBM/tivoli in order to make all files in the

Dashboard Application Services Hub directory structure accessible.Your installation is complete. See “The post-installation script” on page 176 forinformation about the post-installation script, or “Next steps” on page 176 forwhat to do next.


The post-installation scriptThe post-installation script is run automatically when installation is complete.

About this task

For a minimal deployment the script performs four actions:

Procedure1. Starts the DataChannel.2. Starts the DataLoad SNMP Collector, if it is not already running.3. Creates a DataView user named tnpm.4. Gives the poc user permission to view reports under the NOC Reporting group,

with the default password of tnpm.

Results

The script writes a detailed log to the file /var/tmp/poc-post-install.${TIMESTAMP}.log.

Next stepsThe steps to be performed following the deployment of your system.

When the installation is complete, you are ready to perform the final configurationtasks that enable you to view reports on the health of your network. These stepsare documented in detail in the Tivoli Netcool Performance Managerdocumentation set.

For each new SNMP DataLoad, change the env file of the Tivoli NetcoolPerformance Manager user to add the directory with the openssh libcrypto.so tothe LD_LIBRARY_PATH (or LIBPATH).

Download the MIB-II filesThe minimal deployment version installs the MIB-II Technology Pack.

About this task

Before beginning the installation, you must download both the Technology PackInstaller and the MIB-II jar files.

To download these files, access either of the following distributions:

Procedurev The product distribution site: https://www-112.ibm.com/software/howtobuy/

softwareandservicesLocated on the product distribution site are the ProvisoPackInstaller.jar file,the bundled jar file, and individual stand-alone technology pack jar files.

v (Optional) The Tivoli Netcool Performance Manager CD distribution, whichcontains the ProvisoPackInstaller.jar file and the jar files for the Starter Kitcomponents.See your IBM customer representative for more information about obtainingsoftware.


https://www-112.ibm.com/software/howtobuy/softwareandservices

https://www-112.ibm.com/software/howtobuy/softwareandservices

Note: Technology Pack Installer and the MIB-II jar files must be in the samedirectory (for example, AP), and no other application jar files should be present,if there are any more jars in that folder the installation step will fail due to "toomany jars" in the specified folder. In addition, you must add the AP directory tothe Tivoli Netcool Performance Manager distribution's directory structure.



Chapter 8. Modifying the current deployment

Describes how to modify an installation of Tivoli Netcool Performance Manager.

It is possible to modify Tivoli Netcool Performance Manager after it has beeninstalled. To add, delete or upgrade components, load the deployed topology fromthe database, make your changes, and run the deployer with the updated topologyas input.

Note: You must run the updated topology through the deployer in order for yourchanges to take effect.

Note the following:v After your initial deployment, always load the topology from the database to

make any additional changes (such as adding or removing a component),because it reflects the current status of your environment. Once you have madeyour changes, you must deploy the updated topology so that it is propagated tothe database. To make any subsequent changes following this deployment, youmust load the topology from the database again.

v You might have a situation where you have modified a topology by both addingnew components and removing components (marking them "To Be Removed").However, the deployer can work in only one mode at a time - installation modeor uninstallation mode. In this situation, first run the deployer in uninstallationmode, then run it again in installation mode.

For information about deleting components from an existing topology, see“Removing a component from the topology” on page 217.

Migrating between platforms

It is possible to migrate components between platforms when performing theTivoli Netcool Performance Manager upgrade.

The only supported migration path is from Solaris to AIX. There is no support forany other platform migration scenario.

Opening a deployed topologyOnce you have installed Tivoli Netcool Performance Manager, you can performincremental installations by modifying the topology that is stored in the database.

About this task

You retrieve the topology, modify it, then pass the updated data to the deployer.When the installation is complete, the deployer stores the revised topology data inthe database.


To open a deployed topology:



Topology window is displayed.3. For the topology source, select and click Next.4. Verify that all of the fields for the database connection are filled in with the

correct values:

Database hostnameThe name of the database host. The default value is localhost.

Port

The port number used for communication with the database. Thedefault value is 1521.

The port number used for communication with the database. Thedefault value is 60000.

Database userThe user name used to access the database. The default value isPV_INSTALL

Database PasswordThe password for the database user account. For example, PV.

DB Name

The SID for the database. The default value is PV.

The name of database. The default value is PV.If desired, click Save as defaults to save these values for future incrementalinstallations.

5. Click Finish.

Results

The topology is retrieved from the database and is displayed in the TopologyEditor.

Adding a new componentAfter you have deployed your topology, you might need to make changes to it.

About this task

For example, you might want to add another SNMP collector.

To add a new component to the topology:



Editor” on page 146).2. Open the existing topology (see “Opening a deployed topology” on page 179).3. In the Logical view of the Topology Editor, right-click the folder for the

component you want to add.4. Select Add XXX from the pop-up menu, where XXX is the name of the

component you want to add.5. The Topology Editor prompts for whatever information is needed to create the

component. See the appropriate section for the component you want to add:v “Adding the hosts” on page 147v “Adding a database configurations component” on page 149v “Adding a DataMart” on page 150v “Adding a Discovery Server” on page 152v “Discovering existing Dashboard Application Services Hub” on page 153v “Adding a DataView” on page 154v “Adding the DataChannel administrative components” on page 155v “Adding a DataChannel” on page 155v “Adding a Collector” on page 158

Note: that if you add a collector to a topology that has already beendeployed, you must manually bounce the DataChannel managementcomponents (cnsw, logw, cmgrw, amgrw). For more information, see “Manuallystarting the Channel Manager programs” on page 236.

v “Creating and adding multiple SNMP collectors” on page 160v “Adding a Discovery Server” on page 152

6. The new component is displayed in the Logical view of the Topology Editor.7. Save the updated topology. You must save the topology after you add the

component and before you run the deployer. This step is not optional.8. Run the deployer (see “Starting the Deployer” on page 164), passing the

updated topology as input.The deployer can determine that most of the components described in thetopology are already installed, and installs only the new component.

9. When the installation ends successfully, the deployer uploads the updatedtopology into the database.For information about removing a component from the Tivoli NetcoolPerformance Manager environment, see “Removing a component from thetopology” on page 217.

Example

In this example, you update the installed version of Tivoli Netcool PerformanceManager to add a new DataChannel and two SNMP DataLoaders to the existingsystem.

To update the Tivoli Netcool Performance Manager installation:1. If it is not already open, open the Topology Editor (see “Starting the Topology

Editor” on page 146).2. Open the existing topology (see “Opening a deployed topology” on page 179).3. In the Logical view of the Topology Editor, right-click the DataChannels folder.

Chapter 8. Modifying the current deployment 181

4. Select Add Data Channel from the pop-up menu. Following the directions in“Adding a DataChannel” on page 155, add the following components:a. Add a new DataChannel (Data Channel 2) with two different SNMP

DataLoaders to the topology. The Topology Editor creates the newDataChannel.

b. Add two SNMP collectors to the channel structure created by the TopologyEditor. The editor automatically creates a Daily Loader component, anHourly Loader component, and two Sub Channels with an FTE componentand a CME component.

5. Save the updated topology.6. Run the deployer (see “Starting the Deployer” on page 164), passing the

updated topology as input.The deployer can determine that most of the components described in thetopology are already installed, and installs only the new components (in theexample, DataChannel 5 with two new subchannels and DataLoaders).

7. When the installation ends, successful or not, the deployer uploads the updatedtopology into the database.

Changing configuration parameters of existing Tivoli NetcoolPerformance Manager components

Configuration information is stored in the database. This enables theDataChannel-related components to retrieve the configuration from the database atrun time.

You set the configuration information using the Topology Editor. As with the othercomponents, if you make changes to the configuration values, you must pass theupdated topology data to the deployer to have the changes propagated to both theenvironment and the database.

Note: After the updated configuration has been stored in the database, you mustmanually start, stop, or bounce the affected DataChannel component to have yourchanges take effect.

Moving components to a different hostYou can use the Topology Editor to move components between hosts.

About this task

You can move all components between hosts when they have not yet beeninstalled and are in the configured state. You can move SNMP and UBA collectorswhen they are in the configured state or after they have been deployed and are inthe installed state.

If the component in the topology has not yet been deployed and is in theconfigured state, the Topology Editor provides a Change Host option in thepop-up menu when you click the component name in the Logical view. Thisoption allows you to change the host associated with the component prior todeployment.

If the component is an SNMP or UBA collector that was previously deployed andis in the installed state, the Topology Editor provides a Migrate option in the


pop-up menu. This option instructs the deployer to uninstall the component fromthe previous host and re-install it on the new system.

For instructions on moving deployed SNMP and UBA collectors after deployment,see “Moving a deployed collector to a different host.” For instructions on movingcomponents that have not yet been deployed, see the information below.

Note: The movement of installed DataChannel Remote components is notsupported. All other components can be moved.

To change the host associated with a component before deployment:

Procedure1. Start the Topology Editor (if it is not already running) and open the topology

that includes the component's current host (see “Starting the Topology Editor”on page 146 and “Opening a deployed topology” on page 179).

2. In the Logical view, navigate to the name of the component to move.3. Right-click the component name, then click Change Host from the pop-up

menu.The Migrate Component dialog appears, containing a drop-down list of hostswhere you can move the component.

4. Select the name of the new host from the list, then click Finish.The name of the new host appears in the Properties tab.

Moving a deployed collector to a different hostYou can move a deployed SNMP or UBA collector to a different host. Theinstructions for doing so differ for SNMP collectors and UBA collectors.

After you move a collector to a new host, it may take up to an hour for the changeto be registered in the database.

Moving a deployed SNMP collector (scenario 1)The steps required to move a deployed SNMP collector to a different host ifcollector is the last SNMP collector on original host.

About this task

Note: To avoid the loss of collected data, leave the collector running on theoriginal host until you complete Step 7 on page 108.

To move a deployed SNMP collector to a different host then follow these steps:


that includes the collector's current host (see “Starting the Topology Editor” onpage 146 and “Opening a deployed topology” on page 179).

2. In the Logical view, navigate to the name of the collector to move. For exampleif moving SNMP 1.1, navigate as follows:DataChannels > DataChannel 1 > Collector 1.1 > Collector SNMP.1.1

3. Right-click the collector name (for example, Collector SNMP 1.1), then clickMigrate from the pop-up menu.


The Migrate Collector dialog appears, containing a drop-down list of hostswhere you can move the collector.

Note: If you are moving a collector that has not been deployed, select Changehost from the pop-up menu (Migrate is grayed out). After the Migrate Collectordialog appears, continue with the steps below.

4. Select the name of the new host from the list, then click Finish.In the Physical view, the status of the collector on the new host is Configured.The status of the collector on the original host is To be uninstalled. You willremove the collector from the original host in Step 9.

Note: If you are migrating a collector that has not been deployed, the name ofthe original host is automatically removed from the Physical view.

5. Click Topology > Save Topology to save the topology data.6. Click Run > Run Deployer for Installation to run the deployer, passing the

updated topology as input. For more information on running the deployer, see“Starting the Deployer” on page 164.The deployer installs the collector on the new host and starts it.

Note: Both collectors are now collecting data - the original collector on theoriginal host, and the new collector on the new host.

7. Before continuing with the steps below, note the current time, and wait until atime period equivalent to two of the collector's collection periods elapses.Doing so guards against data loss between collections on the original host andthe start of collections on the new host.Because data collection on the new host is likely to begin sometime after thefirst collection period begins, the data collected during the first collectionperiod will likely be incomplete. By waiting for two collection time periods toelapse, you can be confident that data for one full collection period will becollected.The default collection period is 15 to 30 minutes. You can find the collectionperiod for the sub-element, sub-element group, or collection formula associatedwith the collector in the DataMart Request Editor. For information on viewingand setting a collection period, see the Configuring and Operating DataMart.

8. Bounce the FTE for the collector on the collector's new host, as in the followingexample:./dccmd bounce FTE.1.1

The FTE now recognizes the collector's configuration on the new host, and willbegin retrieving data from the collector's output directory on the new host.

9. In the current Topology Editor session, click Run > Run Deployer forUninstallation. Remove the collector from original host and save the topology.Run deployer for Uninstallation.

Note: This step is not necessary if you are moving a collector that has not beendeployed.

Moving a deployed SNMP collector (scenario 2)The steps required to move a deployed SNMP collector to a different host ifcollector is not the last SNMP collector on original host.

About this task

To move a deployed SNMP collector to a different host then follow these steps:



that includes the collector's current host (see “Starting the Topology Editor” onpage 146 and “Opening a deployed topology” on page 179).

2. In the Logical view, navigate to the name of the collector to move. For exampleif moving SNMP 1.1, navigate as follows:DataChannels > DataChannel 1 > Collector 1.1 > Collector SNMP.1.1

3. Right-click the collector name (for example, Collector SNMP 1.1), then clickMigrate from the pop-up menu.The Migrate Collector dialog appears, containing a drop-down list of hostswhere you can move the collector.

Note: If you are moving a collector that has not been deployed, select Changehost from the pop-up menu (Migrate is grayed out). After the Migrate Collectordialog appears, continue with the steps below.

4. Select the name of new host from list, and then click Finish. In the Physicalview, the status of collector on the new host is configured.

5. Click Topology > Save Topology to save the topology data.6. Click Run > Run Deployer for Installation to run the deployer, passing the

updated topology as input. For more information on running the deployer, see“Starting the Deployer” on page 164.The deployer installs the collector on the new host and starts it.

Note: Both collectors are now collecting data - the original collector on theoriginal host, and the new collector on the new host.

7. Bounce the FTE for the collector on the collector's new host, as in the followingexample:./dccmd bounce FTE.1.1

The FTE now recognizes the collector's configuration on the new host, and willbegin retrieving data from the collector's output directory on the new host.

Note: There is no need to click Run Deployer for Uninstallation in this case.

Moving a deployed SNMP collector to or from a HAMenvironmentIf you move a deployed SNMP collector into or out of a High Availability Manager(HAM) environment, you must perform the steps in this section.

About this task

To move a deployed SNMP collector to or from a HAM environment:

Procedure1. Move the collector as described in “Moving a deployed SNMP collector

(scenario 1)” on page 183.

Note: If you are moving a spare collector out of the HAM environment, thenavigation path is different than the path shown in Step 2 of the aboveinstructions. For example, suppose you have a single HAM environment with acluster MyCluster on host MyHost, and you are moving the second SNMPspare out of the HAM. The navigation path to the spare would be as follows:


DataChannels > Administrative Components > High Availability Managers >HAM MyServer.1 > MyCluster > Collector Processes > Collection ProcessSNMP Spare 2.

2. Log in as Tivoli Netcool Performance Manager UNIX user, pvuser, on thecollector's new host.

3. Change to the directory where DataLoad is installed. For example:cd /opt/dataload

4. Source the DataLoad environment:. ./dataLoad.env

5. Stop the SNMP collector:pvmdmgr stop

6. Edit the file dataLoad.env and set the field DL_HA_MODE as follows:v Set DL_HA_MODE=true if you moved the collector onto a HAM host.v Set DL_HA_MODE=false if you moved the collector off of a HAM host.

7. Edit the file dataLoad.env and set the field DL_HA_MODE_1 as follows:v Set DL_HA_MODE_1=true if you moved the collector onto a HAM host.v Set DL_HA_MODE_1=false if you moved the collector off of a HAM host.

8. Source the DataLoad environment again:. ./dataLoad.env

9. Start the SNMP collector:pvmdmgr start

Note: If you move an SNMP collector to or from a HAM host, youmust bounce the HAM. For information, see “Stopping and restarting modifiedcomponents” on page 214.

Moving a deployed UBA bulk collectorThe steps required to move a deployed UBA collector to a different host.

About this task

Note: You cannot move BCOL collectors, or UBA collectors that have a BLB orQCIF subcomponent. If you want to move a UBA collector that has thesesubcomponents, you must manually remove it from the old host in the topologyand then add it to the new host.

To move a deployed UBA collector to a different host:

Procedure1. Log in as pvuser to the DataChannel host where the UBA collector is running.2. Change to the directory where DataChannel is installed. For example:

cd /opt/datachannel

3. Source the DataChannel environment:. dataChannel.env

4. Stop the collector's UBA and FTE components. For example, to stop thesecomponents for UBA collector 1.1, run the following commands:dccmd stop UBA.1.1

and...dccmd stop FTE.1.1


For information on the dccmd command, see the Tivoli Netcool PerformanceManager Command Line Interface Guide.

Note: Some technology packs have additional pack-specific components thatmust be shut down - namely, BLB (bulk load balancer) and IF (inventory file)components. IF component names have the format xxxIF, where xxx is apack-specific name. For example, Cisco CWM packs have a CWMIFcomponent, Alcatel 5620 SAM packs have a SAMIF component, and Alcatel5620 NM packs have a QCIF component. Other packs do not use thesetechnology-specific components.

5. Tar up the UBA collector's UBA directory. You will copy this directory to thecollector's new host later in the procedure (Step 13).For example, to tar up a UBA directory for UBA collector 1.1, run thefollowing command:

Note: This step is not necessary if the collector's current host and the newhost share a file system.

tar -cvf UBA_1_1.tar ./UBA.1.1/*

Note: Some technology packs have additional pack-specific directories thatneed to be moved. These directories have the same namesas the corresponding pack-specific components described in Step 4.

6. Start the Topology Editor (if it is not already running) and open the topologythat includes the collector's current host (see “Starting the Topology Editor” onpage 146 and “Opening a deployed topology” on page 179).

7. In the Logical view, navigate to the name of the collector to move - forexample, Collector UBA.1.1.

8. Right-click the collector name and select Migrate from the pop-up menu.The Migrate Collector dialog appears, containing a drop-down list of hostswhere you can move the collector.

9. Select the name of the new host from the list, then click Finish.In the Physical view, the status of the collector on the new host is Configured.The collector is no longer listed under the original host.

Note: If the UBA collector was the only DataChannel component on theoriginal host, the collector will be listed under that host,and its status will be "To be uninstalled." You can remove the DataChannelinstallation from the original host after you finish the steps below. Forinformation on removing DataChannel from the host, see “Removing acomponent from the topology” on page 217.

10. Click Topology > Save Topology to save the topology.11. Click Run > Run Deployer for Installation to run the deployer, passing the

updated topology as input. For more information on running the deployer, see“Starting the Deployer” on page 164.If DataChannel is not already installed on the new host, this step installs it.

12. Click Run > Run Deployer for Uninstallation to remove the collector fromthe original host, passing the updated topology as input. For moreinformation, see “Removing a component from the topology” on page 217.

13. Copy any directory you tarred in Step 5 and the associated JavaScript files tothe new host.

Note: This step is not necessary if the collector's original host and the newhost share a file system.


For example, to copy UBA_1_1.tar and the JavaScript files from the collector'soriginal host:a. Log in as pvuser to the UBA collector's new host.b. Change to the directory where DataChannel is installed. For example:

cd /opt/datachannel

c. FTP to the collector's original host.d. Run the following commands to copy the tar file to the new host. For

example:cd /opt/datachannelget UBA_1_1.tarbyetar -xvf UBA_1_1.tar

e. Change to the directory where the JavaScript files for the technology packassociated with the collector are located:cd /opt/datachannel/scripts

f. FTP the JavaScript files from the /opt/datachannel/scripts directory on theoriginal host to the /opt/datachannel/scripts directory on the new host.

14. Log in as pvuser to the Channel Manager host where the AdministratorComponents (including CMGR) are running.

15. Stop and restart the Channel Manager by performing the following steps:a. Change to the $DC_HOME directory (typically, /opt/datachannel).b. Source the DataChannel environment:

. dataChannel.env

c. Get the CMGR process ID by running the following command:ps -ef | grep CMGR

The process ID appears in the output immediately after the user ID, asshown below in bold:pvuser 6561 6560 0 Aug 21 ? 3:04 /opt/datachannel/bin/CMGR_visualn/dc.im-a CMGRpvuser 25976 24244 0 11:39:38 pts/7 0:00 grep CMGR

d. Stop the CMGR process. For example, if 6561 is the CMGR process ID:kill -9 6561

e. Change to the $DC_HOME/bin directory (typically, /opt/datachannel/bin).f. Restart CMGR by running the following command:

./cmgrw

16. Log in as pvuser to the UBA collector's new host and change to the$DC_HOME/bin directory (typically, /opt/datachannel/bin).

17. Run the following command to verify that Application Manager (AMGR) isrunning on the new host:./findvisual

If the AMGR process is running, you will see output that includes an entrylike the following:pvuser 6684 6683 0 Aug 21 ? 3:43 /opt/datachannel/bin/AMGR_visual -nologo/opt/datachannel/bin/dc.im -a AMGR -lo

Note: If AMGR is not running on the new host, do not continue. Verify thatyou have performed the preceding steps correctly.

18. Start the collector's UBA and FTE components on the new host. For example,to start these components for collector 1.1, run the following commands:./dccmd start UBA.1.1

and...


./dccmd start FTE.1.1

Note: If any pack-specific components were shut down on the old host (seeStep 4), you must also start those components on the new host.

Changing the port for a collectorYou can use the Topology Editor to change the port associated with a collector.

About this task

To change the port associated with a collector after deployment:


(see “Starting the Topology Editor” on page 146 and “Opening a deployedtopology” on page 179).

2. In the Logical view, navigate to the collector.3. Highlight the collector to view its properties.

The Topology Editor displays both the collector core parameters and thetechnology pack-specific parameters.

4. Edit the port parameter within the list, SERVICE_PORT, then click Finish.5. Click Topology > Save Topology to save the topology data.6. Click Run > Run Deployer for Installation to run the deployer, passing the

updated topology as input.7. When deployment is complete, log onto the server hosting the collector.8. Log in as Tivoli Netcool Performance Manager UNIX user, pvuser, on the

collector's host.9. Change to the directory where DataLoad is installed. For example:

cd /opt/dataload


11. Stop the SNMP collector:pvmdmgr stop

12. Edit the file dataLoad.env and set the field DL_ADMIN_TCP_PORT.For example:DL_ADMIN_TCP_PORT=8800


14. Start the SNMP collector:pvmdmgr start


Modifying Dashboard Application Services Hub and Tivoli CommonReporting ports

You can update the ports used by Dashboard Application Services Hub and TivoliCommon Reporting.

The Dashboard Application Services Hub specific ports defined and used to buildthe topology.xml file are as follows:WAS_WC_defaulthost 16310COGNOS_CONTENT_DATABASE_PORT 1557IAGLOBAL_LDAP_PORT 389

Changing ports for the Dashboard Application Services HubYou can assign new ports to an installed Dashboard Application Services Hubconsole.

Procedure1. Create a properties file containing values such as host name that match your

environment. The exemplary properties file below uses default values. Modifythe values to match your environment. Save the file in any location.WAS_HOME=C:/IBM/JazzSMwas.install.root=C:/IBM/JazzSMprofileName=DASHProfileprofilePath=C:/IBM/JazzSM/profilestemplatePath=C:/IBM/JazzSM/profileTemplates/defaultnodeName=DASHNodecellName=DASHCellhostName=your_JazzSM_hostportsFile=C:/IBM/JazzSM/properties/DASHPortDef.properties

2. Edit the JazzSM_install_dir/properties/DASHPortDef.properties file tocontain the desired port numbers.

3. Stop the Jazz for Service Management server by navigating to the directory inthe command-line interface. For more information, seeStopping Jazz for Service Management application servers.

Important: To stop the server, you must log in with the same user that youused to install Tivoli Common Reporting.

4. In the command-line interface, navigate to the TCR_install_dir/bin directory.5. Run the following command:

ws_ant.bat -propertyfile C:/temp/tcrwas.props-file "C:/IBM/JazzSM/profileTemplates/default/actions/updatePorts.ant"

C:/temp/tcrwas.props is the path to the properties file created in Step 1.6. Change the port numbers in IBMCognos® Configuration:

a. Open IBM Cognos Configuration by running the following command:

TCR_component_dir\cognos\bin\tcr_cogconfig.bat

TCR_install_dir/cognos/bin/tcr_cogconfig.sh

b. In the Environment section, change the port numbers to the desired values,as in Step 2.

c. Save your settings and close IBM Cognos Configuration.


https://www.ibm.com/support/knowledgecenter/SSBNJ7_1.4.2/jazzsm/ttnpm_jazzsm_stop_jsm.html

7. Start the Jazz for Service Management server by navigating to the directory inthe command-line interface. For more information, see Starting Jazz for ServiceManagement application servers.

Important: To start the server, you must log in with the same user that youused to install Jazz for Service Management.

Port assignmentsThe application server requires a set of sequentially numbered ports.

The sequence of ports is supplied during installation in the response file. Theinstaller checks that the number of required ports (starting with the initial portvalue) are available before assigning them. If one of the ports in the sequence isalready in use, the installer automatically terminates the installation process andyou must specify a different range of ports in the response file.

Viewing the application server profileOpen the application server profile to review the port number assignments andother information.

About this task

The profile of the application server is available as a text file on the computerwhere it is installed.

Procedure1. Locate the /opt/IBM/JazzSM/profile/logs directory.2. Open AboutThisProfile.txt in a text editor.

Example

This is the profile for an installation in a Windows environment as it appears in/opt/IBM/JazzSM/profile/logs/AboutThisProfile.txt:Application server environment to create: Application serverLocation: /opt/IBM/JazzSM/profile/DASHProfileDisk space required: 200 MBProfile name: DASHProfileMake this profile the default: TrueNode name: DASHNode Host name: <myJazzSMserver>.ibm.comEnable administrative security (recommended): TrueAdministrative consoleport: 16315Administrative console secure port: 16316HTTP transport port: 16310HTTPS transport port: 16311Bootstrap port: 16312SOAP connector port: 16313Run application server as a service: FalseCreate a Web server definition: False


http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/admin/psc_t_admin_start_jazzsm_server.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/admin/psc_t_admin_start_jazzsm_server.html


Chapter 9. Using the High Availability Manager

Describes the optional Tivoli Netcool Performance Manager High AvailabilityManager (HAM), including how to set up a HAM environment.

OverviewThe High Availability Manager (HAM) is an optional component for largeinstallations that want to use redundant SNMP collection paths.

The HAM constantly monitors the availability of one or more SNMP collectionhosts, and switches collection to a backup host (called a spare) if a primary hostbecomes unavailable.

The following figure shows a simple HAM configuration with one primary hostand one spare. In the panel on the left, the primary host is operating normally.SNMP data is being collected from the network and channeled to the primary host.In the panel on the right, the HAM has detected that the primary host isunavailable, so it dynamically unbinds the collection path from the primary hostand binds it to the spare.

Important: The High Availability Manager configuration is recommended onlywhen the primary and spare collectors are on different hosts.


HAM basicsAn SNMP collector collects data from a specific set of network resources accordingto a set of configuration properties.

A collector has two basic parts: the collector process running on the host computer,and the collector profile that defines the collector's properties.

Note: Do not confuse a "collector profile" with an "inventory profile." A collectorprofile contains properties used in the collection of data from network resources -properties such as collector number, polling interval, and output directory for thecollected data. An inventory profile contains information used to discover networkresources - properties such as the addresses of the resources to look for and themode of discovery.

A collector that is not part of a HAM environment is static - that is, the collectorprocess and the collector profile are inseparable. But in a HAM environment, thecollector process and collector profile are managed as separate entities. This meansthat if a collector process is unavailable (due to a collector process crash or a hostmachine outage), the HAM can dynamically reconfigure the collector, allowingdata collection to continue. The HAM does so by unbinding the collector profilefrom the unavailable collector process on the primary host, and then binding thecollector profile to a collector process on a backup (spare) host.

Note: It may take several minutes for the HAM to reconfigure a collector,depending on the amount of data being collected.

The parts of a collectorCollector parts and their description.

When you set up a HAM configuration in the Topology Editor, you manage thetwo parts of a collector - the collector process and the collector profile - throughthe following folders in the Logical view:

Collector ProcessesA collector process is a UNIX process representing a runtime instance of acollector. A collector process is identified by the name of the host wherethe process is running and by the collector process port (typically, 3002). Ahost can have just one SNMP collector process.

Managed DefinitionsA managed definition identifies a collector profile through the uniquecollector number defined in the profile.

Every managed definition has a default binding to a host and to thecollector process on that host. The default host and collector process arecalled the managed definition's primary host and collector process. A hostthat you designate as a spare host has a collector process but no defaultmanaged definition.

The following figure shows the parts of a collector that you manage through theCollector Process and Managed Definition folders. In the figure, the HAMdynamically unbinds the collector profile from the collector process on the primaryhost, and then binds the profile to the collector process on the spare. This dynamicre-binding of the collector is accomplished when the HAM binds the manageddefinition - in this case, represented by the unique collector ID, Collector 1 - to thecollector process on the spare.


ClustersA HAM environment can consist of a single set of hosts or multiple sets of hosts.Each set of hosts in a HAM environment is called a cluster.

A cluster is a logical grouping of hosts and collector processes that are managed bya HAM.

The use of multiple clusters is optional. Whether you use multiple clusters or justone has no affect on the operation of the HAM. Clusters simply give you a way toseparate one group of collectors from another, so that you can better deploy andmanage your primary and spare collectors in a way that is appropriate for yourneeds.

Multiple clusters may be useful if you have a large number of SNMP collectorhosts to manage, or if the hosts are located in various geographic areas.

The clusters in a given HAM environment are distinct from one another. In otherwords, the HAM cannot bind a managed definition in one cluster to a collectorprocess in another.

HAM cluster configurationFor host failover to occur, a HAM cluster must have at least one available sparehost.

The cluster can have as few as two hosts - one primary and one spare. Or, it canhave multiple primary hosts with one or more spares ready to replace primaryhosts that become unavailable.

The ratio of primary hosts to spare hosts is expressed as p + s. For example, aHAM cluster with four primary hosts and two spares is referred to as a 4+2cluster.

Chapter 9. Using the High Availability Manager 195

Types of spare hostsThere are two types of spare hosts:

Designated spareThe sole purpose of this type of spare in a HAM cluster is to act as abackup host.

A designated spare has a collector process, but no default manageddefinition. Its collector process remains idle until the HAM detects anoutage on one of the active hosts, and binds that host's managed definitionto the spare's collector process.

A HAM cluster must have at least one designated spare.

Floating spareThis type of spare is a primary host that can also act as a backup host forone or more managed definitions.

Types of HAM clustersThe types of HAM clusters that can be created.

When the HAM binds a managed definition to a spare (either a designated spareor a floating spare), the spare becomes an active component of the collector. Itremains so unless you explicitly reassign the managed definition back to itsprimary host or to another available host in the HAM cluster. This is an importantfact to consider when you plan the hosts to include in a HAM cluster.

There are two types of HAM clusters:

Fixed spare clusterIn this type of cluster, failover can occur only to designated spares. Thereare no floating spares in this type of cluster.

When the HAM binds a managed definition to the spare, the sparetemporarily takes the place of the primary that has become unavailable.When the primary becomes available again, you must reassign themanaged definition back to the primary (or to another available host). Theprimary then resumes its data collection operations, and the spare resumesits role as backup host.

If you do not reassign the managed definition back to the primary, theprimary cannot participate in further collection operations. Since theprimary is not configured as a floating spare, it also cannot act as a sparenow that its collector process is idle. As a result, the HAM cluster loses itsfailover capabilities if no other spare is available.

Note: A primary host cannot act as a spare unless it is configured as afloating spare.

Floating spare clusterThis type of cluster has one or more primary hosts that can also act as aspare. Failover can occur to a floating spare or to a designated spare.

You do not need to reassign the managed definition back to this type ofprimary, as you do with primaries in a fixed spare cluster. When a floatingspare primary becomes available again, it assumes the role of a spare.

You can designate some or all of the primaries in a HAM cluster asfloating spares. If all the primaries in a HAM cluster are floating spares,


you should never have to reassign a managed definition to anotheravailable host in order to maintain failover capability.

Note: IBM recommends that all the primaries in a cluster be of the sametype - either all floating spares or no floating spares.

Example HAM clustersExamples of HAM cluster options.

The Tivoli Netcool Performance Manager High Availability Manager feature isdesigned to provide great flexibility in setting up a HAM cluster. The followingillustrations show just a few of the possible variations.

1 + 1, fixed spareA fixed spare cluster with one primary host and one designated spare.

The figure below shows a fixed spare cluster with one primary host and onedesignated spare:v In the panel on the left, Primary1 is functioning normally. The designated spare

is idle.v In the panel on the right, Primary1 experiences an outage. The HAM unbinds

the collector from Primary1 and binds it to the designated spare.v With the spare in use and no other spares in the HAM cluster, failover can no

longer occur - even after Primary1 returns to service. For failover to be possibleagain, you must reassign Collector 1 to Primary1. This idles the collector processon the spare, making it available for the next failover operation if Primary 1 failsagain.

Note: When a designated spare serves as the only spare for a single primary, as ina 1+1 fixed spare cluster, the HAM pre-loads the primary's collector definition onthe spare. This results in a fast failover with a likely loss of no more than onecollection cycle.

The following table shows the bindings that the HAM can and cannot make in thiscluster:

Collector Possible Host Bindings Host Bindings Not Possible

Collector 1 Primary1 (default binding)

Designated spare

-


2 + 1, fixed spareA fixed spare cluster with two primary hosts and one designated spare

The figure below shows a fixed spare cluster with two primary hosts and onedesignated spare:v In the panel on the left, Primary1 and Primary2 are functioning normally. The

designated spare is idle.v In the panel on the right, Primary2 experiences an outage. The HAM unbinds

the collector from Primary2 and binds it to the designated spare.v With the spare in use and no other spares in the HAM cluster, failover can no

longer occur - even after Primary2 returns to service. For failover to be possibleagain, you must reassign Collector 2 to Primary2. This idles the collector processon the spare, making it available for the next failover operation.




Designated spare

Primary2


Designated spare

Primary1

Note: Due to multi collector functionality, we can also add Collector 1 andCollector 2 on the same Primary host.

2 + 1, both primaries are floating sparesBoth primaries are floating spares.

The figure below shows a floating spare cluster with two primary hosts and onedesignated spare, with each primary configured as a floating spare:v In the panel on the left, Primary1 and Primary2 are functioning normally. The

designated spare is idle.v In the panel on the right, Primary2 experiences an outage. The HAM unbinds

the collector from Primary2 and binds it to the designated spare.v When Primary2 returns to service, it will assume the role of spare, meaning its

collector process remains idle. The host originally defined as the dedicated sparecontinues as the active platform for Collector 2.


v The following figure shows the same cluster after Primary2 has returned toservice. In the panel on the left, Primary2 is idle, prepared to act as backup ifneeded.

v In the panel on the right, Primary1 experiences an outage. The HAM unbindsthe collector from Primary1 and binds it to the floating spare, Primary2.




Primary2

Designated spare

-

Collector 2 Primary1

Primary2 (default binding)

Designated spare

-

3+ 2, fixed sparesA fixed spare cluster with three primary hosts and two designated spares.

The figure below shows a fixed spare cluster with three primary hosts and twodesignated spares:v In the panel on the left, all three primaries are functioning normally. The

designated spares are idle.


v In the panel on the right, Primary3 experiences an outage. The HAM unbindsthe collector from Primary3 and binds it to Designated Spare 2. The HAM choseDesignated Spare 2 over Designated Spare 1 because the managed definition forCollector 3 set the failover priority in that order.

Note: Each managed definition sets its own failover priority. Failover prioritycan be defined differently in different managed definitions.

v With one spare in use and one other spare available (Designated Spare 1),failover is now limited to the one available spare - even after Primary3 returnsto service. For dual failover to be possible again, you must reassign Collector 3to Primary3.

Note: Due to multi collector functionality, we can add multiple designatedspares on a host.




Designated Spare 1

Designated Spare 2

Primary2

Primary3


Designated Spare 1

Designated Spare 2

Primary1

Primary3


Designated Spare 1

Designated Spare 2

Primary1

Primary2

3+ 2, all primaries are floating sparesA floating spare cluster with three primary hosts and two designated spares, witheach primary configured as a floating spare.


The figure below shows a floating spare cluster with three primary hosts and twodesignated spares, with each primary configured as a floating spare:v In the panel on the left, Primary3 had previously experienced an outage. The

HAM unbound its default collector (Collector 3) from Primary3, and bound thecollector to the first available spare in the managed definition's priority list,which happened to be Designated Spare 2. Now that Primary3 is availableagain, it is acting as a spare, while Designated Spare 2 remains the activecollector process for Collector 3.

v In the panel on the right, Primary2 experiences an outage. The HAM unbindsCollector 2 from Primary2, and binds it to the first available spare in themanaged definition's priority list. This happens to be the floating sparePrimary3.

v When Primary2 becomes available again, there will once more be two sparesavailable - Primary2 and Designated Spare 1.




Primary2

Primary3

Designated Spare 1

Designated Spare 2

-



Primary3

Designated Spare 1

Designated Spare 2

-




Primary2


Designated Spare 1

Designated Spare 2

-

High Availability Manager configuration changes to accommodatemultiple collector

It is advised that there are enough spare SNMP DL processes allocated on differentphysical servers to support outages that take down entire physical servers.

Since previous installations of Tivoli Netcool Performance Manager only supportedmultiple SNMP processes on a single physical server via virtualization; this changemakes it more likely that you will have to consider the possibility of an outage thatencompasses multiple SNMP DL processes. The HAM configuration must reflectthe increased risk of a single point of failure at the physical server level because ofthe process consolidation that this change allows.


Resource poolsWhen you configure a managed definition in the Topology Editor, you specify thehosts that the HAM can bind to the managed definition, and also the priority orderin which the hosts are to be bound. This list of hosts is called the resource pool forthe managed definition.

A resource pool includes:v The managed definition's primary host and collector process (that is, the host

and collector process that are bound to the managed definition by default).v Zero or more other primary hosts in the cluster.

If you add a primary host to a managed definition's resource pool, that primaryhost becomes a floating spare for the managed definition.

v Zero or more designated spares in the cluster.Typically, each managed definition includes one or more designated spares in itsresource pool.

Note: If no managed definitions include a designated spare in their resourcepools, there will be no available spares in the cluster, and therefore failovercannot occur in the cluster.

How the SNMP collector worksThe SNMP collector capability and behaviour.

The SNMP collector is state-based and designed both to perform initialization andtermination actions, and to "change state" in response to events generated by theHAM or as a result of internally-generated events (like a timeout, for example).

The following table lists the events that the SNMP collector understands andindicates whether they can be generated by the HAM.

Event HAM-Generated Description

Load Yes Load collection profile, donot begin schedulingcollections.

Pause Yes Stop scheduling collections;do not unload profile.

Reset Yes Reset expiration timer.

Start Yes Start scheduling collections.

Stop Yes Stop scheduling collections;unload profile

Timeout No Expiration timer expires;start scheduling collections.

The SNMP collector can reside in one of the following states, as shown in thefollowing table:


SNMP Collector State Event Description

Idle N/A Initial state; a collectornumber may or may not beassigned; the collectionprofile has not been loaded.

Loading Load Intermediate state betweenIdle and Ready. Occurs aftera Load event. Collectornumber is assigned, and thecollection profile is beingloaded.

Ready N/A Collector number assigned,profile loaded, but notscheduling requests orperforming collections.

Starting Start Intermediate state betweenIdle and Running. Occursafter a Start event. Collectornumber assigned, and profileis being loaded.

Running N/A Actively performing requestsand collections.

Stopping Stop/Pause Intermediate state betweenRunning and Idle.

The following state diagram shows how the SNMP collector transitions through itsvarious states depending upon events or time-outs:

How failover works with the HAM and the SNMP collectorHow Failover Works With the HAM and the SNMP Collector

The following tables illustrate how the HAM communicates with the SNMPcollectors during failover for a 1+1 cluster and a 2+1 cluster.


Table 16. HAM and SNMP Collector in a 1+1 Cluster

State of Primary State of Spare Events and Actions

Running Idle The HAM sends the sparethe Load event for thespecified collection profile.

Running Ready The HAM sends a Pauseevent to the spare to extendthe timeout. Note: If thetimeout expires, the sparewill perform start actionsand transition to a Runningstate.

Running Running The HAM sends a Pauseevent to the collector processthat has been in a Runningstate for a shorter amount oftime.

No response Ready The HAM sends a Startevent to the spare.

Table 17. HAM and SNMP Collector in a 2+1 Cluster

State of Primary State of Spare Events and Actions

Running Idle No action

Running Ready No action

Running Running The HAM sends a Stop eventto the collector process thathas been in Running state forthe shorter amount of time.

No Response Idle The HAM sends a Startevent to the spare.

No Response Ready The HAM sends a Startevent to the spare.

Because more than one physical system may produce SNMP collections, the FileTransfer Engine (FTE) must check every capable system for a specific profile. TheFTE retrieves all output for the specific profile. Any duplicated collections arereconciled by the Complex Metrics Engine (CME).

Obtaining collector statusHow to get the status of a collector.

To obtain status on the SNMP collectors managed by the HAM, enter the followingcommand on the command line:

$ dccmd status HAM.<hostname>.1

The dccmd command returns output similar to the following:COMPONENT APPLICATION HOST STATUS ES DURATION EXTENDED STATUSHAM.DCAIX2.1 HAM DCAIX2 running 10010 1.1 Ok: (box1:3012 ->Running 1.1 for 5h2m26s); No avail spare; Check: dcaix2:3002, birdnestb:3002 1.2 Ok: (box2:3002 ->Running 1.2 for 5h9m36s); No avail spare; Check: box4:3002, box5:3002 1.3 NotRunning; No avail spare;Check: box4:3002, box5:3002


The following list describes EXTENDED STATUS information:v 1.1 - Load # Collection profile 1.1v Ok: - Status of the load. Ok means it is properly collected, Not Running indicates

a severe problem (data losses)v (box1:3012 -> Running 1.1 for 5h2m26s)- The collector that is currently

performing the load, with its status and uptime.v No avail spare - List of possible spare, if something happens to the collector

currently working. In this example there is no spare available, a failover wouldfail. A list of host:port would indicate the possible spare machines.

v Check: box4:3002, box5:3002 - Indicates what is currently wrong with thesystem/configuration. Machines box4:3002 and box5:3002 should be spare butare either not running, or not reachable. The user is instructed to check thesemachines.

For a 1-to-1 failover configuration, the dccmd command might return output likethe following:$ dccmd status HAM.SERVER.1COMPONENT APPLICATION HOST STATUS ES DURATION EXTENDED STATUSHAM.SERVER.1 HAM SERVER running 10010 1.1 Ok: (box1:3002 ->Running 1.1 for 5h2m26s); 1 avail spare: (box2:3002 -> Ready 1.1)

This preceding output shows that Collector 1.1 is in a Running state on Box1, andthat the Collector on Box2 is in a Ready state, with the profile for Collector 1.1loaded.

Creating a HAM environmentThis section describes the steps required to create a 3+1 HAM environment with asingle cluster, and with all three primaries configured as floating spares.

About this task

This is just one of the many variations a HAM environment can have. Theprocedures described in the following sections indicate the specific steps whereyou can vary the configuration.

Note: If you are setting up a new Tivoli Netcool Performance Managerenvironment and plan to use a HAM in that environment, perform the followingtasks in the following order:

Procedure1. Install all collectors.2. Configure and start the HAM.3. Install all technology packs.4. Perform the discovery.


Topology prerequisitesThe minimum component prerequisite.

A 3+1 HAM cluster requires that you have a topology with the followingminimum components:v Three hosts, each bound to an SNMP collector. These act as the primary hosts.

You can create a managed definition for each of the primary hosts.v One additional host that is not bound to an SNMP collector. This acts as the

designated spare.

For information on installing these components, see “Adding a new component”on page 180.

ProceduresThe general procedures for creating a single-cluster HAM with one designatedspare and three floating spares.

Create the HAM and a HAM clusterTo create a High Availability Manager with a single cluster


where you want to add the HAM (see “Starting the Topology Editor” on page146 and “Opening a deployed topology” on page 179).

2. In the Logical view, right-click High Availability Managers, located atDataChannels > Administrative Components.

3. Select Add High Availability Manager from the pop-up menu.The Add High Availability Manager Wizard appears.

4. In the Available hosts field, select the host where you want to add the HAM.

Note: You can install the HAM on a host where a collector process is installed,but you cannot install more than one HAM on a host.

5. In the Identifier field, accept the default identifier.The identifier has the following format:HAM.<HostName>.< n >

where HostName is the name of the host you selected in Step 4, and n is aHAM-assigned sequential number, beginning with 1, that uniquely identifiesthis HAM from others that may be defined on other hosts.

6. Click Finish.The HAM identifier appears under the High Availability Managers folder.

7. Right-click the identifier of the HAM you just created.8. Select Add Cluster from the pop-up menu.

The Add Cluster Monitor Wizard appears.9. In the Identifier field, type a name for the cluster and click Finish.

The cluster name appears under the HAM identifier folder you added inStep 6. The following folders appear under the cluster name:v Collector Processesv Managed Definitions


Note: To add additional clusters to the environment, repeat Step 7 throughStep 9.

Adding the designated spareHow to create and add a designated spare.

About this task

To create a designated spare, you must have a host that is defined in the Physicalview with no SNMP collector assigned to it. For information about adding a hostto a topology, see “Adding the hosts” on page 147

To add a designated spare to a cluster:

Procedure1. In the Logical view, right-click the Collector Processes folder that you created

in Step 9 of the previous section, “Create the HAM and a HAM cluster” onpage 207.

2. Select Add Collection Process SNMP Spare from the menu.The Add Collection Process SNMP Spare - Configure Collector Process SNMPSpare dialog is diaplayed.

3. In the Available hosts field, select the host that you want to make thedesignated spare.

4. The Port field, specifies the next available port number, for the spare's collectorprocess. You can modify the port number. then click Finish.Under the cluster's Collector Processes folder, the entry Collection ProcessSNMP Spare <n > appears, where n is a HAM-assigned sequential number,beginning with 1, that uniquely identifies this designated spare from othersthat may be defined in this cluster.

Note: Repeat Step 1 through Step 4 to add an extra designated spare to thecluster.

Important: The spare collector should have a unique port number.

What to do next

If you be make changes to an already existing configuration, ensure thedataLoad.env file contains all the right settings:1. Change to the directory where DataLoad is installed. For example:

cd /opt/dataload


3. Make sure that DL_HA_MODE field in the dataLoad.env file and set toDL_HA_MODE=true.

4. Make sure that DL_HA_MODE_1 field in the dataLoad.env file and set toDL_HA_MODE_1=true.



Add the managed definitionsA managed definition allows the HAM to bind a collector profile to a collectorprocess.

About this task

Note: When you add a managed definition to a HAM cluster, the associatedcollector process is automatically added to the cluster's Collector Processes folder.

To add a managed definition to a HAM cluster:

Procedure1. In the Logical view, right-click the Managed Definitions folder that you

created in “Create the HAM and a HAM cluster” on page 207.2. Select Add Managed Definition from the pop-up menu.

The Add Managed Definition - Choose Managed Definition dialog appears.3. In the Collector number field, select the unique collector number to associate

with this managed definition.4. Click Finish.

The following entries now appear for the cluster:v Under the cluster's Managed Definitions folder, the entry Managed

Definition < n > appears, where n is the collector number you selected inStep 3.

v Under the cluster's Collector Processes folder, the entry Collector Process[HostName] appears, where HostName is the host that will be bound to theSNMP collector you selected in Step 3. This host is the managed definition'sprimary host.

Note: Repeat Step 1 though to Step 4 to add another managed definition to thecluster.

Example

When you finish adding managed definitions for a 3+1 HAM cluster, the Logicaland Physical views might look like the following:


In this example, the hosts dcsol1a, dcsol1b, and docserver1 are the primaries, anddocserver2 is the designated spare.

Define the resource poolsA resource pool is a list of the spares, in priority order, that the HAM can bind to aparticular managed definition.

About this task

When you create a managed definition, the managed definition's primary host isthe only host in its resource pool. To enable the HAM to bind a manageddefinition to other hosts, you must add more hosts to the managed definition'sresource pool.

To add hosts to a managed definition's resource pool:

Procedure1. Right-click a managed definition in the cluster's Managed Definitions folder.2. Select Configure Managed Definition from the pop-up menu.

The Configure Managed Definition - Collector Process Selection dialog appears,as shown below. In this example, the resource pool being configured is forManaged Definition 1 (that is, the managed definition associated with Collector1).


3. In the Additional Collector Processes list, check the box next to each host toadd to the managed definition's resource pool.Typically, you will add at least the designated spare (in this example,docserver2) to the resource pool. If you add a primary host to the resourcepool, that host becomes a floating spare for the managed definition.

Note: You must add at least one of the hosts in the Additional CollectorProcesses list to the resource pool.Since the goal in this example is to configure all primaries as floating spares,the designated spare and the two primaries (docserver1 and dcsol1a) will beadded to the resource pool.

4. When finished checking the hosts to add to the resource pool, click Next.

Note: If you add just one host to the resource pool, the Next button is notenabled. Click Finish to complete the definition of this resource pool. Return toStep 1 to define a resource pool for the next managed definition in the cluster,or skip to “Save and start the HAM” on page 212 if you are finished definingresource pools.The Configure Managed Definition - Collector Process Order dialog appears, asshown below:


5. Specify the failover priority order for this managed definition. To do so:a. Select a host to move up or down in the priority list, then click the Up or

Down button until the host is positioned where you want.b. Continue moving hosts until the priority list is ordered as you want.c. Click Finish.In this example, if the primary associated with Managed Definition 1 fails, theHAM will attempt to bind the managed definition to the floating spare dcsol1a.If dcsol1a is in use or otherwise unavailable, the HAM attempts to bind themanaged definition to docserver1. The designated spare docserver2 is last inpriority.

6. Return to Step 1 to define a resource pool for the next managed definition inthe cluster, or continue with the next section if you are finished definingresource pools.

Save and start the HAMWhen you finish configuring the HAM as described in the previous sections, youare ready to save the configuration and start the HAM.

About this task

To save and start the HAM:

Procedure1. Click Topology > Save Topology to save the topology file containing the HAM

configuration.2. Run the deployer (see “Starting the Deployer” on page 164), passing the

updated topology file as input.3. Open a terminal window on the DataChannel host.4. Log in as pvuser.5. Change your working directory to the DataChannel bin directory

(/opt/datachannel/bin by default), as follows:cd /opt/datachannel/bin

6. Bounce (stop and restart) the Channel Manager. For instructions, see Step 15 onpage 111.

7. Run the following command:dccmd start ham


Monitoring of the HAM environment begins.For information on using dccmd, see Tivoli Netcool Performance ManagerCommand Line Interface.

Creating an additional HAM environmentHow to create a HAM environment.

Typically, one HAM is sufficient to manage all the collectors you require in yourHAM environment. But for performance reasons, very large Tivoli NetcoolPerformance Manager deployments involving dozens or hundreds of collectorprocesses might benefit from more than one HAM environment.

HAM environments are completely separate from one another. A host in one HAMenvironment cannot fail over to a host in another HAM environment.

To create an additional HAM environment, perform all of the procedures describedin “Creating a HAM environment” on page 206.

Modifying a HAM environmentHow to modify a HAM environment.

You can modify a HAM environment by performing any of the procedures in“Creating a HAM environment” on page 206. For example, you can add collectors,add clusters, configure a primary host as a floating spare, change the failoverpriority order of a resource pool, and make a number of other changes to theenvironment, including moving collectors into or out of a HAM environment.

For information on moving a deployed SNMP collector into or out of a HAMenvironment, see “Moving a deployed SNMP collector to or from a HAMenvironment” on page 185.

You can also modify the configuration parameters of the HAM components thatare writable. For information on modifying configuration parameters, see“Changing configuration parameters of existing Tivoli Netcool PerformanceManager components” on page 182.

Removing HAM componentsHow to remove HAM components.

You can remove HAM components from the environment by right-clicking thecomponent name and selecting Remove from the pop-up menu. The selectedcomponent and any subcomponents will be removed. When you remove SNMPspare from a host, ensure that it is a SNMP component and check if it is the last(SNMP and SNMP Spare) on the host.If the collector is the last SNMP collector on that host:1. Click Remove in the Logical View and save the topology.2. Click Run > Run Deployer for Uninstallation.

If the collector is not the last SNMP collector on original host:3. Click Remove in the Logical View and save the topology.4. Click Run > Run Deployer for Installation.5. Set the DL_HA_MODE field in the dataLoad.env file to FALSE.6. Source the DataLoad environment again:


. ./dataLoad.env

Before you can remove a designated spare (Collection Process SNMP Spare), youmust remove the spare from any resource pools it may belong to. To remove adesignated spare from a resource pool, open the managed definition that containsthe resource pool, and clear the check box next to the name of the designated spareto remove. For information about managing resource pools, see “Define theresource pools” on page 210

Stopping and restarting modified componentsHow to stop and restart modified components.

About this task

If you change the configuration of a HAM or any HAM components, or if you addor remove an existing collector to or from a HAM environment, you must bounce(stop and restart) the Tivoli Netcool Performance Manager components youchanged The is generally true for all Tivoli Netcool Performance Managercomponents that you change, not just HAM.

To bounce a component:

Procedure1. Open a terminal window on the DataChannel host.2. Log in as pvuser.3. Change your working directory to the DataChannel bin directory

(/opt/datachannel/bin by default), as follows:cd /opt/datachannel/bin

4. Run the bounce command in the following format:dccmd bounce <component>

For example:v To bounce the HAM with the identifier HAM.dcsol1b.1, run:

dccmd bounce ham.dcsol1b.1

v To bounce all HAMs in the topology, run:dccmd bounce ham.*.*

v To bounce the FTE for collector 1.1 that is managed by a HAM, run:dccmd bounce fte.1.1

You do not need to bounce the HAM that the FTE and collector are in.For information on using dccmd, see Tivoli Netcool Performance ManagerCommand Line Interface.

5. Bounce the Channel Manager. For instructions, see Step 15.


Viewing the current configurationDuring the process of creating or modifying a HAM cluster, it is useful to checkhow the individual collector processes and managed definitions are currentlyconfigured.

About this task

To view the current configuration of a collector process or managed definition:

Procedure1. Right-click the collector process or managed definition to view.2. Select Show from the menu.

The Show Collector Process... or Show Managed Definition... dialog isdisplayed. The following sections describe the contents of these dialogs.

Show Collector Process... dialogDialog box description.

The following figure shows a collector process configured with three manageddefinitions.

The configuration values are described as follows:v dcsol1a. The primary host where this collector process runs.v 3002. The port through which the collector process receives SNMP data.v 3 2 (Primary) 1. The managed definitions that the HAM can bind to this

collector process. The values have the following meanings:– 3. The managed definition for Collector 3.– 2 (Primary). The managed definition for Collector 2. This is the default

managed definition for the collector process.– 1. The managed definition for Collector 1.


Show Managed Definition... dialogDialog box description.

The Show Managed Definition... dialog contains the resource pool for a particularmanaged definition.

This dialog contains the same information that appears in the Show CollectorProcess... dialog, but for multiple hosts instead of just one. As such, this dialoggives you a broader view of the cluster's configuration than a Show ManagedDefinition... dialog.

The following figure shows a managed definition's resource pool configured withfour hosts:

Note the following about this managed definition's resource pool:v The priority order of the hosts is from top to bottom - therefore, the first

collector process that the HAM will attempt to bind to this managed definitionis the one on host dcsol1a. The collector process on host docserver2 is last in thepriority list.

v The first three hosts are floating spares. They are flagged as such by each havinga primary managed definition.

v The host docserver2 is the only designated spare in the resource pool. It isflagged as such by not having a primary managed definition.


Chapter 10. Uninstalling components

Provides information on how to uninstall components.

When you perform an uninstall, the "uninstaller" is the same deployer used toinstall Tivoli Netcool Performance Manager.

Removing a component from the topologyHow to remove an installed component from the topology.

You might have a situation where you have modified a topology by both addingnew components and removing components (marking them "To Be Removed").However, the deployer can work in only one mode at a time - installation mode oruninstallation mode. In this situation, first run the deployer in uninstallation mode,then run it again in installation mode, except when you are uninstalling dataload.See, “Restrictions and behavior” for Dataload restrictions.

Note: After the deployer has completed an uninstall, you must open the topology(loaded from the database) in the Topology Editor before performing anyadditional operations.

Uninstallation of HAM is not supported on IBM Tivoli Netcool PerformanceManager, Version 1.4.3.

Restrictions and behaviorRestrictions and behavior to observe when you perform an uninstall.

Before you remove a component, note the following information:v You can remove a component from the topology if you have uninstalled the

components that depend on it. To uninstall a component, you must remove itfrom the topology and then run the deployer in uninstall mode and run theactions related to uninstalling the component.

v You can remove a host only if no components are configured or installed on it.v If you remove a component and redeploy the file, the Topology Editor view is

not refreshed automatically. Reload the topology file from the database to viewthe updated topology.

Note: After the components are marked for deletion, the topology must beconsumed by the deployer to propagate the required changes and load theupdated file in the database. When you open the database version of the topology,the "removed" component disappears from the topology.

To remove one or more components from the topology where the host system nolonger exists or is unreachable on the network, do the following steps:


1. Open the Topology Editor and remove all components that are related to thehost system

2. Remove the host system from the topology3. Redeploy the topology, ignoring any messages that are related to the

non-existent or unreachable host.4. At deployment, the modified topology is saved to the database without the

components that were previously installed on the host system.

Note: After the manual uninstall is completed, the DataView instance will remainin the topology after the uninstall operation completes, this is not usually the casefor uninstalled components.

DataLoad restrictionsv If you are removing SNMP/Spare collectors that are installed on host, such that

it is not the last SNMP/Spare collectors, then after you make changes to theTopology, save it and always Run the deployer for Installation option.

v If you are removing the last SNMP/Spare collector, or all the SNMP/Sparecollectors on a host, then after you make changes to the Topology, save it andalways Run the deployer for Uninstallation option.

v You must not remove all SNMP/Spare collectors on a host and addSNMP/Spare collectors to the same host in one step. If you want to remove andadd collectors on a host, first remove all collectors on the host, and then Savetopology. Run for Uninstallation and reopen topology from database. Addcollectors on that host, Save topology, and then Run for Installation.

DataChannel restrictionsv You can remove the DataChannel Administrative Component only after all the

DataChannels have been removed.v If you are uninstalling a DataChannel component, the component must first be

stopped. If you are uninstalling all DataChannel components on a host, then youmust remove the DataChannel entries from the crontab.

v If you delete a DataChannel or collector, the working directories (such as theFTE and CME) are not removed; you must delete these directories manually.

v When a Cross-Collector CME (CC-CME) is installed on the system and formulasare applied against it, the removal of collectors that the CC-CME depends on isnot supported. It is an exceptional case, that is, if you have not installed aCC-CME, collectors can be removed.

DataView restrictions

Uninstall DataView manually if other products are installed in the same DashboardApplication Services Hub instance. Use the following procedure to uninstall aDataView component:1. Run the uninstall command:

/opt/IBM/JazzSM/products/tnpm/dataview/bin/uninstall.sh /opt/IBM/JazzSM<DASH_administrator_username> <DASH_administrator_password>

2. Remove the DataView directory:rm -rf /opt/IBM/JazzSM/products/tnpm/dataview

In the Topology Editor:3. Remove the DataView component.4. Save the topology.


5. Run the deployer for uninstallation.6. Mark the DataView step successful.7. Run the unregister DataView step.

Important: Delete all the existing Tivoli Netcool/OMNIbus Web GUI integrationdashboard pages before you run the uninstallation script. Otherwise, theuninstallation might fail with the following error message:GYMVC0001E: Error occurred: com.ibm.ws.scripting.ScriptingException:com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for isc failed:see previous messages for details.

Removing a componentTo remove component from the topology.


Editor” on page 146).2. Open the existing topology (see “Opening a deployed topology” on page 179).3. In the Logical view of the Topology Editor, right-click the component you want

to delete and select Remove from the pop-up menu.4. The editor marks the component as To Be Removed and removes it from the

display.5. Save the updated topology.6. Run the deployer (see “Starting the Deployer” on page 164).

Note: If you forgot to save the modified topology, the deployer will promptyou to save it first.The deployer can determine that most of the components described in thetopology file are already installed, and removes the component that is nolonger part of the topology.

7. The deployer displays the installation steps page, which lists the steps requiredto remove the component. Note that the name of the component to be removedincludes the suffix "R" (for "Remove"). For example, if you are deleting aDataChannel, the listed component is DCR.

8. Click Run All to run the steps needed to delete the component.9. When the installation ends successfully, the deployer uploads the updated

topology file into the database. Click Done to close the wizard.

Note: If you remove a component and redeploy the file, the Topology Editorview is not refreshed automatically. Reload the topology file from the databaseto view the updated topology.

What to do next

If you have uninstalled DataChannel Components, you need to bounce CMGRafter you have run the deployer, so that it picks up the updated configuration andrealize the components have been removed. If you do not bounce CMGR after thedeployer runs then you get errors when the components are restarted.

Chapter 10. Uninstalling components 219

Removing multiple collectorsRemoving all SNMP and spare collectors on a host.


Editor” on page 146).2. Open the existing topology (see “Opening a deployed topology” on page 179).3. In the Logical view of the Topology Editor, right-click the SNMP collector or

spare collector you want to delete and select Remove from the pop-up menu.4. Repeat step 2 for all SNMP collectors and spare collectors on the host that you

want to remove.5. Save the updated topology.

If there are no more SNMP or Spare collectors remaining on host:6. Save Topology, and then click Run > Run Deployer for Uninstallation.

If there are SNMP or Spare collectors installed on host even after removingsome collectors:

7. Save Topology, and then click Run > Run Deployer for Installation.

Uninstalling the entire Tivoli Netcool Performance Manager systemHow to uninstall the entire system.

To uninstall Tivoli Netcool Performance Manager, you must have the CD or theoriginal electronic image. The uninstaller will prompt you for the location of theimage.

Order of uninstallThe order in which you must uninstall components.

About this task

For all deployments, you must use the Topology Editor to uninstall the TivoliNetcool Performance Manager components in the following order:

Procedure1. DataLoad and DataChannel

When uninstalling DataChannel from a host, you must run ./dccmd stop all,disable, or delete the dataload cron processes and manually stop (kill -9) anyrunning channel processes (identified by running findvisual). For moreinformation about the findvisual command, see Appendix B, “DataChannelarchitecture,” on page 231

2. DataMart3. DataChannel Administrative Components and any remaining DataChannel

components.4. DataView5. Tivoli Netcool Performance Manager Database (remove only after all the other

components have been removed). The database determines the operatingplatform of the Tivoli Netcool Performance Manager environment.


Important: From the deployer installation steps page, run only the UninstallProviso Database step. User can ignore Load Channel Configuration, andLoad Collector Configuration steps.

Note: An error message is seen when user clicks Done, to close the deployerwizard.

User can ignore the error, click OK to proceed to close the deployer wizard.

Restrictions and behaviorBefore you uninstall Tivoli Netcool Performance Manager you must note thefollowing restrictions and behavior:v If you need to stop the uninstallation before it is complete, you can resume it.

The uninstaller relies on the /tmp/ProvisoConsumer directory to store theinformation needed to resume an uninstall. However, if the ProvisoConsumerdirectory is removed for any reason, the -Daction=resume command will notwork.

Note: When you reboot your server, the contents of /tmp might get cleaned out.v When you run the uninstaller, it finds the components that are marked as

"Installed", marks them as "To Be Removed", then deletes them in order. Thedeployer is able to determine the correct steps to be performed. However, if thecomponent is not in the Installed state (for example, the component was notstarted), the Topology Editor deletes the component from the topology - not theuninstaller.

v When the uninstallation is complete, some data files still remain on the disk. Youmust remove these files manually. See “Removing residual files” on page 223 forthe list of files that must be deleted manually.

v If you are not removing the last collector on a host, it is recommended that youfirst remove the other components on the host. Save topology. Run forUninstallation. To remove collectors, see, “Removing multiple collectors” onpage 220.

Performing the uninstallHow to uninstall the Tivoli Netcool Performance Manager installation.

Before you begin

The unistall procedure assumes that you update the topology file:1. If it is not already open, open the Topology Editor (see “Starting the Topology

Editor” on page 146).2. Open the existing topology (see “Opening a deployed topology” on page 179).3. In the Logical view of the Topology Editor, right-click each component that you

want to delete and select Remove from the menu.4. The editor marks all components that you selected for removal as To Be

Removed and removes it from the display.5. Save the updated topology.

About this task

To remove a Tivoli Netcool Performance Manager installation:


Procedure1. You can start the uninstaller from within the Topology Editor or from the

command line.To start the uninstaller from the Topology Editor:v Select Run > Run Deployer for Uninstallation.To start the uninstaller from the command line:a. Log in as root.b. Set and export your DISPLAY variable (see “Setting up a remote X Window

display” on page 65).c. Change directory to the directory that contains the deployer. For example:

# cd /opt/IBM/proviso/deployer

d. Enter the following command:# ./deployer.bin -Daction=uninstall

2. The uninstaller opens, displaying a welcome page. Click Next to continue.3. Accept the default location of the base installation directory of the database

JDBC driver:

v - /opt/oracle/product/12.1.0-client32/jdbc/lib)

v - /opt/db2/product/11.1.0/java

Or click Choose to browse to another directory. Click Next to continue. Adialog opens, asking whether you want to load a topology from disk.

4. Click No.A dialog box opens asking for you to enter the details of the updated topologyfile.

5. Enter the name of the topology file you updated as described in the "Beforeyou begin" section.

6. The database access window prompts for the security credentials. Enter thehost name (for example, delphi) and database administrator password (forexample, PV), and verify the other values (port number, SID or DB_NAME, anduser name). Click Next to continue. The topology as stored in the database isthen compared with the topology loaded from the file.

7. The uninstaller displays several status messages, and then displays a messagestating that the environment status was successfully downloaded and saved tothe file /tmp/ProvisoConsumer/Discovery.xml. Click Next to continue.

8. Repeat the process on each system in the deployment.

Note: After the removal of each component by using the Topology Editor, youmust reload the topology from the Database.

Uninstalling the Topology EditorHow to uninstall the Topology Editor.

About this task

To uninstall the Topology Editor, follow the instructions in the section. Do notdelete the /opt/IBM directory. Doing so causes problem when you try to reinstallthe Topology Editor. If the /opt/IBM directory is accidentally deleted, do theworkaround that is documented in “Installing the Topology Editor” on page 144.


Note: Uninstall Tivoli Netcool Performance Manager before you uninstall theTopology Editor.

To uninstall the Topology Editor:

Procedure1. Log in as root.2. Set and export your DISPLAY variable (see “Setting up a remote X Window

display” on page 65).3. Change directory to the install_dir/uninstall directory. For example:

# cd /opt/IBM/proviso/uninstall

4. Enter the following command:#./Uninstall_Topology_Editor

5. The uninstall wizard opens. Click Uninstall to uninstall the Topology Editor.6. When the script is finished, click Done.

Note: Uninstalling Topology Editor will not remove the *.txt language filesfrom /opt/IBM/proviso/license. It needs to be manually removed.

Removing residual filesHow to remove the possible residual files that may exist after the uninstall process.

About this task

When you uninstall Tivoli Netcool Performance Manager, some of the files remainon the disk and must be removed manually. After you exit from the deployer (inuninstall mode), you must delete these residual files and directories manually.

Perform the following steps:

Procedure1. Log in as database instance name. For example, oracle for Oracle and db2 for

DB2.2. Enter the following commands to stop:

sqlplus "/ as sysdba"shutdown abortexitlsnrctl stop

db2stop force

3. As root, enter the following commands to delete these files and directories:


Table 18. Oracle and IBM DB2 commands to delete these files and directories

rm -fR /tmp/PvInstallrm -fR /var/tmp/PvInstallrm -fR /opt/Provisorm -fR /opt/provisorm -fR $ORACLE_BASE/admin/PVrm -fR $ORACLE_BASE/admin/skeletonrm -fR $ORACLE_HOME/dbs/initPV.orarm -fR $ORACLE_HOME/dbs/lkPVrm -fR $ORACLE_HOME/dbs/orapwPVrm -fR $ORACLE_HOME/lib/libpvmextc.sorm -fR $ORACLE_HOME/lib/libmultiTask.sorm -fR $ORACLE_HOME/lib/libcmu.sorm -fR $ORACLE_HOME/bin/snmptraprm -fR $ORACLE_HOME/bin/notifyDBSpacerm -fR $ORACLE_HOME/bin/notifyConnectionrm -rf /tmp/import_chnl_reg.udef.log

rm -fR /tmp/PvInstallrm -fR /var/tmp/PvInstallrm -fR /opt/Provisorm -fR /opt/provisorm -fR $DB2_BASE/tnpm_dbadminrm -fR $DB2_BASE/create_db.inirm -fR $DB2_BASE/sqllib/function/libpvmextc.sorm -fR $DB2_BASE/sqllib/function/libmultiTask.sorm -fR $DB2_BASE/sqllib/function/libcmu.sorm -fR $DB2_BASE/tnpm_dbadmin/db2/bin/snmptraprm -fR $DB2_BASE/tnpm_dbadmin/db2/bin/notifyDBSpacerm -fR $DB2_BASE/tnpm_dbadmin/db2/bin/notifyConnectionrm -rf /tmp/import_chnl_reg.udef.log

where:v $ORACLE_BASE: /opt/oraclev $DB2_BASE: /opt/db2 andv $ORACLE_HOME: /opt/oracle/product/12.1.0v $DB2_HOME: /opt/db2/opt/db2/product/11.1.0

4. Enter the following commands to clear your database mount points andremove any files in those directories:

Table 19. Commands to clear your Oracle or DB2 mount points

rm -r /raid_2/oradata/*rm -r /raid_3/oradata/*

rm -fR /raid_2/db2data/*rm -fR /raid_3/db2data/*

5. Enter the following command to delete the temporary area used by thedeployer:rm -fr /tmp/ProvisoConsumer

6. Delete the installer file using the following command:rm /var/.com*

7. Delete the startup file, netpvmd.

v For use the command:rm /etc/init.d/netpvmd

v For AIX, use the command:rm /etc/rc.d/init.d/netpvmd

v For Linux, use the command:rm /etc/init.d/netpvmd

Note: The netpvmd startup and stop files are also present in /etc/rc2.d and/etc/rc3.d as S99netpvmd and K99netpvmd. These files must also be removed.


What to do next

Following Tivoli Common Reporting uninstallation:

To prevent any possible system instability caused by residual processespost-uninstall of Tivoli Common Reporting, run thetcr Clean.sh script on allsystems where Tivoli Common Reporting is uninstalled:1. On the host where the Tivoli Common Reporting installation failed, change to

the directory containing tcr Clean.sh:cd /opt/IBM/proviso/deployer/proviso/bin/Util/

2. Run tcr Clean.sh3. When prompted, enter the location where Tivoli Common Reporting was

installed.

Note: If you have uninstalled Tivoli Common Reporting on a remote host, thetcrClean.sh file is sent by using ftp to the remote host for execution.



Appendix A. Remote installation issues

Remote installation of all Tivoli Netcool Performance Manager components issupported.

A remote installation refers to installation on any host that is not the primarydeployer, that is, the host running the Topology Editor. For some systems, securitysettings may not allow for components to be installed remotely. Before deployingon such a system, you must be familiar with the information in this appendix.

When remote install is not possibleWhat to do when remote installation is not possible.

There may arise situations where a remote host does not support FTP or theremote execution of files.

A remote host may not support FTP or the remote execution of files.

It is possible your topology may include hosts one which:v FTP is possible, but REXEC/RSH are not.v Neither FTP nor REXEC/RSH are possible

This section describes how to deploy in these situations.

FTP is possible, but REXEC or RSH are notIn situations where FTP is possible but remote execution or remote shell are not.

About this task

For any remote host where FTP is possible, but REXEC or RSH are not,deployment of the required component or components must be carried out usingthe following steps.

There are two options for deployment.

Procedurev Option 1:

1. Unselect the Remote Command Execution option during the installation. Thedeployer creates and transfers the directory with the required componentpackage in it.

2. As root, log in to the remote system and manually run the run.sh script.v Option 2:

Follow the directions outlined in “Installing on a remote host by using asecondary deployer” on page 228.


Neither FTP nor REXEC/RSH are possibleIn situations where FTP, remote execution and remote shell are not possible.

About this task

For any remote host where neither FTP nor REXEC or RSH are possible thedeployment of the required component or components must be carried out usingthe following steps.

There are two options for deployment.

Procedurev Option 1:

1. Unselect the FTP option during the installation. The deployer creates adirectory containing the required component package.

2. Copy the required component directory to the target system.3. As root, log in to the remote system and manually run the run.sh script.

v Option 2:Follow the directions outlined in “Installing on a remote host by using asecondary deployer.”

Installing on a remote host by using a secondary deployerThe general procedure for installing a component on a remote host by using asecondary deployer.

About this task

A secondary deployer is used when the host you want to install on does notsupport remote installation.

The following steps describe how to install a Tivoli Netcool Performance Managercomponent by using a secondary deployer. For the purpose of clarity, name theprimary deployer host as delphi, and the host on which you want to install acomponent by using the secondary deployer that you can name corinth.

Procedure1. Copy the Tivoli Netcool Performance Manager distribution to the server on

which you would like to set up the secondary deployer, that is, copy thedistribution to corinth. For more information about copying the Tivoli NetcoolPerformance Manager distribution to a server, see “Downloading the TivoliNetcool Performance Manager distribution to disk” on page 83.

2. Open the Topology Editor on the primary deployer host, that is, on delphi, andadd the remote component to the topology definition.You must complete this task already when you create your original topologydefinition. If you already have added the remote component to your topologydefinition, skip to the next step.

3. Deploy the new topology that contains the added component by using theTopology Editor. You can do this by clicking Run> > Run Deployer forInstallation. This pushes the edited topology to the database.

4. Do the following, to open the Deployer on corinth:


a. Connect to corinth, change to the directory where you download theproduct distribution, and start the deployer either in graphical mode (bystarting the Launchpad and clicking Start Deployer) or CLI mode (bybrowsing to the directory that contains the deployer and entering thecommand ./deployer.bin).

b. Enter the database credentials when prompted. The deployer connects tothe database.For more information about how to run a secondary deployer, see“Secondary Deployers” on page 165.

Note: The secondary deployer sees the topology data and knows that therequired component is still to be installed on corinth when you do step 3.

5. Follow the on screen instructions to install the wanted component.

Note: You cannot start the deployer simultaneously from two different hosts.Only one deployer can be active at one time.

Appendix A. Remote installation issues 229


Appendix B. DataChannel architecture

Provides detailed information about the DataChannel architecture.

Data collectionDataChannel data collection.

A Tivoli Netcool Performance Manager DataChannel consists of a number ofcomponents, including the following:v File Transfer Engine (FTE)v Complex Metric Engine (CME)v Daily Database Loader (DLDR)v Hourly Database Loader (LDR)v Plan Builder (PBL)v Channel Manager

The FTE, DLDR, LDR, and PBL components are assigned to each configuredDataChannel. The FTE and CME components are assigned to one or moreCollector subchannels.

Data is produced by Tivoli Netcool Performance Manager DataLoad Collectors.Both SNMP and BULK Collectors are fed into a subchannel's channel processor.Data moves through the CME and is synchronized in the Hourly Loader. TheHourly Loader computes group aggregations from resource aggregation records.The Daily Loader provides statistics on metric channel tables and metrictablespaces and inserts data into the database.

Data is moved from one channel component to another as files. These files arewritten to and read from staging directories between each component. Within eachstaging directory there are subdirectories named do, output, and done. The dosubdirectory contains files that are waiting to be processed by a channelcomponent. The output subdirectory stores data for the next channel component towork on. After files are processed, they are moved to the done directory. All filemovement is accomplished by the FTE component.

Data aggregationA DataChannel aggregates data collected by collectors for eventual use byDataView reports.

The DataChannel provides online statistical calculations of raw collected data, anddetects real-time threshold violations.

Aggregations include:v Resource aggregation for every metric and resourcev Group aggregation for every groupv User-defined aggregation computed from raw data

Threshold detections in real time include:v Raw data violating configured thresholds


v Raw data violating configured thresholds and exceeding the threshold during aspecific duration of time

v Averaged data violating configured thresholds

Management programs and watchdog scriptsLists the names and corresponding watchdog scripts for the DataChannelmanagement programs.

The following table lists the names and corresponding watchdog scripts for theDataChannel management programs running on different DataChannel hosts.

Table 10: Programs and Scripts

Component Program Executable*Corresponding

Watchdog Script Notes

Channel NameServer

CNS cnsw Runs on the hostrunning the ChannelManager.Log Server LOG logw

Channel Manager CMGR cmgrw

Application Manager AMGR amgrw One per subchannelhost and one on theChannel Managerhost.

* The actual component's executable file seen in the output of ps -ef is named XXX_visual ,where XXX is an entry in this column. For example, the file running for CMGR is seen asCMGR_visual.

The watchdog scripts run every few minutes from cron. Their function is tomonitor their corresponding management component, and to restart it if necessary.You can add watchdog scripts for the Channel Manager programs to the crontabfor the pvuser on each host on which you installed a DataChannel component.

To add watchdog scripts to the crontab:1. Log in as pvuser. Make sure this login occurs on the server running the

Channel Manager components.2. At a shell prompt, go to the DataChannel conf subdirectory. For example:

$ cd /opt/datachannel/conf

3. Open the file dc.cron with a text editor. (The dc.cron files differ for differenthosts running different DataChannel programs. The following example showsthe dc.cron file for the host running the Channel Manager programs.)

0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6 /opt/datachannel/bin/cnsw> /dev/null 2>&11,6,11,16,21.26,31,36,41,46,51,56 1-31 1-12 0-6 /opt/datachannel/bin/logw> /dev/null 2>&12,7,12,17,22.27,32,37,42,47,52,57 1-31 1-12 0-6 /opt/datachannel/bin/cmgrw> /dev/null 2>&13,8,13,18,23.28,33,38,43,48,53,58 1-31 1-12 0-6 /opt/datachannel/bin/amgrw> /dev/null 2>&1

4. Copy the lines in the dc.cron file to the clipboard.5. At another shell prompt, edit the crontab for the current user.


export EDITOR=vicrontab -e

A text editor session opens, showing the current crontab settings.6. Paste the lines from the dc.cron tab into the crontab file. For example:

0 * * * * [ -f /opt/datamart/dataMart.env ] && [ -x /opt/datamart/bin/pollinv ]&& ....0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6 /opt/datachannel/bin/cnsw >

/dev/null 2>&11,6,11,16,21,26,31,36,41,46,51,56 1-31 1-12 0-6 /opt/datachannel/bin/logw >

/dev/null 2>&12,7,12,17,22,27,32,37,42,47,52,57 1-31 1-12 0-6 /opt/datachannel/bin/cmgrw >

/dev/null 2>&13,8,13,18,23,28,33,38,43,48,53,58 1-31 1-12 0-6 /opt/datachannel/bin/amgrw >

/dev/null 2>&1

7. Save and exit the crontab file.8. Repeat steps 1 to 8 on each DataChannel host, with this difference:

The dc.cron file on collector and loader hosts will have only one line, like thisexample:

0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6/opt/datachannel/bin/amgrw > /dev/null 2>&1

On such hosts, this is the only line you need to add to the pvuser crontab.

DataChannel application programsDataChannel Application Program names and descriptions.

The DataChannel subchannel application programs are listed in Table 11.

Table 11: DataChannel Subchannel Application Program Names

DataChannel Program* Description Example

BCOL.n.c Bulk Collector process forchannel n, with Collectornumber c

BCOL.1.2

UBA.n.c UBA Bulk Collector processfor channel n, with Collectornumber c

UBA.1.100

CME.n.s Complex Metric Engine forchannel n, Collector numbers

CME.2.1

DLDR.n Daily Loader for channel n DLDR.1

LDR.n Hourly Loader for channel n LDR.2

FTE.n. File Transfer Engine forchannel n

FTE.1.1

PBL.n. Plan Builder for channel n PBL.1

* The actual application's executable file visible in the output of ps -ef is namedXXX_visual, where XXX is an entry in this column.

Note: For historical reasons, the SNMP DataLoad collector is managed by TivoliNetcool Performance Manager DataMart, and does not appear in Table 11.

Appendix B. DataChannel architecture 233

Starting the DataChannel management programsHow to check if DataChannel management programs are running and then startapplication programs.

Procedurev Verify that the DataChannel management programs are running:

1. Log in as pvuser on each DataChannel host.2. Change to the DataChannel installation's bin subdirectory. For example:

$ cd /opt/datachannel/bin

3. Run the findvisual command:$ ./findvisual

In the resulting output, look for:– The AMGR process on every DataChannel host– The CNS, CMGR, LOG, and AMGR processes on the Channel Manager

hostv If the DataChannel management programs are running on all DataChannel

hosts, start the application programs on all DataChannel hosts by followingthese steps:1. Log in as pvuser. Make sure this login occurs on the host running the

Channel Manager programs.2. Change to the DataChannel installation's bin subdirectory. For example:


3. Run the following command to start all DataChannel applications on allconfigured DataChannel hosts:./dccmd start all

The command shows a success message like the following example.

Done: 12 components started, 0 components already running

See the Command Line Interface Reference for information about the dccmdcommand.

There is a Java process associated with the LOG server that must be stoppedshould the proviso.log need to be re-created:1. To find this Java process, enter the following:

ps -eaf | grep LOG

The output should be similar to the following:pvuser 15774 15773 0 Nov 29 ?7:59 java -Xms256m -Xmx384m com.ibm.tivoli.analytics.Main -a LOG

2. Kill this process using the command:kill -9 15774

15774 - is the pid of the Java process as discovered using the grep command.3. Restart the LOGW process.


Starting the DataLoad SNMP collectorHow to start the DataLoad SNMP Collector

About this task

Once you have started the DataChannel components, check every server that hostsa DataLoad SNMP collector. to make sure the collectors are running. To checkwhether a collector is running, run the following command:ps -ef | grep -i pvmd

If the collector is running, you will see output similar to the following:pvuser 27118 1 15 10:03:27 pts/4 0:06 /opt/dataload/bin/pvmd -nologo-noherald /opt/dataload/bin/dc.im -headless -a S

If a collector is not running, perform the following steps:

Procedure1. Log into the server that is running Tivoli Netcool Performance Manager SNMP

DataLoad by entering the username and password you specified wheninstalling SNMP DataLoad.

2. Source the DataLoad environment file by entering the following command:./$DLHOME/dataLoad.env

where $DLHOME is the location where SNMP DataLoad is installed on the system(/opt/dataload, by default).

Note: If DataLoad shares the same server as DataMart, make sure you unsetthe environment variable by issuing the following command from a BASH shellcommand line:unset PV_PRODUCT

3. Change to the DataLoad bin directory by entering the following command:cd $PVMHOME/bin

4. Start the DataLoad SNMP collector using the following command:pvmdmgr start

The command displays the following message when the SNMP collector hasbeen successfully started:

PVM Collecting Daemon is running.

Results

The script controlling the starting and stopping of SNMP collectors, pvmdmgr,prevents the possibility that multiple collector instances can be runningsimultaneously.

If a user starts a second instance, that second instance will die by itself in undertwo minutes without ever contacting or confusing the relevant watchdog script.


DataChannel management components in a distributed configurationA description of the DataChannel management components.

Two channels running on the same system share a common Application Manager(AMGR) that has a watchdog script, amgrw. The AMGR is responsible for starting,monitoring through watchdog scripts, and gathering status for each applicationserver process for the system it runs on. Application programs include the FTE,CME, LDR, and DLDR programs.

An example of multiple processes running on the same host is:v Application Manager (AMGR)v Complex Metric Engines (CME)v File Transfer Engines (FTE)v Hourly Data Loaders (LDR)v Daily Data Loaders (DLDR)

Each program has its own set of program and staging directories.

Manually starting the Channel Manager programsIf you need to manually start the Channel Manager programs, you must do so in acertain order.

About this task

After a manual start, the program's watchdog script restarts the program asrequired.

Procedurev To start the Channel Manager programs manually:

1. Log in as pvuser on the host running the Channel Manager programs.2. At a shell prompt, change to the dataChannel/bin subdirectory. For example:


3. Enter the following commands at a shell prompt, in this order:For the Channel Name Server, enter:./cnsw

For the Log Server, enter:./logw

For the Channel Manager, enter:./cmgrw

For the Application Manager, enter:./amgrw

v To manually start the DataChannel programs on all hosts in your DataChannelconfiguration:1. Start the Channel Manager programs, as described in the previous section.2. On each DataChannel host, start the amgrw script.3. On the Channel Manager host, start the application programs as described in

“Starting the DataChannel management programs” on page 234.


Adding DataChannels to an existing systemHow to add DataChannels to an existing system.

About this task

If you add and configure a new remote DataChannel using the Topology Editorafter the initial deployment of your topology, the system will not pick up thesechanges, unless the user manually stop starts the relevant processes, as explainedin Chapter 8, “Modifying the current deployment,” on page 179.

To shut down the DataChannel:

Note: The DataChannel CMGR, CNS, AMGR, and LOG visual processes mustremain running until you have gathered the DataChannel parameters from yourenvironment.

Procedure1. On the DataChannel host, log in as the component user, such as pvuser.2. Change your working directory to the DataChannel bin directory

(/opt/datachannel/bin by default) using the following command: $ cd/opt/datachannel/bin

3. Shut down the DataChannel FTE.Prior to shutting down all DataChannel components, some DataChannel workqueues must be emptied.To shut down the DataChannel FTE and empty the work queues:$ ./dccmd stop FTE.*

4. Let all DataChannel components continue to process until the .../do directoriesfor the FTE and CME components contain no files.The .../do directories are located in the subdirectories of $DCHOME (typically,/opt/datachannel) that contain the DataChannel components - for example,FTE.1.1, CME.1.1.

5. Shut down all CMEs on the same hour (So the operator state files will be insynch with each other). To accomplish this:a. Identify the leading CME by either looking at the do and done directories

in each CME and the DAT files inside there; or using dccmd status all to seewhich CME is reporting the latest hour in its processing status.

b. All CMEs on that hour must be stopped and then continue using the sameapproach to finding the hour being processed and stop each CME as itreaches the same hour until all CMEs are stopped. CMEs are stopped usingthe command:$ ./dccmd stop CME

6. Use the following dccmd commands to stop the DataChannel applications:$ ./dccmd stop DLDR$ ./dccmd stop LDR$ ./dccmd stop FTE$ ./dccmd stop DISC$ ./dccmd stop UBA (if required)

Note: For details on how to restart a DataChannel, see “Manually starting theChannel Manager programs” on page 236.


DataChannel terminologyTerms used throughout the Tivoli Netcool Performance Manager DataChannelinstallation procedure.

Collector SubchannelA subdivision of a DataChannel, with each Collector subchannel associatedwith a single Collector and CME. The division into Collector subchannelshelps eliminate latency or loss of data caused by delayed Collectors. If aCollector subchannel disconnects for a period of time, only that Collector isaffected, and all other Collector subchannels continue processing. Thenumber of Collector subchannels per DataChannel differs according to theneeds of a particular deployment. See the Requirements for informationrelated to system configuration requirements. The terms Collector andCollectors are used to refer to Collector subchannel and Collectorsubchannels.

Complex Metric Engine (CME)A DataChannel program that performs on-the-fly calculations on rawmetrics data for a DataChannel. These calculations include timeaggregations for resources, as well as statistical calculations using raw data,thresholds, properties, and constants as inputs. If CME formulas aredefined for the incoming metrics data, the values are processed by thoseformulas. The CME synchronizes metadata at the beginning of each hour,and only processes the metadata that exists for the hour.

CORBA (Common Object Request Broker Architecture)An industry-standard programming architecture that enables pieces ofprograms, called objects, to communicate with one another regardless ofthe programming language that they were written in or the operatingsystem they are running on.

Daily Database Loader (DLDR)A DataChannel program that gathers statistical data processed by aDataChannel's CME and inserts it into the Tivoli Netcool PerformanceManager database. There is one Daily Loader for each DataChannel; it ispart of the channel processor component of the DataChannel.

DataChannel Remote (DCR)A DataChannel installation configuration in which the subchannel, CMEand FTE components are installed and run on one host, while the Loadercomponents are installed and run on another host. In this configuration,the subchannel hosts can continue processing data and detecting thresholdviolations, even while disconnected from the Channel Manager server.

DataChannel StandardA DataChannel installation configuration in which all component programsof each subchannel are installed and run on the same server. DataChannelStandard installation is described.

DataLoad Bulk CollectorA DataLoad program that processes different data formats and resourcefiles supplied by network devices, network management platforms,network probes, and other types of resources such as BMC Patrol. TheBulk Collector translates bulk statistics provided in flat files into TivoliNetcool Performance Manager metadata and data. If operating insynchronized inventory mode, the Bulk Collector passes the resources andproperties to the Tivoli Netcool Performance Manager DataMart Inventoryapplication.


DataLoad SNMP CollectorA DataLoad program that collects data from network resources via SNMPpolling. The SNMP Collector provides raw data files to the DataChannelfor processing by the CME.

DataLoad UBA Bulk CollectorA DataLoad program that imports data from files (referred to as Bulk inputfiles) generated by non-SNMP devices, including Alcatel 5620 NM, AlcatelSAM, and Cisco CWM. These Bulk input files contain formats that theBulk Collector is unable to handle.

Discovery Server (DISC)A DataChannel program that runs as a daemon to perform an inventory ofSNMP network devices from which to gather statistical data.

Hourly Database Loader (LDR)A DataChannel program that serves as the point of data synchronizationand merging, and of late data processing, for each DataChannel. TheHourly Loader gathers files generated by the CME, computes groupaggregations from the individual resource aggregation records, and loadsthe data into the Tivoli Netcool Performance Manager database.

File Transfer Engine (FTE)A DataChannel program that periodically scans the Collector outputdirectories, examines the global execution plan to determine whichcomputation requests require the data, then sorts the incoming data forstorage.

Next-Hour PolicySpecifies the number of seconds to wait past the hour for files to arrivebefore the next hourly directory is created. The default value causes theDataChannel to wait until 15 minutes after the hour before it startsprocessing data for the next hour. To avoid losing data, you need to set apercentage and a time-out period during the configuration of the CME.

Plan Builder (PBL)A DataChannel program that creates the metric data routing andprocessing plan for the other components in the DataChannel.



Appendix C. Aggregation sets

Describes how to configure and install aggregation sets.

OverviewAn aggregation set is a grouping of network management raw data and computedstatistical information stored in the Tivoli Netcool Performance Manager databasefor a single timezone.

For example, if your company provides network services to customers in both theEastern and Central US timezones, you must configure two aggregation sets.

Because each aggregation set is closely linked with a timezone, aggregation sets aresometimes referred to as timezones in the in Tivoli Netcool Performance Managerdocumentation. However, the two concepts are separate.

Note: "Aggregation set" is abbreviated to "Aggset" in some setup program menus.

Configuring aggregation setsHow to configure aggregation sets.

About this task

When you configure an aggregation set, the following information is stored in thedatabase:v The timezone ID number associated with this aggregation set.v The timezone offset from GMT, in seconds.v Optionally, the dates that Daylight Savings Time (DST) begins and ends in the

associated timezone for each year from the present through 2014. (Or you canconfigure an aggregation set to ignore DST transitions.)

You configure an aggregation set either by creating a new set or by modifying anexisting set. The first aggregation set is installed by default when you install TivoliNetcool Performance Manager Datamart, so if your network will monitor only onetimezone, you need only to configure the existing set.

To configure an aggregation set:

Procedure1. Log in as root. (Remain logged in as root for the remainder of this appendix.)2. At a shell prompt, change to the directory where Tivoli Netcool Performance

Manager DataMart program files are installed. For example:# cd /opt/datamart

3. Load the DataMart environment variables into your current shell'senvironment using the following command:# . ./dataMart.env

4. Change to the bin directory:# cd bin


5. Enter the following command:# ./create_modify_aggset_def

The following menu is displayed:

--------------------------------------------------Tivoli Netcool Performance Manager DatabaseDate: <Current Date> <Current Time>Script name: create_modify_aggset_defScript revision: <revision_number>

- Aggregation set creation- Aggregation set modification- DST configuration for an aggregation set

--------------------------------------------------

Database user................. : [ PV_ADMIN ]Database user password........ : [ ]

Menu :

1. Input password for PV_ADMIN.2. Configure an aggset.0. Exit

Choice : 1

6. Type 1 at the Choice prompt and pressEnter to enter the password forPV_ADMIN. The script prompts twice for the password you set up for PV_ADMIN.

==> Enter password for PV_ADMIN : PV==> Re-enter password : PV

Note: The script obtains the DB_USER_ROOT setting from the Tivoli NetcoolPerformance Manager database configured in previous chapters, andconstructs the name of the Tivoli Netcool Performance Manager databaseadministrative login name, PV_ADMIN, from that base. If you set a differentsetting, the "Database user" entry reflects your settings. For example, if youpreviously set DB_USER_ROOTDB_USER_ROOT=PROV, this script would generate theadministrative login name PROV_ADMIN.

7. To configure the first aggregation set, type 2 at the Choice prompt and pressEnter twice.The script shows the current settings for the aggregation set with ID 0(configured by default):

The following Time Zones are defined into the Database :___________________________________________________________________________________id | Date (in GMT) | offset in | Name | Aggsetstatus

| | seconds | |___________________________________________________________________________________0 | 1970/01/01 00:00:00 | 0 | GMT | Aggset created==> Press <Enter> to continue ....

You can use this aggregation set as-is, or modify it to create a new timezone.8. Press Enter. A list of predefined timezones and their timezone numbers is

displayed:


Num | OffSet | Time zone Name | Short | Long| Hours | | Description | Description___________________________________________________________________________________[ 1] : -10:00 | America/Adak | HAST | Hawaii-Aleutian Standard Time[ 2] : -10:00 | Pacific/Rarotonga | CKT | Cook Is. Time[ 3] : -09:00 | America/Anchorage | AKST | Alaska Standard Time[ 4] : -09:00 | AST | AKST | Alaska Standard Time[ 5] : -08:00 | PST | PST | Pacific Standard Time[ 6] : -07:00 | MST | MST | Mountain Standard Time[ 7] : -06:00 | America/Mexico_City| CST | Central Standard Time[ 8] : -06:00 | CST | CST | Central Standard Time[ 9] : -05:00 | EST | EST | Eastern Standard Time[10] : -04:00 | America/Santiago | CLT | Chile Time[11] : -03:00 | America/Sao_Paulo | BRT | Brazil Time[12] : -01:00 | Atlantic/Azores | AZOT | Azores Time[13] : 000:00 | Europe/London | GMT | Greenwich Mean Time[14] : +01:00 | Europe/Paris | CET | Central European Time[15] : +01:00 | ECT | CET | Central European Time[16] : +02:00 | Africa/Cairo | EET | Eastern European Time[17] : +02:00 | Europe/Helsinki | EET | Eastern European Time[18] : +02:00 | Europe/Bucharest | EET | Eastern European Time[19] : +03:00 | Asia/Baghdad | AST | Arabia Standard Time[20] : +03:00 | Europe/Moscow | MSK | Moscow Standard Time[21] : +04:00 | Asia/Baku | AZT | Azerbaijan Time[22] : +05:00 | Asia/Yekaterinburg | YEKT | Yekaterinburg Time[23] : +06:00 | Asia/Novosibirsk | NOVT | Novosibirsk Time[24] : +07:00 | Asia/Krasnoyarsk | KRAT | Krasnoyarsk Time[25] : +08:00 | Asia/Irkutsk | IRKT | Irkutsk Time[26] : +09:00 | Asia/Yakutsk | YAKT | Yakutsk Time[27] : +10:00 | Australia/Sydney | EST | Eastern Standard Time (NewSouth Wales)[28] : +11:00 | Pacific/Noumea | NCT | New Caledonia Time[29] : +12:00 | Pacific/Auckland | NZST | New Zealand Standard Time[30] : +12:00 | Asia/Anadyr | ANAT | Anadyr Time==> Select Time Zone number [1-30 ] (E : Exit) : 9

9. Type the number of the timezone you want to associate with aggregation set0. For example, type 9 for Eastern Standard Time.The script prompts:

==> Select an Aggset ID to add/modify (E: Exit) : 0

To associate the specified timezone, EST, with the database's defaultaggregation set, type 0.

10. The script asks whether you want your aggregation set to include DaylightSaving Time (DST) transition dates:

Does your Time Zone manage DST [Y/N] : Y

For most time zones, type Y and press Enter.11. The script displays the results:

Appendix C. Aggregation sets 243

Complete with Success ...The following Time Zone has been modified:___________________________________________________________________________________id | Date (in GMT) | offset in | Name | Aggset status

| | seconds | |___________________________________________________________________________________0 | 1970/01/01 00:00:00 | 0 | GMT | Aggset created0 | 2004/09/29 22:00:00 | -14400 | EST_2004_DST | Aggset created0 | 2004/10/31 06:00:00 | -18000 | EST_2004 | Aggset created0 | 2005/04/03 07:00:00 | -14400 | EST_2005_DST | Aggset created0 | 2005/10/30 06:00:00 | -18000 | EST_2005 | Aggset created0 | 2006/04/02 07:00:00 | -14400 | EST_2006_DST | Aggset created0 | 2006/10/29 06:00:00 | -18000 | EST_2006 | Aggset created0 | 2007/04/01 07:00:00 | -14400 | EST_2007_DST | Aggset created0 | 2007/10/28 06:00:00 | -18000 | EST_2007 | Aggset created0 | 2008/04/06 07:00:00 | -14400 | EST_2008_DST | Aggset created0 | 2008/10/26 06:00:00 | -18000 | EST_2008 | Aggset created0 | 2009/04/05 07:00:00 | -14400 | EST_2009_DST | Aggset created0 | 2009/10/25 06:00:00 | -18000 | EST_2009 | Aggset created0 | 2010/04/04 07:00:00 | -14400 | EST_2010_DST | Aggset created0 | 2010/10/31 06:00:00 | -18000 | EST_2010 | Aggset created==> Press <Enter> to continue ....

Note: The dates that appear in your output will most likely be different fromthe dates that appear in the example.

12. Press Enter to return to the script's main menu.13. To configure a second aggregation set, type 2 at the Choice prompt and press

Enter three times.14. Specify the timezone number of your second timezone. For example, type 8 to

specify Central Standard Time.The script prompts:

==> Select an Aggset ID to add/modify (E: Exit) : 1

If you enter a set number that does not exist in the database, the script createsa new aggregation set with that number. Type the next available set number,1.

15. Respond Y to the timezone management query.The script shows the results of creating the second aggregation set:

____________The following Time Zone has been modified :___________________________________________________________________________________id | Date (in GMT) | offset in | Name | Aggset status

| | seconds | |___________________________________________________________________________________1 | 2004/09/29 23:00:00 | -18000 | CST_2004_DST | Aggset created1 | 2004/10/31 07:00:00 | -21600 | CST_2004 | Aggset created1 | 2005/04/03 08:00:00 | -18000 | CST_2005_DST | Aggset created1 | 2005/10/30 07:00:00 | -21600 | CST_2005 | Aggset created1 | 2006/04/02 08:00:00 | -18000 | CST_2006_DST | Aggset created1 | 2006/10/29 07:00:00 | -21600 | CST_2006 | Aggset created1 | 2007/04/01 08:00:00 | -18000 | CST_2007_DST | Aggset created1 | 2007/10/28 07:00:00 | -21600 | CST_2007 | Aggset created1 | 2008/04/06 08:00:00 | -18000 | CST_2008_DST | Aggset created1 | 2008/10/26 07:00:00 | -21600 | CST_2008 | Aggset created1 | 2009/04/05 08:00:00 | -18000 | CST_2009_DST | Aggset created1 | 2009/10/25 07:00:00 | -21600 | CST_2009 | Aggset created1 | 2010/04/04 08:00:00 | -18000 | CST_2010_DST | Aggset created1 | 2010/10/31 07:00:00 | -21600 | CST_2010 | Aggset created==> Press <Enter> to continue ....

16. Press Enter to return to the main menu, where you can add more aggregationsets, or type 0 to exit.


The next step is to install the aggregation sets on the server on which youinstalled Tivoli Netcool Performance Manager DataMart.

Installing aggregation setsHow to install aggregation sets.

When you install DataMart, aggregation set 0 is automatically installed. If youconfigured only the default aggregation set (in “Configuring aggregation sets” onpage 241), you can skip this section. However, if you configured the time zones foradditional aggregation sets, you must install the non-zero sets using the steps inthis section.

Start the Tivoli Netcool Performance Manager setup programHow to start the Tivoli Netcool Performance Manager Setup Program.

About this task

Start the setup program by following these steps:

Procedure1. Make sure your EDITOR environment variable is set.2. Change to the /opt/Proviso directory:

cd /opt/Proviso

3. Start the setup program:./setup

The setup program's main menu is displayed:

Tivoli Netcool Performance Manager <version number> - [Main Menu]1. Install2. Upgrade3. Uninstall0. Exit

Choice [1]> 1

4. Type 1 at the Choice prompt and press Enter. The Install menu is displayed:

Tivoli Netcool Performance Manager <version number> - [Install]1. Tivoli Netcool Performance Manager Database Configuration0. Previous Menu

Choice [1]> 1

Set aggregation set installation parametersHow to set the aggregation set installation parameters.

Procedure1. Type 1 at the Choice prompt and press Enter. Setup displays the installation

environment menu:


Tivoli Netcool Performance Manager Database Configuration <version number> -[installation environment]

1. PROVISO_HOME : /opt/Proviso2. DATABASE_DEF_HOME : -3. CHANNELS_DEF_HOME : -4. AGGRSETS_DEF_HOME : -5. Continue0. Exit

Choice [5]> 5

Note: Menu options 2, 3, and 4 are used later in the installation process.2. Make sure the value for PROVISO_HOME is the same one you used when

you installed the database configuration. If it is not, type 1 at the Choiceprompt and correct the directory location.

3. The script displays the component installation menu:

Tivoli Netcool Performance Manager Database Configuration <version number> -[component installation]

1. Database2. Channel3. Aggregation set0. Exit

Choice [1]> 3

4. Type 3 at the Choice prompt and press Enter. The script displays theinstallation environment menu:

Tivoli Netcool Performance Manager Aggregation Set <version number> -[installation environment]

1. PROVISO_HOME : /opt/Proviso2. DATABASE_HOME : /opt/oracle/product/12.1.0 or /opt/db2/product/11.1.0

3. ORACLE_SID : PV4. DB_USER_ROOT : -5. Continue0. Previous Menu

Choice [5]> 4

5. Type 4 at the Choice prompt and press Enter to specify the same value forDB_USER_ROOT that you specified in previous chapters. This manual'sdefault value is PV.

Enter value for DB_USER_ROOT [] : PV

6. Make sure that the values for PROVISO_HOME, DATABASE_HOME, andORACLE_SID or DB_NAME are the same ones you entered in previouschapters. Correct the values if necessary.

7. Type 5 at the Choice prompt and press Enter. Setup displays the AggregationSet installation options menu:

Tivoli Netcool Performance Manager Aggregation Set <version number> -[installation options]

1. List of configured aggregation sets2. List of installed aggregation sets3. Number of the aggregation set to install : -4. Channel where to install aggregation set : (all)5. Start date of aggregation set : <Current Date>6. Continue0. Back to options menu

Choice [6]>

Note: Do not change the value for option 4. Retain the default value, "all."


8. The first time you use any menu option, the script prompts for the passwordfor PV_ADMIN:

Enter password for PV_ADMIN : PV

9. Use menu option 1 to list the aggregation sets you configured in “Configuringaggregation sets” on page 241. The script displays a list similar to thefollowing:

============= LIST OF CONFIGURED AGGREGATION SETS ============Num Effect Time Name Time lag---- --------------------- ------------------------------------------- --------

0 01-01-1970 00:00:00 GMT +0h04-01-2007 07:00:00 EST_2007_DST -4h04-02-2006 07:00:00 EST_2006_DST -4h04-03-2005 07:00:00 EST_2005_DST -4h04-04-2010 07:00:00 EST_2010_DST -4h04-05-2009 07:00:00 EST_2009_DST -4h04-06-2008 07:00:00 EST_2008_DST -4h09-29-2004 22:00:00 EST_2004_DST -4h10-25-2009 06:00:00 EST_2009 -5h10-26-2008 06:00:00 EST_2008 -5h10-28-2007 06:00:00 EST_2007 -5h10-29-2006 06:00:00 EST_2006 -5h10-30-2005 06:00:00 EST_2005 -5h10-31-2004 06:00:00 EST_2004 -5h10-31-2010 06:00:00 EST_2010 -5h

1 04-01-2007 08:00:00 CST_2007_DST -5h04-02-2006 08:00:00 CST_2006_DST -5h04-03-2005 08:00:00 CST_2005_DST -5h04-04-2010 08:00:00 CST_2010_DST -5h04-05-2009 08:00:00 CST_2009_DST -5h04-06-2008 08:00:00 CST_2008_DST -5h09-29-2004 23:00:00 CST_2004_DST -5h10-25-2009 07:00:00 CST_2009 -6h10-26-2008 07:00:00 CST_2008 -6h10-28-2007 07:00:00 CST_2007 -6h10-29-2006 07:00:00 CST_2006 -6h10-30-2005 07:00:00 CST_2005 -6h10-31-2004 07:00:00 CST_2004 -6h10-31-2010 07:00:00 CST_2010 -6h

2 aggregation sets configuredPress enter...

10. Select option 2 to list the aggregation sets already installed. The output issimilar to the following:

============== LIST OF CREATED AGGREGATION SETS ========================== X: created ==== #: partially created ============Channels 0| 1AggSets -----------------------------------------------------------------------| 0 XPress enter...

Remember that aggregation set 0 is automatically installed when you installthe database channel, and continues to be installed even if you modified set 0by assigning a different timezone.

11. Select option 3 to designate the aggregation set to install. In the examplesabove, set 0 is already installed, but set 1 is waiting to be installed. Thus, enter1 at the prompt:

Enter Aggregation Set number between 1 and 998 : 1

12. By default, the date to start collecting data on the designated aggregation setis today's date. You can instead use menu option 5 to designate a future dateto start collecting data. Set an appropriate future date for your installation.


Enter start date (GMT) using Oracle or DB2 format ’yyyy.mm.dd-hh24’ : 2009.08.31-00WARNING! Start date is set in the future.No loading is allowed until start date (GMT) is reached.Do you confirm the start date (Y/N) [N] ? y

13. When all menu parameters are set, type 6 at the Choice prompt and pressEnter.

Edit aggregation set parameters fileHow to edit the aggregation set parameters file

About this task

Procedure1. The script prompts that it will start the editor specified in the EDITOR

environment variable and open the aggregation set parameters file. Press Enter.An editing session opens containing the aggsetreg.udef configuration file, asshown in this example:

## Tivoli Netcool Performance Manager Datamart# <Current Date>

### Channel C01: GROUPS DAILY aggregates storage

#[AGGSETREG/C01/1DGA/TABLE/CURRENT]

PARTITION_EXTENTS=5PARTITION_SIZE=100K#[AGGSETREG/C01/1DGA/TABLE/HISTORIC]

PARTITION_EXTENTS=5PARTITION_SIZE=100K#[AGGSETREG/C01/1DGA/TABLESPACE/CURRENT]CREATION_PATH=/raid_2/oradata

EXTENT_SIZE=64KSIZE=10M#[AGGSETREG/C01/1DGA/TABLESPACE/HISTORIC]CREATION_PATH=/raid_3/oradata

EXTENT_SIZE=64KSIZE=10M## Channel C01: RESOURCES DAILY aggregates storage

#[AGGSETREG/C01/1DRA/TABLE/CURRENT]

PARTITION_EXTENTS=5PARTITION_SIZE=100K#...

2. Do not make changes to this file unless you have explicit instructions fromProfessional Services.Only if you have guidelines from Professional Services for advancedconfiguration of your aggregation sets, make the suggested edits.Save and close the file.

3. When you close the configuration file, the script checks the file parameters andstarts installing the aggregation set. The installation takes three to ten minutes,depending on the speed of your server.A message like the following is displayed when the installation completes:


P R O V I S O A g g r e g a t i o n S e t <version number>||||||||||||||||||||||||AggregationSet installed

Tivoli Netcool Performance Manager Aggregation Set 1 on Channel 1 successfully installed !Press Enter...

Linking DataView groups to timezonesOnce you have configured and installed the aggregation sets, you must linkDataView groups to a timezone.

About this task

You can link a defined timezone to a calendar you create in the DataView GUI, orthe CME Permanent calendar (a 24-hour calendar).

When you link a group to a specific timezone and calendar, all subgroups inheritthe same timezone and calendar.

Procedurev Best practice:

Use a separate calendar for each timezone. If you link multiple timezones to thesame calendar, a change to one timezone calendar setting will affect all thetimezones linked to that calendar.

v To link a group to a timezone:1. Create a calendar with the DataView GUI, or use the default CME

Permanent calendar.2. Create a text file (for example, linkGroupTZ.txt) with the following format:

– Each line has three fields separated by |_|.– The first field is a DataView group name.– The second field is a timezone name from the Tivoli Netcool Performance

Manager internal timezone list. See “Configuring aggregation sets” onpage 241 for a list of timezone names.

– The third field is the name of the calendar you create, or CME Permanent.The following example line demonstrates the file format:

~Group~USEast|_|EST_2005_DST|_|CME Permanent|_|

Enter as many lines as you have timezone entries in your aggregation setconfiguration.

3. At a shell prompt, enter a command similar to the following, which uses theResource Manager's CLI to link the group to the timezone:resmgr -import segp -colNames "npath tz.name cal.name" -file linkGroupTZ.txt

v To unlink a timezone:– Use the resmgr command. For example:

resmgr -delete linkGroupSE_TZC -colNames "npath tz.name cal.name" -file linkGroupTZ.txt

v To review timezone to group associations:– Use the resmgr command. For example:

resmgr -export segp -colNames "name tz.name cal.name" -file link.txt



Appendix D. Deployer CLI options

Deployer CLI options and their descriptions.

To run the deployer from the command line, entering the following command:# ./deployer.bin [options]

The deployer.bin command accepts the following options:

Option Description

-Daction=patch Performs a patch installation of TivoliNetcool Performance Manager. SeeAppendix G, “Installing an interim fix,” onpage 271 for more information.

-Daction=resume Resumes an interrupted installation at thecurrent step. Note that this option is possibleonly when the /tmp/ProvisoConsumerdirectory is available. See “Resuming apartially successful first-time installation” onpage 169 for more information.

-Daction=uninstall Uninstalls all components marked "To BeRemoved" in the current topology file. See“Uninstalling the entire Tivoli NetcoolPerformance Manager system” on page 220for more information.

-DCheckUser=true Specifies whether the deployer checks to seeif it is running as root before performinginstall operations. Possible values are trueand false. For most install scenarios,running the deployer as the operatingsystem root is required. You can use thisoption to override root user checking.Default is true.

-DOracleClient=oracle_client_home

-DDB2Client=DB2_client_home

Enables you to specify the database clienthome, so the wizard screen that promptsyou for that information is skipped.

-DOracleServerHost=hostname

-DDB2ServerHost=hostname

Specifies the hostname or IP address wherethe database server resides.


Option Description

-DOracleServerPort=port

-DDB2ServerPort=port

Specifies the communication port used bythe database server. Default is 1521 forOracle and 60000 for IBM DB2.

-DOracleSID=sid

-DDBName=database name

Specifies the database server ID. Default isPV.

-DOracleAdminUser=admin_user

-DDB2AdminUser=admin_user

Specifies the administrator username for thedatabase server. Default is PV_INSTALL.

-DOracleAdminPassword=admin_password

-DDB2AdminPassword=admin_password

Specifies the administrator password for thedatabase server. Default is PV.

-DPrimary=true Indicates that the deployer is running on theprimary server. This option is used by theTopology Editor to invoke the deployer. Usethis option to force a channel configurationupdate in the database.

-DTarget=id Instructs the deployer to install or uninstallthe component specified using the idparameter, regardless of the current status ofthe component in the topology. Use thisoption to force an install or uninstall of acomponent in a high-availability (HA)environment, or when fixing an incompleteor damaged installation. Table 12 contains alist of possible values for the id parameter.

-DTopologyFile=topology_file_path Tells the deployer to use the specifiedtopology file instead of prompting for thefile.

-DTrace=true Causes the deployer to log additionaldiagnostic information.


Option Description

-DUsehostname=hostname Enables you to override the hostname thatthe deployer uses to define where it isrunning. This option is useful whenhostname aliasing is used and none of thehostnames listed in the topology.xml filematch the hostname of the machine wherethe deployer is running.

Using the -DTarget optionHow to use the -DTarget option to force an install or uninstall of a component ordamaged installation.

You can use the -DTarget option to force an install or uninstall of a component in ahigh-availability (HA) environment, or when fixing an incomplete or damagedinstallation. The -DTarget option uses the following syntax:

deployer.bin -DTarget=id

where id is a supported target identifier code.

If you are using the -DTarget option to force the uninstall of a component, youmust also specify the -Daction=uninstall option when you run the deployerapplication. The following example shows how to force the uninstallation ofDataMart on the local system:

deployer.bin -Daction=uninstall -DTarget=DMR

Table 12 shows the possible values for the id parameter.

Table 12: Target Identifier Codes

Value Description

DB Instructs the deployer to install the databasesetup components on the local machine.

DM Instructs the deployer to install theDataMart component on the local machine.

DV Instructs the deployer to install theDataView component on the local machine.

DC Instructs the deployer to install theDataChannel component on the localmachine.

DL Instructs the deployer to install theDataLoad component on the local machine.

DBR Instructs the deployer to remove thedatabase setup components from the localmachine. Requires the -Daction=uninstalloption.

DMR Instructs the deployer to remove theDataMart component from the localmachine. Requires the -Daction=uninstalloption.

Appendix D. Deployer CLI options 253

Value Description

DVR Instructs the deployer to remove theDataView component from the localmachine. Requires the -Daction=uninstalloption.

DCR Instructs the deployer to remove theDataChannel component from the localmachine. Requires the -Daction=uninstalloption.

DLR Instructs the deployer to remove theDataLoad component from the localmachine. Requires the -Daction=uninstalloption.

DBU Instructs the deployer to upgrade thedatabase setup components on the localmachine.

DMU Instructs the deployer to upgrade theDataMart component on the local machine.

DVU Instructs the deployer to upgrade theDataView component on the local machine.

DCU Instructs the deployer to upgrade theDataChannel component on the localmachine.

DLU Instructs the deployer to upgrade theDataLoad component on the local machine.

When you run the deployer using the -DTarget option, note the following:v The deployer does not perform component registration in the versioning tables

of the database.v The deployer does not upload modified topology information to the database.v The deployer does not allow you to you select other nodes besides the local

node in the Node Selection panel.v In the case of an uninstall, the deployer does not remove the component from

the topology.


Appendix E. Secure file transfer installation

This section describes the OpenSSH installation, configuration, and testing processin detail for each platform.

OverviewHow to install OpenSSH for Secure File Transfer (SFTP) among Tivoli NetcoolPerformance Manager components.

This document explains how to install OpenSSH for Secure File Transfer (SFTP)among Tivoli Netcool Performance Manager components. You must be proficient inyour operating system and have a basic understanding of public/private keyencryption when working with SFTP. For the purposes of this document, an SFTP"client" is the node that initiates the SFTP connection and login attempt, while theSFTP "server" is the node that accepts the connection and permits the loginattempt. This distinction is important for generating public/private keys andauthorization, as the SFTP server should have the public key of the SFTP client inits authorized hosts file. This process is described in more detail later.

For Tivoli Netcool Performance Manager to use SFTP for the remote execution ofcomponents and file transfer, OpenSSH must be configured for key-basedauthentication when connecting from the Tivoli Netcool Performance Manageraccount on the client (the host running the Tivoli Netcool Performance Managerprocess that needs to use SFTP) to the account on the server. In addition, the hostkeys must be established such that the host key confirmation prompt is notdisplayed during the connection.

Enabling SFTPThe use of SFTP is supported in Tivoli Netcool Performance Manager.

Tivoli Netcool Performance Manager SFTP can be enabled for a single component,set of components, or all components as needed. This table shows the TivoliNetcool Performance Manager components that support SFTP:

Client Server Description

Node on which DataChannelresides.

All other DataChannel nodesto be installed.

Installer can use SFTP toinstall Tivoli NetcoolPerformance Managersoftware to remote locations.

Bulk Collector DataMart Inventory Transfer of inventory files.

FTE Bulk Collector FTE transfers files fromBCOL to CME.

FTE DataLoad SNMP collector Transfer of SNMP data.

CME/LDR Remote CME Downstream CME and LDRboth transfer files fromremote CME.

Note: This document is intended only as a guideline to installing OpenSSH. TivoliNetcool Performance Manager calls the ssh binary file directly and uses the SFTP


protocol to transfer files, so the essential Tivoli Netcool Performance Managerrequirement is that OpenSSH is used and public key authentication is enabled. Thefollowing procedures are examples of one method of installing and configuringOpenSSH. The precise method and final configuration for your site should bedecided by your local operating system security administrator.

For detailed information about OpenSSH and its command syntax, visit thefollowing URL:

http://www.openssh.com/manual.html

Installing OpenSSHThis section describes the steps necessary to install OpenSSH on AIX, Solaris andLinux.

Note: The following sections refer to the earliest supported version of the requiredpackages. Refer to the OpenSSH documentation for information about updatedversions.

AIX systems

To install OpenSSH on AIX systems you must follow all steps described in thissection.

Download the required software packagesHow to download the required packages.

Procedure1. In your browser, enter the following URL:

http://www-03.ibm.com/servers/aix/products/aixos/linux/download.html

2. From the AIX Toolbox for Linux Applications page, download the followingfiles according to the instructions to each Tivoli Netcool Performance Managersystem where SFTP is to be used:v prngd - Pseudo Random Number Generation Daemon (prngd-0.9.29-

1.aix5.1.ppc.rpm or later).v zlib - zlib compression and decompression library (zlib-1.2.2-

4.aix5.1.ppc.rpm or later).3. From the AIX Toolbox for Linux Applications page, click the AIX Toolbox

Cryptographic Content link.4. Download the following files to each Tivoli Netcool Performance Manager

system where SFTP is to be used:openssl-0.9.7g-1.aix5.1.ppc.rpm or later

5. In your browser, enter the following URL:http://sourceforge.net/projects/openssh-aix

6. From the OpenSSH on AIX page, search for and download the following filesaccording to the instructions to each Tivoli Netcool Performance Managersystem where SFTP is to be used:openssh-4.1p1_53.tar.Z or later


Install the required packagesHow to install the required packages on each Tivoli Netcool Performance Managersystem where SFTP is to be used.

Procedure1. Log in to the system as root.2. Change your working directory to the location where the software packages

have been downloaded by using the following command:# cd /download/location

3. Run the RPM Packaging Manager for each package, in the specified order,using the following commands:# rpm -i zlib# rpm -i prndg# rpm -i openssl

4. Uncompress and untar the openssh tar file by entering the followingcommands:

$ uncompress openssh-4.1p1_53.tar.Z$ tar xvf openssh-4.1p1_53.tar

5. Using the System Management Interface Tool (SMIT), install the opensshpackage.

6. Exit from SMIT.

Configure OpenSSH server to start up on system bootAfter installing the OpenSSH server and client, you must configure the OpenSSHserver to start up on system boot.

Procedure

To configure the server to start on system boot, modify the /etc/rc.d/rc2.d/Ssshdinit script as follows:#! /usr/bin/sh## start/stop the secure shell daemon

case "$1" in’start’)# Start the ssh daemonif [ -x /usr/local/sbin/sshd ]; thenecho "starting SSHD daemon"/usr/local/sbin/sshd & fi;;

’stop’)# Stop the ssh daemonkill -9 `ps -eaf | grep /usr/local/sbin/sshd | grep -v grep |awk ’{print $2}’ | xargs`;;*)

echo "usage: sshd {start|stop}";;

Appendix E. Secure file transfer installation 257

Solaris systems

OpenSSH is required for SFTP to work with Tivoli Netcool Performance Manageron Solaris systems.

The version of SSH installed with the Solaris 10 operating system is not supported.

Note: The following sections refer to the current version of the required packages.Refer to the OpenSSH documentation for information about updated versions.

To install OpenSSH on Solaris systems, follow all steps described in this section.

Download the required software packagesHow to download the required packages.

Procedure1. In your browser, enter the following URL: http://www.sunfreeware.com2. From the Freeware for Solaris page, follow the instructions to download the

following files to each Tivoli Netcool Performance Manager system where SFTPis to be used. Ensure that you download the correct files for your version ofSolaris.v gcc - Compiler. Ensure that you download the full Solaris package and not

just the source code (gcc-3.2.3-sol9-sparc-local.gz or later).v openssh - SSH client (openssh-4.5p1-sol-sparc-local.gz or later).v openssl - SSL executable files and libraries (openssl-0.9.8d-sol9-sparc-local.gz

or later).v zlib - zlib compression and decompression library (zlib-1.2.3-sol9-sparc-

local.gz or later).

What to do next

Note: The user should ensure they have the libcrypto.so.0.9.8 instead oflibcrypto.so.1.0.0. to use OpenSSH on Solaris.

Install the required software packagesHow to install the required software packages.

About this task

To install the required packages, do the following on each Tivoli NetcoolPerformance Manager system where SFTP is to be used:

Procedure1. Log in to the system as root.2. Change your working directory to the location where the software packages

have been downloaded using the following command:# cd /download/location

3. Copy the downloaded software packages to /usr/local/src, or a similarlocation, using the following commands:


# cp gcc-version-sparc-local.gz /usr/local/src# cp zlib-version-sparc-local.gz /usr/local/src# cp openssl-version-sparc-local.gz /usr/local/src# cp openssh-version-sparc-local.gz /usr/local/src

4. Change your working directory to /usr/local/src using the followingcommand:# cd /usr/local/src

5. Install the gcc compiler:a. Uncompress gcc using the following command:

gunzip gcc-version-sparc-local.gz

b. Add the gcc package using the following command:pkgadd -d gcc-version-sparc-local

6. Install the zlib compression library:a. Uncompress zlib using the following command:

gunzip zlib-version-sparc-local.gz

b. Add the zlib package using the following command:pkgadd -d zlib-version-sparc-local

7. Install the OpenSSL executable and binary files:a. Uncompress OpenSSL using the following command:

gunzip openssl-version-sparc-local.gz

b. Add the OpenSSL package using the following command:pkgadd -d openssl-version-sparc-local

8. Install the OpenSSH client:a. Uncompress OpenSSH using the following command:

gunzip openssh-version-sparc-local.gz

b. Add the OpenSSH package using the following command:pkgadd -d openssh-version-sparc-local

c. Create a group and user for sshd using the following commands:groupadd sshduseradd -g sshd sshd

9. Optional: Remove Sun SSH from the path and link OpenSSH:a. Change your working directory to /usr/bin using the following command:

cd /usr/bin

b. Move the Sun SSH files and link the OpenSSH files using the followingcommands:# mv ssh ssh.sun# mv ssh-add ssh-add.sun# mv ssh-agent ssh-agent.sun# mv ssh-keygen ssh-keygen.sun# mv ssh-keyscan ssh-keyscan.sun# ln -s /usr/local/bin/ssh ssh# ln -s /usr/local/bin/ssh-add ssh-add# ln -s /usr/local/bin/ssh-agent ssh-agent# ln -s /usr/local/bin/ssh-keygen ssh-keygen# ln -s /usr/local/bin/ssh-keyscan ssh-keyscan

Configure OpenSSH server to start up on system bootAfter installing the OpenSSH server and client, you must configure the OpenSSHserver to start up on system boot.

About this task

To configure the server to start on system boot:


Procedure1. Create or modify the /etc/init.d/sshd init script as follows:

#! /bin/sh## start/stop the secure shell daemon

case "$1" in’start’)

# Start the ssh daemonif [ -x /usr/sbin/sshd ]; thenecho "starting SSHD daemon"/usr/sbin/sshd &fi;;

’stop’)# Stop the ssh daemon/usr/bin/pkill -x sshd;;

*)echo "usage: /etc/init.d/sshd {start|stop}"

;;

2. Check that /etc/rc3.d/S89sshd exists (or any sshd startup script exists) and isa soft link to /etc/init.d/sshd.If not, create it using the following command:

ln -s /etc/init.d/sshd /etc/rc3.d/S89sshd

Linux systems

OpenSSH is required for VSFTP to work with Tivoli Netcool Performance Manager.OpenSSH is installed by default on any RHEL system.

Configuring OpenSSHThis section describes how to configure the OpenSSH server and client.

Configuring the OpenSSH serverHow to configuring the OpenSSH Server on Linux.

About this task

To configure the OpenSSH Server, follow these steps on each Tivoli NetcoolPerformance Manager system where SFTP is to be used:

Procedure1. Log in to the system as root.2. Change your working directory to the location where the OpenSSH Server was

installed (/usr/local/etc/sshd_config by default) using the followingcommand:# cd /usr/local/etc

3. Using the text editor of your choice, open the sshd_config file. This is anexample of a sshd_config file:


#***************************************************************************# sshd_config# This is the sshd server system-wide configuration file. See sshd(8)# for more information.# The strategy used for options in the default sshd_config shipped with# OpenSSH is to specify options with their default value where# possible, but leave them commented. Uncommented options change a# default value.Port 22Protocol 2ListenAddress 0.0.0.0HostKey /usr/local/etc/ssh_host_dsa_keySyslogFacility AUTHLogLevel INFOPubkeyAuthentication yesAuthorizedKeysFile .ssh/authorized_keysRhostsAuthentication noRhostsRSAAuthentication noHostbasedAuthentication noPasswordAuthentication yesChallengeResponseAuthentication noSubsystem sftp /usr/local/libexec/sftp-server#****************************************************************

4. Locate the Protocol parameter. For security purposes, it is recommended thatthis parameter is set to Protcol 2 as follows:Protocol 2

5. Locate the HostKeys for protocol version 2 parameter and ensure that it isset as follows:

HostKey /usr/local/etc/ssh_host_dsa_key

6. Locate the PubkeyAuthentication parameter and ensure that it is set as follows:PubkeyAuthentication yes

7. Locate the PasswordAuthentication parameter and ensure that it is set asfollows:PasswordAuthentication yes

8. Locate the Subsystem parameter and ensure that the SFTP subsystem and pathare correct. Using defaults, the Subsystem parameter appears as follows:Subsystem sftp /usr/local/libexec/sftp-server

Configuring OpenSSH clientHow to configure OpenSSH client.

The OpenSSH client requires no configuration if it used in its default form. Thedefault location for the OpenSSH client file is /usr/local/etc/ssh_config.

Generating public and private keysBy default, OpenSSH generates public and private keys for the root user. You mustgenerate public and private keys with the Tivoli Netcool Performance Manageruser for the SFTP functions to work in Tivoli Netcool Performance Manager.

About this task

To generate public and private keys:

Procedure1. Log in as pvuser on the node that will be the SFTP client. This node is

referred to as SFTPclient in these instructions, but you must replaceSFTPclient with the name of your node.


2. Create an .ssh directory in the home directory of the Tivoli NetcoolPerformance Manager user, set permissions to x/r/w for owner (700), thenchange to the directory using the following commands:$ mkdir ~/.ssh$ chmod 700 ~/.ssh$ cd ~/.ssh

3. Generate a DSA public and private key with no passphrase (DSA encryptionis used as an example). The following example shows a UNIX server calledSFTPclient:$ /usr/local/bin/ssh-keygen -t dsa -f SFTPclient -P ""

Generating public/private dsa key pair.Your identification has been saved in SFTPclient.Your public key has been saved in SFTPclient.pub.The key fingerprint is: 77:67:2f:34:d4:2c:66:db:9b:1f:9a:36:fe:c7:07:c6 pvuser@SFTPclient

4. The previous command generates two files, SFTPclient (the private key) andSFTPclient.pub (the public key). Copy the private key to id_dsa in the ~/.sshdirectory by entering the following command:

$ cp -p ~/.ssh/SFTPclient ~/.ssh/id_dsa

id_dsa identifies the node when it contacts other nodes.5. To permit Tivoli Netcool Performance Manager components on SFTPclient to

communicate, you must append the contents of the SFTPclient.pub key file tothe file authorized_keys in the ~/.ssh directory by using the followingcommands:cd ~/.sshcat SFTPclient.pub >> authorized_keys

6. Log on to the other node that will be the SFTP server. This node is referred toas SFTPserver in these instructions, but you must replace SFTPserver with thename of your node.

7. Repeat Step 1 through Step 5 on the SFTPserver node, replacing SFTPclientwith SFTPserver.

8. Copy (with FTP, scp, or a similar utility) the public key from SFTPclient toSFTPserver and append the contents of the key file to the file authorized_keysin the ~/.ssh directory. If you cut and paste lines, be careful not to introducecarriage returns.Use the following FTP session as an example:SFTPserver:~/.ssh> ftp SFTPclientConnected to SFTPclient.220 SFTPclient FTP server (SunOS 5.8) ready.Name (SFTPclient:pvuser): pvuser331 Password required for pvuser.Password:

230 User pvuser logged in.ftp> bin200 Type set to I.ftp> get .ssh/SFTPclient.pub200 PORT command successful.150 Binary data connection for .ssh/SFTPclient.pub226 Binary Transfer complete.local: .ssh/SFTPclient.pub remote: .ssh/SFTPclient.pubftp> quit221 Goodbye.SFTPserver:~/.ssh> cat SFTPclient.pub >> authorized_keys

9. Optional: If you want to set up bidirectional SFTP, repeat Step 8, but from theSFTserver node to the SFTPclient node.


Note: This step is not needed for Tivoli Netcool Performance Manager.Use the following FTP session as an example:SFTPclient:~/.ssh> ftp SFTPserverConnected to SFTPserver.220 SFTPserver FTP server (SunOS 5.8) ready.Name (SFTPserver:pvuser): pvuser331 Password required for pvuser.Password:230 User pvuser logged in.ftp> bin180 Tivoli Netcool Performance Manager Installation Guide, Version 1.4.3200 Type set to I.ftp> get .ssh/SFTPserver.pub200 PORT command successful.150 Binary data connection for .ssh/SFTPserver.pub226 Binary Transfer complete.local: .ssh/SFTPserver.pub remote: .ssh/SFTPserver.pubftp> quit221 Goodbye.SFTPclient:~/.ssh> cat SFTPserver.pub >> authorized_keys

10. When finished, the SFTPclient and SFTPserver should look similar to thefollowing:SFTPclient:~/.ssh> ls -al ~/.sshtotal 10

drwx------ 2 pvuser pvuser 512 Nov 25 16:56 .drwxr-xr-x 28 pvuser pvuser 1024 Nov 25 15:25 ..-rw------- 1 pvuser pvuser 883 Nov 25 15:21 id_dsa-rw-r--r-- 1 pvuser pvuser 836 Nov 25 16:33 known_hosts

SFTPserver:~/.ssh> ls -al ~/.sshtotal 10

drwx------ 2 pvuser pvuser 512 Nov 25 16:56 .drwxr-xr-x 28 pvuser pvuser 1024 Nov 25 15:25 ..-rw------- 1 pvuser pvuser 883 Nov 25 15:21 id_dsa-rw-r--r-- 1 pvuser pvuser 836 Nov 25 16:33 known_hosts

The important files are:v authorized_keys, which contains the public keys of the nodes that are

authorized to connect to this nodev id_dsa, which contains the private key of the node it is onv known_hosts, which contains the public keys of the node that you want to

connect toFor security, the private key (id_dsa) should be -rw------. Likewise, thepublic key Node<number>.pub, authorized_keys, and known_hosts should be-rw-r--r--.The directory itself should be -rwx-----.

Note: The directory that contains the .ssh directory might also need to bewritable by owner.

11. The first time you connect using SSH or SFTP to the other node, it will ask ifthe public key fingerprint is correct, and then save that fingerprint inknown_hosts. Optionally, you can manually populate the client's known_hostsfile with the server's public host key (by default, /usr/local/etc/ssh_host_dsa_key.pub).For large-scale deployments, a more efficient and reliable procedure is:a. From one host, ssh to each SFTP server and accept the fingerprint. This

builds a master known_hosts file with all the necessary hosts.


b. Copy that master file to every other SFTP client.

Note: If the known_hosts file has not been populated and secure filetransfer (SFTP) is attempted through Tivoli Netcool Performance Manager,SFTP fails with vague errors.

Testing OpenSSH and SFTPHow to test OpenSSH and SFTP.

About this task

For the following tests, the commands normally work without asking for apassword. If you are prompted for a password, public/private key encryption isnot working.

Ensure that you specify the full path to the ssh and sshd binary files. Otherwise,you might use another previously installed SSH client or server.

To test OpenSSH and SFTP:

Procedure1. On both nodes, kill any existing sshd processes and start the sshd process from

the packages you installed, by entering the following commands:pkill -9 sshd;/usr/local/sbin/sshd &

The path can be different depending on the installation.2. From SFTPclient, run the following command:

/usr/local/bin/ssh SFTPserver

3. From SFTPclient, run the following command:/usr/local/bin/sftp SFTPserver

4. Optional: If you set up bidirectional SFTP, run the following command fromSFTPserver:

/usr/local/bin/ssh SFTPclient

5. Optional: If you set up bidirectional SFTP, run the following command fromSFTPserver:

/usr/local/bin/sftp SFTPclient

6. If all tests allow you to log in without specifying a password, follow the TivoliNetcool Performance Manager instructions on how to enable SFTP in eachTivoli Netcool Performance Manager component. Make sure to specify the fullpath to SSH in the Tivoli Netcool Performance Manager configuration files. Inaddition, make sure the user that Tivoli Netcool Performance Manager is run asis the same as the user that you used to generate keys.


TroubleshootingHow to troubleshoot OpenSSH and its public keys.

About this task

If you find that OpenSSH is not working properly with public keys:

Procedure1. Check the ~/known_hosts file on the node acting as the SSH client and make

sure the client host name and IP information is present and correct.2. Check the ~/authorized_keys file on the node acting as the SSH server and

make sure that the client public key is present and correct. Ensure that thepermissions are -rw-r--r--.

3. Check the ~/id.dsa file on the node acting as the SSH client and make surethat the client's private key is present and correct. Ensure that the permissionsare -rw-------.

4. Check the ~/.ssh directory on both nodes to ensure that the permissions onthe directories are -rwx------.

5. Check for syntax errors (common ones are misspelling authorized_keys andknown_hosts without the "s" at the end). In addition, if you copied and pastedkeys into known hosts or authorized keys files, you probably have introducedcarriage returns in the middle of a single, very long line.

6. Check the ~ (home directory) permissions to ensure that they are only writableby owner.

7. If the permissions are correct, kill the sshd process and restart in debug modeas follows:

pkill -9 sshd /usr/local/sbin/sshd -d

8. Test SSH again in verbose mode on the other node by entering the followingcommand:

/usr/local/bin/ssh -v SFTPserver

9. Read the debugging information about both client and server andtroubleshoot from there.

10. Check the log file /var/adm/messages for additional troubleshootinginformation.

Tivoli Netcool Performance Manager SFTP errorsErrors that you may encounter.

In the Tivoli Netcool Performance Manager log files, you might see the followingerrors:v [DC10120] FTPERR error: incompatible version, result: sftp status:

SSH2_FX_FAILURE:: incompatible version, log:

This error indicates that the SSH server (sshd) is SSH2 rather than OpenSSH.OpenSSH is required for Tivoli Netcool Performance Manager to functioncorrectly.

v [DC10120] FTPERR error: bad version msg, result: sftp status:SSH2_FX_NO_CONNECTION:: connection not established - check sshconfiguration, log:


This error indicates that the SSH configuration is incorrect or the wrong versionof the SSH server (sshd) is running. OpenSSH is required for Tivoli NetcoolPerformance Manager to function correctly.


Appendix F. LDAP integration

Detailed information on how to configure LDAP (Lightweight Directory AccessProtocol) as a default authentication/authorization mechanism for Tivoli NetcoolPerformance Manager.

Supported LDAP serversA list of LDAP servers supported by Tivoli Netcool Performance Manager.v Domino 6.5.4, 7.0v IBM Tivoli Directory Server 6.3v IBM z/OS Security Server 1.6, 1.7v IBM z/OS.e Security Server 1.6, 1.7v Microsoft Active Directory 2000, 2003v Novell eDirectory 8.7.3, 8.8

LDAP configurationThere are two scenarios for LDAP Configuration; Configure LDAP duringinstallation of Tivoli Netcool Performance Manager and configure LDAP after theTivoli Netcool Performance Manager installation is complete.

For postinstallation of LDAP configuration, see http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/config/psc_t_config_user_registry.html. After this process is complete, do the followingtasks:v Restart the Jazz for Service Management server after the configuration is

complete.v Assign Tivoli Netcool Performance Manager roles to LDAP users. For more

information, see “Assigning Tivoli Netcool Performance Manager roles to LDAPusers” on page 269

The configuration of LDAP as a default authentication and authorizationmechanism for Tivoli Netcool Performance Manager is achieved by using theTopology Editor. Follow the steps from “Enable LDAP configuration” onwardsuntil “Assigning Tivoli Netcool Performance Manager roles to LDAP users” onpage 269.

Enable LDAP configurationThe LDAP configuration option becomes available after adding a DashboardApplication Services Hub to your topology.

About this task

Note: The process of installing a Dashboard Application Services Hub is describedin Chapter 4, “Installing Jazz for Service Management,” on page 91.

To enable LDAP configuration:


http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/config/psc_t_config_user_registry.html



Procedure1. In Logical View of Topology Editor, select the Dashboard Application Services

Hub that you have installed.2. Open Advanced Properties.3. Click the checkbox opposite the

IAGLOBAL_USER_REGISTRY_LDAP_SELECTED property. This enablesLDAP.

4. In Advanced Properties, enter the LDAP connection details. This requires thatyou populate the following fields:

WAS_USER_NAMEThis is the name you have registered as the Advanced Properties user.For example, "smadmin".

IAGLOBAL_LDAP_BIND_DNThis username specified must have read and write permissions inLDAP 3. Typically this will be an LDAP administrator username. Forexample "cn=Directory Manager".

IALOCAL_LDAP_BIND_PASSWORDThis is the password for the Bind Distinguished Name specified.

IAGLOBAL_LDAP_NAMEThis is the LDAP server host name. Should this LDAP server existbehind firewall, make sure that this host has been authenticated.

IAGLOBAL_LDAP_PORTFor example, "1389".

IAGLOBAL_LDAP_REPOSITORY_IDThis is a string used to identify the LDAP repository, which can be setto the string of your choice.

IAGLOBAL_LDAP_BASE_ENTRYThe distinguished name of a base entry in LDAP.

For example, for IBM the base entry is o=IBM, c=US.

Verifying the DataView installationVerify that the correct users are within the correct groups.

About this task

When the DataView installation is complete, it should have created two users andtwo groups in LDAP:

Users:v tnpmv tnpmScheduler

Groups:v tnpmUsersv tnpmAdministrators


Procedure

Verify from the UI that the users tnpm and tnpmScheduler are members of thetnpmAdministrators group.

Assigning Tivoli Netcool Performance Manager roles to LDAPusers

To successfully authenticate your LDAP user, you need to assign them to one ofthe appropriate roles

Procedure

To successfully authenticate you LDAP user, you must assign them to one of thefollowing roles:v tnpmUserv tnpmAdministrator

This can be done by smadmin user, by navigating to Users and Groups > UserRoles, and assigning the correct roles.Alternatively tipcli.sh can be used for assigning roles to the user.JazzSM/profile/bin/tipcli.sh MapRolesToUser --usernameJazzSM_HOME<DASH_admin_user> --password <DASH_admin_password>--userID <userUniqueId> --rolesList <roleName>

Where <userUniqueId> is the concatenation of user name and realm in which userinformation is stored.For example:JazzSM_HOME/JazzSM/profile/bin/tipcli.sh MapRolesToUser --username<DASH_admin_user> --password <DASH_admin_password> --userIDuid=<user_name>,dc=<server>,dc=<server>,dc=<company>,dc=com --rolesListtnpmUser

Roles specific to an application, such as tnpmUser for Tivoli Netcool PerformanceManager are not stored in LDAP. For example, if you assign a Tivoli NetcoolPerformance Manager role to an LDAP user on DASH_instance1, you must alsoassign the same role to the user on DASH_instance2. Otherwise, the user cannotauthenticate on DASH_instance2.

What to do next

Assign tnpmUser and tnpmAdministrator roles to the LDAP users at the Jazz forService Management User Roles page after LDAP integration is done. Otherwise,LDAP users might not able to view the DataView reports.

Appendix F. LDAP integration 269


Appendix G. Installing an interim fix

Describes how to install an interim fix (or patch) release of Tivoli NetcoolPerformance Manager.

OverviewInterim fix installation overview.

Unlike major, minor, and maintenance releases, which are planned, patch releases(interim fixes and fix packs) are unscheduled and are delivered under thefollowing circumstances:v A customer is experiencing a "blocking" problem and cannot wait for a

scheduled release for the fix.v The customer's support contract specifies a timeframe for delivering a fix for a

blocking problem and that timeframe does not correspond with a scheduledrelease.

v Development determines that a patch is necessary.

Note: Patches are designed to be incorporated into the next scheduled release,assuming there is adequate time to integrate the code.

Installation rulesRules that apply to the installation of patches.

Note the following installation rules for patch installations:v Apply fix to Database before any other components.v Fixes for the Database and DataMart must be installed on that host.v Fixes for the DataChannel, DataLoad, DataMart and DataView can be installed

remotely from the local host in a distributed system.v Fix packs are installed on general availability (GA) products.v Sequentially numbered fix packs can be installed on any fix pack with a lower

number.v Interim fixes must be installed on the absolute fix pack.

The patch installer verifies that your installation conforms to these rules.

Behavior and restrictionsBehaviour and restrictions that apply to the installation of patches.

If remote installation of a component is not possible, the deployer grays out theany remote component host on the node selection page.

The maintenance deployer must run locally on each DataMart host to apply apatch.


Before you beginWhat you must do before you begin a patch installation.

A patch release updates the file system for the component that the patch isintended for and updates the versioning information in the database.

To verify that the versioning was updated correctly for the components in thedatabase, you can run several queries both before and after the installation andcompare the results. For detailed information, see the Tivoli Netcool PerformanceManager Technical Note: Tools for Version Reporting document.

Installing a patchHow to install a patch.

About this task

To install a patch:

Procedure1. You must have received or downloaded the maintenance package from IBM

Support. The maintenance package contains the Maintenance Descriptor File,an XML file that describes the contents of the fix pack. Follow the instructionsin the README for the fix pack release to obtain the maintenance packageand unzip the files.

Note: for each tar.gz file, you must unzip them, and then un-tar them. Forexample:

gunzip filename.tar.gztar -xvf filename.tar

2. Log in as root.3. Set and export your DISPLAY environment variable (see “Setting up a remote

X Window display” on page 65).4. Start the patch deployer using one of the following methods:

From the launchpad:a. Click Start Tivoli Netcool Performance Manager Maintenance Deployer

option in the list of tasks.b. Click the Start Tivoli Netcool Performance Manager Maintenance

Deployer link.From the command line:v Run the following command:

# ./deployer.bin -Daction=patch

5. The deployer displays a welcome page. Click Next to continue.6. Accept the default location of the base installation directory of the database

JDBC driver.

/opt/oracle/product/12.1.0-client32

/opt/db2/product/11.1.0/java


or, click Choose to navigate to another directory. Click Next to continue.7. On the patch folder page, click Choose to select the patch you want to install.8. Navigate to the directory that contains the files for the fix pack, and click into

the appropriate directory. Click Select to select that directory, then click Nextto continue.

9. A pop-up window asks whether you want to download the topology file.Click Yes.

10. Verify that all of the fields for the database connection are filled in with thecorrect values:

Database hostnameEnter the name of the database host.

Port

Specifies the port number used for communication with thedatabase. The default value is 1521.

Specifies the port number used for communication with thedatabase. The default value is 60000.

Database userSpecifies the username used to access the database. The default valueis PV_INSTALL.

Database PasswordEnter the password for the database user account (for example, PV).

Database name

Specifies the SID for the database. The default value is PV.

Specifies the name of database. The default value is PV.Click Next.

11. When the topology has been downloaded from the database, click Next.12. The node selection window shows the target systems and how the files will be

transferred. The table has one row for each machine where at least one TivoliNetcool Performance Manager component will be installed. Verify the settings,then click Next to continue.

13. The deployer displays summary information about the installation. Review theinformation, then click Next.The deployer displays the table of installation steps.

14. Run through each installation step just as you would for a normal installation.15. When all the steps have completed successfully, click Done to close the

wizard.

Appendix G. Installing an interim fix 273


Appendix H. Error codes and log files

This appendix lists the Tivoli Netcool Performance Manager error messages andlog files.

See Appendix I, “Troubleshooting,” on page 297 for information abouttroubleshooting problems with the Tivoli Netcool Performance Managerinstallation.

Error codesThe following sections describe the error messages generated by the Deployer, theToplogy Editor and InstallAnywhere.

Deployer messagesThe Deployer messages.

Table 13 lists the error messages returned by the Tivoli Netcool PerformanceManager deployer.

Table 13: Deployer Messages

Error Code Description User Action

DataMart Messages

GYMCI5101E The DataMart installationfailed.

See the DataMart installerlogs for details.

Database Configuration Messages

GYMCI5201E The database installationfailed. See the installation logfor details.

See the root_install_dir/database/install/log/Oracle_SID /install.log file.

GYMCI5202E The database uninstallationscript failed because of asyntax error. This script mustbe run as oracle. Forexample: ./uninstall_db/var/tmp/PvInstall/install.cfg.silent

Check the syntax and runthe script again.

GYMCI5204E The database could not beremoved because someOracle environment variablesare not correctly set. Some orall of the Oracle environmentvariables are not set (forexample, ORACLE_HOME,ORACLE_SID, orORACLE_BASE).

Check that all the requiredOracle variables are set andtry again.



GYMCI5205E An error occurred whentrying to start the Oracledatabase.

See the Oracle alert file forpossible startup errors.Resolve any problemsreported in the log and tryagain.

GYMCI5206E An error occurred whentrying to shut down theOracle database.

See the Oracle alert file forpossible shutdown errors.Resolve any problemsreported in the log and tryagain.

GYMCI5207E An error occurred whilequerying the database todetermine the data files thatare owned by the database.

See the Oracle alert file fordetails of errors. You mightneed to manually deleteOracle data files usingoperating system commands.

GYMCI5208E This version of IBM TivoliNetcool PerformanceManager is not supported onthe host operating system.

See the installation guide toknow list of supportedoperating systems.

GYMCI5209E The database could not beremoved because some DB2environment variables arenot correctly set.

Check that all the requiredDB2 variables are set and tryagain.

GYMCI5210E The database doesn't exists. Check whether the databaseexists or not and try again.

GYMCI5211E An error occurred while thedropping database.

Check log files to get moredetails

DataChannel Messages

GYMCI5301E The database channelinstallation failed. See theinstallation log for details.

See the file root_install_dir/channel/install/log/Oracle_SID/install.log.

GYMCI5401E An error occurred whilerunning a script.

See the message producedwith the error code for moredetails.

GYMCI5402E Unable to find an expectedfile.


GYMCI5403E The data in one of the files isnot valid.


GYMCI5404E Unable to find an expectedfile or expected data.


GYMCI5405E Scripts cannot functioncorrectly because theLD_ASSUME_KERNELvariable is set.

Unset the variable and tryagain.

GYMCI5406E An action parameter ismissing.




GYMCI5407E An error occurred whileprocessing the tar command.


GYMCI5408E The product version you aretrying to install seems to befor a different operatingsystem.


GYMCI5409E Unable to locate installedpackage information for theoperating system.


GYMCI5410E A file has an unexpectedowner, group, orpermissions.


GYMCI5411E A problem was found by thePvCheck module whenchecking the environment.


GYMCI5412E The installation modulefailed.

See the messages in standarderror for more details.

GYMCI5413E The patch installation failed. See the messages in standarderror for more details.

GYMCI5414E The remove action failed. See the messages in standarderror for more details.

GYMCI5415E An unrecoverable erroroccurred while running thescript.


Dataload Messages

GYMCI5501E An error occurred whenrunning the script.


GYMCI5502E Unable to find an expectedfile.


GYMCI5503E The data in one of the files isnot valid.


GYMCI5504E Unable to find an expectedfile or expected data.


GYMCI5505E Scripts cannot functioncorrectly because theLD_ASSUME_KERNELvariable is set.

Unset the variable and tryagain.

GYMCI5506E An action parameter ismissing.


GYMCI5507E An error occurred whileprocessing the tar command.


Appendix H. Error codes and log files 277


GYMCI5508E The product version you aretrying to install seems to befor a different operatingsystem.


GYMCI5509E Unable to locate installedpackage information for theoperating system.


GYMCI5510E A file has an unexpectedowner, group or permissions.


GYMCI5511E A problem was found by thePvCheck module whenchecking the environment.


GYMCI5512E The installation modulefailed.


GYMCI5513E The patch installation failed. See the messages in standarderror for more details.

GYMCI5514E The remove action failed. See the messages in standarderror for more details.

GYMCI5515E An unrecoverable erroroccurred while running thescript.


Prerequisite Checkers: Operating System

GYMCI6001E The syntax of thecheck_osscript is not correct.The specified componentdoes not exist. The syntaxis:check_osPROVISO_COMPONENTwherePROVISO_COMPONENT isDL, DC, DM, DB, or DV.

Correct the syntax and tryagain.

GYMCI6002E This version of IBM TivoliTivoli Netcool PerformanceManager is not supported onthe host operating system.

See the check_os.ini file fora list of supported operatingsystems.

GYMCI6003E The specified componentdoes not exist or is notsupported on this operatingsystem.

Ensure that you havespecified the correctcomponent. If you have, theoperating system must beupgraded before thecomponent can be installed.

GYMCI6004E The operating system is notat the prerequisite patchlevel. Some requiredoperating system patches arenot installed.

Check the productdocumentation for a list ofrequired patches. Apply anymissing patches and tryagain.

GYMCI6005E The host operating system isnot supported for thisinstallation.

Perform the installation on asupported operating system.



GYMCI6006E In the /etc/security/limitsfile, some values are missingor incorrect. Values must notbe lower than specified inthe check_os.ini file.

Check the values in thecheck_os.ini and edit thedefault stanza in the/etc/security/limits file sothat valid values arespecified for all requiredlimits.

Prerequisite Checkers: Database

GYMCI6101E The syntax of the check_dbscript is not correct. Thesyntax is: check_db [client -server] [new - upgrade][ORACLE_SID ortnsnames.ora entry]

Correct the syntax and tryagain.

GYMCI6102E The host operating system isnot supported for thisinstallation.

Perform the installation on asupported operating system.

GYMCI6103E This version of the IBMTivoli Tivoli NetcoolPerformance Managerdatabase is not supported onthe current version of thehost operating system.

See the check_os.ini file fora list of supported operatingsystem versions.

GYMCI6104E Some required Oraclevariables are missing orundefined.

Check the Oracle usersenvironment files (forexample, .profile and.bash_profile).

GYMCI6105E An Oracle binary is missingor not valid.

Ensure that Oracle iscorrectly installed.

GYMCI6106E The instance of Oracleinstalled on the host is not ata supported version.

Check the list of supportedOracle versions in thecheck_db.ini file.

GYMCI6107E Unable to contact the Oracleserver using the tnspingutility with the specifiedORACLE_SID.

Check that your Oraclelistener is running on thedatabase server. Start thelistener if it is not running.

GYMCI6108E An Oracle instance isrunning on the host whereyou have requested a newserver installation.

Check whether you haveselected the correct host for anew Oracle serverinstallation. If the selectedhost is correct, remove theexisting Oracle instance first.

GYMCI6109E The number of bits (32 or 64)for the Oracle binary doesnot match the values definedin the check_db.ini file.

Check the list of supportedOracle versions in thecheck_db.ini file.

GYMCI6110E The installation methodpassed to the script is notvalid. Valid installationmethods are New andUpgrade.

Pass the New or Upgradeoption to the script.



GYMCI6111E The installation type passedto the script is not valid.Valid installation methodsare Client and Server.

Pass the Client or Serveroption to the script.

GYMCI6112E The script was run withoptions set for a new serverinstallation, but an Oracleinstance configuration file(init.ora) already exists forthe specified SID. Thepresence of the init.ora fileindicates the presence of anOracle instance.

Check that a new serverinstallation is the correctaction for this SID. If it is,remove the existing Oracleinstance configuration files.

GYMCI6113E A symbolic link was foundin the Oracle home path. TheOracle home path cannotcontain any symbolic links.

Remove any symbolic links.Specify the Oracle home pathusing only real directories.

GYMCI6114W Cannot contact the OracleListener. The tnsping utilitywas run to check the OracleListener status, but, theListener could not becontacted.

Check that the OracleListener is running. Start it ifnecessary.

GYMCI6115E The semaphore and sharedmemory check failed. Thesysdef command was used tocheck the values forsemaphores and sharedmemory. The command didnot report the minimumvalue for a particularsemaphore or sharedmemory.

Check that the required/etc/system parameters areset up for Oracle. Check thatthe values of theseparameters meet theminimum values listed in thecheck_db.ini file.

GYMCI6116E Could not find thebos.adt.lib package in theCOMMITTED state. Thepackage might not beinstalled. The package iseither not installed or not ina COMMITTED state.

Ensure that the bos.adt.libpackage is installed andcommitted and then tryagain.

GYMCI6117E Could not log in to thedatabase. The verify baseoption was used. The optionattempts to log into thedatabase to ensure it isrunning. However, the scriptcould not log in to thedatabase.

Check that the database andOracle Listener are up andrunning. If not, start them.

GYMCI6118E The checkextc script failed.The verify base option wasused. The option runs thecheckextc script to ensureexternal procedure calls canbe performed.

Check that the Tivoli NetcoolPerformance Managerdatabase was createdproperly.



GYMCI6119E The tnsnames.ora file ismissing. A tnsnames.ora filein should exist inORACLE_HOME/network/admin directory.

Check that the tnsnames.orafile exists in theORACLE_HOME/network/admin directory. Ifit does not, create it.

GYMCI6120E Some required DB2 variablesare missing or undefined.

Check log files to get moredetails.

GYMCI6121E A DB2 binary is missing ornot valid.

Ensure that DB2 is correctlyinstalled.

GYMCI6122E The instance of DB2 installedon the host is not asupported version.

Check the list of supportedDB2 versions in thecheck_DB2_[version]_db.inifile.

GYMCI6123E A DB2 instance is notrunning on the host whereyou have requested a newserver installation.

Check whether you haveselected the correct host for anew DB2 server installation.If the selected host is correct,start DB2 instance first.

GYMCI6124E The number of bits (32 or 64)for the DB2 binary does notmatch the values defined inthecheck_DB2_[version]_db.inifile.

Check the list of supportedDB2 versions in thecheck_DB2_[version]_db.inifile.

GYMCI6125E A symbolic link was foundin the Database Home path.Remove any symbolic links.

Specify the Database Homepath by using only realdirectories.

GYMCI6126E The RHEL kernel parametercheck failed. Check that therequired /etc/systemparameters are setup forDB2.

Check that the values ofthese parameters meet theminimum values that arelisted in thecheck_DB2_[version]_db.inifile.

Minimal Deployment: Post-Installation Messages

GYMCI7500E An internal processing erroroccurred in the script.

Check the logs and theoutput from the script. Lookfor incorrect configuration orimproper invocation.

GYMCI7501E The required configurationor messages files for thepoc-post-install script are notin the same directory as thescript. These files should beunpacked by the installertogether with the script.

Check for errors thatoccurred during theinstallation steps.

GYMCI7502E An environment file ismissing or is in the wronglocation.

Check the poc-post-installconfiguration file. Themissing environment file andexpected path is identified inthe log file.



GYMCI7503E The SNMP DataLoad did notstart. The SNMP DataLoadprocess (pvmd) failed tostart.

Check the SNMP DataLoadlog for errors during startup.

GYMCI7504E The network inventoryfailed. New devices cannotbe discovered unless theinventory runs successfully.

Check the inventory log forerrors. Ensure the DISCserver and SNMP DataLoad(Collector) processes arerunning.

GYMCI7505E The Report Groupingoperation failed. This actiondoes not depend on anyexternal applicationprocesses. The database mustbe running, and correctDataMart grouping ruledefinitions are required.

Check the inventory log filefor more details of theReport Grouping failure.

GYMCI7506E The DataChannel commandline failed. It is possible thatthe CNS, CMGR, and AMGRprocesses are not running.

Ensure that the requiredprocesses are running. Checkthe proviso.log for details ofthe failure.

GYMCI7507E The Report User was notcreated. The web user willnot be able to view reports.The DataMart resmgr utilityis used to add thisconfiguration to thedatabase. It is possible thatthe database is not running.

Ensure that the database isrunning, and check for errorlogs in the DataMart logsdirectory.

GYMCI7508E Failed to associate a ReportUser to a group. The reportuser is associated with agroup to allow the user toview reports. The DataMartresmgr utility is used to addthis configuration to thedatabase. It is possible thatthe database is not running.

Ensure that the database isrunning, and check for errorlogs in the DataMart logsdirectory. Ensure that thespecified report group exists.

GYMCI7509E A report user could not bedeleted from the database.

Check for error and tracelogs in the DataMart logsdirectory.

GYMCI7510E Failed to create a Web User.The user will not be able toauthenticate with theWeb/application server.

Check the Web/applicationserver log file for errors.Ensure that theWeb/application server isrunning.

GYMCI7511E The Web group could not becreated, and the Web usermight not be properlyconfigured to view reports.

Check the Web/applicationserver log file for errors.Ensure that theWeb/application server isrunning.



GYMCI7512E Failed to associate the WebUser with a group. The Webuser might not be properlyconfigured to view reportsunless successfully associatedwith a group.

Check the Web/applicationserver log file for errors.Ensure that theWeb/application server isrunning. This step relies onthe database componentonly.

GYMCI7513E Failed to delete Web Users.Web user authentication wasnot removed.

Check the Web/applicationserver logs.

GYMCI7514E The Channel Naming Servicefailed to start.Cross-applicationcommunication cannotfunction.

Check for walkback or errorfiles in the DataChannel logor state directory.

GYMCI7515E The central LOG serverfailed to start. Logging forDataChannel will beunavailable.

Check for walkback or errorfiles in the DataChannel logor state directory.

GYMCI7516E The Channel Manager failedto start. DataChannelapplications cannot bestarted or stopped.Application status will beunavailable.

Check the proviso.log filefor errors. Check forwalkback or error files in theDataChannel log or statedirectory.

GYMCI7517E The Application Managerfailed to start. DataChannelapplications cannot bestarted or stopped.Application status will beunavailable.

Check the proviso.log filefor errors. Check forwalkback or error files in theDataChannel log or statedirectory.

GYMCI7518E Failed to create the DV usergroup. The DV user willremain in the Orphansgroup.

Check the poc-post-installlogin /var/tmp for moredetails on the errorcondition.

GYMCI7519E Failed to associate the DVuser to the DV group. TheDV user will remain in theOrphans group.

Check the poc-post-installlogin /var/tmp for moredetails on the errorcondition.

GYMCI7520E The Web Application serveris not running or took toolong to start up.

Start the Web Applicationserver as documented.

GYMCI7597E The MIB-II Technology Packjar file was not found in thespecified directory.

Add the MIB2 TechnologyPack JAR file to the directory.Remove other JAR files andtry again.

GYMCI7598E Too many jar files are presentin the specified directory.Only two jar file can bepresent in the directory: theProvisoPackInstaller.jar andthe MIB-II Technology Packjar.

Remove the other JAR filesand try again.



GYMCI7599E The Technology Packinstaller failed. Check theTechnology Pack installerlogs for details.

GYMCI6126E The RHEL kernel parametercheck failed. Check that therequired /etc/systemparameters are setup forDB2.

Check that the values ofthese parameters meet theminimum values that arelisted in thecheck_DB2_[version]_db.inifile.

Installer Action Messages and IA Flow Messages

GYMCI9998E Unable to find a message forthe key. The message wasnot retrieved from themessage catalog.

See the installation log formore details.

GYMCI9999E An unknown error occurredfor the component namewith the error code. Themessage could not beretrieved from the catalog.


GYMCI9001E An error occurred duringinstallation. An exception hasbeen generated during aninstallation step.


GYMCI9002E An unrecoverable erroroccurred when running thecommand .


GYMCI9003E An unrecoverable erroroccurred while running acommand.


GYMCI9004E An error occurred whileconnecting to the database.


GYMCI9005E An error occurred whileperforming a databaseoperation.


GYMCI9006E Remote File Transfer hasbeen disabled.

To continue, change the stepproperty to Allow RemoteExecution and run the stepagain, or manually transferthe directory to the host.When the transfer iscompleted, change the stepstatus to Success andcontinue the installation.

GYMCI9007E An error occurred whileremotely connecting totarget. There are connectionproblems with the host.


GYMCI9008E An error occurred whileconnecting to target. Thereare connection problems withthe host.




GYMCI9009E An error occurred whilecopying install_dir.


GYMCI9010E Remote Command Executionhas been disabled.

To continue: 1. Change thestep property to Set AllowRemote Execution 2. Run thestep again. Or, manuallytransfer the directory to thehost. When the transfer iscompleted, change the stepstatus to Success andcontinue the installation.

GYMCI9011E An error occurred during filecreation.


GYMCI9012E An error occurred whileloading the discoveredtopology file.


GYMCI9013E An error occurred whileloading the topology file.


GYMCI9014E The installation engineencountered anunrecoverable error.


GYMCI9015E An error occurred whilesaving the topology file.


GYMCI9016E The installer cannot proceedwith the installation becausethere is insufficient diskspace on the local host.


GYMCI9017E The installer cannotdownload the topology fromthe specified database. Verifythat the Tivoli NetcoolPerformance Managerdatabase exists and that ithas been started. If it doesnot exist, launch the installer,providing a topology file.

Ensure that the correct hostname, port, and SID werespecified and that thedatabase has been started.

GYMCI9018E The installer cannot connectto the specified databaseindicated because ofincorrect credentials.

Ensure that you provide thecorrect user name andpassword.

GYMCI9019W The installer could notestablish a connection to thespecified database. Checkthat the Tivoli NetcoolPerformance Managerdatabase can be contacted.Click Next to proceedwithout checking the currentenvironment status.

Check that the Tivoli NetcoolPerformance Managerdatabase can be contacted.

GYMCI9020E The database connectionparameters do not matchthose in the topology file.

Ensure that you provide thecorrect parameters.



GYMCI9021E An error occurred whileloading the Oracle client jar.


GYMCI9022E The configuration file namewas not found. The stepcannot run.


GYMCI9023W There appear to be nodifferences between thedesired topology state andthe current state of the TivoliNetcool PerformanceManager installation. Theinstaller shows this messagewhen it determines there isnot work that it can do.Normally, this occurs whenthe Tivoli NetcoolPerformance Manager systemis already at the desiredstate. However, it can alsooccur when there arecomponent dependenciesthat are not satisfied.


GYMCI9024E The operating systemspecified for this node in thetopology file is not correct.

Correct the topology file.

GYMCI9025E The path is not valid or youdo not have permissions towrite to it.

Correct the parameter andtry again.

GYMCI9026E The path is not a validOracle path. The sqlpluscommand could not befound.


GYMCI9027E The specified port is notvalid.


GYMCI9028E At least one parameter isnull.

Specify values for therequired parameters.

GYMCI9029E The specified host namecontains unsupportedcharacters.

Ensure that host namesinclude only supportedcharacters.

GYMCI9030E The specified host cannot becontacted.

Ensure that the host name iscorrect and check that thehost is available.

GYMCI9031E The path not exists on thelocal system.

Correct the path and tryagain.



GYMCI9032E An error occurred whilesaving the topology. It hasnot been uploaded to theTivoli Netcool PerformanceManager database. This erroroccurs when there is adatabase connection error orwhen the Tivoli NetcoolPerformance Managerdatabase has not yet beencreated

See the log file for furtherdetails.

GYMCI9033E One of the followingparameters must be set to 1:param1 param2

Check the log file for furtherdetails. Redefine theparameters and try again.

GYMCI9034E An error occurred whilecreating mount pointdirectories.


GYMCI9035E An error occurred whilechanging the ownership orthe group of mount pointdirectories.


GYMCI9036E The machine hostname wasnot found in the TivoliNetcool PerformanceManager model(topology.xml file). Themachine where the installeris running is not part of theTivoli Netcool PerformanceManager topology.

If a host name alias is used,make the machine host namematch the host name in themodel. Alternatively, use theoption-DUsehostname=hostname tooverride the machine hostname used by the installer.

GYMCI9037E The Deployer version youare using is not compatiblewith the component that youare trying to install.

Use a Deployer at a versionthat supports thedeployment of thecomponent you are trying toinstall.

GYMCI9038E The XML file cannot be reador cannot be parsed.

Ensure the file is notcorrupted. See the log file formore details.

GYMCI9039E The deployment cannotproceed, because an erroroccurred the deploymentplan was being generated.

See the log file for moredetails. Check that there issufficient disk space and thatthe Deployer images are notcorrupted.

GYMCI9040E The Deployer cannot managethe indicated component onthe specified node.

See the log file for moredetails about the conditionthat was detected.

GYMCI9041E The user ID you specified isnot defined on the targetsystem.

Check that you havespecified the correct user ID.

GYMCI9042E You specified a host that isrunning on an unsupportedplatform.

Check that you havespecified the correct hostname.

GYMCI9043E The value you specified isnot supported.

Specify one of the supportedvalues.



GYMCI9044I To continue, go to the stepproperty, set Allow RemoteExecution, and rerun thestep or manually transfer thedirectory on the host. Whenthe transfer is completed, putthis step in a Success stateand continue the installation.


GYMCI9045I To continue, go to the stepproperty, set allow RemoteExecution and re-execute thestep or logon to host andperform task manually. Makesure the command completeswith a ZERO return codethen put this step in theSuccess state and continuewith the rest of theinstallation steps.


GYMCI9046I Remote Command Executionhas been disabled by CLIdirective.


GYMCI9047I There may not be enoughspace to install all selectedcomponents


GYMCI9048E An error occurred whileloading the DB2 client jar.


GYMCI9049E The path is not a valid DB2path. The clpplus commandcould not be found.


GYMCI9050E Run for uninstallation ofDataload only when you areuninstalling all Dataloads forhost/hosts.

Remove all Collectors onhost and try again

Topology Editor messagesThe Topology Editor messages.

Table 14 lists the error messages returned by the Topology Editor.

Table 14: Topology Editor Messages



GYM0001E A connection error wascaused by an SQL failurewhen running the report.Details are logged in thetrace file. There is aconnection problem with thedatabase. Possible problemsinclude: The database is notrunning. The databasepassword provided when theengine was created is wrongor has been changed.

Check the error log and tracefiles for the possible cause ofthe problem. Check that thedatabase is up and that theconnection credentials arecorrect. Correct the problemand try the operation again.

GYMCI0000E Folder name containingtechnology pack metadatafiles was not found. Thespecified folder does notexist.

Ensure that you have thecorrect location for thetechnology pack metadatafiles and try the operationagain.

GYMCI0001E An internal error, associatedwith the XML parserconfiguration, occurred.

Contact IBM SoftwareSupport.

GYMCI0002I No item has been found thatsatisfies the filtering criteria.

Ensure that you enter thecorrect filtering criteria andtry the operation again.

GYMCI0003E An error occurred whenreading XML file name. TheXML file might be corrupt orin an incorrect format.

Ensure that you haveselected the correct file andtry the operation again.

GYMCI0004E The input value must be aninteger.

Correct the input value andtry the operation again.

GYMCI0005E An unexpected element wasfound when reading theXML file.

Ensure that you haveselected the correct file andtry the operation again.

GYMCI0006E A value must be specified. Correct the input value andretry the operation.

GYMCI0007E The value must represent alog filter matching regularexpression expression.


GYMCI0008E Metadata file name was notfound. The specified file doesnot exist.

Ensure that you have thecorrect file name and pathand retry the operation.

GYMCI0009E Metadata file name iscorrupted.


GYMCI0010E Metadata file name wasalready imported. Do youwant to replace it?

Click Yes to replace the fileor No to cancel theoperation.

GYMCI0011E Object name was not foundin the repository. Thespecified object does notexist.

Ensure that you have thecorrect object name and trythe operation again.

GYMCI0012E The specified value mustidentify an existing directory.The specified directory doesnot exist.

Ensure that you have thecorrect directory name andtry the operation again.



GYMCI0013E Removing object from host inPhysical View.

No user action required.

GYMCI0014E File name does not exist. Ensure that you have thecorrect file name and try theoperation again.

GYMCI0015E An unexpected erroroccurred writing file name.See the trace file for details.

Ensure that there is sufficientspace to write the file in thefile system where theTopology Editor is running.

GYMCI0016E The user or password thatyou specified is wrong.

Correct the login credentialsand try the operation again.

GYMCI0017E The value specified for atleast one of the followingfields is not valid: host name,port, or SID.

Correct the input value orvalues and try the operationagain.

GYMCI0018E The file name is corrupted. Select a valid XML file.

GYMCI0019E An unexpected erroroccurred when retrievingdata from the database. Seethe trace file for details.

Ensure that the database isup and running and that youcan connect to it.

GYMCI0020E An unexpected erroroccurred when parsing filename. See the trace file fordetails.

Select a valid XML file.

GYMCI0021E An unexpected erroroccurred. See the trace filefor details.


GYMCI0022E The input value must be aboolean.


GYMCI0023E The specified value must beone of the followingoperating systems: AIX,SOLARIS, or Linux.


GYMCI0024E The value must be a softwareversion number in the formatn.n.n or n.n.n.n. For example7.1.2, or 7.1.2.1.


GYMCI0025E The value must be an integerin the range minValue tomaxValue, inclusive.


GYMCI0026E The value must be acomma-separated list ofstrings.


GYMCI0027E The value must be a file sizeexpressed in kilobytes. Forexample, 1024K.


GYMCI0028E The value must be a file sizeexpressed in megabytes. Forexample, 512M.




GYMCI0029E The value must be a file sizeexpressed in kilobytes ormegabytes. For example1024K or 512M.


GYMCI0030E The value must be an FTP orSFTP connection string. Forexample,ftp://username:password@hostname/directory.


GYMCI0031E The value must be acomma-separated list ofdirectories. For example,/opt, /var/tmp, /home.


GYMCI0032E Value cannot be afully-qualified domain name,IP address, or namecontaining hyphen or period.

Supply the unqualified hostname without the domain.Do not use the IP address ora name that containshyphens.

GYMCI0033E Metadata file name containsan technology pack with awrong structure.


GYMCI0034E Value should be in theformat YYYY-MM-DD,cannot be a date prior than1970-01-01, or later than thecurrent date.

Specify a date that is withinthe range and in the correctformat.

GYMCI0035E The meta-data file containsan technology pack with thewrong structure.

Obtain a valid meta-data fileand try again.

GYMCI0036E Value should be in theformat YYYY-MM-DD,cannot be a date prior than1970-01-01, or later than thecurrent date.

Correct the input value andretry the operation.

GYMCI0037E The operation failed becausethe specified file does notexist.

Ensure that the file nameand path you specified iscorrect and retry theoperation.

GYMCI0038E The operation failed becauseof an error while validatingthe host name mappings file.

See the trace file for moredetails.

GYMCI0039E The host name retrieved bythe upgrade process is notvalid. Fully qualified hostnames, IP addresses andnames containing hyphens orperiods are not supported.

Correct the entry for thespecified host name in thetopology definition.

GYMCI0040E The upgrade processretrieved two entries for thespecified host name. Thefully qualified host name isnot supported.

Remove the entry for thefully qualified host name.



GYMCI0040W The upgrade process did notretrieve a valid value for thespecified property. A defaultvalue has been used.

Check that the defaultassigned is appropriate andchange it if necessary.

GYMCI0041E No component is present onthe specified host.

Specify a host where at leastone component is present.

GYMCI0042E The operation failed becausethe input value is not thecorrect data type. The correctdata type is Long.


GYMCI0043E The operation failed becausethe input value is not valid.


GYMCI0044W The upgrade process did notretrieve a valid value for thespecified property. A defaultvalue has been used.

Check that the defaultassigned is appropriate andchange it if necessary.

InstallAnywhere messagesThe InstallAnywhere messages.

Table 14 lists the InstallAnywhere™

error messages. These messages could bereturned by either the deployer or the Topology Editor. See the InstallAnywheredocumentation for more information about these error codes and how to resolvethem.

Table 15: Install Anywhere Messages

Error Code Description

0 Success: The installation completedsuccessfully without any warnings or errors.

1 The installation completed successfully, butone or more of the actions from theinstallation sequence caused a warning or anon-fatal error.

8 The silent installation failed because of stepError errors.

-1 One or more of the actions from theinstallation sequence caused a fatal error.

1000 The installation was cancelled by the user.

1001 The installation includes an invalidcommand-line option.

2000 Unhandled error.

2001 The installation failed the authorizationcheck, may indicate an expired version.

2002 The installation failed a rules check. A ruleplaced on the installer itself failed.

2003 An unresolved dependency in silent modecaused the installer to exit.


Error Code Description

2004 The installation failed because not enoughdisk space was detected during theexecution of the Install action.

2005 The installation failed while trying to installon a Windows 64-bit system, but installationdid not include support for Windows 64-bitsystems.

2006 The installation failed because it waslaunched in a UI mode that is not supportedby this installer.

3000 Unhandled error specific to a launcher.

3001 The installation failed due to an errorspecific to the lax.main.class property.

3002 The installation failed due to an errorspecific to the lax.main.method property.

3003 The installation was unable to access themethod specified in the lax.main.methodproperty.

3004 The installation failed due to an exceptionerror caused by the lax.main.methodproperty.

3005 The installation failed because no value wasassigned to the lax.application.nameproperty.

3006 The installation was unable to access thevalue assigned to thelax.nl.java.launcher.main.class property.

3007 The installation failed due to an errorspecific to thelax.nl.java.launcher.main.class property.

3008 The installation failed due to an errorspecific to thelax.nl.java.launcher.main.method property.

3009 The installation was unable to access themethod specified in thelax.nl.launcher.java.main.method property.

4000 A Java executable could not be found at thedirectory specified by the java.home systemproperty.

4001 An incorrect path to the installer jar causedthe relauncher to launch incorrectly.


Log filesA description of the files that are used to log errors for the Tivoli NetcoolPerformance Manager components and its underlying framework.

Several files are used to log errors for the Tivoli Netcool Performance Managercomponents and its underlying framework. These log files include:v “COI log files”v “Deployer log file”v “Eclipse log file” on page 295v “Trace log file” on page 295

See the Technology Pack Installation Guide for information about the technology packlog files.

COI log filesCOI log files description.

The Composite Offering Installer (COI) adds a layer called the COI Plan to theTivoli Netcool Performance Manager installation. The COI Plan consists of a set ofCOI Machine Plans, one for each machine where Tivoli Netcool PerformanceManager components should be installed. A COI Machine Plan is a collection ofCOI Steps to be run on the corresponding machine.

The COI Plan is created in the directory /tmp/ProvisoConsumer/Plan.

The COI provides the following log files:

Table 16: COI Log Files

Log File Description Log File Location

MachinePlan_machinename_ [INSTALL_mmdd_hh.mm].log

For example:

MachinePlan_delphi_[INSTALL _0610_10.37].log

Contains detailedinformation about thetasks executed by theCOI steps on thespecified machine

/tmp/ProvisoConsumer/Plan/MachinePlan_machinename/logs/

DeploymentPlan.log Contains high-levelinformation about theCOI Plan execution

tmp/ProvisoConsumer/Plan/logs/INSTALL_mmdd_hh.mm

Deployer log fileDeployer log file description.

Installation errors and messages are written to the file /tmp/ProvisoConsumer/log.txt. The log file supports two levels:v High (FINEST) - This is the default and only setting.


Eclipse log fileEclipse log file description.

The Eclipse framework logs severe problems in a file under the Topology Editorinstallation directory (for example, /opt/IBM/Proviso/topologyEditor/workspace/.metadata). By default, the Eclipse log file is named .log. You should not need tolook there unless there is a problem with the underlying Eclipse framework.

Trace log fileTrace Log File description.

About this task

The trace log file is located in the Topology Editor installation directory (forexample, /opt/IBM/Proviso/topologyEditor). By default, this file is namedtopologyEditorTrace and the default trace level is FINE.

To change the trace level:

Procedure1. In the Topology Editor, select Window > Preferences. The Log Preferences

window opens.2. Select the new trace level. If desired, change the name of the log file.3. Click Apply to apply your changes. To revert back to the default values, click

Restore Defaults.4. Click OK to close the window.



Appendix I. Troubleshooting

This section lists problems that might occur during an installation and how toresolve them. The problems are grouped by the interface or component exhibitingthe problem.

Deployment problemsA list of deployment problem descriptions and solutions.

Problem Solution

The deployer window does not automaticallybecome the focus window after launchingfrom it from the Topology Editor.

Cause: In some cases (for example, when you export the display ona VNC session on Linux systems), the deployer window does notget the focus.

User action: Click on the deployer window or move other windowsto make the deployer window the focus window.

1. When the user tries to launch the Firefoxbrowser an error is displayed regardingthe Cairo 1.4.10 package.

2. In the Topology Editor, the minimize andmaximize buttons are red in color.

Note: This is an in-built feature in Eclipse4.2.2. See, http://stackoverflow.com/questions/12245102/eclipse-juno-red-minimize-and-maximize-buttons-on-linux

Cause: Cairo 1.4.10 may not support the requested image format.

User action: Start VNC server using the following command:/usr/bin/X11/vncserver -depth 24 -geometry 1280x1024

In a fresh installation, the databaseinstallation step fails.

Cause: You did not perform the necessary preparatory steps.

User action: This step verifies that the Oracle Listener is workingproperly before actually creating the Tivoli Netcool PerformanceManager database. If the step fails: 1. Complete the necessarymanual steps (see “Configure the Oracle listener” on page 111). 2.Change the status of the step to Ready. 3. Resume the installation.The step should complete successfully.


http://stackoverflow.com/questions/12245102/eclipse-juno-red-minimize-and-maximize-buttons-on-linux



Problem Solution

An installation step hangs. Cause: There are many possible causes.

User action:

1. Make sure the installation step is really in a hung state. Forexample, the Tivoli Netcool Performance Managerdatabase-related steps might take more than an hour to complete;other steps complete in far less time.

2. Determine which child process is causing the hang. First, find theinstaller process by entering the following command:

ps -ef

The installer process has an entry similar to this one:

root 12899 7290 10 13:43:31 pts/7 0:10/tmp/install.dir.12899/Solaris/resource/jre/jre/bin/java -Djava.compiler=NONE -

3. Find the process that has that process number (for example,12899) as its father. Continue until you find the last process.

4. Kill the last process using the following command:

kill -9

At this point, the status of the hung step will change toError.

5. If you can determine the cause of the hang, fix the problem andresume the installation. Otherwise, collect the log files andcontact IBM for support.

The deployer hangs when displaying thePreview page. (This step normally takes onlya few seconds).

Cause: The NFS file system is not working properly. User action:Run the df -k command and make sure that all NFS mounted filesystems are working properly. When the problem has beencorrected, restart the deployer.

There is a problem with remote commandexecution.

Cause: The deployer uses either RSH or OpenSSH to performremote command execution. You must configure OpenSSH to makethis connection possible.

User action: After configuring OpenSSH, run the test programprovided in deployer_root/proviso/data/Utils/testremote.sh to testyour configuration, where deployer_root is the root directory for thedeployer. For example:

/export/home/pvuser/443/SOLARIS/Install/ SOL9/deployer

Installation messages report success, butmight include messages similar to thefollowing: Fatal Error]:4:1: An invalidXML character (Unicode: 0x1b) was foundin the element content of the document.

This is screen noise and can safely be ignored.

When you click the Done button to completea fresh installation, the deployer displaysdatabase access error messages.

Cause: You stopped a fresh installation before the installing andconfiguring the Tivoli Netcool Performance Manager database.

User action:If the Tivoli Netcool Performance Manager database hasnot been installed, complete the installation using the-Daction=resume option (see “Resuming a partially successfulfirst-time installation” on page 169). If the database has beeninstalled, there is another problem. Contact IBM Software Support.


Problem Solution

Data does not appear in real-time reports,and right-clicking on a real-time report doesnot display the option menu. This problemcan occur with a silent installation on aSolaris system.

Cause: When it starts, the channel manager (CMGR) placesinformation in the database that is needed for real-time reports tostart correctly. During installation, a cron job is created that startsCMGR. A silent installation might run fast enough that the cron jobdoes not run before DataView is started. In this case, CMGR doesnot add the required information to the database, and real-timereports do not start up correctly.

User action:

1. Make sure that the CMGR process is running (see “Managementprograms and watchdog scripts” on page 232 and “Starting theDataChannel management programs” on page 234).

2. Restart DataView.

Saving installation configuration filesInstallation configuration files can be used to troubleshoot a Tivoli NetcoolPerformance Manager installation.

When you install Tivoli Netcool Performance Manager components, the deployercreates a set of temporary configuration files that are used during the installationprocess. These files specify the components that are to be installed on a targetsystem and the deployment information required to install them. You can use theseconfiguration files to troubleshoot a Tivoli Netcool Performance Managerinstallation.

The temporary configuration files are normally removed from the target systemwhen the deployer completes the installation process. You can prevent thedeployer from removing the files by editing the installer XML file associated with acomponent. This file is named n_comp_name.xml, where n is an index numbergenerated by the deployer and comp is a string that identifies the component.Possible values for the comp string are DataView, DataMart, DataView, DBChannel andDBSetup. Installer XML files are located by default in the /tmp/ProvisoConsumer/Plan/MachinePlan_hostname directory, where hostname is the host name of thetarget system.

To prevent the deployer from removing the temporary files associated with acomponent install, open the corresponding install XML file and modify thefollowing element so that the value of the arg2 property is false:

<equals arg1="${remove.temporary.files}" arg2="true"/>

The following excerpt from the file shows the resulting XML element:<equals arg1="${remove.temporary.files}" arg2="false"/>

When you contact IBM support about a Tivoli Netcool Performance Managerinstallation problem, the support staff might ask you for these files. You can createa tar file or zip archive that contains the entire contents of the/tmp/ProvisoConsumer directory and send it to the IBM support staff for assistance.

Appendix I. Troubleshooting 299

Tivoli Netcool Performance Manager component problemsA list of Tivoli Netcool Performance Manager component problems and solutions.

Problem Solution

A Tivoli Netcool Performance Managercomponent is still listed as Configured inthe Topology Editor even though is installed.

Cause: The component is installed, but hasnot been started. User action: Start thecomponent. Its status changes to Installed.

A new channel component was deployed, orthe channel configuration was changed, butthe change has no effect.

Cause: The channel components need to bebounced. User action: Bounce thecomponents, as described in Appendix B,“DataChannel architecture,” on page 231.

Topology Editor problemsA list of Topology Editor problems and solutions.

Problem Solution

The Topology Editor won't open and the applicationwindow shows a Java exception (core dump).

Cause: You forgot to set and export your DISPLAYvariable. User action: 1. Enter the following commands:

$ DISPLAY=Host_IP_Address:0.0 $ export DISPLAY

2. Restart the Topology Editor.

The splash screen for the Topology Editor is displayed,but the Topology Editor doesn't start and no explanatorymessage is displayed.

Cause: You did not log in as root. User action: 1. Log inas root. 2. Restart the Topology Editor.

The Topology Editor reports the following error whenyou attempt to add a UBA collector: GYMCI0504E Aninternal error occurred while processing file pack

Where pack is the name of the application jar file. Inaddition, the Topology Editor log file contains thefollowing error: YYYY-MM-DD HH:MM:SS SEVEREFileHelper Manifest of file pack is corrupted. Itwas not possible to determine if its install typeis bundle or standalone.

Cause: You tried to add a UBA collector for an SNMPtechnology pack. User action: Make sure that you readthe Tivoli Netcool Performance Manager technologypacks release notes before you install and configure apack and before you add any collectors. The releasenotes contain information on whether a specifictechnology pack is a UBA or SNMP pack. UBA andSNMP packs require you to perform differentconfiguration steps. Before you install and configure antechnology pack, you must also read the information in"Before You Begin" on page Chapter 6:-129 and followthe steps listed in that section.

Tivoli Netcool Performance Manager DB2 database schema fails

Symptoms

The following error might cause the Tivoli Netcool Performance Manager databaseschema installation to fail.SQL0440N No authorized routine named "DB2AUTH.ADD_USER_PL" of type "PROCEDURE"having compatible arguments was found.

This error indicates that the db2auth related files, which are needed during the DB2database installation are missing. These files are normally copied over during


Tivoli Netcool Performance Manager installation process but if for some reason thefiles are not copied over, the Tivoli Netcool Performance Manager database schemainstallation fails.

Resolving the problemYou need to manually copy the db2auth related files from the Tivoli NetcoolPerformance Manager distribution directory to /opt/db2ns/sqllib/security64/plugin/group directory.

For example:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL<version_num>/db2/instance# cp db2authDaemon db2auth.so /opt/db2ns/sqllib/security64/plugin/group

# ls -lrt /opt/db2ns/sqllib/security64/plugin/group-rwxr-xr-x 1 root root 39041 Sep 28 06:34 db2authDaemon-rwxr-xr-x 1 root root 39865 Sep 28 06:34 db2auth.so

Telnet problemsA list of Topology Editor problems and solutions.

Problem Solution

Telnet client fails at initial connection and reports thefollowing error: Not enough room in buffer for displaylocation option reply Can occur when you start TivoliNetcool Performance Manager components from aSolaris 10 system where the user interface is displayedremotely on a Windows desktop using an X Window toollike Exceed.

Cause: Length of the DISPLAY variable passed via thetelnet client is too long (for example,XYZ-DA03430B70B-009034197130.example.com:0.0). Useraction: Set the value of the DISPLAY variable using theIP address of the local system, or the hostname onlywithout the domain name. Then, reconnect to the Solaris10 machine using the telnet client.

Java problemsA list of Java problems and solutions.

Problem Solution

Installer reports a Java Not Found errorduring installation of technology packs.

Cause: The installer expected, but did notfind, Java executables in the path reported inthe error message. The technology packinstallation requires the correct path in orderto function. User action: Create a symboliclink from the reported directory to thedirectory on the system where the Javaexecutables are installed, for example:

ln -s bin_path $JAVA_HOME/bin/java

where bin_path is the directory where thebinaries are located. After you create thesymbolic link, you must re-start thetechnology pack installation.


Testing connectivity to the database

How to test the connectivity to the Oracle database.

About this task

To test client connectivity to the Oracle database:

Procedure1. Make sure you are logged in as oracle and that the DISPLAY environment

variable is set.2. Enter the following command:

$ sqlplus system/[email protected]

In this syntax:v password is the password you set for the Oracle system login name. (The

default password is manager.)v PV is the TNS name for your Tivoli Netcool Performance Manager database

defined in your Oracle Net configuration.For example:

$ sqlplus system/[email protected]

3. Output like the following example indicates a successful connection:

SQL*Plus: Release 12.1.0.2.0 - Production on <Current Date>

Copyright (c) 1982, 2010, Oracle Corporation. All rights reserved.

Connected to:Oracle12c Enterprise Edition Release 12.1.0.2 - ProductionWith the Partitioning optionJServer Release 12.1.0.2.0 - Production

SQL>

4. Type exit at the SQL> prompt.

Testing external procedure call access

In the Oracle Net configuration, you set up an Oracle listener to wait forconnections using external procedure calls.

About this task

The shared library libpvmextc.so executes system commands from stored Oracleprocedures. This file is installed in the $ORACLE_BASE/admin/PV/lib directory(where PV is the ORACLE_SID). A symbolic link to this library file is created by theconfigure_db script in the $ORACLE_HOME/lib directory.

To test external procedure call access:

Procedure1. Make sure you are logged in as oracle and that the DISPLAY environment

variable is set.2. At a shell prompt, change to the following directory path:


$ cd $ORACLE_BASE/admin/skeleton/bin

3. Run the checkextc script, using the system database login name and passwordas a parameter:$ ./checkextc system/password

For example:$ ./checkextc system/manager

4. Output like the following example indicates a successful test.

checkextc - Checking the installation of the library libpvmextc.so

This program try to execute the following unix commandsfrom a PL/SQL stored procedure.

1- Check ExternalCall : echo "UNIX : Check libpvmextc.so configuration."

2- Check Version

3- Check ExternalPipe : pwd

ORACLE : Connecting to Oracle ...ORACLE : Creating library LibExtCall ...ORACLE : Creating function ExternalCall ...ORACLE : Calling function ExternalCall ...UNIX : Check libpvmextc.so configuration succeeded.ORACLE : Creating function Version ...ORACLE : Calling function Version ...UNIX : Check Version libpvmextc.so - Revision: 1.0.1.1ORACLE : Creating function ExternalPipe ...ORACLE : Calling function ExternalPipe ...UNIX : Check ExternalPipe - /var/opt/oracleORACLE : Dropping function Version ...ORACLE : Dropping function ExternalCall ...ORACLE : Dropping function ExternalPipe ...ORACLE : Dropping library LibExtCall ...



Appendix J. Moving DataView content between DashboardApplication Services Hub servers

You can use the synchronize command to move custom DataView content betweenDashboard Application Services Hub servers.

You can copy your custom DataView content, such as JSP pages, CSS and images,from a remote Dashboard Application Services Hub server to a local DashboardApplication Services Hub server. All remote content is copied to the local contentdirectory at JazzSM_HOME/products/tnpm/dataview/legacy/content.

The synchronize commandCopies custom DataView content, such as JSP pages, CSS and images, from aremote Dashboard Application Services Hub to a local Dashboard ApplicationServices Hub. All remote content is copied to the local content directory at<DASH_location>//products/tnpm/dataview/legacy/content.

Location

<DASH_location>/products/tnpm/dataview/legacy/bin

Where <DASH_location> is the Dashboard Application Services Hub installationdirectory, by default /opt/IBM/JazzSM.

Required privileges

Adequate privileges are required to read and write files to the file system. Youmust run this command from the UNIX command line as the Tivoli NetcoolPerformance Manager UNIX user (by default, pvuser), or a user with similar orgreater privileges.

Syntax

synchronize.sh -dashuser <DASH_username> -dashpassword <DASH_password>-sourceuser <source_username> -sourcepassword <source_password> -sourceurl<source_url> [-pattern <pattern>]

Parameters

<DASH_username>A Dashboard Application Services Hub user name for the local DashboardApplication Services Hub.

<DASH_password>The Dashboard Application Services Hub user password for the localDashboard Application Services Hub.

<source_username>A Dashboard Application Services Hub user name for the remote DashboardApplication Services Hub.


<source_password>The Dashboard Application Services Hub user password for the remoteDashboard Application Services Hub.

<source_url>The URL of the remote server, including the port and DataView context.

Optional parameter

<pattern>The name pattern that identifies the types of files to filter for thesynchronization. Wildcards * and ? are supported. To synchronize all files, omitthe pattern; do not use * on its own to synchronize all files.

Example

The following command synchronizes the DataView custom .jsp file content froma remote Dashboard Application Services Hub or Tivoli Integrated Portal to a localDashboard Application Services Hub:./synchronize.sh -dashuser smadmin -dashpasswordsmadmin1 -sourceuser tipadmin -sourcepasswordtipadmin -sourceurl http://10.44.240.70:16710/PV -pattern *.jsp

./synchronize.sh -dashuser smadmin -dashpasswordsmadmin1 -sourceuser tipadmin -sourcepasswordtipadmin -sourceurl http://10.44.240.70:16310/PV

By default, the <source_url> is:http://server.ibm.com:16310/PV


Notices

This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of those


websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

The performance data discussed herein is presented as derived under specificoperating conditions. Actual results may vary.

The client examples cited are presented for illustrative purposes only. Actualperformance results may vary depending on specific configurations and operatingconditions.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to actual people or business enterprises is entirelycoincidental.

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work mustinclude a copyright notice as follows:

© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. _enter the year or years_.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Notices 309

http://www.ibm.com/legal/us/en/copytrade.shtml

Java and all Java-based trademarks and logosare trademarks or registered trademarks ofOracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.


IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Notices 311


IBM®

Printed in USA

Date post:	30-Jul-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

with IBM Corp. · 2017-04-28 · Installa tion Guide IBM. Note Befor e using this information and...

Documents