NetcoolProviso InstallationGuide 443

Tivoli Netcool®/Proviso® Version 4.4.
3 IBM
Document Revision Document Revision R2E3
Installation Guide
Notices
This information was developed for products and incorporated in new editions of the publication. IBM
services offered in the U.S.A. IBM® may not offer the may make improvements and/or changes in the
products, services, or features discussed in this product(s) and/or the program(s) described in this
document in other countries. Consult your local IBM publication at any time without notice.
representative for information about the products and Any references in this information to non-IBM Web
services currently available in your area. Any reference to sites are provided for convenience only and do not in
an IBM product, program, or service is not intended to any manner serve as an endorsement of those Web sites.
state or imply that only that IBM product, program, or The materials at those Web sites are not part of the
service may be used. Any functionally equivalent materials for this IBM product and use of those Web
product, program, or service that does not infringe any sites is at your own risk.
IBM intellectual property right may be used instead.
However, it is the user’s responsibility to evaluate and IBM may use or distribute any of the information you
verify the operation of any non-IBM product, program, supply in any way it believes appropriate without
or service. incurring any obligation to you.
IBM may have patents or pending patent applications Licensees of this program who wish to have information
covering subject matter described in this document. The about it for the purpose of enabling: (i) the exchange of
furnishing of this document does not give you any information between independently created programs
license to these patents. You can send license inquiries, and other programs (including this one) and (ii) the
in writing, to: mutual use of the information which has been
exchanged, should contact:
IBM Director of Licensing
IBM Corporation IBM Corporation
North Castle Drive 2Z4A/101
Armonk, NY 10504-1785 U.S.A. 11400 Burnet Road
Austin, TX 78758
For license inquiries regarding double-byte (DBCS) U.S.A.
information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, Such information may be available, subject to
to: appropriate terms and conditions, including in some
cases payment of a fee.
IBM World Trade Asia Corporation
Licensing The licensed program described in this document and all
2-31 Roppongi 3-chome, Minato-ku licensed material available for it are provided by IBM
Tokyo 106, Japan under terms of the IBM Customer Agreement, IBM
International Program License Agreement or any
The following paragraph does not apply to the equivalent agreement between us.
United Kingdom or any other country where such
provisions are inconsistent with local law: Any performance data contained herein was determined
in a controlled environment. Therefore, the results
INTERNATIONAL BUSINESS MACHINES
obtained in other operating environments may vary
CORPORATION PROVIDES THIS PUBLICATION
significantly. Some measurements may have been made
"AS IS" WITHOUT WARRANTY OF ANY KIND,
on development-level systems and there is no guarantee
EITHER EXPRESS OR IMPLIED, INCLUDING,
that these measurements will be the same on generally
BUT NOT LIMITED TO, THE IMPLIED
available systems. Furthermore, some measurement may
WARRANTIES OF NON-INFRINGEMENT,
have been estimated through extrapolation. Actual
MERCHANTABILITY OR FITNESS FOR A
results may vary. Users of this document should verify
PARTICULAR PURPOSE.
the applicable data for their specific environment.
Some states do not allow disclaimer of express or Information concerning non-IBM products was
implied warranties in certain transactions, therefore, this obtained from the suppliers of those products, their
statement might not apply to you. published announcements or other publicly available
This information could include technical inaccuracies or sources. IBM has not tested those products and cannot
typographical errors. Changes are periodically made to confirm the accuracy of performance, compatibility or
the information herein; these changes will be any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products techniques on various operating systems. You may copy,
should be addressed to the suppliers of those products. modify, and distribute these sample programs in any
form without payment to IBM, for the purposes of
All statements regarding IBM’s future direction or intent
developing, using, marketing or distributing application
are subject to change or withdrawal without notice, and
programs conforming to the application programming
represent goals and objectives only.
interface for the operating system for which the sample
This information is for planning purposes only. The programs are written. These examples have not been
information herein is subject to change before the thoroughly tested under all conditions. IBM, therefore,
products described become available. cannot guarantee or imply reliability, serviceability, or
This information contains examples of data and reports function of these programs. You may copy, modify, and
used in daily business operations. To illustrate them as distribute these sample programs in any form without
completely as possible, the examples include the names payment to IBM for the purposes of developing, using,
of individuals, companies, brands, and products. All of marketing, or distributing application programs
these names are fictitious and any similarity to the names conforming to IBM's application programming
and addresses used by an actual business enterprise is interfaces.
entirely coincidental. If you are viewing this information in softcopy form, the
COPYRIGHT LICENSE: photographs and color illustrations might not appear.
This information contains sample application programs

in source language, which illustrate programming
Trademarks
AIX®, DB2®, developerWorks®, eServer, i5/OS®,
IBM®, the IBM logo®, IBMLink, iSeries®, Lotus®,
Netcool®, Netcool/Proviso®, OMEGAMON®, Java™ and all Java-based
Passport Advantage®, pSeries®, Rational®, Redbooks®, trademarks and logos are
OS/390®, OS/400®, Tivoli®, the Tivoli logo®, Tivoli trademarks or registered
Enterprise Console®, WebSphere®, and zSeries® are trademarks of Sun Microsystems,
trademarks or registered trademarks of International Inc. in the United States, other
Business Machines Corporation in the United States, countries, or both.
other countries, or both.
UNIX® is a registered trademark of The Open Group in
Intel® is a registered trademark of Intel Corporation or the United States and other countries.
its subsidiaries in the United States, other countries, or
both. Other company, product, and service names may be
trademarks or service marks of others.
Linux is a trademark of Linus Torvalds in the United
States, other countries, or both.
Microsoft® and Windows® are registered trademarks of Copyright International Business Machines
Microsoft Corporation in the United States, other Corporation 2008. All rights reserved.
countries, or both. US Government Users Restricted Rights — Use,
duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Netcool/Proviso Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring Your Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The Graphical Installation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
The Launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
The Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Topology Editor Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
The topology.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Topology Editor Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Topology Editor Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
The Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Primary Versus Secondary Deployers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Node Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Step Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Step Status Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Resuming a Partially Successful First-Time Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Installation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Pre-Installation Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting Up a Remote X Window Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Specifying the DISPLAY Environment Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Disabling Access Control to the Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Changing the Ethernet Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Solaris Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Setting the Resource Limits (AIX Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Netcool/Proviso Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Chapter 2: Installing and Configuring the Prerequisite Software . . . . . . . . . . . . . . . . . . . . . 46
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Netcool/Proviso Installation Guide, Version Version 4.4.3 4

Contents
Specifying a Basename for DB_USER_ROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Specifying Oracle Login Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Adding the pvuser Login Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Adding pvuser to a Standalone Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Multiple Computer Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Adding pvuser on an NIS-Managed Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Assumed Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Installing the Oracle Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Step 1: Ensure that the Oracle User is not in NIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Step 2: Download the Oracle Distribution and Patch to Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Step 3: Download the Netcool/Proviso Distribution to Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Step 4: Verify the Required Operating System Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
On Solaris Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
On AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Step 5: Set the System Parameters (Solaris Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Step 6: Run the Oracle Server Configuration Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Structure Created by the configure_ora Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Step 7: Set a Password for the Oracle Login Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Step 8: Run the Pre-Installation Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Step 9: Verify PATH and Environment for the Oracle Login Name. . . . . . . . . . . . . . . . . . . . . . . 60
Step 10: Install Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Using the Menu-Based Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Using Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Step 11: Run the root.sh Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Step 12: Install Oracle Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Additional AIX Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Step 13: Set the ORACLE_SID Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Step 14: Set Automatic Startup of the Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Step 15: Configure the Oracle Listener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Step 16: Configure the Oracle Net Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Installing the Oracle Client (Patch Version 9.2.0.8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Pre-Installation Tasks for Linux Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Step 2: Download the Oracle Distribution and Patch to Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Step 3: Run the Oracle Client Configuration Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Step 5: Run the Pre-Installation Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Step 6: Verify the PATH and Environment for the Oracle Login Name . . . . . . . . . . . . . . . . . . . 79
Step 7: Install the Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Step 8: Run the root.sh Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Step 9: Install Oracle Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Step 10: Configure the Oracle Net Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
5 Netcool/Proviso Installation Guide, Version Version 4.4.3

Contents
Create the sqlnet.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Create the tnsnames.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Test the Oracle Net Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Installing the Oracle Client (Patch Version 9.2.0.6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Pre-Installation Tasks for Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Step 2: Download the Oracle Distribution and Patch to Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Step 3: Run the Oracle Client Configuration Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Step 5: Run the Pre-Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Step 6: Verify the PATH and Environment for the Oracle Login Name . . . . . . . . . . . . . . . . . . . 91
Step 7: Install the Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Step 8: Run the root.sh Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Step 9: Install Oracle Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Step 10: Configure the Oracle Net Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Create the sqlnet.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Create the tnsnames.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Test the Oracle Net Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Chapter 3: Installing Netcool/Proviso in a Distributed Environment . . . . . . . . . . . . . . . . . 98
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Starting the Launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Installing the Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Starting the Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Creating a New Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Adding and Configuring the Netcool/Proviso Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Step 1: Add the Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Step 2: Add a Database Configurations Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Step 3: Add a DataMart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Event Notification Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Step 4: Add a Discovery Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Adding Multiple Discovery Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Step 5: Add a DataView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Step 6: Add the DataChannel Administrative Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Step 7: Add a DataChannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Step 8: Add a Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Collector Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Creating an SNMP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Saving the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Contents
Opening an Existing Topology File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Starting the Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Primary Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Secondary Deployers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Deploying the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Chapter 4: Installing Netcool/Proviso as a Minimal Deployment . . . . . . . . . . . . . . . . . . . . 116
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Special Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Installing on Solaris Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Step 1: Download the MIB-II Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Step 2: Start the Launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Step 3: Start the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Installing on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Step 1: Download the MIB-II Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Step 2: Start the Launchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Step 3: Install the Components on the AIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Step 4: Install the Components on the Solaris System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Step 5: Complete the Installation on the AIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
The Post-Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Chapter 5: Installing Technology Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Installing the Starter Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Starter Kit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Where to Obtain Starter Kit Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Backing Up Inventory Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Pre-Installation Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Installing Technology Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Adding UBA Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Adding a UBA Collector for UBA Packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Adding UBA Collectors for the Nortel CS2000 Technology Pack . . . . . . . . . . . . . . . . . . . . . . . 135
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Contents
Chapter 6: Modifying the Current Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Opening a Deployed Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Adding a New Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Example: Performing an Incremental Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Changing Configuration Parameters of Existing Netcool/Proviso Components. . . . . . . . . . . . . . . 143
Moving Components to a Different Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Moving a Deployed Collector to a Different Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Moving a Deployed SNMP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Moving a Deployed SNMP Collector to or from a HAM Environment . . . . . . . . . . . . . . . 146
Moving a Deployed UBA Bulk Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Chapter 7:Using the High Availability Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
HAM Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
The Parts of a Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
HAM Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Types of Spare Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Types of HAM Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Example HAM Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
1 + 1, Fixed Spare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
2 + 1, Fixed Spare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
2 + 1, Both Primaries are Floating Spares. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
3+ 2, Fixed Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
3+ 2, All Primaries are Floating Spares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
How the SNMP Collector Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
How Failover Works With the HAM and the SNMP Collector. . . . . . . . . . . . . . . . . . . . . . . . . . 161
Creating a HAM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Topology Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Step 1: Create the HAM and a HAM Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Step 2: Add the Designated Spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Step 3: Add the Managed Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Step 4: Define the Resource Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Step 5: Save and Start the HAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Creating an Additional HAM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Modifying a HAM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Contents
Removing HAM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Stopping and Restarting Modified Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Viewing the Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Show Collector Process... Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Show Managed Definition... Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Chapter 8: Uninstalling Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Removing a Component from the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Restrictions and Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Removing a Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Uninstalling Netcool/Proviso . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Restrictions and Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Performing the Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Uninstalling the Topology Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Residual Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Appendix A: Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Co-Location Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Appendix B: DataChannels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
DataChannel Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Data Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Management Programs and Watchdog Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
DataChannel Application Program Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Starting the DataChannel Management Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Starting the DataLoad SNMP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
DataChannel Management Components in a Distributed Configuration . . . . . . . . . . . . . . . . . . . . . 186
Manually Starting the Channel Manager Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
SNMP Traps from Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Appendix C: Aggregation Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Configuring Aggregation Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Installing Aggregation Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Step 1: Start the Netcool/Proviso Setup Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Step 2: Set Aggregation Set Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Step 3: Edit Aggregation Set Parameters File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Contents
Linking DataView Groups to Timezones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Appendix D: Installing Multiple DataView Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
DataView Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
About a Distributed Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Choosing a Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Installing a DataView Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Uploading Style Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Configuring the DataView Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Adding Servers to a Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Configuring the Cache Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Restarting Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Verifying Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Deleting Servers from Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Multi-SilverMaster Database Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Basic Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Updating the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Installing SilverStream on a Secondary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Installing DataView on a Secondary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Re-Running the DataView Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Steps to Install Netcool/Proviso DataView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Test the DataView Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Confirming the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Primary DataView Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Secondary DataView Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
An Incorrectly Configured Secondary DataView Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Uploading Style Sheets onto Secondary Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Removing the Database Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Combined Cluster and Multi-SilverMaster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
SilverStream Installation on a Secondary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
HTTP Port Number and SSL Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Steps to Install SilverStream Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Step 1: Install Oracle Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Add the SilverMaster TNS Service Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Test the SilverMaster TNS Service Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Step 2: Pre-Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Contents
Step 3: Create Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Step 4: Run the SilverStream Install Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Step 5: Test the SilverStream Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Step 6: Configure the SilverStream Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Additional SilverStream Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Step 7: Stop the SilverStream Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Appendix E: Deployer CLI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Using the -DTarget Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Appendix F: Using Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Sample Properties Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

The Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Running the Deployer in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
The Topology Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Appendix G: Installing an Interim Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Installation Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Behavior and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Installing a Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Appendix H: Error Codes and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Deployer Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Topology Editor Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
InstallAnywhere Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
COI Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Deployer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Eclipse Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Trace Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Appendix I: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Deployment Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Contents
Saving Installation Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Netcool/Proviso Component Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Topology Editor Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Telnet Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Java Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Testing Connectivity to the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Testing External Procedure Call Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Contents

Preface
The purpose of this guide is to help you install the Netcool/Proviso product suite and the Oracle database
management system. This guide assumes you are a network administrator or operations specialist who has
knowledge of network management and installing applications on operating systems.
Audience
The audience for this manual is the network administrator or operations specialist responsible for installing the
Netcool/Proviso product suite on an enterprise network. To install Netcool/Proviso successfully, you should
have a thorough understanding of the following subjects:
• Basic principles of TCP/IP networks and network management
• SNMP concepts
• Administration of the Solaris or AIX operating environment
• Administration of the Oracle database management system
• Netcool/Proviso
Organization
This guide is organized as follows:
Section Page
Chapter 1, Introduction 18
Chapter 2, Installing and Configuring the Prerequisite Software 46
Chapter 3, Installing Netcool/Proviso in a Distributed Environment 98
Chapter 4, Installing Netcool/Proviso as a Minimal Deployment 116
Chapter 5, Installing Technology Packs 126
Chapter 6, Modifying the Current Deployment 140
Chapter 8, Uninstalling Components 170
Appendix A, Deployment Considerations 176
Appendix B, DataChannels 182
Appendix C, Aggregation Sets 188
Appendix D, Installing Multiple DataView Servers 200
Appendix E, Deployer CLI Options 234

Preface
Section Page
Appendix F, Using Silent Mode 238
Appendix G, Installing an Interim Fix 242
Appendix H, Error Codes and Log Files 246
Appendix I, Troubleshooting 264
The Default UNIX Shell

The installation scripts and procedures in this manual generally presume, but do not require, the use of the Korn
or Bash shells, and only Korn shell syntax is shown in examples. If you are a user of the C shell or Tcsh, make
the necessary adjustments in the commands shown as examples throughout this manual.
This guide uses the following shell prompts in the examples:
• # (pound sign) indicates commands you perform when logged in as root.
• $ (dollar sign) indicates commands you perform when logged in as oracle or pvuser.
• SQL> indicates commands you perform at the SQL*Plus prompt.
The Netcool/Proviso Product Suite

Netcool/Proviso is made up of the following components:
• Netcool/Proviso DataMart is a set of management, configuration and troubleshooting GUIs that the
Netcool/Proviso System Administrator uses to define policies and configuration, as well as verify and
troubleshoot operations.
• Netcool/Proviso DataLoad provides flexible, distributed data collection and data import of SNMP and
non-SNMP data to a centralized database.
• Netcool/Proviso DataChannel aggregates the data collected through Netcool/Proviso DataLoad for use
by the Netcool/Proviso DataView reporting functions. It also processes on-line calculations and detects real-
time threshold violations.
• Netcool/Proviso DataView is a reliable application server for on-demand, web-based network reports.
• Netcool/Proviso Technology Packs extend the Netcool/Proviso system with service-ready reports for
network operations, business development, and customer viewing.
The following figure shows the different Netcool/Proviso modules.

Preface
Figure 1: Netcool/Proviso Modules

DataLoad DataChannel DataMart DataView
collects computes provides data produces and
network data. aggregations management manages reports.
and stores data and applications.
in DataMart.
Netcool/Proviso documentations consists of the following:

• release notes
• configuration recommendations
• user guides
• technical notes
• online help
The documentation is available for viewing and downloading on the infocenter at:
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_proviso.doc/welcome.htm

Preface

Chapter 1: Introduction
This chapter provides an overview of the Netcool/Proviso product suite and provides important pre-installation
setup information. In addition, this chapter provides an overview of the installation interface introduced in
Version Version 4.4.3. The topics are as follows:
Topic Page
Netcool/Proviso Architecture 18
Configuring Your Deployment 20
The Graphical Installation Interface 21
Pre-Installation Setup Tasks 41
Netcool/Proviso Distribution 45
Netcool/Proviso Architecture
With the exception of DataView, the Netcool/Proviso components run on:
• SPARC-based servers from Sun Microsystems® that run the Solaris™ operating system
• AIX® servers from IBM® (not DataView)
• Linux® servers (DataLoad SNMP collector only)
Note: DataView is supported on Solaris systems only.
Exact, release-specific requirements, prerequisites, and recommendations for hardware and software are
described in detail in the Netcool/Proviso Configuration Recommendations document.
You can work with Professional Services to plan and size the deployment of Netcool/Proviso components in
your environment.

The following diagram provides a high-level overview of the Netcool/Proviso architecture.
The Netcool/Proviso system components are as follows:

• Netcool/Proviso database — The Netcool/Proviso database is hosted on Oracle.
• Netcool/Proviso DataMart — Netcool/Proviso DataMart is the user and administrative interface to the
Netcool/Proviso database and to other Netcool/Proviso components.
• Netcool/Proviso DataLoad — Netcool/Proviso DataLoad consists of one or more components that
collect network statistical raw data from network devices and from network management systems.
• Netcool/Proviso DataChannel — Netcool/Proviso DataChannel is a collection of components that
collect data from DataLoad collectors, aggregate and process the data, and load the data into the
Netcool/Proviso database. DataChannel components also serve as the escalation point for collected data
that is determined to be over threshold limits.
• Netcool/Proviso DataView — Netcool/Proviso DataView is the Web server hosting and analysis
platform. This platform is used to display Web-based management reports based on network data aggregated
and placed in the Netcool/Proviso database.
• Netcool/Proviso Technology Packs — Each technology pack is a set of components that describes the
format and structure of network statistical data generated by network devices. Each technology pack is
specific for 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.
• SilverStream Application Server — The SilverStream application server provides a database-aware Web
server foundation for the Web-based management reports displayed by Netcool/Proviso DataView. The
SilverStream application server is an essential component of each DataView installation.
Note: The SilverStream application server is now called the exteNd application server. However, this
documentation, the graphical user interface, and in many cases the exteNd software, continue to use both names.
If you are setting up a demonstration or evaluation system, it is possible to install all Netcool/Proviso
components on a single server for Solaris systems, or two servers for AIX systems (one for DataView, and one
for the Netcool/Proviso components).
However, a production Netcool/Proviso system that generates and produces management reports for a real-
world network is likely to be installed on several servers. Netcool/Proviso components can be installed to run on
as few as two or three servers, up to dozens of servers.
Table 1 provides an example of where to install Netcool/Proviso components, using four servers. Use this
example as a guide to help you determine where to install the Netcool/Proviso components in your environment.

Table 1: Netcool/Proviso Components Installed on Four Servers
Server Name Netcool/Proviso Components Hosted Notes
delphi Oracle server Install the Topology Editor and

Netcool/Proviso DataMart primary deployer on this system. For
Netcool/Proviso Discovery Server more information, see The Topology
Editor on page 23.
corinth Oracle client You could install Netcool/Proviso

Netcool/Proviso DataLoad, SNMP collector components remotely on this system.
Netcool/Proviso DataLoad, Bulk Load collector
sparta Oracle client

DataChannel
athens Oracle client In a distributed deployment, you

SilverStream application server would use a secondary deployer on
this system to install DataView. For
Netcool/Proviso DataView
more information, see Primary Versus
Secondary Deployers on page 35.
Configuring Your Deployment

This guide provides instructions for installing Netcool/Proviso components, but not necessarily for configuring
the installed components into a finished system that produces management reports. After going through the steps
in this guide, you will have a set of running Netcool/Proviso components ready to configure into a fully
functional system.
The goal of this guide is to get each component installed and running in its barest form. The running component
does not necessarily have network statistical data flowing into and out of it yet. In particular, at the end of this
installation procedure, there are no or few management reports that can be viewed in DataView.
Configuring installed components into a working system is the subject of other manuals in the Netcool/Proviso
documentation set. Before configuring your deployment, you should be familiar with the information in
Appendix A, Deployment Considerations.

The Graphical Installation Interface

Netcool/Proviso Version Version 4.4.3 provides a graphical installation interface that enables you to easily
configure the infrastructure and then install the Netcool/Proviso components. This graphical interface has the
following components:
• Launchpad — This front-end panel provides a common starting point for installing and configuring
Netcool/Proviso. From this Web page, you can perform operations such as launching the Topology Editor,
running the deployer, and so on.
• Topology Editor — This interface enables you to define the Netcool/Proviso component layout and
configuration and view it in tree form. The Topology Editor offers several different graphical views,
including the Logical, Physical, and Technology Pack views. When you are done creating the installation plan
(the topology), you save it to an XML file.
• Deployer — This wizard presents a series of pages to guide you through each step of the installation. The
deployer runs a series of installation scripts to install the Netcool/Proviso components according to the
topology XML file.
• APInstaller — This installer presents a series of pages to guide you through each step of the technology
pack installation. See Chapter 5, Installing Technology Packs for more information about this installer.
Versions of this software prior to 4.4.3 stored configuration information in files named dc.cfg and dl.cfg.
Information previously stored in these files is now located in the Netcool/Proviso database. You specify these
configuration settings using the Topology Editor. For more information, see Changing Configuration Parameters of
Existing Netcool/Proviso Components on page 143.
Figure 2 shows how the installation interfaces communicate with each other.
Figure 2: Installation Interfaces

As shown in the figure, the launchpad provides a a common starting point for installing and configuring
Netcool/Proviso. You can use it to install and then open the Topology Editor.
When you install Netcool/Proviso in a distributed environment, you must first create the topology file using the
Topology Editor. If you are performing a minimal deployment installation, the deployer uses a predefined
topology file.

The deployer installs the Netcool/Proviso components according to the topology file supplied to it, then saves
the file in the database.
For detailed information about how to use each interface, see the following topics:
• The Launchpad on page 22
• The Topology Editor on page 23
• The Deployer on page 34
For descriptions of the supported installation scenarios, see Installation Scenarios on page 40.
The Launchpad
The launchpad provides an easy-to-use starting point for the different interfaces that perform common
Netcool/Proviso operations. For example, the launchpad provides access to the Topology Editor, the deployer,
and the APInstaller.
You must have a Web browser installed in order to run the launchpad. See the Netcool/Proviso Configuration
Recommendations document for the list of supported browsers.
The launchpad has two sections: the left side of the page lists the available operations and the right side displays
informations, links, and instructions for the selected operation, as shown in Figure 3.
Figure 3: Netcool/Proviso Launchpad

The available operations are as follows:

• Product Information — Provides an overview of Netcool/Proviso, including a link to the Information
Center.
• Prerequisite Information — Lists the Oracle version required for this release.
• Install Topology Editor — Enables you to install or start the Topology Editor. The Topology Editor
enables you to create or modify the Netcool/Proviso topology, which describes the Netcool/Proviso
product layout and configuration. For information about how to use the Topology Editor, see The Topology
Editor on page 23; for procedural instructions on creating a topology, see Chapter 3, Installing Netcool/Proviso in
a Distributed Environment.
• Install Technology Pack — Launches the APInstaller. For detailed information about installing technology
packs, see Chapter 5, Installing Technology Packs.
• Upgrade Preparation — Currently, this functionality is not supported.
• Netcool/Proviso Configuration Update — Launches a tool that enables you to perform configuration
changes to the Netcool/Proviso database.
• Install Tivoli Netcool/Proviso 4.4.3 for Minimal Deployment — Installs a minimal deployment version
of Netcool/Proviso. A minimal deployment installation is used primarily for demonstration or evaluation
purposes. For detailed information, see Chapter 4, Installing Netcool/Proviso as a Minimal Deployment.
• Start Tivoli Netcool/Proviso 4.4.3 Maintenance Deployer — Starts the wizard that enables you to install
a patch release of Netcool/Proviso. For detailed information, see Appendix G, Installing an Interim Fix.
• Start Deployer — Starts a secondary deployer. For information about how to use the deployer, see The
Deployer on page 34; for procedural instructions on installing Netcool/Proviso, see Starting the Deployer on
page 111.
• Exit — Closes the launchpad. Alternatively, click the X in the upper, right-hand corner of the launchpad.
To perform an operation:
• Click an option to display the corresponding information or instructions on the right side of the page.
For information about starting the launchpad, see Starting the Launchpad on page 99.
The Topology Editor

The Topology Editor enables you to graphically set up the Netcool/Proviso infrastructure; the infrastructure is
then saved to an XML file (named topology.xml by default). The deployer uses this XML file as input to install
the Netcool/Proviso components according to the specified structure.
The following sections describe how to use the Topology Editor. The topics are as follows:
• Topology Editor Views on page 24
• The topology.xml File on page 30
• Topology Editor Tools on page 30
• Topology Editor Menus on page 33
For information about installing the Topology Editor, see Installing the Topology Editor on page 100. For information
about starting the Topology Editor, see Starting the Topology Editor on page 101.

Topology Editor Views

The Topology Editor provides a set of views to describe the deployed topology and that enable you to configure
the component properties. Figure 4 shows the layout of the Topology Editor, with no topology defined.
Figure 4: Topology Editor Views

There are three main views:
• Logical View — Displays the logical components of the Netcool/Proviso infrastructure (Database,
DataView, DataMart, DataChannels, and so on) in the form of a tree. For more information, see Logical
View on page 25.
• Physical View — Displays all the hosts that are part of the Netcool/Proviso infrastructure. For more
information, see Physical View on page 26.
• Technology Pack View — Lists the technology packs that can be used to configure DataLoaders. To add
an technology pack to this view, you must first load it. For more information, see Technology Pack View on
page 27.
The Topology Editor provides the following additional views:
• Properties and Advanced Properties views — When you select an object in either the Logical or Physical
view, the basic properties of the object are displayed in the Properties view; any advanced properties are listed
in the second tab. For more information, see Properties and Advanced Properties Views on page 27.
• Problems View — Lists all the errors generated when the Topology Editor validates the defined topology
(such as missing parameters). For more information, see Problems View on page 29.

Logical View
The Logical view of the Topology Editor displays the logical components using a tree structure similar to the
following:
The top of the tree is the Netcool/Proviso Topology node, which corresponds to the XML file created by the
Topology Editor. Only one topology can be handled during a Topology Editor session. This tree is created
automatically when you create a new topology (see Creating a New Topology on page 102).

Physical View
The Physical view displays a list of defined hosts; under each host, the view shows all the Netcool/Proviso
components installed on that host. The following figure shows the Physical View with a single host.
When you add a new host, you must specify basic information about the host, such as the operating system,
version, login account, and password. The host also contains parameters related to the Oracle client installed on it.
The Status for each component is set to one of the following values:
• Configured — The component has been installed, but has not been started.
If you remove a Configured component, that component is automatically removed from the Topology
Editor and is not saved in the topology file.
• Installed — The component has been started. You cannot remove a component from a deployed topology
until it has been started.
If you remove an Installed component, the component’s status changes to “To Be Removed”. Once you run
the topology file through the deployer in uninstallation mode, the component is physically uninstalled and
removed from the topology.
• To Be Removed — The component will be removed from the topology when you run the deployer in
uninstallation mode.
For more information about removing components, see Chapter 8, Uninstalling Components.

Technology Pack View

The Technology Pack view, shown in the following figure, lists the technology packs for which you have loaded
the corresponding XSD metadata files.
Once a DataLoader has been configured for an technology pack, the technology pack is shown in the Technology
Pack view. Expand the technology pack to see the collectors used by that technology pack.
For information about loading the metadata files, see Chapter 5, Installing Technology Packs.
Properties and Advanced Properties Views

When you select a component in the Logical view, or select a host in the Physical view, the Properties view
displays a table of basic parameters for that object, as shown in the following figure. If the selected component
has additional properties, they are listed in the Advanced Properties view. If there are no additional properties,
the Advanced Properties table is empty.

For each property, the table lists the name, description, current value, default value, and whether the property is
inherited from another component. In addition, the table displays an icon that describes the status of the property.
There are three different icons:
• Green check mark — The property value is valid.
• Yellow exclamation point — This value is inherited from upstream components (for example, from the
host, from the DataChannel if the property is on a collector, or from the Global DataChannel configuration).
In addition, the Is Inherited column includes a check mark for these properties.
Note that if you accept the default value, the value will change when you change the parameter value from
which this property is inherited.
• Red X — The property value is missing or is incorrect. Any red Xs must be resolved before you can install
the product. Note that when any property values are in error, the property includes a red X icon and the
problem is listed in the Problems view.
Changing Column Widths

To see the complete property names and their descriptions, you must resize the table columns in the property
views.
To change the width of a column in the properties table:
1. Place the cursor on the column separator that you want to move. The cursor changes to a dual-headed arrow.
2. Drag the column separator to the new location, then release the mouse button.
Changing a Property Value

If you change the value of a property, the Topology Editor verifies that the new value complies with any
restrictions for that property and marks the value with the appropriate icon (for example, valid or error). You
must resolve any properties that are marked with red X icons.
To change a property value:
1. In the Properties view, click the table cell in the Value column that you want to change. A text box is
displayed. For example:
2. Type the new value, then press Enter.

The Topology Editor verifies the new value. If it complies with any restrictions, the red X icon is changed to a
green check mark, and the error is removed from the Problems view.
Note the following restrictions:
• Once you have installed Netcool/Proviso, not all the components allow you to modify the property values.
For those that do allow you to change the values, you must redeploy the topology to propagate the change.
For more information, see Chapter 6, Modifying the Current Deployment.
• Although the Topology Editor allows you to change the database account prefix (DB_USER_ROOT), the
change is not propagated to all the related properties. Therefore, you should not change this value.

Restoring the Default Values

If you change the value of a property and want to roll back to its default value, highlight the property and click
the Restore Default icon .
To roll back all the component properties to their default values, click the Restore All Default icon .
Problems View
The Problems view warns you about:
• Missing values for required properties
• Values that do not pass the validation test
For example:
In addition, all the components that have errors are marked with a red X icon in the Logical view. See Changing a
Property Value on page 28 for information about resolving these errors.
The Problems view contains two additional tabs:
• Events — Lists the code, its description, and the time an event occurred
• Help — Displays information about the selected property

The topology.xml File

The topology describes the Netcool/Proviso infrastructure that you want to create.
Using the Topology Editor, you create an XML file that describes the topology to be deployed. By default, this
file is named topology.xml, but you can rename it. Once the topology is ready to deploy (you have specified
all the components and configurations, and resolved any errors), you pass the topology file to the deployer. When
the installation is complete, the deployer stores the topology file in the Netcool/Proviso database.
The topology file has three main sections that map the information from the three main views of the Topology
Editor:
• Logical view (see page 25)
• Physical view (see page 26)
• Technology Pack view (see page 27)
For detailed instructions about creating the topology.xml file, see Creating a New Topology on page 102.
Topology Editor Tools

Because the Topology Editor contains several different views, display “real estate” might be at a premium. The
editor enables you to easily close, enlarge, and restore the views, and provides tools to help accomplish these tasks.
Window Tools
Every view in the Topology Editor contains the following tools to enable you to manipulate the window:
Table 2: Tools for Property Values
Tool Description
Displays the editor tools for the current view in menu

format
Minimizes the view
Maximizes the view so it fills the entire display area
White X in the tab Closes the view

Minimizing Views
If you minimize a view, its corresponding icon is displayed in the right margin, along with an icon to restore the
view to its previous state. For example:
Restores all the views in this group
Properties view
Advanced Properties view
Restores the Logical view
Logical view
To restore a view, click the Restore tool for that group. If there are multiple views in the group (for example, the
Properties and Advanced Properties views), you can restore an individual view by clicking the corresponding
view’s icon.
Maximizing Views
Click the Maximize icon to display the view in the entire display area. If you maximize a view, all the other views
are automatically minimized and their icons are displayed in the right margin. Note that the maximized view
includes a new Restore icon in its window banner to restore the previous display settings.
Restoring the Original View

To restore the original layout of the Topology Editor views:
1. Select Window > Reset Perspective.

2. The Topology Editor asks for confirmation to restore the default views. Click OK.
The display is refreshed to show the default view of the Topology Editor, as shown in Figure 4 on page 24.
Note: If you completely close a view, this is the only way to redisplay the closed view.

Tools for the Main Editor Views

Table 3 lists the available tools for the main Topology Editor views — the Logical, Physical, and Technology Pack
views.
Table 3: Main View Tools
Tool Description
Home returns to the original tree view.

By default, the Logical view displays a tree of components and subcomponents.
If you use the Go Into tool to view only a certain component and its
subcomponents, click Home to return to the original view.
Returns to the previous display.
Go Into displays the subcomponents for the current component.

For example, if you highlight DataChannels in the Logical view and click Go
Into, only the DataChannel subcomponents are displayed in the view. Click
Home to return to the original view.
Displays the editor tools for the current view in menu format.
Properties and Advanced Properties Views

Table 4 lists the editor tools that enable you to manipulate property values.
Table 4: Tools for Property Values
Tool Description
Adds a user-defined property
Removes the selected user-defined property
Restores the default value of the current property
Restores the default values for all the properties for the current component
Displays the editor tools for the current view in menu format

Topology Editor Menus

The Topology Editor provides the following menus:
• Topology Menu
• Run Menu
• Window Menu
• Help Menu
Topology Menu
The Topology menu enables you to create, modify, and save the topology you create using the editor. The options
are as follows:
• Create new topology — Creates a new topology, which describes the Netcool/Proviso infrastructure. For
detailed instructions, see Creating a New Topology on page 102.
• Open existing topology — Opens an existing topology so you can make changes to it. See Opening an Existing
Topology File on page 110 and Opening a Deployed Topology on page 141 for more information.
Note: After your initial deployment, always load the topology file 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 made your changes, you must deploy the updated topology so that it is propagated to the database. To
make any subsequent changes following this deployment, you must load the topology file from the database again.
• Save topology — Saves the current topology under the default name, topology.xml. See The topology.xml
File on page 30 for more information about this file.
• Save topology as — Saves the current topology with the name you specify.
• Exit — Closes the Topology Editor. Alternatively, click the X in the upper, right-hand corner.
Run Menu
The Run menu runs the primary deployer in installation or uninstallation mode. The options are as follows:
• Run Deployer for Installation — Runs the deployer in installation mode to install the Netcool/Proviso
components according to the specified topology. See The Deployer on page 34 for general information about
the wizard; for detailed information about the actual installation, see Starting the Deployer on page 111.
• Run Deployer for Uninstallation — Runs the deployer in uninstallation mode to remove the
Netcool/Proviso components. For more information, see Uninstalling Netcool/Proviso on page 172.
Note: When you use the Run menu options (install or uninstall), the deployer uses the last saved topology file,
not the current one. Be sure to save the topology file before using a Run command.
Window Menu
The Window menu controls the overall display of the Topology Editor window. The options are as follows:
• Reset Perspective — Displays the default view of the Topology Editor. Use this option to redisplay a view
that you completely closed.
• Preferences — Lists the logging preferences. By default, the log level is set to FINE and the messages are
written to the file trace.log.
See Trace Log File on page 263 for instructions on renaming the log file and changing the log level.

Help Menu
The Help menu offers a single option, About IBM Tivoli Netcool Proviso - Topology Editor, which enables
you to access the following information about the Topology Editor:
• Plug-in Details — Lists information about all the plug-ins used by the editor, including the name, provider,
ID, and whether the plug-in is signed. Two buttons enable you to view more detailed information about a
plug-in:
• Legal info — Opens a Web browser that displays the legal information for the plug-in.
• Show Signing Info — Expands the Plug-ins dialog box to display the signing certificate for the plug-in.
Click Hide Signing Info to hide this information.
Click OK to close the Plug-ins dialog box.
• Configuration Details — Displays the configuration details for the editor. Click Copy to Clipboard to
copy this information to a text file so you can edit it. Click Close to close this dialog box.
Click OK to close the window.
The Deployer
When you are satisfied with the topology and have resolved any problems, save it to an XML file (see Saving the
Topology on page 110). You are now ready to install Netcool/Proviso using the deployer.
The deployer displays a series of pages to guide you through the Netcool/Proviso 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. For
more information, see Installation Steps on page 37.
This section provides an overview of the deployer. The topics are as follows:
• Primary Versus Secondary Deployers on page 35
• Node Selection on page 36
• Installation Steps on page 37
• Step Properties on page 38
• Step Status Values on page 39
• Resuming a Partially Successful First-Time Installation on page 40
In addition, you can run the deployer in silent mode. See Appendix F, Using Silent Mode for detailed information.

Primary Versus Secondary Deployers

Only one instance of the Topology Editor can exist in the Netcool/Proviso environment. The Topology Editor includes an embedded
copy of the deployer. The combination of the Topology Editor and the embedded instance of the deployer is
called the primary deployer. The primary deployer should run on the DataMart system. If you install DataMart on
the same system as the Oracle server, the primary deployer should also be on that system.
Note: If you are making changes to the Netcool/Proviso system configuration, use the primary deployer to make
those changes.
You can start the primary deployer from within the Topology Editor (by selecting Run > Run Deployer for
Installation). Once the primary deployer has completed the Netcool/Proviso installation, it stores the topology
data and the channel configuration (DataChannel and DataLoad) in the database. The primary deployer must
complete before other operations can occur.
In addition to the primary deployer, you can run a secondary deployer on any other system in the
Netcool/Proviso deployment where the Topology Editor is not installed. A secondary deployer performs local
installations of other Netcool/Proviso components by retrieving the topology file from the database.
Netcool/Proviso Version Version 4.4.3 supports remote installation of DataLoad and DataChannel only: You
must use a secondary deployer to install those distributed components that cannot be installed remotely. To set
up a secondary deployer, copy the distribution’s tar file to each remote machine so you can access the deployer
(and only the deployer) on that machine. For more information, see Remote Installation on page 178.
For example, if you install Netcool/Proviso on an AIX system, you would use the primary deployer to install most
of the components on the AIX system. However, because DataView is supported only on Solaris systems, you
would use a secondary deployer to install DataView on the second (Solaris) system.
Note: You cannot launch the deployer simultaneously from two different hosts. Only one deployer can be active
at any given time.
Note the following:

• Any system that runs a secondary deployer must have Java and X Window support. See the Netcool/Proviso
Configuration Recommendations document for version requirements.
• Secondary deployers cannot be used on Linux systems; only remote installations are supported on Linux.

Node Selection
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 Netcool/Proviso component will be installed, as shown in the following
figure:
The fields are as follows:

• Enable — Determines whether the deployer should perform actions on the target machine.
• Check prerequisites — Runs scripts to verify that the prerequisite software has been installed.
• Remote Command Execution — Specifies whether you can run commands on the remote machine, and
whether you can use RSH, OpenSSH, or both RSH and OpenSSH.
Remote installation is not supported for the DataMart, DataView, and database components. If you are
installing the components on multiple servers, the remote host for these components will not be selectable:
you must start the deployer locally on that host to install those components. For more information, see Remote
Installation on page 178 and Primary Versus Secondary Deployers on page 35.
• File Transfer — Specifies whether you can transfer files to the remote machine, and which transfer method
to use (FTP or SCP/SFTP).
Note that the settings for the Remote Command Execution and File Transfer fields apply to all the selected
(checked) nodes. However, different machines could have different access levels.
For example, suppose that you have two machines, Host A and Host B. Host A can do remote command
execution, but cannot transfer files to other machines. Host B can do both remote command execution and file
transfers. To deploy Netcool/Proviso on these two machines:
1. Disable Host A and enable Host B.

2. Enable the Remote Command Execution and File Transfer. options for Host B.
3. Install the components on Host B.
4. Run the deployer again, disabling Host B and enabling Host A.
5. Enable Remote Command Execution and disable File Transfer. for Host A.
6. Install the components on Host A.

Installation Steps
When you run the deployer, it displays a page that lists all the installation steps needed to install the
Netcool/Proviso components. Each step is a separate line in the table, and the steps are numbered beginning
with 0. Each step includes a status value, which is initially set to Ready. Note that you must run all the steps in
sequence.
Each component to be installed might require more than one step to be performed; the last step of the installation
sequence is always a step named “Register componentName”. This step registers in the database that the specified
component was installed on the given host.
The following figure shows a sample steps page:
To run each installation step separately:
1. Click Run Next to run the first step with status of Ready.
2. The status changes from Ready to Running. If the step is successful, the status changes to Success. If it
fails, it changes to Error and you must resolve the problem. For more information about troubleshooting
installation errors, see Step Properties on page 38.
3. If that step is successful, continue processing each step in turn.
To run all installation steps at the same time:
1. Verify that Stop on Error is enabled. This option stops the installation if it encounters an error with a step.
2. Click Run All. All the installation steps are processed sequentially.
Note that the Stop button is enabled only when you select Run All. Use Stop to stop the deployer after the
current step has completed.
Note: If you are installing DataLoad and DataChannel remotely, the steps Load Channel Configuration and
Load Collector Configuration might be duplicated in the list of installation steps. This duplication is both normal
and necessary. These steps verify that:
– The necessary configuration data is stored in the database.
– The configuration stored in the database is consistent with the one loaded at the beginning of the deployment.
– The DataLoad and DataChannel components are installed correctly.

When you close the steps page, the deployer stores the current step status in the /tmp/ProvisoConsumer
directory. You can retrieve the step status using the following command:
./deployer.bin –Daction=resume
The step status persists until you start the deployer again and generate a new list of steps. For more information,
see Resuming a Partially Successful First-Time Installation on page 40.
Important: If you modify a deployed topology such that only the database configuration (CFG component) is
changed, do not select the Check Prerequisites option. Otherwise, when you pass the updated topology to the
deployer, the Check OS step will fail. One example of a database configuration-only change is adding another UBA
to a DataChannel that has already been deployed.
The following figure shows a node selection page with a CFG component:
Step Properties
The deployer enables you to view property values and change them on-the-fly. If an installation step fails, you can
use the details window to view detailed information about the step to help you resolve the problem, or to change
the value of a property.
To view the step’s properties:
1. In the table of steps, right-click the step and select Properties. The deployer displays a window with several
tabs, depending on the actual step.
2. Click the Properties tab.
3. Change the values as necessary, then click Apply. The new value is written to the topology file.
4. Click OK to close the details window.

Tabs of the Step Details Window

The step details window is made up of several tabs, which vary according to the actual installation step. The tabs
include the following:
• Status — Displays read-only information about the step, including its description, target node, and current
status. Use the Change Status field to change the step’s status from Error to Ready after you have fixed
the problem that caused this step to fail.
• Properties — Displays the properties of the current step. The number of properties listed depends on that
step.
• Output — Displays status and error messages (if any) that result from running the step. If there is an error,
use these messages to help diagnose the problem. For example:
Step Status Values

There are four possible status values for an installation step:
• Ready — The step is ready to run. This is the initial value of a step.
• Success — The step ran and completed successfully.
• Error — The step ran, but failed.
• Held — The step was not run because a step that preceded it failed.
When a step runs, its status changes from Ready, to Running, then to Success or Error. If an installation step
fails, correct the problem, then change the step’s status from Error to Ready to run the step again.
To change the status of a step:
1. In the table of steps, right-click the step and select Set Status from the pop-up menu.
2. Select the appropriate status from the menu.
or
1. In the table of steps, right-click the step and select Properties from the pop-up menu.
2. Click the Status tab.
3. Set the Change Status field to the appropriate value.

Resuming a Partially Successful First-Time Installation

In this scenario, you try deploying a Netcool/Proviso topology for the first time. You define the topology and
start the installation. Although some of the components of the Netcool/Proviso topology are installed
successfully, the overall installation does not complete successfully.
It addition, it is possible to skip a section of the installation. For example, a remote node might not be accessible
for some reason. After skipping this portion of the installation, resume the installation to continue with the
remaining steps. The deployer will list only those steps needed to complete the installation on the missing node.
For example, suppose that during the first installation, Oracle wasn’t running, so the database check failed. Stop
the installation, start Oracle, then resume the installation.
To resume a partial installation:
1. 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 where you left off.
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 to another directory. Click
Next to continue.
4. The steps page shows the installation steps in the very same state they were in when 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.
Installation Scenarios
The new graphical interface supports the following installation scenarios:
• Performing a first-time installation
In this scenario, you deploy a Netcool/Proviso topology for the first time. You define the infrastructure and
successfully install the product. For more information, see Creating a New Topology on page 102.
• Performing a minimal deployment installation
A minimal deployment installation installs all the Netcool/Proviso components on a single Solaris host, or
on an AIX server and a Solaris server. This type of installation is used primarily for demonstration purposes,
and installs the product with the least amount of user input. For more information, see Chapter 4, Installing
Netcool/Proviso as a Minimal Deployment.
• Changing the current environment
In this scenario, you update the installed version of Netcool/Proviso to add or remove a component, or to
change the property values for a component. For example, an incremental installation might include:
— Adding DataChannels to the existing system
— Adding DataLoaders to the existing system
For more information, see Chapter 6, Modifying the Current Deployment.

• Installing technology pack

In this scenario, you install an technology pack in the existing Netcool/Proviso environment. For more
information, see Chapter 5, Installing Technology Packs.
• Uninstalling components
In this scenario, you remove components from the current Netcool/Proviso topology — or you uninstall
the entire infrastructure. For more information, see Chapter 8, Uninstalling Components.
• Performing a patch installation
For this scenario, you have received or downloaded the maintenance package for Netcool/Proviso. The
maintenance package contains the maintenance descriptor file, which describes the contents of the patch.
For more information, see Appendix G, Installing an Interim Fix.
Note: A future release of the product will support the upgrade scenario (Netcool/Proviso Version 4.4.1 or 4.4.2
to Version 4.4.3).
Before you can install Netcool/Proviso, you must:
1. Perform the pre-installation setup tasks described in the following section.

2. Install the prerequisite software, as described in Chapter 2, Installing and Configuring the Prerequisite Software.
Pre-Installation Setup Tasks

Before installing the prerequisite software, perform the following setup tasks:
• Setting Up a Remote X Window Display
• Changing the Ethernet Characteristics
• Setting the Resource Limits (AIX Only)
Setting Up a Remote X Window Display

For most installations, it does not matter whether you use a Telnet, rlogin, Xterm, or Terminal window to get to
a shell prompt.
However, some installation steps must be performed from a window that supports the X Window server protocols.
This means that the steps described in later chapters must be run from an Xterm window on a remote system or
from a terminal window on the target system’s graphical display. See the Netcool/Proviso Configuration Recommendations
document for the list of supported X emulators.
Specifying the DISPLAY Environment Variable

If you use an X Window System shell window such as Xterm, you must set the DISPLAY environment variable
to point to the IP address and screen number of the system you are using. Command sequences in this manual
do not remind you at every stage to set this variable.
If you use the su command to become different users, be especially vigilant to set DISPLAY before running X
Window System-compliant programs.

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
If the response is empty, set DISPLAY (as shown in the previous example).
Disabling Access Control to the Display

If you encounter error messages when trying to run X Window System-based programs, you might need to
temporarily disable X Window System access control so an installation step can proceed.
To disable access control:
1. Set the DISPLAY environment variable.

2. Enter the following command when logged in as root:
# /usr/openwin/bin/xhost +
Note that disabling access control is what enables access to the current machine from X clients on other
machines.
Changing the Ethernet Characteristics

Before installing Netcool/Proviso, you must force both the ethernet adapter and the port on the switch to 100
full duplex mode — autonegotiate settings are not enough.
AIX Systems
To change the setting to full duplex:
1. Using the System Management Interface Tool (SMIT), navigate to Devices > Communication > Ethernet
Adapter > Change/Show Characteristics of an Ethernet 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.
Important: If the AIX node is a virtual partition, you must perform these steps on the virtual I/O server (including
the reboot).

Solaris Systems
This section describes how to set a network interface card (NIC) and a BGE network driver to full duplex mode.
NIC
To change the NIC to full duplex mode:
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

• 1 — Up
• 0 — Down
link_speed Determines the link speed

• 0 — 10Mb/sec
• 1 — 100Mb/sec
link_mode Determines the duplex mode

• 0 — Half duplex
• 1 — Full duplex
adv_autoneg_cap Determines whether auto negotiation is on

• 0 — Off
• 1 — On
For example:
ndd -get /dev/hme link_status
In these commands, /dev/hme is your NIC; you might need to substitute your own /dev/xxx.
3. To set your NIC to 100Mb/s with full duplex for the current session, run the following commands:
ndd -set /dev/hme adv_100hdx_cap 0
ndd -set /dev/hme adv_100fdx_cap 1
ndd -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=0
set hme:hme_adv_100hdx_cap=0
set hme:hme_adv_100fdx_cap=1
4. Verify that your NIC is functioning as required by rerunning the commands listed in Step 2.

BGE Network Driver

To change a BGE network driver to full duplex mode:
1. To determine the link speed and current duplex setting, run the following command:
% kstat bge:0 | egrep 'speed|duplex'
The output is similar to the following:
duplex full
ifspeed 100000000
link_duplex 2
link_speed 100
The parameters are as follows:
Parameter Description
link_duplex Determines the duplex setting

• 1 — Half-duplex
• 2 — Full duplex
link_speed Determines the link speed

• 10 — 10 Mb/sec
• 100 — 100 Mb/sec
• 1000 — 1 Gb/sec
2. Create a file named bge.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.

Setting the Resource Limits (AIX Only)

On AIX systems, the default user process limits are not adequate for Netcool/Proviso.
To set the correct user process limits on AIX systems:
1. 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 = 2000
Note: Apply these settings to every AIX system running a Netcool/Proviso 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 Netcool/Proviso user and then log in again for the changes to
take effect.
Netcool/Proviso Distribution
The Netcool/Proviso distribution is available as a DVD/CD and as an electronic image. The instructions in this
guide assume that you are installing from an electronic image.
If you install the product from an electronic image, be sure to keep a copy of the distribution image in a well-
known directory, because you will need this image in the future to make any changes to the environment, including
uninstalling Netcool/Proviso.

Chapter 2: Installing and Configuring the
Prerequisite Software
This chapter describes how to install and configure some of the prerequisite software for Netcool/Proviso. The
topics are as follows:
Topic Page
Overview 46
Before You Begin 47
Installing the Oracle Server 51
Installing the Oracle Client (Patch Version 9.2.0.8) 73
Installing the Oracle Client (Patch Version 9.2.0.6) 85
Next Steps 97
Overview
Before beginning the Netcool/Proviso installation, you must install the prerequisite software listed in the
Netcool/Proviso Configuration Recommendations, including:
• Oracle server — You must install an instance of the Oracle server on the system where you plan to install
the Netcool/Proviso DataMart component. To use Oracle with Netcool/Proviso, you must install Oracle as
described in this chapter — do not use a separate Oracle installation method provided by Oracle Corporation.
Oracle client — You must install Oracle client software on each system where you plan to install a
Netcool/Proviso component, except for the system where you installed the Oracle server. Netcool/Proviso
components require two different patch versions of the client software. The DataView component requires
version 9.2.0.6. All other components require version 9.2.0.8.
If you are installing DataView on the same system where you are installing another Netcool/Proviso
component, you must install patch version 9.2.0.6 in addition to other Oracle client or server components
otherwise installed.
For example, if you are installing DataView on the same system where you installed the Oracle server, you
must also install the Oracle client with the patch version 9.2.0.6. If you are installing DataView on the same
system as another Netcool/Proviso component and the Oracle server is not located on the system, you must
install two instances of the Oracle client, one with patch version 9.2.0.6 and one with version 9.2.0.8.
When you complete the steps in this chapter, the Oracle server and client will be installed and running, with
tablespaces sized and ready to accept the installation of a Netcool/Proviso DataMart database. You can
communicate with Oracle using the SQLPlus command-line utility.
You can download the Oracle installation media from the following URL:
http://www.oracle.com/technology/software/products

Chapter 2: Installing and Configuring the Prerequisite Software
For information about installing Oracle, see Installing the Oracle Server on page 51, Installing the Oracle Client (Patch
Version 9.2.0.8) on page 73 and Installing the Oracle Client (Patch Version 9.2.0.6) on page 85.
Note: The Netcool/Proviso script used to install Oracle is platform-independent and can be used to install either
Solaris, AIX, or Linux, regardless of the operating system distribution media.
• OpenSSH — You must install and configure OpenSSH before installing Netcool/Proviso. For details, see
Netcool/Proviso Technical Note: Secure File Transfer Installation.
• Web browser — The launchpad requires a Web browser. IBM recommends using Mozilla with the
launchpad. For the complete list of supported browsers, see the Netcool/Proviso Configuration Recommendations
document.
• Java — Java is used by DataMart, DataLoad, and the technology packs.
• Acrobat Reader — Adobe® Acrobat Reader® is free software that enables you to read the Netcool/Proviso
documentation delivered in Portable Document Format (PDF). If you already have Acrobat installed, you
do not need to install Acrobat again. Note that Acrobat Reader requires the GIMP Toolkit (GTK+) and
several additional libraries. See the Netcool/Proviso Configuration Recommendations for more information.
You can download Adobe Reader from the Adobe Web site (http://www.adobe.com).
See the Netcool/Proviso Configuration Recommendations document for the complete list of prerequisite software and their
supported versions.
Before You Begin

To install Oracle for use with Netcool/Proviso, you need:
• An appropriately sized server with the operating system installed and running (for the Oracle server).
Note: Professional Services can provide the minimum CPU speed, memory size, and disk configuration
requirements for your Netcool/Proviso installation.
• The current version of Netcool/Proviso software.

• The downloaded files for the Oracle installation.
• Oracle server patch files.
• Oracle client patch files. The DataView component requires client patch version 9.2.0.6. All other
Netcool/Proviso components require client version 9.2.0.8.
• If you are installing Oracle on an AIX system, follow the instructions in Asynchronous I/O Support on page 54
before installing Oracle.
Before installing Oracle, read the setup and password information. The topics are as follows:
• Specifying a Basename for DB_USER_ROOT on page 48
• Specifying Oracle Login Passwords on page 48
• Adding the pvuser Login Name on page 49
• Assumed Values on page 50

Specifying a Basename for DB_USER_ROOT

Different Netcool/Proviso components use different Oracle login names so that database access can be
controlled separately by component, and for database troubleshooting clarity. The Netcool/Proviso installation
generates the appropriate login names for each Netcool/Proviso subsystem. You provide a basename, which the
installation retains as the variable DB_USER_ROOT.
Note: This is not an operating system environment variable, but a variable used internally by the installer.
The default DB_USER_ROOT value is PV. IBM strongly encourages you to retain the default value.
Oracle login names are generated from the DB_USER_ROOT basename by appending a function or subsystem
identifier to the basename, as in the following examples:
• PV_ADMIN
• PV_INSTALL
• PV_LDR
• PV_CHANNEL
• PV_COLL
• PV_CHNL_MANAGER
• PV_GUI
In addition, separate Oracle login names are generated for each Netcool/Proviso DataChannel and subsystem,
identified by an appended channel number, as in the following examples:
• PV_CHANNEL_01
• PV_CHANNEL_02
• PV_LDR_01
• PV_LDR_02
Specifying Oracle Login Passwords

For each component that requires an Oracle login name, you must provide a password for that login name. 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. The default password is usually
shown in uppercase, but is sometimes shown in lowercase. In both cases, the same default password is intended.
You can retain the default password, or enter passwords of your own according to your site password standards.
You should use the same password for all Netcool/Proviso subsystem Oracle login names. If you use different
passwords for each login name, keep a record of the passwords you assign to each login name.

The Netcool/Proviso installer uses PV for three default values, as described in Table 5.
Table 5: Uses of PV as Default Values
Installer
Default Used As Recommendation
Value
PV Default value of the DB_USER_ROOT variable, the In all instances, use the default
basename on which Oracle login names are generated value PV, unless your site has an
explicit naming standard or an
PV or pv Default password for all Oracle login names explicit password policy.
PV Default Oracle database name, also called the Oracle TNS

name
Important: If you use a non-default value, you must remember to use the same value in all installation stages. For
example, if you set your Oracle TNS name to PROV instead of PV, you must override the default PV entry in all
subsequent steps that call for the TNS name.
Adding the pvuser Login Name

Decide in advance where to place the home directory of the pvuser login name. Do not place the home directory
in the same location as the Netcool/Proviso program files. That is, do not use /opt/proviso or any other
directory in /opt for the home directory. Use a standard home directory mounted on /home or /export/home,
as available. This guide uses /export/home/pvuser as the example home directory.
Add the pvuser login name to every system on which you install a Netcool/Proviso component, including the
system hosting the Oracle server.
Adding pvuser to a Standalone Computer

Use the steps in this section to add the pvuser login name to each standalone computer. 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 a network-wide database of login names such as Yellow Pages or Network Information
Services (NIS or NIS+), see Adding pvuser on an NIS-Managed Network on page 50.
To add pvuser:
1. Log in as root.
2. Set and export the DISPLAY environment variable (see Setting Up a Remote X Window Display on page 41).
3. At a shell prompt, run the following command:
# useradd -g staff -m -d /export/home/pvuser -k /etc/skel -s /bin/ksh pvuser
Substitute the home directory you selected, if you did not use /export/home/pvuser.
4. Set a password for pvuser :
# passwd pvuser
The system prompts you to specify a new password twice. The default pvuser password assumed by the
Netcool/Proviso installer is pv.

5. Test logging in as pvuser, either by logging out and back in, or with the su command, as follows:
# su - pvuser
Confirm that you are logged in as pvuser with the id command:
$ id
These instructions create a pvuser login name with the following attributes:
Attribute Value
login name pvuser
member of group staff
home directory /home/export/pvuser
login shell Korn shell (/bin/ksh)
copy skeleton setup files (.profile, and /etc/skel

so on) from this directory
Note: The pvuser account must have write access to the /tmp directory.
Multiple Computer Considerations

If you are creating the pvuser login name on more than one computer in your network, avoid confusion by
specifying the same user ID number for each pvuser login name on each computer.
When you have created the first pvuser login name, log in as pvuser and run the id command. The system responds
with the user name and user ID number (and the group 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 to the useradd command to
specify the same user ID number:
# useradd -g staff -m -d /export/home/pvuser -k /etc/skel -s /bin/ksh -u 1001 pvuser
Adding 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 to each Netcool/Proviso computer’s local setup files,
or to the network login name database.
Assumed Values
The 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 login name for this user must be oracle. Use of
another operating system name for the Oracle user is not
supported.
Password for Oracle user oracle
ORACLE_SID = PV
TNS name for Netcool/Proviso database instance PV
Oracle installed in (ORACLE_HOME =) /opt/oracle/product/n

Note: The value of ORACLE_HOME cannot contain
soft links to other directories or filesystems. Be sure to
specify the entire absolute path to Oracle.
Oracle login name for database administrator (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 can substitute site-specific values for these
settings. However, IBM strongly recommends using the default values the first time you install Netcool/Proviso.
See Specifying a Basename for DB_USER_ROOT on page 48 for more information.
Installing the Oracle Server

This section documents the steps to install the Oracle server and verify the installation. Install the Oracle server
on the same machine that hosts DataMart.
Step 1: Ensure that the Oracle User is not in NIS

The oracle user must be created locally, and must not be part of Network Information Services (NIS). 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:
1. 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 Step 6: Run the Oracle Server Configuration
Script on page 56).
3. Re-enable NIS.
Important: The local Oracle account should be used before the NIS Oracle user.

Step 2: Download the Oracle Distribution and Patch to Disk

To download the Oracle installation files to your target server’s hard disk:
1. Log in as root.
2. Set the DISPLAY environment variable.
3. Create a directory to hold the contents of the Oracle distribution. For example:
# mkdir /var/tmp/Oraclen
where n is the version number for Oracle.
4. Create subdirectories named Diskn for each Oracle file and create one Patch subdirectory. The
Netcool/Proviso installation script expects subdirectories named Disk1, Disk2, and Disk3, so use these
exact names. For example:
# cd /var/tmp/Oraclen
# mkdir Disk1 Disk2 Disk3 Patch
5. Download the Oracle files to the corresponding directories.
6. Locate the appropriate upgrade patch file for your version of Oracle on the Oracle Web site and download
it to your /var/tmp/Oraclen directory. See the Netcool/Proviso Configuration Recommendations document for the
list of supported patch files.
7. (Optional) If the patch file you download contains a tar file distributed in zip file format, unzip the tar file
from the zip file. For example:
# unzip BuildInfo_OS.zip
where n is the version number for Oracle, OS is the operating system, and BuildInfo is a version and build-
specific number (such as p2376472_8174).
Important: Because the patch delivery files contain a directory structure that starts with a Disk1 directory, do not
untar the patch file into the same top-level /var/tmp/Oraclen directory that you used in Steps 2 and 3. Doing
so would mix the original Oracle release’s files with the patch files in the same Disk1 subdirectory. Oracle will fail
to install under those circumstances.
8. Untar the patch delivery file into your Patch subdirectory. For example:
# cd /var/tmp/Oraclen/Patch
# tar xvf ../VersionInfo_OS_release.tar
where n is the version number for Oracle, OS is the operating system, and VersionInfo is a version-specific
number, such as 9208.
The system creates a directory structure similar to the following:
/var/tmp/Oraclen
Disk1
Disk2
Disk3
Patch
Disk1
Before you proceed to the next step, make sure that you obtain the upgrade instructions provided by Oracle for
the patch. The instructions contain information on performing steps required for the upgrade that are not
documented in this guide. If you are installing the Oracle patch on an AIX system, you might need to run the
sbinclean command and execute the catpatch.sql and utlrp.sql SQL scripts as part of the upgrade
procedure. Additional requirements might exist for other platforms.

Step 3: Download the Netcool/Proviso Distribution to Disk

To download the Netcool/Proviso distribution to a directory on your target server’s hard disk:
1. Create a directory to hold the contents of your Netcool/Proviso distribution. For example:
# mkdir /var/tmp/cdproviso
2. Download the distribution to the directory created in the previous step. You will run a variety of scripts and
programs from directories residing in the directory created on the hard drive, including:
— Oracle configuration script
— Pre-installation script
— Installation script
— Netcool/Proviso setup program
The instructions in this chapter assume that the root installation directory is /var/tmp/cdproviso.
Step 4: Verify the Required Operating System Packages
On Solaris Systems
Before installing the Oracle server, make sure the following Solaris packages are installed on your system.
Package Description
SUNWarc Archives and Libraries/Generic
SUNWbtool CCS tools bundles with SunOS/Generic
SUNWhea SunOS Header Files/Generic
SUNWlibm Forte Developer bundled libraries
SUNWlibms Forte Developer bundled shared libraries
SUNWsprot Solaris bundled tools
SUNWtoo Programming Tools
To verify that the required Solaris packages are installed:
1. Enter the following command at the shell prompt:

# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot
SUNWtoo SUNWuiu8
The following output confirms that the specified Solaris packages are installed correctly:
system SUNWarc Archive Libraries
system SUNWbtool CCS tools bundled with SunOS
system SUNWhea SunOS Header Files
system SUNWlibm Forte Developer Bundled libm
system SUNWlibms Forte Developer Bundled shared libm
system SUNWsprot Solaris Bundled tools
system SUNWtoo Programming Tools
system SUNWuiu8 Iconv modules for UTF-8 Locale

2. If these packages are not installed on your system, see the Solaris Installation Guide for instructions on installing
supplementary package software.
On AIX Systems
Before you install Oracle on AIX systems, verify that your system meets the required release level, as specified in
the Netcool/Proviso Configuration Recommendations document.
To verify your AIX release level:
1. As root, enter the following command at the shell prompt:

# oslevel -r
This command returns a string that represents the maintenance level for your AIX system. For example, the
following string represents AIX 5.3 maintenance release 4:
5300-04
2. The bos.adt.libm fileset is required and must be installed before you install Oracle.
To determine whether the fileset has been installed, enter the following command:
# lslpp -l | grep bos.adt.libm
If the fileset has been installed, the system returns its name and version. For example:
bos.adt.libm 5.3.0.40 COMMITTED Base Application Development Math Library
In this example, the string ”5.3.0.40” represents the version number of the file.
See the Netcool/Proviso Configuration Recommendations for detailed information about how to install the latest filesets.
Asynchronous I/O Support

Before installing Oracle on AIX systems, you must set up asynchronous I/O (AIO), or the installation might fail.
To set up asynchronous I/O:
1. As root, enter the following command to check the current status of AIO support:
# lsdev -Cc aio
The status should be Available.

2. If the status shown is Defined, change the STATE to be configured at system restart option to Available
by entering the following command:
# smit chaio
3. Reboot the system.

4. Re-enter the following command to check the current status of AIO support:
# lsdev -Cc aio
Verify that the status is set to Available.

5. Continue with Step 6: Run the Oracle Server Configuration Script on page 56.

Step 5: Set the System Parameters (Solaris Only)

Before you install the Oracle server, set the Solaris shared memory and semaphore parameters as described in this
section.
When you install Netcool/Proviso, you specify the size of the deployment — small, medium, or large. The value
you select affects the Oracle PROCESSES parameter. You must set the appropriate kernel parameter level in
order for the deployment to work properly.
The two parameters affected by the deployment size are seminfo_semmsl and seminfo_semmns. These
parameters define the maximum size of a semaphore set and the maximum number of semaphores in the system.
The recommended settings (600 and 800, respectively) will work correctly for all three deployment sizes.
However, if you use a custom configuration that is much larger than the large deployment guideline (300,000
resources), you must change the values of the two parameters to the appropriate level.
Note: These entries are only for the system running the Oracle server, not the Oracle client.
To set Solaris system parameters:
1. As root, change to the /etc directory:

# cd /etc
2. Verify the amount of installed RAM on your server by entering the following command:
# prtconf -v | grep Memory
3. Create a backup of the system file, then open the system file with a text editor.
4. Set the shmmax parameter by adding a line at the bottom of the file in the following form:
set shmsys:shminfo_shmmax=nnn
In this syntax, nnn must be the installed system RAM in bytes, divided by 2.
For example, if your system has 1 GB RAM, the maximum shared memory should be set to 512 MB. Thus,
the value to enter would be 512 x 1024 x 1024, or 536870912.
set shmsys:shminfo_shmmax=536870912
5. In the system file, locate lines beginning with set shmsys:shminfo, and set the following minimum
parameters. If these lines do not exist in your system file, add them as shown:
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmni=100
set semsys:seminfo_semmsl=600
set semsys:seminfo_semmns=800
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
6. Save and exit the system file.
7. Reboot your system before continuing to the next step.

Step 6: Run the Oracle Server Configuration Script

In this step, you set up the Oracle environment using the configure_ora script provided with the
Netcool/Proviso DataMart files on the Netcool/Proviso distribution. This script automatically creates the
following configuration:
• Adds the dba and oinstall groups to /etc/group
• Adds the login name oracle, whose primary group membership is dba and secondary group membership is
oinstall
• Creates the Oracle directory structure
• Creates startup and shutdown scripts for Oracle server processes
To configure the Oracle installation environment using the configure_ora script:
1. As root, set the ORACLE_BASE environment variable to point to the top-level directory where you want
the Oracle server files installed. The default installation directory is /opt/oracle.
For example:
# ORACLE_BASE=/opt/oracle
# export ORACLE_BASE
Note: The configure_ora script places this variable into the oracle login account’s .profile file.
To check that the variable is set correctly, enter the following command:
# env | grep ORA
2. Change to the following directory:
Solaris systems:
# cd /var/tmp/cdproviso/SOLARIS/DataBase/SOLnum/instance
AIX systems:
# cd /var/tmp/cdproviso/AIX5/DataBase/instance
where:
— /var/tmp/cdproviso is the directory on the hard drive where you copied the contents of the
Netcool/Proviso distribution in Step 3 on page 53.
— On Solaris systems, SOLnum is the string “SOL” and the Solaris version number. For example, SOL9. This
string is not included in the directory path on AIX systems.
3. 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.9 Generic ]
Host ......... : [ delphi ]
Logname ...... : [ root ]
ORACLE_BASE .. : [ /opt/oracle ]
DBA group ................. : [ dba ]

OUI Inventory group ....... : [ oinstall ]
Oracle Software owner ..... : [ oracle ]
Configure Oracle release .. : [ 9.2.0 ]
Menu :
1. Set current release to next supported release
2. Check environment.
0. Exit
Choice:
4. Type 2 at the Choice prompt and press Enter.

The script creates the dba and oinstall groups and the ORACLE_BASE directory, unless they already exist:
Checking environment...
Checking for group [ dba ] --> Created.
Checking for group [ oinstall ] --> Created.
Checking ORACLE_BASE
** WARNING
** ORACLE_BASE directory does not exist.
** [ /opt/oracle ]
**
** Create it ? (n/y) y
5. Type y and press Enter.

The script creates the /opt/oracle directory and continues as follows:
Checking for user [ oracle ]
** WARNING
** User [ oracle ] does not exist.
**
** Create it locally ? (n/y) y
6. Type y and press Enter.

The script creates the oracle user and continues as follows:

--> Created.
Checking for oracle directory tree :
[ /opt/oracle/product ] --> Created.
[ /opt/oracle/product/9.2.0 ] --> Created.
[ /opt/oracle/product/9.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...
7. Press the Enter key to continue. The configure_ora main screen is refreshed.
8. Type 0 and press Enter to exit the configure_ora script.
Note: You must set a password for the oracle login name (see Step 7: Set a Password for the Oracle Login Name on
page 59).
Structure Created by the configure_ora Script

The script creates the Oracle directory structure. The following example shows the directory structure created
for Oracle 9i, where ORACLE_BASE was set to /opt/oracle:
/opt/oracle/product
/opt/oracle/product/9.2.0
/opt/oracle/product/9.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:
• /etc/init.d/dbora, which starts the Oracle Listener and database server automatically on each system
boot
• Symbolic links to /etc/init.d/dbora in /etc/rc0.d, /etc/rc1.d, and /etc/rc2.d
• Oracle configuration files /var/opt/oracle/oratab and lsnrtab

• A .profile file for the oracle user containing the following lines:
# -- Begin Oracle Settings --
umask 022
ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/product/9.2.0
NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
LD_LIBRARY_PATH=$ORACLE_HOME/lib
TNS_ADMIN=$ORACLE_HOME/network/admin
PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin
EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.so
export PATH ORACLE_BASE ORACLE_HOME NLS_LANG

export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN
export EXTPROC_DLLS
# -- End Oracle Settings --
Note the following:

• The value of ORACLE_HOME cannot contain soft links to other directories or filesystems. Be sure to
specify the entire absolute path to Oracle.
• You will add the ORACLE_SID variable to this file later, in Step 13: Set the ORACLE_SID Variable on page 67.
Step 7: Set a Password for the Oracle Login Name

The configure_ora script you ran in the previous section creates the oracle login name. You must assign a
password for the oracle login name to maintain system security, and because subsequent installation steps expect
the password to be already set.
To set a password:
1. As root, enter the following command:

# passwd oracle
2. Enter and re-enter the password (oracle, by default) as prompted. The password is set.
Step 8: Run the Pre-Installation Script

Run the pre-installation script that verifies readiness to install Oracle:
1. As root, change to the following directory:

Solaris systems:
# cd /var/tmp/cdproviso/SOLARIS/DataBase/SOLnum/instance/ora_installer

AIX systems:
# cd /var/tmp/cdproviso/AIX5/DataBase/instance/ora_installer
where:
2. Set the ORACLE_BASE environment variable. For example:
You must use the same ORACLE_BASE setting that you specified in Step 6: Run the Oracle Server Configuration
Script on page 56.
3. Enter the following command:
# ./pre_install_as_root
The following messages indicate success:
Checking that you are logged in as root --> Ok.
Checking ORACLE_BASE --> Ok.
Checking oraInst.loc file --> Ok.
If the script shows an error, correct the situation causing the error before proceeding to the next step.
Step 9: Verify PATH and Environment for the Oracle Login Name
Before proceeding to install Oracle server files, make sure the /usr/ccs/bin directory is in the PATH
environment variable for the oracle login name.
To verify the PATH and environment:
1. Log in as oracle. Set and export the DISPLAY environment variable.

If you are using the su command to become oracle, use a hyphen as the second argument so the oracle name’s
login environment is loaded:
# su - oracle
2. Verify that the environment variable ORACLE_BASE has been set by entering the following command:
$ env | grep ORA
If the response does not include ORACLE_BASE=/opt/oracle, stop and make sure the .profile file was
set for the oracle user as described in Step 6: Run the Oracle Server Configuration Script on page 56.
3. To verify the path, enter the following command:
$ echo $PATH
The output should show that /usr/ccs/bin is part of the search path. For example:
/usr/bin:/opt/oracle/product/9.2.0/bin:/usr/ccs/bin
3-a. If the directory does not appear in the path, add it by entering the following commands:
$ PATH=$PATH:/usr/ccs/bin
$ export PATH

Step 10: Install Oracle

There are two ways to install the Oracle database files:
• Using the Menu-Based Script on page 61
• Using Batch Mode on page 63
IBM recommends using the menu-based script method the first time you install Netcool/Proviso.
Note: If you installed the Oracle server, Oracle client, or upgrade patches to the Oracle server or Oracle client
using batch mode, skip this step. The Oracle installation script provided by IBM is used to install Oracle server,
Oracle client, and to install upgrade patches to an existing Oracle server or Client installation. You should follow
this step if you are not familiar with the Oracle installation process. If you understand the Oracle installation
process, use batch mode (see Using Batch Mode on page 63).
Using the Menu-Based Script

To install the Oracle server using the menu-based script:
1. As oracle, change to the following directory:

Solaris systems:
$ cd /var/tmp/cdproviso/SOLARIS/DataBase/SOLnum/instance/ora_installer
AIX systems:
where:
2. 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.9 Generic ]
Host ......... : [ delphi ]
Logname ...... : [ oracle ]
Install Oracle release .... : [ 9.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/9.2.0 ]
c) DBA group ..................... : [ dba ]
d) OUI Inventory group ........... : [ oinstall ]
e) Oracle Software owner ......... : [ oracle ]
f) Directory where CDs were copied:
[ ]
Menu :
1. Set current release to next supported release
2. Set install type to: Client
3. Perform install
0. Exit
Choice :
3. Verify the following settings:

— The Oracle release number should be 9.2.0.
— The Installation type field should be set to Server.
This field cycles between three settings: Server, Client, and Patch. Type 2 at the Choice prompt and press
Enter until Server is displayed.
4. Type f at the Choice prompt and press Enter.
5. At the Choice prompt, enter the full path to the directory. For example:
Choice: f
Enter new value for CD directory: /var/tmp/Oracle9
6. Edit other menu settings as required.

For example, if you used non-default values for ORACLE_BASE or ORACLE_HOME, enter your settings
until the menu shows the correct information.
7. 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 to perform the installation.
8. Type Y at the Choice prompt and press Enter. The installation script starts installing Oracle and displays a
series of status messages.
Note: You can safely ignore any “font.properties not found” messages in the output.
When the installation reaches the In Summary Page stage, the installation slows down significantly while
Oracle files are copied and linked.

9. When the installation is complete, messages similar to the following are displayed:
In End of Installation Page
The installation of Oracle9i Database was successful.
Please check /opt/oracle/oraInventory/logs/silentInstall2004-09-28_04-23-53PM.log
for more details.
The Oracle installation has completed. Please check the

messages above to determine if the install completed
successfully. If you do not see successful completion
messages, consult the install log at:
/opt/oracle/oraInventory/logs
Press C to continue...
Note: Write down the log file location to aid in troubleshooting if there is an 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.
Using Batch Mode

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 client installation. You should follow this step if you are familiar
with the Oracle installation 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 Step 10 on page 61). If you installed
the Oracle server, Oracle client, or upgrade patches to the Oracle server or Oracle client using the menu-based
script, skip this step.
Batch mode is the only Oracle installation method that lets you change the settings for the Oracle primary and
secondary group names, and the name of the oracle user login, if you have not used the default settings.
To install Oracle using batch mode:

Solaris systems:
AIX systems:
where:

2. Open the perform_oracle_inst.ini file with a text editor. This file contains a number 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
3. Make the necessary edits to the installation values. You can uncomment lines already included in the file to
use those values for the installation.
For example, uncomment the following line to install Oracle server:
ORA_TYPE=Server
4. Save your edits and close the file.
5. Run the installation script with the b flag. For example:
$ ./perform_oracle_inst b
The installation program verifies the values and performs the installation as shown in the section for the menu-
based installation (see Step 10: Install Oracle on page 61).

Step 11: Run the root.sh Script

After successfully running an Oracle server installation, you must run the root.sh script.
Note: This step is also required after an Oracle patch installation. See Step 12 on page 66 for information on
how to perform an Oracle patch installation.
To run the root.sh script:
1. Log in as root or become superuser. Set the DISPLAY environment variable.

2. Change to the directory where Oracle server files were installed. (This is the value of the ORACLE_HOME
environment variable as seen by the oracle login name.) For example:
# cd /opt/oracle/product/9.2.0
3. Run the following command:
./root.sh
Messages similar to the following are displayed:
Running Oracle9 root.sh script...
The following environment variables are set as:

ORACLE_OWNER= oracle
ORACLE_HOME= /opt/oracle/product/9.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 accept the default value.
The default entry might be NFS-mounted at your site so it can be shared among several workstations and
therefore might be write-protected. If so, enter the location of a machine-specific alternate bin directory.
(You might need to create 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 by
Database Configuration Assistant when a database is created
Finished 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.

Step 12: Install Oracle Patches

After you install Oracle, you must install the patchset for your version of Oracle to bring the Oracle version up
to the IBM-validated patch level. See the Configuration Recommendations document for up-to-date information about
the required patches.
Before you complete this step, make sure that you obtain the upgrade instructions provided by Oracle for the
patch that you wish to install. The instructions contain information on performing steps required for the upgrade
that are not documented in this guide. If you are installing the Oracle patch on an AIX system, you might need
to run the sbinclean command and execute the catpatch.sql and utlrp.sql SQL scripts as part of the
upgrade procedure. Additional requirements might exist for other platforms.
Note: Do not skip this step. Upgrade the Oracle version before you install the Netcool/Proviso database
structure.
To install the Oracle patchset:

Solaris systems:
AIX systems:
where:
3. Verify the following settings:
— The Oracle release number should be 9.2.0.
— The Installation type field should be set to Patch.
This field cycles between three settings: Server, Client, and Patch. Type 2 at the Choice prompt and press
Enter until Patch is displayed.
4. To specify the path, type f at the Choice prompt and press Enter.
5. At the Choice prompt, enter the full path to the patch directory you created to hold the contents of the patch
release (see Step 2: Download the Oracle Distribution and Patch to Disk on page 52). For example:
Choice: f
Enter new value for CD directory: /var/tmp/Oracle9/patch
6. To begin the upgrade installation, type 3 at the Choice prompt and press Enter. The installation script checks
the environment, then asks whether you want to perform the installation.

7. Type y at the Choice prompt and press Enter. The script proceeds to install the patch release files, showing
a long series of messages much like the ones shown during installation of the base release.
In the messages, look for “success” notifications. If the script shows unsuccessful installation messages,
check the installation log file specified in the message. Correct the error conditions identified in the log file,
then rerun the patch installation and double-check all menu settings.
8. 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 same screen.
9. Exit from the menu.
Note: If you try to start Oracle as the database administrator (DBA) at this point, the startup will fail because
the file initPV.ora does not yet exist. This file is created during the Netcool/Proviso installation.
Additional AIX Patch

If you installed the Oracle server on an AIX system, you must apply an additional patch. Otherwise, the database
installation will fail.
Apply the patch as follows:
1. As oracle, copy the file owapatch.sql from /Oracle_AIX_dir/oracle9.2.0.8-AIX-patches to the

/opt/oracle/product/9.2.0/rdbms/admin directory.
2. Unzip p2858130_92080_AIX64-5L.zip into the /tmp directory.
3. From the Oracle_patches_dir/oracle9.2.0.8-AIX-patches/OPatch directory, run the following
command:
opatch apply /tmp/2858130
Step 13: Set the ORACLE_SID Variable

A system identifier (SID) identifies each Oracle database instance for internal connectivity on the Oracle server
itself. (Connectivity from Oracle Clients to the server is controlled by the TNS names system configured later.)
The environment variable for the system identifier is ORACLE_SID.
Decide on an SID to use for your Netcool/Proviso database instance. The assumed default for the
Netcool/Proviso installation is PV. IBM recommends using this default SID unless your site has established
Oracle SID naming conventions.
To set the ORACLE_SID environment variable:
1. As oracle, open the .profile file with a text editor.

2. 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 022
ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/product/9.2.0
ORACLE_SID=PV; export ORACLE_SID
NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
LD_LIBRARY_PATH=$ORACLE_HOME/lib
TNS_ADMIN=$ORACLE_HOME/network/admin
PATH=$PATH:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/delphi/bin
EXTPROC_DLLS=ONLY:${LD_LIBRARY_PATH}/libpvmextc.so
export PATH ORACLE_BASE ORACLE_HOME NLS_LANG

export ORA_NLS33 LD_LIBRARY_PATH TNS_ADMIN
export EXTPROC_DLLS
# -- End Oracle Settings --
3. Save and exit the .profile file.

4. Enter the following shell command to activate the change to your profile:
$ . ./.profile
5. Make sure the variable was set by entering the following command:
$ env | grep CLE_SID
Step 14: Set Automatic Startup of the Database Instance

In this step, you configure your Oracle host to automatically start the Netcool/Proviso database instance at
system startup time.
To set up automatic startup:
1. Make sure you are logged in as oracle and that the DISPLAY environment variable is set.
2. Depending on your operating system, change to the following directory:
Solaris systems:
$ cd /var/opt/oracle
AIX systems:
$ cd /etc

3. Edit the oratab file with a text editor. The last line of this file looks like this example:
*:/opt/oracle/product/9.2.0:N
4. Make the following edits to this line:

— Replace * with $ORACLE_SID (PV by default).
— Replace N with Y.
The last line should now be:
PV:/opt/oracle/product/9.2.0:Y
5. Save and close the oratab file.
Step 15: Configure the Oracle Listener

Note: Instead of creating the listener.ora file manually, as described in the steps that follow, you can
create it by running the Oracle Net Configuration Assistant utility. See the Oracle Corporation documentation
for information about Net Configuration Assistant.
The Oracle Listener process manages database connection requests from Oracle clients to an Oracle server.
To configure the Oracle Listener:
1. As oracle, change to one of the following directories:

$ cd $TNS_ADMIN
or
$ cd /opt/oracle/product/9.2.0/network/admin
2. Using a text editor, create a text file named listener.ora and enter text as shown in the following
example. Substitute the name of your Oracle server in the HOST= line.

Note that by Oracle convention, the keywords in this file are in uppercase but uppercase is not required.
# listener.ora network configuration file in directory
# /opt/oracle/product/9.2.0/network/admin
LISTENER=
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = delphi) (PORT = 1521))
)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC))
)
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /opt/oracle/product/9.2.0)
(PROGRAM = extproc)
)
(SID_DESC =
(GLOBAL_DBNAME = PV.WORLD)
(SID_NAME = PV)
(ORACLE_HOME = /opt/oracle/product/9.2.0)
)
)

4. Depending on your operating system, change to the following directory:
Solaris systems:
$ cd /var/opt/oracle
AIX systems:
$ cd /etc
5. Edit the lsnrtab file and add a line in the following format to the end of the file (after the initial comments):
LISTENER:value_of_ORACLE-HOME:Y
For example:
LISTENER:/opt/oracle/product/9.2.0:Y
In this syntax, LISTENER is the name of the listener process.
7. 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 for a successful completion
message.

Step 16: Configure the Oracle Net Client

In this step, you configure an Oracle Net client by setting up the TNS (Transport Network Substrate) service
names for your Netcool/Proviso database instance and the SilverStream instance.
To set up the TNS service names:
1. As oracle, change to one of the following directories:

$ cd $TNS_ADMIN
or
$ cd /opt/oracle/product/9.2.0/network/admin
2. Create the sqlnet.ora file, which will manage Oracle network operations. You must create an
sqlnet.ora file for both Oracle server and Oracle client installations. Follow these steps:
2-a. Using a text editor, create an sqlnet.ora file.
2-b. Add the following lines to this file:
NAMES.DIRECTORY_PATH=(TNSNAMES)
NAMES.DEFAULT_DOMAIN=WORLD
For example:
# sqlnet.ora network configuration file in
Note: If you do not use WORLD as the DEFAULT_DOMAIN value, make sure you enter the same value
for DEFAULT_DOMAIN in both sqlnet.ora and tnsnames.ora.
2-c. Write and quit the file.

3. Create the tnsnames.ora file, which maintains the relationships between logical node names and physical
locations of Oracle Servers in the network.
Note: You must configure a tnsnames.ora file for both Oracle server and Oracle client installations.
However, the tnsnames.ora file for Client installations should not have the
EXTPROC_CONNECTION_DATA section.

Follow these steps:

3-a. Using a text editor, create the tnsnames.ora file.
3-b. Enter lines similar to the following example, using the actual name of your Oracle server in the
HOST=delphi line.
# tnsnames.ora network configuration file in

#
# 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)
)
)
SILVERMASTER.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
Note: Indents in this file must be preserved.

Note the following:

— You will use the value in the INSTANCE_NAME field as the TNS entry when installing
Netcool/Proviso DataMart.
— IBM strongly recommends that you include the line (ENABLE=BROKEN) in the PV.WORLD
entry, as shown in the example. This parameter setting prevents CME processes from hanging in the
event that the CME is disconnected from the database before results are returned to the CME.
— If configuring tnsnames.ora for a server installation, be sure to append the same domain suffix to
all entries including EXTPROC_CONNECTION_DATA that you specified for the
NAMES.DEFAULT_DOMAIN entry in the sqlnet.ora file. That is, append.WORLD to each entry.
— The last set of lines configures the SilverMaster TNS server name.
3-c. Write and quit the file.
4. 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 following syntax:
tnsping Net_service_name 10
For example:
$ tnsping PV 10
Note: If either test is not successful, check your configuration and retest.
5. Test the SilverMaster TNS service name configuration by entering the following command:
$ tnsping silvermaster 10
Installing the Oracle Client (Patch Version 9.2.0.8)

You must install Oracle client software on each system where you plan to install a Netcool/Proviso component,
with the exception of the system where you installed the Oracle server.
Netcool/Proviso components require two different patch versions of the client software. The DataView
component requires version 9.2.0.6. All other components require version 9.2.0.8.
If you are installing DataView on the same system where you are installing another Netcool/Proviso component,
you must install patch version 9.2.0.6 in addition to other Oracle client or server components otherwise installed.
For example, if you are installing DataView on the same system where you installed the Oracle server, you must
also install the Oracle client with the patch version 9.2.0.6. If you are installing DataView on the same system as
another Netcool/Proviso component and the Oracle server is not located on the system, you must install two
instances of the Oracle client, one with patch version 9.2.0.6 and one with version 9.2.0.8.
When you configure the deployment properties for the DataView component in the topology editor, you must
make sure to specify the home directory of the patch 9.2.0.6 install as the Oracle home directory.
The instructions in this section contain information on installing the Oracle client software with the version
9.2.0.8 patch. For instructions on installing the software with the 9.2.0.6 patch, see Installing the Oracle Client (Patch
Version 9.2.0.6).

If you are installing the Oracle client on a Linux host, follow the directions in Pre-Installation Tasks for Linux Systems
before beginning the Oracle installation.
Pre-Installation Tasks for Linux Systems

Netcool/Proviso supports SNMP DataLoad collectors on Linux systems.
Before installing Oracle client on your Linux host, perform the following tasks:
1. Check the Linux version, by entering the following command at a system prompt:
uname -a
You should see output similar to the following:
Linux pmglnx2.usma.ibm.com 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007
i686 i686 i386 GNU/Linux
To verify the processor type, run the following command:
uname –p
The result should be:
i686
2. Run the command rpm -q for each of the following packages to verify that they are installed:
— compat-db
— compat-gcc-32
— compat-gcc-32-c++
— compat-libgcc-296
— compat-libstdc++-296
— gcc
— gcc-c++
— gnome-libs
— gnome-libs-devel
— libaio-devel
— libaio
— make
— openmotif21
— xorg-x11-deprecated-libs-devel
— xorg-x11-deprecated-libs
If any of these packages are missing, install them.
3. By default, FTP is not enabled on Linux systems. To enable FTP on your Linux host, run the following
command as root:
/etc/init.d/vsftpd start

4. As root, run the following command:

rpm -ihv filename
where filename is one of the following:
— compat-libcwait-2.1-1.i386.rpm
— compat-oracle-rhel4-1.0-5.i386.rpm
You are now ready to install the Oracle client on your Linux host. The scripts for installing the Oracle client are
in ImageDir/RHEL/DataBase/instance, where ImageDir is the directory that contains the extracted
Netcool/Proviso installation package. For example:
/export/home/pvuser/443/RHEL/DataBase/instance

2. Run the configure_client script to create a local oracle account (see Step 6: Run the Oracle Server Configuration
Script on page 56).
3. Re-enable NIS.
Important: The local Oracle account should be used before the NIS oracle user.

Download each Oracle installation file to a separate directory on your target server’s hard disk or to a network-
accessible shared disk.
To download the files to disk:

3. Create subdirectories named Diskn for each Oracle distribution file and create one Patch subdirectory. The
5. Locate the appropriate upgrade patch file or files for your version of Oracle on the Oracle Web site and
download it to your /var/tmp/Oraclen directory. See the Netcool/Proviso Configuration Recommendations
document for the list of supported patch files.

6. (Optional) If the patch file or files you download contain a tar file distributed in zip file format, unzip the tar
file from the zip file. For example:
7. Untar the patch delivery file or files into your Patch subdirectory. For example:
/var/tmp/Oraclen
Disk1
Disk2
Disk3
Patch
Disk1
See your database administrator to determine whether there are any company-specific requirements for installing
Oracle in your environment.
Step 3: Run the Oracle Client Configuration Script

The Oracle client configuration script is a shell script that creates the environment for the client software
installation on the local system. This script is named configure_client and is located with the
Netcool/Proviso files that you obtained in Step 3: Download the Netcool/Proviso Distribution to Disk on page 53. If you
are performing this step as part of an upgrade procedure, make sure that you run the configuration script
provided with the target version of Netcool/Proviso. For example, if you are upgrading from version 4.4.1 to
4.4.3, make sure that you are using the configuration script provided with the version 4.4.3 distribution.
The client configuration script makes the following changes to the local system:
• Adds the dba and oinstall groups to /etc/group.
• Adds the Solaris login name oracle, whose primary group membership is dba, and secondary group
membership is oinstall.
• Creates the Oracle client directory structure. When you create the environment for patch version 9.2.0.8, the
default location for this directory structure is $ORACLE_BASE/product/9.2.0. You specify this directory
as the target location when you install the Oracle client.

To configure the Oracle installation environment:
the Oracle client files installed. The default installation directory is /opt/oracle.
For example:
Note: The configure_client script places this variable into the oracle login name’s .profile file.
# env | grep ORA
Solaris systems:
AIX systems:
where:
3. Run the Oracle configuration script using the following command:
# ./configure_client
--------------------------------------------------
configure_client
Setting the Oracle client environment
<Current Date>
--------------------------------------------------
OS ........... : [ SunOS 5.9 Generic ]
Host ......... : [ corinth ]
DBA group ................. : [ dba ]

Menu :
1. Set current release 9.2.0.
3. Add 9.2.0.6 client support.
0. Exit
Choice:


The script creates the dba and oinstall groups, and the ORACLE_BASE directory, unless they already exist.
** WARNING
** [ /opt/oracle ]
**
If prompted, type y and press Enter.

** WARNING
**
If prompted, type y to create the oracle user and press Enter.

--> Created.
[ /opt/oracle/product/9.2.0 ] --> Created.
Checking for oracle .profile file --> Created.
5. Press Enter to continue. The configure_client main screen is displayed.

6. Type 0 and press Enter to exit the script.

The configure_client script you ran in the previous section creates the oracle login name. You must assign a
password for the oracle login name to maintain system security, and because upcoming installation scripts expect a
password to be already set.
To set the password:
1. As root, enter:
# passwd oracle



Solaris systems:
# cd /var/tmp/cdproviso/SOLARIS/DataBase/SOLnum/instance/ora_installer
AIX systems:
where:
You must use the same ORACLE_BASE setting that you specified in Step 3: Run the Oracle Client Configuration
Script on page 76.
Step 6: Verify the PATH and Environment for the Oracle Login Name
Before proceeding to install Oracle client files, make sure the /usr/ccs/bin directory is in the PATH

If you are using the su command to become oracle, use a hyphen as the second argument so the oracle
name’s login environment is loaded:
# su - oracle
2. Verify that the environment variable ORACLE_BASE is set by entering the following command:
$ env | grep ORA
If the response does not include ORACLE_BASE=/opt/oracle, stop and make sure the .profile file was
set for the oracle user as described in Step 6: Run the Oracle Server Configuration Script on page 56.
$ echo $PATH

$ export PATH
Step 7: Install the Oracle Client

The Oracle installation script is a shell script that you can use to install the Oracle server, Oracle client software,
or patches to existing installations of the Oracle server and client. This script is named perform_oracle_inst
and is located with the Netcool/Proviso files that you obtained in Step 3: Download the Netcool/Proviso Distribution to
Disk on page 53. This script is provided by IBM as part of the Netcool/Proviso installation package.
An Oracle client installation is not usable until the following Net configuration files are configured and installed:
• tnsnames.ora
• sqlnet.ora
You will configure these files in later steps.
To install the Oracle client:

Solaris systems:
AIX systems:
where:


--------------------------------------------------
perform_oracle_inst
<Current Date>
--------------------------------------------------
OS ........... : [ SunOS 5.9 Generic ]
Host ......... : [ delphi ]

Installation type.......... : [ Client ]
c) DBA group ..................... : [ dba ]
[ ]
Menu :
1. Set current release to: 9.2.0
3. Perform install
0. Exit
Choice :
3. Enter f at the Choice prompt and press Enter.

4. Enter the full path to the directory you created to hold the Oracle distribution in Step 2: Download the Oracle
Distribution and Patch to Disk on page 52. For example:
Choice: f
5. Edit any other menu settings as necessary. Make sure that the values for ORACLE_BASE and
ORACLE_HOME correspond to the locations you specified when you ran the Oracle client configuration
script.
6. To start the Oracle installation, type 3 at the Choice prompt and press Enter.
7. The installation script checks the environment, then asks whether you want to perform the installation. Type
Y at the Choice prompt and press Enter. The installation script starts installing Oracle and displays a series
of status messages.
8. When the installation process completes, the installation displays a success message. Write down the log file
location to aid in troubleshooting if there is an installation error.
11. Perform the steps in Step 8: Run the root.sh Script on page 82.


After successfully running an Oracle client installation, you must run the root.sh script.
Note: To view the messages and screens that are displayed by the script, see the corresponding step in the Oracle
server installation (page 65).
1. Log in as root. Set and export the DISPLAY environment variable.

2. Change to the directory where Oracle client files were installed. (This is the value of the ORACLE_HOME
# cd /opt/oracle/product/9.2.0
./root.sh
The default entry may be NFS-mounted at your site so that it can be shared among several Sun workstations
and may thereby be write-protected. If so, enter the location of a machine-specific alternate bin directory.
(You may have to create this alternate directory first at a shell prompt.) For example, enter:
/usr/corinth/bin.
5. The script displays a series of informational messages and runs to completion with no further prompts.

After you install the Oracle client software, you must install patch version 9.2.0.8.
structure.
1. Follow the instructions to run the perform_oracle_inst script, as shown in Step 12: Install Oracle
Patches on page 66. Go through the menus as described in that section, with the following changes:
1-a. Enter 2 at the Choice prompt and press Enter until the Installation type field is set to Patch.
1-b. Type f at the Choice prompt and press Enter.
1-c. At the Choice prompt, type the full path to the patch directory you created in Download the Oracle
Distribution and Patch to Disk to hold the client patch 9.2.0.8 contents. For example:
Choice: f
Enter new value for CD directory: /var/tmp/Oracle9/Patch
2. Type 3 at the Choice prompt and press Enter. The script checks the environment 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 of messages much like the ones shown during installation of the base
release.

4. Watch the script’s messages for success entries.
Note: If the script shows unsuccessful installation messages, check the installation log file named in the message.
Correct the error conditions identified in the log file, then rerun the patch installation and double-check all menu
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, because messages from several installation
threads are written to the same screen. If the installation has paused, type C to continue.

Next, you configure the Oracle Net client by setting up the TNS (Transport Network Substrate) service names
for your Netcool/Proviso database instance and SilverStream instance. You must perform this step for each
instance of the Oracle client software that you installed on the system.
You must configure sqlnet.ora and tnsnames.ora files for both Oracle server and Oracle client
installations. However, the tnsnames.ora file for client installations should not have the
If you are installing DataView and one or more other Netcool/Proviso components on the same system, you
must make sure that the tnsnames.ora and sqlnet.ora files for each set of client software are identical. The
easiest way to do this is to create these files when you are configuring the first client instance for Net and then to
copy it to the corresponding directory when you configure the second instance.
Create the sqlnet.ora File

The sqlnet.ora file manages Oracle network operations. You can create a new sqlnet.ora file, or FTP the
file from your Oracle server.

$ cd $ORACLE_HOME/network/admin
2. Using a text editor, create the sqlnet.ora file and add the following lines to it:
For example:
3. Write and quit the sqlnet.ora file.

Create the tnsnames.ora File

The tnsnames.ora file maintains the relationships between logical node names and physical locations of Oracle
servers in the network. You can create a new tnsnames.ora file, or FTP the file from your Oracle server.
1. Using a text editor, create the tnsnames.ora and add the following lines:

#
PV.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
Substitute the name of your Oracle server in the HOST= line.

Note the following:
— You will use the value in the INSTANCE_NAME field as the TNS entry when installing DataMart.
— If you reconfigure the Oracle client to connect to a different Oracle database in another Netcool/Proviso
installation, be sure you update the HOST entry in the tnsnames.ora file, then restart the Oracle client.

Test the Oracle Net Configuration

To test the Oracle Net configuration:
1. As oracle, enter a command with the following syntax:

For example:
tnsping PV.WORLD 10
2. Test again, using the same Net instance name without the domain suffix:
tnsping PV 10
Installing the Oracle Client (Patch Version 9.2.0.6)

You must install Oracle client software with the patch version 9.2.0.6 on the system where you are installing the
Netcool/Proviso DataView component.
If you are installing DataView on the same system where you are installing another Netcool/Proviso component,
you must install patch version 9.2.0.6 in addition to other Oracle client or server components otherwise installed.
For example, if you are installing DataView on the same system where you installed the Oracle server, you must
also install the Oracle client with the patch version 9.2.0.6. If you are installing DataView on the same system as
another Netcool/Proviso component and the Oracle server is not located on the system, you must install two
instances of the Oracle client, one with patch version 9.2.0.6 and one with version 9.2.0.8.
When you configure the deployment properties for the DataView component in the topology editor, you must
make sure to specify the home directory of the patch 9.2.0.6 install as the Oracle home directory.
If you are installing the Oracle client on a Linux host, follow the directions in Pre-Installation Tasks for Linux Systems
before beginning the Oracle installation.
Pre-Installation Tasks for Linux Systems

Netcool/Proviso supports SNMP DataLoad collectors on Linux systems.
Before installing Oracle client on your Linux host, perform the following tasks:
1. Check the Linux version, by entering the following command at a system prompt:
uname -a
You should see output similar to the following:
Linux pmglnx2.usma.ibm.com 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007
i686 i686 i386 GNU/Linux

To verify the processor type, run the following command:

uname –p
The result should be:
i686
2. Run the command rpm -q for each of the following packages to verify that they are installed:
— compat-db
— compat-gcc-32
— compat-gcc-32-c++
— compat-libgcc-296
— gcc
— gcc-c++
— gnome-libs
— gnome-libs-devel
— libaio-devel
— libaio
— make
— openmotif21
— xorg-x11-deprecated-libs-devel
— xorg-x11-deprecated-libs
If any of these packages are missing, install them.
3. By default, FTP is not enabled on Linux systems. To enable FTP on your Linux host, run the following
command as root:
/etc/init.d/vsftpd start
rpm -ihv filename
where filename is one of the following:
— compat-libcwait-2.1-1.i386.rpm
— compat-oracle-rhel4-1.0-5.i386.rpm
You are now ready to install the Oracle client on your Linux host. The scripts for installing the Oracle client are
in ImageDir/RHEL/DataBase/instance, where ImageDir is the directory that contains the extracted
Netcool/Proviso installation package. For example:
/export/home/pvuser/443/RHEL/DataBase/instance


2. Run the configure_client script to create a local oracle account (see Step 6: Run the Oracle Server Configuration
Script on page 56).
3. Re-enable NIS.
Important: The local Oracle account should be used before the NIS oracle user.

Download each Oracle installation file to a separate directory on your target server’s hard disk or to a network-
accessible shared disk.
To download the files to disk:

3. Create subdirectories named Diskn for each Oracle distribution file and create one Patch subdirectory. The
5. Locate the appropriate upgrade patch file or files for your version of Oracle on the Oracle Web site and
download it to your /var/tmp/Oraclen directory. See the Netcool/Proviso Configuration Recommendations
document for the list of supported patch files.
6. (Optional) If the patch file or files you download contain a tar file distributed in zip file format, unzip the tar
file from the zip file. For example:

7. Untar the patch delivery file or files into your Patch subdirectory. For example:
/var/tmp/Oraclen
Disk1
Disk2
Disk3
Patch
Disk1
See your database administrator to determine whether there are any company-specific requirements for installing
Oracle in your environment.
Step 3: Run the Oracle Client Configuration Script

The Oracle client configuration script is a shell script that creates the environment for the client software
installation on the local system. This script is named configure_client and is located with the
Netcool/Proviso files that you obtained in Step 3: Download the Netcool/Proviso Distribution to Disk on page 53.
The client configuration script makes the following changes to the local system:
• Adds the dba and oinstall groups to /etc/group.
• Adds the Solaris login name oracle, whose primary group membership is dba, and secondary group
membership is oinstall.
• Creates the Oracle client directory structure. When you create the environment for patch version 9.2.0.6, the
default location for this directory structure is $ORACLE_BASE/product/9.2.0.6. You specify this
directory as the target location when you install the Oracle client.
To configure the Oracle installation environment:
the Oracle client files installed. The default installation directory is /opt/oracle.
For example:
Note: The configure_client script places this variable into the oracle login name’s .profile.9206 file. This
login script is not automatically executed when you log in as the oracle user. You must manually force the operating
system to run this script by entering . /opt/oracle/.profile.9206 when you log in as the oracle user.
# env | grep ORA
Solaris systems:

AIX systems:
where:
3. Run the Oracle configuration script using the following command:
# ./configure_client
--------------------------------------------------
configure_client
Setting the Oracle client environment
<Current Date>
--------------------------------------------------
OS ........... : [ SunOS 5.9 Generic ]
Host ......... : [ corinth ]
DBA group ................. : [ dba ]

Menu :
1. Set current release 9.2.0.
3. Add 9.2.0.6 client support.
0. Exit
Choice:

The script creates the dba and oinstall groups, and the Oracle directories, unless they already exist.
** WARNING
** [ /opt/oracle ]
**
If prompted, type y and press Enter.

** WARNING
**

If prompted, type y to create the oracle user and press Enter.

--> Created.
[ /opt/oracle/product/9.2.0.6 ] --> Created.
Checking for oracle .profile.9206 file --> Created.
5. Press Enter to continue. The configure_client main screen is displayed.

6. Type 0 and press Enter to exit the script.

The configure_client script you ran in the previous section creates the oracle login name. If the this user does
not already exist on the system, you must assign a password for the oracle login name to maintain system security,
and because upcoming installation scripts expect a password to be already set.
To set the password:
1. As root, enter:
# passwd oracle


Solaris systems:
# cd /var/tmp/cdproviso/build_num/SOLARIS/DataBase/SOLnum/instance/ora_installer
AIX systems:
# cd /var/tmp/cdproviso/build_num/AIX5/DataBase/instance/ora_installer
where:
— build_num is the build number for Netcool/Proviso. For example, 4.4.3.0.28.
You must use the same ORACLE_BASE setting that you specified in Step 3: Run the Oracle Client Configuration
Script on page 76.


Step 6: Verify the PATH and Environment for the Oracle Login Name
Before proceeding to install Oracle client files, make sure the /usr/ccs/bin directory is in the PATH

Solaris systems:
AIX systems:
where:
3. Run the environment clean-up script by entering the following command:
./reset_ora_env
4. Force the operating system to run the .profile.9206 login script by entering the following command:
. /opt/oracle/.profile.9206
5. Verify that the environment variable ORACLE_BASE is set by entering the following command:
$ env | grep ORA
$ echo $PATH
$ export PATH

Step 7: Install the Oracle Client

The Oracle installation script is a shell script that you can use to install the Oracle server, Oracle client software,
or patches to existing installations of the Oracle server and client. This script is named perform_oracle_inst
and is located with the Netcool/Proviso files that you obtained in Step 3: Download the Netcool/Proviso Distribution to
Disk on page 53. This script is provided by IBM as part of the Netcool/Proviso installation package.
Note: When you install the Oracle client for use with the version 9.2.0.6 patch, you must run the installation
script with the -install9206 option.
An Oracle client installation is not usable until the following Net configuration files are configured and installed:
• tnsnames.ora
• sqlnet.ora
You will configure these files in later steps.
To install the Oracle client:

Solaris systems:
AIX systems:
where:
$ ./perform_oracle_inst -install9206
The installer prints a message to the screen that notifies you that you have chosen to install the client software
as required to operate with patch version 9.2.0.6.
3. Press Enter.


--------------------------------------------------
perform_oracle_inst
<Current Date>
--------------------------------------------------
OS ........... : [ SunOS 5.9 Generic ]
Host ......... : [ delphi ]

Installation type.......... : [ Client ]
c) DBA group ..................... : [ dba ]
[ ]
Warning: You are current in 9.2.0.6 installation mode
Menu :
1. Set current release to: 9.2.0
3. Perform install
0. 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 Step 2: Download the Oracle
Distribution and Patch to Disk on page 87. For example:
Choice: f
6. Edit any other menu settings as necessary. Make sure that the values for ORACLE_BASE and
ORACLE_HOME correspond to the locations you specified when you ran the Oracle client configuration
script. The default value of ORACLE_BASE is /opt/oracle. The default value of ORACLE_HOME is
/opt/oracle/product/9.2.0.6.
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. The installation script starts installing Oracle and displays a series
of status messages.
9. When the installation process completes, the installation displays a success message. Write down the log file
location to aid in troubleshooting if there is an installation error.


12. Perform the steps in Step 8: Run the root.sh Script on page 94.

After successfully running an Oracle client installation, you must run the root.sh script.
Note: To view the messages and screens that are displayed by the script, see the corresponding step in the Oracle
server installation (page 65).
1. Log in as root. Set and export the DISPLAY environment variable.

2. Change to the directory where Oracle client files were installed. (This is the value of the ORACLE_HOME
# cd /opt/oracle/product/9.2.0.6
./root.sh
The default entry may be NFS-mounted at your site so that it can be shared among several Sun workstations
and may thereby be write-protected. If so, enter the location of a machine-specific alternate bin directory.
(You may have to create this alternate directory first at a shell prompt.) For example, enter:
/usr/corinth/bin.
5. The script displays a series of informational messages and runs to completion with no further prompts.

After you install the Oracle client software, you must install patch version 9.2.0.6.
structure.
1. Follow the instructions to run the perform_oracle_inst script with the -install9206 option, as
shown in Step 7: Install the Oracle Client on page 92. Go through the menus as described in that section, with the
following changes:
1-a. Enter 2 at the Choice prompt and press Enter until the Installation type field is set to Patch.
1-b. Type f at the Choice prompt and press Enter.
1-c. At the Choice prompt, type the full path to the patch directory you created in Download the Oracle
Distribution and Patch to Disk to hold the client patch 9.2.0.6 contents. For example:
Choice: f
Enter new value for CD directory: /var/tmp/Oracle9/Patch
2. Type 3 at the Choice prompt and press Enter. The script checks the environment 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 of messages much like the ones shown during installation of the base
release.
4. Watch the script’s messages for success entries.
Note: If the script shows unsuccessful installation messages, check the installation log file named in the message.
Correct the error conditions identified in the log file, then rerun the patch installation and double-check all menu
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, because messages from several installation
threads are written to the same screen. If the installation has paused, type C to continue.

Next, you configure the Oracle Net client by setting up the TNS (Transport Network Substrate) service names
for your Netcool/Proviso database instance and SilverStream instance. You must perform this step for each
instance of the Oracle client software that you installed on the system.
You must configure sqlnet.ora and tnsnames.ora files for both Oracle server and Oracle client
installations. However, the tnsnames.ora file for client installations should not have the
If you are installing DataView and one or more other Netcool/Proviso components on the same system, you
must make sure that the tnsnames.ora and sqlnet.ora files for each set of client software are identical. The
easiest way to do this is to create the files when you are configuring the first client instance for Oracle Net and
then to copy it to the corresponding directory when you configure the second instance.
Create the sqlnet.ora File

The sqlnet.ora file manages Oracle network operations. You can create a new sqlnet.ora file, or FTP the
file from your Oracle server.

$ cd $ORACLE_HOME/network/admin
2. Using a text editor, create the sqlnet.ora file and add the following lines to it:
For example:
# /opt/oracle/product/9.2.0.6/network/admin

3. Write and quit the sqlnet.ora file.
Create the tnsnames.ora File

The tnsnames.ora file maintains the relationships between logical node names and physical locations of Oracle
servers in the network. You can create a new tnsnames.ora file, or FTP the file from your Oracle server.
1. Using a text editor, create the tnsnames.ora and add the following lines:

# /opt/oracle/product/9.2.0.6/network/admin
#
PV.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
Substitute the name of your Oracle server in the HOST= line.

Note the following:
— You will use the value in the INSTANCE_NAME field as the TNS entry when installing DataMart.
— If you reconfigure the Oracle client to connect to a different Oracle database in another Netcool/Proviso
installation, be sure you update the HOST entry in the tnsnames.ora file, then restart the Oracle client.

Test the Oracle Net Configuration

To test the Oracle Net configuration:
1. As oracle, enter a command with the following syntax:

For example:
tnsping PV.WORLD 10
2. Test again, using the same Net instance name without the domain suffix:
tnsping PV 10
Next Steps
Once you have installed the prerequisite software, you are ready to begin the actual installation of
Netcool/Proviso. Depending on the type of installation you require, follow the directions in the appropriate
chapter:
• Chapter 3, Installing Netcool/Proviso in a Distributed Environment — Describes how to install Netcool/Proviso in a
distributed production environment.
• Chapter 4, Installing Netcool/Proviso as a Minimal Deployment — Describes how to install Netcool/Proviso as a
minimal deployment, which is used primarily for demonstration or evaluation purposes.

Chapter 3: Installing Netcool/Proviso in a
Distributed Environment
This chapter describes how to install Netcool/Proviso for the first time in a fresh, distributed environment. For
information about installing the Netcool/Proviso components using a minimal deployment, see Chapter 4,
Installing Netcool/Proviso as a Minimal Deployment. For an overview of the graphical user interfaces (GUIs) used to
install Netcool/Proviso, see The Graphical Installation Interface on page 21.
The topics are as follows:
Topic Page
Before You Begin 98
Starting the Launchpad 99
Installing the Topology Editor 100
Starting the Topology Editor 101
Creating a New Topology 102
Adding and Configuring the Netcool/Proviso Components 102
Saving the Topology 110
Starting the Deployer 111
Deploying the Topology 111
Next Steps 114
Before You Begin

Before installing Netcool/Proviso, you must have installed the prerequisite software. For detailed information,
see Chapter 2, Installing and Configuring the Prerequisite Software.
In addition, you must have decided how you want to configure your system. Refer to the following sections:
• Configuring Your Deployment on page 20
• Appendix A, Deployment Considerations on page 176
The general steps used to install Netcool/Proviso are as follows:
1. Start the launchpad.

2. Install the Topology Editor.
3. Start the Topology Editor.
4. Create the topology.

Chapter 3: Installing Netcool/Proviso in a Distributed Environment
5. Add the Netcool/Proviso components.

6. Save the topology to an XML file.
7. Start the deployer.
8. Install Netcool/Proviso 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 been performed. Otherwise, the
installation might fail. See Installing and Configuring the Prerequisite Software on page 46 for information about
tnsping.
Starting the Launchpad

For an overview of the launchpad interface, see The Launchpad on page 22.
To start the launchpad:
1. Log in as root.
2. Set and export the DISPLAY variable (see Setting Up a Remote X Window Display on page 41).
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
Note: The BROWSER command cannot include any spaces around the equal sign.
4. Change directory to the directory where the launchpad resides:

On Solaris systems:
# cd install_dir/build_num/SOLARIS
Example: # cd /export/home/pvuser/443/4.4.3.0.51/SOLARIS
On AIX systems:
# cd install_dir/build_num/AIX
Example: cd /export/home/pvuser/443/4.4.3.0.51/AIX
5. Enter the following command to start the launchpad:
# ./launchpad.sh

Installing the Topology Editor

Only one instance of the Topology Editor can exist in the Netcool/Proviso environment. Install the Topology Editor on the
same system that will host DataMart. If you install DataMart on the same system as the Oracle server, install the
Topology Editor on that same system.
You can install the Topology Editor from the launchpad or from the command line.
To install the Topology Editor:
1. From the launchpad:

1-a. On the launchpad, click the Install Topology Editor option in the list of tasks.
1-b. On the Install Topology Editor page, click the Install Topology Editor link.
From the command line:
1-a. As root, change directory to the directory that contains the Topology Editor installation script. For
example:
# cd ImageDir/topologyEditor/Disk1/InstData/VM
In this syntax, ImageDir is the directory that contains the extracted Netcool/Proviso installation
package. For example:
/export/home/pvuser/443/SOLARIS/Install/SOL9/
topologyEditor/Disk1/InstData/VM
1-b. Enter the following command:
# ./installer.bin
2. The installation wizard opens in a separate window, displaying a welcome page. Click Next.
3. Accept the license agreement, then click Next.
4. Accept the default installation directory (/opt/IBM/proviso), or specify a different one. If you have
previously installed the Topology Editor on this system, the installer does not prompt you for an installation
directory and instead uses the directory where you last installed the application. Click Next to continue.
(/opt/oracle/product/version/jdbc/lib), or click Choose to navigate to another directory.
The Topology Editor uses this location for all components in the topology. You might need to manually
change the directory associated with DataView or other components to accomodate requirements for
different versions of the client software patch. For more information, see Chapter 2, Installing and Configuring
the Prerequisite Software on page 46.
Click Next to continue.
6. Review the installation information, then click Install.
7. When the installation is complete, click Done to close the wizard.
The installation wizard installs the Topology Editor and an instance of the deployer in the following directories:
Interface Directory
Topology Editor install_dir/topologyEditor

For example:
/opt/IBM/proviso/topologyEditor

Interface Directory
Deployer install_dir/deployer
For example:
/opt/IBM/proviso/deployer
The combination of the Topology Editor and the deployer is referred to as the primary deployer. For more
information, see Primary Versus Secondary Deployers on page 35.
Note: To uninstall the Topology Editor, follow the instructions in Uninstalling the Topology Editor on
page 174. Do not simply delete the /opt/IBM directory! Doing so will cause problems when you try to reinstall
the Topology Editor.
If the /opt/IBM directory is accidentally deleted, perform the following steps:
1. Change to the /var directory.

2. Rename the hidden file .com.zerog.registry.xml (for example, rename it to
.com.zerog.registry.xml.backup).
3. Reinstall the Topology Editor.
4. Rename the backup file to the original name (.com.zerog.registry.xml).
Starting the Topology Editor

After you have installed the Topology Editor, you can invoke it from either the launchpad or from the command
line.
To start the Topology Editor from the launchpad:
1. If the Install Topology Editor page is not already open, click the Install Topology Editor option in the list
of tasks to open it.
2. On the Install Topology Editor page, click the Start Topology Editor link.
To start the Topology Editor from the command line:
1. As root, change directory to the directory in which you installed the Topology Editor. For example:
# cd /opt/IBM/proviso/topologyEditor
# ./topologyEditor
The Topology Editor opens, as shown in Figure 4 on page 24.
Note: If your DISPLAY environment variable is not set, the Topology Editor will fail with a Java assertion
message (core dump).

Creating a New Topology

To create a new topology:
1. In the Topology Editor, select Topology > Create new topology. The New Topology window is displayed.
2. Enter the number of resources to be monitored by Netcool/Proviso. The default value is 10000.
3. Click Finish.
The Topology Editor creates the following entities:
• In the Logical view, three items are listed: Netcool/Proviso Topology, DataChannels, and DataMarts.
• In the Physical view, there is a new Hosts folder.
The size of your deployment affects the database sizing. For more information, see Set the System Parameters (Solaris
Only) on page 55. For information about deployment sizes and performance, see the Netcool/Proviso TechNote:
Performance Guidelines for Netcool/Proviso 4.4.x document.
Adding and Configuring the Netcool/Proviso Components

Next, you must add and configure the individual Netcool/Proviso components:
• Step 1,Add the Hosts
• Step 2,Add a Database Configurations Component
• Step 3,Add a DataMart
• Step 5,Add a DataView
• Step 6,Add the DataChannel Administrative Components
• Step 7,Add a DataChannel
• Step 8,Add a Collector
• Step 4,Add a Discovery Server
Step 1: Add the Hosts

The first step is to specify all the machines that will host Netcool/Proviso components. Specify the machine that
hosts the Oracle server as the first host, then add other hosts as needed.
Each host that you define has an associated property named PV user that specifies the default operating system
user for all Netcool/Proviso components installed on the system. You can override this setting in the Advanced
Properties tab when you set the deployment properties for individual components (for example, DataMart and
DataView). This allows you to install and run different components on the same system as different users.
DataChannel components always use the default user associated with the host.
The user account used to transfer files using FTP or SCP/SFTP during installation is always the PV user defined
at the host level, rather than component level.

To add a host to the topology:
1. 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 first host you specify must be the machine on which the
database is located.
The fields are as follows:
— Host name — Enter the name of the host (for example, delphi).
— Operating system — Specifies the operating system (for example, SOLARIS). This field is filled in for
you.
Note: The Netcool/Proviso deployer does not support hybrid configurations. For example, if the database host
is a Solaris system, the entire topology must be deployed on the Solaris platform. The Topology Editor will enforce
this rule, by forcing all the other components to be targeted to the same operating system as the database component.
The one exception to this rule is DataView: it is supported only on Solaris systems. Therefore, if you deploy
Netcool/Proviso on an AIX system, you will be able to deploy DataView on Solaris.
— Oracle home — Specifies the default ORACLE_HOME directory for all Netcool/Proviso components
installed on the system (by default, /opt/oracle/product/9.2.0).
You specified this directory when you installed Oracle server or client components on the system. If
you installed Oracle components in more than one directory (for example, if you installed two instances
of the client software to accomodate DataView and another Netcool/Proviso component on the same
system), you must override this value when you set deployment properties for the DataView
component. See Add a DataView on page 106 for more information.
— PV user — Specifies the default Netcool/Proviso user (for example, pvuser) for all Netcool/Proviso
components installed on the system.
— PV user password — Specifies the password for the default Netcool/Proviso user (for example, PV).
Click Finish to create the host. The Topology Editor adds the host under the Hosts folder in the Physical
view.
3. In the Physical view, select the new host to view its properties in the Properties view. You must enter values
for any properties that have red Xs (for missing or incorrect values). See the Netcool/Proviso Properties Reference
for the complete list of properties for this component. For information about changing the value of a
property, see Changing a Property Value on page 28.
4. Repeat for all the hosts needed for your deployment (for example, athens, corinth, and sparta).
Note: The DataChannel properties will be filled in later automatically.
Step 2: Add a Database Configurations Component

The Database Configurations component hosts all the database-specific parameters. You define the parameters
once, and their values are propagated as needed to the underlying installation scripts.
To add a Database Configurations component:
1. In the Logical view, right-click the Netcool/Proviso 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 machine that hosts the Oracle server (for
example, delphi). Select the appropriate host using the drop-down list.

Note: The operating system of the host where you configure the Database Configurations component determines
the main platform for the entire Netcool/Proviso deployment. This means that you should install all the other
main components (DataView, DataMart, and DataChannel) on machines with the same operating system. The
Topology Editor enforces this constraint by listing only those hosts with the same operating system used to host the
database.
3. Click Finish to create the component, or click Next to configure the mount points for the database.
To configure the mount points:
3-a. In the mount points window, verify the information that the editor has filled in for you:
* Mount Point Directory Name (for example, /raid_2/oradata)
* Used for Metadata Tablespaces? (A check mark indicates True.)
* Used for Temporary Tablespaces? (A check mark indicates True.)
* Used for Metric Tablespaces? (A check mark indicates True.)
* Used for System Tablespaces and Redo? (A check mark indicates True.)
3-b. To add a new mount point, click Add Mount Point. A new, blank row is added to the window. Fill in
the fields as appropriate for the new mount point.
3-c. Click Back to return to the original page.
3-d. Click Finish to create the component.
The Topology Editor adds the new Database Configurations component to the Logical view.
4. Highlight the Database Configurations component to display its properties. Review the property values to
make sure they are valid. For the complete list of properties for this component, see the Netcool/Proviso
Properties Reference.
The Database Configurations component has the following subelements:
• Channel tablespace configurations
• Database Channels
• Database Clients configurations
• Tablespace configurations
• Temporary tablespace configurations
Note: Before you actually install Netcool/Proviso, verify that both the raid_2/oradata and
raid_3/oradata directory structures have been created, and that the oradata subdirectories are owned
by oracle:dba.
Step 3: Add a DataMart

Netcool/Proviso DataMart is normally installed on the same server on which you installed Oracle server and the
Netcool/Proviso database configuration. However, there is no requirement that forces DataMart to reside on the
database server.
Note the following:
• DataMart components cannot be installed remotely. You must run a secondary deployer on each machine
that will host a DataMart. For more information, see Primary Versus Secondary Deployers on page 35.
• If you are installing DataMart on an AIX system, you must add the JRE to the PATH environment variable
for pvuser. Otherwise, the ProvisoInfo server will not start.

To add a DataMart component:
1. 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 the property values to make sure they
are valid. You can specify an alternate installation user for the DataMart component by changing the values
of the USER_LOGIN and USER_PASSWORD properties in the Advanced Properties tab. For the
complete list of properties for this component, see the Netcool/Proviso Properties Reference.
Event Notification Scripts

When you install the DataMart component, two event notification scripts are installed. The scripts are called as
needed by tablespace size checking routines in Oracle and in Netcool/Proviso, if either routine detects low disk
space conditions on a disk partition hosting a portion of the Netcool/Proviso database. Both scripts by default
send their notifications by e-mail to a local login name.
The two files and their installation locations are as follows:
• 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 for available disk space.
• The script installed as /opt/datamart/bin/notifyDBSpace notifies the login name pvuser of the same
condition. This script is called as needed by the Hourly Loader component of Netcool/Proviso
DataChannel. The loader checks for available disk space before attempting its hourly upload of data to the
database.
Either file can be customized to send its warnings to a different e-mail address on the local machine, to an SMTP
server for transmission to a remote machine, or to send the notices to the local network’s SNMP fault
management system (that is, to an SNMP trap manager). You can modify either script to send notifications to an
SNMP trap, instead of, or in addition to its default e-mail notification.
Step 4: Add a Discovery Server

The Discovery Server is the Netcool/Proviso component responsible for SNMP discovery. You can add a
discovery server for each DataMart defined in the topology.
To add a Discovery Server:
• In the Logical view, right-click the DataMart x folder and select Add Discovery server from the menu.
The Topology Editor displays the new Discovery Server under the DataMart n folder in the Logical view.
Adding Multiple Discovery Servers

If you want to run multiple Discovery Servers on multiple hosts in your environment, you must perform
additional steps at deployment to make sure that each host system contains identical inventory files and identical
copies of the inventory hook script. IBM recomends that you only use identically-configured instances of the
Discovery Server.

The inventory files used by the Discovery Server are configuration files named inventory_elements.txt
and inventory_subelements.txt. These files are located in the $PVMHOME/conf directory of the system
where you install the DataMart component. Some technology packs provide custom sub-elements inventory files
with names different from inventory_subelements.txt that are also used by the Discovery Server.
To add multiple Discovery Servers, do the following:
• Install the primary instance of DataMart and the Discovery Server on one target host system.
• Install and configure any required technology packs on the primary host. You modify the contents of the
inventory files during this step.
• Install secondary instances of DataMart and the Discovery Server on corresponding target host systems.
• Replicate the inventory files from the system where the primary instance of DataMart is running to the
$PVMHOME/conf directory on the secondary hosts. You must also replicate the InventoryHook.sh script
that is located in the $PVMHOME/bin directory and any other files that this script requires.
Step 5: Add a DataView

DataView is supported on Solaris systems only.
Note: To display DataView real-time charts, you must have the Java runtime environment (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:
1. In the Logical view, right-click the Netcool/Proviso Topology folder and select Add DataView from the
menu. The host selection window is displayed.
2. Using the drop-down list of available hosts, select the DataView host (for example, athens).
3. Click Finish.
The Topology Editor adds the new DataView component to the Logical view.
4. Highlight the DataView component to display its properties.
5. Make sure that the ORACLE_HOME property specifies the directory where the appropriate Oracle client
software is installed on the target system. The DataView component requires an instance of the client
software patched to level 9.2.0.6. The default ORACLE_HOME location is
/opt/oracle/product/9.2.0.6. For more information, see Installing the Oracle Client (Patch Version
9.2.0.6) on page 85.
6. Review the other property values to make sure they are valid. You can specify an alternate installation user
for the DataView component by changing the values of the UNIX_DV_USER and UNIX_DV_GROUP
properties in the Advanced Properties tab. For the complete list of properties for this component, see the
Netcool/Proviso Properties Reference.

Step 6: Add the DataChannel Administrative Components

To add DataChannel Administrative components:
1. 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 (for example, corinth).
3. Click Finish.
The Topology Editor adds four new components to the Logical view:
• Channel Manager — Enables you to start and stop individual DataChannels and monitor the state of
various DataChannel programs. There is one Channel Manager for the entire DataChannel configuration.
The Channel Manager components are installed on the first host you specify
• Corba Naming Server — Provides near real-time data to DataView.
• Log Server — Used to store user, debug, and error information.
• Global DataChannel properties — These are the global property values that apply to all DataChannel
components.
Step 7: Add a DataChannel

A DataChannel is a software module that receives and processes network statistical information from both SNMP
and non-SNMP (BULK) sources. This statistical information is then loaded into a database where it can be
queried by SQL applications and captured as raw data or displayed on a portal in a variety of reports.
Typically, collectors are associated with technology packs, a suite of Netcool/Proviso programs specific to a particular
network device or technology. A technology pack tells the collector what kind of data to collect on target devices
and how to process that data. See Installing Technology Packs on page 126 for detailed information about technology
packs.
To add a DataChannel:
1. In the Logical view, right-click the DataChannels folder and select Add DataChannel from the menu. The
Configure the DataChannel window is displayed.
2. Using the drop-down list of available hosts, select the machine that will host the 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 DataChannel always installs and runs as
the default user for the host (by default, pvuser). Review the other property values to make sure they are valid.
For the complete list of properties for this component, see the Netcool/Proviso Properties Reference.
The DataChannel has the following subelements:
• Daily Loader x — Processes 24 hours of raw data every day, merges it together, then loads it into the
database. The loader process provides statistics on metric channel tables and metric tablespaces.
• Hourly Loader x — Reads files output by the Complex Metric Engine (CME) and loads the data into the
database every hour. The loader process provides statistics on metric channel tables and metric tablespaces.

The Topology Editor includes the channel number in the element names. For example, DataChannel 1 would
have Daily Loader 1 and File Transfer Engine 1.
Note: When you add DataChannel x, the Problems view shows that the Input Directories property
for the Hourly Loader is blank. This missing value will automatically be filled in when you add a DataLoad
collector (as described in the next section) and the error will be resolved.
For advanced information about DataChannels, see Appendix B, DataChannels on page 182.
Step 8: Add a Collector

Collectors collect and process raw statistical data about network devices obtained from various network resources.
The collectors send the received data through a DataChannel for loading into the Netcool/Proviso database.
Note that collectors do not need to be on the same machine as the Oracle server and DataMart.
Collector Types
There are two basic types of collectors:
• SNMP collector — Collects data using SNMP polling directly to network services. Specify this collector
type if you plan to install a Netcool/Proviso SNMP technology pack. These technology packs operate in
networking environments where the associated devices on which they operate use an SNMP protocol.
• Bulk DataLoad collector — Imports data from files. The files can have multiple origins, including log files
generated by network devices, files generated by SNMP collectors on remote networks, or files generated by
a non-Netcool/Proviso network management database.
There are two types of bulk collectors:
— 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 install a Netcool/Proviso UBA technology pack,
including Alcatel 5620 NM, Alcatel 5620 SAM, and Cisco CWM.
— BCOL. A bulk Collector that retrieves and interprets the flat file output of network devices or network
management systems. This collector type is not recommended for Netcool/Proviso UBA technology
packs, and is used in custom technology packs.
If you are creating a UBA collector, you must associate it with a specific technology pack. For this reason, IBM
recommends that you install the relevant technology pack before creating the UBA collector. Therefore, you would
perform the following sequence of steps:
1. Install Netcool/Proviso, 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.
4. Redeploy the topology file.
For detailed information about UBA technology packs and the installation process, see Chapter 5, Installing
Technology Packs. Configure the installed pack by following the instructions in the pack-specific user's guide.

Restrictions
• The maximum collector identification number is 999.
• There is no relationship between the channel number and the collector number (that is, there is no predefined
range for collector numbers based on channel number). Therefore, collector 555 could be attached to
DataChannel 7.
• Each database channel can have a maximum of 40 subchannels (and therefore, 40 collectors).
Creating an SNMP Collector

To add an SNMP collector:
1. In the Logical view, right-click the DataChannel x folder. The pop-up menu lists the following options:
— Add Collector SNMP — Creates an SNMP collector.
— Add Collector UBA — Creates a UBA collector. See Chapter 5, Installing Technology Packs for information
about creating this type of collector.
Important: When you create a UBA collector, you must specify which technology pack to associate it with. Therefore,
IBM recommends that you not create the UBA collector first. Instead, install Netcool/Proviso, download and install
the technology pack, modify the deployed topology to load the technology pack and create the UBA collector, then
redeploy the topology. For detailed information on UBA Technology Packs, see Chapter 5, Installing Technology
Packs.
— Add Collector BCOL — Creates a BCOL collector. This collector type is used in custom technology
packs.
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 folder in the Logical view.
5. Highlight the collector to view its properties. The Topology Editor displays both the SNMP collector core
parameters and the SNMP technology pack-specific parameters. The core parameters are configured with all
SNMP technology packs. You can specify an alternate installation user for the SNMP collector by changing
the values of the pv_user, pv_user_group and pv_user_password properties in the Advanced Properties tab.
Review the values for the parameters to make sure they are valid.
For information about the core parameters, see the Netcool/Proviso Properties Reference. For information about
the pack-specific parameters, see the Topology Editor Help (described in Problems View on page 29).
The collector has two components:
• Complex Metric Engine x — Perform calculations on the collected data.
• 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 a collector. As part of routine
maintenance, check the size of this file to prevent it from growing too large.

Note: Your Solaris version can be configured with strict access default settings for secure environments. Strict
FTP access settings might interfere with automatic transfers between a DataChannel subchannel and the
DataLoad server. Check for FTP lockouts in /etc/ftpd/ftpusers, and check for strict FTP rules in
/etc/ftpd/ftpaccess.
Note that the Topology Editor includes the channel and collector numbers in the element names. For example,
DataChannel 1 could have Collector SNMP 1.1, with Complex Metric Engine 1.1 and File Transfer Engine 1.1.
Saving the Topology

When you are satisfied with the infrastructure, verify that all the property values are correct and that any problems
have been resolved, then save the topology to an XML file.
To save the topology as an XML file:
1. 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 to close the file browser window.
3. The file name and path is displayed in the original window. Click Finish to save the file and close the window.
You are now ready to deploy the topology file (see Starting the Deployer on page 111).
Note that until you actually deploy the topology file, you can continue making changes to it as needed by following
the directions in Opening an Existing Topology File. See Chapter 6, Modifying the Current Deployment for more
information about making changes to a deployed topology file.
Opening an Existing Topology File

As you create the topology, you can save the file and update it as needed.
To open a topology file that exists but that has not yet been deployed:
1. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 101).
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 is displayed in the Open Topology window.
Click Finish.
The topology is displayed in the Topology Editor.
4. Change the topology as needed.

Starting the Deployer

The primary deployer is installed on the same machine as the Topology Editor. You first run the topology file on
the primary deployer, and then run secondary installers on the other machines in the distributed environment.
See Primary Versus Secondary Deployers on page 35 for more information about primary and secondary deployers.
Note: Before you start the deployer, verify that all the database tests have been performed. Otherwise, the
installation might fail. See Chapter 2, Installing and Configuring the Prerequisite Software for more information.
Primary Deployer
To run the primary deployer from the Topology Editor:
• Select Run> Run Deployer for Installation.
Note: When you use the Run menu options (Installer or Uninstaller), the deployer uses the last saved topology
file, not the current one. Be sure to save the topology file before using a Run command.
Secondary Deployers
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.
To run a secondary deployer from the command line:
1. As root, change directory to the directory that contains the deployer. For example:
# cd /opt/IBM/proviso/deployer
# ./deployer.bin
See Appendix E, Deployer CLI Options for the list of supported command-line options.
Deploying the Topology

The deployer displays a series of pages to guide you through the Netcool/Proviso 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. For
more information about the deployer interface, see The Deployer on page 34.
Important: By default, Netcool/Proviso uses Monday to determine when a new week begins. If you wish to specify
a different day, you must change the FIRST_WEEK_DAY parameter in the Database Registry using the
dbRegEdit utility. This parameter can only be changed when you first deploy the topology that installs your
Netcool/Proviso environment, and it must be changed BEFORE the Database Channel is installed. For more
information, see the Netcool/Proviso Registry and Space Management Tech Note.
If you need to stop the installation, you can resume it at a later time. For more information, see Resuming a Partially
Successful First-Time Installation on page 40.

To deploy the Netcool/Proviso topology:
1. The deployer displays 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 the correct location. Click Next to continue.
Note: If you start the deployer from within the Topology Editor, this step is skipped.
3. The database access window prompts for the security credentials. Enter the host name (for example, delphi)
and database administrator password (for example, PV), and verify the other values (port number, SID, and
user name). Note that if the database does not yet exist, these parameters must match the values you specified
when you created the database configuration component (see Add a Database Configurations Component on
page 103). Click Next to continue.
4. The node selection window shows the target systems and how the files will be transferred (see Node
Selection on page 36 for an explanation of this window). The table has one row for each machine where at
least one Netcool/Proviso component will be installed.
The default settings are as follows:
— The Enable checkbox is selected. If this option is not selected, no actions will be performed on that
machine.
— The Check prerequisites checkbox is selected, which runs scripts to verify that the prerequisite software
has been installed.
— Remote execution is enabled, using both RSH and SSH.
Remote installation is not supported for the DataMart, DataView, and database components. If you are
installing the components on multiple servers, the remote host for these components will not be
selectable: you must start the deployer locally on that host to install those components. For more
information, see Remote Installation on page 178 and Primary Versus Secondary Deployers on page 35.
— File transfer using FTP is enabled.
If desired, reset the values as appropriate for your deployment.
5. The deployer displays summary information about the installation. Review the information, then click Next.
The deployer displays the table of installation steps (see Installation Steps on page 37 for an overview of the
steps table). Note the following:
— If an installation step fails, see Step Status Values on page 39 for debugging information. Continue the
installation by following the instructions in Resuming a Partially Successful First-Time Installation on page 40.
— Some of the installation steps can take a long time to complete. However, if an installation step fails, it
will fail in a short amount of time.
6. Click Run All to run all the steps in sequence.
7. The deployer prompts you for the location of the setup files. Use the file selection window to navigate to the
top-level directory for your operating system, /ImageDir/OPERATING_SYSTEM to avoid further prompts.
For example:
/export/home/pvuser/443/SOLARIS

Alternatively, you can specify the file locations as prompted. The setup files are located in the following
directories:
Location Default Location
Database setup file /install_dir/OPERATING_SYSTEM/DataBase/

OSVersion/setup
For example:
/export/home/pvuser/443/SOLARIS/DataBase/SOL9/
setup
DataMart setup directory /install_dir/OPERATING_SYSTEM/DataMart/

OSVersion/setup
For example:
/export/home/pvuser/443/SOLARIS/DataMart/SOL9/
setup
DataChannel setup directory /install_dir/OPERATING_SYSTEM/DataChannel/

dcSetup
For example:
/export//home/pvuser/443/SOLARIS/DataChannel/
dcSetup
DataLoad setup directory /install_dir/OPERATING_SYSTEM/DataLoad/dlSetup

For example:
/export//home/pvuser/443/SOLARIS/DataLoad/
dlSetup
exteNd (Silverstream) directory /install_dir/exteNd40k

For example:
/export/home/pvuser/443/exteNd40k
DataView setup directory /install_dir/OPERATING_SYSTEM/DataView/

OSVersion/dvinstaller
For example:
/export//home/pvuser/443/SOLARIS/DataView/SOL9/
dvinstaller
8. When all the steps have completed successfully, click Done to close the wizard.
If you are installing DataView on a separate machine, follow these additional steps to complete the
installation:
9. Start the secondary deployer (see Secondary Deployers on page 111) on the other machine.
Next to continue.
12. A pop-up window asks whether you want to download the topology file. If you want to download the file,
click Yes and then enter the path to your topology file on the first host, or click Choose to navigate to the
correct location. Otherwise, click No.

13. Enter the full path to your topology file on the first host, or click Choose to navigate to the correct location.
14. The database access window prompts for the security credentials. Enter the hostname and password and
verify the other values (port number, SID, and user name). Note that if the database does not yet exist, these
parameters must match the values you specified when you created the database configuration component
(see Add a Database Configurations Component on page 103).
15. The deployer displays a page stating that the environment was successfully downloaded. Click Next.
16. The node selection window shows the target system and how the files will be transferred. Accept the defaults
and click Next.
17. The deployer displays summary information about the installation. Review the information, then click
Install to begin the installation.
The deployer displays some informational messages, then displays the table of installation steps (see
Installation Steps on page 37 for information about this table).
18. Click Run All to run all the installation steps.
Next Steps
The next step is to install the technology packs, as described in Chapter 5, Installing Technology Packs.
Once you have created the topology and installed Netcool/Proviso, it is very easy to make changes to the
environment. Simply open the deployed topology file (loading it from the database), make your changes, and run
the deployer with the updated topology file as input. For more information about performing incremental
installations, see Chapter 6, Modifying the Current Deployment.
Note: After your initial deployment, always load the topology file 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 made your changes, you must deploy the updated topology so that it is propagated to the database. To
make any subsequent changes following this deployment, you must load the topology file from the database again.
To improve performance, IBM recommends that you regularly compute the statistics on metadata tables. You can
compute these statistics by creating a cron entry that executes the dbMgr (Database Manager Utility)
analyzeMetaDataTables command at intervals.
The following example shows a cron entry that checks statistics every hour at 30 minutes past the hour. Note
that the ForceCollection option is set to N, so that statistics will only be calculated when the internal calendar
determines that it is necessary, and not every hour:
0 5 * * * [ -f /opt/DM/dataMart.env ] && [ -x /opt/DM/bin/dbMgr ] && .
/opt/DM/dataMart.env && dbMgr analyzeMetaDataTables A
For more information on dbMgr and the analyzeMetaDataTables command, see the Netcool/Proviso dbMgr
Reference Guide.


Chapter 4: Installing Netcool/Proviso as a
Minimal Deployment
This chapter describes how to install Netcool/Proviso as a minimal deployment. The topics are as follows:
Topic Page
Overview 116
Before You Begin 116
Installing on Solaris Systems 117
Installing on AIX Systems 120
The Post-Installation Script 124
Next Steps 124
Overview
A minimal deployment installation is used primarily for demonstration or evaluation purposes, and installs the product
on the smallest number of machines possible, with minimal user input. This installation type installs all the
Netcool/Proviso components on the local host using a predefined topology file to define the infrastructure.
However, if you are installing a minimal deployment version of Netcool/Proviso on an AIX system, two servers
are used (one AIX system and one Solaris system) because DataView is supported on Solaris systems only. The
minimal deployment installation also installs the MIB-II SNMP technology pack.
When you perform a minimal deployment installation, the Netcool/Proviso components are installed on the
server you’re running the deployer from — with the exception of the DataView component on AIX systems.
Before You Begin

Before installing Netcool/Proviso, you must have installed the prerequisite software.
If you are installing DataView on the same system where you are installing the other Netcool/Proviso
components, as is typical for minimal deployments, you must install the Oracle client software twice, once for
patch version 9.2.0.6 and once for patch version 9.2.0.8.
For detailed information, see Chapter 2, Installing and Configuring the Prerequisite Software.
Note: Before you start the installation, verify that all the database tests have been performed. Otherwise, the
installation might fail. See Installing and Configuring the Prerequisite Software on page 46 for information about
tnsping.

Chapter 4: Installing Netcool/Proviso as a Minimal Deployment
Special Consideration
By default, Netcool/Proviso uses Monday to determine when a new week begins. If you wish to specify a different
day, you must change the FIRST_WEEK_DAY parameter in the Database Registry using the dbRegEdit utility. This
parameter can only be changed when you first deploy the topology that installs your Netcool/Proviso
environment, and it must be changed BEFORE the Database Channel is installed. For more information, see the
Netcool/Proviso Registry and Space Management Tech Note.
Installing on Solaris Systems

This section provides step-by-step instructions for installing Netcool/Proviso on a single Solaris machine.
Step 1: Download the MIB-II Files

The minimal deployment version installs the MIB-II Technology Pack. Before beginning the installation, you
must download the APInstaller and the MIB-II jar files.
Note: Both files must be in the same directory (for example, AP), and no other application jar files should be
present. In addition, you must add the AP directory to the Netcool/Proviso distribution’s directory structure.
See Pre-Installation Setup Tasks on page 129 for information about downloading these files.
Step 2: Start the Launchpad

1. Log in as root.
# BROWSER=/opt/mozilla/mozilla
# export BROWSER

# cd install_dir/SOLARIS
For example:
# cd /export/home/pvuser/443/SOLARIS
# ./launchpad.sh

Step 3: Start the Installation

A minimal deployment installation uses a predefined topology file.
To start the installation on a Solaris system:
1. On the launchpad, click the Install Tivoli Netcool/Proviso 4.4.3 for Minimal Deployment option in the
list of tasks, then click the Install Tivoli Netcool/Proviso 4.4.3 for Minimal Deployment link to start the
deployer.
Alternatively, you can start the deployer from the command line, as follows:
1-a. Log in as root.
1-b. Set and export your DISPLAY variable (see Setting Up a Remote X Window Display on page 41).
1-c. Change directory to the directory that contains the deployer
(root_dir/SOLARIS/Install/SOL9/deployer). For example:
# cd /export/home/pvuser/443/SOLARIS/Install/SOL9/deployer
1-d. Enter the following command:
# ./deployer.bin -Daction=poc
3. Accept the terms of the license agreement, then click Next.
Next to continue.
5. The deployer prompts for the directory in which to install Netcool/Proviso. Accept the default value
(/opt/proviso) or click Choose to navigate to another directory. Click Next to continue.
6. Verify the following additional information about the Oracle database:
— Oracle Base. The base directory for the Oracle installation (for example, /opt/oracle). Accept the
provided path or click Choose to navigate to another directory.
— Oracle Home. The root directory of the Oracle database (for example,
/opt/oracle/product/9.2.0). Accept the provided path or click Choose to navigate to another
directory.
— Oracle Port. The port used for Oracle communications. The default value is 1521.
7. The deployer prompts for the directory where you installed the Oracle client software with patch version
9.2.0.6 on the system. The Oracle client with patch 9.2.0.6 is required by the DataView component. Accept
the provided path or click Choose to navigate to another directory.
8. The node selection window shows the target system and how the files will be transferred. These settings are
ignored for a Solaris minimal deployment installation because all the components are installed on a single
server.

9. The deployer displays summary information about the installation. Review the information, then click Next
to begin the installation.
steps table). Note the following:
installation by following the instructions in Resuming a Partially Successful First-Time Installation on page 40
For example:
directories:

OSVersion/setup
For example:
setup

OSVersion/setup
For example:
setup
DataChannel setup directory /install_dir/OPERATING_SYSTEM/DataChannel/

dcSetup
For example:
/export//home/pvuser/443/SOLARIS/DataChannel/
dcSetup

For example:
/export//home/pvuser/443/SOLARIS/DataLoad/
dlSetup

For example:


For example:
/export//home/pvuser/443/SOLARIS/DataView/SOL9/
dvinstaller
Your installation is complete. See The Post-Installation Script on page 124 for information about the post-installation
script, or Next Steps on page 124 for what to do next.
Installing on AIX Systems

If you are installing a minimal deployment version of Netcool/Proviso on an AIX system, two servers are used:
an AIX system and a Solaris system. The AIX server will host the database, DataMart, DataChannel, DataLoader
and the technology pack installation. The Solaris server will host DataView and the SilverStream component.
Step 1: Download the MIB-II Files

The minimal deployment version installs the MIB-II Technology Pack. Before beginning the installation, you
must download the APInstaller and the MIB-II jar files.
Note: Both files must be in the same directory (for example, AP), and no other application jar files should be
present. In addition, you must add the AP directory to the Netcool/Proviso distribution’s directory structure.
See Pre-Installation Setup Tasks on page 129 for information about downloading these files.
Step 2: Start the Launchpad

1. Log in as root.
# BROWSER=/usr/mozilla/firefox/firefox
# export BROWSER

# cd install_dir/AIX
For example:
# cd /export/home/pvuser/443/AIX


# ./launchpad.sh
Step 3: Install the Components on the AIX System

A minimal deployment installation uses a predefined topology file.
To perform a minimal deployment installation on an AIX system:
1. On the launchpad, click the Install Tivoli Netcool/Proviso 4.4.3 for Minimal Deployment option in the
list of tasks, then click the Install Tivoli Netcool/Proviso 4.4.3 for Minimal Deployment link to start the
deployer.
Alternatively, you can start the deployer from the command line, as follows:
1-c. Change directory to the directory that contains the deployer
(root_dir/version/AIX/Install/deployer). For example:
# cd /export/home/pvuser/443/AIX/Install/deployer
3. Accept the terms of the license agreement, then click Next.
Next to continue.
5. The deployer prompts for the directory in which to install Netcool/Proviso. Accept the default value
(/opt/proviso) or click Choose to navigate to another directory. Click Next to continue.
6. Verify the following additional information about the Oracle database:
— Oracle Base. The base directory for the Oracle installation (for example, /opt/oracle). Accept the
provided path or click Choose to navigate to another directory.
— Oracle Home. The root directory of the Oracle database (for example,
/opt/oracle/product/9.2.0). Accept the provided path or click Choose to navigate to another
directory.
— Oracle Port. The port used for Oracle communications. The default value is 1521.
7. Enter information for the Solaris host where the DataView components will be installed.
8. The node selection window shows the target system and how the files will be transferred. The default values
are as follows:
— Remote execution is enabled, using both RSH and SSH
— File transfer using FTP is enabled
For AIX installations, two rows are listed: one for the Solaris system and one for the AIX system. Enable
only the AIX row. (Because DataView and the SilverStream component do not support remote installation,
you must install them separately on the Solaris system.)

The deployer displays the table of installation steps (see Installation Steps on page 37 for information about
the steps table). Note the following:
installation by following the instructions in Resuming a Partially Successful First-Time Installation on page 40.
For example:
/export/home/pvuser/443/AIX
directories:

OSVersion/setup
For example:
/export/home/pvuser/443/AIX/DataMart/AIX/setup

OSVersion/setup
For example:
/export/home/pvuser/443/AIX/DataMart/AIX5/setup
DataChannel setup directory /install_dir/=OPERATING_SYSTEM/DataChannel/

dcSetup
For example:
/export//home/pvuser/443/AIX/DataChannel/
dcSetup

For example:
/export//home/pvuser/443/AIX/DataLoad/dlSetup

For example:

For example:
/export//home/pvuser/443/AIX/DataView/AIX5/
dvinstaller

12. When the installation on the AIX system is complete, click Done to close the wizard.
Step 4: Install the Components on the Solaris System

On the Solaris system that will host DataView:
13. Log in as root.
14. Set and export your DISPLAY variable (see Setting Up a Remote X Window Display on page 41).
15. Change directory to the directory that contains the deployer
(root_dir/SOLARIS/Install/SOL9/deployer). For example:
# cd /export/home/pvuser/443/SOLARIS/Install/SOL9/deployer
16. Start the deployer using the following command:
# ./deployer.bin
Next to continue.
19. A pop-up window asks whether to download the topology from the database. Click Yes.
20. Enter information about the database you created on the AIX system. Click Next to continue.
21. The deployer displays a page stating that the topology download was successful. Click Next to continue.
22. The deployer displays a page stating that the environment was successfully downloaded. Click Next to
continue.
23. The node selection window lists the Solaris machine where the DataView components will be installed. Note
that remote command execution and file transfer are useless in this context because the components are
being installed on the local machine.
The deployer displays the table of installation steps.
25. Click Run All to perform all the installation steps.
26. When the installation on the Solaris system is complete, click Done to close the wizard.
Step 5: Complete the Installation on the AIX System

To complete the installation, perform the following tasks on the original AIX system:
./deployer.bin –Daction=mib
Next to continue.
30. A pop-up window asks whether to download the topology from the database. Click Yes.

31. Enter information about the database you created on the AIX system. Click Next to continue.
32. The deployer displays a page stating that the topology download was successful. Click Next to continue.
33. The deployer displays a page stating that the environment was successfully downloaded. Click Next to
continue.
34. The node selection window is displayed. Accept the defaults and click Next to continue.
The deployer displays the table of installation steps.
36. Click Run All to perform all the installation steps.
37. When the installation is complete, click Done to close the wizard.
The Post-Installation Script

The post-installation script for a minimal deployment performs four actions:
1. Starts the DataChannel.

2. Starts the DataLoad SNMP Collector, if it is not already running.
3. Creates a DataView user named poc.
4. Gives the poc user permission to view reports under the NOC Reporting branch.
The script writes a detailed log to the file /var/tmp/poc-post-install.${TIMESTAMP}.log.
Next Steps
When the installation is complete, you are ready to perform the final configuration tasks that enable you to view
reports on the health of your network. These steps are documented in detail in the Netcool/Proviso
documentation set.
For information about the MIB-II Technology Pack, see the MIB-II Technology Pack User’s Guide.
Note: In Version 4.4.3, you cannot use the Topology Editor to configure SNMP technology packs. Because
SNMP packs do not require configuration, they are ignored by the Topology Editor.
For information about installing additional technology packs, see Chapter 5, Installing Technology Packs.
Important: Before installing any additional technology packs, you must install the Starter Kit base packages, which
are included in the bundled jar file and checked by default in the Feature Selection screen of the APInstaller. The
Starter Kit base packages contain critical dependencies that all technology packs require.


Chapter 5: Installing Technology Packs
This chapter describes how to install technology packs, and consists of the following topics:
Topic Page
Overview 126
Installing the Starter Kit 128
Pre-Installation Setup Tasks 129
Installing Technology Packs 131
Adding UBA Collectors 133
Log Files 138
Overview
This chapter explains how to install technology packs on your Netcool/Proviso system. Netcool/Proviso
supports the following types of technology packs:
• Bundled — Multiple technology packs that are contained in a single, “bundled” jar file.
• Stand-alone — Individual technology packs that are contained in separate jar files, one for each stand-alone
technology pack.
Both types of packs are installed with a common installer, with slightly different screens depending on the type
of pack you are installing.
In all likelihood, you will be installing a combination of bundled and stand-alone packs. As a result, the
installation instructions cover the following user-case scenarios:
• Bundled only
• Stand-alone only
• Bundled and stand-alone
WARNING: Following a new installation of Netcool/Proviso, you MUST install the Starter Kit base
packages, which are included in the bundled jar file and checked by default in the Feature Selection screen
of APInstaller. The Starter Kit base packages contain critical dependencies that all technology packs require.
For more information see Installing the Starter Kit on page 128.

Before You Begin

Before installing a technology pack, ensure that you have or have done the following:
• Completed the Netcool/Proviso installation.
• Added an SNMP Collector, as described in Add a Collector on page 108. You added an SNMP Collector as
part of installing Netcool/Proviso.
Note: For UBA technology packs, you will add a UBA Collector and associate it with a UBA pack as part
of this technology pack installation.
• Access to the Netcool/Proviso DataMart server that is running an X Window server.
Note: If there is no graphics card on the DataMart server, the Xvfb virtual frame buffer package that provides
X Window services is automatically installed. For more information, see Setting Up a Remote X Window
Display on page 41.
• The Oracle TNS name of the server on which you installed Oracle server with the Netcool/Proviso database
configuration. See Specifying a Basename for DB_USER_ROOT on page 48 for more information.
• The correct version of Java. See the Netcool/Proviso Configuration Recommendations for more information.
• Access to the following distributions:
— The product distribution site:
https://www-112.ibm.com/software/howtobuy/softwareandservices
Located on the product distribution site are the ProvisoPackInstaller.jar file, the bundled jar
file, and individual stand-alone technology pack jar files.
— (Optional) The Netcool/Proviso CD distribution, which contains the ProvisoPackInstaller.jar
file and the jar files for the Starter Kit components.
See Installing the Starter Kit on page 128 for more information about the Starter Kit.
See your IBM customer representative for more information about obtaining software.
• Access to the following site to check for interim fixes or fix packs that might apply to your technology pack:
http://www-306.ibm.com/software/sysmgmt/products/support/NetcoolProviso.html
• The Netcool/Proviso documentation and technology pack release notes, which are available at the following
site:
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/
com.ibm.netcool_proviso.doc/welcome.htm
Always check the release notes before installing a technology pack to determine:
— If the pack is bundled or stand-alone.
— If the pack has any dependencies. For example, some packs require that the MIB-II Technology Pack be
installed.
— If the pack is an SNMP or UBA pack. UBA packs must be associated with a UBA collector as part of
the pack installation.
— If the pack is upgradeable.

Installing the Starter Kit

The Starter Kit is available as part of the Netcool/Proviso distribution. The Starter Kit contains a number of base
packages required by all technology packs. In addition, the Starter Kit includes two SNMP technology packs:
MIB-II and Cisco Device. You should understand the following topics related to the Starter Kit:
• Starter Kit Components
• Where to Obtain Starter Kit Components
• Backing Up Inventory Files
Starter Kit Components

The Starter Kit consists of the following discrete components:
• Starter Kit base packages — The following Starter Kit base packages are contained in the bundled jar file,
and are checked by default in the Feature Selection screen of APInstaller:
— MIBs, StyleSheets, and config files release_number — Includes MIBs, stylesheets, and configuration
files. Also includes the localization utility (APLocalizeInstall.jar) that APInstaller copies to the
DataMart config directory (/opt/datamart/conf, by default).
— AP Base DB Content release_number — Includes device sub-element properties, Discovery formulas,
and default Calendar definitions.
— Generic Metrics release_number — Includes a global set of generic metrics.
— Standard Thresholds release_number — Includes the defined thresholds.
— DV Navigator Reporter Set Wizard Pack release_number — Includes the Reporter Set Wizard tool that
enables pack developers to define a template that generates a set of reporters.
— Frame Relay Pack release_number — This is the Frame Relay technology pack that is still part of the
Starter Kit base packages.
WARNING: Following a new installation of Netcool/Proviso, you MUST install the Starter Kit base
packages, which are included in the bundled jar file and checked by default in the Feature Selection screen
of APInstaller. The Starter Kit base packages contain critical dependencies that all technology packs require.
• MIB-II Technology Pack — This component is contained in its own stand-alone jar file. Installing this
component is optional, unless required by other technology packs. See the technology pack release notes for
more information.
• Cisco Device Technology Pack — This component is contained in its own stand-alone jar file. Installing
this technology pack is optional, unless required by other technology packs. See the technology pack release
notes for more information.
Where to Obtain Starter Kit Components

You obtain the Starter Kit components from the following distributions:
• The product distribution site:
• The Netcool/Proviso CD

You download from the product distribution site or copy from the CD the following jar files:
• ProvisoPackInstaller.jar file — Contains the APInstaller, which installs all of the components that
make up the Starter Kit, as well as all other bundled and stand-alone packs.
• Bundled jar file — Contains the Starter Kit base packages and bundled packs.
• Stand-alone jar files for the MIB-II and Cisco Device technology packs.
The previously listed jar files are located in the following directories on the CD:
Proviso/AP
Proviso/AP/jar
The procedure for downloading the bundled jar and stand-alone jar files and installing the Starter Kit base
packages are described in Step 7 on page 130 and Step 9-d on page 132, respectively.
Backing Up Inventory Files

Following a new installation of Netcool/Proviso, you must install the Starter Kit base packages, which are included
in the bundled jar file and checked by default in the Feature Selection screen of APInstaller. The Starter Kit base
packages contain critical dependencies that all technology packs require.
Note that when the MIBs, StyleSheets, and config files base package of the Starter Kit is installed, it overwrites
the inventory_elements.txt and inventory_subelements.txt files — these files contain information about all bundled packs,
but not stand-alone packs and custom discovery formulas. If you have hand-edited these files, you need to do the
following:
• Before you install the MIBs, StyleSheets, and config files base package of the Starter Kit, make backup
copies of these files.
• After the installation completes, you need to diff these files and merge back the edits.
To create backup copies:
1. Change your working directory to the conf directory using the following command:
cd $PVMHOME/conf
2. Make backup copies of the inventory control files by entering the following commands:
cp inventory_elements.txt inventory_elements.txt.ORIG
cp inventory_subelements.txt inventory_elements.txt.ORIG
Pre-Installation Setup Tasks

Before starting a technology pack installation, perform the following setup tasks:
1. Determine which technology packs you want to install, then refer to the release notes to determine whether
the pack is bundled or stand-alone.
Note: If you are installing multiple packs, plan to download all the jar files and install all the packs at the same
time.
2. Open a terminal emulator and log in to the DataMart server as pvuser.

3. Change your working directory to the DataMart home directory (/opt/datamart, by default).

4. Load the shell with the DataMart environment by sourcing the dataMart.env file, as follows:
. /opt/datamart/dataMart.env
Note: After you load the DataMart environment into the shell, the PVMHOME variable is set to the
DataMart home directory, /opt/datamart by default. These instructions assume that this variable has been set.
5. Set and export the DISPLAY environment variable (see Setting Up a Remote X Window Display on page 41), so
that the APInstaller GUI will display back on your system.
6. On the DataMart server, create an app-packs directory to hold the technology pack jar files and the
ProvisoPackInstaller.jar file, by executing the following command:
mkdir -p $PVMHOME/version/app-packs
7. Download the jar files to the directory you created in Step 6 by following these steps:
7-a. Change your working directory to the app-packs directory that you created in Step 6, using the
following command:
cd $PVMHOME/version/app-packs
7-b. Download the following from this URL:
— The ProvisoPackInstaller.jar file
— Any stand-alone jar files
— The bundled jar file
Note: You will need the bundled jar file to install the Starter Kit base packages. See Starter Kit Components on
page 128 for descriptions of the base packages.
7-c. After you finish downloading the jar files, verify that the files are in this directory by entering the
following command:
ls -l
8. (Optional) Copy the Starter Kit component jar files from the Netcool/Proviso CD by following these steps:
8-a. Mount the CD using a command such as, /mnt/cdrom/path.
8-b. Using the directory information specified in Where to Obtain Starter Kit Components on page 128, copy the
ProvisoPackInstaller.jar file, the bundled jar file, and the MIB-II and Cisco Device
technology pack stand-alone jar files to the app-packs directory that you created in Step 6.
8-c. After you finish copying the jar files, verify that the files are in this directory by entering the following
command:
ls -l
8-d. Unmount the CD.
9. Begin the installation, as explained in Installing Technology Packs on page 131.

Installing Technology Packs

This section explains how to install Netcool/Proviso technology packs.
To install Netcool/Proviso technology packs, follow these steps:
1. Invoke the installer as follows:

From the launchpad (preferred method):
1-a. If it is not already open, open the launchpad (see Starting the Launchpad on page 99).
Note: You can use the terminal emulator you opened in Step 2 on page 129 to start the launchpad. You must,
however, su to root. Otherwise, the launchpad will fail to start.
1-b. On the launchpad, click the Install Technology Pack option.

1-c. On the Install Technology Pack screen, enter the following information:
* The DataMart home directory (/opt/datamart, by default)
* The Java run-time environment home directory (for example, /usr/java).
* The Proviso user (for example, pvuser)
1-d. Click the Install Technology Pack link.
1-e. A window prompts you to select the technology pack installation setup directory. Click Browse to locate
the directory that you created in Step 6 on page 130:
$PVMHOME/version/app-packs
Important: You cannot install technology packs from the Netcool/Proviso CD.
1-f. Click the directory, then click Select to display the specified directory in the window, and then click OK.
Note: The preferred method for installing technology packs is from the launchpad.
1-a. Change your working directory to the technology packs directory that you created in Step 6 on page
130, by entering the following command:
cd $PVMHOME/version/app-packs
1-b. To invoke APInstaller, enter the following command:
java -Xmx256M -jar ProvisoPackInstaller.jar
Note: The -Xmx256M option is required to allocate sufficient memory for APInstaller to successfully install
multiple bundled and stand-alone technology packs.
2. When APInstaller starts up, it displays a Netcool/Proviso Technology Packs screen. Click Next.
3. The APInstaller displays a Feature Selection screen, which lists in the left panel all the packs you
downloaded to the directory created in Step 6 on page 130. All of the packs are automatically selected for
installation. Deselect any technology packs in the list that you do not want to install, then click Next.
Note: You must install the Starter Kit base packages (which are included in the bundle) as the first technology
pack following a new installation of Netcool/Proviso. See Installing the Starter Kit on page 128 for more
information.
Note: The prerequisites for technology packs item in the Feature Selection screen is always installed. You
cannot deselect this item, and the Starter Kit is not included in this item.

4. APInstaller displays a warning that tells you the Starter Kit must be the first technology pack to install
following a new installation of Netcool/Proviso.
Note: This warning message displays every time you invoke APInstaller, whether or not the Starter Kit base
packages are installed.
If you have already installed or are about to install the Starter Kit base packages, click Yes to continue.
Otherwise, click No, then download the bundle (Step 7 on page 130) and restart the installation.
5. Accept the license agreement by clicking on the accept the terms button, then click Next.
6. APInstaller displays the Database Access Parameters screen with the parameter values that you specified
when installing and configuring Oracle, the Netcool/Proviso database, and Netcool/Proviso DataMart (see
Chapter 2, Installing and Configuring the Prerequisite Software and Chapter 3, Installing Netcool/Proviso in a Distributed
Environment).
Re-enter the password of the database user, which is PV by default.
7. Click Next to continue.
8. APInstaller displays the Silver Stream Database Access Parameters screen with the parameter values that
you specified when installing and configuring Netcool/Proviso DataView as described in Chapter 3, Installing
Netcool/Proviso in a Distributed Environment.
Re-enter the password of the Silver Stream user, which is admin by default.
9. Depending on the type of packs you are installing, you will be presented with slightly different screens:
Stand-alone packs only:
9-a. Click Next to start the installation. As the stand-alone packs are installed, APInstaller displays the name
of each pack and indicates the progress.
When the installation completes, the Technology Pack Install Complete screen is displayed.
9-b. Click Finish to exit APInstaller.
9-c. Go to Step 10 on page 133 to perform post-installation tasks.
Bundled and stand-alone packs:
— APInstaller installs all of the stand-alone technology packs and displays the name of each pack and
indicates progress. When the installation of the stand-alone packs completes, the Netcool/Proviso
Technology Packs screen appears, and the installation of bundled packs begins.
For more information, see Step 9-a under Bundled packs only.
Bundled packs only:
9-a. An Update Proviso Database message box displays briefly, followed by a Netcool/Proviso
Technology Packs screen. Click Next to continue.
9-b. APInstaller displays the Database Details screen with the parameter values that you specified when
installing and configuring Oracle, the Netcool/Proviso database, and Netcool/Proviso DataMart as
described in previous chapters of this installation guide (see Chapter 2, Installing and Configuring the
Prerequisite Software and Chapter 3, Installing Netcool/Proviso in a Distributed Environment).
Re-enter the password of the database user, which is PV by default.
9-c. Click Next to continue. The Select Packages screen appears.
9-d. On the Select Packages screen, do the following:
— Install the Starter Kit base packages.
Note: The Starter Kit base packages are checked by default if they have not yet been installed.
— Select any additional bundled technology packs that you want to install.

9-e. Click Next to continue.

9-f. Confirm your bundled pack selections on the Install Options Selected screen or click Back to return
to the Select Packages screen to remove or add technology packs to the list.
9-g. When you are satisfied with your selections, click Next.
APInstaller begins copying files associated with the bundled packs, displaying several status windows.
Note: APInstaller might display Replace File windows if it detects existing files, for example,
inventory_elements.txt and inventory_subelements.txt. See Backing Up Inventory
Files on page 129 for more information about backing up these files.
9-h. When APInstaller finishes copying all the necessary files for the bundled packs and updates the
database, it displays the ReadMe File screen. By default, the checkbox for reviewing the README
file is selected. The README file tells you to download the pack Release Notes from the information
center. Click Finish.
9-i. APInstaller displays a series of messages in the terminal emulator as it uploads style sheets and other
pack-related files to the database. Upon completion, APInstaller displays an Technology Pack Install
Complete screen. Click Finish to exit APInstaller.
10. After the installation completes, do the following, depending upon the types of packs (SNMP or UBA) you
installed:
Note: As explained in the Before You Begin on page 127, refer to the technology pack release notes to determine
the pack type (SNMP or UBA).
UBA packs:
— Add a UBA Collector, as follows:
* All UBA packs except CS2K, see Adding a UBA Collector for UBA Packs on page 134
* CS2K, see Adding UBA Collectors for the Nortel CS2000 Technology Pack on page 135
— Configure the technology pack, as described in the associated technology pack user’s guide.
SNMP packs:
— Configure the pack, as described in the associated technology pack user’s guide.
Important: Technology packs will not work unless they are configured.
Adding UBA Collectors

UBA technology packs require that you add a UBA Collector as follows:
• For all UBA technology packs except for Nortel CS2000, follow the instructions in Adding a UBA Collector
for UBA Packs on page 134.
• For the Nortel CS2000 Technology Pack, follow the instructions in Adding UBA Collectors for the Nortel
CS2000 Technology Pack on page 135. This technology pack has some specific requirements beyond those of
the typical UBA pack and requires some additional steps.

Adding a UBA Collector for UBA Packs

To add a UBA Collector for a UBA technology pack, follow these steps:
1. Load the pack’s XSD file into an existing topology, as follows:

1-a. If it is not already open, open the Topology Editor (see Starting the Topology Editor on page 101).
1-b. Open a deployed topology (a topology.xml file) (see Opening a Deployed Topology on page 141).
1-c. In the Technology Pack view, right-click the Technology Packs folder and select Load Technology
Pack from the pop-up menu.
1-d. The Load the technology pack configuration metadata window displays. There are two radio buttons:
XSD file and JAR file.
1-e. Click the JAR file radio button and select Browse.
Note: The JAR file radio button is selected by default.
1-f. Using the Directory: field, the up and down arrows, and the Folders pane on the configuration
metadata window, navigate to the $PVMHOME/version/app-packs directory where the technology
pack jar files reside.
1-g. For bundled UBA packs:
— Select the bundled jar file, then click OK. The bundled jar file displays in the Load the
technology pack configuration metadata window.
— Click Next. The Topology Editor displays the list of XSD files for the bundled packs you installed.
— Select one or more XSD files to import into the topology. Click Select all to select all of the XSD
files.
Note: You can also click on a single XSD file and press the CTRL key to select any number of other XSD files.
— Click Finish. The Topology Editor adds the selected bundled technology pack or packs to the list
of technology packs displayed in the Technology Packs view.
1-h. For stand-alone UBA packs:
— Select a technology pack jar file, then click OK. The pack jar file displays in the configuration
metadata window.
— Click Finish. The Topology Editor adds the selected stand-alone technology pack to the list of
technology packs displayed in the Technology Packs view.
2. After loading a UBA pack’s XSD file, you must add a UBA Collector and associate it with a UBA technology
pack, as follows:
2-a. In the Logical view, right-click the DataChannel x folder and select the Add Collector UBA from the
menu.
2-b. The Configure Collector window opens. Select the appropriate technology pack (for example, Alcatel
8920 SQM) from the drop-down list of technology packs, then click Next.
2-c. Using the drop-down list of available hosts on the Configure Collector window, select the machine that
will host the collector (for example, corinth).
2-d. Accept the default collector number (for example, 2).
2-e. Click Finish.
2-f. Highlight the collector to view its properties. The Topology Editor displays both the UBA collector
core parameters and the UBA technology pack-specific parameters. The core parameters are

configured with all UBA technology packs. Review the values for the parameters to make sure they are
valid. For information about the core parameters, see the Netcool/Proviso Properties Reference. For
information about the pack-specific parameters, see the Topology Editor Help.
The UBA collector is associated with two DataChannel components:
— Complex Metric Engine (CME) x.x — Performs calculations on the collected data.
— File Transfer Engine (FTE) x.x — Transfers files from the collector’s output directories and
places them in the input directory of the CME.
Note that the Topology Editor includes the channel and collector numbers in the component names.
For example, Data Channel 1 could have Collector UBA 1.1, with Complex Metric Engine 1.1 and File
Transfer Engine 1.1.
The FTE writes data to the file /var/adm/wtmpx on each system that hosts a collector. As part of
routine maintenance, check the size of this file to prevent it from growing too large.
Note: Your Solaris version can be configured with strict access default settings for secure environments. Strict
FTP access settings might interfere with automatic transfers between a DataChannel subchannel and the
DataLoad server. Check for FTP lockouts in /etc/ftpd/ftpusers, and check for strict FTP rules in
/etc/ftpd/ftpaccess.
Note: To add additional UBA collectors for a UBA technology pack, repeat Step 2-a through Step 2-f.
2-g. Redeploy the updated topology (see Starting the Deployer on page 111).
3. Configure the UBA technology packs you have installed, by referring to the configuration appendix of the
appropriate technology pack user’s guide.
Adding UBA Collectors for the Nortel CS2000 Technology Pack

The Nortel CS2000 Technology Pack requires you to add one UBA collector for each of the following devices
running in the network:
• Passport Packet Voice Gateway (PVG) — The UBA executing on this subchannel retrieves Bulk input files
generated by the PVG device.
• Universal Signaling Point (USP) — The UBA executing on this subchannel retrieves Bulk input files
generated by the USP device.
• Nortel CS2K Performance — The UBA executing on this subchannel retrieves Bulk input files generated by
the Nortel CS2K Performance device.
• Nortel Integrated Element Management System (IEMS) — The UBA executing on this subchannel retrieves
Bulk input files generated by the Nortel CS2K IEMS system.
For example, if there are two PVG devices you would add two UBA collectors, one for each PVG device operating
in the network. If there are two USP devices you would add two UBA collectors, one for each USP device
operating in the network, and so forth.
The Nortel CS2000 Technology Pack also requires you to add multiple UBA collectors for the following call
records:
• Nortel Succession Communication Server 2000 (CS2K) CDR call records — The UBAs executing on this
subchannel retrieve Bulk input files generated by the cs2kcdr.pl pre-processor.
For example, if you expect the UBA to process a large amount of CS2K CDR call records you would add multiple
(for example, three) UBA collectors, each with a unique collector number. Each of these UBA collectors is then

mapped to a Master UBA. The Topology Editor displays the appropriate windows for you to add multiple UBA
collectors and add the Master UBA.
The Topology Editor simplifies the task of adding UBA collectors for each of these devices and the CS2K CDR
call records by associating each with an “technology pack” that displays in the Technology Packs view after you
load the XSD file. Table 6 maps each device to its associated “technology pack”.
Table 6: Nortel CS2000 Devices Mapped to Technology Packs
CS2000 Device/System/Calls Records Pack Displayed in Technology Packs view
PVG Nortel CS2K - PVG
Nortel CS2K CDR Nortel CS2K - CDR
USP Nortel CS2K - USP
Nortel CS2K Performance Nortel CS2K - CS2K Performance
IEMS Nortel CS2K - IEMS
To add a UBA Collector for the Nortel CS2K - PVG, Nortel CS2K - USP, Nortel CS2K - CS2K
Performance, and Nortel CS2K - IEMS packs listed in Table 6, follow these steps:
1. Load the Nortel CS2000 pack’s XSD file into an existing topology, as described in Step 1-a on page 134
through Step 1-f on page 134 and Step 1-h on page 134. After you load the XSD file for the Nortel CS2000
Technology Pack, the “technology packs” listed in Table 8 display in the Technology Packs view.
In effect, the Nortel CS2000 Technology Pack is organized into five “technology packs”, one for each of the
supported devices. You will add a UBA Collector for each of these four “technology packs”.
2. To add a UBA Collector and associate it with the Nortel CS2K - PVG technology pack:
2-a. In the Logical view, right-click the DataChannel x folder and select the Add Collector UBA from the
menu.
2-b. The Configure Collector window opens. Select the Nortel CS2K - PVG technology pack from the
drop-down list of technology packs, then click Next.
2-c. Using the drop-down list of available hosts on the Configure Collector window, select the machine that
will host the collector (for example, corinth).
2-d. Accept the default collector number (for example, 2).
2-e. Click Finish.
See Step 2-f on page 136 for information related to the CME and FTE DataChannel components.
2-f. Highlight the collector to view its properties. The Topology Editor displays both the UBA collector
valid. For information about the core parameters, see the Netcool/Proviso Properties Reference. For
information about the pack-specific parameters, see the Topology Editor Help.
3. To add a UBA Collector for each of the Nortel CS2K - USP, Nortel CS2K - CS2K Performance, and Nortel
CS2K - IEMS technology packs, repeat Step 2-a on page 136 through Step 2-f on page 136 making sure to
select the appropriate pack from the drop-down list of technology packs displayed in the Configure Collector
window.
Note: To add additional UBA collectors for any of these UBA technology packs, repeat Step 2-a through
Step 2-f.

To add multiple UBA Collectors and specify a Master ID for the Nortel CS2K - CDR pack listed in
Table 6, follow these steps:
1. In the Logical view, right-click the DataChannel x folder and select the Add Collector UBA from the menu.
2. The Configure Collector window opens. Select the Nortel CS2K - CDR technology pack from the drop-down
list of technology packs, then click Next.
3. The Configure Collector window requests you enter the number of UBA collectors. The number you enter
here depends on the volume of records the UBA collectors need to process. If there are large volumes of
records, consider adding three or four UBA collectors. Specify the value in the Number of UBA Collectors
field.
4. Click Next.
5. The Configure Collector window requests that you enter the basic settings for the number of UBA collectors
you specified in Step 3 as follows:
— UBA instance 1 — Using the drop-down list of available hosts on the Configure Collector window, select
the machine that will host the collector (for example, corinth) of UBA instance 1 for this Nortel CS2K -
CDR pack. Accept the default collector number (for example, 5). Click Next.
— UBA instance 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) of UBA instance 2 for this Nortel CS2K -
CDR pack. Accept the default collector number (for example, 6). Click Next.
— UBA instance x — Using the drop-down list of available hosts on the Configure Collector window, select
the machine that will host the collector (for example, corinth) of UBA instance x for this Nortel CS2K -
CDR pack. Accept the default collector number (for example, x). Click Next.
6. The Configure Collector window requests that you enter the basic settings for the master UBA of this
multiple in-line inventory technology pack.
6-a. Using the drop-down list of available hosts on the Configure Collector window, select the machine that
will host the collector (for example, corinth) of the master UBA.
6-b. Accept the default collector number (for example, 21).
WARNING: If you do not accept the default and specify a collector number, make
sure this number has not been assigned to an existing collector.
6-c. Click Finish.

The Topology Editor displays the new collectors under the DataChannel x folder in the Logical view.
See Step 2-f on page 136 for information related to the CME and FTE DataChannel components.
6-d. Highlight the collectors to view their properties. The Topology Editor displays both the UBA collector
valid. The following properties are of particular interest:
* COLLECTOR_ALIAS — This is the collector number specified for the Master UBA. You should not
modify this parameter.
* INPUT_ID — Specifies an ID to be mapped to one of the output streams associated with the
cs2kcdr.pl pre-processor. The cs2kcdr.pl pre-processor can be configured to output files in
multiple streams every run interval.
Note: See the Netcool/Proviso Nortel CS2K Carrier VoIP Technology Pack User’s Guide for information on
configuring the cs2kcdr.pl pre-processor. You configure the cs2kcdr.pl pre-processor by editing
variables defined in the cs2kcdr-config.pl configuration file. For example, you specify the number of

output streams the pre-processor should create by editing the $numberOfOutputs variable. The number specified
for this variable should match the number of UBA Collectors that you add for the Nortel CS2K - CDR pack.
Thus, if you added five UBA Collectors, you must specify the value 5 for $numberOfOutputs.
For example, a cs2kcdr.pl pre-processor that is configured for five output streams will write five
different output files, as in the following example:
example-file.0.csv
example-file.1.csv
example-file.2.csv
example-file.3.csv
example-file.4.csv
Thus, each of the UBA Collectors you added for the Nortel CS2K - CDR pack must be associated with
an output stream. Using the five output streams as an example, you might specify the INPUT_ID
parameters for the UBA Collectors as follows:
— UBA instance 1 — Specify the value 0 (zero) so that UBA instance 1 processes example-
file.0.csv output files.
— UBA instance 2 — Specify the value 1 so that UBA instance 2 processes example-file.1.csv
output files.
output files.
output files.
output files.
7. Redeploy the updated topology (see Starting the Deployer on page 111).
8. Configure the Nortel CS2000 Technology Pack, as explained in the user’s guide.
Log Files
APInstaller writes a log file to the /usr/tmp directory. This log file contains a detailed history of the tasks the
APInstaller performs as it installs technology packs. You can check this log file to help solve any issues that might
occur during technology pack installation. For example, the log file might contain a message that indicates that
the APInstaller GUI could not display back on your system because the DISPLAY environment variable was not
set. Log file names have the format APInstallnumber.log. For example:
APInstall1213136138386.log


Chapter 6: Modifying the Current
Deployment
Once you have created the topology and installed Netcool/Proviso, it is very easy to make changes to the
environment. Simply load the deployed topology from the database, make your changes, and run the deployer
with the updated topology as input.
Note: You must run the updated topology through the deployer in order for your changes to take effect.
This chapter describes how to modify an installation of Netcool/Proviso. The topics are as follows:
Topic Page
Opening a Deployed Topology 141
Adding a New Component 141
Example: Performing an Incremental Installation 142
Changing Configuration Parameters of Existing 143

Netcool/Proviso Components
Moving Components to a Different Host 144
Moving a Deployed Collector to a Different Host 144
Note the following:

• 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 made your changes, you must deploy the updated topology so that it is propagated to the database. To
make any subsequent changes following this deployment, you must load the topology from the database
again.
• You might have a situation where you have modified a topology by both adding new components and
removing components (marking them “To Be Removed”). However, the deployer can work in only one
mode at a time — installation mode or uninstallation mode. In this situation, first run the deployer in
uninstallation mode, 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 170.

Chapter 6: Modifying the Current Deployment
Opening a Deployed Topology

Once you have installed Netcool/Proviso, you can perform incremental installations by modifying the topology
that is stored in the database. 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 in the database.
To open a deployed topology:
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:
— Database hostname — The name of the database host. The default value is localhost.
— Port — The port number used for communication with the database. The default value is 1521.
— Database user — The user name used to access the database. The default value is PV_INSTALL.
— Database Password — The password for the database user account. For example, PV.
— SID — The SID for the database. The default value is PV.
If desired, click Save as defaults to save these values for future incremental installations.
Click Finish.
The topology is retrieved from the database and is displayed in the Topology Editor.
Adding a New Component

After you have deployed your topology, you might need to make changes to it. For example, you might want to
add another SNMP collector.
To add a new component to the topology:
2. Open the existing topology (see Opening a Deployed Topology on page 141).
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:
— Add the Hosts on page 102
— Add a Database Configurations Component on page 103
— Add a DataMart on page 104
— Add a DataView on page 106
— Add the DataChannel Administrative Components on page 107
— Add a DataChannel on page 107
— Add a Collector on page 108

Note that if you add a collector to a topology that has already been deployed, you must manually bounce
the DataChannel management components (cnsw, logw, cmgrw, amgrw). For more information, see
Manually Starting the Channel Manager Programs on page 186.
— Add a Discovery Server on page 105
6. The new component is displayed in the Logical view of the Topology Editor.
7. Save the updated topology. You must save the topology after you add the component and before you run the
deployer. This step is not optional.
8. Run the deployer (see Starting the Deployer on page 111), passing the updated topology as input.
The deployer can determine that most of the components described in the topology are already installed, and
installs only the new component.
9. When the installation ends successfully, the deployer uploads the updated topology into the database.
For information about removing a component from the Netcool/Proviso environment, see Removing a Component
from the Topology on page 170.
Example: Performing an Incremental Installation

In this example, you update the installed version of Netcool/Proviso to add a new DataChannel and two SNMP
DataLoaders to the existing system.
To update the Netcool/Proviso installation:
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 107, add the following components:
4-a. Add a new DataChannel (Data Channel 2) with two different SNMP DataLoaders to the topology. The
Topology Editor creates the new DataChannel.
4-b. Add two SNMP collectors to the channel structure created by the Topology Editor. The editor
automatically creates a Daily Loader component, an Hourly Loader component, and two Sub Channels
with an FTE component and a CME component.
5. Save the updated topology.
6. Run the deployer (see Starting the Deployer on page 111), passing the updated topology as input.
The deployer can determine that most of the components described in the topology are already installed, and
installs only the new components (in the example, DataChannel 5 with two new subchannels and
DataLoaders).
7. When the installation ends successfully, the deployer uploads the updated topology into the database.

Changing Configuration Parameters of Existing Netcool/Proviso

Components
Beginning with Netcool/Proviso Version Version 4.4.3, the configuration information that was previously stored
in the dc.cfg and dl.cfg files is now stored in the database. This change enables the DataChannel-related
components to retrieve the configuration from the database at run time, instead of relying on a local copy of the
files.
You set the configuration information using the Topology Editor, described in The Topology Editor on page 23. As
with the other components, if you make changes to the configuration values, you must pass the updated topology
data to the deployer to have the changes propagated to both the environment and the database.
Note: After the updated configuration has been stored in the database, you must manually start, stop, or bounce
the affected DataChannel component to have your changes take effect.
For example, suppose that you want to change the FC_QUOTA parameter of one the UBA collectors.
To change the value of a configuration parameter:
1. If it is not already open, open the launchpad (see Starting the Launchpad on page 99).
3. Load the existing topology into the editor (see Opening a Deployed Topology on page 141).
4. In the Logical View, select the component whose parameter you want to modify; the parameters are displayed
in the Properties and Advanced Properties Views (see page 32). Modify the parameter values as needed, then
save the updated topology. For example, change the value of the FC_QUOTA parameter of a UBA collector.
5. Run the deployer (see Starting the Deployer on page 111), passing the updated topology data as input.
The deployer can determine that the components described in the topology are already installed. By
comparing the configuration values in the current version of the file to the values in the database, the
deployer can determine that the FC_QUOTA value has been changed.
6. When the installation is complete, the deployer loads the new topology description into the database.

Moving Components to a Different Host

You can use the Topology Editor to move components between hosts. You can move all components between
hosts when they have not yet been installed and are in the configured state. You can move SNMP and UBA
collectors when they are in the configured state or after they have been deployed and are in the installed state.
If the component in the topology has not yet been deployed and is in the configured state, the Topology Editor
provides a Change Host option in the pop-up menu when you click the component name in the Logical view.
This option allows you to change the host associated with the component prior to deployment.
If the component is an SNMP or UBA collector that was previously deployed and is in the installed state, the
Topology Editor provides a Move option in the pop-up menu. This option instructs the deployer to uninstall the
component from the 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 144. For instructions on moving components that have not yet been deployed, see the
information below.
To change the host associated with a component before deployment:
1. Start the Topology Editor (if it is not already running) and open the topology that includes the component’s
current host (see Starting the Topology Editor on page 101 and Opening a Deployed Topology on page 141).
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 Move Component dialog appears, containing a drop-down list of hosts where 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 Host

You can move a deployed SNMP or UBA collector to a different host. The instructions 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 change to be registered in the database.
Moving a Deployed SNMP Collector

Note: To avoid the loss of collected data, leave the collector running on the original host until you complete Step 7
on page 145.
To move a deployed SNMP collector to a different host:
1. Start the Topology Editor (if it is not already running) and open the topology that includes the collector’s
2. In the Logical view, navigate to the name of the collector to move. For example if 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 click Move from the pop-up menu.

The Move Collector dialog appears, containing a drop-down list of hosts where you can move the collector.
Note: If you are moving a collector that has not been deployed, select Change host from the pop-up menu (Move
is grayed out). After the Move Collector dialog appears, continue with the steps below.
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 will remove the collector from the original host in Step 9.
Note: If you are moving a collector that has not been deployed, the name of the 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 111.
The deployer installs the collector on the new host and starts it.
Note: Both collectors are now collecting data — the original collector on the original host, and the new collector
on the new host.
7. Before continuing with the steps below, note the current time, and wait until a time period equivalent to two
of the collector’s collection periods elapses. Doing so guards against data loss between collections on the
original host and the start of collections on the new host.
Because data collection on the new host is likely to begin sometime after the first collection period begins,
the data collected during the first collection period will likely be incomplete. By waiting for two collection
time periods to elapse, you can be confident that data for one full collection period will be collected.
The default collection period is 15 minutes. You can find the collection period for the sub-element, sub-
element group, or collection formula associated with the collector in the DataMart Request Editor. For
information on viewing and setting a collection period, see the Netcool/Proviso DataMart Configuration Guide.
8. Bounce the FTE for the collector on the collector’s new host, as in the following example:
./dccmd bounce FTE.1.1
The FTE now recognizes the collector’s configuration on the new host, and will begin retrieving data from
the collector’s output directory on the new host.
9. In the current Topology Editor session, click Run > Run Deployer for Uninstallation to remove the
collector from the original host, passing the updated topology as input. For more information, see Removing
a Component from the Topology on page 170.
Note: This step is not necessary if you are moving a collector that has not been deployed.

Moving a Deployed SNMP Collector to or from a HAM Environment

If you move a deployed SNMP collector into or out of a High Availability Manager (HAM) environment, you
must perform the steps in this section.
To move a deployed SNMP collector to or from a HAM environment:
1. Move the collector as described in Moving a Deployed SNMP Collector on page 144.
Note: If you are moving a spare collector out of the HAM environment, the navigation path is different than
the path shown in Step 2 of the above instructions. For example, suppose you have a single HAM environment
with a cluster MyCluster on host MyHost, and you are moving the second SNMP spare 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 Process SNMP Spare 2
2. Log in as pvuser on the collector’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:
— Set DL_HA_MODE=true if you moved the collector onto a HAM host.
— 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, you must bounce the HAM. For information,
see Stopping and Restarting Modified Components on page 167.
Moving a Deployed UBA Bulk Collector

Note: You cannot move BCOL collectors, or UBA collectors that have a BLB or QCIF subcomponent. If you
want to move a UBA collector that has these subcomponents, you must manually remove it from the old host in
the topology and then add it to the new host.
To move a deployed UBA collector to a different host:
1. 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 these components 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 Netcool/Proviso Command Line Interface Guide.
Note: Some technology packs have additional pack-specific components that must be shut down — namely, BLB
(bulk load balancer) and IF (inventory file) components. IF component names have the format xxxIF, where xxx
is a pack-specific name. For example, Cisco CWM packs have a CWMIF component, Alcatel 5620 SAM
packs have a SAMIF component, and Alcatel 5620 NM packs have a QCIF component. Other packs do not
use these technology-specific components.
5. Tar up the UBA collector’s UBA directory. You will copy this directory to the collector’s new host later in the
procedure (Step 13).
Note: This step is not necessary if the collector’s current host and the new host share a file system.
For example, to tar up a UBA directory for UBA collector 1.1, run the following command:
tar -cvf UBA_1_1.tar ./UBA.1.1/*
Note: Some technology packs have additional pack-specific directories that need to be moved. These directories
have the same names as the corresponding pack-specific components described in Step 4.
6. Start the Topology Editor (if it is not already running) and open the topology that includes the collector’s
7. In the Logical view, navigate to the name of the collector to move — for example, Collector UBA.1.1.
8. Right-click the collector name and select Move from the pop-up menu.
The Move Collector dialog appears, containing a drop-down list of hosts where you can move the collector.
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 the original host, the collector will be listed
under that host, and its status will be “To be uninstalled.” You can remove the DataChannel installation from
the original host after you finish the steps below. For information on removing DataChannel from the host, see
Removing a Component from the Topology on page 170.
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 111.
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 from the original host, passing the
updated topology as input. For more information, see Removing a Component from the Topology on page 170.
13. Copy any directory you tarred in Step 5 and the associated JavaScript files to the new host.
Note: This step is not necessary if the collector’s original host and the new host share a file system.

For example, to copy UBA_1_1.tar and the JavaScript files from the collector’s original host:
13-a. Log in as pvuser to the UBA collector’s new host.
13-b. Change to the directory where DataChannel is installed. For example:
cd /opt/datachannel
13-c. FTP to the collector’s original host.
13-d. Run the following commands to copy the tar file to the new host. For example:
cd /opt/datachannel
get UBA_1_1.tar
bye
tar -xvf UBA_1_1.tar
13-e. Change to the directory where the JavaScript files for the technology pack associated with the collector
are located:
cd /opt/datachannel/scripts
13-f. FTP the JavaScript files from the /opt/datachannel/scripts directory on the original host to
the /opt/datachannel/scripts directory on the new host.
14. Log in as pvuser to the Channel Manager host where the Administrator Components (including CMGR)
are running.
15. Stop and restart the Channel Manager by performing the following steps:
15-a. Change to the $DC_HOME directory (typically, /opt/datachannel).
15-b. Source the DataChannel environment:
. dataChannel.env
15-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, as shown below in bold:
pvuser 6561 6560 0 Aug 21 ? 3:04 /opt/datachannel/bin/CMGR_visual
-nologo /opt/datachannel/bin/dc.im -a CMGR
pvuser 25976 24244 0 11:39:38 pts/7 0:00 grep CMGR
15-d. Stop the CMGR process. For example, if 6561 is the CMGR process ID:
kill -9 6561
15-e. Change to the $DC_HOME/bin directory (typically, /opt/datachannel/bin).
15-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) is running on the new host:
./findvisual
If the AMGR process is running, you will see output that includes an entry like 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 that you 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 (see Step 4), you must also start those
components on the new host.

Chapter 7: Using the High Availability
Manager
This chapter describes the optional Netcool/Proviso High Availability Manager (HAM), including how to set up
a HAM environment. The topics are as follows:
Topic Page
Overview 150
HAM Basics 151
HAM Cluster Configuration 152
Resource Pools 159
How the SNMP Collector Works 159
Creating a HAM Environment 162
Modifying a HAM Environment 167
Viewing the Current Configuration 168
Overview
The High Availability Manager (HAM) is an optional component for large installations that want to use redundant
SNMP collection paths. The HAM constantly monitors the availability of one or more SNMP collection hosts,
and switches collection to a backup host (called a spare) if a primary host becomes unavailable.
The following figure shows a simple HAM configuration with one primary host and 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 is unavailable, so it
dynamically unbinds the collection path from the primary host and binds it to the spare.
Network with Network with

SNMP devices SNMP devices
Hosts Hosts
Collector Collector
P r im a r y P ri m a ry
S p a re S pa re

Chapter 7: Using the High Availability Manager
HAM Basics
An SNMP collector collects data from a specific set of network resources according to 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 collector profile contains properties used
in the collection of data from network resources — properties such as collector number, polling interval, and output
directory for the collected data. An inventory profile contains information used to discover network resources —
properties such as the addresses of the resources to look for and the mode of discovery.
A collector that is not part of a HAM environment is static — that is, the collector process and the collector
profile are inseparable. But in a HAM environment, the collector process and collector profile are managed as
separate entities. This means that if a collector process is unavailable (due to a collector process crash or a host
machine outage), the HAM can dynamically reconfigure the collector, allowing data collection to continue. The
HAM does so by unbinding the collector profile from the unavailable collector process on the primary host, and
then binding the collector 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 Collector

When you set up a HAM configuration in the Topology Editor, you manage the two parts of a collector — the
collector process and the collector profile — through the following folders in the Logical view:
• 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 host where the process is running and by the collector
process port (typically 3002).
A host can have just one SNMP collector process.
• Managed Definitions. A managed definition identifies a collector profile through the unique collector number
defined in the profile.
Every managed definition has a default binding to a host and to the collector process on that host. The
default host and collector process are called the managed definition’s primary host and collector process.
A host that you designate as a spare host has a collector process but no default managed definition.
The following figure shows the parts of a collector that you manage through the Collector Process and Managed
Definition folders. In the figure, the HAM dynamically unbinds the collector profile from the collector process
on the primary host, and then binds the profile to the collector process on the spare. This dynamic re-binding of

the collector is accomplished when the HAM binds the managed definition — in this case, represented by the
unique collector ID, Collector 1 — to the collector process on the spare.
Network with Network with

SNMP devices Managed Collector SNMP devices Managed Collector
Definition Process Definition Process
Hosts Hosts
Collector 1 Collector 1
P r im a r y P rim a ry
S p a re S pa re
Clusters
A 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 by a HAM.
The use of multiple clusters is optional. Whether you use multiple clusters or just one has no affect on the
operation of the HAM. Clusters simply give you a way to separate one group of collectors from another, so that
you can better deploy and manage your primary and spare collectors in a way that is appropriate for your needs.
Multiple clusters may be useful if you have a large number of SNMP collector hosts 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 other words, the HAM cannot bind
a managed definition in one cluster to a collector process in another.
HAM Cluster Configuration

For host failover to occur, a HAM cluster must have at least one available spare host.
The cluster can have as few as two hosts — one primary and one spare. Or, it can have multiple primary hosts
with one or more spares ready to replace primary hosts that become unavailable.
The ratio of primary hosts to spare hosts is expressed as p + s. For example, a HAM cluster with four primary
hosts and two spares is referred to as a 4+2 cluster.

Types of Spare Hosts

There are two types of spare hosts:
• 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 the active hosts, and binds that host’s managed definition to
the spare’s collector process.
A HAM cluster must have at least one designated spare.
• Floating spare. This type of spare is a primary host that can also act as a backup host for one or more
managed definitions.
Types of HAM Clusters

When the HAM binds a managed definition to a spare (either a designated spare or a floating spare), the spare
becomes an active component of the collector. It remains so unless you explicitly reassign the managed definition
back to its primary host or to another available host in the HAM cluster. This is an important fact to consider
when you plan the hosts to include in a HAM cluster.
There are two types of HAM clusters:
• 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 temporarily takes the place of the primary
that has become unavailable. When the primary becomes available again, you must reassign the managed
definition back to the primary (or to another available host). The primary then resumes its data collection
operations, and the spare resumes its role as backup host.
If you do not reassign the managed definition back to the primary, the primary cannot participate in further
collection operations. Since the primary is not configured as a floating spare, it also cannot act as a spare now
that its collector process is idle. As a result, the HAM cluster loses its failover capabilities if no other spare
is available.
Note: A primary host cannot act as a spare unless it is configured as a floating spare.
• Floating spare cluster. This type of cluster has one or more primary hosts that can also act as a spare.
Failover can occur to a floating spare or to a designated spare.
You do not need to reassign the managed definition back to this type of primary, as you do with primaries
in a fixed spare cluster. When a floating spare primary becomes available again, it assumes the role of a spare.
You can designate some or all of the primaries in a HAM cluster as floating spares. If all the primaries in a
HAM cluster are floating spares, you should never have to reassign a managed definition to another available
host in order to maintain 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 Clusters

The Netcool/Proviso High Availability Manager feature is designed to provide great flexibility in setting up a
HAM cluster. The following illustrations show just a few of the possible variations.
1 + 1, Fixed Spare
The figure below shows a fixed spare cluster with one primary host and one designated spare:
• In the panel on the left, Primary1 is functioning normally. The designated spare is idle.
• In the panel on the right, Primary1 experiences an outage. The HAM unbinds the collector from Primary1
and binds it to the designated spare.
• With the spare in use and no other spares in the HAM cluster, failover can no longer occur — even after
Primary1 returns to service. For failover to be possible again, you must reassign Collector 1 to Primary1. This
idles the collector process on the spare, making it available for the next failover operation if Primary 1 fails again.
Network with Managed Network with Managed

SNMP devices Definitions Hosts SNMP devices Definitions Hosts
Collector 1 Collector 1 Outage

P r im a r y 1 P rim a ry 1
D e s i g n a te d D e s ig n a t e d
S p a re S pa re
Note: When a designated spare serves as the only spare for a single primary, as in a 1+1 fixed spare cluster,
the HAM pre-loads the primary’s collector definition on the spare. This results in a fast failover with a likely loss
of no more than one collection cycle.
The following table shows the bindings that the HAM can and cannot make in this cluster:
Collector Possible Host Bindings Host Bindings Not Possible
Collector 1 Primary1 (default binding) —

Designated spare

2 + 1, Fixed Spare
The figure below shows a fixed spare cluster with two primary hosts and one designated spare:
• In the panel on the left, Primary1 and Primary2 are functioning normally. The designated spare is idle.
• 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 possible again, you must reassign Collector 2 to Primary2. This
idles the collector process on the spare, making it available for the next failover operation.

P r im a r y 1 P r im a r y 1

S p a re S pa re
Collector 1 Primary1 (default binding) Primary2

Designated spare

Designated spare

2 + 1, Both Primaries are Floating Spares

The figure below shows a floating spare cluster with two primary hosts and one designated spare, with each
primary configured as a floating spare:
• In the panel on the left, Primary1 and Primary2 are functioning normally. The designated spare is idle.
• 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 spare continues as the active platform for Collector 2.

Collector 1 P r im a r y 1 / Collector 1 P r im a r y 1 /
F lo a t in g F lo a t in g
S pa re S pa re

P r im a r y 2 / P rim a ry 2 /
F lo a t in g F l o a ti n g
S pa re S p a re
S p a re S pa re
• The following figure shows the same cluster after Primary2 has returned to service. In the panel on the left,
Primary2 is idle, prepared to act as backup if needed.
and binds it to the floating spare, Primary2.

Outage
Collector 1 P r im a r y 1 / Collector 1 P rim a ry 1 /
S pa re S p a re
Collector 2 P rim a ry 2 / Collector 2 P r im a r y 2 /

F l o a ti n g F lo a t in g
S p a re S pa re
D e s ig n a t e d D e s ig n a t e d
S pa re S pa re

Primary2
Designated spare
Collector 2 Primary1 —
Primary2 (default binding)
Designated spare

3+ 2, Fixed Spares
The figure below shows a fixed spare cluster with three primary hosts and two designated spares:
• In the panel on the left, all three primaries are functioning normally. The designated spares are idle.
and binds it to Designated Spare 2. The HAM chose Designated Spare 2 over Designated Spare 1 because
the managed definition for Collector 3 set the failover priority in that order.
Note: Each managed definition sets its own failover priority. Failover priority can be defined differently in
different managed definitions.
• 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 returns to service. For dual failover to be possible again, you must
reassign Collector 3 to Primary3.

Outage
D e s i g n a te d D e s i g n a te d
S p a re 1 S p a re 1
S p a re 2 S pa re 2

Designated Spare 1 Primary3
Designated Spare 2

Designated Spare 2

Designated Spare 2

3+ 2, All Primaries are Floating Spares

The figure below shows a floating spare cluster with three primary hosts and two designated spares, with each
primary configured as a floating spare:
• In the panel on the left, Primary3 had previously experienced an outage. The HAM unbound its default
collector (Collector 3) from Primary3, and bound the collector to the first available spare in the managed
definition’s priority list, which happened to be Designated Spare 2. Now that Primary3 is available again, it
is acting as a spare, while Designated Spare 2 remains the active collector process for Collector 3.
• In the panel on the right, Primary2 experiences an outage. The HAM unbinds Collector 2 from Primary2,
and binds it to the first available spare in the managed definition’s priority list. This happens to be the floating
spare Primary3.
• When Primary2 becomes available again, there will once more be two spares available — Primary2 and
Designated Spare 1.
Network with Managed Hosts Network with Managed Hosts

SNMP devices Definitions SNMP devices Definitions
Collector 1 P r im a r y 1 / Collector 1 P r im a r y 1 /
F lo a t in g F lo a t in g
S pa re S pa re
P r im a r y 2 / P rim a ry 2 / Outage
Collector 2
S pa re Collector 2 S p a re
Collector 3 P rim a ry 3 / P r im a r y 3 /
F l o a ti n g F lo a t in g
S p a re S pa re
Collector 3
D e s i g n a te d D e s i g n a te d
S p a re 1 S p a re 1
D e s ig n a t e d D e s ig n a t e d
S pa re 2 S pa re 2

Primary2
Primary3
Designated Spare 1
Designated Spare 2
Primary3
Designated Spare 1
Designated Spare 2
Primary2
Designated Spare 1
Designated Spare 2

Resource Pools
When you configure a managed definition in the Topology Editor, you specify the hosts that the HAM can bind
to the managed definition, and also the priority order in which the hosts are to be bound. This list of hosts is
called the resource pool for the managed definition.
A resource pool includes:
• 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).
• Zero or more other primary hosts in the cluster.
If you add a primary host to a managed definition’s resource pool, that primary host becomes a floating spare
for the managed definition.
• Zero or more designated spares in the cluster.
Typically, each managed definition includes one or more designated spares in its resource pool.
Note: If no managed definitions include a designated spare in their resource pools, there will be no available spares
in the cluster, and therefore failover cannot occur in the cluster.
How the SNMP Collector Works

The SNMP collector is state-based and designed both to perform initialization and termination actions, and to
“change state” in response to events generated by the HAM or as a result of internally-generated events (like a
timeout, for example).
The following table lists the events that the SNMP collector understands and indicates whether they can be
generated by the HAM.
Event HAM-Generated Description
Load Yes Load collection profile, do not begin scheduling collections.
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 the following table:
SNMP Collector State Event Description
Idle N/A Initial state; a collector number may or may not be assigned;
the collection profile has not been loaded.
Loading Load Intermediate state between Idle and Ready. Occurs after a
Load event. Collector number is assigned, and the collection
profile is being loaded.
Ready N/A Collector number assigned, profile loaded, but not

scheduling requests or performing collections.
Starting Start Intermediate state between Idle and Running. Occurs after a
Start event. Collector number assigned, and profile is being
loaded.
Running N/A Actively performing requests and collections.
Stopping Stop/Pause Intermediate state between Running and Idle.
The following state diagram shows how the SNMP collector transitions through its various states depending upon
events or time-outs:

How Failover Works With the HAM and the SNMP Collector
The following tables illustrate how the HAM communicates with the SNMP collectors during failover for a 1+1
cluster and a 2+1 cluster.
Table 7: HAM and SNMP Collector in a 1+1 Cluster
State of Primary State of Spare Events and Actions
Running Idle The HAM sends the spare the Load event for the specified
collection profile.
Running Ready The HAM sends a Pause event to the spare to extend the
timeout.
Note: If the timeout expires, the spare will perform start actions and
transition to a Running state.
Running Running The HAM sends a Pause event to the collector process that
has been in a Running state for a shorter amount of time.
No response Ready The HAM sends a Start event to the spare.
Table 8: 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 event to the collector process that
has been in Running state for the shorter amount of time.
No Response Idle The HAM sends a Start event to the spare.
No Response Ready The HAM sends a Start event to the spare.
Because more than one physical system may produce SNMP collections, the File Transfer Engine (FTE) must
check every capable system for a specific profile. The FTE retrieves all output for the specific profile. Any
duplicated collections are reconciled by the Complex Metrics Engine (CME).

Creating a HAM Environment

This section describes the steps required to create a 3+1 HAM environment with a single cluster, and with all
three primaries configured as floating spares.
This is just one of the many variations a HAM environment can have. The procedures described in the following
sections indicate the specific steps where you can vary the configuration.
Note: If you are setting up a new Netcool/Proviso environment and plan to use a HAM in that environment,
perform the following tasks in the following order:
1. Install all collectors.
2. Configure and start the HAM.
3. Install all technology packs.
4. Perform the discovery.
Topology Prerequisites
A 3+1 HAM cluster requires that you have a topology with the following minimum components:
• 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.
• 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 141.
Procedures
The general procedures for creating a single-cluster HAM with one designated spare and three floating spares
are as follows:
1. Create the HAM and a HAM Cluster

2. Add the Designated Spare
3. Add the Managed Definitions
4. Define the Resource Pools
5. Save and Start the HAM
The following sections describe these procedures in detail.
Step 1: Create the HAM and a HAM Cluster

To create a High Availability Manager with a single cluster:
1. 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 page 101 and Opening a Deployed Topology on page 141).
2. In the Logical view, right-click High Availability Managers, located as follows:
DataChannels > 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 a HAM-assigned sequential number,
beginning with 1, that uniquely identifies this 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 in Step 6. The following folders appear
under the cluster name:
— Collector Processes
— Managed Definitions
Note: To add additional clusters to the environment, repeat Step 7 through Step 9.
Step 2: Add the Designated Spare

To create a designated spare, you must have a host defined in the Physical view with no SNMP collector assigned
to it. For information on adding a host to a topology, see Step 1: Add the Hosts on page 102.
To add a designated spare to a cluster:
1. In the Logical view, right-click the Collector Processes folder that you created in Step 9 of the
previous section, Step 1: Create the HAM and a HAM Cluster.
2. Select Add Collection Process SNMP Spare from the pop-up menu.
The Add Collection Process SNMP Spare — Configure Collector Process SNMP Spare dialog appears.
3. In the Available hosts field, select the host that you want to make the designated spare.
This field contains the names of hosts in the Physical view that do not have SNMP collectors assigned
to them.
4. In the Port field, specify the default port number, 3002, for the spare’s collector process, then click Finish.
Under the cluster’s Collector Processes folder, the entry Collection Process SNMP Spare <n> appears,
where n is a HAM-assigned sequential number, beginning with 1, that uniquely identifies this designated
spare from others that may be defined in this cluster.
Note: Repeat Step 1 through Step 4 to add an additional designated spare to the cluster.

Step 3: Add the Managed Definitions

A managed definition allows the HAM to bind a collector profile to a collector process.
Note: When you add a managed definition to a HAM cluster, the associated collector process is automatically
added to the cluster’s Collector Processes folder.
To add a managed definition to a HAM cluster:
1. In the Logical view, right-click the Managed Definitions folder that you created in Step 9 of the section
Step 1: Create the HAM and a HAM Cluster on page 163.
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:
— Under the cluster’s Managed Definitions folder, the entry Managed Definition <n> appears, where
n is the collector number you selected in Step 3.
— Under the cluster’s Collector Processes folder, the entry Collector Process [HostName] appears,
where HostName is the host that will be bound to the SNMP collector you selected in Step 3. This host
is the managed definition’s primary host.
Note: Repeat Step 1 through Step 4 to add another managed definition to the cluster.
When you finish adding managed definitions for a 3+1 HAM cluster, the Logical and Physical views might look
like the following:
In this example, the hosts dcsol1a, dcsol1b, and docserver1 are the primaries, and docserver2 is the
designated spare.

Step 4: Define the Resource Pools

A resource pool is a list of the spares, in priority order, that the HAM can bind to a particular managed definition.
When you create a managed definition, the managed definition’s primary host is the only host in its resource pool.
To enable the HAM to bind a managed definition to other hosts, you must add more hosts to the managed
definition’s resource pool.
To add hosts to a managed definition’s resource pool:
1. 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 for Managed Definition 1 (that is, the managed definition
associated with Collector 1).
3. In the Additional Collector Processes list, check the box next to each host to add 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 resource pool, that host becomes a floating spare for the managed definition.
Note: You must add at least one of the hosts in the Additional Collector Processes 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 be added 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 not enabled. Click Finish to complete
the definition of this resource pool. Return to Step 1 to define a resource pool for the next managed definition in
the cluster, or skip to Step 5: Save and Start the HAM if you are finished defining resource pools.

The Configure Managed Definition — Collector Process Order dialog appears, as shown below:
5. Specify the failover priority order for this managed definition. To do so:
5-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.
5-b. Continue moving hosts until the priority list is ordered as you want.
5-c. Click Finish.
In this example, if the primary associated with Managed Definition 1 fails, the HAM 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 the managed definition to docserver1. The designated spare docserver2 is last in priority.
6. Return to Step 1 to define a resource pool for the next managed definition in the cluster, or continue with
the next section if you are finished defining resource pools.
Step 5: Save and Start the HAM

When you finish configuring the HAM as described in the previous sections, you are ready to save the
configuration and start the HAM.
To save and start the HAM:
1. Click Topology > Save Topology to save the topology file containing the HAM configuration.
2. Run the deployer (see Starting the Deployer on page 111), 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 on page 148.
dccmd -action start ham
Monitoring of the HAM environment begins.
For information on using dccmd, see the Netcool/Proviso Command Line Interface Guide.

Creating an Additional HAM Environment

Typically, one HAM is sufficient to manage all the collectors you require in your HAM environment. But for
performance reasons, very large Proviso deployments involving dozens or hundreds of collector processes might
benefit from more than one HAM environment.
HAM environments are completely separate from one another. A host in one HAM environment cannot fail over
to a host in another HAM environment.
To create an additional HAM environment, perform all of the procedures described in Creating a HAM
Environment on page 162.
Modifying a HAM Environment

You can modify a HAM environment by performing any of the procedures in Creating a HAM Environment on
page 162. For example, you can add collectors, add clusters, configure a primary host as a floating spare, change
the failover priority order of a resource pool, and make a number of other changes to the environment, including
moving collectors into or out of a HAM environment.
For information on moving a deployed SNMP collector into or out of a HAM environment, see Moving a Deployed
SNMP Collector to or from a HAM Environment on page 146.
You can also modify the configuration parameters of the HAM components that are writable. For information
on modifying configuration parameters, see Changing Configuration Parameters of Existing Netcool/Proviso
Components on page 143.
Removing HAM Components

You can remove HAM components from the environment by right-clicking the component name and selecting
Remove from the pop-up menu. The selected component and any subcomponents will be removed.
Before you can remove a designated spare (Collection Process SNMP Spare), you must remove the spare from
any resource pools it may belong to. To remove a designated spare from a resource pool, open the managed
definition that contains the resource pool, and clear the check box next to the name of the designated spare to
remove. For information about managing resource pools, see Step 4: Define the Resource Pools on page 165.
Stopping and Restarting Modified Components

If you change the configuration of a HAM or any HAM components, or if you add or remove an existing collector
to or from a HAM environment, you must bounce (stop and restart) the Netcool/Proviso components you
changed The is generally true for all Netcool/Proviso components that you change, not just HAM.
To bounce a component:
1. 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:
— To bounce the HAM with the identifier HAM.dcsol1b.1, run:
dccmd bounce ham.dcsol1b.1
— To bounce all HAMs in the topology, run:
dccmd bounce ham.*.*
— 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 Netcool/Proviso Command Line Interface Guide.
5. Bounce the Channel Manager. For instructions, see Step 15 on page 148.
Note: If your DataView real-time charts no longer work as expected after you perform the above procedure, you
may need to re-start the SilverStream application server. For details, see the appendix on real-time troubleshooting
in the Netcool/Proviso DataView User’s Guide.
Viewing the Current Configuration

During the process of creating or modifying a HAM cluster, you may find it useful to check how the individual
collector processes and managed definitions are currently configured.
To view the current configuration of a collector process or managed definition:
1. 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... Dialog

The following figure shows a collector process configured with three managed definitions.

The configuration values are described as follows:

• dcsol1a. The primary host where this collector process runs.
• 3002. The port through which the collector process receives SNMP data.
• 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... Dialog

The Show Managed Definition... dialog contains the resource pool for a particular managed definition.
This dialog contains the same information that appears in the Show Collector Process... dialog, but for multiple
hosts instead of just one. As such, this dialog gives you a broader view of the cluster’s configuration than a Show
Managed Definition... dialog.
The following figure shows a managed definition’s resource pool configured with four hosts:
Note the following about this managed definition’s resource pool:

• 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 definition is the one on host dcsol1a. The collector process on host
docserver2 is last in the priority list.
• The first three hosts are floating spares. They are flagged as such by each having a primary managed
definition.
• The host docserver2 is the only designated spare in the resource pool. It is flagged as such by not having a
primary managed definition.

Chapter 8: Uninstalling Components
This chapter provides information about uninstalling components. When you perform an uninstall, the
“uninstaller” is the same deployer used to install Netcool/Proviso.
Topic Page
Removing a Component from the Topology 170
Uninstalling Netcool/Proviso 172
Uninstalling the Topology Editor 174
Residual Files 175
Note: The uninstall feature does not uninstall technology packs.
Removing a Component from the Topology

This section describes how to remove an installed component from the topology. It contains the following topics:
• Restrictions and Behavior on page 170
• Removing a Component on page 171
You might have a situation where you have modified a topology by both adding new components and removing
components (marking them “To Be Removed”). However, the deployer can work in only one mode at a time —
installation mode or uninstallation mode. In this situation, first run the deployer in uninstallation mode, then run
it again in installation mode.
Important: After the deployer has completed an uninstall, you must open the topology (loaded from the database)
in the Topology Editor before performing any additional operations.
Restrictions and Behavior

Before you remove a component, note the following:
• You can remove a host only if no components are configured or installed on it.
• You can remove the DataChannel Administrative Component only after all the DataChannels have been
removed.
• 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 view the updated topology.
Note: Once components are marked for deletion, the topology must be consumed by the deployer to propagate the
required changes and load the updated file in the database. When you open the database version of the topology,
the “removed” component will disappear from the topology.

• If you delete a DataChannel or collector, the working directories (such as the FTE and CME) are not
removed. You must delete these directories manually.
To remove one or more components from the topology where the host system no longer exists or is unreachable
on the network, do the following:
• Open the Topology Editor and remove all components related to the host system
• Remove the host system from the topology
• Redeploy the topology, ignoring any messages related to the non-existent or unreachable host.
At deployment, the modified topology is saved to the database without the components that were previously
installed on the host system.
Removing a Component
To remove component from the topology:
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 111).
Note: If you forgot to save the modified topology, the deployer will prompt you to save it first.
The deployer can determine that most of the components described in the topology file are already installed,
and removes the component that is no longer part of the topology.
7. The deployer displays the installation steps page, which lists the steps required to remove the component.
Note that the name of the component to be removed includes the suffix “R” (for “Remove”). For example,
if you are deleting a DataChannel, 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 Editor view is not refreshed automatically.
Reload the topology file from the database to view the updated topology.

Uninstalling Netcool/Proviso
Note: To uninstall Netcool/Proviso, you must have the CD or the original electronic image. The uninstaller will
prompt you for the location of the image.
This section contains the following topics:

• Restrictions and Behavior on page 172
• Performing the Uninstall on page 173
• Uninstalling the Topology Editor on page 174
Restrictions and Behavior

Before you uninstall Netcool/Proviso, note the following restrictions and behavior:
• For distributed deployments, you must uninstall the Netcool/Proviso components in the following order:
— DataLoad
— DataChannel
When uninstalling DataChannel from a host, you must manually stop (kill -9) any running channel
processes (identified by running findvisual). See Chapter B, DataChannels for more information about
the findvisual command.
— DataView
— DataMart
— Netcool/Proviso Database (remove only after all the other components have been removed). The
database determines the operating platform of the Netcool/Proviso environment.
• If you are uninstalling Netcool/Proviso from an AIX system, perform the uninstallation procedure first on
the Solaris system, then on the AIX system.
• 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 the information needed to resume an uninstall. However, if
the ProvisoConsumer directory is removed for any reason, the -Daction=resume command will not
work.
Note: When you reboot your server, the contents of /tmp might get cleaned out.
• 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. The deployer is able to determine the correct steps to be performed.
However, if the component is not in the Installed state (for example, the component was not started), the
Topology Editor deletes the component from the topology — not the uninstaller.
• When the uninstallation is complete, some data files still remain on the disk. You must remove these files
manually. See Residual Files on page 175 for the list of files that must be deleted manually.

Performing the Uninstall

To remove a Netcool/Proviso installation:
1. You can start the uninstaller from within the Topology Editor or from the command line.
To start the uninstaller from the Topology Editor:
— Select Run > Run Deployer for Uninstallation.
To start the uninstaller from the command line:
1-c. Change directory to the directory that contains the deployer. For example:
# cd /opt/IBM/proviso/deployer
# ./deployer.bin -Daction=uninstall
2. The uninstaller opens, displaying a welcome page. Click Next to continue.
Next to continue.
4. A pop-up opens, asking whether you want to download the topology from the database. Click Yes.
5. The database access window prompts for the security credentials. Enter the host name (for example, delphi)
and database administrator password (for example, 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 was successful and saved to the file
/tmp/ProvisoConsumer/Topology.xml. Click Next to continue.
7. The uninstaller displays several status messages, then displays a message stating that the environment status
was successfully downloaded and saved to the 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.

Uninstalling the Topology Editor

To uninstall the Topology Editor, follow the instructions in this section. Do not simply delete the /opt/IBM
directory! Doing so will cause problems when you try to reinstall the Topology Editor. If the /opt/IBM directory
is accidentally deleted, perform the workaround documented in Installing the Topology Editor on page 100.
Note: Uninstall Netcool/Proviso before uninstalling the Topology Editor.
To uninstall the Topology Editor:
1. Log in as root.
2. Set and export your DISPLAY variable (see Setting Up a Remote X Window Display on page 41).
3. Change directory to the install_dir/uninstall directory. For example:
# cd /opt/IBM/proviso/uninstall
#./Uninstall_Topology_Editor
5. The Uninstall wizard opens. Click Uninstall to uninstall the Topology Editor.
6. When the script is finished, click Done.

Residual Files
When you uninstall Netcool/Proviso, some of the files remain on the disk and must be removed manually. After
you exit from the deployer (in uninstall mode), you must delete these residual files and directories manually.
Perform the following steps:
1. As oracle, enter the following commands to stop Oracle:

sqlplus "/ as sysdba"
shutdown abort
exit
lsnrctl stop
2. As root, enter the following commands to delete these files and directories:
rm -fR /tmp/PvInstall
rm -fR /var/tmp/PvInstall
rm -fR /opt/Proviso
rm -fR $ORACLE_BASE/admin/PV
rm -fR $ORACLE_BASE/admin/skeleton
rm -fR $ORACLE_HOME/dbs/initPV.ora
rm -fR $ORACLE_HOME/dbs/lkPV
rm -fR $ORACLE_HOME/dbs/orapwPV
rm -fR $ORACLE_HOME/lib/libpvmextc.so
rm -fR $ORACLE_HOME/lib/libmultiTask.so
rm -fR $ORACLE_HOME/lib/libcmu.so
rm -fR $ORACLE_HOME/bin/snmptrap
rm -fR $ORACLE_HOME/bin/notifyDBSpace
rm -fR $ORACLE_HOME/bin/notifyConnection
where $ORACLE_BASE is /opt/oracle and $ORACLE_HOME is /opt/oracle/product/9.2.0.
3. Enter the following commands to clear your Oracle mount points and remove any files in those directories:
rm -r /raid_2/oradata/*
rm -r /raid_3/oradata/*
4. Enter the following command to delete the temporary area used by the deployer:
rm -fr /tmp/ProvisoConsumer
5. Delete the installer file using the following command:
rm /var/.com*
6. Delete the startup file using the following command:
rm /etc/rc.d/init.d/netpvmd

Appendix A: Deployment Considerations
Before configuring your deployment, you must be familiar with the information in this appendix. The topics are
as follows:
Topic Page
Co-Location Rules 176
Remote Installation 178
Co-Location Rules
Table 9 lists how many of each component can be deployed per Netcool/Proviso system and whether multiple
instances can be installed on the same server.
In this table:
• 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 per channel and 8 channels, theoretically N=320. However,
the practical limit is probably much lower.
• System — The entire Netcool/Proviso system.
• Per host — A single physical host can be partitioned using zones, which effectively gives you multiple hosts.
Note that all CME, DLDR, FTE, and LDR components within a channel must share the same filesystem.
Table 9: Co-Location Rules
Co-Location Co-Location Constraints

Component Number of Instances Allowed
Constraints Supported by Deployer?
AMGR One per host that supports Yes

DataChannel components
BCOL • N per system Yes
• One per corresponding
subchannel
CME One per subchannel Filesystem Yes
CMGR One per system Yes
Database One per system Yes
Database One per DataChannel; maximum Yes

channel of 8

Table 9: Co-Location Rules
Co-Location Co-Location Constraints

Component Number of Instances Allowed
Constraints Supported by Deployer?
DataLoad • N per system Yes

(SNMP
collector)
subchannel
• One per host
DataMart • N per system Yes

• One per host
DataView • N per system One per system. Installs one on

the primary server; subsequent
• One per host
servers require manual
installation.
Discovery Server • N per system Co-locate with Yes

• One per host corresponding
DataMart
DLDR One per channel Filesystem Yes
FTE One per subchannel Filesystem Yes
HAM N+M per system, where N is the Yes

number of collectors that HAM is
monitoring, and M is the number
of standby collectors
LDR One per channel Filesystem Yes
Log One per system Yes
UBA (simple) • N per system Yes

subchannel
UBA (complex) Pack-dependent Pack-dependent Pack-dependent
In the Logical view of the Topology Editor, the DataChannel component contains the subchannels, LDR, and
DLDR components, with a maximum of 8 channels per system. The subchannel contains the collector, FTE, and
CME, with a maximum of 40 subchannels per channel.

Remote Installation
Netcool/Proviso 4.4.3 supports remote installations for the DataChannel and DataLoad components only.
If you have a mixture of components — some that support remote installation and some that do not — the
deployer treats the node as not supporting remote installation. For example, if you have DataChannel and
DataMart on the same “remote” node (in respect to the primary deployer), the deployer treats the node as remote.
Run the deployer locally on that node to install the components (as in column 3 of DataMart or column 3, point
2 of DataChannel in the table).
Table 10 provides remote installation information for each component.
Table 10: Remote Installation Details
Component to If FTP and

If FTP is Possible, But REXEC/RSH Neither FTP Nor REXEC/RSH is
be Installed REXEC/RSH are
are not Possible Possible
Remotely Possible
DataLoad Supported Option 1: Option 1:

SNMP
1. Unselect the Remote 1. Unselect the FTP option
Command Execution during the installation.
option during the installation.
The deployer creates a
The deployer creates and directory with the DataLoad
transfers the directory with SNMP package in it.
the DataLoad SNMP package
in it. 2. Copy the directory to the
target system.
2. As root, log in to the remote
system and manually run the 3. As root, log in to the remote
system and manually run the
run.sh script.
run.sh script.
Option 2:
Option2:
1. Connect to the remote
machine and launch the
deployer again (either in machine and launch the
graphical or CLI mode) using deployer again (either in
graphical or CLI mode) using
the product CD.
the product CD.
If the CD is not available, you
can FTP or NFS the If the CD is not available, you
can FTP or NFS the
DataLoad SNMP directory
and deployer package to the DataLoad SNMP directory
remote machine. and deployer package to the
remote machine.
2. The deployer connects to the
database. 2. The deployer connects to the
database, then installs the
3. Install the DataLoad DataLoad component on this
component. machine.


Remotely Possible
DataChannel Supported Option 1: Option 1:
1. Unselect the Remote 1. Unselect the FTP option

Command Execution during the installation.
option during the installation.
The deployer creates a
The deployer creates and directory with the
transfers the directory with DataChannel package in it.
the DataChannel in it.
2. Copy the DataChannel
2. As root, log in to the remote directory to the target system.
3. As root, log in to the remote
run.sh script.
Option 2: run.sh script.
Option2:
deployer again (either in
graphical or CLI mode) using machine and launch the
the product CD. deployer again (either in
If the CD is not available, you the product CD.
can FTP or NFS the
DataChannel directory and If the CD is not available, you
can FTP or NFS the
deployer package to the
remote machine. DataChannel directory and
2. The deployer connects to the remote machine.
database.
3. Install the DataChannel database, then installs the
component. DataChannel component on
this machine.
DataMart Not supported Not supported 1. Connect to the remote
the product CD.
can FTP or NFS the
DataMart and deployer
package to the remote
machine.
DataMart component on this
machine.


Remotely Possible
DataView Not supported Not supported 1. Connect to the remote

the product CD.
can FTP or NFS the
DataView and deployer
package to the remote
machine.
DataView component on this
machine.
Database Not supported Not supported 1. Copy the topology.xml
file to the remote machine.
deployer (either in graphical
or CLI mode using the
product CD.
can FTP or NFS the
Database directory and
remote machine.


Appendix B: DataChannels
This chapter provides detailed information about the DataChannel architecture.

Topic Page
DataChannel Architecture 182
Starting the DataLoad SNMP Collector 185
DataChannel Management Components in a Distributed Configuration 186
SNMP Traps from Logs 187
DataChannel Architecture
A DataChannel is composed of the File Transfer Engine (FTE), Complex Metrics Engine (CME), and Daily and
Hourly Loaders. The FTE and CME components are assigned to one or more subchannels.
Data is produced by 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. The Hourly Loader
computes group aggregations from resource aggregation records. The Daily Loader provides statistics on metric
channel tables and metric tablespaces and inserts data into the database.
Figure 5 illustrates the data flow across a single DataChannel with two subchannels.
Figure 5: DataChannel Standard

Data is moved from one channel component to another as files. These files are written to and read from staging
directories between each component. Within each staging directory there are subdirectories name do, output

and done. The do subdirectory contains files acquired by the subsystem that are waiting to be processed. The
output subdirectory stores data for the next subsystem to work on. After files are processed, they are moved to
the done directory. All file movement is accomplished by the FTE component.
Data Aggregation
A DataChannel aggregates data collected by collectors for eventual use by DataView reports. The DataChannel
provides online statistical calculations of raw collected data, and detects real-time threshold violations.
Aggregations include:
• Resource aggregation for every metric and resource
• Group aggregation for every group
• User-defined aggregation computed from raw data
Threshold detections in real time include:
• Raw data violating configured thresholds
• Raw data violating configured thresholds and exceeding the threshold during a specific duration of time
• Averaged data violating configured thresholds
Management Programs and Watchdog Scripts

The following table lists the names and corresponding watchdog scripts for the DataChannel management
programs running on different DataChannel hosts.
Table 11: Programs and Scripts
Corresponding
Component Program Executable1 Notes
Watchdog Script
Channel Name Server CNS cnsw

Runs on the host running the
Log Server LOG logw
Channel Manager.
Channel Manager CMGR cmgrw
Application Manager AMGR amgrw One per subchannel host and

one on the Channel Manager
host.
1. 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 as CMGR_visual.
The watchdog scripts run every few minutes from cron. Their function is to monitor their corresponding
management component, and to restart it, if necessary. You can add watchdog scripts for the Channel Manager
programs to the crontab for 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 different hosts running different
DataChannel programs. The following example shows the 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>&1
1,6,11,16,21.26,31,36,41,46,51,56 1-31 1-12 0-6 /opt/datachannel/bin/logw > /dev/null
2>&1
2,7,12,17,22.27,32,37,42,47,52,57 1-31 1-12 0-6 /opt/datachannel/bin/cmgrw >
/dev/null 2>&1
3,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>&1
1,6,11,16,21,26,31,36,41,46,51,56 1-31 1-12 0-6 /opt/datachannel/bin/logw > /dev/null
2>&1
2,7,12,17,22,27,32,37,42,47,52,57 1-31 1-12 0-6 /opt/datachannel/bin/cmgrw >
/dev/null 2>&1
3,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 this example:
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 Program Names

The DataChannel subchannel application programs are listed in Table 12.
Table 12: DataChannel Subchannel Application Program Names
DataChannel
Description Example
Program1
BCOL.n.c Bulk collector process for channel n, with collector number c BCOL.1.100
FTE.n.s File Transfer Engine for channel n, subchannel s FTE.1.1
CME.n.s Complex Metrics Engine for channel n, subchannel s CME.2.1
LDR.n Hourly Loader for channel n LDR.2
DLDR.n Daily Loader for channel n DLDR.1

1. The actual application’s executable file visible in the output of ps -ef is named XXX_visual, where XXX is an entry
in this column. For example, the file running for FTE.1.1 is seen as FTE.1.1_visual.
Note: For historical reasons, the SNMP DataLoad collector is managed by Netcool/Proviso DataMart,
and does not appear in Table 12.
Starting the DataChannel Management Programs

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 host
If the DataChannel management programs are running on all DataChannel hosts, start the application
programs on all DataChannel hosts by following these 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 all configured DataChannel hosts:
./dccmd -action start -channel all
The command shows a success message like the following example.
Done: 12 components started, 0 components already running
See the Netcool/Proviso Command Line Interface Guide for information about the dccmd command.
Starting the DataLoad SNMP Collector

Once you have started the DataChannel components, check every server that hosts a DataLoad SNMP collector.
to make sure the collectors are running. To check whether a collector is running, run the following command:
ps -ef | grep -i pvmd
If the collector is running, you will see output similar to the following:
pvuser 27118 1 15 10:03:27 pts/4 0:06 /opt/dataload/bin/pvmd -nologo
-noherald /opt/dataload/bin/dc.im -headless -a S
If a collector is not running, perform the following steps:
1. Log into the server that is running Netcool/Proviso SNMP DataLoad by entering the username and
password you specified when installing 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 unset the environment variable by
issuing the following command from a BASH shell command 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 has been successfully started:
PVM Collecting Daemon is running.
DataChannel Management Components in a Distributed

Configuration
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 application server 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:
• 1 Application Manager (AMGR)
• 2 Complex Metric Engines (CME)
• 2 File Transfer Engines (FTE)
• 2 Hourly Data Loaders (LDR)
• 2 Daily Data Loaders (DLDR)
Each program has its own set of program and staging directories.
Manually Starting the Channel Manager Programs

If you need to manually start the Channel Manager programs, you must do so in a certain order. After a manual
start, the program’s watchdog script restarts the program as required.
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
To manually start the DataChannel programs on all hosts in your DataChannel configuration:
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 185.
SNMP Traps from Logs

The log-to-traps feature scans the DataChannel log file (by default, proviso.log) for the specified messages.
If matching messages are found, the feature sends an SNMP trap to the specified host and port.
You enable the log-to-traps feature by setting up one or more rules files that describe the log file messages you
want to convert to SNMP traps.
For more information, see the Technical Note entitled Setting SNMP Traps for Log Messages.

Appendix C: Aggregation Sets
This appendix describes how to configure and install aggregation sets. The topics are as follows:
Topic Page
Overview 188
Configuring Aggregation Sets 188
Installing Aggregation Sets 192
Linking DataView Groups to Timezones 197
Overview
An aggregation set is a grouping of network management raw data and computed statistical information stored
in the Netcool/Proviso database for a single timezone. For example, if your company provides network services
to customers in both the Eastern and Central US timezones, you must configure two aggregation sets.
Because each aggregation set is closely linked with a timezone, aggregation sets are sometimes referred to as
timezones in the in Netcool/Proviso documentation. However, the two concepts are separate.
Note: “Aggregation set” is abbreviated to “Aggset” in some setup program menus.
Configuring Aggregation Sets

When you configure an aggregation set, the following information is stored in the database:
• The timezone ID number associated with this aggregation set.
• The timezone offset from GMT, in seconds.
• 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 can configure an aggregation set to ignore DST transitions.)
You configure an aggregation set either by creating a new set or by modifying an existing set. The first aggregation
set is installed by default when you install Netcool/Proviso Datamart, so if your network will monitor only one
timezone, you need only to configure the existing set.
To configure an aggregation set:
1. 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 Netcool/Proviso DataMart program files are installed. For
example:
# cd /opt/datamart

3. Load the DataMart environment variables into your current shell’s environment using the following
command:
# . ./dataMart.env
4. Change to the bin directory:
# cd bin
# ./create_modify_aggset_def
The following menu is displayed:
--------------------------------------------------
Netcool/Proviso Database
Date: <Current Date> <Current Time>
Script name: create_modify_aggset_def
Script 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 for PV_ADMIN. The script prompts
twice for the password you set up for PV_ADMIN.
==> Enter password for PV_ADMIN : PV
==> Re-enter password : PV
Note: The script obtains the DB_USER_ROOT setting from the Netcool/Proviso database configured in
previous chapters, and constructs the name of the Netcool/Proviso database administrative login name,
PV_ADMIN, from that base. If you set a different DB_USER_ROOT setting, the “Database user” entry
reflects your settings. For example, if you previously set DB_USER_ROOT=PROV, this script would generate
the administrative login name PROV_ADMIN.
7. To configure the first aggregation set, type 2 at the Choice prompt and press Enter 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:
Num | OffSet | Time zone Name | Short | Long
| Hours | | Description | Description
___________________________________________________________________________________
[ 1] : -10:00 | America/Adak | HAST | Hawaii-Aleutian Standard Time
[ 2] : -10:00 | Pacific/Rarotonga | CKT | Cook Is. Time
[ 3] : -09:00 | America/Anchorage | AKST | Alaska Standard Time
[ 4] : -09:00 | AST | AKST | Alaska Standard Time
[ 5] : -08:00 | PST | PST | Pacific Standard Time
[ 6] : -07:00 | MST | MST | Mountain Standard Time
[ 7] : -06:00 | America/Mexico_City| CST | Central Standard Time
[ 8] : -06:00 | CST | CST | Central Standard Time
[ 9] : -05:00 | EST | EST | Eastern Standard Time
[10] : -04:00 | America/Santiago | CLT | Chile Time
[11] : -03:00 | America/Sao_Paulo | BRT | Brazil Time
[12] : -01:00 | Atlantic/Azores | AZOT | Azores Time
[13] : 000:00 | Europe/London | GMT | Greenwich Mean Time
[14] : +01:00 | Europe/Paris | CET | Central European Time
[15] : +01:00 | ECT | CET | Central European Time
[16] : +02:00 | Africa/Cairo | EET | Eastern European Time
[17] : +02:00 | Europe/Helsinki | EET | Eastern European Time
[18] : +02:00 | Europe/Bucharest | EET | Eastern European Time
[19] : +03:00 | Asia/Baghdad | AST | Arabia Standard Time
[20] : +03:00 | Europe/Moscow | MSK | Moscow Standard Time
[21] : +04:00 | Asia/Baku | AZT | Azerbaijan Time
[22] : +05:00 | Asia/Yekaterinburg | YEKT | Yekaterinburg Time
[23] : +06:00 | Asia/Novosibirsk | NOVT | Novosibirsk Time
[24] : +07:00 | Asia/Krasnoyarsk | KRAT | Krasnoyarsk Time
[25] : +08:00 | Asia/Irkutsk | IRKT | Irkutsk Time
[26] : +09:00 | Asia/Yakutsk | YAKT | Yakutsk Time
[27] : +10:00 | Australia/Sydney | EST | Eastern Standard Time (New
South Wales)
[28] : +11:00 | Pacific/Noumea | NCT | New Caledonia Time
[29] : +12:00 | Pacific/Auckland | NZST | New Zealand Standard Time
[30] : +12:00 | Asia/Anadyr | ANAT | Anadyr Time
==> Select Time Zone number [1-30 ] (E : Exit) : 9
9. Type the number of the timezone you want to associate with aggregation set 0. For example, type 9 for
Eastern Standard Time.
The script prompts:
==> Select an Aggset ID to add/modify (E: Exit) : 0
To associate the specified timezone, EST, with the database’s default aggregation set, type 0.
10. The script asks whether you want your aggregation set to include Daylight Saving Time (DST) transition
dates:
Does your Time Zone manage DST [Y/N] : Y
For most time zones, type Y and press Enter.

11. The script displays the results:

Complete with Success ...
The following Time Zone has been modified:

___________________________________________________________________________________
| | seconds | |
___________________________________________________________________________________
0 | 1970/01/01 00:00:00 | 0 | GMT | Aggset created

0 | 2004/09/29 22:00:00 | -14400 | EST_2004_DST | Aggset created
0 | 2004/10/31 06:00:00 | -18000 | EST_2004 | Aggset created
Note: The dates that appear in your output will most likely be different from the 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 creates a 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 :
___________________________________________________________________________________
______________

| | seconds | |
___________________________________________________________________________________
______________
1 | 2004/09/29 23:00:00 | -18000 | CST_2004_DST | Aggset created

1 | 2004/10/31 07:00:00 | -21600 | CST_2004 | Aggset created
16. Press Enter to return to the main menu, where you can add more aggregation sets, or type 0 to exit.
The next step is to install the aggregation sets on the server on which you installed Netcool/Proviso DataMart.
Installing Aggregation Sets

When you install DataMart, aggregation set 0 is automatically installed. If you configured only the default
aggregation set (in Configuring Aggregation Sets on page 188), you can skip this section. However, f you configured
timezones for additional aggregation sets, you must install the non-zero sets using the steps in this section.
Step 1: Start the Netcool/Proviso Setup Program

Start the setup program by following these steps:
1. 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:

Netcool/Proviso <version number> - [Main Menu]
1. Install
2. Upgrade
3. Uninstall
0. Exit
Choice [1]> 1
4. Type 1 at the Choice prompt and press Enter. The Install menu is displayed:
Netcool/Proviso <version number> - [Install]
1. Netcool/Proviso Database Configuration
0. Previous Menu
Choice [1]> 1
Step 2: Set Aggregation Set Installation Parameters

5. Type 1 at the Choice prompt and press Enter. Setup displays the installation environment menu:
Netcool/Proviso Database Configuration <version number> - [installation environment]
1. PROVISO_HOME : /opt/Proviso
2. DATABASE_DEF_HOME : -
3. CHANNELS_DEF_HOME : -
4. AGGRSETS_DEF_HOME : -
5. Continue
0. Exit
Choice [5]> 5
Note: Menu options 2, 3, and 4 are used later in the installation process.
6. 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 Choice prompt and correct the directory location.
7. The script displays the component installation menu:
Netcool/Proviso Database Configuration <version number> - [component installation]
1. Database
2. Channel
3. Aggregation set
0. Exit
Choice [1]> 3

8. Type 3 at the Choice prompt and press Enter. The script displays the installation environment menu:
Netcool/Proviso Aggregation Set <version number> - [installation environment]
1. PROVISO_HOME : /opt/Proviso
2. ORACLE_HOME : /opt/oracle/product/9.2.0
3. ORACLE_SID : PV
4. DB_USER_ROOT : -
5. Continue
0. Previous Menu
Choice [5]> 4
9. Type 4 at the Choice prompt and press Enter to specify the same value for DB_USER_ROOT that you
specified in previous chapters. This manual’s default value is PV.
Enter value for DB_USER_ROOT [] : PV
10. Make sure that the values for PROVISO_HOME, ORACLE_HOME, and ORACLE_SID are the same
ones you entered in previous chapters. Correct the values if necessary.
11. Type 5 at the Choice prompt and press Enter. Setup displays the Aggregation Set installation options menu:
Netcool/Proviso Aggregation Set <version number> - [installation options]
1. List of configured aggregation sets

2. List of installed aggregation sets
3. Number of the aggregation set to install : -
4. Channel where to install aggregation set : (all)
5. Start date of aggregation set : <Current Date>
6. Continue
0. Back to options menu
Choice [6]>
Note: Do not change the value for option 4. Retain the default value, “all.”
12. The first time you use any menu option, the script prompts for the password for PV_ADMIN:
Enter password for PV_ADMIN : PV

13. Use menu option 1 to list the aggregation sets you configured in Configuring Aggregation Sets on page 188. The
script displays a list similar to the following:
============= LIST OF CONFIGURED AGGREGATION SETS ============
Num Effect Time Name Time lag

---- --------------------- ------------------------------------------- --------
0 01-01-1970 00:00:00 GMT +0h
04-01-2007 07:00:00 EST_2007_DST -4h
04-02-2006 07:00:00 EST_2006_DST -4h
04-03-2005 07:00:00 EST_2005_DST -4h
04-04-2010 07:00:00 EST_2010_DST -4h
04-05-2009 07:00:00 EST_2009_DST -4h
04-06-2008 07:00:00 EST_2008_DST -4h
09-29-2004 22:00:00 EST_2004_DST -4h
10-25-2009 06:00:00 EST_2009 -5h
10-26-2008 06:00:00 EST_2008 -5h
10-28-2007 06:00:00 EST_2007 -5h
10-29-2006 06:00:00 EST_2006 -5h
10-30-2005 06:00:00 EST_2005 -5h
10-31-2004 06:00:00 EST_2004 -5h
10-31-2010 06:00:00 EST_2010 -5h
1 04-01-2007 08:00:00 CST_2007_DST -5h
04-02-2006 08:00:00 CST_2006_DST -5h
04-03-2005 08:00:00 CST_2005_DST -5h
04-04-2010 08:00:00 CST_2010_DST -5h
04-05-2009 08:00:00 CST_2009_DST -5h
04-06-2008 08:00:00 CST_2008_DST -5h
09-29-2004 23:00:00 CST_2004_DST -5h
10-25-2009 07:00:00 CST_2009 -6h
10-26-2008 07:00:00 CST_2008 -6h
10-28-2007 07:00:00 CST_2007 -6h
10-29-2006 07:00:00 CST_2006 -6h
10-30-2005 07:00:00 CST_2005 -6h
10-31-2004 07:00:00 CST_2004 -6h
10-31-2010 07:00:00 CST_2010 -6h
2 aggregation sets configured
Press enter...
14. Select option 2 to list the aggregation sets already installed. The output is similar to the following:
============== LIST OF CREATED AGGREGATION SETS ==============
============ X: created ==== #: partially created ============
Channels 0
| 1
AggSets -----------------------------------------------------------------------
| 0 X
Press enter...
Remember that aggregation set 0 is automatically installed when you install the database channel, and
continues to be installed even if you modified set 0 by assigning a different timezone.
15. Select option 3 to designate the aggregation set to install. In the examples above, set 0 is already installed, but
set 1 is waiting to be installed. Thus, enter 1 at the prompt:
Enter Aggregation Set number between 1 and 998 : 1

16. By default, the date to start collecting data on the designated aggregation set is today’s date. You can instead
use menu option 5 to designate a future date to start collecting data. Set an appropriate future date for your
installation.
Enter start date (GMT) using Oracle format 'yyyy.mm.dd-hh24' : 2009.04.13-00
WARNING! 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
17. When all menu parameters are set, type 6 at the Choice prompt and press Enter.
Step 3: Edit Aggregation Set Parameters File

18. 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, as shown in this example:
#
# Netcool/Proviso Datamart
# <Current Date>
#
#
# Channel C01: GROUPS DAILY aggregates storage
#
[AGGSETREG/C01/1DGA/TABLE/CURRENT]
PARTITION_EXTENTS=5
PARTITION_SIZE=100K
#
[AGGSETREG/C01/1DGA/TABLE/HISTORIC]
PARTITION_EXTENTS=5
PARTITION_SIZE=100K
#
[AGGSETREG/C01/1DGA/TABLESPACE/CURRENT]
CREATION_PATH=/raid_2/oradata
EXTENT_SIZE=64K
SIZE=10M
#
[AGGSETREG/C01/1DGA/TABLESPACE/HISTORIC]
CREATION_PATH=/raid_3/oradata
EXTENT_SIZE=64K
SIZE=10M
#
# Channel C01: RESOURCES DAILY aggregates storage
#
[AGGSETREG/C01/1DRA/TABLE/CURRENT]
PARTITION_EXTENTS=5
PARTITION_SIZE=100K
#
...
19. Do not make changes to this file unless you have explicit instructions from Professional Services.
Only if you have guidelines from Professional Services for advanced configuration of your aggregation sets,
make the suggested edits.
Save and close the file.

20. When you close the configuration file, the script checks the file parameters and starts 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
Netcool/Proviso Aggregation Set 1 on Channel 1 successfully

installed !
Press Enter...
Linking DataView Groups to Timezones

Once you have configured and installed the aggregation sets, you must link DataView groups to a timezone. You
can link a defined timezone to a calendar you create in the DataView GUI, or the CME Permanent calendar (a
24-hour calendar).
When you link a group to a specific timezone and calendar, all subgroups inherit the same timezone and calendar.
Best practice:
Use a separate calendar for each timezone. If you link multiple timezones to the same calendar, a change to
one timezone calendar setting will affect all the timezones linked to that calendar.
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 Netcool/Proviso internal timezone list. See Configuring
Aggregation Sets on page 188 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 set configuration.
3. At a shell prompt, enter a command similar to the following, which uses the Resource Manager’s CLI to link
the group to the timezone:
resmgr -import segp -colNames “npath tz.name cal.name” -file linkGroupTZ.txt
To unlink a timezone:
• Use the resmgr command. For example:
resmgr -delete linkGroupEST -colNames “npath tz.name cal.name” -file linkGroupTZ.txt

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: Installing Multiple DataView Servers
This appendix describes how to install and configure DataView on multiple servers in one of the following
configurations:
• DataView cluster, where the DataView servers function together as a single system.
• Multi-SilverMaster database configuration, where the DataView servers function independently.
Topic Page
DataView Cluster 200
Multi-SilverMaster Database Installation 207
Combined Cluster and Multi-SilverMaster Configuration 220
SilverStream Installation on a Secondary Server 221
Note: To display DataView real-time charts, you must have the Java runtime environment (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.
DataView Cluster
A Netcool/Proviso DataView cluster consists of multiple SilverStream servers operating together as a single
system and accessing the same set of report and configuration data. By sharing the processing load on different
hosts, a cluster allows you to scale your DataView deployment.
In a clustered environment, one of the servers is the primary server, and the others are secondary servers. The
Netcool/Proviso installer installs DataView and the SilverStream application server on the primary server, as
described in Add a DataView on page 106. The following sections describe the additional steps you must perform
to install DataView and SilverStream on the secondary servers.
Before You Begin

The primary server and all clustering components must be installed before you begin installing Netcool/Proviso
DataView on secondary servers. For information about SilverStream clusters and cluster components, see the
Novell exteNd Application Server Administration Guide.

Before installing Netcool/Proviso DataView in a distributed environment, ensure that the SilverStream cluster is
properly set up. Verify that:
• Each server has a unique IP address.
• Each server in the cluster can communicate over TCP/IP.
• Each server in the cluster can communicate with the Netcool/Proviso Database.
• Load balancing hardware can communicate with each server.
• The primary SilverStream server is installed.
• Each SilverStream server has been shut down.
Important: You must install the SilverStream Cache Manager on the most reliable host in the cluster to prevent
this single point of failure within the cluster and to ensure the operation of the DataView servers in fail-over mode.
About a Distributed Architecture

The following diagram illustrates a distributed Netcool/Proviso system configuration, including two clustered
DataView servers.
Choosing a Load Balancer

You can choose from a variety of load balancers to use with a DataView cluster. Features your load-balancer
should have include:
• Basic IP-based load balancing
• Sticky sessions based on incoming IP
• Up/down status based on checking for a listening port
IBM has qualified DataView clustering using Cisco 11051 Content Services Switch (CSS) as a replacement for the
now unsupported Cisco LocalDirector 416/417 load balancer.
The following is the link to the CSS Basic Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_401/bsccfggd/index.htm

Installing a DataView Cluster

You can install the Netcool/Proviso DataView server in a clustered configuration by installing DataView content
on every DataView host belonging to the cluster.
Use the Netcool/Proviso installer to install the DataView server on the first server (the primary server) in the
cluster, as described in Add a DataView on page 106. You then use the following instructions to install the
DataView content on the secondary severs in the cluster.
The following instructions assume an installation of a DataView cluster containing two servers:
• Server 1: called host A in the instructions
• Server 2: called host B in the instructions
The instructions assume that:
• Netcool/Proviso DataView and the SilverStream application server have already been installed on host A,
the primary server in the DataView cluster. For information on installing DataView and SilverStream on the
primary server, see Add a DataView on page 106.
• The SilverStream server has already been installed on host B, without running SilverMaster.init during
the installation.
For information on installing SilverStream, see SilverStream Installation on a Secondary Server on page 221.
Note: The secondary server should use the primary server’s SilverMaster database.
• The Oracle client has been installed on host B.

• Both the primary and secondary server in the DataView cluster store DataView, SilverStream, and Oracle in
the same respective directories. For example, host A and host B store DataView, SilverStream, and Oracle
in the following directories:
— /opt/dataview
— /opt/silverstream
— /opt/oracle/product/9.2.0.6
To install a secondary DataView server in a DataView cluster:
1. Log in as root to host A.

2. Change to the /opt/dataview directory by entering the following command:
cd /opt/dataview
3. Tar all files in the DV_HOME directory on host A that were created during the primary DataView installation
by entering the following command:
tar –cvf dv.tar *
4. Change to the /usr/X11R6 directory on host A by entering the following command:
cd /usr/X11R6
5. Tar the Xvfb files in the directory by entering the following command:
tar cvf X11R6.tar /usr/X11R6
6. Log on as root to host B.
7. Untar the Xvfb files on host B by entering the following command:
tar xvf /usr/X11R6

8. Copy the Xvfb and SilverStream scripts from the /etc/init.d directory on host A to the
/etc/init.d directory on host B.
9. Change to the /etc/rc3.d directory on host B by entering the following command:
cd /etc/rc3.d
10. Create links for the Xvfb and SilverStream scripts to the start and stop files in the /etc/rc3.d
directory by entering the following commands:
ln -s /etc/init.d/Xvfb ./S98Xvfb
ln -s /etc/init.d/Xvfb ./K98Xvfb
ln -s /etc/init.d/SilverStream ./S98SilverStream
ln -s /etc/init.d/SilverStream ./K98SilverStream
11. On host B, manually create a directory similar to the DV_HOME directory (/opt/dataview) on host A.
Creating a similar directory prevents having to make any modifications.
12. Transfer the file dv.tar from host A into the /opt/dataview directory on host B.
While in /opt/dataview on host B, enter the following commands:
ftp hosta
cd /opt/dataview
binary
get dv.tar
13. Untar the contents of dv.tar file in the /opt/dataview directory on host B.
tar –xpvf dv.tar
14. Copy $SSHOME/.agprofile (typically, /opt/silverstream) on host B to a backup file, as in the
following example:
cd /opt/silverstream
ls -l -a
total 98
drwxr-xr-x 25 pvuser staff 1024 May 31 14:41 .
drwxr-xr-x 11 root sys 512 Jun 20 09:35 ..
drwxr-xr-x 2 pvuser staff 512 May 30 14:09 AgFullText
-rw-r--r-- 1 pvuser staff 565 May 30 14:05 .aginstdefs
-rw-r--r-- 1 pvuser staff 4221 May 30 14:22 .agprofile
.
.
.
cp .agprofile .agprofile.backup27June06
After you create the backup file, copy $SSHOME/.agprofile on host A to $SSHOME on host B. This
action overwrites the .agprofile in $SSHOME on host B. There should be no need to enter manual edits
to .agprofile.
15. Start the SilverStream server on host B.
After you start SilverStream server using the server’s console, the following startup messages should appear,
signifying the successful installation of the secondary DataView server on host 2.
Java Version: Sun Microsystems Inc. 1.3.1_20 (1.3.1_20-b03)

JVM Version: Sun Microsystems Inc. Java HotSpot(TM) Server VM mixed mode
SilverStream Server loading properties from:
/opt/silverstream/Resources/httpd.props

SilverStream Server using name service port 54890.

Starting the JBroker orb naming service on port 54890 on host pmg01.usma.ibm.com
The naming service started successfully
Cannot launch JBrokerMQ server as port value could not be obtained from props file
FullText Indexer version: 4.0A9/7.0A9
SilverStream Server [Build Number:Release4.0.0 (020918_1)] serving at:
http://pmg01.usma.ibm.com:8080 (runtime, design, admin)
Fri May 23 15:57:34 EDT 2008 . Attempting to parse XML file using internal user
authentication.
Fri May 23 15:58:24 EDT 2008 . New XML file
http://pmg01.usma.ibm.com:8080/PV/SilverStream/Objectstore/General/GQEDV.xml
loaded successfully!!!
authentication.
http://pmg01.usma.ibm.com:8080/PV/SilverStream/Objectstore/General/GQEPS.xml
authentication.
http://pmg01.usma.ibm.com:8080/PV/SilverStream/Objectstore/General/GQECS.xml
Fri May 23 15:58:45 EDT 2008 . Setting environment --> Raw Retention Period In
Days : 32
Fri May 23 15:58:45 EDT 2008 . Setting environment --> Daily Retention Period In
Days : 200
Fri May 23 15:58:45 EDT 2008 . Setting environment --> Weekly Retention Period In
Weeks : 80
Fri May 23 15:58:45 EDT 2008 . Setting environment --> Monthly Retention Period
In Months : 18
Fri May 23 15:58:45 EDT 2008 . Setting environment --> Starting Day Of Week Is
Sunday : true
Fri May 23 15:58:45 EDT 2008 . General Directory :
http://pmg01.usma.ibm.com:8080/PV/SilverStream/Objectstore/General/
authentication.
Fri May 23 15:59:18 EDT 2008 WARNING Scheduler.Startup Process SCHD-3 W0100 :
Scheduler is not running. Need to configure the Email Host Server.
Fri May 23 15:59:18 EDT 2008 . Initialization DV CORBA_PORT_NUMBER = 45105
Fri May 23 15:59:26 EDT 2008 . persisting version information: type = DV,
relVersion = 4.0.0k, name = exteNd Application Server, buildVersion = 020918_1,
serverName = pmg01.usma.ibm.com, componentId = 8080
Fri May 23 15:59:27 EDT 2008 . persisting version information: type = DV,
relVersion = 4.4.3.0, name = DataView, buildVersion = FD4_2, serverName =
pmg01.usma.ibm.com, componentId = 8080
Fri May 23 15:59:39 EDT 2008 . CORBA NRT_432_ACTIVE = true

Uploading Style Sheets

It is not necessary to explicitly upload technology pack style sheets onto the secondary servers in a cluster.
When you install a Netcool/Proviso technology pack, the style sheets are automatically uploaded to the primary
server in the cluster. The database location where the style sheets are uploaded is shared by all the servers in the
cluster, so no additional uploads are required for the secondary DataView servers in the cluster.
Configuring the DataView Cluster

This section explains how to configure a Netcool/Proviso DataView server cluster. All the servers in a DataView
server cluster are connected to the same SilverMaster database.
For more information about server clusters, see the SilverStream documentation.
Adding Servers to a Cluster Configuration

Note: Ensure all servers in the cluster connect to the same SilverMaster database before you create the cluster.
To add servers to a cluster configuration:
1. On the system you designate as the Cache Manager, log in as the user who runs the server (typically pvuser).
2. Start the cache manager. For example:
cd /opt/silverstream/bin
./SilverCacheMgr &
3. Start all SilverStream servers included in the cluster. For example:
/etc/init.d/SilverStream start
4. Start the SilverStream Server Management Console (SMC) on the primary server. For example:
./smc
Note: Solaris Version 9 and higher includes a command also named smc. Be sure to use ./smc from
/opt/silverstream/bin, or you will inadvertently run the Solaris smc command.
The SilverStream Server Management Console (SMC) appears.

5. Click New on the SMC toolbar to start the cluster wizard. The New Cluster screen appears.
6. Enter a name for the cluster in the Cluster Name field.
You can assign the cluster any name you like, but do not use spaces.
7. Click Add to include a server in the cluster. The Add Server screen appears.
Note: Ensure the first server you add is the server chosen as the master server. All subsequent servers you add
must be configured to use the same SilverMaster.
8. Enter the server name and port number of the server to add. For example
cedar:8080
9. Click OK. The server name appears in the Servers list on the New Cluster screen.
10. Repeat Step 7 through Step 9 until you have added all servers you want included in the cluster.

11. Click Next. You are now prompted to configure the Cache Manager for the new cluster. See the following
section, Configuring the Cache Manager on page 206, for instructions.
Note: The Cache Manager must be running before any servers in a cluster start.
Configuring the Cache Manager

The Cache Manager registers each server as it starts and ensures the content cache on every server in the cluster
is synchronized.
In a clustered environment, multiple servers can simultaneously change the same data in the SilverStream system
tables. The Cache Manager listens for notifications of changes to the application. It ensures that servers in the
cluster are notified when another server invalidates cache objects. Servers then discard their invalid cache entries
and get an updated version of the resource the next time the object is needed.
Note: Before publishing changes to the cluster, confirm that the Cache Manager is running.
To configure the Cache Manager:
1. Enter the host name of the Cache Manager in the Host field of the New Cluster screen. For example:
cedar
2. Retain the default RMI port number 54891 for the Cache Manager. You can change the port number later
if necessary.
Note: Do not check the User SilverStream Load Manager components box.
3. Click Finish. The following message appears:
Please restart SilverCacheMgr before restarting your SilverStream

servers.
If using the SilverStream Load Manager, SilverLoadMgr and

SilverDispatcher must be restarted before starting your
SilverStream servers.
4. Click OK. The new cluster name appears in the SMC.

5. Restart the cluster servers, as described in Restarting Cluster Servers on page 206.
Restarting Cluster Servers

You must restart the servers included in the new cluster.
Note: Before you restart the cluster servers, you must restart SilverCacheMgr.
To restart cluster servers:
1. Click the server name.

2. Click Restart on the toolbar.
3. Click OK to acknowledge that you want to restart the specified server.
4. Verify the cluster configuration, as described in the following section.

Verifying Cluster Configuration

This section explains how to verify the cluster configuration, once you have configured the cluster and the Cache
Manager.
To verify cluster configuration:
1. Start the SilverStream Server Management Console.

2. Highlight the name of your cluster (for example, NOCCluster).
3. Click Configuration on the toolbar.
4. Click Servers. The cluster name appears with a list of servers it contains.
Deleting Servers from Cluster

You can delete servers from a cluster.
To delete servers from cluster:
1. Start the SilverStream Server Management Console.

2. Choose the cluster name.
3. Click the name of the server to select it.
4. Click Delete.
5. Click OK to confirm the deletion.
Multi-SilverMaster Database Installation

You can install multiple SilverMaster databases in a single Netcool/Proviso deployment. In a multi-
SilverMaster environment, DataView servers running on separate machines operate independently, each
with its own report tree.
In a multi-SilverMaster environment, one of the DataView servers is the primary server, and the others are
secondary servers. The Netcool/Proviso installer installs DataView and the SilverStream application server on
the primary server, as described in Add a DataView on page 106. The following sections describe the additional
steps you must perform to install and configure DataView and SilverStream on each secondary server in the
multi-SilverMaster environment.
Requirements
These instructions assume that you have already used the Netcool/Proviso installer to install DataMart and at
least one DataChannel in your Netcool/Proviso deployment, and one DataView (for the primary DataView
server), as described in Chapter 3, Installing Netcool/Proviso in a Distributed Environment. The instructions also
assume that you have installed one or more technology packs, as described in Chapter 5, Installing Technology Packs.

In addition, the following resources are required to install multi-SilverMaster databases:

• A separate Solaris system for each DataView server.
It is possible to install the DataView servers using the SilverMaster database on a single Solaris system. These
instructions assume that separate Solaris systems will be used.
• Disk space for new tablespaces.
The secondary DataView server requires two additional tablespaces with a total size of 150 MB.
• Oracle users for each of the tablespaces.
A separate Oracle user is created for each tablespace.
• Disk space for extending temporary tablespaces.
Each DataView server requires a temporary tablespace size of 150 MB. The default database installation
allocates a tablespace of 150 MB. That tablespace must be extended by 150 MB for the secondary DataView
installation.
Note: You must validate that there is enough disk space before starting the multi-SilverMaster installation.
Basic Installation Tasks

A multi-SilverMaster installation requires the following basic tasks:
1. Add new tablespaces and user accounts to the Oracle database, and extend the temporary tablespaces.
2. Install SilverStream on a secondary server.
3. Install DataView on a secondary server.
The following sections describe these tasks.
Updating the Oracle Database

The commands for adding the tablespaces and users to the Oracle database and for extending the temporary
tablespaces are packaged in an SQL script named InstallDBSupportForExtraDV.sql.
To update the Oracle database:
1. Log in as oracle.
2. Insert the Netcool/Proviso 4.4.3 installation CD-ROM.
3. Change to the DBSupportForExtraDV directory on the CD-ROM, as follows:
$ cd /cdrom/SOLARIS/DataBase/SOL9/extraTools/DBSupportForExtraDV
4. Run the script using the following format
$ sqlplus loginname/password@tnsname @InstallDBSupportForExtraDV.sql
For example:
sqlplus PV_ADMIN/PV@PV @InstallDBSupportForExtraDV.sql

You see a response like the following:

SQL*Plus: Release 9.2.0.6.0 - Production on Thu May 1 09:33:26 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning option
JServer Release 9.2.0.6.0 - Production
===========================================================
= =
= This script creates additional REPORTMASTER and =
= REPORT users for an additional DV installation. =
= =
===========================================================
Hit Enter to continue or Control C to exit
5. Press Enter.
6. Enter a report ID (for example, 1 for the first multi-SilverMaster installation, 2 for the next, and so on):
===========================================================
= =
= The current list of installed report ids =
= =
===========================================================
No additional report ids are installed
===========================================================
= =
= Enter the report id you wish to create =
= =
===========================================================
The report ID is used as a suffix for the following names:

• PV_REPORTMASTER — The Oracle user name for the SilverStream SilverMaster database.
• PV_REPORT — The Oracle user name for the DataView content database.
For example, if you enter 1 for the report ID, the names PV_REPORTMASTER1 and PV_REPORT1 are
created. You will need to enter these names later, when installing DataView.

7. Press Enter. You see a response like the following:

===========================================================
= =
= The current REPT and REPM tablespaces reside in the =
= following path(s) =
= =
===========================================================
File Path: /raid_3/oradata/PV/
===========================================================
= =
= Enter the path where you want the new tablespaces to =
= be created. Make sure you enter the full path. See =
= the original tablespace path above. If you wish to =
= use the same path, simply cut and paste the path from =
= above. Both the REPT and REPM tablespaces will be =
= created using this path. Make sure that there is at =
= least 300M free on this mount point. =
= =
===========================================================
8. Specify the location for the new tablespaces, then press Enter. You see a response like the following:
===========================================================
= =
= The current REPT and REPM tablespaces reside in the =
= following path(s) =
= =
===========================================================
File Path: /raid_3/oradata/PV/
===========================================================
= =
= Enter the path where you want the new tablespaces to =
= be created. Make sure you enter the full path. See =
= the original tablespace path above. If you wish to =
= use the same path, simply cut and paste the path from =
= above. Both the REPT and REPM tablespaces will be =
= created using this path. Make sure that there is at =
= least 300M free on this mount point. =
= =
===========================================================
/export/homeO/oradata/PV/
===========================================================
= =
= Two new users will be created. What passwords do you =
= wish these users to have? =
= =
===========================================================
9. Type the password for the new user accounts, then press Enter.
For security reasons, the password you type will not be displayed.
10. Retype the password to confirm it, then press Enter.
The database updates are now complete.
Note: If an error occurs while running the script, determine the cause of the error, run the remove script described
in Removing the Database Updates on page 220, and then rerun the install script with the correct information.

Installing SilverStream on a Secondary Server

For instructions, see SilverStream Installation on a Secondary Server on page 221.
Installing DataView on a Secondary Server

Install Netcool/Proviso DataView on the host on which you installed the SilverStream Application Server.
To install Netcool/Proviso DataView, you need:
• Access to the Sun server that will act as your DataView host.
• The Oracle TNS name of the server on which you installed Oracle server with Netcool/Proviso database
configuration.
• Oracle client software installed and running on your target SilverStream host, configured as described in Add
the SilverMaster TNS Service Name on page 222.
• Netcool/Proviso Database, DataMart, DataLoad, and technology packs installed and running on one or
more Sun servers in your network.
• A Netcool/Proviso distribution containing the supported version of SilverStream server for your
Netcool/Proviso installation.
• The current version of Netcool/Proviso software.
Assumptions
The DataView installation steps that follow have the default values and assumptions shown below:
Hostname of Oracle server delphi
Hostname for SilverStream and DataView athens
Oracle home directory (ORACLE_HOME=) /opt/oracle/product/n

For example:
/opt/oracle/product/9.2.0.6
Oracle login name for Netcool/Proviso administrator PV_ADMIN
Oracle SilverMaster user PV_REPORTMASTER1
DataView content database user PV_REPORT1
Oracle login password for the users PV_ADMIN, PV

PV_REPORTMASTER1, and PV_REPORT1
SilverStream admin user administrator
SilverStream admin password admin
For the complete list of DataView properties, see the Netcool/Proviso Properties Reference
settings. However, IBM strongly recommends using the default values the first time through a Netcool/Proviso
installation. For more information, see Specifying a Basename for DB_USER_ROOT on page 48.

Installation Overview
The DataView installation script presents a scrolling list of prompts. For each prompt, you accept the default
entry or enter a valid value, and the script builds its internal list of installation parameters. The script then installs
DataView and adds DataView-related entries to the Netcool/Proviso database.
When installation is complete, you see a message indicating a successful DataView installation. You can go to your
DataView server with a Web browser and see the initial unconfigured DataView portal page.
Re-Running the DataView Installation

If you stop and restart the DataView installation script or if you reinstall DataView, the installation script locates
the automatically saved installation log from the last run. The script then displays the values from the log in a
confirmation screen like the one shown in Step 7. on page 216.
The install script then prompts you, as follows:
Found this configuration in previous install file /var/tmp/PvInstall/dvinstall.cfg
(parameters not explicitly set in config file are set to defaults)
Do you want to use this saved configuration? (yes/no/quit) [yes]
Press Enter to use the saved configuration values.

In this case, all values you entered in the earlier installation are preserved as the script’s new defaults, except for
passwords. You must re-enter all passwords.
Steps to Install Netcool/Proviso DataView

Before proceeding, Make sure the SilverStream server is installed but shut down.
To shut down the SilverStream server, follow the instructions in Stop the SilverStream Server on page 232.
To start the DataView installation script and install DataView:
1. Log in as root.
3. Change to the following directory on the CD-ROM:
$ cd /cdrom/SOLARIS/DataView/SOLnum
For example:
$ cd /cdrom/SOLARIS/DataView/SOL9
4. Enter the following command to start the installation program:
# ./dvinstaller -action install_dv

The initial screen of the DataView installation program appears much like this example:
SilverStream/DataView Installer <version number>
logging to /var/tmp/PvInstall/2008.04.22-13.29.install.dv
Started DataView install at <Current Date>
/var/tmp/PvInstall/dvinstall.cfg
Looking for previous configuration file ...

/var/tmp/PvInstall/dvinstall.cfg not found, running interactively.
Note : To accept the default parameters in brackets, hit the "Enter" key.
To go back to the previous question, type "<" (without the quotes).
To go back to the first question, type "<<" (without the quotes).
Netcool/Proviso Unix parameters :

1. Enter the Unix user name for the Netcool/Proviso user [pvuser]:
5. Take note of the navigation instructions in the initial screen.

6. Respond to each prompt by pressing Enter to accept the default value, or by typing your own values to use
non-default entries.
Install Script Prompt Default Value Recommended Action
Netcool/Proviso Unix parameters:
Enter the Unix user name for the Netcool/Proviso user pvuser Accept the default.
Enter the Unix user group name for the Netcool/Proviso staff Accept the default.
user
Enter the Unix user name under which SilverStream pvuser Accept the default.
will run
Oracle parameters:
Enter the host name for the Oracle server The current server’s host Type the name of your
name Netcool/Proviso Oracle
server.
Enter the port used by Oracle for internal 1521 Accept the default.
communications
Enter the Oracle version 9 Accept the default for

Oracle 9.
Enter the directory where Oracle is installed /opt/oracle/ Accept the default for
product/9.2.0.6 Oracle 9.
Enter the Oracle login name for the Netcool/Proviso PV_ADMIN Accept the default.
administrator
Enter the Oracle login password for the Netcool/Proviso PV Accept the default.
administrator
Enter the Oracle TNS name for the SilverStream SILVERMASTER Accept the default.
SilverMaster database

Enter the Oracle login name for the SilverStream PV_REPORTMASTER Enter
SilverMaster database PV_REPORTMASTER
followed by the report
ID you specified in Step 6.
on page 209.
For example, if the report
ID is 1, enter
PV_REPORTMASTER1.
Enter the Oracle login password for the SilverStream PV Accept the default.
SilverMaster database
Enter the Oracle TNS name for the DataView content PV_SYSTEM Accept the default.
database
Enter the Oracle login name for the DataView content PV_REPORT Enter PV_REPORT
database followed by the report
ID you specified in Step 6.
on page 209.
For example, if the report
ID is 1, enter
PV_REPORT1.
Enter the Oracle login password for the DataView PV Accept the default.
content database
Enter the Oracle TNS name for the Netcool/Proviso PV Accept the default.
metric database
Enter the Oracle login name for the Netcool/Proviso PV_LOIS Accept the default.
metric database
Enter the Oracle login password for the Netcool/Proviso PV Accept the default.
metric database
SilverStream parameters:
Enter the directory where SilverStream will be installed /opt/silverstream Accept the default.
Note: After you provide a value or accept the default, the
following message appears:
Reading SilverStream configuration .... ok
Enter the SilverStream user name for the administration administrator Accept the default.
account
Enter the SilverStream user password for the admin Accept the default.
administration account
Install virtual framebuffer and auto-boot SilverStream? yes Accept the default.
Enter the SilverStream port number for the HTTP 8080 Accept the default (unless
service you installed SilverStream
to run on a different port).
Enter the SilverStream port number for the name service 54890 Accept the default.

DataView parameters:
Enter the directory where DataView will be installed /opt/dataview Accept the default.
Will this DataView server be under the control of an HA no Ignore — currently not
cluster agent? supported.
Enter the backup directory for DataView content /var/tmp/PvInstall/ Accept the default.
PVRbackup
Backup DataView content before installing? no If this is your first

DataView install, on this
server, there is nothing to
backup, so enter no.
If you are re-installing
DataView, enter yes.
Overwrite old DataView backup directory, if it exists? no This only applies if you
responded yes to the
previous prompt. Enter
no if you want to preserve
a previous installation’s
DataView backup.
Restore DataView content from backup directory after no If this is your first
installing? DataView install on this
server, enter no.
To restore previously
backed-up data, enter yes.
Overwrite old DataView installation, if it exists? yes Accept the default.

7. The install script shows the installation parameters you specified, like the following example.
Current Configuration:
Netcool/Proviso Unix parameters:
Netcool/Proviso Unix user = pvuser

Netcool/Proviso Unix group = staff
Unix user SilverStream runs as = pvuser
Oracle parameters:
Oracle host = DOCSERVER2

Oracle listener port = 1521
Version of Oracle = 9
Local Oracle home directory = /opt/oracle/product/9.2.0.6
Oracle login name for the Netcool/Proviso administrator = PV_ADMIN
Oracle login password for the Netcool/Proviso administrator = *****
Oracle TNS name for the SilverStream SilverMaster database = SILVERMASTER
Oracle login name for the SilverStream SilverMaster database = PV_REPORTMASTER1
Oracle login password for the SilverStream SilverMaster database = *****
Oracle TNS name for the DataView content database = PV_SYSTEM
Oracle login name for the DataView content database = PV_REPORT1
Oracle login password for the DataView content database = *****
Oracle TNS name for the Netcool/Proviso metric database = PV
Oracle login name for the Netcool/Proviso metric database = PV_LOIS
Oracle login password for the Netcool/Proviso metric database = *****
SilverStream parameters:
Home directory = /opt/silverstream

Administrator username = administrator
Administrator password = *****
Install autoboot/virtual framebuffer = yes
SilverStream port number for the HTTP service = 8080
DataView parameters:
Directory where DataView will be installed = /opt/dataview

Is the DataView server under the control of an HA cluster agent? = no
Dataview content backup directory = /var/tmp/PvInstall/PVRbackup
Backup Dataview content before making changes = no
Overwrite Dataview backup, if it exists = no
Restore backed up Dataview content after install = no
Overwrite Dataview install, if exists = yes
Do you want to use this configuration? (yes/no/quit) [yes] yes
8. Type yes at the prompt and press Enter.

The install script displays hundreds of status and information messages as the installation proceeds. The full
installation takes fifteen to thirty minutes, depending on the speed of your server.
The status messages start like this example:
Writing installation config to /var/tmp/PvInstall/dvinstall.cfg
PREINSTALL
Calculating the amount of disk space available for DataView .... ok
Calculating the amount of disk space needed ..... ok
Checking if there is enough disk space to install DataView .... ok
Calculating the amount of disk space available for Xvfb (virtual framebuffer) .... ok
Checking if there is enough disk space to install Xvfb .... ok
Checking the tnsnames.ora file ..... ok
...

9. At the end of the installation, the install messages contain a success message like the following example.
Setting optimization settings for Oracle 9 back to defaults ....... ok
Restarting SilverStream ...
Restarting SilverStream ...... ok
Uninstall data written to /var/tmp/PvInstall/dvuninstall.cfg.
DataView install is complete at <Current Date>
Installation log written to /var/tmp/PvInstall/dvinstall.log.yyyy.mm.dd.hh.ss

Exiting install.
The installation process automatically exits for both a successful and unsuccessful installation. A successful
installation is marked with the words “DataView install is complete,” as shown above.
If the installation is unsuccessful, start the install process again and correct any inaccurate values.
Test the DataView Installation

Now that DataView is installed and running, if you access the Web server on your DataView server, you see the
DataView server, not the basic SilverStream setup screen described in Step 5: on page 230.
Confirm that DataView is up and running by entering its Web address in any Web browser on your network.
These are the same steps as in Step 5: on page 230.
1. Use a Web address in the form:

http://hostname:8080
For example, enter:
http://athens:8080
2. You have not yet configured any DataView user names, so DataView first prompts with a reminder message
like the following:
No groups assigned to the user. Add groups to users via the User Editor.
3. Click OK to continue.
The URL http://athens:8080 is now automatically redirected to
http://athens:8080/PV/SilverStream/Pages/DVPortal3.html.
The initial, unconfigured DataView portal displays in the browser.
Confirming the Installation

To confirm that the secondary installation succeeded, use the SilverStream AgDBRegistry command to
determine what users DataView is using for storing system files and the SilverMaster files.
To run the command, cd to the bin directory of your SilverStream installation. The default location is:
/opt/silverstream/bin)
The following sections describe what to look for on both the primary DataView server and the secondary
DataView server to confirm that the installation was successful.

Primary DataView Server

After you run the AgDBRegistry command, the command’s output shows where the DataView system files
are stored and where the SilverMaster files are stored. This information is displayed in the User(Password)
column.
For the primary server, the DataView system files should be stored in PV_REPORT, and the SilverMaster files
should be stored in PV_REPORTMASTER. Note that your database names and user prefixes may differ depending
on your choices at the time you installed the database.
Here is an example of how to run the AgDBRegistry command, and a sample of the output:
$ ./AgDBRegistry -show
+ SilverStream Registry Databases Version: 4.0
Database User(Password)
------------------------------------------
pv33_system PV_REPORT(****)
pv33 PV_LOIS(****)
silvermaster pv_reportmaster(****)
Secondary DataView Server

The following example assumes that 1 has been entered as the report ID. The output for the secondary server
looks much like the output for the primary server, except that the report ID is appended to PV_REPORT and
PV_REPORTMASTER — in this example, PV_REPORT1 and PV_REPORTMASTER1
------------------------------------------
pv33 PV_LOIS(****)
pv33_system PV_REPORT1(****)
silvermaster PV_REPORTMASTER1(****)
An Incorrectly Configured Secondary DataView Server

If the system was installed improperly, you will see a combination of PV_<> and PV_<>1 user names, as shown
in the following example:
------------------------------------------
<default> PV_REPORTMASTER1(****)
pv33 PV_LOIS(****)
silvermaster PV_REPORTMASTER1(****)

To repair this situation:
1. Run the following commands:

1-a. ./AgDBRegistry -del pv33
1-b. ./AgDBRegistry -del pv33_system
2. Reinstall DataView using the latest version.
It is also possible that the SilverMaster DB is stored in PV_REPORTMASTER instead of PV_REPORTMASTER1, as
shown below:
------------------------------------------
<default> PV_REPORTMASTER(****)
pv33 PV_LOIS(****)
silvermaster PV_REPORTMASTER(****)
To repair this situation:
1. Use SilverMaster to initialize the new SilverMaster instance — for example, with the PV_REPORTMASTER1
tablespace:
./SilverMasterInit -U PV_REPORTMASTER1 -P PV_REPORT1 -f -A administrator -W admin
Note: Before executing the command, double-check that the correct tablespace is specified. Specifying the wrong
tablespace will wipe out the primary DataView server.
2. Reinstall DataView.
Uploading Style Sheets onto Secondary Servers

Because secondary DataView servers in a multi-SilverMaster environment operate independently of each other,
they cannot share a common set of technology pack style sheets, as clustered DataView servers can. You must
upload the style sheets onto each secondary DataView server in the multi-SilverMaster environment.
During the installation of a Netcool/Proviso technology pack, the style sheets for each pack are installed in
the $PVMHOME/APStyleSheets directory (/opt/datamart/APStyleSheets, by default) on the
DataMart server.
The style sheets must be copied to the SilverStream server and then imported into SilverStream.
To copy and import style sheets onto a secondary DataView server:
1. On the DataMart server, open a new xterm and log in to the SilverStream server using the appropriate UID
and password (pvuser and PV, by default).
2. Create a directory to hold the style sheets, by entering the following command:
mkdir -p /usr/tmp/APstyles
3. Using ftp, copy the style sheets from the $PVMHOME/APStyleSheets directory on the DataMart server
to the /usr/tmp/APstyles directory of the SilverStream server.
4. Change your working directory to the SilverStream SS_HOME/bin subdirectory, replacing SS_HOME with
the location of the SilverStream home directory (/opt/silverstream by default). For example:
cd SS_HOME/bin

5. Import the style sheets using the SilverCmd command with the following syntax:
./SilverCmd PublishFromFile DV_host:8080 Proviso_TNS temp-stylesheets-dir
-U SS_admin_name -P SS_admin_password
where:
— DV_host is your SilverStream-DataView server’s hostname. For example: athens
— Proviso_TNS is the TNS name of your Netcool/Proviso database. For example: PV.
— temp-stylesheets-dir is the full path to the directory where you copied the technology pack style sheets from
their installed location on the DataMart server.
— SS_admin_name is the SilverStream administration login name you specified when installing the
SilverStream server. For example: administrator.
— SS_admin_password is the password for the SS_admin_name. For example: admin.
The following command uses the example values described in the previous list:
./SilverCmd PublishFromFile athens:8080 PV /tmp/styles -U administrator -P admin
The command prints a series of upload messages, like the following, as it imports the style sheets:
Uploading /tmp/styles/APStyleSheets/stylesheetname.html.meta
The stylesheetname variable represents the name of the style sheet.
You should see messages similar to these when you execute the command. Upon completion, the command
writes Done to the console.
Removing the Database Updates

The RemoveDBSupportForExtraDV.sql script has been included with this distribution in case it is necessary
to remove the tablespaces and users. It does not shrink the temporary tablespace.
Combined Cluster and Multi-SilverMaster Configuration

You can set up a complex Netcool/Proviso deployment that includes both multi-SilverMaster servers and
DataView clusters. In such a deployment, any DataView server in the multi-SilverMaster environment can have
its own cluster.
You install and configure the secondary DataView servers as described in this appendix. When uploading
technology pack style sheets, keep in mind that the DataView servers in a cluster share the same style sheets, but
the multi-SilverMaster servers do not. You must upload style sheets onto each multi-SilverMaster server.

SilverStream Installation on a Secondary Server

This section describes how to install SilverStream on a secondary server. In most cases, the procedure is the same
for both clustered deployments and multi-SilverMaster deployments. The instructions will specify the few cases
where the procedure differs.
Install the SilverStream application server on the same host on which you will install the secondary
Netcool/Proviso DataView.
To install the SilverStream server, you need to:
• Install and configure an instance of Oracle client software on your SilverStream server and add a
SilverStream-specific entry to the tnsnames.ora file.
• Have access to the Sun server that will act as your DataView host.
• Know the Oracle TNS name of the server on which you installed the Oracle server with the Netcool/Proviso
database configuration.
• Install and have running on one or more Sun servers: Netcool/Proviso Database, DataMart, DataLoad,
and technology packs.
• Have access to a Netcool/Proviso 4.4.3 installation CD-ROM containing the supported version of
SilverStream server for your Netcool/Proviso installation.
When you complete the SilverStream installation steps, you see a message indicating a successful installation and
a successful start of the SilverStream server. You will be able to go to your SilverStream server with a Web
browser and view the initial setup page.
Assumptions
The SilverStream installation steps that follow have the default values and assumptions shown below:
Hostname of Oracle server delphi
Hostname for SilverStream and DataView athens
Oracle home directory (ORACLE_HOME=) /opt/oracle/product/n

For example:
Oracle login name for Netcool/Proviso administrator PV_ADMIN
Oracle SilverMaster user PV_REPORTMASTER
Oracle SilverMaster password (for PV_ADMIN and PV

PV_REPORTMASTER)
SilverStream admin user administrator
SilverStream admin password admin
SilverStream license string C6632800000001F3E22D05192006
For the complete list of SilverStream properties, see the DataView Properties chapter of theNetcool/Proviso
Properties Reference.

settings. However, IBM strongly recommends using the default values the first time through a Netcool/Proviso
installation. For more information, see Specifying a Basename for DB_USER_ROOT on page 48.
HTTP Port Number and SSL Considerations

The SilverStream server installs a Web server on the target system. By default, the SilverStream Web server runs
on TCP port 8080, and the Web server process runs as pvuser. IBM recommends you use these default settings.
If you want to use a TCP port below 1024 for the SilverStream Web server, including the standard Web server
port 80, then you must install and run both the SilverStream server and DataView as root. Doing so has security
implications for your DataView report access.
You must also install and run SilverStream as root if you will use SSL authentication for viewing DataView
reports.
If you decide to run SilverStream as root, you must also run the Netcool/Proviso DataView components as root.
Steps to Install SilverStream Server

The steps to install the SilverStream application server appear in the following table:
Step Page
Step 1,Install Oracle Client 222

Step 2,Pre-Installation Steps 225
Step 3,Create Installation Directory 226
Step 4,Run the SilverStream Install Script 226
Step 5,Test the SilverStream Server 230
Step 7,Stop the SilverStream Server 232
The SilverStream installation script presents a scrolling list of prompts. For each prompt, you accept the default
entry or enter a valid value, and the script builds its internal list of installation parameters. The script then installs
the SilverStream server and adds SilverStream-related entries to the Netcool/Proviso database.
Step 1: Install Oracle Client

Note: If you are installing SilverStream and Netcool/Proviso DataView on a different machine than the Oracle
server, you must install Oracle client software. Follow the instructions in Installing the Oracle Client (Patch
Version 9.2.0.6) on page 85 then return to this page.
Add the SilverMaster TNS Service Name

The following instructions use the directories for an Oracle 9i installation as examples.
Note: Always create a back-up of your existing tnsnames.ora file before making these edits.

To add TNS service names:
2. At a shell prompt, change to the $TNS_ADMIN directory. For example:
$ cd $TNS_ADMIN
or
$ cd /opt/oracle/product/9.2.0.6/network/admin
3. Edit the tnsnames.ora file using a text editor. For example:
$ vi tnsnames.ora
4. Add the following entries for SILVERMASTER.WORLD and PV_SYSTEM.WORLD to the bottom of the file.
Substitute the hostname of your Oracle server in the HOST= lines. For example, in the illustration below, the
Oracle hostname is delphi:
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
PV_SYSTEM.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
Notice that the new entries are identical to the PV.WORLD entry already in the file, except for the first line of
each new entry. For each new entry, you can copy and paste the PV.WORLD entry, and edit the first line of
each new entry to read SILVERMASTER.WORLD = or PV_SYSTEM.WORLD =, respectively.

5. After editing, your entire tnsnames.ora file for the SilverStream server’s Oracle client should look like this
example, except for the HOST= lines:
PV.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
PV_SYSTEM.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = delphi)
(PORT = 1521)
)
)
(CONNECT_DATA =
)
)
Test the SilverMaster TNS Service Name

To test the SilverMaster TNS service name configuration:
1. Make sure you are logged in as oracle.

tnsping silvermaster 10

The command responds with success messages like the following example:
TNS Ping Utility for Solaris: Version 9.2.0.6 - Production on <Current Date>
Copyright (c) 1997 Oracle Corporation. All rights reserved.
Used parameter files:

/opt/oracle/product/9.2.0.6/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST
= eng2) (PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = PV.WORLD) (INSTANCE_NAME =
PV)))
OK (10 msec)
OK (0 msec)
OK (10 msec)
OK (0 msec)
OK (0 msec)
OK (10 msec)
OK (0 msec)
OK (0 msec)
OK (10 msec)
OK (0 msec)
Step 2: Pre-Installation Steps

You must run the DVOptimizerToRule.sql script before installing SilverStream to ensure the best
performance during installation, when SilverStream analyzes the data structure of a database. This setting
performed by this script is unset by the DataView installation script.
3. Change to the following directory on the CD-ROM:
$ cd /cdrom/SOLARIS/DataView/SOL9/pvrscripts
4. Run the script using the following format
$ sqlplus loginname/password@tnsname @DVOptimizerToRule.sql
For example:
sqlplus PV_ADMIN/PV@PV @DVOptimizerToRule.sql

The script starts and runs to completion, showing output like the following example:
SQL*Plus: Release 9.2.0.6.0 - Production on <Current Date>
Connected to:
[ ... some screen text not shown ... ]
Updating optimizer mode for the LOIS client to RULE

-------------------------------------------------------------
Updating optimizer mode for the REPORT client to RULE
-------------------------------------------------------------
Updating optimizer mode for the REPORTMASTER client to RULE
-------------------------------------------------------------
Optimizer update successfully completed
-------------------------------------------------------------
SQL>
5. Enter exit at the SQL> prompt to return to the shell prompt.
Step 3: Create Installation Directory

If you install SilverStream as pvuser as recommended, the installation script cannot create the top-level installation
directory. Create the directory ahead of time.
1. Log in as root.
2. At a shell prompt, enter the following commands:
cd /opt
mkdir silverstream
chown pvuser:staff silverstream
chmod 775 silverstream
Step 4: Run the SilverStream Install Script

To install the SilverStream Application Server:
1. Log in as pvuser. (Recommended.)

You can also install and run SilverStream as root under certain circumstances, as described in HTTP Port
Number and SSL Considerations on page 222.
3. Change to the exteNd SilverStream installation directory on the CD-ROM:
$ cd /cdrom/exteNd40k
Note: If you set the Oracle environment variables by executing the .profile file (for example, ./opt/oracle/.profile),
the installation process automatically proposes the correct path.

4. Enter the following command to start the installation program:

./install.sh
A welcome screen displays, like the following example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Welcome to the SilverStream Server installation for Unix
Please read the Installation Notes in:

/cdrom/extend40k/Docs/relnotes.html
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Press return to view the license agreement:
5. The install script scrolls through several prompts. Respond to each prompt as shown in the following table.
Install Script Prompt Default Value IBM Recommends
Press return to view the license agreement: None Must press Enter to
continue.
Enter “y” to accept this license agreement y Must press Enter to accept
the default.
Please enter the directory where you would like to install /opt/silverstream Accept the default.
the SilverStream Server.
Install the SilverStream documentation files? no Does not matter for

DataView. Enter your
preference.
Install the SilverStream sample application files? no Enter y.
6. The install script next shows a menu of database types like the following example.
Please enter the Database type: [choose option # or shortcut answer in ()]
1. Informix Cloudscape (C,1)
2. Informix Online Dynamic Server (I,2)
3. -not used-
4. Microsoft SQL Server 2000 type 4 JDBC driver (M,4)
5. IBM DB2 UDB 5.2 (D,5)
6. IBM DB2 UDB 6.1/7.1 (B,6)
7. Oracle 7 (R,7)
8. Oracle 8 (O,8)
9. Oracle 9i (9)
10. -not used-
11. Sybase Adaptive Server Enterprise 11 (S,11)
12. Sybase Adaptive Server Enterprise 12 (Y,12)
13. Sybase Adaptive Server Anywhere 6 with jConnect 5.x (A6,13)
(q=quit, b=back, default='Oracle8') : 9
Enter 9 to select Oracle 9i.

7. The install script then scrolls through several more prompts. Respond to each prompt as shown in the
following table.
Please specify whether you would like to use 1 = Oracle Call Enter 1.
the Oracle Thin JDBC drive or the Oracle Call Interface
Interface (OCI). 2 = Oracle Thin JDBC
driver
Please enter the ORACLE_HOME directory /opt/app/oracle/ Enter the full path for your Oracle
product/8.0.6 home directory. For example:
Note: If you set the Oracle environment variables
by executing the .profile file (for example,
./opt/oracle/.profile), the installation process
automatically proposes the correct path.
Would you like to use Oracle synonym no Accept the default, no.
support?
Please enter the Oracle TNS name. none Enter SILVERMASTER.

This is the TNS name you set up in
Add the SilverMaster TNS Service
Name on page 222.
Please enter the name of your SilverMaster SilverMaster Accept the default.
database.
Please enter the Database access username. none Enter PV_REPORTMASTER.
Please enter the Database access password. none Enter PV.
Upgrade your existing SilverMaster? no Accept the default, no

for a first-time installation.
Should this installation Configure your yes • For a multi-SilverMaster

SilverStream Server (execute SilverMasterInit)? installation, accept the default
(yes) for a first-time installation.
If upgrading SilverStream,
specify no.
• For a cluster installation,
specify no.
Restrict access to the SilverStream server? yes Accept the default, yes.
The default response of yes to the last prompt means that unauthorized users cannot access administration
operations or browse directory listings, and means all users must log in when they access the server.
Installing the SilverStream server without restricting access means all users can perform administrative
operations and browse directory listings until you lock down access by setting permissions. IBM strongly
recommends restricting access.
Note: The prompts you see next may differ slightly from the prompts that appear on the following pages,
depending on responses you provided to the prompts in the table above.

8. The install script then scrolls through more prompts. Respond to each prompt as shown in the following
table.
Enter the user name for the SilverStream none Enter administrator.
administration account.
Enter the password for the SilverStream none Enter admin1.

administration account.
1. If you use a different password, do not use a reserved character such as space, $, !, @, # or %.
9. The install script next shows text describing the choice of Web server TCP port. If you are installing
SilverStream as pvuser, accept the default and recommended value, 8080.
See HTTP Port Number and SSL Considerations on page 222 for more information on other options.
10. The install script scrolls through two more prompts. Respond to each prompt as shown in the following
table.
Please enter the Name Service port number 54890 Accept the default, 54890.
Would you like to configure jBroker MQ at the yes Override the default and enter no.
end of this install?
11. The install script prompts:

Please enter the SilverStream License string.
Enter the following license string with no spaces:
C6632800000001F3E22D05192006
12. The install script goes through some initial setup, then shows a confirmation screen and prompts for
permission to install SilverStream:
+ setting up LD_LIBRARY_PATH ...
+ set : $JRE_HOME/lib/sparc
+ add : $ORACLE_HOME/lib
+ add : $SILVERSTREAMROOT/bin
+ add : $SILVERSTREAMROOT/fts/lib
-----------------------------------------------------------------------
Install Notes : /cdrom/extend40f/Docs/relnotes.html
SilverMaster Name: SilverMaster
DB Username : PV_REPORTMASTER
DB Password : PV
License string : XNNN NNNN NNNN NNNN NNXN MMDD YYYY
HTTP Port number : 8080
Oracle Db Alias : SilverMaster
ORACLE_HOME : /opt/oracle/product/9.2.0.6
LD_LIBRARY_PATH =
$JRE_HOME/lib/sparc:$ORACLE_HOME/lib:$SILVERSTREAMROOT/bin:$SILVERSTREAMROOT/fts/lib
Install the SilverStream Server

into '/opt/silverstream' now? (y/n/b=back) [y] : y

13. Enter y and press Enter to install the SilverStream server.

The installation process begins and shows hundreds of status messages scrolling down the screen. The
installation process takes ten to twenty minutes, depending on the speed of your server.
When the installation completes, the script prompts for permission to start the SilverStream server:
...
...
----------------------------------------------------------------------
SilverStream Server installation finished: /opt/silverstream
Start the SilverServer now ? (y/n) [y] : y
14. Enter y and press Enter to start the SilverStream server.

The startup process shows status and success messages like the following examples.
+ cd /opt/silverstream
+ /opt/silverstream/bin/SilverServer &
Please register your product at:

http://www.silverstream.com/productreg.html
$ Java Version: Sun Microsystems Inc. 1.3.1_03 (1.3.1_03-b03)

JVM Version: Sun Microsystems Inc. Java HotSpot(TM) Server VM interpreted mode
SilverStream Server loading properties from: /opt/silverstream/Resources/httpd.props
SilverStream Server using name service port 54890.
Starting the JBroker orb naming service on port 54890 on host athens
The naming service started successfully
FullText Indexer version: 4.0A9/7.0A9
SilverStream Server [Build Number:Release4.0.0 (020918_1)] serving at:
http://athens:8080 (runtime, design, admin)
Step 5: Test the SilverStream Server

The SilverStream server is now installed and running, but is not configured with any data. You can confirm that
the server is up and running by entering its Web address in any Web browser on your network.
1. Use a Web address in the form:

http://hostname:8080
For example, enter:
http://athens:8080
2. The SilverStream server prompts for the SilverStream administrator login name and password. Enter the
values you specified in Step 4: on page 226. For example:
administrator
admin
3. The unconfigured SilverStream server shows a simple Web page with the heading SilverMaster and three text
links, as in this example:
SilverMaster
robots.txt
SilverMaster
SilverStream

Step 6: Configure the SilverStream Server

Note: This step is required only for setting up a multi-SilverMaster environment. If you are setting up a cluster,
proceed to Step 7: on page 232.
After SilverStream is installed and running, you must define configuration settings required for proper
Netcool/Proviso DataView performance. You do so using the SilverStream Server Management Console (SMC).
Note: SilverStream provides a command line tool called SilverCmd that lets you perform functions without going
through the SMC. Refer to the SilverStream documentation for more information.
To access the SMC and configure SilverStream:
1. Log in with the same user name used when you installed SilverStream.
Note: If the SMC and Netcool/Proviso DataView are installed on the same system, you must start both
applications with the same user name.
2. Open a terminal emulator.

3. Change your working directory to the location where SMC is installed (/opt/silverstream/bin by
default). For example:
4. Open SMC by entering the following command:
./smc server:portNumber
For example:
./smc athens:8080
Note: If you have configured separate ports for different types of users and operations, you must specify your
administration port to start the SMC.
The SilverStream login prompt appears.

5. Enter your administrator login name and password.
The SilverStream Server Management Console window appears.
6. Click Configuration on the toolbar.
7. Click Connections to view client connection settings.
8. Make sure the following fields are set to the values shown below:
Field Value
Maximum number of client connections 250
Free client connections for “busy” 10
Free client connections for “light” 10
Idle client connections for “light” 250
9. Click Update.
10. Click Advanced.
11. Click Performance to view performance settings:

12. Set Number of pre-fetch buffers to 250.

13. Click Update.
14. Restart the SilverStream server in either of these ways:
— Click Restart on the toolbar.
— If you plan to install Netcool/Proviso DataView next, shut down the exteNd SilverStream server, as
described in Step 7: on page 232.
Additional SilverStream Configuration

The Netcool/Proviso DataView installation process sets the following additional configuration parameters:
• Maximum number of database connections: 20.
(The value appears in the Max Connections field of the SMC Database page.)
• Server will not reuse TCP connections.
(The value is represented by a cleared checkbox, named Keep Alive enabled - Server will reuse TCP
connections. The checkbox appears on the Performance tab of the SMC Advanced page.)
Step 7: Stop the SilverStream Server

If you proceed to the Netcool/Proviso DataView installation described in the next chapter, shut down the
SilverStream server before proceeding. The DataView installer will restart SilverStream as required.
1. Log in as pvuser on the host running the SilverStream server.

2. Change to the SilverStream installation’s bin directory. For example:
$ cd /opt/silverstream/bin
3. At the shell prompt, run a command with the following syntax:
./SilverCmd ServerState hostname:8080 shutdown -U adminlogin -P password
where:
— hostname is the name of the SilverStream host
— 8080 is the port on which the SilverStream server operates. If you used a different port number, enter
that number.
— adminlogin is the SilverStream administrative login you specified during installation.
— password is the SilverStream password for adminlogin
Using this manual’s defaults, the command to run would be:
./SilverCmd ServerState athens:8080 shutdown -U administrator -P admin
4. The system shows prompts like the following to verify that the server has been shut down.
http-server: Beginning server shutdown
http-server: closing all client connections; this might take some time ...
http-server: waiting for client connections to terminate.
http-server: all client connections closed.
http-server: done
+++++++++++$ /opt/silverstream/bin/SilverServer_ Terminated with code 0.


Appendix E: Deployer CLI Options
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:
The deployer.bin command accepts the following options:
Option Description
-Daction=clean Forces the deployer to remove all the

Netcool/Proviso components installed on the
machine where the command is run — not just
those components marked for deletion in the
Topology Editor.
Note: Use this option with caution, because forcing
the deletion of Netcool/Proviso components
outside of the scope and control of the Topology
Editor might cause some inconsistency in the
Netcool/Proviso installation. IBM recommends that
you uninstall components by first removing them
from the topology using the Topology Editor, then
running the uninstaller using the
-Daction=uninstall command.
-Daction=mib Used with -Daction=poc to complete a minimal

deployment installation on an AIX system.
-Daction=patch Performs a patch installation of Netcool/Proviso.

See Appendix G, Installing an Interim Fix for more
information.
-Daction=poc Performs a minimal deployment installation. See

Chapter 4, Installing Netcool/Proviso as a Minimal
Deployment for more information.
-Daction=resume Resumes an interrupted installation at the current

step. Note that this option is possible only when the
/tmp/ProvisoConsumer directory is available.
See Resuming a Partially Successful First-Time
Installation on page 40 for more information.
-Daction=uninstall Uninstalls all components marked “To Be

Removed” in the current topology file. See
Uninstalling Netcool/Proviso on page 172 for more
information.

Option Description
-DCheckUser Specifies whether the deployer checks to see if it is

running as root before performing install operations.
Possible values are true and false. For most
install scenarios, running the deployer as the
operating system root is required. You can use this
option to override root user checking. Default is
true.
-DOracleClient=oracle_client_home Enables you to specify the Oracle client home, so

the wizard screen that prompts you for that
information is skipped.
-DOracleServerHost=hostname Specifies the hostname or IP address where the

Oracle server resides.
-DOracleServerPort=port Specifies the communication port used by the

Oracle server. Default is 1521.
-DOracleSID=sid Specifies the Oracle server ID. Default is PV.
-DOracleAdminUser=admin_user Specifies the administrator username for the Oracle

server. Default is PV_INSTALL.
-DOracleAdminUser=admin_password Specifies the administrator password for the Oracle

server. Default is PV.
-DPrimary=true Indicates that the deployer is running on the primary

server. This option is used by the Topology Editor
to invoke the deployer. Use this option to force a
channel configuration update in the database.
-DTarget=id Instructs the deployer to install or uninstall the

component specified using the id parameter,
regardless of the current status of the component in
the topology.
Use this option to force an install or uninstall of a
component in a high-availability (HA) environment,
or when fixing an incomplete or damanged
installation.
Table 13 on page 236 contains a list of possible
values for the id parameter.
-DTopologyFile=topology_file_path Tells the deployer to use the specified topology file

instead of prompting for the file.
-DTrace=true Causes the deployer to log additional diagnostic

information.
-DUsehostname=hostname Enables you to override the hostname that the

deployer uses to define where it is running. This
option is useful when hostname aliasing is used and
none of the hostnames listed in the
topology.xml file match the hostname of the
machine where the deployer is running.
For detailed information about the deployer, see The Deployer on page 34.

Using the -DTarget Option

You can use the -DTarget option to force an install or uninstall of a component in a high-availability (HA)
environment, or when fixing an incomplete or damaged installation. 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, you must also specify the
-DAction=uninstall option when you run the deployer application. The following example shows how to
force the uninstallation of DataMart on the local system:
deployer.bin -DAction=uninstall -DTarget=DMR
Table 13 shows the possible values for the id parameter.
Table 13: Target Identifier Codes
Value Description
DB Instructs the deployer to install the database setup components on the local machine.
DM Instructs the deployer to install the DataMart component on the local machine.
DV Instructs the deployer to install the DataView component on the local machine.
DC Instructs the deployer to install the DataChannel component on the local machine.
DL Instructs the deployer to install the DataLoad component on the local machine.
DBR Instructs the deployer to remove the database setup components from the local machine.
Requires the -DAction=uninstall option.
DMR Instructs the deployer to remove the DataMart component from the local machine. Requires
the -DAction=uninstall option.
DVR Instructs the deployer to remove the DataView component from the local machine. Requires
DCR Instructs the deployer to remove the DataChannel component from the local machine.
Requires the -DAction=uninstall option.
DLR Instructs the deployer to remove the DataLoad component from the local machine. Requires
DBU Instructs the deployer to upgrade the database setup components on the local machine.
DMU Instructs the deployer to upgrade the DataMart component on the local machine.
DVU Instructs the deployer to upgrade the DataView component on the local machine.
DCU Instructs the deployer to upgrade the DataChannel component on the local machine.
DLU Instructs the deployer to upgrade the DataLoad component on the local machine.

When you run the deployer using the -DTarget option, note the following:
• The deployer does not perform component registration in the versioning tables of the database.
• The deployer does not upload modified topology information to the database.
• The deployer does not allow you to you select other nodes besides the local node in the Node Selection panel.
• In the case of an uninstall, the deployer does not remove the component from the topology.

Appendix F: Using Silent Mode
This appendix describes how to use silent mode to run the deployer or to install the Topology Editor. The topics
are as follows:
Topic Page
Sample Properties Files 238
The Deployer 238
The Topology Editor 241
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 the following sample properties files:
• Fresh.properties runs the deployer in standard mode.

• POC.properties runs the deployer in minimal deployment mode.
• topologyEditor.properties runs the Topology Editor installation in silent mode.
The Deployer
This section describes how to run the deployer in silent mode. The topics are as follows:
• Running the Deployer in Silent Mode on page 238
• Status Messages on page 240
• Restrictions on page 240
Running the Deployer in Silent Mode

Use the Fresh.properties file to run the deployer in standard mode, or the POC.properties file to run
the deployer in minimal deployment mode.
For example, to perform a silent fresh installation:
1. As root, log in to the machine on which you want to run the silent installation.
2. Set the DISPLAY environment variable (see Setting Up a Remote X Window Display on page 41).
3. In a text editor, open the Fresh.properties file and make the following edits:

3-a. Set and verify that the Oracle client path is correct.
3-b. Set the DownloadTopology flag to True (1) or False (0).
3-c. If you set DownloadTopology flag to False, set the TopologyFilePath to the location of your
topology.xml file.
3-d. If you are running the deployer application on the same system where the Topology Editor is installed,
set the Primary flag to true.
3-e. Set and verify that the Database Access Information is correct.
3-f. Set and verify the PACKAGE_PATH variable. An example path for Solaris would be:
Your edited file will look similar to the following:
#Oracle client JDBC driver path
#------------------------------
OracleClient=/opt/oracle/product/9.2.0.6.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=lab238053
OracleServerPort=1521
OracleSID=PV
OracleAdminUser=PV_INSTALL
OracleAdminPassword=PV
#Check Prerequisites Flag(true/false)

#Use true only for first time install
#-------------------------------------
CHECK_PREREQ=true
# Netcool/Proviso installation packages path

#---------------------------
PACKAGE_PATH=/cdrom/SOLARIS
#Silver Stream installation packages path

#-------------------------------------
SS_BUNDLE=/cdrom/exteNd40k
3-g. Write and quit the file.

4. Change to the /opt/IBM/proviso/deployer directory.


./deployer.bin –i silent –f propertyFileWithPath
For example:
./deployer.bin –i silent –f /opt/IBM/proviso/deployer/proviso/data/Silent/Fresh.properties
Status Messages
To verify a successful installation, look for a zero status code and the following message in the
/tmp/ProvisoConsumer/result.log file:
CMW3019I Silent installation completed.
If the installation fails, the log file will contain a non-zero code and the following messages:
CMW3018W An installation step has failed during silent installation.
CMW0007E Silent installation failed. Installer stopped.
If the installation fails:
1. As root, enter the following command:

./deployer.bin -Daction=resume
steps table).
2. Select the step that failed and view the output messages. See Step Status Values on page 39 for information
about debugging a failed step.
3. Correct the problem.
4. Continue the installation by following the instructions in Resuming a Partially Successful First-Time Installation on
page 40.
Restrictions
• The silent deployer does not support remote installations. You must manually invoke the script on each
machine.
• Silent resume is not supported. If you need to resume a partial silent installation, use the
-Daction=resume option to complete the installation using graphical mode (the steps table). The step that
originally failed might have been in the middle of a step sequence that cannot be re-created by a subsequent
-i silent invocation.

The Topology Editor

You can also install the Topology Editor in silent mode. The Topology Editor is installed with the installer named
installer.bin, located in the
root_dir/OS/Install/OS_ver/topologyEditor/Disk1/InstData/VM directory.
For example:
/export/home/pvuser/SOLARIS/Install/SOL9/topologyEditor/Disk1/
InstData/VM
To install the Topology Editor in silent mode:
1. As root, log in to the machine on which you want to run the silent installation.
2. Set the DISPLAY environment variable (see Setting Up a Remote X Window Display on page 41).
3. Change to the directory that contains the deployer.bin file (for example,
/opt/IBM/proviso/deployer), then change to the /proviso/data/Silent subdirectory.
4. Using a text editor, open the topologyEditor.properties file and make the following edits:
4-a. Set and verify that the Oracle client path is correct.
4-b. Set the DownloadTopology flag to True (1) or False (0).
4-c. If you set DownloadTopology flag to False, set the TopologyFilePath to the location of your
topology.xml file.
4-d. Set and verify that the Database Access Information is correct.
4-e. Set and verify the PACKAGE_PATH variable.
4-f. Write and quit the file.
./installer.bin -i silent -f ..../silent/topologyEditor.properties

Appendix G: Installing an Interim Fix
This appendix describes how to install an interim fix (or patch) release of Netcool/Proviso. The topics are as
follows:
Topic Page
Overview 242
Installing a Patch 243
Overview
Unlike major, minor, and maintenance releases, which are planned, patch releases (interim fixes and fix packs) are
unscheduled and are delivered under the following circumstances:
• A customer is experiencing a “blocking” problem and cannot wait for a scheduled release for the fix.
• The customer’s support contract specifies a timeframe for delivering a fix for a blocking problem and that
timeframe does not correspond with a scheduled release.
• 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 Rules
Note the following installation rules for patch installations:
• Fixes for the Database, DataMart, and DataView must be installed on that host.
• Fixes for the DataChannel and DataLoad can be installed remotely from the local host in a distributed
system.
• Fix packs are installed on general availability (GA) products.
• Sequentially numbered fix packs can be installed on any fix pack with a lower number.
• Interim fixes must be installed on the absolute fix pack.
The patch installer verifies that your installation conforms to these rules.

Behavior and Restrictions

It is important to note that when you apply a patch, the versioning information for the component is not updated.
For example, suppose your deployment has more than one DataMart installed — DM1 and DM2. The deployer
will compute the steps to patch both DataMart installations. However, because the deployer does not support
remote DataMart installations, the deployer grays out the remote DataMart host on the node selection page.
The general process is as follows:
1. Start the deployer on host DM1. You will be able to patch DM1, but not DM2 (DM2 will be grayed out).
2. Log in to DM2 and start the deployer in maintenance mode to patch DM2. Note that even though you
already patched DM1, it is still shown (but is grayed out) on the node selection page.
Before You Begin

A patch release updates the file system for the component that the patch is intended for and updates the
versioning information in the database.
To verify that the versioning was updated correctly for the components in the database, you can run several
queries both before and after the installation and compare the results. For detailed information, see the
Netcool/Proviso Technical Note: Tools for Version Reporting document.
Installing a Patch
To install a patch:
1. 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 instructions in the README for the fix pack release to obtain the maintenance package and
unzip the files.
Note that for each tar.gz file, you must unzip them, and then un-tar them. For example:
gunzip filename.tar.gz
tar -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 41).
4. Start the patch deployer using one of the following methods:
From the launchpad:
4-a. Click the Start Tivoli Netcool/Proviso 4.4.3 Maintenance Deployer option in the list of tasks.
4-b. Click the Start Tivoli Netcool/Proviso 4.4.3 Maintenance Deployer link.
— Run the following command:
# ./deployer.bin -Daction=patch

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 (for
example, 4.4.3.0-TIV-PROV-IF0002). Click Select to select that directory, then click Next to 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 the correct values:
• Database hostname — Enter the name of the database host.
• Port — Specifies the port number used for communication with the database. The default value is 1521.
• Database user — Specifies the username used to access the database. The default value is PV_INSTALL.
• Database Password — Enter the password for the database user account (for example, PV).
• 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 Netcool/Proviso component will be installed. Verify the settings,
then click Next to continue.
13. The deployer displays summary information about the installation. Review the information, then click Next.
The deployer displays the table of installation steps (see Installation Steps on page 37).
14. Run through each installation step just as you would for a normal installation.


Appendix H: Error Codes and Log Files
This appendix lists the Netcool/Proviso error messages and log files. The topics are as follows:
Topic Page
Error Codes 246
Log Files 262
See Appendix I, Troubleshooting for information about troubleshooting problems with the Netcool/Proviso
installation.
Error Codes
The following sections describe the error messages generated by:
• The deployer (page 246)
• The Topology Editor (page 257)
• InstallAnywhere (page 260)
Deployer Messages
Table 14 lists the error messages returned by the Netcool/Proviso deployer.
Table 14: Deployer Messages
Error Code Description User Action
DataView Messages
GYMCI5000E A system command failed. See the installation log for more details.
A standard UNIX system command failed. These
commands are used for standard system
operations, such as creating directories, changing
file permissions, and removing files.
GYMCI5001E This operating system is not supported for the Install SilverStream on a Sun Solaris system.
SilverStream installation. Only Sun Solaris is
supported.
GYMCI5002E The operating system is not at the prerequisite See the installation log for details. Install the
patch level. required patches, then try the installation
Some required operating system patches are not again.
installed.

GYMCI5003E The Oracle configuration file, tnsnames.ora, Add an entry for SilverMaster to the
does not include an entry for SilverMaster. tnsnames.ora file, then try the
installation again.
GYMCI5004E The Oracle configuration file, tnsnames.ora, Ensure that the file exists in the correct
was not found. location.
The tnsnames.ora file must be created and
stored in the $TNS_ADMIN directory.
GYMCI5005E Unable to connect to the Oracle database. See the installation log for more details.
It is possible that a specified connection parameter Ensure that the connection parameters you
is incorrect, or the Oracle server might not be are using are correct and that the Oracle
available. server is up and running.
GYMCI5006E An error occurred while running the See the installation log for more details. Check
DVOptimizerToRule.sql script to initialize that the database and listener are running.
the database.
It is possible that the Oracle database and listener
are not running.
GYMCI5007E An error occurred while trying to remove entries See the installation log for more details. Check
for a resource from a database table. that the database and listener are running.
are not running.
GYMCI5008E An error occurred while trying to remove version See the installation log for more details. Check
information from a database table. that the database and listener are running.
are not running.
GYMCI5009E An error occurred while reading the configuration Contact IBM Software Support.
file. The name of a parameter or the format of the
file is incorrect.
GYMCI5010E The file system does not have sufficient free space See the installation log for more details.
to complete the installation. Ensure that you have sufficient space on the
file system before retrying the installation.
GYMCI5011E The DataView license file is missing. Contact IBM Software Support.
The license file was not found, but this file should
not be required. The installation log will contain
more details of the error.
GYMCI5012E A configuration file or directory is missing. See the installation log for more details.
GYMCI5013E An error occurred while creating a configuration See the installation log for more details.
file. The file could not be created.
The installer failed to create one of the required
configuration files.
GYMCI5014E An error occurred while updating a configuration See the installation log for more details.
file. The file could not be modified.
The installer failed to make a required modification
to one of the configuration files.

GYMCI5015E The SilverStream server could not be started. See the installation log for more details.
The SilverServer executable does not exist in the
SilverStream bin directory or it cannot be run.
SilverStream Messages
GYMCI5020E An error occurred when connecting to the See the installation log for more details.
SilverStream server.
It is possible that the specified user name,
password, or port are not correct or that the
SilverStream server is not running.
GYMCI5021E An error occurred while configuring the See the installation log for details.
SilverStream server.
One of the commands that configures
SilverStream failed.
GYMCI5022E An error occurred while running a SilverStream See the installation log for details.
command.
One of the SilverStream commands that runs
during the installation of DataView and the
SilverStream server failed.
DataMart Messages
GYMCI5101E The DataMart installation failed. See the DataMart installer logs for details.
Database Configuration Messages
GYMCI5201E The database installation failed. See the installation See the
log for details. root_install_dir/database/install/log
/Oracle_SID/install.log file.
GYMCI5202E The database uninstallation script failed because of Check the syntax and run the script again.
a syntax error.
This script must be run as oracle. For example:
./uninstall_db
/var/tmp/PvInstall/
install.cfg.silent
GYMCI5204E The database could not be removed because some Check that all the required Oracle variables
Oracle environment variables are not correctly set. are set and try again.
Some or all of the Oracle environment variables
are not set (for example, ORACLE_HOME,
ORACLE_SID, or ORACLE_BASE).
GYMCI5205E An error occurred when trying to start the Oracle See the Oracle alert file for possible startup
database. errors. Resolve any problems reported in the
log and try again.
GYMCI5206E An error occurred when trying to shut down the See the Oracle alert file for possible shutdown
Oracle database. errors. Resolve any problems reported in the
log and try again.
GYMCI5207E An error occurred while querying the database to See the Oracle alert file for details of errors.
determine the data files that are owned by the You might need to manually delete Oracle
database. data files using operating system commands.

DataChannel Messages
GYMCI5301E The database channel installation failed. See the See the file
installation log for details. root_install_dir/channel/install/log/
Oracle_SID/install.log.
GYMCI5401E An error occurred while running a script. See the message produced with the error code
for more details.
GYMCI5402E Unable to find an expected file. See the message produced with the error code
for more details.
GYMCI5403E The data in one of the files is not valid. See the message produced with the error code
for more details.
GYMCI5404E Unable to find an expected file or expected data. See the message produced with the error code
for more details.
GYMCI5405E Scripts cannot function correctly because the Unset the variable and try again.
LD_ASSUME_KERNEL variable is set.
GYMCI5406E An action parameter is missing. See the message produced with the error code
for more details.
GYMCI5407E An error occurred while processing the tar See the message produced with the error code
command. for more details.
GYMCI5408E The product version you are trying to install seems See the message produced with the error code
to be for a different operating system. for more details.
GYMCI5409E Unable to locate installed package information for See the message produced with the error code
the operating system. for more details.
GYMCI5410E A file has an unexpected owner, group, or See the message produced with the error code
permissions. for more details.
GYMCI5411E A problem was found by the PvCheck module See the message produced with the error code
when checking the environment. for more details.
GYMCI5412E The installation module failed. See the messages in standard error for more
details.
GYMCI5413E The patch installation failed. See the messages in standard error for more
details.
GYMCI5414E The remove action failed. See the messages in standard error for more
details.
GYMCI5415E An unrecoverable error occurred while running the See the message produced with the error code
script. for more details.
Dataload Messages
GYMCI5501E An error occurred when running the script. See the message produced with the error code
for more details.
GYMCI5502E Unable to find an expected file. See the message produced with the error code
for more details.

GYMCI5503E The data in one of the files is not valid. See the message produced with the error code
for more details.
GYMCI5504E Unable to find an expected file or expected data. See the message produced with the error code
for more details.
GYMCI5505E Scripts cannot function correctly because the Unset the variable and try again.
LD_ASSUME_KERNEL variable is set.
GYMCI5506E An action parameter is missing. See the message produced with the error code
for more details.
GYMCI5507E An error occurred while processing the tar See the message produced with the error code
command. for more details.
GYMCI5508E The product version you are trying to install seems See the message produced with the error code
to be for a different operating system. for more details.
GYMCI5509E Unable to locate installed package information for See the message produced with the error code
the operating system. for more details.
GYMCI5510E A file has an unexpected owner, group or See the message produced with the error code
permissions. for more details.
GYMCI5511E A problem was found by the PvCheck module See the message produced with the error code
when checking the environment. for more details.
GYMCI5512E The installation module failed. See the message produced with the error code
for more details.
GYMCI5513E The patch installation failed. See the messages in standard error for more
details.
GYMCI5514E The remove action failed. See the messages in standard error for more
details.
GYMCI5515E An unrecoverable error occurred while running the See the message produced with the error code
script. for more details.
Prerequisite Checkers: Operating System
GYMCI6001E The syntax of the check_os script is not correct. Correct the syntax and try again.
The specified component does not exist.The
syntax is:
check_os PROVISO_COMPONENT
where PROVISO_COMPONENT is DL, DC,
DM, DB, or DV.
GYMCI6002E This version of IBM Tivoli Netcool/Proviso is not See the check_os.ini file for a list of
supported on the host operating system. supported operating systems.
GYMCI6003E The specified component does not exist or is not Ensure that you have specified the correct
supported on this operating system. component. If you have, the operating system
must be upgraded before the component can
be installed.

GYMCI6004E The operating system is not at the prerequisite Check the product documentation for a list of
patch level. required patches. Apply any missing patches
Some required operating system patches are not and try again.
installed.
GYMCI6005E The host operating system is not supported for this Perform the installation on a supported
installation. operating system.
GYMCI6006E In the /etc/security/limits file, some Check the values in the check_os.ini
values are missing or incorrect. Values must not be and edit the default stanza in the
lower than specified in the check_os.ini file. /etc/security/limits file so that
valid values are specified for all required
limits.
Prerequisite Checkers: Database
GYMCI6101E The syntax of the check_db script is not correct. Correct the syntax and try again.
The syntax is:
check_db [client - server] [new - upgrade]
[ORACLE_SID or tnsnames.ora entry]
GYMCI6102E The host operating system is not supported for this Perform the installation on a supported
installation. operating system.
GYMCI6103E This version of the IBM Tivoli Netcool/Proviso See the check_os.ini file for a list of
database is not supported on the current version of supported operating system versions.
the host operating system.
GYMCI6104E Some required Oracle variables are missing or Check the Oracle users environment files (for
undefined. example, .profile and .bash_profile).
GYMCI6105E An Oracle binary is missing or not valid. Ensure that Oracle is correctly installed.
GYMCI6106E The instance of Oracle installed on the host is not Check the list of supported Oracle versions in
at a supported version. the check_db.ini file.
GYMCI6107E Unable to contact the Oracle server using the Check that your Oracle listener is running on
tnsping utility with the specified ORACLE_SID. the database server. Start the listener if it is not
running.
GYMCI6108E An Oracle instance is running on the host where Check whether you have selected the correct
you have requested a new server installation. host for a new Oracle server installation. If the
selected host is correct, remove the existing
Oracle instance first.
GYMCI6109E The number of bits (32 or 64) for the Oracle binary Check the list of supported Oracle versions in
does not match the values defined in the the check_db.ini file.
check_db.ini file.
GYMCI6110E The installation method passed to the script is not Pass the New or Upgrade option to the script.
valid. Valid installation methods are New and
Upgrade.
GYMCI6111E The installation type passed to the script is not Pass the Client or Server option to the script.
valid. Valid installation methods are Client and
Server.

GYMCI6112E The script was run with options set for a new Check that a new server installation is the
server installation, but an Oracle instance correct action for this SID. If it is, remove the
configuration file (init.ora) already exists for existing Oracle instance configuration files.
the specified SID.
The presence of the init.ora file indicates the
presence of an Oracle instance.
GYMCI6113E A symbolic link was found in the Oracle home Remove any symbolic links. Specify the
path. Oracle home path using only real directories.
The Oracle home path cannot contain any
symbolic links.
GYMCI6114W Cannot contact the Oracle Listener. Check that the Oracle Listener is running.
The tnsping utility was run to check the Oracle Start it if necessary.
Listener status, but, the Listener could not be
contacted.
GYMCI6115E The Solaris semaphore and shared memory check Check that the required /etc/system
failed. parameters are set up for Oracle. Check that
The sysdef command was used to check the the values of these parameters meet the
values for semaphores and shared memory. The minimum values listed in the
command did not report the minimum value for a check_db.ini file.
particular semaphore or shared memory.
GYMCI6116E Could not find the bos.adt.lib package in the Ensure that the bos.adt.lib package is
COMMITTED state. The package might not be installed and committed and then try again.
installed.
The package is either not installed or not in a
COMMITTED state.
GYMCI6117E Could not log in to the database. Check that the database and Oracle Listener
The verify base option was used. The option are up and running. If not, start them.
attempts to log into the database to ensure it is
running. However, the script could not log in to
the database.
GYMCI6118E The checkextc script failed. Check that the Netcool/Proviso database was
The verify base option was used. The option runs created properly.
the checkextc script to ensure external procedure
calls can be performed.
GYMCI6119E The tnsnames.ora file is missing. Check that the tnsnames.ora file exists
A tnsnames.ora file in should exist in in the
ORACLE_HOME/network/admin ORACLE_HOME/network/admin
directory. directory. If it does not, create it.
Minimal Deployment: Post-Installation Messages
GYMCI7500E An internal processing error occurred in the script. Check the logs and the output from the script.
Look for incorrect configuration or improper
invocation.
GYMCI7501E The required configuration or messages files for Check for errors that occurred during the
the poc-post-install script are not in the installation steps.
same directory as the script.
These files should be unpacked by the installer
together with the script.

GYMCI7502E An environment file is missing or is in the wrong Check the poc-post-install

location. configuration file. The missing environment
file and expected path will be identified in the
log file.
GYMCI7503E The SNMP DataLoad did not start. Check the SNMP DataLoad log for errors
The SNMP DataLoad process (pvmd) failed to during startup.
start.
GYMCI7504E The network inventory failed. New devices cannot Check the inventory log for errors. Ensure the
be discovered unless the inventory runs DISC server and SNMP DataLoad (Collector)
successfully. processes are running.
GYMCI7505E The Report Grouping operation failed. Check the inventory log file for more details
This action does not depend on any external of the Report Grouping failure.
application processes. The database must be
running, and correct DataMart grouping rule
definitions are required.
GYMCI7506E The DataChannel command line failed. Ensure that the required processes are
It is possible that the CNS, CMGR, and AMGR running. Check the proviso.log for
processes are not running. details of the failure.
GYMCI7507E The Report User was not created. The Web user Ensure that the database is running, and check
will not be able to view reports. for error logs in the DataMart logs directory.
The DataMart resmgr utility is used to add this
configuration to the database. It is possible that the
database is not running.
GYMCI7508E Failed to associate a Report User to a group. Ensure that the database is running, and check
The report user is associated with a group to allow for error logs in the DataMart logs directory.
the user to view reports. The DataMart resmgr Ensure that the specified report group exists.
utility is used to add this configuration to the
database. It is possible that the database is not
running.
GYMCI7509E A report user could not be deleted from the Check for error and trace logs in the DataMart
database. logs directory.
GYMCI7510E Failed to create a Web User. Check the Web/application server log file for
The user will not be able to authenticate with the errors. Ensure that the Web/application
Web/application server. server is running.
GYMCI7511E The Web group could not be created, and the Web Check the Web/application server log file for
user might not be properly configured to view errors. Ensure that the Web/application
reports. server is running.
GYMCI7512E Failed to associate the Web User with a group. Check the Web/application server log file for
The Web user might not be properly configured to errors. Ensure that the Web/application
view reports unless successfully associated with a server is running. This step relies on the
group. database component only.
GYMCI7513E Failed to delete Web Users. Check the Web/application server logs.
Web user authentication was not removed.
GYMCI7514E The Channel Naming Service failed to start. Cross- Check for walkback or error files in the
application communication cannot function. DataChannel log or state directory.

GYMCI7515E The central LOG server failed to start. Logging for Check for walkback or error files in the
DataChannel will be unavailable. DataChannel log or state directory.
GYMCI7516E The Channel Manager failed to start. DataChannel Check the proviso.log file for errors.
applications cannot be started or stopped. Check for walkback or error files in the
Application status will be unavailable. DataChannel log or state directory.
GYMCI7517E The Application Manager failed to start. Check the proviso.log file for errors.
DataChannel applications cannot be started or Check for walkback or error files in the
stopped. Application status will be unavailable. DataChannel log or state directory.
GYMCI7518E Failed to create the DV user group. Check the poc-post-install log in
The DV user will remain in the Orphans group. /var/tmp for more details on the error
condition.
GYMCI7519E Failed to associate the DV user to the DV group. Check the poc-post-install log in
The DV user will remain in the Orphans group. /var/tmp for more details on the error
condition.
GYMCI7520E The Web Application server is not running or took Start up the Web Application server as
too long to start up. documented.
GYMCI7597E The MIB-II Technology Pack jar file was not Add the MIB2 Technology Pack jar to the
found in the specified directory. directory. Remove other jar files and try again.
GYMCI7598E Too many jar files are present in the specified Remove the other jar files and try again.
directory.
Only two jar file can be present in the directory:
the ProvisoPackInstaller.jar and the MIB-II
Technology Pack jar.
GYMCI7599E The Technology Pack installer failed. Check the

Technology Pack installer logs for details.
Installer Action Messages and IA Flow Messages
GYMCI9998E Unable to find a message for the key. See the installation log for more details.
The message was not retrieved from the message
catalog.
GYMCI9999E An unknown error occurred for the component See the installation log for more details.
name with the error code code. The message could
not be retrieved from the catalog.
GYMCI9001E An error occurred during installation. See the installation log for more details.
An exception has been generated during an
installation step.
GYMCI9002E An unrecoverable error occurred when running the See the installation log for more details.
command command.
GYMCI9003E An unrecoverable error occurred while running a See the installation log for more details.
command.
GYMCI9004E An error occurred while connecting to the See the installation log for more details.
database.
GYMCI9005E An error occurred while performing a database See the installation log for more details.
operation.

GYMCI9006E Remote File Transfer has been disabled. To continue, change the step property to
Allow Remote Execution and run the step
again, or manually transfer the directory to the
host. When the transfer is completed, change
the step status to Success and continue the
installation.
GYMCI9007E An error occurred while remotely connecting to See the installation log for more details.
target.
There are connection problems with the host.
GYMCI9008E An error occurred while connecting to target. See the installation log for more details.
There are connection problems with the host.
GYMCI9009E An error occurred while copying install_dir. See the installation log for more details.
GYMCI9010E Remote Command Execution has been disabled. To continue:

1. Change the step property to Set Allow
Remote Execution.
2. Run the step again.
Or, manually transfer the directory to the
host.
When the transfer is completed, change the
step status to Success and continue the
installation.
GYMCI9011E An error occurred during file creation. See the installation log for more details.
GYMCI9012E An error occurred while loading the discovered See the installation log for more details.
topology file.
GYMCI9013E An error occurred while loading the topology file. See the installation log for more details.
GYMCI9014E The installation engine encountered an See the installation log for more details.
unrecoverable error.
GYMCI9015E An error occurred while saving the topology file. See the installation log for more details.
GYMCI9016E The installer cannot proceed with the installation See the installation log for more details.
because there is insufficient disk space on the local
host.
GYMCI9017E The installer cannot download the topology from Ensure that the correct host name, port, and
the specified database. Verify that the SID were specified and that the database has
Netcool/Proviso database exists and that it has been started.
been started.
If it does not exist, launch the installer, providing a
topology file.
GYMCI9018E The installer cannot connect to the specified Ensure that you provide the correct user name
database indicated because of incorrect credentials. and password.
GYMCI9019W The installer could not establish a connection to Check that the Netcool/Proviso database can
the specified database. Check that the be contacted.
Netcool/Proviso database can be contacted.
Click Next to proceed without checking the
current environment status.

GYMCI9020E The database connection parameters do not match Ensure that you provide the correct
those in the topology file. parameters.
GYMCI9021E An error occurred while loading the Oracle client See the installation log for more details.
jar.
GYMCI9022E The configuration file name was not found. The See the installation log for more details.
step cannot run.
GYMCI9023W There appear to be no differences between the See the installation log for more details.
desired topology state and the current state of the
Netcool/Proviso installation.
The installer shows this message when it
determines there is not work that it can do.
Normally, this occurs when the Netcool/Proviso
system is already at the desired state. However, it
can also occur when there are component
dependencies that are not satisfied.
GYMCI9024E The operating system specified for this node in the Correct the topology file.
topology file is not correct.
GYMCI9025E The path is not valid or you do not have Correct the parameter and try again.
permissions to write to it.
GYMCI9026E The path is not a valid Oracle path. The sqlplus Correct the parameter and try again.
command could not be found.
GYMCI9027E The specified port is not valid. Correct the parameter and try again.
GYMCI9028E At least one parameter is null. Specify values for the required parameters.
GYMCI9029E The specified host name contains unsupported Ensure that host names include only
characters. supported characters.
GYMCI9030E The specified host cannot be contacted. Ensure that the host name is correct and
check that the host is available.
GYMCI9031E The path not exists on the local system. Correct the path and try again.
GYMCI9032E An error occurred while saving the topology. It has See the log file for further details.
not been uploaded to the Netcool/Proviso
database.
This error occurs when there is a database
connection error or when the Netcool/Proviso
database has not yet been created
GYMCI9033E One of the following parameters must be set to 1: Check the log file for further details. Redefine
param1 param2 the parameters and try again.
GYMCI9034E An error occurred while creating mount point See the log file for further details.
directories.
GYMCI9035E An error occurred while changing the ownership See the log file for further details.
or the group of mount point directories.

GYMCI9036E The machine hostname was not found in the If a host name alias is used, make the machine
Netcool/Proviso model (topology.xml file). host name match the host name in the model.
The machine where the installer is running is not Alternatively, use the option
part of the Netcool/Proviso topology. -DUsehostname=hostname to override the
machine host name used by the installer.
GYMCI9037E The Deployer version you are using is not Use a Deployer at a version that supports the
compatible with the component that you are trying deployment of the component you are trying
to install. to install.
GYMCI9038E The XML file cannot be read or cannot be parsed. Ensure the file is not corrupted. See the log
file for more details.
GYMCI9039E The deployment cannot proceed, because an error See the log file for more details. Check that
occurred the deployment plan was being there is sufficient disk space and that the
generated. Deployer images are not corrupted.
GYMCI9040E The Deployer cannot manage the indicated See the log file for more details about the
component on the specified node. condition that was detected.
GYMCI9041E The user ID you specified is not defined on the Check that you have specified the correct user
target system. ID.
GYMCI9042E You specified a host that is running on an Check that you have specified the correct host
unsupported platform. name.
GYMCI9043E The value you specified is not supported. Specify one of the supported values.
Topology Editor Messages

Table 15 lists the error messages returned by the Topology Editor.
Table 15: Topology Editor Messages
GYM0001E A connection error was caused by an SQL failure Check the error log and trace files for the
when running the report. Details are logged in the possible cause of the problem. Check that the
trace file. database is up and that the connection
There is a connection problem with the database. credentials are correct. Correct the problem
Possible problems include: and try the operation again.
The database is not running.
The database password provided when the engine
was created is wrong or has been changed.
GYMCI0000E Folder name containing technology pack metadata Ensure that you have the correct location for
files was not found. the technology pack metadata files and try the
The specified folder does not exist. operation again.
GYMCI0001E An internal error, associated with the XML parser Contact IBM Software Support.
configuration, occurred.
GYMCI0002I No item has been found that satisfies the filtering Ensure that you enter the correct filtering
criteria. criteria and try the operation again.

GYMCI0003E An error occurred when reading XML file name. Ensure that you have selected the correct file
The XML file might be corrupt or in an incorrect and try the operation again.
format.
GYMCI0004E The input value must be an integer. Correct the input value and try the operation
again.
GYMCI0005E An unexpected element was found when reading Ensure that you have selected the correct file
the XML file. and try the operation again.
GYMCI0006E A value must be specified. Correct the input value and retry the
operation.
GYMCI0007E The value must represent a log filter matching Correct the input value and try the operation
regular expression expression. again.
GYMCI0008E Metadata file name was not found. Ensure that you have the correct file name
The specified file does not exist. and path and retry the operation.
GYMCI0009E Metadata file name is corrupted. Contact IBM Software Support.
GYMCI0010E Metadata file name was already imported. Do you Click Yes to replace the file or No to cancel
want to replace it? the operation.
GYMCI0011E Object name was not found in the repository. Ensure that you have the correct object name
The specified object does not exist. and try the operation again.
GYMCI0012E The specified value must identify an existing Ensure that you have the correct directory
directory. name and try the operation again.
The specified directory does not exist.
GYMCI0013E Removing object from host in Physical View. No user action required.
GYMCI0014E File name does not exist. Ensure that you have the correct file name
and try the operation again.
GYMCI0015E An unexpected error occurred writing file name. See Ensure that there is sufficient space to write
the trace file for details. the file in the file system where the Topology
Editor is running.
GYMCI0016E The user or password that you specified is wrong. Correct the login credentials and try the
operation again.
GYMCI0017E The value specified for at least one of the following Correct the input value or values and try the
fields is not valid: host name, port, or SID. operation again.
GYMCI0018E The file name is corrupted. Select a valid XML file.
GYMCI0019E An unexpected error occurred when retrieving data Ensure that the database is up and running
from the database. See the trace file for details. and that you can connect to it.
GYMCI0020E An unexpected error occurred when parsing file Select a valid XML file.
name. See the trace file for details.
GYMCI0021E An unexpected error occurred. See the trace file Contact IBM Software Support.
for details.
GYMCI0022E The input value must be a boolean. Correct the input value and try the operation
again.

GYMCI0023E The specified value must be one of the following Correct the input value and try the operation
operating systems: AIX, SOLARIS, or Linux. again.
GYMCI0024E The value must be a software version number in Correct the input value and try the operation
the format n.n.n or n.n.n.n. For example 7.1.2, or again.
7.1.2.1.
GYMCI0025E The value must be an integer in the range minValue Correct the input value and try the operation
to maxValue, inclusive. again.
GYMCI0026E The value must be a comma-separated list of Correct the input value and try the operation
strings. again.
GYMCI0027E The value must be a file size expressed in kilobytes. Correct the input value and try the operation
For example, 1024K. again.
GYMCI0028E The value must be a file size expressed in Correct the input value and try the operation
megabytes. For example, 512M. again.
GYMCI0029E The value must be a file size expressed in kilobytes Correct the input value and try the operation
or megabytes. For example 1024K or 512M. again.
GYMCI0030E The value must be an FTP or SFTP connection Correct the input value and try the operation
string. For example, again.
ftp://username:password@hostname
/directory.
GYMCI0031E The value must be a comma-separated list of Correct the input value and try the operation
directories. For example, /opt, /var/tmp, again.
/home.
GYMCI0032E Value cannot be a fully-qualified domain name, IP Supply the unqualified host name without the
address, or name containing hyphen or period. domain. Do not use the IP address or a name
that contains hyphens.
GYMCI0033E Metadata file name contains an technology pack Contact IBM Software Support.
with a wrong structure.
GYMCI0034E Value should be in the format YYYY-MM-DD, Specify a date that is within the range and in
cannot be a date prior than 1970-01-01, or later the correct format.
than the current date.
GYMCI0035E The meta-data file contains an technology pack Obtain a valid meta-data file and try again.
with the wrong structure.
GYMCI0036E Value should be in the format YYYY-MM-DD, Correct the input value and retry the
cannot be a date prior than 1970-01-01, or later operation.
than the current date.
GYMCI0037E The operation failed because the specified file does Ensure that the file name and path you
not exist. specified is correct and retry the operation.
GYMCI0038E The operation failed because of an error while See the trace file for more details.
validating the host name mappings file.
GYMCI0039E The host name retrieved by the upgrade process is Correct the entry for the specified host name
not valid. Fully qualified host names, IP addresses in the topology definition.
and names containing hyphens or periods are not
supported.

GYMCI0040E The upgrade process retrieved two entries for the Remove the entry for the fully qualified host
specified host name. The fully qualified host name name.
is not supported.
GYMCI0040W The upgrade process did not retrieve a valid value Check that the default assigned is appropriate
for the specified property. A default value has been and change it if necessary.
used.
GYMCI0041E No component is present on the specified host. Specify a host where at least one component
is present.
GYMCI0042E The operation failed because the input value is not Correct the input value and retry the
the correct data type. The correct data type is operation.
Long.
GYMCI0043E The operation failed because the input value is not Correct the input value and retry the
valid. operation.
GYMCI0044W The upgrade process did not retrieve a valid value Check that the default assigned is appropriate
for the specified property. A default value has been and change it if necessary.
used.
InstallAnywhere Messages
Table 15 lists the InstallAnywhere™ error messages. These messages could be returned by either the deployer or
the Topology Editor. See the InstallAnywhere documentation for more information about these error codes and
how to resolve them.
Table 16: Install Anywhere Messages
Error Code Description
0 Success: The installation completed successfully without any warnings or errors.
1 The installation completed successfully, but one or more of the actions from the installation
sequence caused a warning or a non-fatal error.
8 The silent installation failed because of step Errord errors.
–1 One or more of the actions from the installation sequence caused a fatal error.
1000 The installation was cancelled by the user.
1001 The installation includes an invalid command-line option.
2000 Unhandled error.
2001 The installation failed the authorization check, may indicate an expired version.
2002 The installation failed a rules check. A rule placed on the installer itself failed.
2003 An unresolved dependency in silent mode caused the installer to exit.
2004 The installation failed because not enough disk space was detected during the execution of the
Install action.

Table 16: Install Anywhere Messages
Error Code Description
2005 The installation failed while trying to install on a Windows 64-bit system, but installation did not
include support for Windows 64-bit systems.
2006 The installation failed because it was launched in a UI mode that is not supported by this installer.
3000 Unhandled error specific to a launcher.
3001 The installation failed due to an error specific to the lax.main.class property.
3002 The installation failed due to an error specific to the lax.main.method property.
3003 The installation was unable to access the method specified in the lax.main.method property.
3004 The installation failed due to an exception error caused by the lax.main.method property.
3005 The installation failed because no value was assigned to the lax.application.name property.
3006 The installation was unable to access the value assigned to the
lax.nl.java.launcher.main.class property.
3007 The installation failed due to an error specific to the lax.nl.java.launcher.main.class

property.
3008 The installation failed due to an error specific to the

lax.nl.java.launcher.main.method property.
3009 The installation was unable to access the method specified in the
lax.nl.launcher.java.main.method property.
4000 A Java executable could not be found at the directory specified by the java.home system
property.
4001 An incorrect path to the installer jar caused the relauncher to launch incorrectly.

Log Files
Several files are used to log errors for the Netcool/Proviso components and its underlying framework. These log
files include:
• COI Log Files
• Deployer Log File
• Eclipse Log File
• Trace Log File
See Chapter 5, Installing Technology Packs for information about the technology pack log files.
COI Log Files

The Composite Offering Installer (COI) adds a layer called the COI Plan to the Netcool/Proviso installation. The
COI Plan consists of a set of COI Machine Plans, one for each machine where Netcool/Proviso components
should be installed. A COI Machine Plan is a collection of COI Steps to be run on the corresponding machine.
(See Installation Steps on page 37 for a description of the steps used in the Netcool/Proviso installation.)
The COI Plan is created in the directory /tmp/ProvisoConsumer/Plan.
The COI provides the following log files:
Table 17: COI Log Files
Log File Description Log File Location
MachinePlan_machinename_ Contains detailed /tmp/ProvisoConsumer/Plan/

[INSTALL_mmdd_hh.mm].log information about the tasks MachinePlan_machinename/logs/
executed by the COI steps on
For example:
the specified machine
MachinePlan_delphi_[INSTALL
_0610_10.37].log
DeploymentPlan.log Contains high-level tmp/ProvisoConsumer/Plan/

information about the COI logs/INSTALL_mmdd_hh.mm
Plan execution
Deployer Log File

Installation errors and messages are written to the file /tmp/ProvisoConsumer/log.txt. The log file
supports two levels:
• Low (INFO) — This is the default setting.
• High (FINEST)
To change the log level to high:
• Run the deployer with the -DTrace option set to true. For example:
# ./deployer.bin -DTrace=true

Eclipse Log File

The Eclipse framework logs severe problems in a file under the Topology Editor installation directory (for
example, /opt/IBM/Proviso/topologyEditor/workspace/.metadata). By default, the Eclipse log file
is named .log. You should not need to look there unless there is a problem with the underlying Eclipse
framework.
Trace Log File

The trace log file is located in the Topology Editor installation directory (for example,
/opt/IBM/Proviso/topologyEditor). By default, this file is named topologyEditorTrace and the
default trace level is FINE.
To change the trace level:
1. In the Topology Editor, select Window > Preferences. The Log Preferences window opens.
2. Select the new trace level. If desired, change the name of the log file.
3. Click Apply to apply your changes. To revert back to the default values, click Restore Defaults.
4. Click OK to close the window.

Appendix I: Troubleshooting
This appendix lists problems that might occur during an installation and how to resolve them. The problems are
grouped by the interface or component exhibiting the problem. The topics are as follows:
Topic Page
Deployment Problems 264
Netcool/Proviso Component Problems 268
Topology Editor Problems 269
Telnet Problems 270
Java Problems 270
Testing Connectivity to the Database 270
Testing External Procedure Call Access 271
See also Appendix H, Error Codes and Log Files.
Deployment Problems
Problem Solution
The deployer window does not Cause:

automatically become the focus In some cases (for example, when you export the display on a VNC
window after launching from it from session on Linux systems), the deployer window does not get the
the Topology Editor. focus.
User action:
Click on the deployer window or move other windows to make the
deployer window the focus window.
In a fresh installation, the database Cause:

installation step fails. You did not perform the necessary preparatory steps.
User action:
This step verifies that the Oracle Listener is working properly before
actually creating the Netcool/Proviso database.
If the step fails:
1. Complete the necessary manual steps (see Configure the Oracle
Listener on page 69).
2. Change the status of the step to Ready.
3. Resume the installation. The step should complete successfully.

Problem Solution
An installation step hangs. Cause:

There are many possible causes.
User action:
1. Make sure the installation step is really in a hung state. For
example, the Netcool/Proviso database-related steps might take
more than an hour to complete; other steps complete in far less
time.
2. Determine which child process is causing the hang. First, find the
installer 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 -
Next, find the process that has that process number (for example,
12899) as its father. Continue until you find the last process.
4. Kill the last process using the following command:
kill -9
At this point, the status of the hung step will change to Error.
5. If you can determine the cause of the hang, fix the problem and
resume the installation. Otherwise, collect the log files and contact
IBM for support.
The deployer hangs when displaying Cause:

the Preview page. (This step normally The NFS file system is not working properly.
takes only a few seconds). User action:
Run the df -k command and make sure that all NFS mounted file
systems are working properly. When the problem has been corrected,
restart the deployer.
There is a problem with remote Cause:

command execution. The deployer uses either RSH or OpenSSH to perform remote
command execution. You must configure OpenSSH to make this
connection possible.
User action:
After configuring OpenSSH, run the test program provided in
deployer_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
You specified a remote installation of Cause:

DataView (or DataMart) even The remote host is marked as unavailable because remote installation
through it is not supported, making of DataView (or DataMart) is not supported.
the remote host unavailable in the User action:
node selection page. Start a secondary deployer on the host where you intend to install
DataView (or DataMart).

Problem Solution
Installation messages report success, This is screen noise and can safely be ignored.
but might include messages similar to
the following:
Fatal Error]:4:1: An
invalid XML character
(Unicode: 0x1b) was
found in the element
content of the document.
When you click the Done button to Cause:

complete a fresh installation, the You stopped a fresh installation before the installing and configuring
deployer displays database access the Netcool/Proviso database.
error messages. User action:
If the Netcool/Proviso database has not been installed, complete the
installation using the -Daction=resume option (see Resuming a
Partially Successful First-Time Installation on page 40).
If the database has been installed, there is another problem. Contact

IBM Software Support.
Data does not appear in real-time Cause:

reports, and right-clicking on a real- When it starts, the channel manager (CMGR) places information in
time report does not display the the database that is needed for real-time reports to start correctly.
option menu. During installation, a cron job is created that starts CMGR. A silent
installation might run fast enough that the cron job does not run
This problem can occur with a silent before DataView is started. In this case, CMGR does not add the
installation or a minimal deployment required information to the database, and real-time reports do not
installation on a Solaris system. start up correctly.
User action:
1. Make sure that the CMGR process is running (see Management
Programs and Watchdog Scripts on page 183 and Starting the DataChannel
Management Programs on page 185).
2. Restart DataView using the following commands:
$ su -
# /etc/init.d/SilverStream stop
# /etc/init.d/SilverStream start
Installer fails to create a SilverStream Cause:

web user and reports the error Must The .bashrc or .profile startup file for the installation user
be attached to terminal contains a command such as DISPLAY=`who -m | awk -F'
for 'am I' option. ' '{print $6}' | sed s/$//g | sed
s/$/:0.0/g` that can only be run when a process is attached to
a terminal device (tty).
User action:
Edit the startup file to remove the command or make it conditional
upon attachment to the terminal device as follows:
test -t 0 && DISPLAY=`who am i | awk ...

Saving Installation Configuration Files

When you install Netcool/Proviso components, the deployer creates a set of temporary configuration files that
are used during the installation process. These files specify the components that are to be installed on a target
system and the deployment information required to install them. You can use these configuration files to
troubleshoot a Netcool/Proviso installation.
The temporary configuration files are normally removed from the target system when the deployer completes the
installation process. You can prevent the deployer from removing the files by editing the installer XML file
associated with a component. This file is named n_comp_name.xml, where n is an index number generated by
the deployer and comp is a string that identifies the component. Possibe values for the comp string are
DataView, DataMart, DataView, DBChannel and DBSetup. Installer XML files are located by default in the
/tmp/ProvisoConsumer/Plan/MachinePlan_hostname directory, where hostname is the host name
of the target system.
To prevent the deployer from removing the temporary files associated with a component install, open the
corresponding install XML file and modify the following 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 Netcool/Proviso installation problem, the support staff might ask you
for these files. You can create a 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.

Netcool/Proviso Component Problems
Problem Solution
The DataView installation failed Cause:

because SilverStream (exteNd) was Your server interface is set to half duplex mode.
not installed. User action:
Set the server interface to 100 full duplex mode.
The network or server is operating See Changing the Ethernet Characteristics on page 42 for more
slowly. Slow behavior can have information.
different causes; two possible causes
are described here. Cause:
Either the server hosting SilverStream or the server hosting Oracle is
running slowly. This can occur when the host does not have enough
RAM or swap space.
User action:
• A minimal deployment installation should have a minimum of
4G RAM and 4G swap.
• A SilverStream installation should have 1G RAM and 1G swap
allocated for SilverStream, in addition to the RAM and swap
required by other operating system and application processes.
• Other configurations should be sized by IBM Professional
Services.
NOTE: If you deploy many technology packs (especially SAM, NM,
and Nortel CS2K, which either have multiple UBAs or require
multiple DataChannel applications), you might require more
hardware capacity than is specified in the minimal configuration. In
these situations, before moving to a production environment, IBM
strongly recommends that you have Professional Services size your
deployment so that they can recommend additional hardware, if
necessary.
A Netcool/Proviso component is still Cause:

listed as Configured in the Topology The component is installed, but has not been started.
Editor even though it’s been installed. User action:
Start the component. Its status changes to Installed.
A new channel component was Cause:

deployed, or the channel The channel components need to be bounced.
configuration was changed, but the User action:
change has no effect. Bounce the components, as described in Appendix B, DataChannels.

Topology Editor Problems
Problem Solution
The Topology Editor won’t open and Cause:

the application window shows a Java You forgot to set and export your DISPLAY variable.
exception (core dump). 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 Cause:

Editor is displayed, but the Topology You did not log in as root.
Editor doesn’t start and no User action:
explanatory message is displayed. 1. Log in as root.
2. Restart the Topology Editor.
The topology editor reports the Cause:

following error when you attempt to You tried to add a UBA collector for an SNMP technology pack.
add a UBA collector: User action:
Make sure that you read the Netcool/Proviso technology packs
GYMCI0504E An internal
release notes before you install and configure a pack and before you
error occurred while
add any collectors. The release notes contain information on whether
processing file pack
a specific technology pack is a UBA or SNMP pack. UBA and SNMP
where pack is the name of the packs require you to perform different configuration steps.
application jar file. Before you install and configure an technology pack, you must also
In addition, the topology editor log read the information in Before You Begin on page 127 and follow the
file contains the following error: steps listed in that section.
YYYY-MM-DD HH:MM:SS
SEVERE FileHelper
Manifest of file pack is
corrupted. It was not
possible to determine if
its install type is
bundle or standalone.

Telnet Problems
Problem Solution
Telnet client fails at initial connection Cause:

and reports the following error: Length of the DISPLAY variable passed via the telnet client is too
long (for example, XYZ-DA03430B70B-
Not enough room in 009034197130.example.com:0.0).
buffer for display User action:
location option reply Set the value of the DISPLAY variable using the IP address of the
local system, or the hostname only without the domain name. Then,
Can occur when you start Proviso reconnect to the Solaris 10 machine using the telnet client.
components from a Solaris 10 system
where the user interface is displayed
remotely on a Windows desktop
using an X Window tool like Exceed.
Java Problems
Problem Solution
Installer reports a Java Not Found Cause:

error during installation of technology The installer expected, but did not find, Java executables in the path
packs. reported in the error message. The technology pack installation
requires the correct path in order to function.
User action:
Create a symbolic link from the reported directory to the directory
on the system where the Java executables are installed, for example:
ln -s bin_path $JAVA_HOME/bin/java
where bin_path is the directory where the binaries are located.
After you create the symbolic link, you must re-start the technology
pack installation.
Testing Connectivity to the Database

To test client connectivity to the Oracle database:
$ sqlplus system/password@PV.WORLD
In this syntax:
— password is the password you set for the Oracle system login name. (The default password is manager.)
— PV is the TNS name for your Netcool/Proviso database defined in your Oracle Net configuration.

For example:
$ sqlplus system/manager@PV.WORLD
3. Output like the following example indicates a successful connection:
SQL*Plus: Release 9.2.0.8.0 - Production on <Current Date>
Connected to:
SQL>
4. Type exit at the SQL> prompt.
Testing External Procedure Call Access

In the Oracle Net configuration, you set up an Oracle listener to wait for connections using external procedure
calls. The shared library libpvmextc.so executes system commands from stored Oracle procedures. 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 the configure_db script in the $ORACLE_HOME/lib directory.
To test external procedure call access:
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 password as 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 commands

from 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.1
ORACLE : Creating function ExternalPipe ...

ORACLE : Calling function ExternalPipe ...
UNIX : Check ExternalPipe - /var/opt/oracle
ORACLE : Dropping function Version ...

ORACLE : Dropping function ExternalCall ...
ORACLE : Dropping function ExternalPipe ...
ORACLE : Dropping library LibExtCall ...


Additional Copyright Information
The following copyright information is for software used by Netcool/Proviso.
Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and
other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any
purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any
distributions. No written agreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software
may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly
indicated on the first page of each file where they apply.
IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS
DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND
DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only
"Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause
52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as
"Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c)
(1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and others acting in its behalf permission
to use and distribute the software in accordance with the terms specified in this license.
SCOTTY Stack
This software is copyrighted by Juergen Schoenwaelder, the Technical University of Braunschweig, the University of Twente, and
other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN “AS IS” BASIS, AND THE AUTHORS AND

Additional Copyright information

Various copyrights apply to this package, listed in 3 separate parts below. Please make sure that you include all the parts. Up until
2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project
has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP
community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also
under a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001.
Part 1: CMU/UCD copyright notice: (BSD like)
Copyright © 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000
Copyright © 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission
notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be
used in advertising or publicity pertaining to distribution of the software without specific written permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD
TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL,
INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS
OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Part 2: Networks Associates Technology, Inc copyright notice (BSD)

Copyright © 2001, Networks Associates Technology, Inc
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
• Neither the name of the NAI Labs nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 3: Cambridge Broadband Ltd. copyright notice (BSD)
Portions of this code are copyright © 2001, Cambridge Broadband Ltd.
All rights reserved.
conditions are met:
• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
• The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
BLT 2.4u
Portions (c) 1993 AT&T, (c) 1993 - 1998 Lucent Technologies, (c) 1994-1998 Sun Microsystems, Inc., and (c) 1987-1993 The
Regents of the University of California.
notice appear in supporting documentation, and that the names of AT&T, Lucent Technologies Inc., Sun Microsystems, Inc. and
The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without
specific written permission.
THE COPYRIGHT HOLDERS AND OTHER CONTRIBUTORS DISCLAIM ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL THE COPYRIGHT HOLDERS OR OTHER CONTRIBUTORS BE LIABLE FOR ANY SPECIAL,
CMU-SNMP 1.14
CMU/UCD copyright notice: (BSD like) Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Scotty 2.8, incrTCL 3.0, [incr TCL] 3.2

Portions Copyright (c) 1987-1994 The Regents of the University of California. Copyright (c) 1994-1995 Sun Microsystems, Inc.

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following
terms apply to all files associated with the software unless explicitly disclaimed in individual files.
AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND
RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subject to the restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause as DFARS 252.227-7013 and FAR 52.227-
19.
Portions Copyright (c) 1993-1998 Lucent Technologies, Inc.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both that the copyright notice and warranty
disclaimer appear in supporting documentation, and that the names of Lucent Technologies any of their entities not be used in
advertising or publicity pertaining to distribution of the software without specific, written prior permission.
Lucent disclaims all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no
event shall Lucent be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of
use, data or profits, whether in an action of contract, negligence or other tortuous action, arising out of or in connection with the
use or performance of this software.
UCD SNMP 4.2.5

Portions Copyright 1989, 1991, 1992 by Carnegie Mellon University. Derivative Work - 1996, 1998-2000, Copyright 1996, 1998-
2000 The Regents of the University of California All Rights Reserved
Portions Copyright: (c) 2001-2003, Networks Associates Technology, Inc, (c) 2001-2003, Cambridge Broadband Ltd, (c) 2003-
2005, Sparta, Inc., (c) 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications,
(c) Fabasoft R&D Software GmbH & Co KG, 2003 oss@fabasoft.com. All rights reserved.
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.

3. Neither the names of Networks Associates Technology, Inc, Cambridge Broadband Ltd., Sparta, Inc., Cisco, Inc, Beijing
University of Posts and Telecommunications, Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product
names, nor the names of their contributors may be used to endorse or promote products derived from this software without specific
prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS `ÀS IS'' AND ANY
THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
JDOM 1.0
Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows
these conditions in the documentation and/or other materials provided with the distribution.
3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written
permission. For written permission, please contact <request_AT_jdom_DOT_org>.
4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written
permission from the JDOM Project Management <request_AT_jdom_DOT_org>.
In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or
in the software itself an acknowledgement equivalent to the following:
"This product includes software developed by the JDOM Project (http://www.jdom.org/)." Alternatively, the acknowledgment
may be graphical using the logos available at http://www.jdom.org/images/logos.
THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally
created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. For more
information on the JDOM Project, please see <http://www.jdom.org/>.
Regex 1.1a
Copyright (C) 1996, 1999 Vassili Bykov. It is provided to the Smalltalk community in hope it will be useful.
1. This license applies to the package as a whole, as well as to any component of it. By performing any of the activities described
below, you accept the terms of this agreement.
2. The software is provided free of charge, and `às is'', in hope that it will be useful, with ABSOLUTELY NO WARRANTY. The
entire risk and all responsibility for the use of the software is with you. Under no circumstances the author may be held responsible

for loss of data, loss of profit, or any other damage resulting directly or indirectly from the use of the software, even if the damage
is caused by defects in the software.
3. You may use this software in any applications you build.
4. You may distribute this software provided that the software documentation and copyright notices are included and intact.
5. You may create and distribute modified versions of the software, such as ports to other Smalltalk dialects or derived work,
provided that:
a. any modified version is expressly marked as such and is not misrepresented as the original software;
b. credit is given to the original software in the source code and documentation of the derived work;
c. the copyright notice at the top of this document accompanies copyright notices of any modified version.
Xwpick
Copyright © 1993, 1994 by Evgeni Chernyaev
Permission to use, copy, modify, and distribute this software and its documentation for non-commercial purpose is hereby granted
without fee, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission
notice appear in supporting documentation. Xwpick is used for printing utilities.
Sieve of Erastothenes
Copyright Frank Pilhofer, fp@fpx.de
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.
Neither the name of Frank Pilhofer nor the names of its contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

Index
A DataView 200
High Availability Manager 152, 153
Acrobat Reader ratio of primary to spare hosts 152
installing 97 collector process 151
adding collector profile 151
collector to topology 108 collectors
database configurations component to topology adding to topology 108
103 moving to a different host 144
DataChannel administrative components to moving to or from a HAM 146
topology 107 co-location rules 176
DataChannel to topology 107 components
DataMart to topology 104 adding to deployed topology 141
DataView 200 changing configuration parameters 143
DataView to topology 106 stop and restart 167
High Availability Manager 162, 167
configuration parameters
hosts to topology 102
changing values 143
UBA collectors 133
creating a topology 102
Advanced Properties view
about 27
aggregation sets
D
about 188
data aggregation 183
configuring 188
database configurations component
installing 192
adding to topology 103
AIX
DataChannel
installing Netcool/Proviso
distributed environment 98
application program names 184
minimal deployment 120
architecture 182
support 18
management components 186
APInstaller
watchdog scripts 183
using 131
DataChannel administrative components
application programs
starting 185
DataMart
B copyright information for tools 274
DataView
backup hosts
see spare hosts
linking aggregation sets to groups 197
bouncing modified HAM components 167
poc user 124
DataView component
C clusters 200
multi-SilverMaster installation 207
channel manager programs
deleting
starting manually 186
See uninstalling
stop and restart 148
deployed topology
clusters
adding components to 141

Index
opening 141 viewing configuration 168

deployer hosts
about 34 adding to topology 102
command-line options 234 clusters 152
node selection page 36 listed on node selection page 36
primary versus secondary 35 primary and spare 150, 151
running 111
running in silent mode 238 I
starting 111
steps page 37 incremental installation 140
deployment example 142
modifying the current 140 installation
designated spare 153 resuming 40
DISPLAY environment variable scenarios 40
setting 41 setup tasks 41
distributed environment steps
installing Netcool/Proviso in 98 about 37
details 39
properties 38
E status values 39
troubleshooting 264
error codes 246
installing
ethernet characteristics 42
Acrobat Reader 97
DataView clusters 200
F multi-SilverMaster 207
Netcool/Proviso
failover 161 distributed 98
fixed spare cluster 153 minimal deployment 116
floating spare 153 AIX 120
floating spare cluster 153 Solaris 117
full duplex mode patches 242
resuming 40
setting 42
Oracle client (patch version 9.2.0.6) 85
Oracle client (patch version 9.2.0.8) 73
H Oracle server 51
technology packs 126
HAM
the Starter Kit 128
see High Availability Manager
the Topology Editor 100
Help menu 34
interim fixes
High Availability Manager installing 242
about 150
bouncing modified components 167
clusters 152
L
creating 162, 167
launchpad
examples 154
about 22
failover 161
starting 99
modifying 167
Linux
moving collectors 146
removing components 167 installing Oracle client 74, 85
resource pools 159 support 18

Index
load balancer for DataView cluster 201 remote installation

log files 262 about 178
COI 262 supported platforms 18
deployer 262 troubleshooting the installation 264
Eclipse 263 uninstalling 172
technology packs 138 what’s new in Version 4.4.3 21
trace 263 node selection page
Logical view 25 about 36
log-to-traps feature 187
O
M
Oracle
managed definitions client (patch version 9.2.0.6) 85
about 151 client (patch version 9.2.0.8) 73
resource pools 159 client patch versions 46
maximizing views 31 server 51
minimal deployment 116 updating for multi-SilverMaster 208
AIX 120
post-installation script 124 P
Solaris 117
minimizing views 31 partial installation
modifying a deployed topology resuming 40
adding components 141 Patch versions for Oracle client software 46
example 142 patches
multi-SilverMaster installation 207 installing 242
Physical view 26
N poc user 124
pre-installation setup tasks 41
Netcool/Proviso prerequisite software 46
architecture 18 primary deployer 35
co-location rules 176 primary hosts
components about 150
adding 102 acting as backup hosts 153
co-location rules 176 Problems view
overview 19
about 29
error codes 246
properties
fresh installation 98
changing values 28
incremental installation 140
restoring default values 29
installation scenarios 40
Properties view
installing
distributed environment 98 about 27
fresh 98 changing a value 28
interim fixes 242 resizing columns 28
minimal deployment 116 pvuser
modifying the current environment 140 setting 49
patches 242
modifying the current deployment 140
pre-installation setup tasks 41
prerequisite software 46

Index
R about 37
style sheets, uploading on secondary servers 219
redundant collection paths 150
remote installation T
about 178
removing Technology Pack view
See uninstalling about 27
resource limits technology packs
setting 45 adding UBA collectors 133
resource pools 159 installing 126
restart Channel Manager 148 installing the Starter Kit 128
log files 138
restoring
pre-installation tasks 129
default property values 29
timezones 188
views 31
linking to DataView groups 197
resuming a partial installation 40
topology
Run menu 33
adding a collector 108
adding a High Availability Manager 162, 167
S adding DataChannel 107
adding DataMart 104
SCOTTY Stack
adding DataView 106
copyright information 274
adding hosts 102
secondary deployers 35
adding Netcool/Proviso components 102
secondary server installation adding the Database Configurations component
DataView 202, 211 103
SilverStream 221 adding the DataChannel Administrative
silent mode 238 components 107
SilverMaster 207 creating 102
SilverStream server, secondary 221 opening a deployed file 141
SNMP Collectors opening an existing topology file 110
events and states 159 saving 110
High Availability Manager environment 150 Topology Editor
moving to a different host 144 about 23
moving to or from a HAM 146 installing 100
starting 185 using silent mode 241
software menus 33
prerequisite 46 opening 24
starting 101
Solaris
tools 30
installing Netcool/Proviso
topology.xml file 30
distributed environment 98
uninstalling 174
minimal deployment 117
views 24
support 18
maximizing 31
spare hosts
minimizing 31
about 150 restoring 31
types 153
Topology menu 33
Starter Kit
topology.xml file
installing 128 See topology
steps page troubleshooting 264

Index
U
UBA collectors
adding 133
moving to a different host 146
uninstalling
components 170
High Availability Manager components 167
Netcool/Proviso 172
V
views
maximizing 31
minimizing 31
of the Topology Editor 24
restoring 31
W
watchdog scripts 183
Window menu 33
X
Xwpick
copyright information 276, 279

Index

NetcoolProviso InstallationGuide 443

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetcoolProviso InstallationGuide 443

Uploaded by

Copyright:

Available Formats

Tivoli Netcool®/Proviso® Version 4.4.

This information contains sample application programs

Chapter 2: Installing and Configuring the Prerequisite Software . . . . . . . . . . . . . . . . . . . . . 46

Netcool/Proviso Installation Guide, Version Version 4.4.3 4

Specifying a Basename for DB_USER_ROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5 Netcool/Proviso Installation Guide, Version Version 4.4.3

Create the sqlnet.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Chapter 3: Installing Netcool/Proviso in a Distributed Environment . . . . . . . . . . . . . . . . . 98

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Netcool/Proviso Installation Guide, Version Version 4.4.3 6

Opening an Existing Topology File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Chapter 4: Installing Netcool/Proviso as a Minimal Deployment . . . . . . . . . . . . . . . . . . . . 116

Chapter 5: Installing Technology Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

7 Netcool/Proviso Installation Guide, Version Version 4.4.3

Chapter 6: Modifying the Current Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Opening a Deployed Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 7:Using the High Availability Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Netcool/Proviso Installation Guide, Version Version 4.4.3 8

Removing HAM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Chapter 8: Uninstalling Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Removing a Component from the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Appendix A: Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Co-Location Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Appendix B: DataChannels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

DataChannel Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Appendix C: Aggregation Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

9 Netcool/Proviso Installation Guide, Version Version 4.4.3

Linking DataView Groups to Timezones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Appendix D: Installing Multiple DataView Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

DataView Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Netcool/Proviso Installation Guide, Version Version 4.4.3 10

Step 3: Create Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Appendix E: Deployer CLI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Using the -DTarget Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Appendix F: Using Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Sample Properties Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Appendix G: Installing an Interim Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Appendix H: Error Codes and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Appendix I: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Deployment Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

11 Netcool/Proviso Installation Guide, Version Version 4.4.3

Saving Installation Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Netcool/Proviso Installation Guide, Version Version 4.4.3 12

13 Netcool/Proviso Installation Guide, Version Version 4.4.3

Chapter 2, Installing and Configuring the Prerequisite Software 46

Chapter 3, Installing Netcool/Proviso in a Distributed Environment 98

Chapter 4, Installing Netcool/Proviso as a Minimal Deployment 116

Chapter 5, Installing Technology Packs 126

Chapter 6, Modifying the Current Deployment 140

Chapter 8, Uninstalling Components 170

Appendix A, Deployment Considerations 176

Appendix B, DataChannels 182

Appendix C, Aggregation Sets 188

Appendix D, Installing Multiple DataView Servers 200

Appendix E, Deployer CLI Options 234

Netcool/Proviso Installation Guide, Version Version 4.4.3 14

Appendix F, Using Silent Mode 238

Appendix G, Installing an Interim Fix 242

Appendix H, Error Codes and Log Files 246

Appendix I, Troubleshooting 264

The Default UNIX Shell