TNPM 1.3.1 Install Guide Wireline Component

Tivoli® Netcool Performance Manager 1.3.1Wireline ComponentDocument Revision R2E1

Installation Guide1.3.1

��

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

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

Contents

Preface . . . . . . . . . . . . . . viiAudience . . . . . . . . . . . . . . . viiTivoli Netcool Performance Manager - WirelineComponent . . . . . . . . . . . . . . viiThe Default UNIX Shell . . . . . . . . . . ix

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

Co-location rules . . . . . . . . . . . . 2Inheritance . . . . . . . . . . . . . . 4Notable subcomponents and features . . . . . 5

Typical installation topology . . . . . . . . . 8Basic topology scenario . . . . . . . . . . 8Intermediate topology scenario . . . . . . . 9Advanced topology scenario. . . . . . . . 10

Tivoli Netcool Performance Manager distribution . . 11

Chapter 2. Installing and configuringthe prerequisite software . . . . . . . 13Overview . . . . . . . . . . . . . . . 13

Supported platforms . . . . . . . . . . 14Pre-Installation setup tasks . . . . . . . . . 14

Setting up a remote X Window display . . . . 14Changing the ethernet characteristics . . . . . 15Adding the pvuser login name . . . . . . . 18Setting the resource limits (AIX only) . . . . . 20Set the system parameters (Solaris only) . . . . 21Enable FTP on Linux systems (Linux only) . . . 23Disable SELinux (Linux only) . . . . . . . 23Set the kernel parameters (Linux only) . . . . 24Install a libcrypto.so . . . . . . . . . . 24

Deployer pre-requisites . . . . . . . . . . 25Operating system check . . . . . . . . . 25Mount points check . . . . . . . . . . 25Authentication between distributed servers . . . 26

Downloading the Tivoli Netcool PerformanceManager distribution to disk . . . . . . . . 26

Downloading Tivoli Common Reporting to disk 27General Oracle setup tasks . . . . . . . . . 27

Specifying a basename for DB_USER_ROOT . . 28Specifying Oracle login passwords. . . . . . 28Assumed values . . . . . . . . . . . . 29

Installing the Oracle server . . . . . . . . . 30Ensure that the Oracle User is not in NIS . . . 30Download the Oracle distribution and patch todisk . . . . . . . . . . . . . . . . 31Verify the required operating system packages. . 32Run the Oracle server configuration script . . . 33Set a password for the Oracle login name . . . 36Run the pre-installation script . . . . . . . 36Run the rootpre.sh script (AIX only) . . . . . 37Verify PATH and environment for the Oraclelogin name . . . . . . . . . . . . . 38Install Oracle . . . . . . . . . . . . . 38Run the root.sh script . . . . . . . . . . 42

Install Oracle patches . . . . . . . . . . 43Relax permissions on ORACLE_HOME . . . . 44Set the ORACLE_SID variable . . . . . . . 45Set automatic startup of the database instance . . 45Configure the Oracle listener . . . . . . . 46Configure the Oracle net client . . . . . . . 48Shut down of performance impacting Oracle jobs 50

Installing the Oracle client . . . . . . . . . 50Ensure that the Oracle User is not in NIS . . . 50Download the Oracle distribution and patch todisk . . . . . . . . . . . . . . . . 51Run the Oracle client configuration script . . . 52Set a password for the Oracle login name . . . 54Run the pre-installation script . . . . . . . 54Verify PATH and environment for the Oraclelogin name . . . . . . . . . . . . . 55Install the Oracle client . . . . . . . . . 56Run the root.sh script . . . . . . . . . . 58Install Oracle patches . . . . . . . . . . 58Relax permissions on ORACLE_HOME . . . . 60Configure the Oracle net client . . . . . . . 60

Next steps . . . . . . . . . . . . . . . 62

Chapter 3. Installing in a distributedenvironment . . . . . . . . . . . . 63Distributed installation process . . . . . . . . 63Starting the Launchpad . . . . . . . . . . 65Installing the Topology Editor . . . . . . . . 66Starting the Topology Editor. . . . . . . . . 67Creating a new topology . . . . . . . . . . 68Adding and configuring the Tivoli NetcoolPerformance Manager components . . . . . . 68

Add the hosts . . . . . . . . . . . . 68Add a database configurations component . . . 70Add a DataMart . . . . . . . . . . . . 71Add a Discovery Server . . . . . . . . . 73Add a Tivoli Integrated Portal . . . . . . . 74Add a DataView. . . . . . . . . . . . 75Add the DataChannel administrative components 76Add a DataChannel . . . . . . . . . . 76Add a Collector . . . . . . . . . . . . 78Add a Cross Collector CME . . . . . . . . 80

Saving the topology . . . . . . . . . . . 81Opening an existing topology file . . . . . . 82

Starting the Deployer . . . . . . . . . . . 82Primary Deployer . . . . . . . . . . . 82Secondary Deployers . . . . . . . . . . 83Pre-deployment check . . . . . . . . . . 83

Deploying the topology . . . . . . . . . . 84Next steps . . . . . . . . . . . . . . . 86Resuming a partially successful first-timeinstallation . . . . . . . . . . . . . . 87

Chapter 4. Installing as a minimaldeployment. . . . . . . . . . . . . 89

© Copyright IBM Corp. 2006, 2010 iii

Overview . . . . . . . . . . . . . . . 89Before you begin . . . . . . . . . . . . 89

Special consideration . . . . . . . . . . 90Overriding default values . . . . . . . . 90

Installing a minimal deployment . . . . . . . 91Download the MIB-II files . . . . . . . . 91Starting the Launchpad . . . . . . . . . 91Start the installation . . . . . . . . . . 92

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

Chapter 5. Modifying the currentdeployment. . . . . . . . . . . . . 95Opening a deployed topology . . . . . . . . 95Adding a new component . . . . . . . . . 96Changing configuration parameters of existingTivoli Netcool Performance Manager components . 98Moving components to a different host . . . . . 98Moving a deployed collector to a different host . . 99

Moving a deployed SNMP collector . . . . . 99Moving a deployed UBA bulk collector. . . . 101

Chapter 6. Using the High AvailabilityManager . . . . . . . . . . . . . 105Overview. . . . . . . . . . . . . . . 105HAM basics . . . . . . . . . . . . . . 105

The parts of a collector . . . . . . . . . 106Clusters . . . . . . . . . . . . . . 107

HAM cluster configuration . . . . . . . . . 107Types of spare hosts . . . . . . . . . . 107Types of HAM clusters . . . . . . . . . 108Example HAM clusters . . . . . . . . . 108

Resource pools . . . . . . . . . . . . . 114How the SNMP collector works . . . . . . . 114

How failover works with the HAM and theSNMP collector . . . . . . . . . . . . 115Obtaining collector status . . . . . . . . 116

Creating a HAM environment . . . . . . . . 117Topology prerequisites . . . . . . . . . 118Procedures . . . . . . . . . . . . . 118Create the HAM and a HAM cluster . . . . 118Add the designated spare . . . . . . . . 119Add the managed definitions . . . . . . . 120Define the resource pools . . . . . . . . 121Save and start the HAM. . . . . . . . . 123Creating an additional HAM environment. . . 124

Modifying a HAM environment . . . . . . . 124Removing HAM components . . . . . . . 124Stopping and restarting modified components 125

Viewing the current configuration . . . . . . 125Show Collector Process... dialog . . . . . . 126Show Managed Definition... dialog . . . . . 126

Chapter 7. Uninstalling components 129Removing a component from the topology . . . 129

Restrictions and behavior . . . . . . . . 129Removing a component . . . . . . . . . 130

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

Order of uninstall . . . . . . . . . . . 131

Restrictions and behavior . . . . . . . . 132Performing the uninstall. . . . . . . . . 132

Uninstalling the topology editor . . . . . . . 133Residual files . . . . . . . . . . . . . 133

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

FTP is possible, but REXEC or RSH are not . . 137Neither FTP nor REXEC/RSH are possible . . 138

Installing on a remote host using a secondarydeployer . . . . . . . . . . . . . . . 138

Appendix B. DataChannels . . . . . 141Data collection . . . . . . . . . . . . . 141

Data aggregation . . . . . . . . . . . 141Management programs and watchdog scripts 142DataChannel application programs . . . . . 143

Starting the DataLoad SNMP collector . . . . . 144DataChannel management components in adistributed configuration . . . . . . . . . 145

Manually starting the Channel Managerprograms . . . . . . . . . . . . . . 146

Adding DataChannels to an existing system . . . 146DataChannel terminology . . . . . . . . . 147

Appendix C. Aggregation sets . . . . 149Overview. . . . . . . . . . . . . . . 149Configuring aggregation sets . . . . . . . . 149Installing aggregation sets . . . . . . . . . 153

Start the Tivoli Netcool Performance Managersetup program . . . . . . . . . . . . 153Set aggregation set installation parameters . . 153Edit aggregation set parameters file . . . . . 156

Linking DataView groups to timezones. . . . . 157

Appendix D. Deployer CLI options 159Using the -DTarget option . . . . . . . . . 160

Appendix E. Secure file transferinstallation . . . . . . . . . . . . 163Overview. . . . . . . . . . . . . . . 163Enabling SFTP . . . . . . . . . . . . . 163Installing OpenSSH . . . . . . . . . . . 164

AIX systems . . . . . . . . . . . . . 164Solaris systems . . . . . . . . . . . . 166Linux systems . . . . . . . . . . . . 168

Configuring OpenSSH . . . . . . . . . . 168Configuring the OpenSSH server . . . . . . 168Configuring OpenSSH client . . . . . . . 169Generating public and private keys . . . . . 169

Testing OpenSSH and SFTP . . . . . . . . 172Troubleshooting . . . . . . . . . . . . 172Netcool/Provisio SFTP errors . . . . . . . . 173

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

Enable LDAP configuration . . . . . . . 175

iv IBM Tivoli Netcool Performance Manager: Installation Guide

Verifying the DataView installation . . . . . 176Assigning Tivoli Netcool Performance Managerroles to LDAP users . . . . . . . . . . 176

Appendix G. Using silent mode. . . . 179Sample properties files . . . . . . . . . . 179The Deployer . . . . . . . . . . . . . 179

Running the Deployer in silent mode . . . . 179Confirming the status of a silent install . . . . 180Restrictions . . . . . . . . . . . . . 181

The Topology Editor . . . . . . . . . . . 181

Appendix H. Installing an interim fix 183Overview. . . . . . . . . . . . . . . 183

Installation rules . . . . . . . . . . . 183Behavior and restrictions . . . . . . . . 183

Before you begin . . . . . . . . . . . . 184Installing a patch . . . . . . . . . . . . 184

Appendix I. Error codes and log files 187Error codes . . . . . . . . . . . . . . 187

Deployer messages . . . . . . . . . . 187Topology Editor messages . . . . . . . . 200InstallAnywhere messages . . . . . . . . 204

Log files . . . . . . . . . . . . . . . 205COI log files. . . . . . . . . . . . . 205Deployer log file . . . . . . . . . . . 206Eclipse log file . . . . . . . . . . . . 206

Trace log file . . . . . . . . . . . . 206

Appendix J. Troubleshooting. . . . . 207Deployment problems . . . . . . . . . . 207

Saving installation configuration files . . . . 209Tivoli Netcool Performance Manager componentproblems . . . . . . . . . . . . . . . 209Topology Editor problems . . . . . . . . . 210Telnet problems . . . . . . . . . . . . 210Java problems . . . . . . . . . . . . . 211Testing connectivity to the database . . . . . . 211Testing external procedure call access . . . . . 212

Appendix K. Migrating DataViewcontent and users . . . . . . . . . 213Moving DataView content between TivoliIntegrated Portal servers. . . . . . . . . . 213

The synchronize command . . . . . . . . 213Migrating SilverStream content to the TivoliIntegrated Portal . . . . . . . . . . . . 214

SilverStream page conversion . . . . . . . 214The migrate command . . . . . . . . . 216

Notices . . . . . . . . . . . . . . 219

Trademarks . . . . . . . . . . . . 223

Contents v

vi IBM Tivoli Netcool Performance Manager: Installation Guide

Preface

The purpose of this manual

IBM® Tivoli Netcool Performance Manager 1.3.1 is a bundled product consisting ofa wireline component and a wireless component.

The purpose of this guide is to help you install theTivoli Netcool PerformanceManager product suite and the Oracle database management system.

This guide provides instructions for installing Tivoli Netcool Performance Managercomponents, but not necessarily for configuring the installed components into afinished system that produces management reports. After going through the stepsin this guide, you will have a set of running Tivoli Netcool Performance Managercomponents ready to configure into a fully functional system.

The goal of this guide is to get each component installed and running in its barestform. The running component does not necessarily have network statistical dataflowing into and out of it yet. In particular, at the end of this installationprocedure, there are no or few management reports that can be viewed inDataView.

Configuring installed components into a working system is the subject of othermanuals in the Tivoli Netcool Performance Manager documentation set.

AudienceThe audience for this manual.

The audience for this manual is the network administrator or operations specialistresponsible for installing the Tivoli Netcool Performance Manager product suite onan enterprise network. To install Tivoli Netcool Performance Manager successfully,you should have a thorough 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 Tivoli Netcool Performance Manager

Tivoli Netcool Performance Manager - Wireline ComponentIBM® Tivoli® Netcool® Performance Manager 1.3.1 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.

© Copyright IBM Corp. 2006, 2010 vii

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 Configuration recommendationsv User guidesv Technical notesv Online help

The documentation is available for viewing and downloading on the informationcenter at http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.html.

viii IBM Tivoli Netcool Performance Manager: Installation Guide

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.html

The Default UNIX ShellAdd short description The installation scripts and procedures in this manualgenerally presume, but do not require, the use of the Korn or Bash shells, and onlyKorn shell syntax is shown 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 or

pvuser.v SQL> indicates commands you perform at the SQL*Plus prompt.

Preface ix

x IBM Tivoli Netcool Performance Manager: Installation Guide

Chapter 1. Introduction

Introduction to Tivoli Netcool Performance Manager installation.

This chapter provides an overview of the Tivoli Netcool Performance Managerproduct suite and provides important pre-installation setup information. Inaddition, this chapter provides an overview of the installation interface introducedin version 1.3.1.

Tivoli Netcool Performance Manager architectureTivoli Netcool Performance Manager system components.

The Tivoli Netcool Performance Manager components run on:v SPARC-based servers from Sun Microsystems that run the Solaris operating

systemv AIX servers from IBMv Linux servers

Exact, release-specific requirements, prerequisites, and recommendations forhardware and software are described in detail in the IBM Tivoli NetcoolPerformance Manager: Configuration Recommendations Guide.

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.

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.

© Copyright IBM Corp. 2006, 2010 1

v Tivoli Netcool Performance Manager DataMart - Tivoli Netcool PerformanceManager 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 hosting and analysis platform. Thisplatform is used to display Web-based management reports based on networkdata 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 generated by network devices. Each technology pack is specificfor a particular device, or class of devices; or for a particular company's devices;or for a protocol (such as standard SNMP values) common to many devices.

v Tivoli Integrated Portal - The Tivoli Integrated Portal application provides adatabase-aware Web server foundation for the Web-based management reportsdisplayed by Tivoli Netcool Performance Manager DataView. The TivoliIntegrated Portal application server is an essential component of each DataViewinstallation.

Platform support

All components of the Tivoli Netcool Performance Manager - Wireline Componentcan run on a heterogenous mix of AIX, Linux, and Solaris operating systems.

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 share thesame filesystem.

2 IBM Tivoli Netcool Performance Manager: Installation Guide

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

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

Chapter 1. Introduction 3

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

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 asscociated Default Value is alsoupdated.

If we change the DUS Remote User property value, that is the child value, it doesnot propogate 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.


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

CollectorsCollectors 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.

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.

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

The number of collectors in your system will affect the topology configuration. Youcan have multiple BULK collectors, UBA or BCOL, on a single host, but you canonly have one SNMP based collector per host. The number of collectors is in turndriven by the number of required Technology Packs.

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 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 theIBM Tivoli Netcool Performance Manager: Technology Pack Installation Guide,pack-specific installation guides are also provided. Please consult both sets ofdocumentation for important installation or topology information.

High AvailabilityHigh Availability description.

High availability can be implemented for Tivoli Netcool Performance Manager intwo forms:v High Availability Manager (HAM): This is a DataChannel component that can

be configured to handle availability of SNMP collectors.v Veritas Cluster or Sun Cluster (referred to as HA within the documentation):

This method of implementing high availability has a much broader scope andcan cover all or a combination of the database, DataChannel, DataMart andDataView components.

The following High Availability (HA) documents are available for download fromthe Tivoli Open Process Automation Library (OPAL), http://www-01.ibm.com/software/brandcatalog/opal/.v TNPM High Availability Overview

Describes high availability solutions for the Tivoli Netcool Performance Managerproduct.

v Sun Cluster TNPM Agent Guide

Describes how Sun Clusters can be used with TNPM to created a highavailability Tivoli Netcool Performance Manager system.

v High Availability Operations and Deployment

Describes an example system that was configured to provide high availability.v TNPM High Availability Installation and Configuration

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

For information covering the High Availability Manager, see Chapter 6, “Using theHigh Availability Manager,” on page 105


Installation and topology considerations for the High Availability Manager.

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

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:


http://www-01.ibm.com/software/brandcatalog/opal/


v Disk space is running low: Disk space may be impacted by the addition of anew DataChannel component. In which case, the user may want to add a newfile system managed by a new Disk Usage Server.

v Separate disk quota management: The user may want to separately manage thequotas assigned to discrete DataChannel components. For more information, see“Disk quota management.”

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 management:

Disk 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 should an estimate beincorrect, only one number needs to be changed instead of potentially updating thequota for each component separately.

Flow control:

Flow 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 considerations for flow control.

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


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 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 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 client

v Tivoli NetcoolPerformance ManagerDataChannel

You could install TivoliNetcool PerformanceManager componentsremotely on this system

athens v Oracle client

v Tivoli Integrated Portal

v Tivoli NetcoolPerformance ManagerDataView

You could install TivoliNetcool PerformanceManager componentsremotely on this system.Your configuration can use apre-existing Tivoli IntegratedPortal, or install and includea 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 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 second machine,thessaloniki, for the purposes of failover. HAM only manages SNMP collectors;therefore, the HAM in this scenario will manage availability of the DataLoadSNMP collector and not the Bulk Load collector. The HAM must be put on thesame 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 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 client




Tivoli Netcool Performance Manager distributionHow to get your hands on the product distribution.

The Tivoli Netcool Performance Manager distribution is available as a DVD/CDand as an electronic image. The instructions in this guide assume that you areinstalling 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 any changes to the environment, including uninstalling TivoliNetcool Performance Manager.


Chapter 2. Installing and configuring the prerequisite software

Installing and configuring the software required by Tivoli Netcool PerformanceManager.

This chapter describes how to install and configure the prerequisite software forTivoli Netcool Performance Manager.

OverviewBefore beginning the Tivoli Netcool Performance Manager installation, you mustinstall the prerequisite software listed in the IBM Tivoli Netcool PerformanceManager: Configuration Recommendations Guide.

The required software includes:v Oracle server: To use Oracle with Tivoli Netcool Performance Manager, you

must install Oracle as described in this chapter - do not use a separate Oracleinstallation method provided by Oracle Corporation.

v Oracle client: You must install Oracle client software on each system where youplan to install a Tivoli Netcool Performance Manager component, except for thesystem where you installed the Oracle server.When you complete the steps in this chapter, the Oracle server and client will beinstalled and running, with tablespaces sized and ready to accept the installationof a Tivoli Netcool Performance Manager DataMart database. You cancommunicate with Oracle using the SQLPlus command-line utility.The steps in this chapter use IBM-provided installation scripts to install andconfigure the Oracle database from the Oracle distribution and patch. For usewith Tivoli Netcool Performance Manager, you must install Oracle as describedin this chapter. Do not use a separate Oracle installation method provided byOracle Corporation. You should obtain the official Oracle distribution from youredelivery site (after purchase of an Oracle license). See the IBM Tivoli NetcoolPerformance Manager: Configuration Recommendations Guide for recommendationswhen purchasing a license from Oracle.

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

v OpenSSH: You must install and configure OpenSSH before installing TivoliNetcool Performance Manager. For details, see Appendix E, “Secure file transferinstallation,” on page 163. Linux systems require the installation of VSFTP (VerySecure FTP).

v Web browser: The launchpad requires a Web browser. IBM recommends usingMozilla with the launchpad. For the complete list of supported browsers, see theIBM Tivoli Netcool Performance Manager: Configuration Recommendations Guidedocument.

v Java: Java is used by DataMart, DataLoad, and the technology packs. You mustensure you are using the IBM JRE and not the RHEL JRE. The IBM JRE issupplied with the Topology Editor or with TIP. To ensure you are using the rightJRE you can either:


– Set the JRE path to conform to that used by the Topology Editor, do thisusing 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. Seethe IBM Tivoli Netcool Performance Manager: Configuration RecommendationsGuide document for JRE download details.

Note: See the IBM Tivoli Netcool Performance Manager: ConfigurationRecommendations Guide document for the complete list of prerequisite software andtheir 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 Oracle Software

All Tivoli Netcool Performance ManagerComponents:

v Database

v DataView

v DataChannel

v DataLoad

v DataMart

v Solaris 10 64-bit

v AIX 6.1 64-bit

v RHEL 5.5, 64-bit

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.

Note: See the IBM Tivoli Netcool Performance Manager: ConfigurationRecommendations Guide document for the list of supported 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).

Chapter 2. Installing and configuring the prerequisite software 15

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

Communication > Ethernet Adapter > Change/Show Characteristics of anEthernet Adapter.

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

100_Full_Duplex.6. 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 will be referred to as "pvuser".

Decide in advance where to place the home directory of the pvuser login username.Use a standard home directory mounted on /home or /export/home, as available.

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 server.


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 20.

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 14.)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 document 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


Attribute Value

home directory /home/export/pvuser

login shell Korn shell (/bin/ksh)

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 have created 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 should be added toeach Tivoli Netcool Performance Manager computer's local setup files, or to thenetwork login name database.

Setting the resource limits (AIX only)On 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.

Set the system parameters (Solaris only)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 system file, then open the system file with a texteditor.

d. Set the parameter NOEXEC_USER_STACK to 1, by adding the followingline at the 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. See

Oracle® Database Installation Guide 10g Release 2 (10.2) for SolarisOperating System (SPARC 64-Bit) Part Number B15690-02


(http://download.oracle.com/docs/cd/B19306_01/install.102/b15690/pre_install.htm#sthref259), section 2.6: Configuring Kernel Parameters. Seealso Oracle Metalink ID 169706.1, Oracle Database on Unix AIX, HP-UX,Linux, Mac OS X, Solaris, Tru64 Unix Operating Systems Installation andConfiguration Requirements Quick Reference (8.0.5 to 11.2), which listsSolaris 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

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 100project: 100: group.dbaNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-memory

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

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

Enable FTP on Linux systems (Linux only)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. Change to the following directory:

# /etc/init.d

3. Run the following command:# ./vsftpd start

Disable SELinux (Linux only)Tivoli Netcool Performance Manager will not install 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. Open the SELinux config file for editing:

$ cat /etc/selinux/config

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

To:SELINUX=disabled

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


Set the kernel parameters (Linux only)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 = 512 x processes (for example 65536 for 128 processes)v net.ipv4.ip_local_port_range =9000 65500v net.core.rmem_default = 262144v net.core.rmem_max = 2097152v 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

Install a libcrypto.soFor full SNMPv3 support, SNMP DataLoad must have access to the libcrypto.so.

About this task

Note: As libcrypto.so is delivered as standard on Linux platforms, steps 1 and 2are not required if you are running on Linux.

For each new and existing SNMP DataLoad, you must perform the following steps.

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 using the following code:

# cd /usr/lib# ar -xv ./libcrypto.a# ln -s libcrypto.so.0.9.8 libcrypto.so

3. Update the dataload.env file so that the LD_LIBRARY_PATH (on Solaris & Linux)or LIBPATH (on AIX) environment variables include the path:/ProvisoAutomation/proviso/thirdparty/openssl.org/openssl-0.9.8o/{YourOS}/lib


http://www.openssl.org/

What to do next

Check the variable has been set by doing the following:1. Open a fresh shell2. Check the dataload.env file.3. Bounce the SNMP DL

Upon startup, with a valid library, the collector will log the following logmessages: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, please consult the IBM Tivoli Netcool Performance Manager:Configuration Recommendations Guide.

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 will require sufficient space to store that component. The defaultinstall directory is /opt. You do not have to use the default. This can be set toany directory 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, please consult the IBM TivoliNetcool Performance Manager: Configuration Recommendations Guide documentation.


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 18.

Downloading the Tivoli Netcool Performance Manager distribution todisk

To download the Tivoli Netcool Performance Manager distribution to a directoryon a target server's hard disk:

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 will be madeusing the token <DIST_DIR>.You will run a variety of scripts and programs from directories residing in thedirectory created on the hard drive, including:v Oracle 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.

4. If the current host is the primary deployer do the following:a. Change to the following directory:

On Solaris systems:$ cd <DIST_DIR>/proviso/SOLARIS/DataChannel/SOL10/sparc

On AIX systems:$ cd <DIST_DIR>/proviso/AIX/DataChannel/AIX/powerpc

On Linux systems:$ cd <DIST_DIR>/proviso/RHEL/DataChannel/RHEL5/i686/

b. Untar the dc.tar file. For example:tar -xvf dc.tar


Downloading Tivoli Common Reporting to diskTo download the TCR distribution to a directory on a target server's hard disk.

About this task

The TCR driver must be untarred so it can be used by the Tivoli NetcoolPerformance Manager Common Installer. The following process ensures the user isrequired to specify the TCR media location only once:

Procedure1. Create a folder named TCR as a peer to the other Tivoli Netcool Performance

Manager Components, that is, DataView, DataChannel, etc. For example:<DIST_DIR>/proviso/SOLARIS/TCR

2. Extract the TCR 2.1 inside this folder.Should the user decide not to extract the tar as a peer to the other components,a TCR folder must still be created having a path to the TCR install.sh the sameas: ./TCR/TCRInstaller/install.sh

Note: If the user extracts the tar directly into the same root location as theTivoli Netcool Performance Manager Components then the TCR launchpad.shwill overwrite the Tivoli Netcool Performance Manager Installer launchpad.sh,meaning the launchpad cannot be started for the installer.

General Oracle setup tasksHow to install Oracle for use with Tivoli Netcool Performance Manager.

To install Oracle you will need:v An appropriately sized server with the operating system installed and running

(for the Oracle server).

Note: For a basic overview of the minimum CPU speed, memory size, and diskconfiguration requirements for your Tivoli Netcool Performance Managerinstallation, see the IBM Tivoli Netcool Performance Manager: ConfigurationRecommendations Guide. For more detailed information you can contact IBMProfessional Services.

v The current version of Tivoli Netcool Performance Manager software.v The downloaded files for the Oracle installation.v Oracle server patch files.v Oracle client patch files.v If you are installing Oracle on an AIX system, follow the instructions in

Asynchronous I/O Support (AIX Only) before installing Oracle.

Before installing Oracle, 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 adatabase as the installation program will likely interfere. The co-hosting of TNPMwill also affect performance in unknown ways. If a co-host is required then theCustomer should seek out Professional Services for support.


Specifying a basename for DB_USER_ROOTTivoli Netcool Performance Manager components use distinct Oracle login namesso that database access can be controlled separately by component, and fordatabase troubleshooting 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 strongly encourages you to retainthe default value.

Results

Oracle login names are generated from the DB_USER_ROOT basename byappending a function or subsystem identifier to the basename, as in the followingexamples: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 Oracle 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 Oracle login passwordsFor each component that requires an Oracle login name, you must provide apassword for that login name.

About this task

In every case, the installer uses the default Oracle password, PV.

Oracle passwords are not case-sensitive, so PV and pv are the same password. Thedefault password is usually shown in uppercase, but is sometimes shown inlowercase. In both cases, the same default password is intended.


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 Oracle login names. If you use different passwords for each login name,keep a record of the passwords you assign to each login name.

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,the basename on whichOracle login names aregenerated

In all instances, use thedefault value PV, unlessyour site has an explicitnaming standard or anexplicit password policy.

PV or pv Default password for allOracle login names

PV Default Oracle databasename, also called the OracleTNS name

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, if you set your Oracle 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 chapter assume the following default values:

Setting Value Assumed in this Chapter

Hostname of the Oracle server delphi

Oracle server program files installed in /opt/oracle

ORACLE_BASE = /opt/oracle

Operating system login name for Oracle user oracle Note: The default name created isoracle. However, you can set another namefor the Oracle user.

Password for Oracle user oracle

ORACLE_SID = PV

TNS name for Tivoli Netcool PerformanceManager database instance

PV


Setting Value Assumed in this Chapter

Oracle installed in (ORACLE_HOME =) /opt/oracle/product/n

Note: The value of ORACLE_HOME cannotcontain soft links to other directories orfilesystems. Be sure to specify the entireabsolute path to Oracle. Tivoli NetcoolPerformance Manager expects an OptimalFlexible Architecture (OFA) structure whereORACLE_HOME is a sub-directory toORACLE_BASE.

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 /raid_2/oradata

Path for Oracle data, mount point 2 /raid_3/oradata

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 page28 for more information.

Installing the Oracle serverThis section describes the steps required to install the Oracle server and verify theinstallation.

The instructions in this section contain information on installing the Oracle 10server software with the version 10.2.0.4 patch.

Note: The Tivoli Netcool Performance Manager documentation describes how toconfigure Oracle using the init.ora file. It is possible to configure Oracle using aSPFILE; however, the documentation does not cover how this is achieved.

Ensure that the Oracle User is not in NISThe oracle user must be created locally, and must not be part of NetworkInformation Services (NIS).

About this task

The configure_ora script does not support oracle users who are part of NIS.

If the oracle account is already in NIS, do the following:

Procedure1. On the system where the Oracle database is to be installed, disable NIS. For

more information, see your operating system documentation.


2. Run the configure_ora script to create a local oracle account (see “Run theOracle server configuration script” on page 33).

3. Re-enable NIS.

Note: The local Oracle account should be used before the NIS Oracle user.

Download the Oracle distribution and patch to diskThe process of downloading the Oracle distribution

About this task

To download the Oracle installation files to your target server's hard disk:

Procedure1. Log in as root.2. Create a directory to hold the contents of the Oracle distribution. For example:

# mkdir /var/tmp/oracle10201# mkdir /var/tmp/oracle10204

3. Download the Oracle files to the /var/tmp/oracle10201 directory.4. Locate the appropriate upgrade patch file for your version of Oracle on the

Oracle Web site and download it to your /var/tmp/oracle10204 directory.5. Unzip the oracle distribution files that now reside in the /var/tmp/oracle10201

and /var/tmp/oracle10204 directories.Before you proceed to the next step, make sure that you obtain the upgradeinstructions provided by Oracle for the patch. The instructions containinformation on performing steps required for the upgrade that are notdocumented in this guide. If you are installing the Oracle patch on an AIXsystem, you might need to run the sbinclean command and execute thecatpatch.sql and utlrp.sql SQL scripts as part of the upgrade procedure.Additional requirements might exist for other platforms.See your database administrator to determine whether there are anycompany-specific requirements for installing Oracle in your environment.

If you have downloaded Oracle using OTNIf you have downloaded the Oracle installation files using OTN there are a numberof steps you must perform.

About this task

If you have downloaded the Oracle installation files using OTN, you must do thefollowing:

Procedure1. Log in as root.2. Create a directory to contain your Oracle 10.2.0.1.0 files. For example:

# mkdir /var/tmp/oracle10201

3. Download your gzipped 'cpio' Oracle files to this directory.4. Oracle Server folder setup:

a. Within the oracle 10.2.0.1.0 distribution directory you have created, create asubdirectory called 'database'.

b. Gunzip the '10gr2_db_sol.cpio.gz' file that was downloaded from Oracle.c. Cpio extract '10gr2_db_sol.cpio' into the 'database' subdirectory


cd databasecpio -idmv < 10gr2_db_sol.cpio

5. Oracle Client folder setup:a. Within the oracle 10.2.0.1.0 distribution directory you have created, create a

subdirectory called 'client'.b. Gunzip the '10gr2_client_sol.cpio.gz ' file that was downloaded from Oracle.c. Cpio extract '10gr2_client_sol.cpio' into the 'client' subdirectory:

cd clientcpio -idmv < 10gr2_client_sol.cpio)

Verify the required operating system packagesThe set of required Oracle packages vary by platform.

About this task

Before installing the Oracle server, do the following:

Procedure

Make sure all the required Solaris packages and patches are installed on yoursystem. All required packages and patches are specified in the IBM Tivoli NetcoolPerformance Manager: Configuration Recommendations Guide.

Verify the required operating system packagesThe set of required Oracle packages vary by platform.

About this task

Before installing the Oracle server, do the following:

Procedure

Make sure all the required Solaris packages and patches are installed on yoursystem. All required packages and patches are specified in the IBM Tivoli NetcoolPerformance Manager: Configuration Recommendations Guide.

On AIX systemsVerify that your AIX system has all prerequisite packages and patches.

Before you install Oracle on AIX systems, verify that your system meets therequired release level, as specified in the IBM Tivoli Netcool Performance Manager:Configuration Recommendations Guide document.

Before installing the Oracle server, make sure all the required AIX packages andpatches are installed on your system. All required packages and patches arespecified in the IBM Tivoli Netcool Performance Manager: ConfigurationRecommendations Guide document.

On Linux systemsVerify that your Linux system has all prerequisite packages and patches.

Before you install Oracle on Linux systems, verify that your system meets therequired release level, and make sure all required Linux packages and patches areinstalled on your system. Release level and all required packages and patches arespecified in the IBM Tivoli Netcool Performance Manager: Configuration


Recommendations Guide.

Run the Oracle server configuration scriptIn this step, you set up the Oracle environment using the configure_ora scriptprovided with the Tivoli Netcool Performance Manager DataMart files on theTivoli Netcool Performance Manager distribution.

About this task

This script automatically creates the following configuration:v Adds the dba and oinstall groups to /etc/group

v Adds the login name oracle, the primary group membership of which is dba andsecondary group membership is oinstall, plus:– The default login name created is oracle; however, you can set this to be any

name of your choosing.– ORACLE_BASE is set as the user home directory. If you would prefer to use a

different home directory for the oracle user, create the oracle user manuallybefore running configure_ora.Note: If .profile already exists and ORACLE_HOME has already been set,then the configure_ora script will not update it. If you are changing the valueof ORACLE_BASE or ORACLE_HOME, you must edit .profile manually tomake these changes. Note: It is possible for you to create the oracle usermanually, before running the configure_ora script, but this is notrecommended. Oracle requires that certain attributes are set for the oracleuser, if these attributes are not in place, errors may occur.

v Creates the Oracle directory structure.v Creates startup and shutdown scripts for Oracle server processes.

To configure the Oracle installation environment using the configure_ora script:

Procedure1. Log in as root.2. Set the ORACLE_BASE environment variable to point to the top-level

directory where you want the Oracle server files installed. The defaultinstallation directory is /opt/oracle. This can be set to any directory requiredby your organization.For example:

# ORACLE_BASE=/opt/oracle # export ORACLE_BASE

Note: The configure_ora script places this variable into the oracle loginaccount's .profile file.To check that the variable is set correctly, enter the following command:# env | grep ORA

3. Change to the following directory:Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance

AIX systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX/instance

Linux systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL5/instance

where:


<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 26.

4. Run the Oracle configuration script by entering the following command:# ./configure_ora

The following screen is displayed:

--------------------------------------------------configure_ora

Setting the Oracle environment<Current Date>

--------------------------------------------------OS ........... : [ SunOS 5.10 Generic ]Host ......... : [ delphi ]Logname ...... : [ root ]

ORACLE_BASE .. : [ /opt/oracle ]

DBA group ................. : [ dba ]OUI Inventory group ....... : [ oinstall ]Oracle Software owner ..... : [ oracle ]

Configure Oracle release .. : [ 10.2.0 ]

Menu :1. Modify Oracle software owner.2. Next supported release3. Check environment.0. Exit

Choice:

5. (Optional) To create a different name for the Oracle user other than the defaultoracle, type 1 and follow the instructions.

Note: The Oracle user will be referred to as "oracle" for the remainder of thisdocument. If you have set the username to be a non-default string, that is,something other than "oracle" , make sure to substitute your non- defaultstring for each occurrence of "oracle" within any task description.

6. Type 3 at the Choice prompt and press Enter.The script creates the dba and oinstall groups and the ORACLE_BASEdirectory, 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

7. 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

8. 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/10.2.0 ] --> Created.[ /opt/oracle/product/10.2.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...

9. Press the Enter key to continue. The configure_ora main screen is refreshed.10. Type 0 and press Enter to exit the configure_ora script.

Note: You must set a password for the oracle login name (see “Set apassword for the Oracle login name” on page 36).

Structure created by the configure_ora scriptThe configure_ora script creates the Oracle directory structure.

The following example shows the directory structure created for Oracle, whereORACLE_BASE was set to /opt/oracle:/opt/oracle/product/opt/oracle/product/10.2.0/opt/oracle/product/10.2.0/dbs/opt/oracle/admin/opt/oracle/admin/skeleton/opt/oracle/admin/skeleton/bin/opt/oracle/local

The script creates the following setup files:

Solaris specific files:

v /etc/init.d/dbora, which starts the Oracle Listener and database serverautomatically on each system boot

v Symbolic links to /etc/init.d/dbora in /etc/rc0.d, /etc/rc1.d, and /etc/rc2.d

v Oracle configuration files /var/opt/oracle/oratab and lsnrtab.

AIX specific files:

v /etc/inittab is modified to contain the dbstart and lsnrctl startup 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 containing the following lines:

# -- Begin Oracle Settings --umask 022ORACLE_BASE=/opt/oracleORACLE_HOME=$ORACLE_BASE/product/10.2.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 the following:v The value of ORACLE_HOME cannot contain soft links to other directories or

filesystems. Be sure to specify the entire absolute path to Oracle.v You will add the ORACLE_SID variable to this file later, in “Set the

ORACLE_SID variable” on page 45.

Set a password for the Oracle login nameYou must assign a password for the oracle login name to maintain system security.

About this task

The configure_ora script you ran in the previous section creates the oracle loginname. You must assign a password for the oracle login name to maintain systemsecurity, and because subsequent installation steps expect the password to bealready set.

To set a password:

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

# passwd oracle

3. Enter and re-enter the password (oracle, by default) as prompted. The passwordis set.

Run the pre-installation scriptThe steps required to run the pre-installation script.

About this task

Note: If you are installing on a Solaris system, it is required that you have alreadycompleted the tasks as described in “Set the system parameters (Solaris only)” onpage 21 before continuing your Oracle server installation on Solaris.

Run the pre-installation script that verifies readiness to install Oracle:

Procedure1. Log in as root.2. Change to the following directory:


Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance/ora_installer

AIX systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX/instance/ora_installer

Linux systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL5/instance/ora_installer

where:v <DIST_DIR> is the directory on the hard drive where you copied the contents

of the Tivoli Netcool Performance Manager distribution in “Downloading theTivoli Netcool Performance Manager distribution to disk” on page 26.

3. Set the ORACLE_BASE environment variable. For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE

You must use the same ORACLE_BASE setting that you specified in “Run theOracle server configuration script” on page 33

4. 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.

Run the rootpre.sh script (AIX only)To run the rootpre.sh script.

Procedure1. Log in as root or become superuser.2. Set the DISPLAY environment variable.3. Change to the directory /var/tmp/oracle10201/database/rootpre.

Note: The Oracle server distribution is downloaded to /var/tmp/oracle10201as per the instructions in the section “Downloading the Tivoli NetcoolPerformance Manager distribution to disk” on page 26.

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.


Verify PATH and environment for the Oracle login nameThe steps required to verify PATH and Environment for the Oracle Login Name.

About this task

Before proceeding to install Oracle server files, make sure the /usr/ccs/bindirectory is in the PATH environment variable for the oracle login name.

To verify the PATH and environment:

Procedure1. Log in as oracle.2. 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 name's login environment is loaded:# su - oracle

3. 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 Oracleserver configuration script” on page 33.

4. To verify the path, enter the following command:$ echo $PATH

The output should show that /usr/ccs/bin is part of the search path. Forexample:

/usr/bin:/opt/oracle/product/10.2.0/bin:/usr/ccs/bin

a. If the directory does not appear in the path, add it by entering thefollowing commands:

$ PATH=$PATH:/usr/ccs/bin $ export PATH

Install OracleThere are two ways to install the Oracle database files.v “Using the menu-based script”: The Oracle installation script provided by IBM is

used to install Oracle server, Oracle client, and to install upgrade patches. Youshould follow this step if you are not familiar with the Oracle installationprocess.

v “Using batch mode” on page 40: If you understand and are very familiar withthe Oracle installation process, use batch mode.

Note: Choose one method, either the menu based script or the batch mode, do notimplement both.

Using the menu-based scriptThe steps required to install the Oracle server using the menu-based script.

About this task

To install the Oracle server using the menu-based script:


Procedure1. Log in as oracle.2. Change to the following directory:





of the Tivoli Netcool Performance Manager distribution in “Downloadingthe Tivoli Netcool Performance Manager distribution to disk” on page 26.

3. Enter the following command to start the installer:$ ./perform_oracle_inst

The installation menu is displayed:

--------------------------------------------------perform_oracle_inst

Installation of oracle binaries<Current Date>

--------------------------------------------------OS ........... : [ SunOS 5.10 Generic ]Host ......... : [ delphi ]Logname ...... : [ oracle ]

Install Oracle release .... : [ 10.2.0 ]Installation type.......... : [ Server ]

Enter the appropriate letter to modify the entries below:

a) ORACLE_BASE .. : [ /opt/oracle ]b) ORACLE_HOME .. : [ /opt/oracle/product/10.2.0 ]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 :

4. Verify the following settings:v The Oracle release number should be 10.2.0.v The Installation type field should be set to Server.

This field cycles between three settings: Server, Client, and Patch. Type 2 atthe Choice prompt and press Enter until Server is displayed.

5. Type f at the Choice prompt and press Enter.6. At the Choice prompt, enter the full path to the directory containing the

installation files. For example:

Choice: fEnter new value for CD directory: /var/tmp/oracle10201

7. Edit other menu settings as required.


For example, if you used non-default values for ORACLE_BASE orORACLE_HOME, enter your settings until the menu shows the correctinformation.

8. To begin the Oracle installation, type 3 at the Choice prompt and press Enter.The installation script checks the environment, then asks whether you want toperform the installation.

9. 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, or any Linux operating system prerequisite failure, as this relates to aproblem with the Oracle Universal Installer. For more information on thisproblem with the Oracle Universal Installer, see the Oracle technote"Prerequisite Checks Fail When Installing 10.2 On Red Hat 5 (RHEL5) [ID456634.1]".When the installation reaches the In Summary Page stage, the installationslows down significantly while Oracle files are copied and linked.

10. When the installation is complete, messages similar to the following aredisplayed:

In End of Installation PageThe installation of Oracle10 Database was successful.Please check /opt/oracle/oraInventory/logs/silentInstall2004-09-28_04-23-53PM.logfor more details.

The Oracle installation has completed. Please 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: Write down the log file location to aid in troubleshooting if there is aninstallation error.

11. Type C and press Enter to return to the installation menu.12. Type 0 and press Enter to exit the installation menu.

Using batch modeBatch mode is the only Oracle installation method that lets you change the settingsfor the Oracle primary and secondary group names, and the name of the oracleuser login, if you have not used the default settings.

About this task

Note: The IBM-provided Oracle installation script is used to install Oracle server,Oracle client, and to install upgrade patches to an existing Oracle server or clientinstallation. You should follow this step if you are familiar with the Oracleinstallation process because it is more efficient to install Oracle using batch mode.If you do not understand the Oracle installation process, use the menu-based script(see “Install Oracle” on page 38). If you installed the Oracle server, Oracle client, orupgrade patches to the Oracle server or Oracle client using the menu-based script,skip this step.

To install Oracle using batch mode:







of the Tivoli Netcool Performance Manager distribution in “Downloading theTivoli Netcool Performance Manager distribution to disk” on page 26.

3. Open the perform_oracle_inst.ini file with a text editor. This file contains anumber of Oracle installation settings similar to the following:

# You can install either a server install,# a client install or a patchset. To# install in batch mode you must enter a# value. Uncomment the appropriate value.##ORA_TYPE=Server#ORA_TYPE=Client#ORA_TYPE=Patch## What is the directory where you copied the# Oracle install CD’s.#INSTALL_DIRECTORY=## Script will automatically use the# ORACLE_BASE defined in you environment# or you can define it below.##ORACLE_BASE=## Script will automatically use the# ORACLE_HOME defined in you environment# or you can define it below.##ORACLE_HOME=## What unix account is the oracle software# owner? A typical default is supplied.#ORA_USR_OWN=oracle## What is the oracle dba unix group name?# A typical default is supplied.#ORA_GRP_DBA=dba## What is the oracle oui unix group name?# A typical default is supplied.#ORA_GRP_OUI=oinstall

4. Make the necessary edits to the installation values. You can uncomment linesalready included in the file to use those values for the installation.For example, uncomment the following line to install Oracle server:ORA_TYPE=Server


5. Save your edits and close the file.6. Run the installation script with the b flag:

$ ./perform_oracle_inst b

The installation program verifies the values and performs the installation asshown in the section for the menu-based installation (see “Install Oracle” onpage 38).

Run the root.sh scriptAfter successfully running an Oracle server installation, you must run the root.shscript.

About this task

To run the root.sh script:

Procedure1. Log in as root or become superuser.2. Change to the directory where Oracle files were installed. (This is the value of

the ORACLE_HOME environment variable as seen by the oracle login name.)For example:

# cd /opt/oracle/product/10.2.0

3. Run the following command:./root.sh

Messages similar to the following are displayed:

Running Oracle10 root.sh script...The following environment variables are set as:

ORACLE_OWNER= oracleORACLE_HOME= /opt/oracle/product/10.2.0

Enter the full pathname of the local bin directory: [/usr/local/bin]:

4. If the default entry, /usr/local/bin, is writable by root, press Enter to acceptthe default value.The default entry might be NFS-mounted at your site so it can be sharedamong several workstations and therefore might be write-protected. If so, enterthe location of a machine-specific alternate bin directory. (You might need tocreate this alternate directory at a shell prompt first.) For example, enter/usr/delphi/bin.

5. The script continues as follows:

...Adding entry to /var/opt/oracle/oratab file...Entries will be added to the /var/opt/oracle/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root.sh script.Now product-specific root actions will be performed.#

6. The script runs to completion with no further prompts.


Install Oracle patchesAfter you install Oracle, you must install the patchset for your version of Oracle tobring the Oracle version up to the IBM-validated patch level.

About this task

The basic patch required for Oracle 10g is patch version 10.2.0.4

See the IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guidefor up-to-date information about the required patches.

In the interests of keeping this manual as short as possible, instructions providedby Oracle on how to perform an installation are not replicated within this manual.It is, however, recommended that before you complete this step that you obtainand read the upgrade instructions provided by Oracle for the patch that you wishto install. Your specific system may require supplementary steps not covered inthis document, but which the Oracle instructions cover in detail.

For example, if you are installing the Oracle patch on an AIX system, it is possibleyou may need to run the sbinclean command and execute the catpatch.sql andutlrp.sql SQL scripts as part of the upgrade procedure. Additional requirementsmight exist for other platforms.

Note: Do not skip this step. Upgrade the Oracle version before you install theTivoli Netcool Performance Manager database structure.

To install the Oracle patchset:








4. Verify the following settings:v The Oracle release number should be 10.2.0.v The Installation type field should be set to Patch.

This field cycles between three settings: Server, Client, and Patch. Type 2 atthe Choice prompt and press Enter until Patch is displayed.

5. To specify the path, type f at the Choice prompt and press Enter.


6. At the Choice prompt, enter the full path to the patch directory you created tohold the contents of the patch release (see “Download the Oracle distributionand patch to disk” on page 31). For example:


7. To begin the upgrade installation, type 3 at the Choice prompt and pressEnter. The installation script checks the environment, then asks whether youwant to perform the installation.

8. Type y at the Choice prompt and press Enter. The script proceeds to installthe patch release files, showing a long series of messages much like the onesshown during installation of the base release.

Note: You can safely ignore any "font.properties not found" messages in theoutput.In the messages, look for "success" notifications. If the script showsunsuccessful installation messages, check the installation log file specified inthe message. Correct the error conditions identified in the log file, then rerunthe patch installation and double-check all menu settings.

9. When the installation is complete, type C and press Enter.

Note: The message telling you to press C might have already scrolled past,because messages from several installation threads are written to the samescreen.

10. Exit from the menu.

Note: If you try to start Oracle as the database administrator (DBA) at thispoint, the startup will fail because the file initPV.ora does not yet exist. Thisfile is created during the Tivoli Netcool Performance Manager installation.

11. Carry out the steps as described in “Run the root.sh script” on page 42.This step is also required after an Oracle patch installation.

Relax permissions on ORACLE_HOMEWhen the install has finished, you must change permissions on the directoriesunder ORACLE_HOME.

About this task

During the installation, Oracle sets very restrictive permissions onORACLE_HOME. Oracle provides a script that can be run after the install to relaxpermissions. To run the script:


$ cd ORACLE_HOME/install.

3. Enter the following command to start the script:$ ./changePerm.sh


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=$ORACLE_BASE/product/10.2.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

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:


Solaris systems:$ cd /var/opt/oracle

AIX systems:$ cd /etc

Linux Systems:$ cd /etc

3. Edit the oratab file with a text editor. The last line of this file looks like thisexample:

*:/opt/oracle/product/10.2.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 should now be:

PV:/opt/oracle/product/10.2.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:v

Procedure1. Log in as oracle.2. Change to one of the following directories:

$ cd $TNS_ADMIN

or$ cd /opt/oracle/product/10.2.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/10.2.0/network/adminLISTENER=

(DESCRIPTION_LIST =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP) (HOST = yourhost) (PORT = 1521))

)


(ADDRESS_LIST =(ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC))

))

)SID_LIST_LISTENER =

(SID_LIST =(SID_DESC =

(SID_NAME = PLSExtProc)(ORACLE_HOME = /opt/oracle/product/10.2.0)(PROGRAM = extproc)

)(SID_DESC =

(GLOBAL_DBNAME = PV.WORLD)(SID_NAME = PV)(ORACLE_HOME = /opt/oracle/product/10.2.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. (optional) Replace the default port number 1521 in the line (PORT = 1521)

with your required port number.c. Write and quit the file.

5. Depending on your operating system, change to the following directory:Solaris systems:$ cd /var/opt/oracle

AIX systems:$ cd /etc

Linux 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/10.2.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/10.2.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=WORLD

For example:# sqlnet.ora network configuration file in# /opt/oracle/product/10.2.0/network/adminNAMES.DIRECTORY_PATH=(TNSNAMES)NAMES.DEFAULT_DOMAIN=WORLD

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 file.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/10.2.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 will 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 includingEXTPROC_CONNECTION_DATA that you specified for theNAMES.DEFAULT_DOMAIN entry in the sqlnet.ora file. 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.


Shut down of performance impacting Oracle jobsThere are a few Oracle jobs that impact on performance, these are automaticallyshut down by the installation code.

About this task

It should be noted that the following Oracle jobs are automatically disabled by theinstallation code in order to maintain an acceptable level of performance:v GATHER_STATS_JOB: statistics gathering job.v AUTO_SPACE_ADVISOR_JOB: auto space advisor maintenance jobv MGMT_CONFIG_JOB: Configuration collection job.v MGMT_STATS_CONFIG_JOB: OCM Statistics collection job.

It is recommended that these jobs should remain shut down.

Procedure

Should you discern any impact to performance, please confirm that these jobs arenot in operation.

Installing the Oracle clientYou must install Oracle client software on each system where you plan to install aTivoli Netcool Performance Manager component, with the exception of the systemwhere you installed the Oracle server.

The instructions in this section contain information on installing the Oracle clientsoftware with the version 10.2.0.4 patch.

Ensure that the Oracle User is not in NISThe oracle user must be created locally, and must not be part of NetworkInformation Services (NIS).

About this task

The configure_ora script does not support oracle users who are part of NIS.

If the oracle account is already in NIS, do the following:

Procedure1. On the system where the Oracle database is to be installed, disable NIS. For

more information, see your operating system documentation.2. Run the configure_ora script to create a local oracle account (see “Run the

Oracle server configuration script” on page 33).3. Re-enable NIS.

Note: The local Oracle account should be used before the NIS Oracle user.


Download the Oracle distribution and patch to diskThe process of downloading the Oracle distribution

About this task

To download the Oracle installation files to your target server's hard disk:

Procedure1. Log in as root.2. Create a directory to hold the contents of the Oracle distribution. For example:

# mkdir /var/tmp/oracle10201# mkdir /var/tmp/oracle10204

3. Download the Oracle files to the /var/tmp/oracle10201 directory.4. Locate the appropriate upgrade patch file for your version of Oracle on the

Oracle Web site and download it to your /var/tmp/oracle10204 directory.5. Unzip the oracle distribution files that now reside in the /var/tmp/oracle10201

and /var/tmp/oracle10204 directories.Before you proceed to the next step, make sure that you obtain the upgradeinstructions provided by Oracle for the patch. The instructions containinformation on performing steps required for the upgrade that are notdocumented in this guide. If you are installing the Oracle patch on an AIXsystem, you might need to run the sbinclean command and execute thecatpatch.sql and utlrp.sql SQL scripts as part of the upgrade procedure.Additional requirements might exist for other platforms.See your database administrator to determine whether there are anycompany-specific requirements for installing Oracle in your environment.

If you have downloaded Oracle using OTNIf you have downloaded the Oracle installation files using OTN there are a numberof steps you must perform.

About this task

If you have downloaded the Oracle installation files using OTN, you must do thefollowing:

Procedure1. Log in as root.2. Create a directory to contain your Oracle 10.2.0.1.0 files. For example:

# mkdir /var/tmp/oracle10201

3. Download your gzipped 'cpio' Oracle files to this directory.4. Oracle Server folder setup:

a. Within the oracle 10.2.0.1.0 distribution directory you have created, create asubdirectory called 'database'.

b. Gunzip the '10gr2_db_sol.cpio.gz' file that was downloaded from Oracle.c. Cpio extract '10gr2_db_sol.cpio' into the 'database' subdirectory

cd databasecpio -idmv < 10gr2_db_sol.cpio

5. Oracle Client folder setup:a. Within the oracle 10.2.0.1.0 distribution directory you have created, create a

subdirectory called 'client'.


b. Gunzip the '10gr2_client_sol.cpio.gz ' file that was downloaded from Oracle.c. Cpio extract '10gr2_client_sol.cpio' into the 'client' subdirectory:

cd clientcpio -idmv < 10gr2_client_sol.cpio)

Run the Oracle client configuration scriptThe Oracle client configuration script is a shell script that creates the environmentfor the client software installation on the local system.

About this task

This script is named configure_client and is located with the Tivoli NetcoolPerformance Manager files that you obtained in “Downloading the Tivoli NetcoolPerformance Manager distribution to disk” on page 26. If you are performing thisstep as part of an upgrade procedure, make sure that you run the configurationscript provided with the target 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.v Creates the Oracle client directory structure. When you create the environment

for patch version 10.2.0.4, the default location for this directory structure is$ORACLE_BASE/product/10.2.0. You specify this directory as the target locationwhen you install the Oracle client.

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. Change to the following directory:Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/instance

AIX systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX/instance

Linux systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL5/instance

where:


<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 26.

4. Run the Oracle configuration script using the following command:# ./configure_client

The following screen is displayed:

--------------------------------------------------configure_client

Setting the Oracle client environment<Current Date>

--------------------------------------------------OS ........... : [ SunOS 5.10 Generic ]Host ......... : [ corinth ]Logname ...... : [ root ]

ORACLE_BASE .. : [ /opt/oracle ]

DBA group ................. : [ dba ]OUI Inventory group ....... : [ oinstall ]Oracle Software owner ..... : [ oracle ]

Configure Oracle release .. : [ 10.2.0 ]

Menu :1. Modify Oracle software owner.2. Next supported release.3. Check environment.4. Add 10.2.0.4 client support.0. Exit

Choice:

5. (Optional) To create a different name for the Oracle user other than the defaultoracle, type 1 and follow the instructions.

Note: The Oracle user will be referred to as "oracle" for the remainder of thisdocument. If you have set the username to be a non-default string, that is,something other than "oracle" , make sure to substitute your non- default stringfor each occurance of "oracle" within any task description.

6. Type 3 at the Choice prompt and press Enter.The script creates the dba and oinstall groups, and the ORACLE_BASEdirectory, 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/9.2.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.

Set a password for the Oracle login nameYou must assign a password for the oracle login name to maintain system security.

About this task

The configure_ora script you ran in the previous section creates the oracle loginname. You must assign a password for the oracle login name to maintain systemsecurity, and because subsequent installation steps expect the password to bealready set.

To set a password:

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

# passwd oracle

3. Enter and re-enter the password (oracle, by default) as prompted. The passwordis set.

Run the pre-installation scriptThe steps required to run the pre-installation script.

About this task

Note: If you are installing on a Solaris system, it is required that you have alreadycompleted the tasks as described in “Set the system parameters (Solaris only)” onpage 21 before continuing your Oracle server installation on Solaris.

Run the pre-installation script that verifies readiness to install Oracle:

Procedure1. Log in as root.2. Change to the following directory:




where:


v <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 26.

3. Set the ORACLE_BASE environment variable. For example:# ORACLE_BASE=/opt/oracle# export ORACLE_BASE

You must use the same ORACLE_BASE setting that you specified in “Run theOracle server configuration script” on page 33

4. 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.

Verify PATH and environment for the Oracle login nameThe steps required to verify PATH and Environment for the Oracle Login Name.

About this task

Before proceeding to install Oracle server files, make sure the /usr/ccs/bindirectory is in the PATH environment variable for the oracle login name.

To verify the PATH and environment:

Procedure1. Log in as oracle.2. 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 name's login environment is loaded:# su - oracle

3. 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 Oracleserver configuration script” on page 33.

4. To verify the path, enter the following command:$ echo $PATH

The output should show that /usr/ccs/bin is part of the search path. Forexample:

/usr/bin:/opt/oracle/product/10.2.0/bin:/usr/ccs/bin

a. If the directory does not appear in the path, add it by entering thefollowing commands:

$ PATH=$PATH:/usr/ccs/bin $ export PATH


Install the Oracle clientThe 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.

About this task

This script is named perform_oracle_inst and is located with the Tivoli NetcoolPerformance Manager files that you obtained in “Downloading the Tivoli NetcoolPerformance Manager distribution to disk” on page 26. This script is provided byIBM as part of the Tivoli Netcool Performance 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

You will configure these files in later steps.

To install the Oracle client:








The installation menu is displayed:


--------------------------------------------------perform_oracle_inst

Installation of oracle binaries<Current Date>

--------------------------------------------------OS ........... : [ SunOS 5.10 Generic ]Host ......... : [ delphi ]Logname ...... : [ oracle ]

Install Oracle release .... : [ 10.2.0 ]Installation type.......... : [ Client ]

Enter the appropriate letter to modify the entries below:

a) ORACLE_BASE .. : [ /opt/oracle ]b) ORACLE_HOME .. : [ /opt/oracle/product/10.2.0 ]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 :

4. Enter f at the Choice prompt and press Enter.5. Enter the full path to the directory you created to hold the Oracle distribution

in “Download the Oracle distribution and patch to disk” on page 31. Forexample:


6. Edit any other menu settings as necessary. Make sure that the values forORACLE_BASE and ORACLE_HOME correspond to the locations youspecified when you 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 found" messages in theoutput.When the installation reaches the In Summary Page stage, the installationslows down significantly while Oracle files are copied and linked.

9. When the installation process completes, the installation displays a successmessage. Write down the log file location to aid in troubleshooting if there isan installation error.

10. Type C and press Enter to return to the installation menu.11. Type 0 and press Enter to exit the installation menu.12. Perform the steps in “Run the root.sh script” on page 42.


Run the root.sh scriptAfter successfully running an Oracle server installation, you must run the root.shscript.

About this task

To run the root.sh script:

Procedure1. Log in as root or become superuser.2. Change to the directory where Oracle files were installed. (This is the value of

the ORACLE_HOME environment variable as seen by the oracle login name.)For example:

# cd /opt/oracle/product/10.2.0

3. Run the following command:./root.sh

Messages similar to the following are displayed:

Running Oracle10 root.sh script...The following environment variables are set as:

ORACLE_OWNER= oracleORACLE_HOME= /opt/oracle/product/10.2.0

Enter the full pathname of the local bin directory: [/usr/local/bin]:

4. If the default entry, /usr/local/bin, is writable by root, press Enter to acceptthe default value.The default entry might be NFS-mounted at your site so it can be sharedamong several workstations and therefore might be write-protected. If so, enterthe location of a machine-specific alternate bin directory. (You might need tocreate this alternate directory at a shell prompt first.) For example, enter/usr/delphi/bin.

5. The script continues as follows:

...Adding entry to /var/opt/oracle/oratab file...Entries will be added to the /var/opt/oracle/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root.sh script.Now product-specific root actions will be performed.#

6. The script runs to completion with no further prompts.

Install Oracle patchesAfter you install the Oracle client software, you must install patch version 10.2.0.4.

About this task

In the interests of keeping this manual as short as possible, instructions providedby Oracle on how to perform an installation are not replicated within this manual.

It is, however, recommended that before you complete this step that you obtainand read the upgrade instructions provided by Oracle for the patch that you wishto install.


Your specific system may require supplementary steps not covered in thisdocument, but which the Oracle instructions cover in detail. For example, if youare installing the Oracle patch on an AIX system, it is possible you may need torun the sbinclean command and execute the catpatch.sql and utlrp.sql SQL scriptsas part of the upgrade procedure. Additional requirements might exist for otherplatforms.

Note: Do not skip this step. Upgrade the Oracle version before you install theTivoli Netcool Performance Manager database structure.

To install the Oracle patchset:

Procedure1. Follow the instructions to run the perform_oracle_inst script, as shown in

“Install Oracle patches” on page 43. Go through the menus as described in thatsection, with the following changes:a. Enter 2 at the Choice prompt and press Enter until the Installation type

field is set to Patch.b. Type f at the Choice prompt and press Enter.c. At the Choice prompt, type the full path to the patch directory you created

in “Download the Oracle distribution and patch to disk” on page 31 to holdthe client patch 10.2.0.4 contents. For example:


2. Type 3 at the Choice prompt and press Enter. The script checks theenvironment and displays a series of messages.

3. Type y at the Choice prompt and press Enter to begin the patch installation.The script proceeds to install the patch release files, showing a series ofmessages much like the ones shown during installation of the base release.

Note: You can safely ignore any "font.properties not found" messages in theoutput.

4. Watch the script's messages for success entries.

Note: If the script shows unsuccessful installation messages, check theinstallation log file named in the message. Correct the error conditionsidentified in the log file, then rerun the patch installation and double-check allmenu settings.

5. At the Choice prompt, type C and press Enter to continue.The message telling you to press C may have already scrolled past, becausemessages from several installation threads are written to the same screen. If theinstallation has paused, type C to continue.Relax Permissions onORACLE_HOME


Relax permissions on ORACLE_HOMEWhen the install has finished, you must change permissions on the directoriesunder ORACLE_HOME.

About this task

During the installation, Oracle sets very restrictive permissions onORACLE_HOME. Oracle provides a script that can be run after the install to relaxpermissions. To run the script:


$ cd ORACLE_HOME/install.

3. Enter the following command to start the script:$ ./changePerm.sh

Configure 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 should 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 areidentical. 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.

Create 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:


$ cd $ORACLE_HOME/network/admin

3. To create the sqlnet.ora file, FTP the following file from your Oracle server:


/opt/oracle/admin/skeleton/bin/template.example_tnpm.sqlnet.ora

4. Add the following lines to it:NAMES.DIRECTORY_PATH=(TNSNAMES) NAMES.DEFAULT_DOMAIN=WORLD

For example:

# sqlnet.ora network configuration file in# /opt/oracle/product/10.2.0/network/adminNAMES.DIRECTORY_PATH=(TNSNAMES)NAMES.DEFAULT_DOMAIN=WORLD

Note: If you do not use WORLD as the DEFAULT_DOMAIN value, make sureyou enter the same value for DEFAULT_DOMAIN in both sqlnet.ora andtnsnames.ora.

5. Write and quit the sqlnet.ora file.

Create 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/10.2.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 will 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 databasein another Tivoli Netcool Performance Manager installation, be sure youupdate the HOST entry in the tnsnames.ora file, then restart the Oracleclient.

v Specify the host 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.

Test 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 10

3. Test again, using the same Net instance name without the domain suffix:tnsping PV 10

Look for successful completion messages (OK).

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 Chapter 4, “Installing as a minimal deployment,” on page 89 - Describes how to

install Tivoli Netcool Performance Manager in a distributed productionenvironment.

v Chapter 5, “Modifying the current deployment,” on page 95 - Describes how toinstall Tivoli Netcool Performance Manager as a minimal deployment, which isused primarily for demonstration or evaluation purposes.

v If you are planning on Installing Tivoli Netcool Performance Manager as adistributed environment that uses clustering for high availability, please reviewthe Tivoli Netcool Performance Manager HA (High Availability) documentation,which is available for download by going to http://www-01.ibm.com/software/brandcatalog/opal/ and searching for "Netcool Proviso HA Documentation".




Chapter 3. Installing in a distributed environment

This section describes how to install Tivoli Netcool Performance Manager for thefirst time in a fresh, distributed environment.

For information about installing the Tivoli Netcool Performance Managercomponents using a minimal deployment, see Chapter 4, “Installing as a minimaldeployment,” on page 89.

Distributed installation processThe mains 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.


Before installing Tivoli Netcool Performance Manager, you must have installed theprerequisite software. For detailed information, see Chapter 2, “Installing andconfiguring the prerequisite software,” on page 13.

In addition, you must have decided how you want to configure your system. Referto the following sections:v “Co-location rules” on page 2v “Typical installation topology” on page 8v Appendix A, “Remote installation issues,” on page 137

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 2, “Installing andconfiguring the prerequisite software,” on page 13 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 14).3. Set and export the BROWSER variable to point to your Web browser. For

example:On Solaris systems:# BROWSER=/opt/mozilla/mozilla# export BROWSER

On AIX systems:# BROWSER=/usr/mozilla/firefox/firefox# export BROWSER

On Linux systems:# BROWSER=/usr/bin/firefox# export BROWSER

Note: The BROWSER command cannot include any spaces around the equalsign.

4. Change directory to the directory where the launchpad resides.On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS

On AIX systems:# cd <DIST_DIR>/proviso/AIX

On Linux systems:# cd <DIST_DIR>/proviso/RHEL


5. Enter the following command to start the launchpad:# ./launchpad.sh

Chapter 3. Installing in a distributed environment 65

Installing the Topology EditorThe steps required to install the Topology Editor.

About this task

Only one instance of the Topology Editor can exist in the Tivoli Netcool PerformanceManager environment. Install the Topology Editor on the same system that will hostdatabase 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 oftasks.

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:On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/topologyEditor/Disk1/InstData/VM

On AIX systems:# cd <DIST_DIR>/proviso/AIX/Install/topologyEditor/Disk1/InstData/VM

On Linux systems:# cd <DIST_DIR>/proviso/RHEL/Install/topologyEditor/Disk1/InstData/VM

<DIST_DIR> is the directory on the hard drive where you copied the contentsof the Tivoli Netcool Performance Manager distribution in “Downloadingthe Tivoli Netcool Performance Manager distribution to disk” on page 26

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 the wizard is pointing to the correct directory. The default is

/opt/IBM/proviso. If you have previously installed the Topology Editor on thissystem, the installer does not prompt you for an installation directory andinstead uses the directory where you last installed the application.

5. Click Next to continue.6. Confirm the wizard is pointing to the correct base installation directory of the

Oracle JDBC driver (/opt/oracle/product/version/jdbc/lib), or click Choose tonavigate to another directory.

7. Click Next to continue.8. Review the installation information, then click Run.9. 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

The combination of the Topology Editor and the deployer is referred to as theprimary deployer. For more information, see “Resuming a partially successfulfirst-time installation” on page 87.

Note: To uninstall the Topology Editor, follow the instructions in “Uninstallingthe topology editor” on page 133. Do not delete the /opt/IBM directory. Doingso will cause problems when you try to reinstall the Topology Editor.

If the /opt/IBM directory is accidentally deleted, perform the following steps:a. Change to the /var directory.b. Rename the hidden file .com.zerog.registry.xml (for example, rename it to

.com.zerog.registry.xml.backup).c. Reinstall the Topology Editor.d. Rename the backup file to the original name (.com.zerog.registry.xml).

Starting the Topology EditorAfter you have installed the Topology Editor, you can invoke it from either thelaunchpad or from 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.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 Editorwill fail with a Java assertion message (core dump).


Creating a new topologyThe steps 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.The default value is 10000. The size of your deployment affects the databasesizing.

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 andTivoli Integrated Portals.

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.

Add the hostsThe first step is to specify all the servers that will 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 user 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). This allows you to install and run different components on the samesystem as different users.

Note: DataChannel components always use the default user associated with thehost.

The user account used to transfer files using FTP or SCP/SFTP during installationis always the PV User defined at the host level, rather than component 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 machine.

The fields are as follows:


v Host name - Enter the name of the host (for example, delphi).v Operating system - Specifies the operating system (for example, SOLARIS).

This field is filled in for you.v Oracle home - Specifies the default ORACLE_HOME directory for all Tivoli

Netcool Performance Manager components installed on the system (bydefault, /opt/oracle/product/10.2.0).

v PV User - Specifies the default Tivoli Netcool Performance Manager Unixuser (for example, pvuser) for all Tivoli Netcool Performance Managercomponents 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 have not chosen 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 have chosen to create a Disk Usage Server, click Next and the AddHost window will allow you to 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. This property

allows you to differentiate between a local directory and a remote directorymounted to allow for FTP access.

v Remote Root Directory - Remote directory mounted for FTP access. Thisproperty allows you to differentiate between a local directory and a remotedirectory mounted to allow for FTP access.

v FC FSLL - This is the Flow Control Free Space Low Limit property. Whenthis set limit is reached the Disk Usage Server will contact all componentswho reside in this root directory and tell them to free up all space possible.

v FC QUOTA - This is the Flow Control Quota property. This property allowsyou to set the amount of disk space in bytes available to Tivoli NetcoolPerformance Manager components on this file system.

v Remote User - User account used when attempting to access this Disk UsageServer remotely.

v Remote User Password - User account password used when attempting toaccess this Disk Usage Server remotely.

v Secure file transfer to be used - Boolean indicator identifying if ssh shouldbe used when attempting to access this directory remotely.

v Port Number - Port number to use for remote access (sftp) in case it is a nondefault port.

Click Finishto create the host. The Topology Editor adds the host under theHosts folder in the Physical view.

Note: The DataChannel properties will be filled in automatically at a laterstage.

Adding multiple hostsYou may wish to 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 a comma

separated list.3. Click Next.4. Configure all added hosts.

The Configure hosts dialog allows you to enter configuration settings andapply these settings to one or more of the specified host set.To apply configuration settings to one or more of the specified host set:a. Enter the appropriate host configuration values. All configuration options

are described in Steps 2, and 3 of the previous process, “Add the hosts” onpage 68.

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 have beenspecified disappear from the set of selectable hosts.

d. Repeat steps a, b and c till all hosts are configured.5. Click Finish.

Add 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 Oracle server (for example, delphi). Select the appropriate host usingthe drop-down list.

Note: The operating system of the host where you configure the DatabaseConfigurations component determines the main platform for the entire TivoliNetcool Performance Manager deployment. This means that you should installall the other main components (DataView, DataMart, DataChannel and TivoliIntegrated Portal) on machines with the same operating system. The TopologyEditor enforces this constraint by listing only those hosts with the sameoperating system used to host the database.

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)

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 IBM Tivoli Netcool PerformanceManager: Property Reference Guide.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 actually install Tivoli Netcool Performance Manager, verifythat both the raid_2/oradata and raid_3/oradata directory structures have beencreated, and that the oradata subdirectories are owned by oracle:dba.

Add 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 Oracle 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 or with Tivoli Integrated Portal. Toensure you are using the right JRE you 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. See


the IBM Tivoli Netcool Performance Manager: ConfigurationRecommendations Guide document 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 should 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_PASSWORD properties in the Advanced Propertiestab. For the complete list of properties for this component, see the IBM TivoliNetcool Performance Manager: Property Reference Guide.

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 andin Tivoli Netcool Performance Manager, if either routine detects low disk spaceconditions on a disk partition hosting a portion of the Tivoli Netcool PerformanceManager database. Both scripts by default send their notifications by e-mail to alocal login name.

The two files and their installation locations are as follows:v The script installed as $ORACLE_BASE/admin/$ORACLE_SID/bin/notifyDBSpace

notifies 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.

Either file can be customized to send its warnings to a different e-mail address onthe local machine, to an SMTP server for transmission to a remote machine, or tosend the notices to the local network's SNMP fault management system (that is, toan SNMP trap manager). You can modify either script to send notifications to anSNMP trap, instead of, or in addition to its default e-mail notification.


Add 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.


Add a Tivoli Integrated PortalThe Tivoli Integrated Portal (TIP) provides an integrated console for users to logon and view information contained on the DataView server.

About this task

To add a Tivoli Integrated Portal:

Procedure1. In the Logical view, right-click on the Tivoli Integrated Portals folder and select

Add TIP from the menu.The Configure TIP Wizard is displayed.

2. The Topology Editor gives you the choice of adding an already existing TivoliIntegrated Portal to the topology or to create a new Tivoli Integrated Portal. Tocreate a new TIP, select the Create a new TIP radio button. To import analready existing Tivoli Integrated Portal into the topology, select the Importexisting TIPs from host radio button.

3. Using the drop-down list of available hosts, select the host on which TivoliIntegrated Portal should be installed (for example, delphi).

Note: The hostname of the host selected for the TCR install must not containunderscores. Underscores in the hostname will cause the installation of TCR tofail.

4. Click Finish.The Topology Editor adds the new Tivoli Integrated Portal component to theLogical view.

5. Highlight the Tivoli Integrated Portal component to display its properties.6. Review the other property values to make sure they are valid. For the complete

list of properties for this component, see the IBM Tivoli Netcool PerformanceManager: Property Reference Guide.

Discovering existing Tivoli Integrated PortalsAbout this task

To discover existing Tivoli Integrated Portals:

This step runs an asychronous check for existing Tivoli Integrated Portals on eachselected DataView host. If a Tivoli Integrated Portal is discovered to exist on ahost. The discovered Tivoli Integrated Portal detail is added to the topology.

Procedure1. In the Logical view, right-click on the Tivoli Integrated Portals folder and select

Import existing TIPs from host from the menu. The Run TIP Discovery WizardPage is displayed.

2. Select the check box for each host on which you would like to perform TivoliIntegrated Portal discovery.

3. Click Add TIP.If the discovered Tivoli Integrated Portal is an old version, it is flagged withinthe topology for upgrade.Any DataView without a Tivoli Integrated Portal is flagged within the topologyfor Tivoli Integrated Portal installation on that host.The deployer will take the appropriate action when run.


4. Click Next.5. Configure Tivoli Integrated Portal properties.

a. Enter the appropriate host configuration values.v TCR_INSTALLATION_DIRECTORY: This is the directory in which Tivoli

Common Reporting is installed.v TIP_INSTALLATION_DIRECTORY: This is the directory in which Tivoli

Integrated Portal is installed.v WAS_USER_NAME: This is the WAS user name.v WAS_PASSWORD: This is the WAS password.If you would like to configure LDAP for Tivoli Integrated Portal, select theLDAP check box.

b. Select the check box opposite each of the Tivoli Integrated Portal hosts towhich you want to apply the entered values.

c. Click Next.The hosts for which all configuration settings have been specified disappearfrom the set of selectable hosts.

d. Repeat steps a, b and c till all hosts are configured.6. Click Next to add the discovered Tivoli Intergrated Portals to the topology.

Note: If you discover a Tivoli Common Reporting/Tivoli Intergrated Portal ofversion 2.1 that was installed using the Tivoli Common Reporting installer andnot the Tivoli Netcool Performance Manager installer, the port will not alignwith a Technology Pack automatically. To align the port numbers you mustspecify the Tivoli Intergrated Portal port when performing the Technology Packinstallation.

Add a DataViewHow to add a DataView.

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 Sun download page at http://www.sun.com.

To add a DataView component:

Procedure

In the Logical view, right-click on a Tivoli Integrated Portal and select AddDataView from the menu. The DataView is automatically added inheriting itsproperties from the Tivoli Integrated Portal instance.


Add 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:v Channel Manager - Enables you to start and stop individual DataChannels

and monitor the state of various DataChannel programs. There is oneChannel Manager for the entire DataChannel configuration. The ChannelManager components are installed on the first host you specify

v Corba Naming Server - Provides near real-time data to DataView.v High Availability Managers - This is mainly used for large installations that

want to use redundant SNMP collection paths. The HAM constantlymonitors the availability of one or more SNMP collection hosts, and switchescollection to a backup host (called a spare) if a primary host becomesunavailable.

v Log Server - Used to store user, debug, and error information.v Plan Builder - Creates the metric data routing and processing plan for the

other components in the DataChannel.v Custom DataChannel properties - These are the custom property values that

apply to all DataChannel components.v Global DataChannel properties - These are the global property values that

apply to all DataChannel components.

Add 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 IBM Tivoli Netcool Performance Manager: PropertyReference Guide.The DataChannel has the following subelements:v Daily Loader x - Processes 24 hours of raw data every day, merges it

together, then loads it into the database. The loader process providesstatistics on metric channel tables and metric tablespaces.

v Hourly Loader x - Reads files output by the Complex Metric Engine (CME)and loads the data into the database every hour. The loader process providesstatistics on 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 may wish to separate the data and executable directories for yourDataChannel

About this task

If you wish to separate the data and executable directories for your DataChannel,perform the following steps:

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 will see the DATA_DIR value propagatedto all DC folder values for the host.

3. Change DC_ROOT_EXE_DIRECTORY to the executable directory EXE_DIR.This change will propagate to the DC conf directory, the DataChannel BinDirectory and the Datachannel executable file name.

Note: For advanced information about DataChannels, see Appendix B,“DataChannels,” on page 141.


Add 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 Oracle 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:v SNMP collector - Collects data using SNMP polling directly to network services.

Specify this collector type if you plan to install a Tivoli Netcool PerformanceManager SNMP technology pack. These technology packs operate in networkingenvironments where the associated devices on which they operate use an SNMPprotocol.

v Bulk DataLoad collector - Imports data from files. The files can have multipleorigins, including log files generated by network devices, files generated bySNMP collectors on remote networks, or files generated by a non-Tivoli NetcoolPerformance Manager network management database.

There are two types of bulk collectors:v UBA. A Universal Bulk Adapter (UBA) Collector that handles bulk input files

generated by non-SNMP devices. Specify this collector type if you plan to installa Tivoli Netcool Performance Manager UBA technology pack, including Alcatel5620 NM, Alcatel 5620 SAM, and Cisco CWM.

v BCOL. A bulk Collector that retrieves and interprets the flat file output ofnetwork devices or network management systems. This collector type is notrecommended for Tivoli Netcool Performance Manager UBA technology packs,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 the followingsequence 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 Technology Pack Installation Guide. Configure theinstalled pack by following the instructions in the pack-specific user'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).

Creating an SNMP collectorHow 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 beforea BCOL collector can be added.

Select Add Collector SNMP. The Configure Collector window opens.2. Using the drop-down list of available hosts on the Configure Collector window,

select the machine that will host the collector (for example, corinth).3. Accept the default collector number (for example, 1).4. Click Finish.

The Topology Editor displays the new collector under the DataChannel x folderin the Logical view.

5. 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.

Note: For information about the core parameters, see the IBM Tivoli NetcoolPerformance Manager: Property Reference Guide.

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.

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 will hostthe Cross-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 IBM Tivoli Netcool PerformanceManager: Property Reference Guide

8. After running the deployer to install the Cross-Collector CME you will need torestart the CMGR process.

Note: You will notice that dccmd start all will not start the Cross-CollectorCME at this 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-CME


depends 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 toplolgy 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 will set the number of Cross CollectorCMEs to 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” onpage 82).

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” on page 82.See Chapter 5, “Modifying the current deployment,” on page 95 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 the section Deploying the Topology.

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:

Procedure1. If it is not already open, open the Topology Editor (see “Starting the Topology

Editor” on page 67).2. In the Topology Editor, select Topology > Open existing topology. The Open

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 87 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 2, “Installing andconfiguring the prerequisite software,” on page 13 for more information.

Primary DeployerThe steps 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 using 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 137.

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:On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/deployer/

On AIX systems:# cd <DIST_DIR>/proviso/AIX/Install/deployer/

On Linux 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 “Downloadingthe Tivoli Netcool Performance Manager distribution to disk” on page 26.

3. Enter the following command:# ./deployer.bin

Note: See Appendix D, “Deployer CLI options,” on page 159 for the list ofsupported command-line options.

Pre-deployment checkThe Deployer will fail 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 found at:/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 found at:/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 will return 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 openmotif package is listed as missing:

Install the missing openmotif 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,which enables you to run each step individually or to run all the steps at once. Formore information about the deployer interface, see “Primary Deployer” on page82.

Important: By default, Tivoli Netcool Performance Manager uses Monday todetermine when a new week begins. If you wish to specify a different day, youmust change the FIRST_WEEK_DAY parameter in the Database Registry using thedbRegEdit utility. This parameter can only be changed when you first deploy thetopology that installs your Tivoli Netcool Performance Manager environment, andit must be changed BEFORE the Database Channel is installed. For moreinformation, see the Tivoli Netcool Performance Manager Registry and SpaceManagement Tech Note.

If you need to stop the installation, you can resume it at a later time. For moreinformation, see “Resuming a partially successful first-time installation” on page87.

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,and user name). Note that if the database does not yet exist, these parametersmust match the values you specified when you created the databaseconfiguration component (see “Add a database configurations component” onpage 70). Click Next to continue.

4. The node selection window shows the target systems and how the files will betransferred (see “Secondary Deployers” on page 83 for an explanation of thiswindow). The table has one row for each machine where at least one TivoliNetcool Performance Manager component will be installed.The default settings are as follows:v The Enable checkbox is selected. If this option is not selected, no actions

will be performed on that machine.v The Check prerequisites checkbox is not selected, if selected scripts are run

to verify that the prerequisite software has been installed.v Remote execution is enabled, using both RSH and SSH.

If remote execution cannot be enabled, perhaps due to a particularcustomer's security protocols, see Appendix A, “Remote installation issues,”on page 137 and “Resuming a partially successful first-time installation” onpage 87.

v File transfer using FTP is enabled.If desired, 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 on the Choose the Proviso Media button. 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.

6. The deployer displays summary information about the installation. Review theinformation, then click Next.The deployer displays the table of installation steps (see “Pre-deploymentcheck” on page 83 for an overview of the steps table). Note the following:v Regardless of whether the steps are run, or if they pass or fail, closing the

wizard will result in the topology being posted to the Tivoli NetcoolPerformance Manager Database, assuming it exists.

v If an installation step fails, see “Resuming a partially successful first-timeinstallation” on page 87 for debugging information. Continue theinstallation by following the instructions in “Resuming a partially successfulfirst-time installation” on page 87.

v If the TCR installation step fails, which can happen when there is notenough space available in /usr and /tmp or directory cleanup has not beencarried out, run the tcrClean.sh script. To run this script:

a. Copy the tcrClean.sh script from the Primary Deployer (host where theTopology Editor is installed) to the server where the TCR installation stepfails.The tcrClean.sh script can be found on the Primary Deployer in thedirectory:

/opt/IBM/proviso/deployer/proviso/bin/Util/


b. Run tcrClean.sh.c. When prompted, enter the install location of TCR.d. Continue the installation by following the instructions in “Resuming a

partially successful first-time installation” on page 877. Click Run All to run all the steps in sequence.8. 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 contentsof the Tivoli Netcool Performance Manager distribution in “Downloading theTivoli Netcool Performance Manager distribution to disk” on page 26.

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”on page 26.If Tivoli Integrated Portal is configured to install on a remote host, the RunRemote TIP Install step is included. This step will prompt the user to enter theroot password. The deployer requires this information in order to run as rooton the remote host and perform the Tivoli Integrated Portal installation.

9. When all the steps have completed successfully, click Done to close thewizard.

10. Stop and start TCR:a. Navigate to the /tip_install_dir/products/tcr/bin/ directory.b. Set the ORACLE_HOME environment variable. For example:

ORACLE_HOME=/opt/oracle/product/10.2.0export ORACLE_HOME

c. Execute the following:LD_LIBRARY_PATH= $ORACLE_HOME/lib32:$LD_LIBRARY_PATHexport LD_LIBRARY_PATH

d. Run the following scripts:v stopTCRserver.sh <username> <password>v startTCRserver.sh

Note: These scripts must be run every time Tivoli Integrated Portal isrestarted.

Note: The Topology Editor must be closed after every deployment.

Next stepsThe steps to perform after deployement.

The next step is to install the technology packs, as described in Technology PackInstallation Guide.

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 run


the deployer with the updated topology file as input. For more information aboutperforming incremental installations, see Chapter 5, “Modifying the currentdeployment,” on page 95.

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 dbMgr Reference Guide.

For each new SNMP DataLoad, change the env file of the TNPM user to add thedirectory with the openssh libcrypto.so to the LD_LIBRARY_PATH (or LIBPATH).

Resuming a partially successful first-time installationShould your quit during an installation, this section describes how you can resumethe installation process.

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 skipping this portion of theinstallation, resume the installation to continue with the remaining steps. Thedeployer will list only those steps needed to complete the installation on themissing node.

For example, suppose that during the first installation, Oracle wasn't running, sothe database check failed. Stop the installation, start Oracle, then resume theinstallation.

To resume a partial installation:

Procedure1. After correcting the problem, restart the deployer from the command line using

the following command:


./deployer.bin -Daction=resume

Using the resume switch enables you to resume the installation exactly whereyou left off.

Note: If you are asked to select a topology file in order to resume yourinstallation, select the topology file you saved before beginning the install.

2. The deployer opens, displaying a welcome page. Click Next to continue.3. Accept the default location of the base installation directory of the Oracle JDBC

driver (/opt/oracle/product/version/jdbc/lib), or click Choose to navigate toanother directory. Click Next to continue.

4. The steps page shows the installation steps in the very same state they were inwhen you stopped the installation (with the completed steps marked Success,the failed 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 4. Installing as a minimal deployment

This chapter describes how to install Tivoli Netcool Performance Manager as aminimal deployment.

OverviewA minimal deployment installation is used primarily for demonstration or evaluationpurposes, and installs the product on the smallest number of machines possible,with minimal user input.

This installation type installs all the Tivoli Netcool Performance Managercomponents on the local host using a predefined topology file to define theinfrastructure. The minimal deployment installation also installs the MIB-II SNMPtechnology pack.

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 2, “Installing and configuring the prerequisitesoftware,” on page 13.

Note: Before you start the installation, verify that all the database tests have beenperformed. Otherwise, the installation might fail. See

Chapter 2, “Installing and configuring the prerequisite software,” on page 13

for information about tnsping.

Minimal Installation Process:

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 to beattempted.

Overriding default valuesWhen performing a minimal deployment installation you must accept all defaultvalues. The exceptions are listed in this section.

The expections to this are:v The location of the oracle jdbc driver.

The default is /opt/oracle/product/10.2.0/jdbc/li

v The Tivoli Netcool Performance Manager installation destination folder.The default is /opt/proviso

v Oracle server params. The defaults are:– Oracle Base: /opt/oracle– Oracle home: /opt/oracle/product/10.2.0– Oracle Port: 1521


Installing a minimal deploymentThis section provides step-by-step instructions for installing Tivoli NetcoolPerformance Manager on a single Solaris, AIX or Linux server.

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.

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.

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 14).3. Set and export the BROWSER variable to point to your Web browser. For

example:On Solaris systems:# BROWSER=/opt/mozilla/mozilla# export BROWSER

On AIX systems:# BROWSER=/usr/mozilla/firefox/firefox# export BROWSER

On Linux systems:

Chapter 4. Installing as a minimal deployment 91

https://www-112.ibm.com/software/howtobuy/softwareandservices

https://www-112.ibm.com/software/howtobuy/softwareandservices

# BROWSER=/usr/bin/firefox# export BROWSER

Note: The BROWSER command cannot include any spaces around the equalsign.

4. Change directory to the directory where the launchpad resides.On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS

On AIX systems:# cd <DIST_DIR>/proviso/AIX

On Linux systems:# cd <DIST_DIR>/proviso/RHEL


5. Enter the following command to start the launchpad:# ./launchpad.sh

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 1.3.1

for Minimal Deployment option in the list of tasks, then click the InstallTivoli Netcool Performance Manager 1.3.1 for Minimal Deployment link tostart the deployer.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 14).c. Change directory to the directory that contains the deployer:

On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/deployer

On AIX systems:# cd <DIST_DIR>/proviso/AIX/Install/deployer

On Linux 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 Oracle

JDBC driver (/opt/oracle/product/version/jdbc/lib), or click Choose tonavigate to another directory. Click Next to continue.


5. The deployer prompts for the directory in which to install Tivoli NetcoolPerformance 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 Oracle database:v Oracle Base. The base directory for the Oracle installation (for example,

/opt/oracle). Accept the provided path or click Choose to navigate toanother directory.

v Oracle Home. The root directory of the Oracle database (for example,/opt/oracle/product/10.2.0). Accept the provided path or click Choose tonavigate to another directory.

v Oracle Port. The port used for Oracle communications. The default value is1521.

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 on the Choose the Proviso Media button. 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 83 for an overview of the steps table). Note the following:v If an installation step fails, see Appendix I, “Error codes and log files,” on

page 187 for debugging information. Continue the installation by followingthe instructions in “Resuming a partially successful first-time installation”on page 87

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 TIP

directory structure accessible.Your installation is complete. See “The post-installation script” on page 94 forinformation about the post-installation script, or “Next steps” on page 94 forwhat to do next.

Chapter 4. Installing as a minimal deployment 93

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 information about the MIB-II Technology Pack, see the MIB-II Technology PackUser's Guide.

For information about installing additional technology packs, see the TechnologyPack Installation Guide

For each new SNMP DataLoad, change the env file of the TNPM user to add thedirectory with the openssh libcrypto.so to the LD_LIBRARY_PATH (or LIBPATH).


Chapter 5. Modifying the current deployment

This chapter describes how to modify an installation of Tivoli Netcool PerformanceManager.

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 129.

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:


Editor” on page 67).2. In the Topology Editor, select Topology > Open existing topology. The Open

Topology window is displayed.3. For the topology source, select From database (v. 443) and click Next.4. Verify that all of the fields for the database connection are filled in with the

correct values:


v Database hostname - The name of the database host. The default value islocalhost.

v Port - The port number used for communication with the database. Thedefault value is 1521.

v Database user - The user name used to access the database. The defaultvalue is PV_INSTALL.

v Database Password - The password for the database user account. Forexample, PV.

v SID - The SID for the database. The default value is PV.If desired, click Save as defaults to save these values for future incrementalinstallations.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 67).2. Open the existing topology (see “Opening a deployed topology” on page 95).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 “Add the hosts” on page 68v “Add a database configurations component” on page 70v “Add a DataMart” on page 71v “Add a Discovery Server” on page 73v “Add a Tivoli Integrated Portal” on page 74v “Add a DataView” on page 75v “Add the DataChannel administrative components” on page 76v “Add a DataChannel” on page 76v “Add a Collector” on page 78

Note: that if you add a collector to a topology that has already beendeployed, you must manually bounce the DataChannel management


components (cnsw, logw, cmgrw, amgrw). For more information, see “Manuallystarting the Channel Manager programs” on page 146.

v “Add a Discovery Server” on page 736. 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 82), 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 129.

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 TopologyEditor” on page 67).

2. Open the existing topology (see “Opening a deployed topology” on page 95).3. In the Logical view of the Topology Editor, right-click the DataChannels folder.4. Select Add Data Channel from the pop-up menu. Following the directions in

“Add a DataChannel” on page 76, 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 82), 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.

Chapter 5. Modifying the current deployment 97

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 the configuredstate, the Topology Editor provides a Change Host option in the pop-up menuwhen you click the component name in the Logical view. This option allows you tochange the host associated with the component prior to deployment.

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 thepop-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” on page 99. For instructionson moving components that have not yet been deployed, see the informationbelow.

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. tart 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 67 and “Opening a deployed topology” on page 95).

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 several hours for the changeto be registered in the database.

Moving a deployed SNMP collectorThe steps required to move a deployed SNMP collector to a different 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:

Procedure1. Start the Topology Editor (if it is not already running) and open the topology

that includes the collector's current host (see “Starting the Topology Editor” onpage 67 and “Opening a deployed topology” on page 95).

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 82.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. Doingso guards against data loss between collections on the original host and thestart 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 minutes. You can find the collection periodfor the sub-element, sub-element group, or collection formula associated withthe collector in the DataMart Request Editor. For information on viewing andsetting a collection period, see the Tivoli Netcool Performance Manager DataMartConfiguration Guide.

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 to remove the collector from the original host, passing theupdated topology as input. For more information, see “Removing a componentfrom the topology” on page 129.

Note: This step is not necessary if you are moving a collector that has not beendeployed.

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” on

page 99.

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. Source the DataLoad environment again:. ./dataLoad.env

8. 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 125.

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 names as thecorresponding 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 67 and “Opening a deployed topology” on page 95).

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 DataChannel installation from theoriginal host after you finish the steps below. For information on removingDataChannel from the host, see “Removing a component from the topology”on page 129.

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 82.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 129.

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

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.


Chapter 6. Using the High Availability Manager

This chapter describes the optional Tivoli Netcool Performance Manager HighAvailability Manager (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.

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


collector 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:v Collector Processes. A collector process is a Unix process representing a runtime

instance of a collector. A collector process is identified by the name of the hostwhere the process is running and by the collector process port (typically 3002).A host can have just one SNMP collector process.

v Managed Definitions. A managed definition identifies a collector profile throughthe unique collector number defined in the profile.Every managed definition has a default binding to a host and to the collectorprocess on that host. The default host and collector process are called themanaged definition's primary host and collector process.A host that 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.

Types of spare hostsThere are two types of spare hosts:v Designated spare. The sole purpose of this type of spare in a HAM cluster is to

act as a backup host.A designated spare has a collector process, but no default managed definition.Its collector process remains idle until the HAM detects an outage on one of theactive hosts, and binds that host's managed definition to the spare's collectorprocess.A HAM cluster must have at least one designated spare.

v Floating spare. This type of spare is a primary host that can also act as a backuphost for one or more managed definitions.

Chapter 6. Using the High Availability Manager 107

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:v Fixed spare cluster. In this type of cluster, failover can occur only to designated

spares. There are no floating spares in this type of cluster.When the HAM binds a managed definition to the spare, the spare temporarilytakes the place of the primary that has become unavailable. When the primarybecomes available again, you must reassign the managed definition back to theprimary (or to another available host). The primary then resumes its datacollection operations, and the spare resumes its role as backup host.If you do not reassign the managed definition back to the primary, the primarycannot participate in further collection operations. Since the primary is notconfigured as a floating spare, it also cannot act as a spare now that its collectorprocess is idle. As a result, the HAM cluster loses its failover capabilities if noother spare is available.

Note: A primary host cannot act as a spare unless it is configured as a floatingspare.

v Floating spare cluster. This type of cluster has one or more primary hosts thatcan also act as a spare. Failover can occur to a floating spare or to a designatedspare.You do not need to reassign the managed definition back to this type of primary,as you do with primaries in a fixed spare cluster. When a floating spare primarybecomes available again, it assumes the role of a spare.You can designate some or all of the primaries in a HAM cluster as floatingspares. If all the primaries in a HAM cluster are floating spares, you shouldnever have to reassign a managed definition to another available host in order tomaintain failover capability.

Note: IBM recommends that all the primaries in a cluster be of the same type -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 unbindsthe 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 nolonger 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

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 unbinds

the 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.





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

-


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 5. 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 6. 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 will act as the primary

hosts. You will create a managed definition for each of the primary hosts.v One additional host that is not bound to an SNMP collector. This will act as the

designated spare.

For information on installing these components, see “Adding a new component”on page 96.

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

Procedure1. Start the Topology Editor (if it is not already running) and open the topology

where you want to add the HAM (see “Starting the Topology Editor” on page67 and “Opening a deployed topology” on page 95).

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.

Add the designated spareHow to create and add a designated spare.

About this task

To create a designated spare, you must have a host defined in the Physical viewwith no SNMP collector assigned to it. For information on adding a host to atopology, see “Add the hosts” on page 68

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 118.

2. Select Add Collection Process SNMP Spare from the pop-up menu.The Add Collection Process SNMP Spare - Configure Collector Process SNMPSpare dialog appears.

3. In the Available hosts field, select the host that you want to make thedesignated spare.This field contains the names of hosts in the Physical view that do not haveSNMP collectors assigned to them.

4. In the Port field, specify the default port number, 3002, for the spare's collectorprocess, 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 additional designated spare tothe cluster.

What to do next

Should you be making changes to an already existing configuration, please makesure the dataLoad.env file contains all the right settings:1. Change to the directory where DataLoad is installed. For example:

cd /opt/dataload

2. Source the DataLoad environment:. ./dataLoad.env

3. Make sure that DL_HA_MODE field in the dataLoad.env file and set toDL_HA_MODE=true.

4. Source the DataLoad environment again:. ./dataLoad.env


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 118.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 in Step3.

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 123 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 82), 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 the Tivoli Netcool Performance ManagerCommand Line Interface Guide.

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 117.

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 117. 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 100.

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 98.

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.

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 121


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 the Tivoli Netcool Performance ManagerCommand Line Interface Guide.

5. Bounce the Channel Manager. For instructions, see Step 15.

Viewing the current configurationDuring the process of creating or modifying a HAM cluster, you may find it usefulto check how the individual collector processes and managed definitions arecurrently configured.

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 pop-up menu.

The Show Collector Process... or Show Managed Definition... dialog appears.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 7. Uninstalling components

This chapter provides information about uninstalling 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.

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.

Restrictions and behaviorRestrictions and behaviour to observe when performing an uninstall.

Before you remove a component, note the following: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: Once components are marked for deletion, the topology must be consumedby the deployer to propagate the required changes and load the updated file in thedatabase. When you open the database version of the topology, the "removed"component will disappear 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:1. Open the Topology Editor and remove all components related to the host

system2. Remove the host system from the topology3. Redeploy the topology, ignoring any messages 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.

DataChannel restrictions:v 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 should first bestopped. If you are uninstalling all DataChannel components on a host, then youshould 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. This 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 TivoliIntegrated Portal instance. If other products are installed in the same TivoliIntegrated Portal instance, you must use the following procedure to uninstall aDataView component:1. Run the uninstall command:

<tip_location>/products/tnpm/dataview/bin/uninstall.sh <tip_location><tip_administrator_username> <tip_administrator_password>

2. Remove the DataView directory:rm -rf <tip_location>/products/tnpm/dataview

3. In the Topology Editor:4. Remove the DataView component.5. Save the topology.6. Run the deployer for uninstallation.7. Mark the DataView step successful.8. Run the unregister DataView step.

Note: Once this manual un-install is completed, the DataView instance will remainin the topology after the un-install operation completes, this is not usually the casefor un-installed components.

Removing a componentTo remove component from the topology.


Editor” on page 67).2. Open the existing topology (see “Opening a deployed topology” on page 95).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 82).

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 will need to bounce CMGRafter you have run the deployer, so it will pick up the updated configuration andrealize the components have been removed. If you do not bounce CMGR after thedeployer runs then you may get errors when you the components are restarted.

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). See Appendix B,“DataChannels,” on page 141 for more information about the findvisualcommand.

2. DataMart3. DataChannel Administrative Components and any remaining DataChannel

components.4. DataView Also remove Tivoli Integrated Portal/Tivoli Common Reporting.5. 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.

Chapter 7. Uninstalling components 131

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 “Residual files” on page 133 for the list offiles that must be deleted manually.

Performing the uninstallHow to uninstall the Tivoli Netcool Performance Manager installation.

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 14).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 Oracle JDBC

driver (/opt/oracle/product/version/jdbc/lib), or click Choose to navigate toanother directory. Click Next to continue.

4. A pop-up opens, asking whether you want to download the topology from thedatabase. Click Yes.

5. 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, and user name).Click Next to continue.


6. The uninstaller displays a message stating that the topology download wassuccessful and saved to the file /tmp/ProvisoConsumer/Topology.xml. ClickNext to continue.

7. The uninstaller displays several status messages, then displays a messagestating that the environment status was successfully downloaded and saved tothe file /tmp/ProvisoConsumer/Discovery.xml. Click Next to continue.

8. A pop-up opens, stating that no operations need to be executed on your nodes.The uninstaller closes.

9. Repeat the process on each machine in the deployment.

Note: After the removal of each Component using the Topology Editor, theTopology Editor should 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 this section. Do notsimply delete the /opt/IBM directory. Doing so will cause problems when you tryto reinstall the Topology Editor. If the /opt/IBM directory is accidentally deleted,perform the workaround documented in “Installing the Topology Editor” on page66.

Note: Uninstall Tivoli Netcool Performance Manager before uninstalling 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 14).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.

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 oracle.2. Enter the following commands to stop Oracle:

sqlplus "/ as sysdba"shutdown abortexitlsnrctl stop

3. As root, enter the following 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/notifyConnection

where $ORACLE_BASE is /opt/oracle and $ORACLE_HOME is/opt/oracle/product/10.2.0.

4. Enter the following commands to clear your Oracle mount points and removeany files in those directories:rm -r /raid_2/oradata/*rm -r /raid_3/oradata/*

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

What to do next

Following TCR uninstallation:

To prevent any possible system instability caused by residual processespost-uninstall of TCR, run the tcrClean.sh script on all systems where TCR hasbeen uninstalled:1. On the host where the TCR installation failed, change to the directory

containing tcrClean.sh:cd /opt/IBM/proviso/deployer/proviso/bin/Util/

2. Run tcrClean.sh3. When prompted, enter the location where TCR was installed.


Note: If you have uninstalled TCR on a remote host, the tcrClean.sh file will needto be sent 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 using a secondarydeployer” on page 138.


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 using a secondarydeployer.”

Installing on a remote host using a secondary deployerThe general procedure for installing a component on a remote host using asecondary deployer.

About this task

A secondary deployer is used when the host you wish to install on does notsupport remote installation.

The following steps describe how to install a Tivoli Netcool Performance Managercomponent using a secondary deployer. For the purposes of clarity, we will namethe primary deployer host delphi, and the host on which we want to install acomponent using the secondary deployer we will 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 on copying the Tivoli NetcoolPerformance Manager distribution to a server, see “Downloading the TivoliNetcool Performance Manager distribution to disk” on page 26.

2. Open the Topology Editor on the primary deployer host, that is, on delphi, andadd the remote component to the topology definition.You may have completed this task already when creating your originaltopology definition. If you have already added the remote component to yourtopology definition, skip to the next step.

3. Deploy the new topology containing the added component using the TopologyEditor. This is done by clicking Run > Run Deployer for Installation. This willpush the edited topology to the database.

4. Open the Deployer on corinth by doing the following:


a. Connect to corinth, change to the directory where you have downloaded theproduct distribution, and launch the deployer either in graphical mode (bystarting the Launchpad and clicking Start Deployer) or CLI mode (bynavigating to the directory containing the deployer and entering thecommand ./deployer.bin).

b. Enter the database credentials when prompted. The deployer connects tothe database.For more information on how to run a secondary deployer, see “SecondaryDeployers” on page 83.

Note: Due to Step 3, the secondary deployer sees the topology data andknows that the required component is still to be installed on corinth.

5. Follow the on screen instructions to install the desired component.

Note: You cannot launch the deployer simultaneously from two different hosts.Only one deployer can be active at any given time.

Appendix A. Remote installation issues 139

Appendix B. DataChannels

This section 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 scriptsManagement Programs and Watchdog Scripts

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.

crontab -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.

Starting the DataChannel management programsHow to check if DataChannel management programs are running and then startapplication programs.

Appendix B. DataChannels 143

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 Tivoli Netcool Performance Manager Command Line Interface Guide forinformation about the dccmd command.

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 1 Application Manager (AMGR)v 2 Complex Metric Engines (CME)v 2 File Transfer Engines (FTE)v 2 Hourly Data Loaders (LDR)v 2 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 143.

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 5, “Modifying the current deployment,” on page 95.

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 146.

DataChannel terminologyTerms used throughout the Tivoli Netcool Performance Manager DataChannelinstallation procedure.v Collector Subchannel: A subdivision of a DataChannel, with each Collector

subchannel associated with a single Collector and CME. The division intoCollector subchannels helps eliminate latency or loss of data caused by delayedCollectors. If a Collector subchannel disconnects for a period of time, only thatCollector is affected, and all other Collector subchannels continue processing.The number of Collector subchannels per DataChannel differs according to theneeds of a particular deployment. See the Tivoli Netcool Performance ManagerConfiguration Recommendations for information related to system configurationrequirements. The terms Collector and Collectors are used to refer to Collectorsubchannel and Collector subchannels.

v Complex Metric Engine (CME): A DataChannel program that performson-the-fly calculations on raw metrics data for a DataChannel. These calculationsinclude time aggregations for resources, as well as statistical calculations usingraw data, thresholds, properties, and constants as inputs. If CME formulas aredefined for the incoming metrics data, the values are processed by those


formulas. The CME synchronizes metadata at the beginning of each hour, andonly processes the metadata that exists for the hour.

v CORBA (Common Object Request Broker Architecture): An industry-standardprogramming architecture that enables pieces of programs, called objects, tocommunicate with one another regardless of the programming language thatthey were written in or the operating system they are running on.

v Daily Database Loader (DLDR): A DataChannel program that gathers statisticaldata processed by a DataChannel's CME and inserts it into the Tivoli NetcoolPerformance Manager database. There is one Daily Loader for eachDataChannel; it is part of the channel processor component of the DataChannel.

v DataChannel Remote (DCR): A DataChannel installation configuration in whichthe subchannel, CME and FTE components are installed and run on one host,while the Loader components are installed and run on another host. In thisconfiguration, the subchannel hosts can continue processing data and detectingthreshold violations, even while disconnected from the Channel Manager server.

v DataChannel Standard: A DataChannel installation configuration in which allcomponent programs of each subchannel are installed and run on the sameserver. DataChannel Standard installation is described in this chapter.

v DataLoad Bulk Collector: A DataLoad program that processes different dataformats and resource files supplied by network devices, network managementplatforms, network probes, and other types of resources such as BMC Patrol.The Bulk Collector translates bulk statistics provided in flat files into TivoliNetcool Performance Manager metadata and data. If operating in synchronizedinventory mode, the Bulk Collector passes the resources and properties to theTivoli Netcool Performance Manager DataMart Inventory application.

v DataLoad SNMP Collector: A DataLoad program that collects data fromnetwork resources via SNMP polling. The SNMP Collector provides raw datafiles to the DataChannel for processing by the CME.

v DataLoad UBA Bulk Collector: A DataLoad program that imports data fromfiles (referred to as Bulk input files) generated by non-SNMP devices, includingAlcatel 5620 NM, Alcatel SAM, and Cisco CWM. These Bulk input files containformats that the Bulk Collector is unable to handle.

v Discovery Server (DISC): A DataChannel program that runs as a daemon toperform an inventory of SNMP network devices from which to gather statisticaldata.

v Hourly Database Loader (LDR): A DataChannel program that serves as thepoint of data synchronization and merging, and of late data processing, for eachDataChannel. The Hourly Loader gathers files generated by the CME, computesgroup aggregations from the individual resource aggregation records, and loadsthe data into the Tivoli Netcool Performance Manager database.

v File Transfer Engine (FTE): A DataChannel program that periodically scans theCollector output directories, examines the global execution plan to determinewhich computation requests require the data, then sorts the incoming data forstorage.

v Next-Hour Policy: Specifies the number of seconds to wait past the hour for filesto arrive before the next hourly directory is created. The default value causes theDataChannel to wait until 15 minutes after the hour before it starts processingdata for the next hour. To avoid losing data, you need to set a percentage and atime-out period during the configuration of the CME.

v Plan Builder (PBL): A DataChannel program that creates the metric data routingand processing plan for the other components in the DataChannel.


Appendix C. Aggregation sets

This appendix 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 2010. (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:v

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 press Enter to enter the password forPV_ADMIN. The script prompts twice for the password you set up forPV_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 differentDB_USER_ROOT setting, the "Database user" entry reflects your settings. Forexample, if you previously set DB_USER_ROOT=PROV, this script wouldgenerate the administrative 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 | Aggset status

| | 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:


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 149), you can skip this section. However, f you configured timezones 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. ORACLE_HOME : /opt/oracle/product/10.2.03. 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, ORACLE_HOME, andORACLE_SID are the same ones you entered in previous chapters. Correct thevalues 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 password

for 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 149. 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 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/oradataEXTENT_SIZE=64KSIZE=10M#[AGGSETREG/C01/1DGA/TABLESPACE/HISTORIC]CREATION_PATH=/raid_3/oradataEXTENT_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 149 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]

For example, the following command performs a minimal deployment installation:# ./deployer.bin -Daction=poc

The deployer.bin command accepts the following options:

Option Description

-Daction=mib Used with -Daction=poc to complete aminimal deployment installation on an AIXsystem.

-Daction=patch Performs a patch installation of TivoliNetcool Performance Manager. SeeAppendix H, “Installing an interim fix,” onpage 183 for more information.

-Daction=poc Performs a minimal deployment installation.See Chapter 4, “Installing as a minimaldeployment,” on page 89 for moreinformation.

-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 87 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 131for more information.

-DCheckUser 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 Enables you to specify the Oracle clienthome, so the wizard screen that promptsyou for that information is skipped.

-DOracleServerHost=hostname Specifies the hostname or IP address wherethe Oracle server resides.

-DOracleServerPort=port Specifies the communication port used bythe Oracle server. Default is 1521.


Option Description

-DOracleSID=sid Specifies the Oracle server ID. Default is PV.

-DOracleAdminUser=admin_user Specifies the administrator username for theOracle server. Default is PV_INSTALL.

-DOracleAdminUser=admin_password Specifies the administrator password for theOracle 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.

-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.

TIP Instructs the deployer to install TIP on thelocal 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.

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.

TIPR Instructs the deployer to remove TIPfromthe local machine. Requires the-Daction=uninstall option.

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.

Appendix D. Deployer CLI options 161

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 systemsTo 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 165

Solaris systemsOpenSSH 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 systemsOpenSSH is required for VSFTP to work with Tivoli Netcool PerformanceManager.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): pvuser


331 Password required for pvuser.Password:230 User pvuser logged in.ftp> bin180 Tivoli Netcool Performance Manager Installation Guide, Version 1.3.1200 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.

Netcool/Provisio 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

Ddetailed 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 5.2, 6.0v 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 configurationThe configuration of LDAP as a default authentication and authorizationmechanism for Tivoli Netcool Performance Manager is achieved using theTopology Editor.

Enable LDAP configurationThe LDAP configuration option becomes available after adding a Tivoli IntegratedPortal to your topology.

About this task

Note: The process of adding a Tivoli Integrated Portal to the topology using theTopology Editor is described in “Add a Tivoli Integrated Portal” on page 74.

To enable LDAP configuration:

Procedure1. In Logical View of Topology Editor, select the Tivoli Integrated Portal that you

have added.2. Open the Advanced Properties tab.3. Click the checkbox opposite the

IAGLOBAL_USER_REIGSTRY_LDAP_SELECTED property. This enables LDAP.4. In Advanced Properties tab, enter the LDAP connection details. This requires

that you populate the following fields:v WAS_USER_NAME: This is the name you have registered as the Tivoli

Integrated Portal user. For example, "tipadmin".v IAGLOBAL_LDAP_BIND_DN: This username specified must have read and

write permissions in LDAP 3. Typically this will be an LDAP administratorusername. For example "cn=Directory Manager".

v IALOCAL_LDAP_BIND_PASSWORD: This is the password for the BindDistinguished Name specified.


v IAGLOBAL_LDAP_NAME: This is the LDAP server host name. Should thisLDAP server exist behind firewall, make sure that this host has beenauthenticated.

v IAGLOBAL_LDAP_PORT: For example, "1389".v IAGLOBAL_LDAP_REPOSITORY_ID: This is a string used to identify the

LDAP repository, which can be set to the string of your choice.v IAGLOBAL_LDAP_BASE_ENTRY: The 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 need to assign them to one of thefollowing roles:v tnpmUserv tnpmAdministrator

This can be done by tipadmin user, by navigating to Users and Groups >Administrative User Roles, and assigning the correct roles.Alternatively tipcli.sh can be used for assigning roles to the user.<tip_location>/profiles/TIPProfile/bin/tipcli.sh MapRolesToUser --username<tip_admin_user> --password <tip_admin_password> --userID <userUniqueId> --rolesList <roleName>

where <userUniqueId> is the concatenation of username and realm in which userinformation is stored.For example:


<tip_location>/profiles/TIPProfile/bin/tipcli.sh MapRolesToUser --username<tip_admin_user> --password <tip_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. Roles are stored in a flat XML file in the TIPdirectory. For example, if you assign a Tivoli Netcool Performance Manager role toan LDAP user on tip_instance1, you must also assign the same role to the user ontip_instance2. Otherwise, the user cannot authenticate on tip_instance2.Alternatively you can assign tnpmUser role to tnpmUsers group on tip_instance1.If the user is a member of this group then user can authenticate on tip_instance2.

Appendix F. LDAP integration 177

Appendix G. Using silent mode

This appendix describes how to use silent mode to run the deployer or to installthe Topology Editor.

Sample properties filesThe location and contents of the sample properties files.

The Silent subdirectory under the directory that contains the deployer.bin file(for example, /opt/IBM/proviso/deployer/proviso/data/Silent), contains thefollowing sample properties files:v Fresh.properties runs the deployer in standard mode.v POC.properties runs the deployer in minimal deployment mode.v topologyEditor.properties runs the Topology Editor installation in silent mode.

The DeployerHow to run the deployer in silent mode.

Running the Deployer in silent modeHow to use the Fresh.properties file to run the deployer.

About this task

Use the Fresh.properties file to run the deployer in standard mode, or thePOC.properties file to run the deployer in minimal deployment mode.

For example, to perform a silent fresh installation:

Procedure1. Log in as root.2. Log in to the machine on which you want to run the silent installation.3. In a text editor, open the Fresh.properties file and make the following edits:

a. Set and verify that the Oracle client path is correct.b. Set the DownloadTopology flag to True (1) or False (0).c. If you set DownloadTopology flag to False, set the TopologyFilePath to the

location of your topology.xml file.d. If you are running the deployer application on the same system where the

Topology Editor is installed, set the Primary flag to true.e. Set and verify that the Database Access Information is correct.f. Set and verify the PACKAGE_PATH variable for the relevant system:

On Solaris systems:<DIST_DIR>/proviso/SOLARIS

On AIX systems:<DIST_DIR>/proviso/AIX

On Linux systems:<DIST_DIR>/proviso/RHEL


<DIST_DIR> is the directory on the hard drive where you copied the contentsof the Tivoli Netcool Performance Manager distribution in “Downloadingthe Tivoli Netcool Performance Manager distribution to disk” on page 26.Your edited file will look similar to the following:

#Oracle client JDBC driver path#------------------------------OracleClient=/opt/oracle/product/10.2.0.4.0/jdbc/lib#Download Topology from Proviso database# 1 is true# 0 is false#-------------DownloadTopology=0#Primary# Specify if the configuration has to be updated# Specify true if running the deployer on the same# system where the Topology Editor is installed.# true or false#-------------Primary=false#Topology file# If DownloadTopology=1 this parameter is ignored#-------------TopologyFilePath=/tmp/ProvisoConsumer/Topology.xml#Database access information#---------------------------OracleServerHost=lab238053OracleServerPort=1521OracleSID=PVOracleAdminUser=PV_INSTALLOracleAdminPassword=PV#Check Prerequisites Flag(true/false)#Use true only for first time install#-------------------------------------CHECK_PREREQ=true# Tivoli Netcool Performance Manager installation packages path#---------------------------PACKAGE_PATH=/cdrom/SOLARIS#Silver Stream installation packages path#-------------------------------------SS_BUNDLE=/cdrom/exteNd40k

g. Write and quit the file.4. Change to the /opt/IBM/proviso/deployer directory.5. Run the following command:

./deployer.bin -i silent -f propertyFileWithPath

For example:./deployer.bin -i silent -f /opt/IBM/proviso/deployer/proviso/data/Silent/Fresh.properties

Confirming the status of a silent installHow to verify a successful installation from the log status messages.

To verify a successful installation, you must analyze the /tmp/ProvisoConsumer/log.txt file:

For a successful silent install, /tmp/ProvisoConsumer/log.txt will have thefollowing as the second last line:ConsumerSilent null CMW3019I Silent installation completed

If the installation fails:


if the install has not worked and one of the steps fails you will see one of thefollowing errors:v Product images not found during silent installation

v An installation step has failed during silent installation

v Silent Installatoin Suspended because a reboot is needed

v Engine main loop internal error

RestrictionsDeployer restrictions.

Note the following restrictions:v The silent deployer does not support remote installations. You must manually

invoke the script on each machine.v Silent resume is not supported. If you need to resume a partial silent installation,

use the -Daction=resume option to complete the installation using graphicalmode (the steps table). The step that originally failed might have been in themiddle of a step sequence that cannot be re-created by a subsequent -i silentinvocation.

The Topology EditorYou can also install the Topology Editor in silent mode.

About this task

The Topology Editor is installed with the installer named installer.bin, locatedin:

On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/topologyEditor/Disk1/InstData/VM

On AIX systems:# cd <DIST_DIR>/proviso/AIX/Install/topologyEditor/Disk1/InstData/VM

On Linux systems:# cd <DIST_DIR>/proviso/RHEL/Install/topologyEditor/Disk1/InstData/VM

<DIST_DIR> is the directory on the hard drive where you copied the contents of theTivoli Netcool Performance Manager distribution in “Downloading the TivoliNetcool Performance Manager distribution to disk” on page 26.

To install the Topology Editor in silent mode:

Procedure1. Log in as root to the server on which you want to run the silent installation.2. Change to the directory that contains the deployer.bin file (for example,

/opt/IBM/proviso/deployer), then change to the /proviso/data/Silentsubdirectory.

3. Using a text editor, open the topologyEditor.properties file and make thefollowing edits:a. Set and verify that the Oracle client path is correct.b. Set the DownloadTopology flag to True (1) or False (0).

Appendix G. Using silent mode 181

c. If you set DownloadTopology flag to False, set the TopologyFilePath to thelocation of your topology.xml file.

d. Set and verify that the Database Access Information is correct.e. Set and verify the PACKAGE_PATH variable.f. Write and quit the file.

4. Run the following command:./installer.bin -i silent -f ..../silent/topologyEditor.properties


Appendix H. Installing an interim fix

This appendix describes how to install an interim fix (or patch) release of TivoliNetcool Performance 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 14).4. Start the patch deployer using one of the following methods:

From the launchpad:a. Click the Start Tivoli Tivoli Netcool Performance Manager Maintenance

Deployer option in the list of tasks.b. Click the Start Tivoli 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 Oracle

JDBC driver (/opt/oracle/product/version/jdbc/lib), or click Choose tonavigate 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:v Database hostname - Enter the name of the database host.v Port - Specifies the port number used for communication with the database.

The default value is 1521.v Database user - Specifies the username used to access the database. The

default value is PV_INSTALL.

v Database Password - Enter the password for the database user account (forexample, PV).

v SID - Specifies the SID for the 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 H. Installing an interim fix 185

Appendix I. Error codes and log files

This appendix lists the Tivoli Netcool Performance Manager error messages andlog files.

See Appendix J, “Troubleshooting,” on page 207 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

DataView Messages

GYMCI5000E A system command failed. Astandard UNIX systemcommand failed. Thesecommands are used forstandard system operations,such as creating directories,changing file permissions,and removing files.

See the installation log formore details.

GYMCI5002E The operating system is notat the prerequisite patchlevel. Some requiredoperating system patches arenot installed.

See the installation log fordetails. Install the requiredpatches, then try theinstallation again.

GYMCI5003E The Oracle configuration file,tnsnames.ora, does notinclude an entry forSilverMaster.

Add an entry forSilverMaster to thetnsnames.ora file, then trythe installation again.

GYMCI5004E The Oracle configuration file,tnsnames.ora, was not found.The tnsnames.ora file mustbe created and stored in the$TNS_ADMIN directory.

Ensure that the file exists inthe correct location.

GYMCI5005E Unable to connect to theOracle database. It is possiblethat a specified connectionparameter is incorrect, or theOracle server might not beavailable.

See the installation log formore details. Ensure that theconnection parameters youare using are correct and thatthe Oracle server is up andrunning.



GYMCI5006E An error occurred whilerunning theDVOptimizerToRule.sqlscript to initialize thedatabase. It is possible thatthe Oracle database andlistener are not running.

See the installation log formore details. Check that thedatabase and listener arerunning.

GYMCI5007E An error occurred whiletrying to remove entries for aresource from a databasetable. It is possible that theOracle database and listenerare not running.


GYMCI5008E An error occurred whiletrying to remove versioninformation from a databasetable. It is possible that theOracle database and listenerare not running.


GYMCI5009E An error occurred whilereading the configurationfile. The name of a parameteror the format of the file isincorrect.

Contact IBM SoftwareSupport.

GYMCI5010E The file system does nothave sufficient free space tocomplete the installation.

See the installation log formore details. Ensure that youhave sufficient space on thefile system before retryingthe installation.

GYMCI5011E The DataView license file ismissing. The license file wasnot found, but this fileshould not be required. Theinstallation log will containmore details of the error.


GYMCI5012E A configuration file ordirectory is missing.


GYMCI5013E An error occurred whilecreating a configuration file.The file could not be created.The installer failed to createone of the requiredconfiguration files.


GYMCI5014E An error occurred whileupdating a configuration file.The file could not bemodified. The installer failedto make a requiredmodification to one of theconfiguration files.


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.

DataChannel Messages

GYMCI5301E The database channelinstallation failed. See theinstallation log for details.

See the fileroot_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.


Appendix I. Error codes and log files 189


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.


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 the check_osscript is not correct. Thespecified component doesnot exist.The syntax is: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 for alist 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 for alist 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 Solaris semaphore andshared memory check failed.The sysdef command wasused to check 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 the bos.adt.libpackage in the COMMITTEDstate. The package might notbe installed. 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. If it doesnot, create it.

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 will beidentified in the 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 file forerrors. Check for walkbackor 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 file forerrors. Check for walkbackor 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-installlog in /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-installlog in /var/tmp for moredetails on the errorcondition.

GYMCI7520E The Web Application serveris not running or took toolong to start up.

Start up the Web Applicationserver as documented.

GYMCI7597E The MIB-II Technology Packjar file was not found in thespecified directory.

Add the MIB2 TechnologyPack jar 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.

Installer Action Messages and IA Flow Messages

GYMCI9998E Unable to find a message forthe key. The message wasnot retrieved from themessage catalog.


GYMCI9999E An unknown error occurredfor the component namewith the error code 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 command.


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.

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.




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.

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.


Error Code Description

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” on page 206v “Eclipse log file” on page 206v “Trace log file” on page 206

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 J. 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 notautomatically become the focuswindow after launching from it fromthe Topology Editor.

Cause: In some cases (for example, when you export the display on a VNCsession on Linux systems), the deployer window does not get the focus.

User action: Click on the deployer window or move other windows to makethe deployer window the focus window.

When the user tries to launch theFirefox browser an error is displayedregarding the Cairo 1.4.10 package:

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 working properlybefore actually creating the Tivoli Netcool Performance Manager database. Ifthe step fails: 1. Complete the necessary manual steps (see “Configure theOracle listener” on page 46). 2. Change the status of the step to Ready. 3.Resume the installation. The step should complete successfully.

An installation step hangs. Cause: There are many possible causes.

User action:

1. Make sure the installation step is really in a hung state. For example, theTivoli Netcool Performance Manager database-related steps might takemore 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 itsfather. 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 to Error.

5. If you can determine the cause of the hang, fix the problem and resumethe installation. Otherwise, collect the log files and contact IBM forsupport.

The deployer hangs when displayingthe Preview page. (This step normallytakes only a 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 file systems are workingproperly. When the problem has been corrected, restart the deployer.


Problem Solution

There is a problem with remotecommand execution.

Cause: The deployer uses either RSH or OpenSSH to perform remotecommand execution. You must configure OpenSSH to make this connectionpossible.

User action: After configuring OpenSSH, run the test program provided indeployer_root/proviso/data/Utils/testremote.sh to test your configuration,where deployer_root is the root directory for the deployer. For example:

/export/home/pvuser/443/SOLARIS/Install/ SOL9/deployer

Installation messages report success,but might include messages similar tothe following: Fatal Error]:4:1: Aninvalid XML character (Unicode:0x1b) was found in the elementcontent of the document.

This is screen noise and can safely be ignored.

When you click the Done button tocomplete a fresh installation, thedeployer displays database accesserror messages.

Cause: You stopped a fresh installation before the installing and configuringthe Tivoli Netcool Performance Manager database.

User action:If the Tivoli Netcool Performance Manager database has notbeen installed, complete the installation using the -Daction=resume option(see “Resuming a partially successful first-time installation” on page 87). Ifthe database has been installed, there is another problem. Contact IBMSoftware Support.

Data does not appear in real-timereports, and right-clicking on areal-time report does not display theoption menu. This problem can occurwith a silent installation or a minimaldeployment installation on a Solarissystem.

Cause: When it starts, the channel manager (CMGR) places information inthe database that is needed for real-time reports to start correctly. Duringinstallation, a cron job is created that starts CMGR. A silent installationmight run fast enough that the cron job does not run before DataView isstarted. In this case, CMGR does not add the required information to thedatabase, and real-time reports do not start up correctly.

User action:

1. Make sure that the CMGR process is running (see “Managementprograms and watchdog scripts” on page 142 and “Starting theDataChannel management programs” on page 143).

2. Restart DataView.

During Tivoli Integrated Portal install,the Deployment Engine failed to findpre-installed Tivoli Integrated Portal.

User action:

1. Log in as root.

2. Enter the following commands to restart the Deployment Engine:

# cd /usr/ibm/common/acsi/bin# ./acsisrv.sh -start

3. Check DE is running with the following command

# ./listIU.sh

This will list all IUs in the system.


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.

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 it's beeninstalled.

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,“DataChannels,” on page 141.

Appendix J. Troubleshooting 209

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.

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 databaseHow 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 9.2.0.8.0 - Production on <Current Date>

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:Oracle9i Enterprise Edition Release 9.2.0.8.0 - ProductionWith the Partitioning optionJServer Release 9.2.0.8.0 - Production

SQL>

4. Type exit at the SQL> prompt.

Appendix J. Troubleshooting 211

Testing external procedure call accessIn 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 K. Migrating DataView content and users

When modifying your system to use Tivoli Integrated Portal or changing yourTivoli Integrated Portal, you must migrate existing DataView content and users.

Moving DataView content between Tivoli Integrated Portal serversYou can use the synchronize command to move custom DataView content betweenTivoli Integrated Portal servers.

You can copy your custom DataView content, such as JSP pages, CSS and images,from a remote Tivoli Integrated Portal server to a local Tivoli Integrated Portalserver. All remote content is copied to the local content directory at<tip_location>/products/tnpm/dataview/legacy/content.

The synchronize commandCopies custom DataView content, such as JSP pages, CSS and images, from aremote Tivoli Integrated Portal to a local Tivoli Integrated Portal. All remotecontent is copied to the local content directory at <tip_location>/products/tnpm/dataview/legacy/content.

Location

<tip_location>/products/tnpm/dataview/legacy/bin

Where <tip_location> is the Tivoli Integrated Portal installation directory, by default/opt/IBM/tivoli/tipv2.

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 -tipuser <tip_username -tippassword <tip_password> -sourceuser<source_username> -sourcepassword <source_password> -sourceurl <source_url>[-pattern <pattern>]

Parameters

<tip_username>A Tivoli Integrated Portal user name for the local Tivoli Integrated Portal.

<tip_password>The Tivoli Integrated Portal user password for the local Tivoli IntegratedPortal.

<source_username>A Tivoli Integrated Portal user name for the remote Tivoli Integrated Portal.


<source_password>The Tivoli Integrated Portal user password for the remote Tivoli IntegratedPortal.

<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 Tivoli Integrated Portal to a local Tivoli Integrated Portal:

synchronize.sh -tipuser <tip_username> -tippassword <tip_password>-sourceuser <source_username> -sourcepassword <source_password>https://server.ibm.com:16711:PV *.jsp

Migrating SilverStream content to the Tivoli Integrated PortalUse the migrate command to move SilverStream content, users, or both to theTivoli Integrated Portal.

The migrate command connects remotely to a SilverStream server and migrates allthe specified data to a Tivoli Integrated Portal installation.

The migrate command requires:

Source access credentialsSilverStream administrator user name and password

Destination access credentialsTivoli Integrated Portal administrator user name and password

You can run the migrate command from Solaris, AIX®, or Linux computers. If thereare multiple SilverMasters, you can run the migrate tool and create multiple newDataView servers from a single SilverStream computer. Refer to “The migratecommand” on page 216 for more information.

SilverStream page conversionThe migrate command performs the following processing when convertingSilverStream pages to JavaServer Pages (JSPs).

Each SilverStream page is made up of three parts:v HTML (including HTML markup, inline CSS, JavaScript, and images)v Java codev SilverStream page controls

The migrate command does not modify inline CSS, JavaScript, or images. This typeof page content is extracted from the SilverStream server and imported into TivoliIntegrated Portal unchanged.


The HTML and Java code sections are read from the page, processed andcombined to generate a new JSP.

HTML

When processing HTML sections, SilverStream page controls are replaced withcustom DataView JSP tags. For example, consider the following HTML from aSilverStream page:<div><h1><AGCONTROL name="stylesheetNameLabel"></h1></div>

That HTML is converted to the following JSP. The className attribute in the newJSP tag comes from the SilverStream page control metadata section of theSilverStream page.<<div><h1><proviso:pageControl className="com.sssw.shr.page.AgpLabel"name="stylesheetNameLabel"></h1></div>

Java code

When processing Java code sections, the code is embedded into the JSP directlyusing the standard JSP statement tag. For example, consider the following Javacode from a SilverStream page:<class SomePage extends AgpPage {

private AgpLabel label;public SomePage() {this.label.setText("foo")}}

That Java code is converted to the following JSP:<%!//class SomePage extends AgpPage {private AgpLabel label;public SomePage() {this.label.setText("foo")}}%>

All JSP fragments generated from the HTML and Java code conversion arecombined into one JSP page. When executed, this JSP page generates the sameHTML as the SilverStream page.

The resulting JSP can only be run by using the SilverStream emulation layer. If youare using unsupported SilverStream page controls (AgpTabPane,AgpImageHotSpot and AgpButtonRadio) then the resulting JSP will not workcorrectly.

Appendix K. Migrating DataView content and users 215

The migrate commandMigrates all custom DataView content, or DataView users, from the SilverStreamserver on a previous DataView installation.

The migrate command connects remotely to a SilverStream server and migrates allthe specified data to a Tivoli Integrated Portal installation. Ensure that both theSilverStream and Tivoli Integrated Portal servers are running before running thecommand.

Location

<tip_location>/products/tnpm/dataview/legacy/bin

Where <tip_location> is the Tivoli Integrated Portal installation directory, by default/opt/IBM/tivoli/tipv2.

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

migrate.sh -tipuser <tip_username> -tippassword <tip_password> -ssurl<silverstream_URL> -ssuser <silverstream_username> -sspassword<silverstream_password> -target <content|users|all> [-import ] [-verbose ]

Parameters

<tip_username>A Tivoli Integrated Portal user name for the local Tivoli Integrated Portal.

<tip_password>The Tivoli Integrated Portal user password for the local Tivoli IntegratedPortal.

<silverstream_URL>The URL of the DataView SilverStream server.

<silverstream_username>The SilverStream administrator user name.

<silverstream_password>The SilverStream administrator password.

<content|users|all>Indicates the type of data to be migrated:

content

Migrates all SilverStream content. All content is copied to the contentdirectory in the Tivoli Integrated Portal installation<tip_location>/products/tnpm/dataview/legacy/content.

Depending on the type of content, it is copied to the followingdirectories:v <tip_location>/products/tnpm/dataview/legacy/content/

SilverStream/Pages


v <tip_location>/products/tnpm/dataview/legacy/content/SilverStream/Objectstore/Images

v <tip_location>/products/tnpm/dataview/legacy/content/SilverStream/Objectstore/General

users

Migrates all SilverStream users. Each user in SilverStream is either anadministrator or user. In the Tivoli Integrated Portal, the administratorrole is mapped to tnpmAdministrator, and the user role is mapped totnpmUser. The migration tool creates two user groups,tnpmAdministrators and tnpmUsers, that contain all the users withthe corresponding roles.

Password information is not migrated. Under Tivoli Integrated Portal,the password is set to be the same as the user name. For example, theSilverStream user pvuser with password pv becomes user pvuser withpassword pvuser when migrated to the Tivoli Integrated Portal.

all Exports all SilverStream content and users.

Optional parameters

-importIndicates data should be imported into the Tivoli Integrated Portal.

-verboseIndicates additional migration messages should be displayed.

Example

Run the following command as user root. Assuming a default installation, thiscommand copies all SilverStream content and users in the SilverStream serversilverstreamserver to the /opt/IBM/tivoli/tipv2/products/tnpm/dataview/legacy/content directory in a Tivoli Integrated Portal installation:

migrate.sh -tipuser <tip_username> -tippassword <tip_password>http://silverstreamserver:8080/PV -ssuser <silverstream_username>-sspassword <silverstream_password> all

Appendix K. Migrating DataView content and users 217

Notices

This information was developed for products and services offered in the U.S.A.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 give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

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 states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not 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 Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply 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 Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

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.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

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.

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 the names and addresses used by an actual businessenterprise is entirely coincidental.

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. 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 IBM‘s application programming interfaces.


If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

Notices 221

Trademarks

IBM, 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 http://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.

Cell Broadband Engine and Cell/B.E. are trademarks of Sony ComputerEntertainment, Inc., in the United States, other countries, or both and is used underlicense therefrom.

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.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries,or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.

For trademark attribution, visit the IBM Terms of Use Web site(http://www.ibm.com/legal/us/).


http://www.ibm.com/legal/copytrade.shtml

��

Printed in USA

TNPM 1.3.1 Install Guide Wireline Component

Documents

Transcript of TNPM 1.3.1 Install Guide Wireline Component