Netcool®/Impact: Frontmatter - FM December 15, 2004

Netcool®/ImpactTM
frontmatter.fm December 15, 2004
3.1
Administration Guide
© 2004 Micromuse Inc., Micromuse Ltd. University, Microcorrelation, Acronym, Micromuse Design, Integration Module
All rights reserved. No part of this work may be reproduced in any form or by any for Netcool, The Netcool Company, VISIONETCOOL, and Network Slice.
person without prior written permission of the copyright owner. This document is Micromuse acknowledges the use of I/O Concepts Inc. X-Direct 3270 terminal
proprietary and confidential to Micromuse, and is subject to a confidentiality emulators and hardware components and documentation in Netcool/Fusion.
agreement, as well as applicable common and statutory law. X-Direct ©1989-1999 I/O Concepts Inc. X-Direct and Win-Direct are
trademarks of I/O Concepts Inc.
Micromuse Disclaimer of Warranty and Statement of Limited Liability Netcool/Fusion contains IBM Runtime Environment for AIX®, Java™
Micromuse provides this document "as is", without warranty of any kind, either Technology Edition Runtime Modules © Copyright IBM Corporation 1999. All
express or implied, including, but not limited to, the implied warranties of rights reserved.
merchantability, fitness for a particular purpose or non-infringement. This Micromuse acknowledges the use of the UCD SNMP Library Netcool/ISMs.
document may contain technical inaccuracies or typographical errors. Micromuse Copyright © 1989, 1991, 1992 by Carnegie Mellon University. Derivative Work
may make improvements and changes to the programs described in this document - Copyright © 1996, 1998, 1999, 2000 The Regents of the University of
or this document at any time without notice. Micromuse assumes no responsibility California. All rights reserved.
for the use of the programs or this document except as expressly set forth in the
Portions of the Netcool/ISMs code are copyright ©2001, Cambridge Broadband
applicable Micromuse agreement(s) and subject to terms and conditions set forth
Ltd. All rights reserved.
therein. Micromuse does not warrant that the functions contained in the programs
will meet your requirements, or that the operation of the programs will be Portions of the Netcool/ISMs code are copyright © 2001, Networks Associates
uninterrupted or error-free. Micromuse shall not be liable for any indirect, Technology, Inc. All rights reserved.
consequential or incidental damages arising out of the use or the ability to use the Micromuse acknowledges the use of Viador Inc. software and documentation for
programs or this document. Netcool/Reporter. Viador © 1997-1999 is a trademark of Viador Inc.
Micromuse specifically disclaims any express or implied warranty of fitness for high Micromuse acknowledges the use of software developed by the Apache Group for
risk activities. use in the Apache HTTP server project. Copyright © 1995-1999 The Apache
Micromuse programs and this document are not certified for fault tolerance, and Group. Apache Server is a trademark of the Apache Software Foundation
are not designed, manufactured or intended for use or resale as on-line control (http://www.apache.org/). All rights reserved.
equipment in hazardous environments requiring fail-safe performance, such as in Micromuse acknowledges the use of software developed by Edge Technologies,
the operation of nuclear facilities, aircraft navigation or communication systems, Inc. 2003 Edge Technologies, Inc. and Edge enPortal are trademarks or registered
air traffic control, direct life support machines, or weapons systems ("High Risk trademarks of Edge Technologies Inc. All rights reserved.
Activities") in which the failure of programs could lead directly to death, personal Micromuse acknowledges the use of Merant drivers. Copyright © MERANT
injury, or severe physical or environmental damage. Solutions Inc., 1991-1998.
The following product names are trademarks of Tivoli Systems or IBM
Compliance with Applicable Laws; Export Control Laws
Corporation: AIX, IBM, OS/2, RISC System/6000, Tivoli Management
Use of Micromuse programs and documents is governed by all applicable federal, Environment, and TME10.
state and local laws. All information therein is subject to U.S. export control laws
IBM, NetView/6000 and WebSphere are either trademarks or registered
and may also be subject to the laws of the country where you reside.
trademarks of IBM Corporation. VTAM is a trademark of IBM Corporation.
All Micromuse programs and documents are commercial in nature. Use,
Omegamon is a trademark of Candle Corporation.
duplication or disclosure by the United States Government is subject to the
restrictions set forth in DFARS 252.227-7015 and FAR 52.227-19. Netspy is a trademark of Computer Associates International Inc.
The Sun logo, Sun Microsystems, SunOS, Solaris, SunNet Manager, Java are
Trademarks and Acknowledgements trademarks of Sun Microsystems Inc.
Micromuse and Netcool are registered trademarks of Micromuse. SPARC is a registered trademark of SPARC International Inc. Programs bearing
Other Micromuse trademarks include but are not limited to: Netcool/OMNIbus, the SPARC trademark are based on an architecture developed by Sun
Netcool/OMNIbus for Voice Networks, Netcool/Reporter, Netcool/Internet Microsystems Inc. SPARCstation is a trademark of SPARC International Inc.,
Service Monitors, Netcool/ISMs, Netcool/ISM Global Perspective, Netcool/NT licensed exclusively to Sun Microsystems Inc.
Service Monitors, Netcool/Wireless Service Monitors, Netcool/WSMs, UNIX is a registered trademark of the X/Open Company Ltd.
Netcool/Usage Service Monitors, Netcool/USMs, Netcool/Telco Service Sybase is a registered trademark of Sybase Inc.
Monitors, Netcool/TSMs, Netcool/Fusion, Netcool/Data Center Monitors,
Action Request System and Remedy are registered trademarks of Remedy
Netcool DCMs, Netcool/Impact, Netcool/Visionary, Netcool/Precision, Netcool
Corporation.
Probes & Monitors, Netcool Desktops, Netcool Gateways, Netcool Impact/Data
Source Adaptors, Netcool EventList, Netcool Map, Netcool Virtual Operator, Peregrine System and ServiceCenter are registered trademarks of Peregrine Systems
Netcool/Precision for IP Networks, Netcool/Precision for Transmission Inc.
Networks, Netcool/Firewall, Netcool/Wave, Netcool/Webtop, Netcool TopoViz, HP, HP-UX and OpenView are trademarks of Hewlett-Packard Company.
Netcool/SM Operations, Netcool/SM Configuration, Netcool/OpCenter, InstallShield is a registered trademark of InstallShield Software Corporation.
Netcool/System Service Monitors, Netcool/SSMs, Netcool/Application Service
Microsoft, Windows 95/98/Me/NT/2000/XP are either registered trademarks or
Monitors, Netcool/ASMs, Netcool/ISM WAM, Netcool/SM Reporter, Netcool
trademarks of Microsoft Corporation.
for Asset Management, Netcool/Realtime Active Dashboards,
Netcool/Dashboards, Netcool/RAD, Netcool for Voice over IP, Netcool for Microsoft Internet Information Server/Services (IIS), Microsoft Exchange Server,
Security Management, Netcool Security Manager, Netcool/Portal 2.0 Premium Microsoft SQL Server, Microsoft perfmon and Microsoft Cluster Service are
Edition, Netcool ObjectServer, Netcool/RAD, Netcool/Software Developers Kit, registered trademarks of Microsoft Corporation.
Micromuse Alliance Program, Micromuse Channel Partner, Authorized Netcool BEA and WebLogic are registered trademarks of BEA Systems Inc.
Reseller, Netcool Ready, Netcool Solutions, Netcool Certified, Netcool Certified FireWall-1 is a registered trademark of Check Point Software Technologies Ltd.
Consultant, Netcool Certified Trainer, Netcool CCAI Methodology, Micromuse
Netscape and Netscape Navigator are registered trademarks of Netscape
Communications Corporation in the United States and other countries. Software without restriction, including without limitation the rights to use, copy,
Netscape's logos and Netscape product and service names are also trademarks of modify, merge, publish, distribute, sublicense, and/or sell copies of the Expat
Netscape Communications Corporation, which may be registered in other Software. Expat's permission is subject to the following conditions: The above
countries. copyright notice and this permission notice shall be included in all copies or
substantial portions of the Expat Software. Except as set forth hereunder, all
Micromuse acknowledges the use of Xpm tool kit components.
software provided by Micromuse hereunder is subject to the applicable license
SentinelLM is a trademark of Rainbow Technologies Inc. agreement.
GLOBEtrotter and FLEXlm are registered trademarks of Globetrotter Software Micromuse acknowledges that Netcool Security Manager includes Hypersonic
Inc. SQL. Copyright (c) 2001-2002, The HSQL Development Group. All rights
Red Hat, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM reserved.
logo, Linux Library, PowerTools, Linux Undercover, RHmember, RHmember JABBER® is a registered trademark and its use is granted under a sublicense from
More, Rough Cuts, Rawhide and all Red Hat-based trademarks and logos are the Jabber Software Foundation
trademarks or registered trademarks of Red Hat Inc. in the United States and other
Micromuse acknowledges the use of MySQL in Netcool/Precision for IP
countries.
Networks and in Netcool/Precision for Transmission Networks. Copyright ©
Linux is a registered trademark of Linus Torvalds. 1995, 1996 TcX AB & Monty Program KB & Detron
Nokia is a registered trademark of Nokia Corporation. All other trademarks, registered trademarks and logos are the property of their
WAP Forum™ and all trademarks, service marks and logos based on these respective owners.
designations (Trademarks) are marks of Wireless Application Protocol Forum Ltd. Micromuse Inc., 139 Townsend Street, San Francisco, USA CA 94107
Micromuse acknowledges the use of InstallAnywhere software in Netcool/WAP www.micromuse.com
Service Monitors. Copyright © Zero G Software Inc.
Document Version Number: 1.1
Orbix is a registered trademark of IONA Technologies PLC. Orbix 2000 is a
trademark of IONA Technologies PLC.
Micromuse acknowledges the use of Graph Layout Toolkit in Netcool/ Precision
for IP Networks. Copyright © 1992 - 2001, Tom Sawyer Software, Berkeley,
California. All rights reserved.
Portions of Netcool/Precision for IP Networks are © TIBCO Software, Inc.
1994-2003. All rights reserved. TIB and TIB/Rendezvous are trademarks of
TIBCO Software, Inc.
Portions of Netcool/Precision for IP Networks are Copyright © 1996-2003,
Daniel Stenberg, <daniel@haxx.se>.
Micromuse acknowledges the use of Digital X11 in Netcool/Precision for IP
Networks. Copyright 1987, 1988 by Digital Equipment Corporation, Maynard,
Massachusetts, All Rights Reserved. DIGITAL DISCLAIMS ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN
NO EVENT SHALL DIGITAL 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 TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Netcool/SM Operations, Netcool/SM Configuration and Netcool/OpCenter
include software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http://www.openssl.org/).
Micromuse acknowledges the use of software developed by ObjectPlanet. ©2003
ObjectPlanet, Inc, Ovre Slottsgate, 0157 Oslo, Norway.
Micromuse acknowledges the use of Expat in Netcool/ASM. Copyright 1998,
1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper. Copyright
2001, 2002 Expat maintainers. THE EXPAT SOFTWARE IS PROVIDED
HEREUNDER "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS OF THE EXPAT SOFTWARE BE LIABLE FOR
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE EXPAT SOFTWARE OR
THE USE OR OTHER DEALINGS IN THE SOFTWARE. Expat explicitly
grants its permission to any person obtaining a copy of any Expat software and
associated documentation files (the "Expat Software") to deal in the Expat
Contents
MMGuideTOC.fm December 15, 2004 10:15 am
Contents
Preface ...................................................................................... 1
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
About the Netcool/Impact 3.1 Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Associated Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Netcool/Impact Solutions Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Netcool/Impact User Interface Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Netcool/Impact Policy Reference Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Netcool/Impact Web Services Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Netcool/Impact Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Netcool/Impact Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Typographical Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Note, Tip, and Warning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Syntax and Example Subheadings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Operating System Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1: Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About Netcool/Impact Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
What Is a Netcool/Impact Installation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
What Are the Supported Installation Types? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
How Do I Set Up an Installation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
How Do I Manage an Installation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Installation Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Netcool Common License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Netcool Security Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Netcool GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installation Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Netcool/Impact 3.1 Administration Guide i

Contents
Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Single System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Distributed Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Setting Up an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Planning an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Licensing Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Creating a Netcool/Impact Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuring Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Running an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Running an Installation Under Process Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
What Is Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
How Do I Set Up Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Managing an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 2: Netcool Common License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

About the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
What Is the License Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
What Are the Supported Configurations?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
What Are the License Server Components? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

How Do I Set Up the License Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
How Do I Install Licenses?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
How Do I Run the License Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Can I Run the License Server Under Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
How Do I Manage the License Server?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
ii Netcool/Impact 3.1 Administration Guide

Contents
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Hardware Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Exceed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Licensing Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
License Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
License Server Daemons (UNIX Platforms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
License Server Service (Windows Platforms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
License Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Command Line Tools (UNIX Platforms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

LMTOOLS (Windows Platforms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Installing the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Running the License Server Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Setting the License Server Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Verifying Port Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Reading the Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Installing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Generating the License Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Obtaining License Feature Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Requesting the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Installing the License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Managing the License Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Starting the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Viewing License Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Refreshing the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Stopping the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Viewing the License Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Netcool/Impact 3.1 Administration Guide iii

Contents
Managing the License Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Starting the License Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Viewing License Server Status on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Refreshing the License Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Stopping the License Server on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Viewing the License Host ID on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Using the FLEXlm Command Line Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Quorum Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
What Is Quorum Licensing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
How Do I Set Up a Quorum? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
How Do I Configure Netcool/Impact Components to Use a Quorum? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Uninstalling the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Uninstalling on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Uninstalling on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Chapter 3: Netcool GUI Server ....................................................... 53

About the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
What Is the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
How Do I Set Up the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
How Do I License the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

How Do I Run the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Can I Run the GUI Server Under Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
How Do I Administer the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Java Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
License Server Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Security Manager Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Web Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Exceed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
iv Netcool/Impact 3.1 Administration Guide

Contents
GUI Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Servlet Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Application Registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
GUI Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Installing the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Installing the Java Development Kit (AIX and HP-UX Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Running the GUI Server Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Setting the GUI Server Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Licensing the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Quorum Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Running the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Starting the GUI Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Stopping the GUI Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Starting the GUI Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Stopping the GUI Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuring the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuring Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring the Servlet Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring the Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Registry Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
What Is Registry Clustering? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
What Are the Clustering Components? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
How Do I Set Up Registry Clustering? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

How Do I Run a Registry Cluster?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
How Does Registry Clustering Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
How Do I View Registry Status? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
GUI Server Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Netcool/Impact 3.1 Administration Guide v

Contents
Uninstalling the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Uninstalling on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 4: Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
About Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
What Is Netcool/Impact? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
What Are the Netcool/Impact Components? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
How Do I Set Up Netcool/Impact? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
How Do I License Netcool/Impact?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
How Do I Configure Netcool/Impact? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
How Do I Manage Netcool/Impact? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Java Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
License Server Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Security Manager Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
GUI Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Web Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Netcool/OMNIbus Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Exceed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Netcool/Impact Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Netcool/Impact Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Netcool/Impact Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Netcool/Impact DSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Netcool/Impact CVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Netcool/Impact JRExec Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Netcool/Impact Operator View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Netcool/Impact GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Netcool/Impact Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
vi Netcool/Impact 3.1 Administration Guide

Contents
Installing Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configuring the Operating System Kernel (UNIX Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Running the Netcool/Impact Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Setting the IMPACT_HOME Environment Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Upgrading Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Upgrading from Netcool/Impact 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Upgrading from Netcool/Impact 2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Licensing Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Configuring Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Quorum Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Configuring Registry Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configuring Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Backing Up and Restoring Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Uninstalling Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Uninstalling on Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Chapter 5: Netcool/Impact Server .................................................. 103

About the Netcool/Impact Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
What Is the Netcool/Impact Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
What Are the Supported Server Configurations? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
What Is a Server Instance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
How Do I Set Up a Server Instance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
How Do I Run a Server Instance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
How Do I Monitor a Server Instance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Creating Server Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Netcool/Impact 3.1 Administration Guide vii

Contents
Running Server Instances on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Starting Netcool/Impact on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Stopping Netcool/Impact on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Running Server Instances on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Starting Netcool/Impact on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Stopping Netcool/Impact on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Monitoring Server Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Deleting Server Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Running the Remove Server Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Running the Remove CVS Archives Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Chapter 6: Netcool/Impact Server Clustering ................................... 111

About Server Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
What Is Server Clustering? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
What are the Clustering Components?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
How Does Clustering Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
How Do I Set Up Server Cluster? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Clustering Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Primary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Secondary Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
How Server Clustering Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Event Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Event Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Setting Up a Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Installing a Server Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configuring a Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
viii Netcool/Impact 3.1 Administration Guide

Contents
Running a Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Starting a Cluster Member. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Stopping a Cluster Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Chapter 7: Netcool/Impact Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

About Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
How Version Control Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Element Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Check Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Check In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Element Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Element Renaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Configuring Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Chapter 8: Netcool/Impact Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

About the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
What is the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
How Do I Set Up the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
How Do I License the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

How Do I Run the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
How Do I Manage the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Cygwin Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Configuring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Setting the Database Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Setting PostgreSQL Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Running the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Starting the Database on UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Stopping the Database on UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Starting the Database on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Stopping the Database on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Netcool/Impact 3.1 Administration Guide ix

Contents
Managing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Resetting the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Viewing the Database Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Connecting to the Database with the Command Line Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Restoring the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Chapter 9: Netcool/Impact JRExec Server ........................................ 133

About the JRExec Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
What Is the JRExec Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
How Do I Set Up the JRExec Server?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

How Do I Run the JRExec Server?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Can I Run the JRExec Server Under Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
How Do I Configure the JRExec Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Running the JRExec Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Starting the JRExec Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Stopping the JRExec Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Starting the JRExec Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Stopping the JRExec Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Configuring the JRExec Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Chapter 10: Netcool/Impact Self-Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

About Netcool/Impact Self-Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
What Is Self-Monitoring?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
How Does Self-Monitoring Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

How Does Self-Monitoring Work with a Netcool/Impact Cluster? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
How Do I Set Up Self-Monitoring? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
How Do I Manage Netcool/Impact Events?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
x Netcool/Impact 3.1 Administration Guide

Contents
Memory Status Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

About Memory Status Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Memory Status Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Memory Event Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Queue Size Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

About Queue Size Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Queue Status Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Queue Status Event Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Setting Up Self-Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Setting Up Self-Monitoring Using the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Setting Up Self-Monitoring Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Viewing Information About Self-Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Memory Status History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Queue Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Queue Status History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Current JVM Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Available JVM Heap Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Maximum JVM Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Maximum Required Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Available System Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Deduplication Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Monitoring Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
ObjectServer Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Chapter 11: Command Line Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

nci_crypt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
nci_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
nci_import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Netcool/Impact 3.1 Administration Guide xi

Contents
nci_trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Runtime Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
UNIX Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Windows Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Appendix A: Supplementary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Netcool License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Netcool GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Netcool Security Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Netcool/Impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Netcool/Impact Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Firewall Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

UNIX Kernel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Configuring Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Configuring Red Hat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Configuring HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Configuring AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Appendix B: DSA Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

About the Built-In DSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
SQL Database DSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
DB2 DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

JDBC Driver Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Data Source Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Flat File DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Data Type Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
xii Netcool/Impact 3.1 Administration Guide

Contents
Informix DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

JDBC Driver Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
MySQL DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

JDBC Driver Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
ObjectServer DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Supported Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
ODBC DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

JDBC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Oracle DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

JDBC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
PostgreSQL DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

JDBC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
SQL Server DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

JDBC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Netcool/Impact 3.1 Administration Guide xiii

Contents
Sybase DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Supported Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
xiv Netcool/Impact 3.1 Administration Guide

Preface
00_Preface.fm December 15, 2004
This preface contains information about this guide and about the Netcool/Impact documentation.
It contains the following sections:
• Audience on page 2
• About the Netcool/Impact 3.1 Administration Guide on page 3
• Associated Publications on page 4
• Typographical Notation on page 6
• Operating System Considerations on page 9
Netcool/Impact 3.1 Administration Guide 1

Preface
Audience
This guide contains information on installing, configuring and running Netcool/Impact and its related
software components. It is intended for Netcool/Impact administrators and for other users who are
responsible for setting up and managing this product.
2 Netcool/Impact 3.1 Administration Guide

About the Netcool/Impact 3.1 Administration Guide
About the Netcool/Impact 3.1 Administration Guide

This guide contains the following chapters:
• Chapter 1: Getting Started on page 11

• Chapter 2: Netcool Common License Server on page 27
• Chapter 3: Netcool GUI Server on page 53
• Chapter 4: Netcool/Impact on page 79
• Chapter 5: Netcool/Impact Server on page 103
• Chapter 6: Netcool/Impact Server Clustering on page 111
• Chapter 7: Netcool/Impact Version Control on page 121
• Chapter 8: Netcool/Impact Database on page 125
• Chapter 9: Netcool/Impact JRExec Server on page 133
• Chapter 10: Netcool/Impact Self-Monitoring on page 137
• Chapter 11: Command Line Tools on page 153
• Appendix A: Supplementary Information on page 161
• Appendix B: DSA Reference on page 169

Preface
Associated Publications
Netcool/Impact 3.1 provides the following addtional documentation:
• Netcool/Impact Solutions Guide

• Netcool/Impact User Interface Guide
• Netcool/Impact Policy Reference Guide
• Netcool/Impact Web Services Guide
• Netcool/Impact Online Help
• Netcool/Impact Release Notes
Netcool/Impact Solutions Guide

This guide contains information on implementing Netcool/Impact solutions in your environment. It
contains information on setting up a data model, working with services and developing policies. This guide
is intended for Netcool/Impact administrations and for other users who are responsible for implementing
Netcool/Impact.
Netcool/Impact User Interface Guide

This guide provides step-by-step instructions on using the Netcool/Impact user interface. It is intended for
all Netcool/Impact users.
Netcool/Impact Policy Reference Guide

This guide contains reference information about the Netcool/Impact Policy Language (IPL). It contains
complete information about policy language syntax, data types, operators and functions. It is intended for
users who are responsible for writing and running Netcool/Impact policies.
Netcool/Impact Web Services Guide

This guide contains information on using the Netcool/Impact Web Services DSA and on using
Netcool/Impact as a web service.
Netcool/Impact Online Help

This online help system provides step-by-step instructions on using the Netcool/Impact user interface. It
also provides a complete policy language reference. This guide is intended for all Netcool/Impact users.

Associated Publications
Netcool/Impact Release Notes

This guide provides information about new features, system requirements and known issues for this version
of Netcool/Impact.

Preface
Typographical Notation
Table 1 shows the typographical notation and conventions used to describe commands, SQL syntax, and
graphical user interface (GUI) features. This notation is used throughout this book and other Netcool®
publications.
Table 1: Typographical Notation and Conventions (1 of 2)
Example Description
Monospace The following are described in a monospace font:
• Commands and command line options
• Screen representations
• Source code
• Object names
• Program names
• SQL syntax elements
• File, path, and directory names
Italicized monospace text indicates a variable that the user must populate. For example, -password
password.
Bold The following application characteristics are described in a bold font style:
• Buttons
• Frames
• Text fields
• Menu entries
A bold arrow symbol indicates a menu entry selection. For example, File→Save.
Italic The following are described in an italic font style:
• An application window name; for example, the Login window
• Information that the user must enter

• The introduction of a new term or definition
• Emphasized text

Typographical Notation
Table 1: Typographical Notation and Conventions (2 of 2)
Example Description
[1] Code or command examples are occasionally prefixed with a line number in square brackets. For
example:
[1] First command...

[2] Second command...
[3] Third command...
{ a | b } In SQL syntax notation, curly brackets enclose two or more required alternative choices, separated by
vertical bars.
[ ] In SQL syntax notation, square brackets indicate an optional element or clause. Multiple elements or
clauses are separated by vertical bars.
| In SQL syntax notation, vertical bars separate two or more alternative syntax elements.
... In SQL syntax notation, ellipses indicate that the preceding element can be repeated. The repetition is
unlimited unless otherwise indicated.
,... In SQL syntax notation, ellipses preceded by a comma indicate that the preceding element can be
repeated, with each repeated element separated from the last by a comma. The repetition is unlimited
unless otherwise indicated.
a In SQL syntax notation, an underlined element indicates a default option.
( ) In SQL syntax notation, parentheses appearing within the statement syntax are part of the syntax and
should be typed as shown unless otherwise indicated.
Many Netcool commands have one or more command line options that can be specified following a hyphen
(-).
Command line options can be string, integer, or BOOLEAN types:
• A string can contain alphanumeric characters. If the string has spaces in it, enclose it in quotation
(") marks.
• An integer must contain a positive whole number or zero (0).
• A BOOLEAN must be set to TRUE or FALSE.
SQL keywords are not case-sensitive, and may appear in uppercase, lowercase, or mixed case. Names of
ObjectServer objects and identifiers are case-sensitive.

Preface
Note, Tip, and Warning Information

The following types of information boxes are used in the documentation:
Note: Note is used for extra information about the feature or operation that is being described. Essentially,
this is for extra data that is important but not vital to the user.
Tip: Tip is used for additional information that might be useful for the user. For example, when describing
an installation process, there might be a shortcut that could be used instead of following the standard
installation instructions.
Warning: Warning is used for highlighting vital instructions, cautions, or critical information. Pay close
! attention to warnings, as they contain information that is vital to the successful use of our products.
Syntax and Example Subheadings

The following types of constrained subheading are used in the documentation:
Syntax
Syntax subheadings contain examples of ObjectServer SQL syntax commands and their usage. For example:
CREATE DATABASE database_name;
Example
Example subheadings describe typical or generic scenarios, or samples of code. For example:
[1] <body>
[2] <img src="ChartView?template=barchart&format=PNG
[3] &request=image&chart=quote&width=800&height=400" border="0" height="400"
[4] width="800" alt="Events by Severity"
[5] >
[6] </body>

Operating System Considerations
Operating System Considerations

All command line formats and examples are for the standard UNIX shell. UNIX is case-sensitive. You must
type commands in the case shown in the book.
Unless otherwise specified, command files are located in the $IMPACT_HOME/bin directory, where
$IMPACT_HOME is the UNIX environment variable that contains the path to the Netcool/Impact home
directory.
On Microsoft Windows platforms, replace $IMPACT_HOME with %IMPACT_HOME% and the forward
slash (/) with a backward slash (\).

Preface

Chapter 1: Getting Started
01_Getting_Started.fm December 15, 2004 10:15 am
This chapter contains the information you need to get started with a Netcool/Impact installation.
• About Netcool/Impact Installations on page 12

• Installation Components on page 14
• Installation Architecture on page 15
• Installation Types on page 16
• Setting Up an Installation on page 18
• Running an Installation on page 21
• Running an Installation Under Process Control on page 23
• Managing an Installation on page 25

1.1 About Netcool/Impact Installations

This section contains overview information about Netcool/Impact installations.
It contains the following topics:
• What Is a Netcool/Impact Installation?

• What Are the Supported Installation Types?
• How Do I Set Up an Installation?
• How Do I Manage an Installation?
What Is a Netcool/Impact Installation?

A Netcool/Impact installation is an implementation of Netcool/Impact and its related software components.
The components of an installation are:
• Netcool/Impact
• Netcool Common License Server
• Netcool Security Manager
• Netcool GUI Server
For more information, see Installation Components on page 14.
What Are the Supported Installation Types?

Netcool/Impact supports both single system and distributed installations. Single system installations consist
of Netcool/Impact and its related software components installed on a single target system. A distributed
installation is one in which Netcool/Impact and its components are installed on multiple systems and then
configured to work together across a network.
For more information, see Installation Types on page 16.
How Do I Set Up an Installation?

Before you set up an installation, you must first understand your environment and your goals for
Netcool/Impact. You can then plan how you want to install the product based on your requirements. After
you finish planning, you can install, license and configure the installation components on the appropriate
target systems.
For more information, see Setting Up an Installation on page 18.

About Netcool/Impact Installations
How Do I Manage an Installation?

You manage an installation of Netcool/Impact using either command line scripts (on UNIX platforms) or
Windows-based management tools and applications (on Windows platforms). Netcool/Impact also provides
web-based GUIs that you can use to perform administration tasks. In addition, Netcool/Impact and its
related components provide a variety of log files and other tools that you can also use to monitor their status
and troubleshoot problems.

1.2 Installation Components

A Netcool/Impact installation has the following components:
• Netcool/Impact
• Netcool Common License Server
• Netcool Security Manager
• Netcool GUI Server
Netcool/Impact
Netcool/Impact is the analysis and correlation engine for the Netcool suite of network management
products. Netcool/Impact allows you to extensively customize and enhance Netcool/OMNIbus and other
Netcool products by adding such functionality as advanced event and business data correlation, event
enrichment and event notification. In addition, you can use Netcool/Impact to integrate
Netcool/OMNIbus with a wide variety of third party software, including databases, messaging systems and
network inventory applications.
Netcool/Impact is the primary component of the installation. For more information on Netcool/Impact, see
Chapter 4: Netcool/Impact on page 79.
Netcool Common License Server

The Netcool Common License Server provides licensing functionality for Netcool/Impact, the Netcool
Security Manager and the Netcool GUI Server. For more information on the Netcool Common License
Server, see Chapter 2: Netcool Common License Server on page 27.
Netcool Security Manager

The Netcool Security Manager provides user authentication for Netcool/Impact and the Netcool GUI
Server. For more information on the Netcool Security Manager, see the Netcool Security Manager
Administration Guide.
Netcool GUI Server

The GUI Server is a standalone server application that hosts web-based graphical user interfaces for
Netcool/Impact and the Netcool Security Manager. For more information on the Netcool GUI Server, see
Chapter 3: Netcool GUI Server on page 53.

Installation Architecture
1.3 Installation Architecture

The following figure shows the basic architecture of a Netcool/Impact installation.
Netcool/
Impact
Netcool Netcool
Common Security
License Manager
Server
Netcool
GUI
Server
Figure 1: Netcool/Impact Installation Architecture

1.4 Installation Types

Netcool/Impact supports the following installation types:
• Single System Installation

• Distributed Installation
Single System Installation

A single server installation consists of Netcool/Impact and the related software components installed on a
single system. This type of installation is suitable for testing and demonstrating Netcool/Impact. Single
server installations are not recommended for live production environments.
Distributed Installation
A distributed installation is one in which Netcool/Impact and its components are installed on multiple
systems and then configured to work together across a network. This type of installation is the most common
and offers the highest degree of flexibility and customization for live production environments.
There are a variety of possible configurations for this type of installation. One recommended configuration
is as follows:
• Each instance of the Netcool/Impact server is located on a separate system.

• The Netcool Common License Server, Netcool Security Manager and the Netcool GUI Server,
which can be shared between multiple Netcool products, are located on one or more separate systems.

Installation Types
The following figure shows this type of distributed installation.
Netcool/
Impact
Netcool/ Netcool/
Impact Impact
Netcool Netcool
Common Security
License Netcool Manager
Server GUI
Server
Figure 2: Netcool/Impact Distributed Installation

1.5 Setting Up an Installation

This section contains general information on setting up a Netcool/Impact installation.
• Before You Begin

• Planning an Installation
• Installing Components
• Licensing Components
• Creating a Netcool/Impact Server Instance
• Configuring Components
Before You Begin

Before you start setting up Netcool/Impact, you must have an understanding of how Netcool/OMNIbus
and other Netcool products are installed and used in your environment. Specifically, you must know what
type of alerts are collected by Netcool probes and monitors and how the alerts are stored in the
Netcool/OMNIbus ObjectServer database. You must also have an understanding of your network topology,
including the types of systems, devices and applications that exist on the network and how they are
monitored by Netcool/OMNIbus.
Planning an Installation
After you understand how Netcool/OMNIbus and other Netcool products are installed and used in your
environment, you can plan your Netcool/Impact installation.
For testing or demonstration purposes, Micromuse recommends that you install Netcool/Impact and its
components on a single system. This type of installation requires little planning and is the easiest to create
and maintain.
For real-life production installations, you must take into account your goals, requirements and available
resources before you install the software. Micromuse recommends that you create a diagram of the
installation you want to create before you begin. Your Micromuse account representative can help you
determine what type of hardware you need to run the installation and how to configure it to fit your
requirements.

Setting Up an Installation
Installing Components
You must install the components in the following order:
• License Server
• GUI Server
• Security Manager
• Netcool/Impact
If you have already installed the License Server, the Security Manager or the GUI Server for use with another
Netcool product, you do not need to install another instance for use with Netcool/Impact.
Netcool/Impact and its components provide installer programs that you can run in GUI mode or in console
mode. In GUI mode, the installers present a series of graphical windows that guide you through the
installation process. In console mode, the installers prompt you for required information from the command
line. If you are running the installer remotely using telnet or another command line application, you must
run the installer in console mode.
Micromuse recommends that you prepare a worksheet and record the information that you provide to the
installer programs. You can print and use the sample worksheet included in the Appendix A: Supplementary
Information on page 161, or create your own.
For more information, see:
• Installing the License Server on page 36

• Installing the GUI Server on page 60
• Installing the Security Manager in the Netcool Security Manager Administration Guide.
• Installing Netcool/Impact on page 88
Licensing Components
Netcool/Impact, the Security Manager and the GUI Server are compatible with the Netcool/Impact 2.3
license server and the Netcool Common License Server. You must obtain the license feature codes for
Netcool/Impact and its related components and then install them in the license server before you can run
them.
For more information, see Licensing the Security Manager in the Security Manager Administration Guide,
Licensing the GUI Server on page 63 and Upgrading Netcool/Impact on page 91.

Creating a Netcool/Impact Server Instance

After you have installed Netcool/Impact and its related software components, you must create a new
instance of the Netcool/Impact server.
Netcool/Impact provides a program named nci_new_server that guides you through the instance
creation process. This program creates the required properties files and other files associated with the server
instance and stores them in the $IMPACT_HOME/etc directory.
For more information, see Creating Server Instances on page 106.
Configuring Components
The installer programs set the minimum required configuration properties during installation. You can
change the configuration of a component at any time by manually editing the properties files. Depending
on the component, you might need to stop and restart after making configuration changes.

Running an Installation
1.6 Running an Installation

Micromuse recommends that you start Netcool/Impact and its related components in the following order:
• License Server
• GUI Server
• Security Manager
• Netcool/Impact
You must start the Netcool/Impact server after you start the other components.
The following table shows the commands for starting the components on UNIX platforms.
Table 2: Netcool/Impact Component Commands
Component Command
License Server $NCLICENSE/bin/nc_start_license
GUI Server $GUI_HOME/bin/ncgui_server
Security Manager $SM_HOME/bin/ncsm_server
Netcool/Impact $IMPACT_HOME/bin/nci_db start (Optional)
$IMPACT_HOME/bin/nci_server server
where server is the name of the server instance
On Windows platforms, Netcool/Impact and its related components run as Windows services. To start and
stop these programs, you must use the Windows Services Administration tools. The License Server also
provides a Windows program called LMTOOLS that you can use to start and stop the server.
The following table shows the names of the Windows services.
Table 3: Netcool/Impact Windows Services (1 of 2)
Component Service Name
License Server Netcool License Server
GUI Server Netcool GUI Server
Security Manager Netcool Security RMI, Netcool Database (Security), Netcool Security Manager

Table 3: Netcool/Impact Windows Services (2 of 2)
Component Service Name
Netcool/Impact Netcool Impact server
where server is the name of the server instance,

Netcool Database (Impact)

Running an Installation Under Process Control
1.7 Running an Installation Under Process Control

This section contains information running Netcool/Impact and its related components under process
control.
• What Is Process Control?

• How Do I Set Up Process Control?
• Sample Configuration File
What Is Process Control?

Process control is a feature of Netcool/OMNIbus that helps maintain uptime for applications in the Netcool
suite. You can use this feature to make sure that Netcool/Impact and its related components are
automatically restarted in the event that they stop due to software failure. Use of process control with
Netcool/Impact is optional.
Netcool/Impact, the Netcool Common License Server, the Netcool Security Manager and the Netcool GUI
Server run as "non-pa aware" applications.
For additional information on process control, see the Netcool/OMNIbus Administration Guide.
How Do I Set Up Process Control?

To set up process control, you must install the process control manager on each system in your environment
where you are running Netcool/Impact and its related components. After you have installed the process
control manager, you must edit the nco_pa.conf file on each system.
For instructions on installing the process control manager and setting up process control in your
environment, see the Netcool/OMNIbus Administration Guide.

Sample Configuration File

The following is a sample nco_pa.conf configuration file that shows the process definitions for
Netcool/Impact and its related components. Real-world configuration files will differ depending on how
you have installed and configured your installation.
nco_process ’LicenseServer’
{
Command ’$NCLICENSE/bin/nc_start_license’ run as impact
Host=’HOST_01’
Managed=true
RestartMsg=’The License Server has restarted.’
AlertMsg=’The License Server has gone down.’
RetryCount=3
ProcessType=PaNOT_PA_AWARE
}
nco_process ’GUIServer’
{
Command ’$GUI_HOME/bin/ncgui_server’ run as impact
Host=’HOST_01’
Managed=true
RestartMsg=’The GUI Server has restarted.’
AlertMsg=’The GUI Server has gone down.’
RetryCount=3
}
nco_process ’SecurityManager
{
Command ’$SM_HOME/bin/ncsm_server’ run as impact
Host=’HOST_01’
Managed=true
RestartMsg=’The Security Manager has restarted.’
AlertMsg=’The Security Manager has gone down.’
RetryCount=3
}
nco_process ’Impact_NCI’
{
Command ’$IMPACT_HOME/bin/nci_server NCI’ run as impact
Host=’HOST_01’
Managed=true
RestartMsg=’The Impact Server NCI has restarted.’
AlertMsg=’The Impact Server NCI has gone down.’
RetryCount=3
}

Managing an Installation
1.8 Managing an Installation

You manage an installation of Netcool/Impact using either command line scripts (on UNIX platforms) or
Windows-based management tools and applications (on Windows platforms). Netcool/Impact and the
Netcool Security Manager also provide web-based GUIs that you can use to perform administration tasks.
In addition, Netcool/Impact and its related components provide a variety of log files and other tools that
you can also use to monitor their status and troubleshoot problems.


Chapter 2: Netcool Common License Server
02_License_Server.fm December 15, 2004 10:29 am
This chapter contains information on the Netcool Common License Server 1.0b21.
• About the License Server on page 28

• System Requirements on page 31
• Licensing Architecture on page 32
• License Server Components on page 33
• Installing the License Server on page 36
• Installing Licenses on page 39
• Managing the License Server on UNIX on page 43
• Managing the License Server on Windows on page 45
• Using the FLEXlm Command Line Tools on page 47
• Quorum Licensing on page 48
• Uninstalling the License Server on page 51

2.1 About the License Server

This section contains overview information about the License Server.
• What Is the License Server?

• What Are the Supported Configurations?
• What Are the License Server Components?
• How Do I Set Up the License Server?
• How Do I Install Licenses?
• How Do I Run the License Server?
• Can I Run the License Server Under Process Control?
• How Do I Manage the License Server?
What Is the License Server?

The Netcool Common License Server is a standalone server component that provides licensing functionality
for Netcool/Impact and other products in the Netcool suite. The License Server is based on FLEXlm
licensing technology. FLEXlm is a product of Macrovision Corporation. Version 1.0b21 of the License
Server incorporates FLEXlm version 9.2.
You must install and configure a License Server before you run Netcool/Impact or the Netcool GUI Server.
You must also install licenses for Netcool/Impact and for the Security Manager before you run these
components. If you are already running a License Server in your environment, you do not need to install a
new one for use with Netcool/Impact.
The License Server is supported on all the platforms that are supported for Netcool/Impact and the Netcool
Security Manager. For more information, see System Requirements on page 31.
For more information on FLEXlm, see the FLEXlm End User’s Guide. This guide is available from the
Macrovision website at http://www.macrovision.com.
What Are the Supported Configurations?

Netcool/Impact 3.1, Netcool GUI Server 2.0 and Netcool Security Manager 1.2 support both single-server
and quorum configurations of the License Server. Previous versions of these components supported only
single-server configurations. For more information on quorum licensing, see Quorum Licensing on page 48.

About the License Server
What Are the License Server Components?

The License Server software consists of the licensing daemons (on UNIX platforms) or service (on Windows
platforms), license files and a collection of license tools that you can use to manage licensing in your
environment. For more information, see License Server Components on page 33.
How Do I Set Up the License Server?

Before you set up the License Server, you must first obtain the installation files from the Micromuse Product
CD-ROM or as a download from the Micromuse Technical Support website. The URL for the Micromuse
Technical Support website is http://support.micromuse.com. The installation files include the
License Server installer and a README file.
To install the License Server, you run the installer and follow the on-screen prompts. The installer sets all of
the required configuration properties. On UNIX platforms, you must set the required environment variables
after installation. You can view the installation log to see if the process has completed successfully.
For more information, see Installing the License Server on page 36.
How Do I Install Licenses?

Before you install licenses in the License Server, you must first generate the license host ID for the system
where the License Server is running. Then, you request a license file from Micromuse Technical Support.
To install the licenses, you copy the license file to the target system and request a license file refresh from the
License Server. For more information, see Installing Licenses on page 39.
How Do I Run the License Server?

On UNIX platforms, you start and stop the License Server using the server administration scripts. On
Windows platforms, you can use the Windows services administration tools or the LMTOOLS program.
For more information, see Managing the License Server on UNIX on page 43 and Managing the License Server
on Windows on page 45.
Can I Run the License Server Under Process Control?

You can run the License Server under process control with no special considerations. The License Server runs
by default as a foreground process. There is no need to pass the -z command line argument to the startup
script as in previous versions. The License Server runs as a “non-pa aware” application.

How Do I Manage the License Server?

The License Server provides a set of command line tools that allow you to manage licensing in your
environment. You can use these tools to view the License Server status, view license usage, refresh licenses
and perform other related tasks. On Windows platforms, you can also use the LMTOOLS program. This
program allows you to perform all of the management functionality provided by the command line tools.
For more information, see Managing the License Server on UNIX on page 43 and Managing the License Server
on Windows on page 45.

System Requirements
2.2 System Requirements

Make sure that the target system fulfills the requirements in this section before installing the License Server.
Platform Support
The License Server is supported on the following platforms:
• Sun Microsystems Solaris 7, 8 and 9

• Red Hat Linux 9.0 and Enterprise Server 3.0
• Microsoft Windows 2000 Server, Windows XP and Windows 2003 Server
• IBM AIX 5L (5.1 and 5.2)
• Hewlett-Packard HP-UX 11.00
Hardware Support
Hardware requirements for the License Server vary depending on your environment and license usage. For
recommendations on hardware sizing for the License Server, contact your Micromuse account manager or
Micromuse Technical Support.
Limitations
You can run only one FLEXlm-enabled Netcool license server per machine. This includes the Netcool
Common License Server, the Netcool/Impact 2.3 license server and the license server distributed with
Netcool/OMNIbus 3.5 and later.
Micromuse recommends that you use the most recent FLEXlm-enabled license server available. License files
are not backward compatible between versions.
Exceed Issues
Micromuse does not recommend the use of Hummingbird Exceed with the License Server installer program.
Under some conditions, the license agreement text displayed by the installer program is not legible when
viewed inside Exceed. You must read the full text of the license agreement and accept the terms of the
agreement before installing this software.

2.3 Licensing Architecture

The following figure shows the relationship between Netcool/Impact, other Netcool applications and the
License Server.
Netcool/RAD Netcool/OMNIbus
Netcool Common
License Server
Other Netcool Netcool/Impact

Applications
Figure 3: Netcool Licensing Architecture

License Server Components
2.4 License Server Components

The License Server has the following components:
• License server daemons (UNIX only)

• License server service (Windows only)
• License files
• Command line tools
• LMTOOLS (Windows only)
License Server Daemons (UNIX Platforms)

On UNIX platforms, the License Server has two daemons, the FLEXlm daemon and the vendor daemon.
These daemons provide the licensing functionality for the server.
The FLEXlm daemon is named lmgrd. It provides the primary interface to client applications (such as
Netcool/Impact and the Netcool Security Manager) and passes requests to check in and check out licenses
to the vendor daemon. The vendor daemon is named netcool. This daemon is responsible for the core
operations of the License Server.
You run the lmgrd and netcool daemons using the License Server script. You can also launch the
daemons manually from the command line, following instructions provided in the FLEXlm documentation.
License Server Service (Windows Platforms)

On Windows platforms, the License Server runs as a service named lmgrd.exe. This service provides the
primary interface to client applications (such as Netcool/Impact and the Netcool Security Manager) and
handles requests to check in and check out licenses.
You run the lmgrd.exe daemon using the Services Administration tools provided by Windows. You can
also run the service using the LMTOOLS program.
License Files
License files are text files that contain licenses for the License Server. The License Server supports an
unlimited number of license files. The default name for license files is license.lic. The License Server
recognizes any file with a name that ends in .lic as a license file. By default, license files are located in the
$NCLICENSE/etc directory.

License files contain the following elements:
• Server line
• Vendor line
• Feature lines
Server Line
The server line identifies the host system where the License Server is installed. The server line appears in the
license file in the following format:
SERVER host hostID port
where host is the hostname of the system, hostID is the license host ID for the server and port is the
port where you are running the License Server.
Vendor Line
The vendor line identifies the vendor providing the licenses. The vendor line appears in the license file in
the following format:
VENDOR netcool
Feature Lines
Feature lines are lines that contain information about each licensed component, including number of
licenses and the license expiration date. The license file contains one feature line for each licenseable Netcool
component or feature. Feature lines appear in the license file in the following format:
FEATURE feature netcool 3.1 exp_date number ck SIGN
where feature is a Netcool license feature code, exp_date is the expiration date for the licenses and
number is the number of licenses available. The ck and SIGN attributes are used by the License Server for
license validation.

License Server Components
Example License File

The following is an example of the contents of a license file:
SERVER localhost 80f34eb5 27000
VENDOR netcool
USE_SERVER
FEATURE cro_nci_server netcool 4.0 31-Dec-2005 2 ck=221 \

SIGN=A2D69708434E
FEATURE cro_nci_client netcool 4.0 31-Dec-2005 4 ck=199 \

SIGN=939730F86748
FEATURE cro_nci_eventbroker netcool 4.0 31-Dec-2005 2 ck=174 \

SIGN=30DC95B86230
FEATURE cro_nci_objserv_dsa netcool 4.0 31-Dec-2005 2 ck=185 \

SIGN=C39E61ACFE2D
FEATURE cro_nci_mysql_dsa netcool 4.0 31-Dec-2005 2 ck=200 \

SIGN=9C877EF420E2
Command Line Tools (UNIX Platforms)

The License Server provides a set of command line tools that allow you to manage licensing on UNIX
platforms. You can use these tools to view the server status, view license usage, refresh licenses and perform
other related tasks. These tools are located in the $NCLICENSE/bin directory. For more information, see
Managing the License Server on UNIX on page 43.
LMTOOLS (Windows Platforms)

On Windows platforms, the License Server provides a program called LMTOOLS that you can use to
manage licensing. You can use LMTOOLS to perform all of the management functionality provided by the
command line tools. You can also use LMTOOLS to start and stop the License Server. For more
information, see Managing the License Server on Windows on page 45.

2.5 Installing the License Server

To install the License Server, you do the following:
• Run the License Server installer

• Set the License Server environment variables (UNIX only)
• Verify firewall port settings
After you have finished installing the License Server, you can read the installation log to verify that the
software has been installed correctly, or to troubleshoot installation errors.
If you are already running the License Server in your environment, you do not need to create a separate
installation for use with Netcool/Impact.
Running the License Server Installer

The License Server installer copies the program files to the target system and sets the minimum required
configuration properties.
On UNIX platforms, the License Server is distibuted as a zipped tar file named license_ver.tar.gz,
where ver is the version and build number of the package. The installer is a script named
license_install. This script is located in the root level of the tar file. Micromuse recommends that
you do not install the License Server as user root. You can run the installer as any other user that has read,
write and execute permissions to the target directory.
On Windows platforms, the installer is a setup program named licensemgr.msi. You can run the
installer by double-clicking the program icon in Windows Explorer.
The License Server installer prompts you for the following information:
Table 4: Netcool Common License Server Installer Prompts
Prompt Description
Installation directory The directory where you want to install the License Server. On Solaris, Red Hat Linux, and HP-UX,
the default is /opt/netcool/common/license. On AIX, the default is
/usr/netcool/common/license. On Windows 2000, the default is
C:\Program Files\Netcool\Common\License.
Copy startup script You can choose whetherto copy a startup script into the init.d directory. This script
automatically restarts the License Server at system startup. UNIX only.

Installing the License Server
To run the License Server installer on UNIX platforms:
1. At a command line prompt, change the current directory to the directory where the install package is
located.
2. Enter the following:
tar -xvzf license_ver.tar.gz
where ver is the version and build number of the License Server.
3. Enter the following:
./license_install
4. Follow the on-screen prompts.
To run the License Server installer on Windows platforms:
1. Launch licensemgr.msi by double-clicking the file in Windows Explorer.

Setting the License Server Environment Variables

If you are installing the License Server on a UNIX platform, you must set the NCLICENSE and
NETCOOL_LICENSE_FILE environment variables.
NCLICENSE
The NCLICENSE variable specifies the location where you installed the License Server. On Solaris, HP-UX
and Red Hat Linux systems, the default location is /opt/netcool/common/license. On AIX
systems, the default location is /usr/netcool/common/license.
The following example shows how to set NCLICENSE using sh or bash:
NCLICENSE=/opt/netcool/common/license; export NCLICENSE
The following example shows how to set NCLICENSE using csh:
setenv NCLICENSE /opt/netcool/common/license

NETCOOL_LICENSE_FILE
The NETCOOL_LICENSE_FILE specifies the location of Netcool license files on your system. By default,
this location is $NCLICENSE/etc.
The following example shows how to set NETCOOL_LICENSE_FILE using bash or sh:
NETCOOL_LICENSE_FILE=$NCLICENSE/etc
The following example shows how to set NETCOOL_LICENSE_FILE using csh:
setenv NETCOOL_LICENSE_PATH $NCLICENSE/etc
Verifying Port Settings

If the License Server is seperated from Netcool/Impact, the GUI Server or the Security Manager by a
firewall, or you are running the License Server on a Windows machine with a built-in firewall, you should
check the port usage information in Firewall Considerations on page 166 to make sure that the configuration
allows access to the required ports.
Reading the Installation Log

The License Server installation log is named License_Manager_InstallLog.log and is located
in the $NCLICENSE directory. The installation log contains runtime messages generated during the
installation process. You can use this log to verify that you have installed the License Server successfully. You
can also use it to troubleshoot installation problems.

Installing Licenses
2.6 Installing Licenses

To install Netcool licenses, you do the following:
• Generate the license host ID

• Obtain the license feature codes
• Request the license file
• Copy the license file to the system
Generating the License Host ID

When you request a license file from Micromuse Technical Support, you must provide the license host ID
for the system where the License Server is running. The License Server installer automatically generates a
host ID and stores it in a file named hostid.out. This file is located in the $NCLICENSE/log
directory.
You can generate the host ID at any other time by running the nc_hostid script (UNIX platforms) or
the lmhostid command (Windows platforms). The nc_hostid script is located in the
$NCLICENSE/bin directory. The lmhostid command is located by default in the
C:\Program Files\netcool\common\license\bin directory.
Sample UNIX License Host ID

The following example shows sample output from the nc_hostid script:
nco_hostcode v1.04 (15-OCT-2002 11:20:01)
---OUTPUT-BEGIN---
Version: v1.04
Time: 1046691321
cksum: 0024dcf3
3b25306b35266925050112110401056820544f55783721100d0e1b07043c
5054575746504c50426b2b0616055d1b6d2a505d534c4357594c41554844
535363240b0c14160407166b2517194f02101545040704110e091411174f
020d1f6b362636253e42320f1516004f44516b2a4a52564452580d596d26
090904524851515241030745525a5a0a504f505d534c4357594c41554844
5353455c52564f5654575c53555a5c516c360d51594234595551514e015b
0e0c5f0d0f1b06471d541413001602144b4d075801110707001d5064240d
5b564d31485554525e125c1a0d46050709064d105b110200130104584a13
5918190f1500175d6b2944556b243b2f6c

Sample Windows Host ID

The following example shows sample output from the lmhostid command:
lmhostid - Copyright (C) 1989-2002 Macrovision Corporation
The FLEXlm host ID of this machine is "0001025191c4"
Obtaining License Feature Codes

When you request a license file from Micromuse Technical Support, you must provide the code for each
feature that you want to license.
Netcool/Impact License Feature Codes

The following table shows the license feature codes for Netcool/Impact.
Table 5: Netcool/Impact License Feature Codes (1 of 2)
Component Code
Netcool/Impact server cro_nci_server
Netcool/Impact client cro_nci_client
Event reader cro_nci_eventreader
Operator view cro_nci_opview
ObjectServer DSA cro_nci_objserv_dsa
LDAP DSA cro_nci_ldap_dsa
Oracle DSA cro_nci_oracle_dsa
MySQL DSA cro_nci_mysql_dsa
Microsoft SQL Server DSA cro_nci_freetds_dsa
Flat File DSA cro_nci_flatfile_dsa
Informix DSA cro_nci_informix_dsa
DB2 DSA cro_nci_db2_dsa
PostgreSQL DSA cro_nci_postgres_dsa
Sybase DSA cro_nci_sybase_dsa

Installing Licenses
Table 5: Netcool/Impact License Feature Codes (2 of 2)
Component Code
JMS DSA cro_nci_dsamediator_jmssda
Cramer Dimension DSA cro_nci_dsamediator_cramer
Vitria BusinessWare DSA cro_nci_dsamediator_vitria
XML DSA cro_nci_dsamediator_xml
XML DSA (XML Files) cro_nci_dsamediator_xmlfile
Portal Infranet DSA cro_nci_dsamediator_infranet
Granite Xpercom DSA cro_nci_dsamediator_granite
Metasolv DSA cro_nci_dsamediator_metasolv
SNMP DSA cro_nci_dsamediator_snmp
Telcordia DSA cro_nci_dsamediator_telcordia
Tibco TIB/Rendezvous DSA cro_nci_dsamediator_tibco
Web Services DSA cro_nci_webservice_dsa
For more information on licensing requirements for Netcool/Impact, see Upgrading Netcool/Impact on
page 91.
Netcool Security Manager License Feature Codes

The following table shows the license feature codes for the Netcool Security Manager.
Table 6: Netcool Security Manager License Feature Codes
Component Code
Netcool Security Manager cro_ncsm_server
For more information on licensing requirements for the Netcool Security Manager, see the Netcool Security
Manager Administration Guide.

Requesting the License File

To request a license file, send an e-mail to Micromuse Technical Support at
support@micromuse.com. You must attach the license host ID and the license feature codes to the
e-mail. After verifying your license request, Micromuse will reply with an e-mail that contains a license file
named license.lic.
Installing the License File

Copy the license file to the $NCLICENSE/etc directory. If a file named license.lic already exists,
give the license file a unique name with the .lic extension before copying. The License Server reads all
files in the $NCLICENSE/etc directory that have the .lic extension.

Managing the License Server on UNIX
2.7 Managing the License Server on UNIX

The License Server provides a set of command line scripts that you can use to manage licensing on UNIX
platforms. These scripts are located in the $NCLICENSE/bin directory. The scripts allow you to do the
following:
• Start the License Server

• View License Server status
• Refresh the License Server
• Stop the License Server
• View the license host ID
For complete syntax and sample output from the command line scripts, see the Netcool/Impact Reference
Guide.
Starting the License Server

To start the License Server on UNIX platforms, you run the nc_start_license script. This script
launches the License Server and causes it to read all of the license files located in the $NCLICENSE/etc
directory.
To run the nc_start_license script, enter the following at a command line prompt:
$NCLICENSE/bin/nc_start_license
Viewing License Server Status

To view the status of the License Server, you run the nc_print_license script. This script prints the
server status and information on license usage to the standard output.
To run the nc_print_license script, enter the following at a command line prompt:
$NCLICENSE/bin/nc_print_license
Refreshing the License Server

To refresh the License Server, you run the nc_read_license script. This script causes the server to
re-read all of the license files located in the $NCLICENSE/etc directory.
To run the nc_read_license script, enter the following at a command line prompt:
$NCLICENSE/bin/nc_read_license

Stopping the License Server

To stop the License Server, you run the nc_stop_license script.
To run the nc_stop_license script, enter the following at a command line prompt:
$NCLICENSE/bin/nc_stop_license
Viewing the License Host ID

The license host ID is a unique identifier used by the License Server to identify the system where it has been
installed. You use the host ID when you request licenses from Micromuse Technical Support.
To view the license host ID, you run the nc_hostid script.
To run the nc_hostid script, enter the following at a command line prompt:
$NCLICENSE/bin/nc_hostid

Managing the License Server on Windows
2.8 Managing the License Server on Windows

The License Server provides a program called LMTOOLS that you can use to manage licensing on Windows
platforms. LMTOOLS allows you to do the following:
• Start the License Server

• View License Server status
• Refresh the License Server
• Stop the License Server
• View the license host ID
Starting the License Server on Windows

To start the License Server:
1. Launch LMTOOLS from the Windows Start Menu.

2. Click the Start → Stop → Reread tab in the LMTOOLS window.
3. Click the Start Service button.
Viewing License Server Status on Windows

To view the status of the License Server and to view information on license usage:

2. Click the Server Status tab in the LMTOOLS window.
3. Click the Perform Status Enquiry button.
Refreshing the License Server on Windows

To cause the License Server to re-read the license files in the license path:

2. Click the Start → Stop → Reread tab.
3. Click the ReRead License File button.

Stopping the License Server on Windows

To start the License Server:

2. Click the Start → Stop → Reread tab in the LMTOOLS window.
3. Click the Stop Service button.
Viewing the License Host ID on Windows

To view the license host ID, you run the lmhostid command from any command prompt. By default,
this command is located in the C:\Program Files\netcool\common\license\bin
directory. You can use this license host ID when you request licenses from Micromuse Technical Support.

Using the FLEXlm Command Line Tools
2.9 Using the FLEXlm Command Line Tools

FLEXlm provides a set of command line tools that allow you to perform advanced administration tasks. The
command line tools are located in the $NCLICENSE/platform/arch/bin directory, where arch
is the name of the operating system where the License Server is installed.
FLEXlm provides the following command line tools:
Table 7: Netcool Common License Server Command Line Tools
Name Description
lmdiag Helps you diagnose problems with checking out licenses.
lmdown Stops the FLEXlm license daemon. Equivalent to nc_stop_license.
lmnewlog Starts a new log file.
lmpath Changes the license file path.
lmreread Refreshes the License Server. Equivalent to nc_read_license.
lmstat Shows the License Server status and license usage. Equivalent to nc_print_license.
lmswitch Switches to a new debug log file.
lmswitchr Switches to a new report log file.
lmver Prints the version number of FLEXlm components.
For complete instructions on running the command line tools, see the FLEXlm End User’s Guide. This
guide is available from the Macrovision website at
http://www.macrovision.com.

2.10 Quorum Licensing

This section contains information on quorum licensing.
• What Is Quorum Licensing?

• How Do I Set Up a Quorum?
• How Do I Configure Netcool/Impact Components to Use a Quorum?
What Is Quorum Licensing?

Quorum licensing is a configuration in which you install multiple License Servers and configure them to act
as a single server. This configuration provides failover functionality between server instances.
Quorum licensing requires exactly three instances of the License Server. Typically, you install these instances
on separate systems in your environment. You must install all instances of the License Server on systems
running the same operating system. The first instance of the License Server is called the primary instance.
The second and third instances are called secondary and tertiary instances.
How Do I Set Up a Quorum?

To set up a licensing quorum, you do the following:
• Install the License Server instances

• Request and install quorum license files
• Run the License Server instances
Installing License Server Instances

You can install the quorum License Server instances in the same way you install a standalone License Server.
There are no additional steps or special considerations.
Requesting and Installing Quorum License Files

When you request licenses from Micromuse Technical Support, you must specify that the licenses are for
use with a quorum configuration. You must also provide host IDs for each of the systems where you plan to
install the License Server.
When Micromuse processes your license request, it produces a single license file that you must install on all
instances of the License Server in the quorum. This license file specifies the hostnames of each of the license
servers and their status as primary, secondary and tertiary instances.

Quorum Licensing
The following example shows a typical quorum license file.

SERVER lic_host_01 80fda0b1 27000
SERVER lic_host_02 80fd3629 27000
SERVER lic_host_03 80fd4557 27000
VENDOR netcool
USE_SERVER
FEATURE cro_nci_client netcool 4.0 permanent 3 SIGN="0002 0A4A 0B3E \

C2D8 E512 0A21 619A DD00 DFC8 F26F 27EC AF6D D97C 8BA6 455B" \
SIGN2="00A7 6CE8 57FB 192D FC5B 52E2 B9DC 0800 F872 B9F6 E367 \
06E2 0C7F 2A17 BFC6"
FEATURE cro_nci_server netcool 4.0 permanent 3 SIGN="0016 7453 25FC \

DE2C 205E 6321 A77E 3700 8637 A47F 08E3 B3D5 E736 D5FD B94E" \
SIGN2="009A EBAB DA22 B1E7 2D92 DEB9 55A8 B500 6C3F EB88 26B1 \
F11D C16C 24E9 FA99"
FEATURE cro_nci_eventbroker netcool 4.0 permanent 3 SIGN="0003 DBEB \

5BCD D55D 82A7 DC98 8D53 FD00 3B01 2D4D F9E9 7C08 EB54 BB06 \
5BB0" SIGN2="00A5 C4BC 1664 4D0F 58DE 323B 0997 6600 25D7 D2FF \
8445 8C8B EF6B 03BB D490"
FEATURE cro_nci_eventreader netcool 4.0 permanent 3 SIGN="0004 1209 \

DCFF 45AD 6F8E 8725 B9C9 AB00 270A 95E9 13D7 EB6C 1705 FBA1 \
AF0B" SIGN2="0082 BF9C FE8E CF88 48F7 EE54 1B7A 4400 437B 4665 \
30E5 9365 CEC0 FBDB 72AE"
In this license file, lic_host_01 is the primary License Server instance, lic_host_02 is the
secondary instance and lic_host_03 is the tertiary instance.
Note: You must explicitly specify the port used by each License Server instance in the license file, regardless
of whether you are using the default port (27000) or another port.
Running the License Server Instances

You must start each of the License Server instances in the order specified in the license file. When you shut
down a single instance of the License Server using the nc_stop_license script or LMTOOLS, all other
instances in the quorum are also stopped automatically.
How Do I Configure Netcool/Impact Components to Use a Quorum?

To configure Netcool/Impact components to use the quorum, you manually edit the contents of each
license properties file so that they contain the hostnames and port numbers of the License Server instances.
You must configure Netcool/Impact, the Netcool GUI Server and the Netcool Security Manager.

The license properties file is named license.props and is located in the etc directory of each component
installation. For example, the Netcool/Impact license properties file is
$IMPACT_HOME/etc/license.props.
To edit the license properties file:
1. Remove all properties currently defined in the file. This includes the impact.license.host
and impact.license.port or license.host and license.port properties.
2. For the Netcool/Impact, add the following property to the file:
impact.license.server=port@host_01,port@host_02,port@host_03
For the Netcool GUI Server, add the following property to the file:
license.server=port@host_01,port@host_02,port@host_03
where host_01, host_02 and host_03 are the primary, secondary and tertiary instances of the
License Server and port is the port number used by the servers (by default, 27000). You must specify
the License Servers in the order that they appear in the license file.

Uninstalling the License Server
2.11 Uninstalling the License Server

This section contains information on uninstalling the License Server on UNIX and Windows platforms. If
you plan to reinstall the License Server, you should copy any license files to a safe location before
uninstalling. You must shut down the License Server before you attempt to uninstall.
Uninstalling on UNIX
When you install the License Server on UNIX platforms, all of the program files are copied to the
$NCLICENSE directory. You can safely uninstall the License Server by deleting this directory and all its
contents.
To uninstall the License Server, enter the following at a command line prompt:
rm -rf $NCLICENSE
Uninstalling on Windows
You can uninstall the License Server on Windows platforms by using the Add/Remove Programs tool in the
Windows Control Panel. This tool launches the License Server uninstaller, which deletes the program files
from the file system and removes License Server information from the Windows registry file.
To uninstall the License Server:
1. In the Start Menu, select Control Panel → Add/Remove Programs.

2. Select Netcool License Server from the list of installed applications and click Remove.
The Add/Remove Programs tool uninstalls the License Server.


Chapter 3: Netcool GUI Server
03_GUI_Server.fm December 15, 2004 10:15 am
This chapter contains information about the Netcool GUI Server 2.0.
• About the GUI Server on page 54

• GUI Server Components on page 58
• GUI Server Architecture on page 59
• Installing the GUI Server on page 60
• Licensing the GUI Server on page 63
• Running the GUI Server on page 65
• Configuring the GUI Server on page 66
• Registry Clustering on page 68
• GUI Server Logging on page 77
• Uninstalling the GUI Server on page 78

3.1 About the GUI Server

This section contains overview information about the Netcool GUI Server.
• What Is the GUI Server?

• How Do I Set Up the GUI Server?
• How Do I Run the GUI Server?
• Can I Run the GUI Server Under Process Control?
• How Do I Administer the GUI Server?
What Is the GUI Server?

The GUI Server is a standalone server application that hosts web-based graphical user interfaces for
Netcool/Impact and other products in the Netcool suite. You must install and configure the GUI Server
before you install Netcool/Impact.
The GUI Server consists of the Servlet Engine and the Netcool Application Registry. For more information,
see GUI Server Components on page 58.
How Do I Set Up the GUI Server?

Before you set up the GUI Server, you must first obtain the installation files from the Micromuse Product
CD-ROM or as a download from the Micromuse Support Site. The installation files include the Netcool
GUI Server installer and a README file.
To install the GUI Server, you run the installer program and follow the on-screen prompts. The installer
sets all of the required configuration properties. On UNIX platforms, you must set the required
environment variables after installation. The installer creates an installation log that you can view to see if
the process completed successfully.
After you have installed the GUI Server, you can change its configuration at any time by manually editing
its properties files.
For more information, see Installing the GUI Server on page 60.

About the GUI Server
How Do I License the GUI Server?

The GUI Server requires a Netcool/Impact client license for each user account that is used to access
Netcool/Impact via the web-based interface. You must obtain the required licenses and install them in your
license server before running Netcool/Impact as an application instance in the GUI Server. When you install
the GUI Server, you specify the hostname and port for this license server. For more information, see
Licensing the GUI Server on page 63.
How Do I Run the GUI Server?

On UNIX platforms, you start and stop the GUI Server using the administration scripts. On Windows
platforms, you start and stop the GUI Server using the Windows Services administration tools. For more
information, see Running the GUI Server on page 65.
Can I Run the GUI Server Under Process Control?

You can run the GUI Server under process control with no special considerations. The GUI Server runs as
a “non-pa aware” application.
How Do I Administer the GUI Server?

After you have started the GUI Server, it requires no additional real-time administration. To check the status
of the GUI Server, you can read the GUI Server log. For more information, see GUI Server Logging on
page 77.


Make sure that the target system fulfills the following requirements before installing the Netcool GUI
Server.
Platform Support
The GUI Server is supported on the following platforms:

• IBM AIX 5L (5.1 and 5.2)
Note: If you intend to install the GUI Server on a Linux platform, Micromuse recommends that you use
Red Hat Enterprise Server 3.0. Red Hat no longer officially supports version 9.0.
Java Support
The GUI Server requires version 1.4.x of the Java 2 Software Development Kit (J2SDK). On Solaris, Red
Hat Linux and Microsoft Windows platforms, the J2SDK is installed automatically when you install the
GUI Server.
You do not have to install the J2SDK independently of the software. On AIX and HP-UX platforms, you
must download and install a compatible version separately from the GUI Server. You can obtain the J2SDK
for AIX from the IBM website at http://www.ibm.com/java. You can obtain the J2SDK for
HP-UX from the Hewlett-Packward website at http://www.hp.com/products1/unix/java.
Note: On AIX and HP-UX platforms, you must download and install the entire J2SDK. Installing the Java
Runtime Environment (JRE) alone is not sufficient.
License Server Compatibility

The GUI Server is compatible with the Netcool Common License Server 1.0b21 or later.

System Requirements
Security Manager Requirements

The GUI Server requires Netcool Security Manager 1.1 or 1.2 for user authentication.
Web Browser Support

The Netcool/Impact GUI runs on the following web browsers:
• Microsoft Internet Explorer 5.5 and later

• Netscape 6 and later
• Mozilla 1.7 and later
Hardware Requirements
Hardware requirements for the GUI Server vary depending on your environment. For recommendations on
hardware sizing for the GUI Server, contact your Micromuse account manager or Micromuse Technical
Support.
Exceed Limitations
Micromuse does not recommend the use of Hummingbird Exceed with the GUI Server installer program.
Under some conditions, the license agreement text displayed by the installer program is not legible when
viewed inside Exceed. You must read the full text of the license agreement and accept the terms of the

3.3 GUI Server Components

The GUI Server has the following components:
• Servlet Engine
• Application Registry
Servlet Engine
The Servlet Engine is a runnable HTTP server application that hosts web-based Netcool user interfaces and
brokers requests between end users’ web browsers and Netcool applications. The Servlet Engine incorporates
Apache Tomcat servlet technology. The version of Tomcat used in the Servlet Engine is 4.1. For more
information, see the Tomcat website at http://jakarta.apache.org/tomcat.
Application Registry
The Netcool Application Registry is a component that provides application registration functionality to the
GUI Server. Netcool applications that use the GUI Server register with the Application Registry at startup.
The GUI Server uses the information stored in the registry when brokering HTTP requests between end
users’ web browsers and the applications. The registry is also used by Netcool/Impact and the Netcool
Security Manager to store information used in server clustering.
Note: The registry is a set of Java servlets that can be run in any J2EE servlet container. By default, the
registry is configured at installation to run in the servlet engine. You do not need to start and stop the registry
separately from the servlet container.

GUI Server Architecture
3.4 GUI Server Architecture

The following figure shows the Netcool GUI Server architecture.
Web
Browser
Internet o
r
Intranet
Netcool
GUI
Netcool/ Other
Server
Impact Netcool
Products
Netcool
Security
Manager
Figure 4: Netcool GUI Server Architecture

3.5 Installing the GUI Server

To install the GUI Server, you do the following:
• Install the Java Development Kit (AIX and HP-UX only)

• Run the GUI Server installer
• Set the GUI Server environment variables (UNIX platforms only)
After you have finished installing the GUI Server, you can read the installation log to verify that the software
has been installed correctly, or to troubleshoot installation errors.
Installing the Java Development Kit (AIX and HP-UX Only)

If you are installing the GUI Server on AIX or HP-UX, you must download and install a compatible version
of the Java 2 Development Kit (J2SDK) before you install the GUI Server. The GUI Server is compatible
with versions 1.4.x of the J2SDK. You must download and install the entire J2SDK. The JRE alone is not
sufficient.
You can download the J2SDK for AIX from the IBM website at http://www.ibm.com/java. You
can download the J2SDK for HP-UX from the Hewlett-Packard website at
http://www.hp.com/products1/unix/java.
Running the GUI Server Installer

The GUI Server installer copies the program files to the target system and sets the minimum required
configuration properties. The installer is named guiserverbuildarch.bin, where build is the
build number of the software and arch is the name of the operating system.
You can run the installer in GUI mode or in console mode. In GUI mode, the installer presents a series of
graphical dialog boxes that guide you through the installation process. In console mode, the installer
prompts you for required information from the command line. If you are installing the GUI Server remotely
using telnet or another command line application, you must run the installer in console mode.
Micromuse recommends that you do not install the GUI Server as the root user. You can run the installer
as any other user that has read, write and execute permissions to the target directory.

Installing the GUI Server
The GUI Server installer prompts you for the following information:
Table 8: Netcool GUI Server Installer Prompts
Prompt Description
Installation directory Directory where you want to install the GUI Server. Default is /opt/netcool/guiserver
on UNIX platforms and C:\Program Files\Netcool\Guiserver on Windows.
Application Registry Directory where you want to install the Netcool Application Registry.
directory
Shutdown port Shutdown port used internally by the Servlet Engine. Default is 8005.
HTTP port HTTP port used by the Servlet Engine. When you log into Netcool/Impact or the Security
Manager via a web browser, you use this HTTP port. Default is 8080.
Security Manager host Hostname or IP address of the system where the Netcool Security Manager is located. Default
is localhost.
Security Manager port Port used by the Security Manager. Default is 8077.
License Server host Hostname or IP address of the system where the License Server is running. Default is localhost.
License Server port Port used by the License Server. Default is 27000.
Java home directory Home directory of the J2SDK installed on the file system. AIX and HP-UX installs only.
Note: By default, the installer configures the GUI Server to install and use a single instance of the Netcool
Application Registry. If you want to set up a registry cluster, you must perform the additional steps described
in Registry Clustering on page 68.
To run the GUI Server installer:
1. At a command line prompt, change the current directory to the directory where the installer is
located.
2. To run the installer in GUI mode, enter the following:
./guiserver.bin
To run the installer in console mode, enter the following:
./guiserver.bin -i console

Setting the GUI Server Environment Variables

If you are installing the GUI Server on a UNIX platform, you must set the GUI_HOME environment
variable to the directory where you installed the application. By default, this directory is
opt/netcoool/guiserver.
The following example shows how to set GUI_HOME using sh or bash:
GUI_HOME=/opt/netcool/guiserver; export GUI_HOME
The following example shows how to set GUI_HOME using csh:
setenv GUI_HOME /opt/netcool/guiserver

If the GUI Server is seperated from Netcool/Impact, the Security Manager or the License Server by a
firewall, or you are running the GUI Server on a Windows machine with a built-in firewall, you should

The GUI Server installation log is named Netcool_GUI_Server_2.0_Install_Log.log and is
located in the $GUI_HOME directory. The installation log contains runtime messages generated during the
installation process. You can use this log to verify that you have installed the GUI Server successfully. You
can also use it to troubleshoot installation problems.

Licensing the GUI Server
3.6 Licensing the GUI Server

This section contains information on licensing the GUI Server.
It contains information on:
• Licensing requirements
• Configuring licensing
• Quorum licensing
Licensing Requirements
The GUI Server requires a Netcool/Impact client license for each user account that is used to access
Netcool/Impact via the web-based interface. You must obtain the required licenses and install them in your
license server before running Netcool/Impact as an application instance in the GUI Server. The license
feature code for client licenses is nci_client.
Configuring Licensing
Licensing properties are located in the license properties file. This file is named license.props and is
located in the $GUI_HOME/etc directory. The licensing properties are set automatically when you install
the GUI Server. However, you can manually edit the license properties file at any time to change the
configuration. If you manually edit the properties file, you must stop and restart the GUI Server before the
change takes effect.
The following table shows the license properties for the GUI Server:
Table 9: Netcool GUI Server License Properties
Property Description
license.server.host Hostname or IP address of the license server to be used by the GUI Server. Default is
localhost.
license.server.port Port of the license server to be used by the GUI Server. Default is 27000.
Quorum Licensing
To use the GUI Server with a quorum licensing configuration, you muse manually edit the contents of the
license properties file so that it contains the hostnames and port numbers of the License Server instances.

1. Remove all properties currently defined in the file. This includes the license.host and
license.port properties.
2. Add the following property to the file:
license.server=port@host_01,port@host_02,port@host_03
License Server and port is the port number used by the servers (by default, 27000). You must specify
the License Servers in the order that they appear in the license file.
For more information on quorum licensing, see Quorum Licensing on page 48.

Running the GUI Server
3.7 Running the GUI Server

This section contains information on starting and stopping the GUI Server on UNIX and Windows
platforms.
Starting the GUI Server on UNIX

You start the GUI Server by running the startup script. This script is named ncgui_server and is
located in the $GUI_HOME/bin directory.
To start the GUI Server, enter the following at a command prompt:
$GUI_HOME/bin/ncgui_server
Stopping the GUI Server on UNIX

You stop the GUI Server by running the shutdown script. This script is named ncgui_shutdown and
is located in the $GUI_HOME/bin directory.
To stop the GUI Server, enter the following at a command prompt:
$GUI_HOME/bin/ncgui_shutdown
Starting the GUI Server on Windows

To start the GUI Server:
1. In the Start Menu, select Control Panel / Administrative Tools / Services.

2. In the Services window that opens, right-click on Netcool GUI Server and select Start.
Stopping the GUI Server on Windows

To stop the GUI Server:
1. In the Start Menu, select Control Panel / Administrative Tools / Services.

2. In the Services window that opens, right-click on Netcool GUI Server and select Stop.

3.8 Configuring the GUI Server

You can configure GUI Server components at any time after installation by manually editing their properties
files. You must stop and restart the GUI Server in order for configuration changes to take effect.
Configuring Authentication
Authentication properties for the GUI Server are located in the server properties file. This file is named
server.props and is located in the $GUI_HOME/etc directory.
The following table shows the authentication properties for the GUI Server.
Table 10: Netcool GUI Server Authentication Properties
security.host Hostname or IP address of the system where the Security Manager is located.
security.port Port used by the Security Manager.
Configuring the Servlet Engine

Configuration properties for the Servlet Engine are located in the servlet properties file. This file is named
server.xml and is located in the $GUI_HOME/etc directory. This properties file contains
information in XML format for the Tomcat servlet technology incorporated into the GUI Server. You
should only modify this file under the supervision of Micromuse Technical Support.
For more information on the servlet properties file, see the Apache Tomcat documentation at
http://jakarta.apache.org/tomcat.
Configuring the Registry

The configuration properties for the Netcool Application Registry are located in the registry properties file.
This file is named registry.props and is located in the $GUI_HOME/etc directory.
Table 11 shows the registry properties for Netcool/Impact:
Table 11: Netcool/Impact Registry Properties (1 of 2)
Propery Description
impact.registry.userid Registry login username. Maintained for backward compatibility only.

Default is admin.

Configuring the GUI Server
Propery Description
impact.registry.password Registry login password. Maintained for backward compatibility only.

Default is netcool.
impact.registry.count Number of registry instances in the cluster.
impact.registry.#.host Hostname of the registry instance, where # is an index value that

identifies the registry instance.
impact.registry.#.port Port used, where # is an index value that identifies the registry instance.
This is the HTTP port used by the GUI Server or Tomcat, which have
8080 as defaults.
impact.registry.#.location URL location on servlet container where registry is installed, where # is

an index value that identifies the registry instance. Default is
/registry/services.
For more information on registry properties, see Registry Clustering on page 68.

3.9 Registry Clustering

This section contains information on registry clustering.
• What Is Registry Clustering?

• What Are the Clustering Components?
• How Do I Set Up Registry Clustering?
• How Do I Run the Registry Cluster?
• How Does Registry Clustering Work?
• How Do I View Registry Status?
What Is Registry Clustering?

Clustering is a feature that allows you to install multiple instances of the Netcool Application Registry and
configure them to provide failover capability. Clustering prevents the registry from acting as a single point
of failure in a Netcool/Impact installation.
What Are the Clustering Components?

A registry cluster consists of a primary registry and one or more secondary registries.
The primary registry is the component responsible for communicating in real time with Netcool
components like Netcool/Impact, the Netcool GUI Server and the Netcool Security Manager. It stores
information about which instances of these components are running and where they are located on the
network.
The secondary registries are responsible for providing failover functionality for the primary registry. They
do not communicate with the Netcool applications in real time, except in the case that the primary registry
fails and a secondary registry assumes the role of the primary.

Registry Clustering
How Do I Set Up Registry Clustering?

To set up registry clustering, you do the following:
• Install two or more instances of a J2EE servlet container on systems in your environment
• Install the registry in the J2EE container applications
• Configure the registry
• Configure the Netcool applications that use the registry (for example, Netcool/Impact, the Netcool
GUI Server and the Netcool Security Manager)
Installing J2EE Servlet Containers

The first step in setting up clustering is to install two or more instances of a J2EE servlet container on systems
in your environment. You can run the registry with any J2EE servlet container. Supported containers
include the Netcool GUI Server and the standalone Tomcat server. Micromuse recommends that you use
Tomcat for scenarios in which you require a lightweight, easily-configurable platform for the registry.
For more information on Tomcat, see http://jakarta.apache.org/tomcat.
Installing the Registries

The next step in setting up clustering is to install the registry in each J2EE servlet container.
You install the registry using the standard GUI Server installer. The installer prompts you whether to install
the GUI Server, the registry or both. If you are installing for use with Tomcat, choose to install the registry
as a standalone component.
During installation, you must specify the directory where you want the registry to reside. If you are installing
the registries for use with the GUI Server, this path must be $GUI_HOME/app3p/tomcat/webapps.
If you are installing for use with Tomcat, this path must be $CATALINA_HOME/webapps, where
$CATALINA_HOME is the directory where Tomcat is installed.
Configuring the Registries

Clustering configuration properties for the registry instances are located in the web.xml file. For the GUI
Server this file is in the $GUI_HOME/app3p/tomcat/webapps/registry/WEB-INF directory.
For Tomcat, this file is in the $CATALINA_HOME/webapps/registry/WEB-INF directory.
To configure the registry instances, you must edit the web.xml file so that it contains a set of property
settings for each registry in the cluster. Each registry must be configured in the exact same way.

Table 12 shows the clustering properties:
Table 12: Registry Clustering Properties
REPLICANT.COUNT Number of registries in the cluster.
REPLICANT.#.HOST Hostname of the registry instance, where # is an index value that identifies the
registry instance.
REPLICANT.#.PORT Port used, where # is an index value that identifies the registry instance. This is
the HTTP port used by the GUI Server or Tomcat, which have 8080 as defaults.
REPLICANT.#.LOCATION URL location on servlet container where registry is installed, where # is an index
value that identifies the registry instance. This is the directory you specified
when you installed the registry. Default is /regsitry/services.
SELFINDEX Index value that identifies this registry cluster. You must specify index values as a
series, starting with zero.
PERSIST_ENABLED Specifies whether the registry should cache its state information to disk at
shutdown and read cached information at startup. Can be true or false.
Micromuse recommends settings this property to true, which is the default.
PERSIST_PATH Specifies the directory where state information is cached. Default is

$GUI_HOME/webapps/registry.

Registry Clustering
The following example shows typically settings for these properties in a clustering scenario with three registry
instances:
<context-param>
<param-name>REPLICANT.COUNT</param-name>
<param-value>3</param-value>
</context-param>
<context-param>
<param-name>REPLICANT.HOST</param-name>
<param-value>registry_host_01</param-value>
</context-param>
<context-param>
<param-name>REPLICANT.PORT</param-name>
</context-param>
<context-param>
<param-name>REPLICANT.LOCATION</param-name>
<param-value>/registry/services</param-value>
</context-param>
<context-param>
</context-param>
<context-param>
</context-param>
<context-param>
</context-param>
<context-param>
</context-param>
<context-param>
</context-param>
<context-param>
</context-param>
<context-param>
<param-name>SELFINDEX</param-name>
</context-param>

Configuring the Netcool Applications

After you have configured the registry instances, you must configure Netcool/Impact, the Netcool GUI
Server, the Netcool Security Manager and any other Netcool components that use the registry cluster.
Registry configuration properties for Netcool components are located in the registry.props file. This
file is located in the etc directory of the component installation. This directory is $IMPACT_HOME/etc
for Netcool/Impact, $GUI_HOME/etc for the GUI Server and $NCSM_HOME/etc for the Netcool
Security Manager.
As with the clustering properties in the web.xml file, you must specify a set for each registry in the cluster.
Note: Property names differ depending on whether you are configuring Netcool/Impact or you are
configuring another component. Registry properties for Netcool/Impact begin with the
impact.registry prefix. Registry properties for other components begin with the registry prefix.
See the default values in the registry.props file for each component to view property names in the
correct format.
Table 13: Netcool/Impact Registry Clustering Properties
Propery Description

Default is admin.

Default is netcool.
impact.registry.#.host Hostname of the registry instance, where # is an index value that identifies
the registry instance.
This is the HTTP port used by the GUI Server or Tomcat, which have 8080
as defaults.
impact.registry.#.location URL location on servlet container where registry is installed, where # is an

index value that identifies the registry instance. Default is
/registry/services.

Registry Clustering
Table 14 shows the registry properties for the GUI Server and the Security Manager:
Table 14: Netcool GUI Server and Netcool Security Manager Clustering Properties
Propery Description
registry.userid Registry login username. Maintained for backward compatibility only. Default
is admin.
registry.password Registry login password. Maintained for backward compatibility only. Default is
netcool.
registry.count Number of registry instances in the cluster.
registry.#.host Hostname of the registry instance, where # is an index value that identifies the
registry instance.
registry.#.port Port used, where # is an index value that identifies the registry instance. This is
the HTTP port used by the GUI Server or Tomcat, which have 8080 as defaults.
registry.#.location URL location on servlet container where registry is installed, where # is an index
value that identifies the registry instance. Default is /registry/services.

The following example shows a typical registry.props file for Netcool/Impact:

impact.registry.userid=admin
impact.registry.password=netcool
impact.registry.count=3
impact.registry.0.host=192.168.1.120
impact.registry.0.port=8888
impact.registry.0.location=/registry/services
The following example shows a typical registry.props file for the GUI Server or Security Manager:
impact.registry.userid=admin
impact.registry.password=netcool
impact.registry.count=3
How Do I Run a Registry Cluster?

To run a registry cluster, start each J2EE servlet container where the registry is installed. You can start the
servlet container applications in any order. The command to start Tomcat is
$CATALINA_HOME/bin/startup.sh. If registry instances are part of a GUI Server installation, you
can start the instances using the standard GUI Server startup script. This script is called ncgui_server
and is located in the $GUI_HOME/bin directory.

Registry Clustering
How Does Registry Clustering Work?

The clustering process has the following phases:
• Startup
• Runtime
• Command Replication
• Failure and Recovery
• Shutdown
Startup
At startup, each registry cluster member reads the ordered cluster member list and its position on that list
from its web.xml file. The registry stores this information internally and uses it to determine its behavior
during runtime.
Runtime
During runtime, the cluster member queries the other cluster members at intervals to determine their status
and to synchronize registry data between them.
Command Replication
When you start and stop Netcool/Impact and the Netcool Security Manager, they issue registration and
un-registration commands to the registry cluster members. When a cluster member receives such a
command, it does one of the following:
• If the member is the primary registry instance, it will execute the command and then publish the
command to every other registry in the cluster. The other registries then execute the command and
update their registration information.
• If the member is not the primary registry instance, it forwards the command to the primary without
executing it. The primary then executes the command as described above.
Failure and Recovery

When a cluster member fails, the other members detect the failure during normal runtime operation. Once
a failure has been detected, the other members update their clustering information and do not attempt to
synchronize data with the failed member. When a cluster member recovers, the other members detect the
recovery and notify it that it needs to re-synchronize its registry data.

Shutdown
When you shut down a cluster member, it determines whether to save its registry information to disk by
reading the PERSIST_ENABLED property in the web.xml file. If PERSIST_ENABLED is set to true, it
saves its registry information in the directory specified by the PERSIST_PATH property. This information
is then read by the cluster member at startup.
How Do I View Registry Status?

The GUI Server provides a web-based tool that you can use to view the status of registry instances. This tool
displays the currently-defined registry instances and whether they are running or stopped. The URL of this
tool is http://host:port/registry/services, where host is the hostname of the system
where the GUI Server is installed and port is the GUI Server port.

GUI Server Logging
3.10 GUI Server Logging

On UNIX platforms, GUI Server log files are located in the $GUI_HOME/log directory. On Windows
platforms, the files are located in the %GUI_HOME%\app3p\tomcat\logs directory.
The GUI Server provides the following log files:
Table 15: GUI Server Log Files
Log File Description
netcoolguiserver.log Used by programs that run as application instances in the GUI Server
(for example, Netcool/Impact and the Netcool Security Manager).
localhost_registry_timestamp.log Used by the Application Registry, where timestamp reflects the time
the GUI Server was started.
localhost_log.timestamp.txt Used to record messages generated by the default GUI context.
You can set properties in the web.xml file to provide additional logging information for the Netcool
Application Registry. Table 16 shows the logging properties in web.xml.
Table 16: Application Registry Logging Properties
ENABLE_GENERAL_LOGGING Enables general logging output from the registry.
ENABLE_REQUEST_LOGGING Enables logging of requests and responses sent and received by the
registry.
ENABLE_PING_LOGGING Enalbes logging of ping messages sent to other registry instances at

intervals.

3.11 Uninstalling the GUI Server

This section contains information on uninstalling the GUI Server on UNIX and Windows platforms. You
must shut down the GUI Server before you attempt to uninstall.
When you install the GUI Server on UNIX platforms, all of the program files are copied to the
$GUI_HOME directory. You can safely uninstall the GUI Server by deleting this directory and all its
contents.
To uninstall the GUI Server, enter the following at a command line prompt:
rm -rf $GUI_HOME
Uninstalling on Windows
You uninstall the GUI Server on Windows platforms by running the uninstaller batch file. This batch file
is named uninstall.bat and is located by default in the
C:\Program Files\netcool\guiserver\UninstallerData directory.
To uninstall the GUI Server, enter the following at a command prompt:

cd C:\Program Files\netcool\guiserver\UninstallerData
uninstall.bat

Chapter 4: Netcool/Impact
04_Impact.fm December 15, 2004 10:15 am
This chapter contains information on Netcool/Impact.
• About Netcool/Impact on page 80

• Netcool/Impact Components on page 85
• Netcool/Impact Architecture on page 87
• Installing Netcool/Impact on page 88
• Upgrading Netcool/Impact on page 91
• Licensing Netcool/Impact on page 95
• Configuring Registry Settings on page 98
• Configuring Authentication on page 99
• Backing Up and Restoring Netcool/Impact on page 100
• Uninstalling Netcool/Impact on page 101

4.1 About Netcool/Impact

This section contains overview information about Netcool/Impact.
• What Is Netcool/Impact?
• What Are the Netcool/Impact Components?
• How Do I Set Up Netcool/Impact?
• How Do I License Netcool/Impact?
• How Do I Configure Netcool/Impact?
• How Do I Manage Netcool/Impact?
What Is Netcool/Impact?
Netcool/Impact is the analysis and correlation engine for the Netcool suite of network management
products. Netcool/Impact allows you to extensively customize and enhance Netcool/OMNIbus and other
Netcool products by adding such functionality as advanced event and business data correlation, event
enrichment and event notification. In addition, you can use Netcool/Impact to integrate
Netcool/OMNIbus with a wide variety of third party software, including databases, messaging systems and
network inventory applications.
What Are the Netcool/Impact Components?

Netcool/Impact has the following components:
• Netcool/Impact server
• Netcool/Impact database
• Netcool/Impact DSAs
• Netcool/Impact CVS
• Netcool/Impact JRExec server
• Netcool/Impact Operator View
• Netcool/Impact GUI
For more information, see Netcool/Impact Components on page 85

About Netcool/Impact
How Do I Set Up Netcool/Impact?

Before you set up Netcool/Impact, you must first obtain the installation files from the Micromuse Product
CD-ROM or as a download from the Micromuse Technical Support website. The URL for the Micromuse
Technical Support website is http://support.micromuse.com. The installation files include the
Netcool/Impact installer and a README file.
To install Netcool/Impact, you run the installer and follow the on-screen prompts. The installer sets all of
the required configuration properties. On UNIX platforms, you must set the required environment variables
after installation. The installer creates an installation log that you can view to see if the process completed
succesfully.
After you have installed Netcool/Impact, you can change its configuration at any time by manually editing
its properties files.
For more information, see Installing Netcool/Impact on page 88.
How Do I License Netcool/Impact?

Netcool/Impact requires the following licenses:
• Netcool/Impact server license

• Netcool/Impact client licenses
• Netcool/Impact Operator View licenses
• Netcool/Impact event reader license
• Netcool/Impact DSA licenses
You must obtain the required licenses and install them in your license server before running Netcool/Impact.
When you install Netcool/Impact, you specify the host and port for this license server.
For more information, see Upgrading Netcool/Impact on page 91.
How Do I Configure Netcool/Impact?

Netcool/Impact provides two sets of properties files. The global properties files control configuration
settings for all instances of the Netcool/Impact server in a configuration. The server properties files control
configuration settings for each instance of the Netcool/Impact server.

How Do I Manage Netcool/Impact?

Netcool/Impact provides a web-based GUI and a telnet-enabled CLI that you can use to perform all of the
required administration tasks. You can also use these tools to manage other aspects of Netcool/Impact, such
as data types, policies and services. Netcool/Impact also provides a set of logs that you can read to view the
status of components or to troubleshoot problems.

System Requirements

Make sure that the target system fulfills the following requirements before installing Netcool/Impact.
Platform Support
Netcool/Impact 3.1 is supported on the following platforms:

• IBM AIX 5L (5.1 and 5.2)
Note: If you intend to install Netcool/Impact on a Linux platform, Micromuse recommends that you use
Red Hat Enterprise Server 3.0. Red Hat no longer officially supports version 9.0.
Java Support
Netcool/Impact 3.1 requires version 1.4.x of the Java 2 Runtime Environment (JRE). The JRE is installed
automatically when you install Netcool/Impact. You do not need to install the JRE independently.
License Server Compatibility

Netcool/Impact 3.1 is compatible with the Netcool Common License Server 1.0b21 or later.
Security Manager Requirements

Netcool/Impact 3.1 requires Netcool Security Manager 1.1 or 1.2 for user authentication.
GUI Server Requirements

Netcool/Impact 3.1 requires version 2.0 of the Netcool GUI Server.

Web Browser Support

The Netcool/Impact GUI runs on the following web browsers:
• Microsoft Internet Explorer 5.5 and later

• Netscape 6 and later
• Mozilla 1.7 and later
Netcool/OMNIbus Support
Netcool/Impact 3.1 supports Netcool/OMNIbus versions 3.5, 3.6, and v7.
Hardware Requirements
Hardware requirements for Netcool/Impact vary depending on your environment. For recommendations
on hardware sizing for Netcool/Impact, contact your Micromuse account manager or Micromuse Technical
Support.
Exceed Limitations
Micromuse does not recommend the use of Hummingbird Exceed with the Netcool/Impact installer
program. Under some conditions, the license agreement text displayed by the installer program is not legible
when viewed inside Exceed. You must read the full text of the license agreement and accept the terms of the

Netcool/Impact Components
4.3 Netcool/Impact Components

Netcool/Impact has the following components:
• Netcool/Impact server
• Netcool/Impact database
• Netcool/Impact DSAs
• Netcool/Impact JRExec server
• Netcool/Impact Operator View
Netcool/Impact Server
The Netcool/Impact server is the primary component of Netcool/Impact. It consists of a collection of
sub-components, called services, that perform the core functionality of the product. It also provides the
mechanisms for creating and managing a Netcool/Impact data model and for creating and managing
Netcool/Impact policies. In addition, the Netcool/Impact server hosts the web-based GUI.
On UNIX platforms, the Netcool/Impact server is a runnable application that you can start and stop using
the server administration scripts. On Windows platforms, the Netcool/Impact server runs as a Windows
service that you can start and stop using the Windows Services Administration tools.
Netcool/Impact Database
The Netcool/Impact database is a customized and pre-configured version of PostgreSQL. Netcool/Impact
uses this database to store information related to its internal reporting features. You can also use this database
as a built-in SQL database data source.
On UNIX platforms, the Netcool/Impact database is started and stopped automatically when you start and
stop Netcool/Impact. You do not have to run the database independently of the Netcool/Impact server. On
Windows platforms, the database runs as a Windows service that you can start and stop using the Windows
Services Administration tools.
For more information, see Chapter 8: Netcool/Impact Database on page 125.

Netcool/Impact DSAs
Netcool/Impact Data Source Adaptors (DSAs) provide the interface between Netcool/Impact and external
data sources. Netcool/Impact has a wide variety of DSAs that allow you to integrate SQL databases, LDAP
directory services and many third party applications with your Netcool installation.
Netcool/Impact CVS
Netcool/Impact CVS is a customized version of the Concurrent Versions System (CVS). Netcool/Impact
CVS is installed automatically when you install Netcool/Impact. You can use this version of CVS to provide
version control functionality to Netcool/Impact, or you can use an alternate system.
Netcool/Impact JRExec Server

The Netcool/Impact JRExec server is a server component that allows Netcool/Impact to run external
commands, scripts and applications from within a policy. You must start and stop the JRExec server
independently of the Netcool/Impact Server. On UNIX platforms, the JRExec server is a runnable server
application that you start using the JRExec server script. On Windows platforms, the JRExec server runs as
a Windows service that you can start and stop using the Windows Services Administration tools.
Netcool/Impact Operator View

The Netcool/Impact Operator View is a web-based tool that you can use to launch policies and view their
results from within Netcool/OMNIbus and other applications. You create and manage the Operator View
using the Netcool/Impact GUI.
Netcool/Impact GUI
The Netcool/Impact GUI is a web-based graphical user interface that you can use to manage
Netcool/Impact data sources, data types, policies and services. You can also use the GUI to view performance
data about Netcool/Impact and to design Netcool/Impact Operator Views. The Netcool/Impact User
Interface Guide contains complete instructions using the Netcool/Impact GUI.

Netcool/Impact Architecture
4.4 Netcool/Impact Architecture

The following figure shows the architecture of Netcool/Impact and its components.
Netcool/
Impact Netcool/
GUI Impact
DSAs
Netcool/
Impact
Netcool/ Netcool/
Impact Impact
Database CVS
Netcool/
Impact
JRExec
Server
Figure 5: Netcool/Impact Architecture

4.5 Installing Netcool/Impact

To install Netcool/Impact, you do the following:
• Configure the operating system kernel (UNIX only)

• Run the Netcool/Impact installer
• Set the Netcool/Impact environment variables (UNIX only)
After you have finished installing Netcool/Impact, you can read the installation log to verify that the
software has been installed correctly, or to troubleshoot installation errors.
Configuring the Operating System Kernel (UNIX Only)

If you plan to use the Netcool/Impact reporting features on a UNIX platform, you must first configure the
operating system kernel so that the shared memory settings fulfill the requirements of the Netcool/Impact
database.
The Netcool/Impact database requires a maximum shared memory setting of at least 32 MB. Micromuse
recommends 64 MB. If you are running Netcool/Impact on the same machine as the Security Manager, you
must also increase the shared memory setting to accomodate the Security Manager database.
For more information, see UNIX Kernel Configuration on page 167.
Running the Netcool/Impact Installer

The Netcool/Impact installer copies the program files to the target system and sets the minimum required
configuration properties. The installer is named impactbuildarch.bin., where build is the build
number and arch is the name of the operating system.
You can run the installer in GUI mode or in console mode. In GUI mode, the installer presents a series of
graphical dialog boxes that guide you through the installation process. In console mode, the installer
prompts you for required information from the command line. If you are installing Netcool/Impact
remotely using telnet or another command line application, you must run the installer in console mode.
You cannot run the installer as user root. You can run the installer as any other user that has read, write and
execute permissions to the target directory.

Installing Netcool/Impact
The Netcool/Impact installer prompts you for the following information:
Table 17: Netcool/Impact Installer Prompts
Prompt Description
Installation directory Directory where you want to install the Security Manager. Default is /opt/netcool/impact
on UNIX platforms and C:\Program Files\Netcool\Impact on Windows.
Version control Specifies which version control system to use with Netcool/Impact. Default is Netcool/Impact
system CVS, which is installed automatically with the product.
License server host Hostname or IP address of the license server to be used by the Security Manager. Default is
localhost.
License server port Port of the license server to be used by the Security Manager. Default is 27000.
Registry host Hostname or IP address of the system where the Netcool Application Registry is running. By
default, the Application Registry is installed on the same system as the GUI Server.
Registry port Port used to communicate with the Application Registry. Default is 8080. This port is the same as
the HTTP port used by the Netcool GUI Server.
PostgreSQL port Port to be used by the Netcool/Impact Database.
Note: By default, the installer configures Netcool/Impact to use a single instance of the Netcool Application
Registry. If you want to set up a registry cluster, you must perform the additional steps described in Registry
Clustering on page 68.
To run the Netcool/Impact installer:
1. At a command line prompt, change the current directory to the directory where the installer is
located.
2. To run the installer in GUI mode, enter the following:
./impactbuildarch.bin
To run the installer in console mode, enter the following:
./impactbuildarch.bin -i console
During installation, the installer asks you if you want to create a new instance of the Netcool/Impact server.
If you answer yes, the installer launches the nci_new_server program. The installer always launches
nci_new_server in GUI mode. If you want to create the server instance in console mode, you must
launch nci_new_server separately. For more information , see Creating Server Instances on page 106.

Setting the IMPACT_HOME Environment Variable

If you are installing Netcool/Impact on a UNIX platform, you must set the IMPACT_HOME environment
variable to the directory where you installed the application. By default, this directory is
/opt/netcool/impact.
The following example shows how to set IMPACT_HOME using sh or bash:
IMPACT_HOME=/opt/netcool/impact; export IMPACT_HOME
The following example shows how to set IMPACT_HOME using csh:
setenv IMPACT_HOME /opt/netcool/impact

If Netcool/Impact is seperated from the GUI Server, the Security Manager or the License Server by a
firewall, or you are running Netcool/Impact on a Windows machine with a built-in firewall, you should

The Netcool/Impact installation log is named Netcool_Impact_3.1_InstallLog.log and is
located in the $IMPACT_HOME directory. The installation log contains runtime messages generated during
the installation process. You can use this log to verify that you have installed Netcool/Impact successfully.
You can also use it to troubleshoot installation problems.

Upgrading Netcool/Impact
4.6 Upgrading Netcool/Impact

This section contains information on upgrading Netcool/Impact from previous versions.
• Upgrading from Netcool/Impact 3.0

• Upgrading from Netcool/Impact 2.3
Upgrades from versions previous to Netcool/Impact 2.3 are not supported.
Upgrading from Netcool/Impact 3.0

To upgrade from Netcool/Impact 3.0, you perform the following steps:
• Install Netcool/Impact 3.1

• Create a new instance of the Netcool/Impact server
• Start the new instance of the Netcool/Impact server
• Export data from Netcool/Impact 3.0
• Manually export project data from Netcool/Impact 3.1 (optional)
• Import data into Netcool/Impact 3.1
Installing Netcool/Impact 3.1

The first step in upgrading from version 3.0 is to install Netcool/Impact 3.1 on the target system. If the
target is the same system as the one where Netcool/Impact 3.0 is installed, make sure that you install into a
separate directory.
Note: Do not attempt to install in the same directory as an existing Netcool/Impact 3.0 installation.
For instructions on installing Netcool/Impact 3.1, see Installing Netcool/Impact on page 88. You can install
the application to upgrade with no special considerations.
Creating a New Server Instance

After installing Netcool/Impact 3.1, you must create a new server instance with the same name and same
cluster name as the instance you are upgrading from version 3.0. You can create this server instance following
the instructions in Creating Server Instances on page 106.

Starting the New Server Instance

Once you have created the new server instance, you can start it using the server startup script. This script is
named nci_server and is located in the $IMPACT_HOME/bin directory. For more information on
starting server instances, see Running Server Instances on UNIX on page 107 or Running Server Instances on
Windows on page 108.
Exporting Data from Netcool/Impact 3.0

The next step in upgrading is to run the export command from the Netcool/Impact 3.0 installation
directory. The Netcool/Impact 3.0 server must be running when you run this command. The export
command is named nci_export and is located in $IMPACT_HOME/bin directory.
The export script extracts data source, data type, service and policy information from the Netcool/Impact
server and stores it in a directory you specify.
Manually Exporting Project Data from Netcool/Impact 3.0

Netcool/Impact 3.0 projects are not automatically exported by the nci_export script. If you want to
re-use version 3.0 projects in the new installation, you must manually export them.
To export projects from the version 3.0 installation:
1. Create a subdirectory of the directory where you exported data in the previous step. This directory
must be named Projects.
2. Manually copy the project list file from the version 3.0 installation into the directory you created.
This file is named servername_projectlist, where servername is the name of the
Netcool/Impact server instance. Then, rename the file to projectlist, omitting the
servername prefix.
3. Each version 3.0 project has an associated project definition file named
servername_projname.proj, where servername is the name of the Netcool/Impact
server instance and projname is the name of the project. Copy each project file into the directory
you created and rename the file to omit the servername prefix.
You do not need to manually import the project data into the version 3.1 installation. The project files are
imported automatically when you run the import script.
Importing Data into Netcool/Impact 3.1

After you have exported the data from Netcool/Impact 3.0, you can then import it into the version 3.1
installation.

Upgrading Netcool/Impact
To import the data, you must copy the directory created by the export script to a location on the file system
accessible to the Netcool/Impact 3.1 installation. Then, you run the import script and specify the location
of this directory. The import script inserts the extracted data source, data type, service and policy
information into the specified version 3.1 server instance. The import command is named nci_import
and is located in the $IMPACT_HOME/bin directory.
After you have imported the the data, you must stop and restart the Netcool/Impact 3.1 server instance.
Upgrading from Netcool/Impact 2.3

To upgrade from Netcool/Impact 2.3, you do the following:
• Stop the Netcool/Impact 2.3 server

• Install Netcool/Impact 3.1 components
• Start the Netcool GUI Server
• Run the Netcool/Impact 3.1 upgrade script
• Start Netcool/Impact 3.1
Note: Netcool/Impact 3.1 only supports CVS for version control after upgrading from version 2.3. If you
want to use another version control system, you must use a completely new installation of Netcool/Impact.
Stopping the Netcool/Impact 2.3 Server

Before you upgrade to Netcool/Impact 3.1, you must stop the version 2.3 server.
You can stop the server by running the shutdown script. This script is named nci_shutdown and is
located in the $IMPACT_HOME/bin directory.
To stop the server, enter the following at a command prompt:

$IMPACT_HOME/bin/nci_shutdown server_name
where server_name is the name of the Netcool/Impact server instance.
Installing the Netcool/Impact 3.1 Components

After you have stopped the version 2.3 server, you can install the Netcool/Impact 3.1 components. At
minimum, you must install the Security Manager, GUI Server and Netcool/Impact at this time.
Note: Do not attempt to install in the same directory as an existing Netcool/Impact 3.0 installation.

Starting the Netcool GUI Server

After you have installed the Netcool/Impact 3.1 components, you must start the GUI Server. The upgrade
script requires the Netcool Application Registry to be running. The Application Registry is installed and run
by default with the GUI Server. You can start the GUI Server using the server startup script. This script is
named ncgui_server and is located in the $GUI_HOME/bin directory.
Running the Netcool/Impact 3.1 Upgrade Script

The upgrade script creates a new Netcool/Impact 3.1 server instance using the configuration properties from
the specified Netcool/Impact 2.3 server. The upgrade script is named nci_upgrade and is located in the
version 3.1 $IMPACT_HOME/upgrade directory.
The upgrade script prompts you for the following information:
Table 18: Netcool/Impact Upgrade Script Prompts
Prompt Description
Version 2.3 installation directory Directory on the system where version 2.3 of Netcool/Impact is installed.
Version 2.3 server name. Name of the version 2.3 server instance that you want to upgrade.
Security Manager host. Hostname or IP address where the Netcool Security Manager is located.
Security Manager port Port where the Security Manager is running.
Version control system. Version control system to be used by version 3.1 of Netcool/Impact.
Starting Netcool/Impact 3.1

After you have run the upgrade script, you can start the new Netcool/Impact 3.1 server instance. This
instance has the same name as in version 2.3.
To start the server instance, enter the following at a command prompt:

$IMPACT_HOME/bin/nci_server server_name
where server_name is the name of the Netcool/Impact 3.1 server instance.

Licensing Netcool/Impact
4.7 Licensing Netcool/Impact

This section contains information on licensing Netcool/Impact.
It contains information on:
• Licensing requirements
• Configuring licensing
• Quorum licensing
Licensing Requirements
Netcool/Impact requires the following licenses:
• Netcool/Impact server license

• Netcool/Impact client licenses
• Netcool/Impact event reader licenses
• Netcool/Impact operator view licenses
• Netcool/Impact DSA licenses
Netcool/Impact Server License

Netcool/Impact requires a license for each instance of the Netcool/Impact server. The license feature code
for the server is cro_nci_server.
Netcool/Impact Client Licenses

Netcool/Impact requires a client license for each user concurrently logged into Netcool/Impact using the
web-based GUI or the CLI. The license feature code for the clients is cro_nci_client.
Netcool/Impact Event Reader Licenses

Netcool/Impact requires an event reader license for each event reader used in the Netcool/Impact server.
The license feature code for the event reader is cro_nci_eventreader.
Netcool/Impact Operator View Licenses

Netcool/Impact requires an Operator View license for each concurrent instance of the Operator view. The
license feature code for the Operator View is cro_nci_opview.

Netcool/Impact DSA licenses

Netcool/Impact requires a DSA license for each DSA used per instance of the Netcool/Impact Server.
The following table shows the license feature codes for Netcool/Impact DSAs:
Table 19: Netcool/Impact DSA License Feature Codes (1 of 2)
Component Code
ObjectServer DSA cro_nci_objserv_dsa
LDAP DSA cro_nci_ldap_dsa
Oracle DSA cro_nci_oracle_dsa
MySQL DSA cro_nci_mysql_dsa
Microsoft SQL Server DSA cro_nci_freetds_dsa
Flat File DSA cro_nci_flatfile_dsa
Informix DSA cro_nci_informix_dsa
DB2 DSA cro_nci_db2_dsa
PostgreSQL DSA cro_nci_postgres_dsa
Sybase DSA cro_nci_sybase_dsa
JMS DSA cro_nci_dsamediator_jmssda
Cramer Dimension DSA cro_nci_dsamediator_cramer
Vitria BusinessWare DSA cro_nci_dsamediator_vitria
XML DSA cro_nci_dsamediator_xml
XML DSA (XML Files) cro_nci_dsamediator_xmlfile
Portal Infranet DSA cro_nci_dsamediator_infranet
Granite Xpercom DSA cro_nci_dsamediator_granite
Metasolv DSA cro_nci_dsamediator_metasolv
SNMP DSA cro_nci_dsamediator_snmp
Telcordia DSA cro_nci_dsamediator_telcordia

Licensing Netcool/Impact
Table 19: Netcool/Impact DSA License Feature Codes (2 of 2)
Component Code
Tibco TIB/Rendezvous DSA cro_nci_dsamediator_tibco
Web Services DSA cro_nci_webservice_dsa
Configuring Licensing
Licensing properties are located in the license properties file. This file is named license.props and is
located in the $IMPACT_HOME/etc directory. The licensing properties are set automatically when you
install Netcool/Impact. However, you can manually edit the license properties file at any time to change the
configuration. If you manually edit the properties file, you must stop and restart the Netcool/Impact server
before the change takes effect.
The following table shows the license properties for Netcool/Impact:
Table 20: Netcool Security Manager License Properties
license.server.host Hostname or IP address of the license server to be used by the Netcool/Impact. Default is
localhost.
license.server.port Port of the license server to be used by the Netcool/Impact. Default is 27000.
Quorum Licensing
To use Netcool/Impact with a quorum licensing configuration, you must manually edit the contents of the
license properties file so that it contains the hostnames and port numbers of the License Server instances.
1. Remove all properties currently defined in the file. This includes the license.host and
license.port properties.
2. Add the following property to the file:
impact.license.server=port@host_01,port@host_02,port@host_03
License Server and port is the port number used by the servers (by default, 27000).
For more information on quorum licensing, see Quorum Licensing on page 48.

4.8 Configuring Registry Settings

Netcool/Impact uses the Netcool Application Registry to store information used in server clustering. The
Application Registry is a component of the Netcool GUI Server.
Registry settings are located in the registry properties file. This file is named registry.props and is
located in the $IMPACT_HOME/etc directory. The required registry properties are set automatically
when you install Netcool/Impact. You can change the registry configuration at any other time by modifying
the properties in this file. You must stop and restart the Netcool/Impact server for the changes to take effect.
Table 21: Netcool/Impact Registry Clustering Properties
Propery Description

Default is admin.

Default is netcool.

This is the HTTP port used by the GUI Server or Tomcat, which have
8080 as defaults.
impact.registry.#.location URL location on servlet container where registry is installed, where # is

an index value that identifies the registry instance. Default is
/registry/services.
For more information on working with the Netcool Application Registry, see Chapter 3: Netcool GUI Server
on page 53.

Configuring Authentication
4.9 Configuring Authentication

Netcool/Impact uses the Netcool Security Manager for authentication. When you install Netcool/Impact,
it inserts a role named ImpactUser into the Security Manager database. You must assign this role to each
Security Manager user who requires access to the Netcool/Impact GUI. For more information on working
with users and roles, see the Netcool Security Manager Administration Guide.

4.10 Backing Up and Restoring Netcool/Impact

To completely back up a Netcool/Impact installation, you can tar or zip the entire $IMPACT_HOME
directory and archive it for future access. This ensures that all parts of the installation, including properties
files and all other configuration data, are preserved. For timed backups of Netcool/Impact, tar or zip the
$IMPACT_HOME directory as a cron job.
To restore the installation, untar or unzip the archive and move the contents to the $IMPACT_HOME
directory.
Note that you can partially back up Netcool/Impact using the nci_export command. However, this
command does not export all of the properties files and other configuration data used by Netcool/Impact.

Uninstalling Netcool/Impact
4.11 Uninstalling Netcool/Impact

This section contains information on uninstalling the Netcool/Impact on UNIX and Windows platforms.
You must shut down Netcool/Impact before you attempt to uninstall.
When you install Netcool/Impact on UNIX platforms, all of the program files are copied to the
$IMPACT_HOME directory. You can safely uninstall the Netcool/Impact by deleting this directory and all
its contents.
To uninstall the Netcool/Impact, enter the following at a command line prompt:
rm -rf $IMPACT_HOME
Uninstalling on Windows Platforms

You uninstall Netcool/Impact on Windows platforms by running the uninstaller batch file. This batch file
is named uninstall.bat and is located by default in the
C:\Program Files\netcool\impact\UninstallerData directory.
To uninstall the Netcool/Impact, enter the following at a command prompt:

cd C:\Program Files\netcool\impact\UninstallerData
uninstall.bat


Chapter 5: Netcool/Impact Server
05_Impact_Server.fm December 15, 2004 10:15 am
This chapter contains information about the Netcool/Impact server.
• About the Netcool/Impact Server on page 104

• Creating Server Instances on page 106
• Running Server Instances on UNIX on page 107
• Running Server Instances on Windows on page 108
• Monitoring Server Instances on page 109
• Deleting Server Instances on page 110

5.1 About the Netcool/Impact Server

This section contains overview information about the Netcool/Impact server.
• What Is the Netcool/Impact Server?

• What Are the Supported Server Configurations?
• What Is a Server Instance?
• How Do I Set Up a Server Instance?
• How Do I Run a Server Instance?
• How Do I Monitor a Server Instance?
What Is the Netcool/Impact Server?

The Netcool/Impact Server is the primary component of Netcool/Impact. It consists of a collection of
sub-components, called services, that perform the core functionality of the product. It also provides the
mechanisms for creating and managing a Netcool/Impact data model and for creating and managing
Netcool/Impact policies. In addition, the Netcool/Impact server hosts the web-based GUI.
On UNIX platforms, the Netcool/Impact Server is a runnable application that you can start and stop using
the server administration scripts. On Windows platforms, the Netcool/Impact Server runs as a Windows
service that you can start and stop using the Windows Services Administration tools.
What Are the Supported Server Configurations?

Netcool/Impact supports both single server and clustered server configurations. Single server configurations
consist of a single instance of the Netcool/Impact Server installed on a single system in your environment.
Clustered server configurations consist of multiple instances of the Netcool/Impact Server installed on
different systems and configured to act as a single server. Clustered server configurations provide backup,
replication and load balancing functionality to Netcool/Impact.
For more information, see Chapter 6: Netcool/Impact Server Clustering on page 111.
What Is a Server Instance?

A server instance is a runnable instance of the Netcool/Impact server. You can run a single or multiple server
instances from a single Netcool/Impact directory. You must create a new instance of the server before you
can run Netcool/Impact in your environment.

About the Netcool/Impact Server
Micromuse recommends that you run a single server instance per system. However, it is possible to run
multiple instances for testing and validation purposes. There is typically no benefit to running multiple
instances of the Netcool/Impact server on a single system in a production environment.
How Do I Set Up a Server Instance?

You can create an instance of the Netcool/Impact server using the nci_new_server program. This
program prompts you for the minimum required configuration properties. You can change the
configuration at any time by manually editing the server properties file. For more information, see Creating
Server Instances on page 106.
How Do I Run a Server Instance?

On UNIX platforms, you start and stop server instances from the command line using the server
administration scripts. On Windows platforms, you run server instances as Windows services. For more
information, see Running Server Instances on UNIX on page 107 and Running Server Instances on Windows
on page 108.
How Do I Monitor a Server Instance?

You can monitor a server instance by viewing the server log. For more information, see Monitoring Server
Instances on page 109.

5.2 Creating Server Instances

To create a new server instance, you run the new server script. This script is named nci_new_server
and is located in the $IMPACT_HOME/install directory.
The new server script creates the set of properties files and other supporting files that define the instance.
These files are created in the $IMPACT_HOME/etc directory.
The new server script prompts you for the following information:
Table 22: Netcool/Impact New Server Script Prompts
Prompt Description
Instance name Name of the new instance. Default is NCI.
Cluster name Name of the server cluster for the new instance. If you are not using server clustering, enter
the instance name. Otherwise, enter the name of the cluster that the instance will participate
in.
Command line port Port used by the command line service for the new instance.
ObjectServer host Hostname or IP address for the primary ObjectServer in your environment.
ObjectServer port Port used by the ObjectServer.
Impact HTTP port Port used by the HTTP service for Netcol/Impact. Default is 5104.
SMTP host Host to be used by the e-mail sender service.
E-Mail sender name Name of the user associated with the e-mail sender service.
Version control system Specifies which version control system to use with Netcool/Impact. Default is Netcool/Impact
CVS, which is installed automatically with the product.
To create a server instance:
1. Enter the following at a command line prompt:

$IMPACT_HOME/install/nci_new_server

Running Server Instances on UNIX
5.3 Running Server Instances on UNIX

This section contains information on starting and stopping Netcool/Impact on UNIX platforms.
Starting Netcool/Impact on UNIX

You start a server instance by running the Netcool/Impact server startup script. This script is named
nci_server and is located in the $IMPACT_HOME/bin directory.
To start a server instance, enter the following at a command prompt:
$IMPACT_HOME/bin/nci_server server
where server is the name of the Netcool/Impact server instance.
Stopping Netcool/Impact on UNIX

You stop a server instance by running the Netcool/Impact server shutdown script. This script is named
nci_shutdown and is located in the $IMPACT_HOME/bin directory. You can only stop server
instances that are running from the $IMPACT_HOME directory. You cannot use nci_shutdown to stop
remote members of a server cluster.
To stop a server instance, enter the following at a command prompt:
$IMPACT_HOME/bin/nci_shutdown server

5.4 Running Server Instances on Windows

This section contains information on starting and stopping Netcool/Impact on UNIX platforms.
Starting Netcool/Impact on Windows

To start Netcool/Impact:
1. In the Start Menu, select Control Panel→Administrative Tools→Services.

2. In the Services window that opens, right-click on Netcool Impact Server and select Properties. In the
Properties dialog box, click Start and then click OK.
Stopping Netcool/Impact on Windows

To stop Netcool/Impact:

2. In the Services window that opens, right-click on Netcool Impact Server and select Properties. In the
Properties dialog box, click Stop and then click OK.

Monitoring Server Instances
5.5 Monitoring Server Instances

You can monitor instances of the Netcool/Impact server by reading the server log files. The server log files
contain messages and other information that can help you track the status of the server and troubleshoot any
problems that might arise. Server log files are named servername_server.log.n, where
servername is the name of the server instance and n is a number that identifies the log file. The server
log files are located in the $IMPACT_HOME/log directory.

5.6 Deleting Server Instances

To delete a server instance, you do the following:
• Run the remove server script

• Run the remove CVS archives script (optional)
Running the Remove Server Script

The remove server script removes the server instance from the Netcool/Impact installation. This script is
named nci_removeserver and is located in the $IMPACT_HOME/bin directory. The script checks
to see if the server instance is running before removing it from the installation. If the instance is running,
the script automatically shuts it down before continuing with operations.
To run the remove server script, enter the following at a command prompt:
$IMPACT_HOME/bin/nci_removeserver server_name
where server_name is the instance of the server you want to remove.
Running the Remove CVS Archives Script

By default, the remove server script does not delete information on policies, data sources, data types and
services from the version control system. If you are using CVS as your version control system, you can run
the remove CVS archives script to completely remove all archives related to a server instance. The remove
CVS archives script is named nci_cvs_remove and is located in the $IMPACT_HOME/bin directory.
To run the remove CVS archives script, enter the following at a command prompt:
$IMPACT_HOME/install/nci_cvs_remove server_name
where server_name is the name of the deleted server instance.

Chapter 6: Netcool/Impact Server Clustering
06_Server_Clustering.fm December 15, 2004 10:15 am
This chapter contains information about Netcool/Impact server clustering.
• About Server Clustering on page 112

• Clustering Components on page 113
• How Server Clustering Works on page 114
• Setting Up a Server Cluster on page 116
• Running a Server Cluster on page 119

6.1 About Server Clustering

This section contains overview information about Netcool/Impact server clustering.
• What Is Server Clustering?

• What Are the Clustering Components?
• How Does Clustering Work?
• How Do I Set Up a Server Cluster?
What Is Server Clustering?

Server clustering is a feature of Netcool/Impact that allows you to install a group of related Netcool/Impact
servers and configure them to operate as a single server instance. You use this feature to add failover and
load-balancing functionality to a Netcool/Impact installation.
Server clustering replaces the failover functionality provided in versions 2.3 and earlier of Netcool/Impact.
The previous functionality is no longer supported in Netcool/Impact 3.1.
What are the Clustering Components?

A Netcool/Impact server cluster consists of the primary server, which is responsible for monitoring the
Netcool/OMNIbus ObjectServer and making events available to secondary cluster members, and secondary
servers. Both primary and secondary servers are responsible for processing the events. Secondary servers do
not connect directly to the ObjectServer. For more information, see Clustering Components on page 113.
How Does Clustering Work?

For information on the server clustering process, see How Server Clustering Works on page 114.
How Do I Set Up Server Cluster?

To set up a server cluster, you install a separate instance of Netcool/Impact on each target system. When you
run the installer program, you specify the same cluster name for each server in the cluster. You can configure
cluster members in the same way you configure single server configurations of Netcool/Impact. Changes
made to the server configuration using the Netcool/Impact GUI are propagated automatically to other
cluster members. Manual changes made to the server properties files are not automatically propagated. For
more information, see Setting Up a Server Cluster on page 116.

Clustering Components
6.2 Clustering Components

A server cluster consists of the following:
• Primary server
• Secondary servers
Primary Server
The primary server is the cluster member that is reponsible for monitoring the Netcool/OMNIbus
ObjectServer and for making events available to the secondary servers for processing, as well as processing
events on its own. The first cluster member that is started automatically becomes the primary server. If the
primary server fails or is shut down, one of the secondary servers automatically becomes the primary.
Secondary Servers
Secondary servers are cluster members that are responsible for retrieving events from the primary server and
for executing policies in response to the incoming events. Secondary servers function solely as
event-processing services in the cluster.
Most services are disabled in the secondary servers. The following services are not disabled:
• Event processor
• Basic servlet service
• Policy logger
• Self-monitoring service

6.3 How Server Clustering Works

Server clustering has the following phases:
• Startup
• Event Monitoring
• Event Processing
• Failover
• Shutdown
Startup
At startup, each server communicates with the Netcool Application Registry. If no other cluster member is
currently registered, it registers itself as the primary server. If a primary server is already registered, it declares
itself a secondary server. By default, each secondary server synchronizes its services, data types, data sources,
policies and configuration settings with the primary server before becoming active.
Event Monitoring
During the event monitoring phase, the primary server queries the ObjectServer at intervals for new and
updated events, and (optionally) receives notification from the ObjectServer when an event is deleted. The
primary server places the incoming events in an event queue and waits for requests from the secondary
servers for event processing. Secondary servers do not query the ObjectServer at any time.
Event Processing
During the event processing phase, each secondary server queries the primary server for events to process.
The minimum interval and maximum number of events to retrieve per query are specified in the event
processor properties file. Similarly, the primary server requests events from its own event queue. For each
retrieved event, the server runs the corresponding policy, dependent on the filter conditions specified in the
event broker. After all the events have been processed, the secondary server queries the primary server again
for new events.
Failover
The secondary servers ping the primary at intervals during runtime. This assures the secondary servers that
the primary is active and functioning.

How Server Clustering Works
If the primary server fails, the first secondary server to become aware of the failure contacts the Netcool
Application Registry and registers itself as the new primary. When the original primary server is restarted, it
becomes another secondary server. If a secondary server fails, there is no impact on the other servers in the
cluster.
Shutdown
If the primary server is manually shut down, the first secondary server to become aware of the failure contacts
the Netcool Application Registry and registers itself as the new primary, as in the failover phase above. If a
secondary server is shut down, there is no impact on the other servers in the cluster.

6.4 Setting Up a Server Cluster

To set up a server cluster, you do the following:
• Install the cluster

• Configure the cluster
Installing a Server Cluster

To install a server cluster, you install a separate instance of the Netcool/Impact server on each target system.
The Netcool/Impact installer prompts you for the cluster name, which is used to identify the members of
the server cluster at startup in the Netcool Application Registry. All servers in a cluster must have the same
cluster name. This name can be any unique identifying string.
Configuring a Server Cluster

The Netcool/Impact installer prompts you for the name of the server cluster during installation. You can set
other configuration options manually at any time. You must stop and restart the Netcool/Impact server
instance in order for any changes to take effect.
Note that configuration changes are propagated from the primary server to the secondary servers. Changes
made to secondary server instances are not propagated back to the primary.
Setting Registry Properties

Properties related to the Netcool Application Registry are located in the registry properties file. This file is
named registry.props and is located in the $IMPACT_HOME/etc directory.
Table 23 shows the registry properties for Netcool/Impact
Propery Description

Default is admin.

Default is netcool.


Setting Up a Server Cluster
Propery Description
This is the HTTP port used by the GUI Server or Tomcat, which have 8080
as defaults.
impact.registry.#.location URL location on servlet container where registry is installed, where # is an

index value that identifies the registry instance. Default is
/registry/services.
For more information on registry properties, see Configuring the Registry on page 66.
Setting Server Properties

Properties related to server clustering are located in the server properties file. This file is named
servername_server.props, where servername is the name of the server instance The server
properties file is located in the $IMPACT_HOME/etc directory.
The following table shows the server clustering properties:
Table 24: Server Clustering Properties (1 of 2)
Name Description Default
impact.cluster.name Name of the server cluster. NCICLUSTER
impact.cluster.pinginterval Interval in milliseconds at which to ping 6000

other cluster members.
impact.cluster.pingtimeout Time in milliseconds to wait before 6000

retrying ping.
impact.cluster.repingcount Number of times to retry ping if the first 3

fails.
impact.cluster.resyncbeforestandby Specifies whether the server synchronizes true

data with the primary at startup before
becoming active.
impact.replication.receiveupdates.for. Specifies whether to synchronize the true

OrgNodes OrgNode cache.
impact.replication.receiveupdates.for. Specifies whether to synchronize true

Hibernations hibernations.
impact.replication.receiveupdates.for. Specifies whether to synchronize service true

ServiceStates states.

Table 24: Server Clustering Properties(Continued) (2 of 2)
Name Description Default
impact.replication.receiveupdates.for. Specifies whether to synchronize data true

Types types.
impact.replication.receiveupdates.for. Specifies whether to synchronize policies. true

ActionTrees
impact.replication.statusinterval Interval at which servers synchronize data. 0

Running a Server Cluster
6.5 Running a Server Cluster

You start and stop cluster members in the same way you start and stop another other instances of the
Netcool/Impact server.
Starting a Cluster Member

You start a cluster member using the server startup script. This script is named nci_server and is located
in the $IMPACT_HOME/bin directory.
To start the Netcool/Impact server, enter the following at a command prompt:
$IMPACT_HOME/bin/nci_server name
where name is the name of the server instance. The default is NCI.
Stopping a Cluster Member

You stop the Netcool/Impact server using the server shutdown script. This script is named
nci_shutdown and is located in the $IMPACT_HOME/bin directory.
To stop the Netcool/Impact server, enter the following at a command prompt:
$IMPACT_HOME/bin/nci_shutdown name
where name is the name of the server instance. The default is NCI.


Chapter 7: Netcool/Impact Version Control
07_Version_Control.fm December 15, 2004 10:15 am
This chapter contains information about Netcool/Impact version control.
• About Version Control on page 122

• How Version Control Works on page 123
• Configuring Version Control on page 124

7.1 About Version Control

Netcool/Impact provides a version control interface that allows you to save Netcool/Impact policies, data
sources, data types and configuration properties as revisions in a source control archive. This interface
supports the following version control systems:
• External CVS
• RCS
• ClearCase
Netcool/Impact CVS is a customized version of the Concurrent Revision System that has been prepared for
use with Netcool/Impact. This version of CVS is installed automatically when you install Netcool/Impact
and is used as the default version control system. If you want to use ClearCase, RCS or another version of
CVS, you must install and configure it before installing Netcool/Impact.
Version control is enabled for Netcool/Impact by default and cannot be disabled.

How Version Control Works
7.2 How Version Control Works

The version control process has the following phases:
• Element creation
• Check out
• Check in
• Element deletion
• Element renaming
Element Creation
Element creation occurs when you create a new policy, data source or data type using the Netcool/Impact
GUI or CLI. In CVS and RCS, Netcool/Impact creates a new archive file named filename,v, where
filename is the name of the policy script file. In ClearCase, Netcool/Impact creates a new element in the
revision database.
Check Out
Check out occurs when you open an existing policy, data source, data type or properties file. At check out,
Netcool/Impact checks out and locks the most recent revision in the version control system. When an
element is locked, the locked icon appears in the Netcool/Impact GUI. Only the user who has currently
checked out the element can modify it.
Check In
Check in occurs when you save a policy. At check in, Netcool/Impact checks the corresponding file in as a
new revision and removes the lock.
Element Deletion
Element deletion occurs when you delete a policy, data source or data type using the Netcool/Impact GUI
or CLI. At element deletion, Netcool/Impact completely removes the entire element or archive from the
version control system, including all revisions.
Element Renaming
Element renaming occurs when you rename a policy, data source or data type using the Netcool/Impact
GUI or CLI. When you rename an element, Netcool/Impact creates a new element using the new name in
the version control system. The old element with the previous name is not deleted.

7.3 Configuring Version Control

You can change the version control configuration at any time after you have installed Netcool/Impact by
manually editing the version control properties file. This file is named
server_versioncontrol.props, where server is the name of the instance of the Netcool/Impact
server. This file is located in $IMPACT_HOME/etc directory.
The following table shows the version control configuration properties:
Table 25: Version Control Configuration Properties
impact.versioncontrol.systemid Integer that represents the type of version control system.
impact.versioncontrol.debug Reserved for internal use.
impact.versioncontrol.path Path to the version control executable (CVS and RCS only)
impact.versioncontrol.cvs.cvsroot Location of the version control archive (CVS only)

Chapter 8: Netcool/Impact Database
08_Database.fm December 15, 2004 10:15 am
This chapter contains information about the Netcool/Impact database.
• About the Database on page 126

• Configuring the Database on page 128
• Running the Database on page 129
• Managing the Database on page 130

8.1 About the Database

This section contains general information about the Netcool/Impact database.
• What is the Database?

• How Do I Set Up the Database?
• How Do I License the Database?
• How Do I Run the Database?
• How Do I Manage the Database?
• Cygwin Limitations
What is the Database?

The Netcool/Impact database is a specially configured version of PostgreSQL that has been prepared for use
with Netcool/Impact. Netcool/Impact uses the database to store the underlying data used by the GUI
reporting tools. You can also use the database as a local SQL database data source.
Netcool/Impact uses one instance of the database for each installation. If you are running multiple instances
of the Netcool/Impact server from one directory on a system, all of the instances will use the same
Netcool/Impact database. If you are running them from multiple directories, each instance will use the
Netcool/Impact database installed in $IMPACT_HOME.
Micromuse recommends that you run the Netcool/Impact database only if you are using the GUI reporting
tools or require a local SQL database data source for use with Netcool/Impact. If you do not plan to use the
database for this functionality, you do not need to run the database.
For more information on PostgreSQL, see the official PostgreSQL documentation. The HTML version of
the documentation is distributed with Netcool/Impact and is located in the
$IMPACT_HOME/platform/arch/pgsql/doc/html directory, where arch is the name of the
operating system platform.
How Do I Set Up the Database?

The database is installed automatically when you install Netcool/Impact. The home directory for the
database is $IMPACT_HOME/platform/arch/pgsql, where arch is the name of the local
operating system.

About the Database
How Do I License the Database?

Netcool/Impact requires a PostgreSQL DSA license in order to access the database. The license feature code
for the PostgreSQL DSA is nci_postgresql_dsa. Generally, you request this license when you
request other Netcool/Impact licenses from Micromuse Technical Support. For information on licensing
Netcool/Impact, see Licensing Netcool/Impact on page 95.
How Do I Run the Database?

You can start and stop the Netcool/Impact database using the database administration script. The database
is not automatically started when you start Netcool/Impact. For more information, see Running the Database
on page 129.
How Do I Manage the Database?

You can also perform administrative tasks with the Netcool/Impact database using the database
administration script. These tasks include viewing the database status, connecting to the database using the
PostgreSQL command line client, and backing up and restoring the database. For more information, see
Managing the Database on page 130.
Cygwin Limitations
Micromuse recommends that you do not use Cygwin on Windows systems where you are running the
Netcool/Impact database. The database uses version 1.5.3 of the Cygwin runtime. This version may conflict
with other versions on the machine.

8.2 Configuring the Database

This section contains information on setting the port used by the Netcool/Impact database and on setting
the PostgreSQL configuration properties.
Setting the Database Port

By default, the Netcool/Impact database uses port 5700. This port number is specified in the
.nci_dbwrapper script, which is called by nci_db. The .nci_dbwrapper script is located in the
$IMPACT_HOME/bin directory.
To change the database port, modify the following line in the .nci_dbwrapper script:
PGPORT=5700
Setting PostgreSQL Configuration Properties

You can configure additional aspects of the database functionality by modifying the PostgreSQL properties
files located in the $IMPACT_HOME/platform/arch/pgsql/data directory, where arch is the
platform where Netcool/Impact is installed. You should only modify these files under the supervision of
Micromuse Technical Support.
The PostgreSQL properties files are described in the official PostgreSQL documentation.

Running the Database
8.3 Running the Database

To start and stop the Netcool/Impact database on UNIX platforms, you use the database administration
script. This script is named nci_db and is located in the $IMPACT_HOME/bin directory. To start and
stop the database on Windows platforms, you use the Windows Services Administration tools.
The database does not start and stop automatically when you start and stop Netcool/Impact.
Before you run the database for the first time, check to see if it is already running. The database is started
automatically when you run the Netcool/Impact installer and may still be running.
Starting the Database on UNIX Platforms

To start the Netcool/Impact database, enter the following at a command line prompt:
$IMPACT_HOME/bin/nci_db start
You do not need to start the database unless you plan to use the GUI reporting tools or use it as a local SQL
database data source.
Stopping the Database on UNIX Platforms

To stop the Netcool/Impact database, enter the following at a command line prompt:
$IMPACT_HOME/bin/nci_db stop
Starting the Database on Windows

To start the Netcool/Impact database:

2. In the Services window that opens, right-click on Netcool Database (Impact) and select Start.
Stopping the Database on Windows

To stop the Netcool/Impact database:

2. In the Services window that opens, right-click on Netcool Database (Impact) and select Stop.

8.4 Managing the Database

You can perform the following tasks using the database administration script:
• Reset the database

• View the database status
• Connect to the database with the command line client
• Back up the database
• Restore the database
The administration script is named nci_db and is located in the $IMPACT_HOME/bin directory.
Resetting the Database

Resetting the database removes all of the historical data stored by the GUI reporting tools.
To reset the database, enter the following at a command line prompt:
$IMPACT_HOME/bin/nci_db setupinit
This command may print multiple error messages to the standard output. In most cases, these error messages
do not indicate a problem with resetting the database. You can redirect the error messages to a log file by
entering the following at a command line prompt:
$IMPACT_HOME/bin/nci_db setupinit 2> error.log
Viewing the Database Status

To view the database status, enter the following at a command line prompt:
$IMPACT_HOME/bin/nci_db status
The following example shows typical output from the status script:
Database on port 5700
Database running.
Connecting to the Database with the Command Line Client

The command line client is a SQL tool that is distributed with the PostgreSQL database. To connect to the
database with the client, enter the following at a command line prompt:
$IMPACT_HOME/bin/nci_db connect

Managing the Database
You can use the client to run SQL statements against the database in real time. For more information, see
the official PostgreSQL documentation.
Backing Up the Database

To back up the database, enter the following at a command line prompt:
$IMPACT_HOME/bin/nci_db backup -backupfile filename
where filename is the name of the backup file.
Restoring the Database

To restore the database from a backup file, enter the following at a command line prompt:
$IMPACT_HOME/bin/nc_db restore -backupfile filename
where filename is the name of the backup file.


Chapter 9: Netcool/Impact JRExec Server
09_JRExec.fm December 15, 2004 10:15 am
This chapter contains information about the Netcool/Impact JRExec server.
• About the JRExec Server on page 134

• Running the JRExec Server on page 135
• Configuring the JRExec Server on page 136

9.1 About the JRExec Server

This section contain overview information about the Netcool/Impact JRExec server. For detailed
information, see the following sections in this chapter.
The section contains the following topics:
• What Is the JRExec Server?

• How Do I Set Up the JRExec Server?
• How Do I Run the JRExec Server?
• Can I Run the JRExec Server Under Process Control?
• How Do I Configure the JRExec Server?
What Is the JRExec Server?

The JRExec server is a runnable server component that Netcool/Impact uses to execute external commands,
scripts and applications from within a policy. You use the JRExec server with the JRExecAction
function. For more information on JRExecAction, see the Netcool/Impact Policy Reference Guide.
How Do I Set Up the JRExec Server?

The JRExec server is automatically installed when you install Netcool/Impact.
How Do I Run the JRExec Server?

On UNIX platforms, you run the JRExec server using the JRExec server script. On Windows platforms, you
can start and stop the server using the Windows Service Administration tools. The Windows service is called
Netcool/Impact JRExec Server.
Can I Run the JRExec Server Under Process Control?

You can run the JRExec server under process control with no special considerations. The JRExec server runs
as a “non-pa aware” application.
How Do I Configure the JRExec Server?

The JRExec server provides a properties file named jrexecserver.props. This file is located in the
$IMPACT_HOME/etc directory and contains the port number used by the JRExec server.

Running the JRExec Server
9.2 Running the JRExec Server

This section contains information on starting and stopping the JRExec server on UNIX and Windows
platforms.
Starting the JRExec Server on UNIX

You start JRExec Server by running the JRExec Server startup script. This script is named nci_jrexec
and is located in the $IMPACT_HOME/bin directory.
To start Netcool/Impact, enter the following at a command prompt:
$IMPACT_HOME/bin/nci_jrexec
Stopping the JRExec Server on UNIX

You stop the JRExec server by manually terminating the server process. To manually terminate the process,
enter the following at a command line prompt:
kill -15 pid
where pid is the process ID of the JRExec Server.
Starting the JRExec Server on Windows

To start Netcool/Impact:

2. In the Services window that opens, right-click on Netcool JRExec Server and select Start.
Stopping the JRExec Server on Windows

To stop Netcool/Impact:

2. In the Services window that opens, right-click on Netcool JRExec Server and select Stop.

9.3 Configuring the JRExec Server

The JRExec server provides a properties file named jrexecserver.props. This file is located in the
$IMPACT_HOME/etc directory and contains the port number used by the JRExec server.
To change the port number used by the JRExec server, open the properties file in any text editor and change
the value of the impact.jrexecserver.port property. If you change this property, you must also
change the value of the impact.jrexec.port property in the server_server.props file,

Chapter 10: Netcool/Impact Self-Monitoring
11_Self-Monitoring.fm December 15, 2004
This chapter contains information about Netcool/Impact self-monitoring.
• About Netcool/Impact Self-Monitoring on page 138

• Memory Status Monitoring on page 140
• Queue Size Monitoring on page 144
• Setting Up Self-Monitoring on page 147
• Viewing Information About Self-Monitoring on page 150

10.1 About Netcool/Impact Self-Monitoring

This section provides overview information about the self-monitoring feature.
• What Is Self-Monitoring?
• How Does Self-Monitoring Work?
• How Does Self-Monitoring Work with a Netcool/Impact Cluster?
• How Do I Set Up Self-Monitoring?
• How Do I Manage Netcool/Impact Events?
What Is Self-Monitoring?
Self-monitoring is a feature of Netcool/Impact that monitors Java and system memory usage, and event
queue size and sends events to the Netcool/OMNIbus ObjectServer regarding memory and queue status.
Self-monitoring allows Netcool operators to monitor the status of Netcool/Impact using an event list in the
same way they monitor the status of other devices and applications.
How Does Self-Monitoring Work?

At intervals, the Netcool/Impact self-monitoring service checks the available memory and sends events to
the ObjectServer that contain information on the status of memory usage. If you are running one or more
event readers, the self-monitoring service also checks the size of the event queues and sends events to the
ObjectServer related to the event queue status. The severity of events sent to the ObjectServer varies
depending on the severity of the memory or event queue status. You can configure the service to deduplicate
the Netcool/Impact events or to send a new event to the ObjectServer at each interval.
How Does Self-Monitoring Work with a Netcool/Impact Cluster?

If you are running multiple Netcool/Impact servers in a cluster, self-monitoring operates on a per-server
basis. This means that you must configure each server instance seperately and that each server runs the
self-monitoring feature independent of other cluster members. Service configuration information is not
propagated between members of the cluster. This allows you to customize self-monitoring to accomodate
each system where you are running Netcool/Impact.

About Netcool/Impact Self-Monitoring
How Do I Set Up Self-Monitoring?

You can set up self-monitoring using the Netcool/Impact GUI or the Netcool/Impact command line
interface (CLI). For single-server configurations of Netcool/Impact, using the GUI is recommended. For a
clustered server configuration, you must set up self-monitoring using the properties file or the CLI.
How Do I Manage Netcool/Impact Events?

Events sent by Netcool/Impact to the ObjectServer as part of self-monitoring are the same as any other
Netcool/OMNIbus events. These events can be viewed by Netcool operators in an event list and managed
according to the normal event handling procedures in your environment. You can also configure the event
reader in Netcool/Impact to launch custom policies that are designed to respond to these events.

10.2 Memory Status Monitoring

This section contains information on monitoring the Netcool/Impact memory status.
• About Memory Status Monitoring

• Memory Status Severity
• Memory Event Fields
About Memory Status Monitoring

Memory monitoring is a process in which the self-monitoring service checks the Java and system memory
and sends events to the Netcool/OMNIbus ObjectServer regarding the memory status at intervals.
Netcool/Impact monitors available memory in both the Java heap and in the system as a whole. The memory
status is significant because Netcool/Impact will fail and report an out-of-memory error if the maximum
available memory is exceeded.
Java Memory Status

When you start an instance of the JVM, you can specify a minimum and maximum heap size using the
-Xms and -Xmx flags. The -Xms flag specifies the minimum size of the memory heap and -Xmx specifies
the maximum size.
With Netcool/Impact, the values for these flags are specified using the XMS and XMX variables in the
runtime definition file. This file is named runtime_def_14 and is located in the
$IMPACT_HOME/platform/arch directory, where arch is the name of the operating system where
Netcool/Impact is installed. The minimum and maximum values are passed to the JVM by the
Netcool/Impact startup script. The default value of XMS is 64M and the default value of XMX is 1000M.
When you enable the self-monitoring feature, Netcool/Impact checks the current heap size at intervals and
compares it to the maximum size specified by the XMX variable. Netcool/Impact then calculates the severity
of the JVM memory status using the rules in Table 26.
System Memory Status

In addition to Java heap memory, the memory monitoring feature also monitors available system memory
as a whole. At maximum, Netcool/Impact uses the amount of Java heap memory specified in the XMX
variable as well as an additional 100 to 120 megabytes of system memory. In order to effectively report on
the memory status for the system, Netcool/Impact must also take into consideration the total amount of
system memory available at a given time compared to the amount of memory currently in use by the
application.

Memory Status Monitoring
When you enable the self-monitoring feature, Netcool/Impact checks the current available system memory
at intervals and compares it to the maximum memory that it requires. Netcool/Impact determines the
maximum memory by adding 150 megabytes to the maximum amount allocated to the Java heap. For
example, if the XMX variable is set to 1000M, Netcool/Impact determines its maximum allocated memory
to be 1150 megabytes. Netcool/Impact then calculates the severity of the system memory status using the
rules in Table 26.
Combined Memory Status

After calculating the severity of the JVM and system memory status, Netcool/Impact sends the event to the
ObjectServer. This event contains the fields described in Table 28. The total severity of the event is the
highest severity between the JVM and system memory status.
Memory Status Severity

Table 26 shows the criteria used by Netcool/Impact to determine the severity of the JVM memory status.
Table 26: Severity Criteria for JVM Memory Events
Severity Criteria
1 Maximum heap limit is greater than twice the current help size.
2 Maximum heap limit is between 1.6 and 2 times the current heap size.
3 Maximum heap limit is between 1.4 and 1.6 times the current heap size.
4 Maximum heap limit is between 1.2 and 1.4 times the current heap size.
5 Maximum heap limit is less than 1.2 times the current heap size.

Table 27 shows the criteria used by Netcool/Impact to determine the severity of the systen memory status.
Table 27: Severity Criteria for System Memory Events
Severity Criteria
1 Available system memory is greater than twice the maximum required memory.
2 Available system memory is between 2 and 1.8 times the maximum required memory.
3 Available system memory is between 1.8 and 1.65 times the maximum required memory.
4 Available system memory is between 1.65 and 1.5 times the maximum required memory.
5 Available system memory is less than 1.5 the maximum required memory.
Note: The total severity of any memory event sent to the ObjectServer is the highest severity between the
JVM and the system memory status.
Memory Event Fields

Table 28 shows the fields in memory events sent to the ObjectServer.
Table 28: Memory Event Fields (1 of 2)
Field Description
Identifier Impact Memory Status for server, where server is the name of the
Netcool/Impact server instance.
Node Hostname of the system where the Netcool/Impact server is running.
NodeAlias IP address of the system where the Netcool/Impact server is running.
Severity Severity calculated according to the rules in Table 26 and Table 27.
Summary Detailed information about the memory status, including information about JVM heap
usage and system memory usage.
Class 10500
Type 13
AlertGroup ImpactStatus
FirstOccurrence Timestamp for the first occurrence of this event.

Memory Status Monitoring
Table 28: Memory Event Fields (2 of 2)
Field Description
LastOccurrence Timestamp for the most recent occurrence of this event.

10.3 Queue Size Monitoring

This section contains information on monitoring the status of Netcool/Impact event reader event queues.
• About Queue Size Monitoring

• Queue Status Severity
• Queue Status Event Fields
About Queue Size Monitoring

Queue size monitoring is the process in which the self-monitoring service checks the size of event reader
event queues at intervals and sends events to the ObjectServer regarding the event queue status. For each
event, the self-monitoring service calculates the severity by determining the rate at which the queue size is
increasing or decreasing since the last interval point. Table 29 shows the rules used to determine the severity.
Table 30 shows the value of fields in the events sent to the ObjectServer.
Queue size monitoring only works when one or more event readers is running in Netcool/Impact.
Queue Status Severity

Table 29 shows the criteria used by Netcool/Impact to determine the severity of the event queue status.
Table 29: Severity Criteria for Queue Status Events
Severity Criteria
1 Number of events in queue is less than or equal to 1.5 times the number of events at previous interval.
2 Number of events in queue is between 1.5 and 2.times the number of events at previous interval.
3 Number of events in queue is between 2 and 3 times the number of events at previous interval.
4 Number of events in queue is between 3 and 5 times the number of events at previous interval.
5 Number of events in queue is more than 5 times the number of events at previous interval.

Queue Size Monitoring
Queue Status Event Fields

Table 28 shows the fields in memory events sent to the ObjectServer.
Table 30: Queue Status Fields
Field Description
Identifier Impact Queue Status for server, where server is the name of the
Netcool/Impact server instance.
Node Hostname of the system where the Netcool/Impact server is running.
NodeAlias IP address of the system where the Netcool/Impact server is running.
Severity Severity calculated according to the rules in Table 26 and Table 27.
Summary Detailed information about the queue status, as described in Table 31.
Class 10500
Type 13
AlertGroup ImpactStatus
FirstOccurrence Timestamp for the first occurrence of this event.
LastOccurrence Timestamp for the most recent occurrence of this event.
Table 31 shows the queue status information sent as the contents of the Summary field.
Table 31: Queue Status Summary Field (1 of 2)
Value Description
Event reader name Name of the event reader associated with the queue.
QueueSize Current number of events in queue.
DeltaQueue Change in queue size since the last interval. If this value is greater than zero, the
queue size has increased. If the value is less than zero, the queue size has
decreased.
QueueIncreaseRate Rate at which the queue is increasing. This value is generated if DeltaQueue is
greater than zero.
QueueDecreaseRate Rate at which the queue is decreasing. This value is generated if DeltaQueue is
less than zero.

Table 31: Queue Status Summary Field (2 of 2)
Value Description
Gap Time difference between the StateChange of the earliest event in queue and
the current time.

Setting Up Self-Monitoring
10.4 Setting Up Self-Monitoring

You can set up event monitoring using the following:
• Netcool/Impact CLI
• Netcool/Impact self-monitoring service properties file
If you are running Netcool/Impact in a clustered server configuration, you must set up self-monitoring using
the CLI or the service properties file.
Setting Up Self-Monitoring Using the GUI

To set up self-monitoring using the Netcool/Impact GUI:
1. Open the GUI in a web browser.

2. In the Service Status panel, select SelfMonitoring.
The Self-Monitoring Configuration window opens.
Figure 6: Self-Monitoring Configuration Window
3. Select a data source from the ObjectServer Data Source list. This is the ObjectServer where any new
events will be sent.

4. Enter an interval in seconds in the Interval field. This is the number of seconds at which you want
Netcool/Impact to check memory status and the event queue size.
5. Enable or disable the Depulication option. This options specifies whether Netcool/Impact should
deduplicate events it sends to the ObjectServer. If you change the deduplication option while the
service is running, you must stop and restart it before the change takes effect.
6. Enable or disable the Startup option. This option specifies whether this service starts automatically
when you start the Netcool/Impact server.
7. Enable or disable the Service Log option. This option specifies whether to print the service log to file.
8. Click OK.
9. In the Service Status panel, click the Start button for the SelfMonitoring service.
Setting Up Self-Monitoring Using the CLI

You can use the Netcool/Impact CLI to set up self-monitoring if you running Netcool/Impact in both single
server and clustered server configurations.
To set up self-monitoring using the CLI:
1. Start the command line interface by opening the following address in any telnet application:
telnet hostname port
where hostname is the name of the system where the Netcool/Impact server is running and port
is the command line port. The default port is 2000.
2. Specify the interval at which you want Netcool/Impact to check memory status and the event queue
size by entering the following:
UPDATE Service SET Interval = seconds WHERE Name = ’SelfMonitoring’;
where seconds is the number of seconds in the interval.

3. Specify the ObjectServer to which you want Netcool/Impact to send self-monitoring events by
entering the following:
UPDATE Service SET DataSource = data_source WHERE Name = ’SelfMonitoring’;
where data_source is the name of an ObjectServer data source.

4. Specify whether you want Netcool/Impact to deduplicate self-monitoring events that it sends to the
ObjectServer by entering the following:
UPDATE Service SET Deduplication = dedup_option WHERE Name = ’SelfMonitoring’;
where dedup_option is true or false.

Setting Up Self-Monitoring
If you change the deduplication option while the service is running, you must stop and restart it
before the change takes effect.
5. Start the self-monitoring service by entering the following:
UPDATE Service SET Running = True WHERE Name = ’Self-Monitoring’;

10.5 Viewing Information About Self-Monitoring

You can use the Netcool/Impact CLI to view the following information about self-monitoring:
• Memory status history

• Queue status
• Queue status history
• Current JVM heap size
• Free JVM heap size
• Maximum JVM heap size
• Maximum required memory
• Available system memory
• Deduplication status
• Monitoring interval
• ObjectServer data source
Memory Status History

The memory status history is a list containing memory status information for the last 100 self-monitoring
intervals. You can use this information to analyze trends in Netcool/Impact memory usage.
To view the memory status history enter the following at a Netcool/Impact CLI prompt:
SELECT MemoryStatusHistory from Service WHERE Name = ’SelfMonitoring";
Queue Status
The status of an event queue, including the queue size, the change in queue size since the previous interval,
and the rate of queue size change.
To view the queue status enter the following at a Netcool/Impact CLI prompt:
SELECT QueueStatus from Service WHERE Name = ’SelfMonitoring";

Viewing Information About Self-Monitoring
Queue Status History

The queue status history is a list containing queue status history information for the last 100 self-monitoring
intervals. You can use this information to analyze trends in the queue status.
To view the queue status history enter the following at a Netcool/Impact CLI prompt:
SELECT QueueStatusHistory from Service WHERE Name = ’SelfMonitoring";
Current JVM Heap Size

The current JVM heap size is the amount of memory in the Java heap that is currently used by
Netcool/Impact.
To view the current JVM heap size, enter the following at a Netcool/Impact CLI prompt:
SELECT TotalVMHeapSize from Service WHERE Name = ’SelfMonitoring";
Available JVM Heap Size

The available JVM heap size is the amount of memory in the Java heap that is unused by Netcool/Impact.
To view the available JVM heap size enter the following at a Netcool/Impact CLI prompt:
SELECT FreeVMHeapSize from Service WHERE Name = ’SelfMonitoring";
Maximum JVM Heap Size

The maximum JVM heap size is the maximum size specified by the XMX variable in the runtime definition
file for Netcool/Impact.
To view the maximum JVM heap size, enter the following at a Netcool/Impact CLI prompt:
SELECT MaxVMHeapSize from Service WHERE Name = ’SelfMonitoring";
Maximum Required Memory

The maximum required memory is the maximum JVM heap size plus the 120 megabyte system memory
overhead used by Netcool/Impact.
To view the maximum required memory, enter the following at a Netcool/Impact CLI prompt:
SELECT MaxVMSize from Service WHERE Name = ’SelfMonitoring";

Available System Memory

The available system memory is the total free memory on the system unused by Netcool/Impact and other
applications.
To view the available system memory, enter the following at a Netcool/Impact CLI prompt:
SELECT FreeSystemMemory from Service WHERE Name = ’SelfMonitoring";
Deduplication Status
The deduplication status indicates whether Netcool/Impact is currently deduplicating self-monitoring
events it sends to the ObjectServer.
To view the deduplication status, enter the following at a Netcool/Impact CLI prompt:
SELECT Deduplication from Service WHERE Name = ’SelfMonitoring";
Monitoring Interval
The monitoring interval specifies the number of seconds at which Netcool/Impact is checking the memory
status and event queue size.
To view the monitoring interval, enter the following at a Netcool/Impact CLI prompt:
SELECT Interval from Service WHERE Name = ’SelfMonitoring";
ObjectServer Data Source

This is the ObjectServer where Netcool/Impact is sending self-monitoring events.
To view the name of the ObjectServer data source, enter the following at a Netcool/Impact CLI prompt:
SELECT DataSource from Service WHERE Name = ’SelfMonitoring";

Chapter 11: Command Line Tools
10_Command_Line_Tools.fm December 15, 2004 10:15 am
This chapter contains information about the Netcool/Impact command line tools.
• nci_crypt on page 154

• nci_export on page 155
• nci_import on page 156
• nci_trigger on page 157

11.1 nci_crypt
The nci_crypt tool encrypts a string using the Netcool/Impact encryption algorithm. You can use this
tool to encrypt passwords passed to Netcool/Impact from the command line with nci_trigger. This
tool is located in the $IMPACT_HOME/bin directory.
To run this tool, enter the following at a command prompt:

$IMPACT_HOME/bin/nci_crypt string
where string is the string you want to encrypt.

nci_export
11.2 nci_export
The nci_export tool exports data source, data type, service and policy information from an instance of
the Netcool/Impact server to a specified directory. This tool is located in the $IMPACT_HOME/bin
directory.
Note: Make sure that the instance of the Netcool/Impact server that contains the data you are exporting is
running before you use nci_export.

$IMPACT_HOME/bin/nci_export server_name directory
where server_name is the name of the server instance whose data you want to export and directory
is the directory where you want to store the exported data.

11.3 nci_import
The nci_import tool imports data that was previously exported from an instance of the Netcool/Impact
server. This data includes all data sources, data types, policies and services currently defined in the server
instance. This tool is located in the $IMPACT_HOME/bin directory.
Note: Make sure that the target instance of the Netcool/Impact server is running before you use
nci_import.

$IMPACT_HOME/bin/nci_import server_name directory
where server_name is the name of the server instance where you want to import the data and
directory is the location that contains data exported using nci_export.

nci_trigger
11.4 nci_trigger
The nci_trigger tool allows you to start a policy from the command line. This tool is located in the
$IMPACT_HOME/bin directory.

$IMPACT_HOME/bin/nci_trigger [-version] | server_name [ user_id | user_id/password |
-e/user_id/encrypted_password | NULL ] policy_name field value field value ...
Note: If no password is defined for the user, you must specify the password as NULL when you execute the
command.
Table 32 shows the command line arguments for nci_trigger.
Table 32: nci_trigger Command Line Arguements
Arguments Description
-version Causes nci_trigger to print the Netcool/Impact version

number, platform and command syntax to standard output and
then exit.
server_name Instance of the Netcool/Impact server where you want the policy
to run.
user_id/password UNIX only. Username and password of a valid Netcool Security

Manager user who has access to Netcool/Impact.
user_id password Windows only. Username and password of a valid Netcool Security
Manager user who has access to Netcool/Impact.
-e/user_id/encrypted_password UNIX only. Username and encrypted password of a valid Netcool

Security Manager user who has access to Netcool/Impact. You can
encrypt passwords using the nci_crypt tool.
-e user_id encrypted_password Windows only. Username and encrypted password of a valid

Netcool Security Manager user who has access to Netcool/Impact.
You can encrypt passwords using the nci_crypt tool.
policy_name Name of the policy to run.
field Name of a field in the event container passed to the policy.

Optional.
value Value of a field in the event container passed to the policy.

Optional.

Note: If you want to run a policy that contains a call to the ReturnEvent function, you must include
Identifier and Serial fields in the event container passed to policy.
Runtime Parameters
If you are using nci_trigger to pass runtime parameters to a policy, you must make sure that you
specify the parameters as variables in the policy using the @ notation.
The following example shows how to use this notation in a policy. In this example, the policy is named
POLICY_01
Log(@Value1);
Log(@Value2);
To run this policy using nci_trigger, you can enter the following at a command prompt:
nci_trigger admin/netcool POLICY_01 Value1 Testing1 Value2 Testing2
This prints the following to the policy log:

Testing1
Testing2
UNIX Examples
This example shows how to run a simple policy from the command line that does not process an in-coming
event. In this example, the policy is named POLICY_01, the user is admin, the password is netcool
and the server instance is NCI.
nci_trigger NCI admin/netcool POLICY_01
This example shows how to run a policy using an encrypted password. In this example, the password was
previously encrypted using the nci_crypt tool.
nci_trigger NCI_02 -e/admin/7E6C7364EFD7CD69 POLICY_02
This example shows how to to run a policy and pass event field values to the policy as the contents of an
incoming event container.
nci_trigger NCI admin/netcool POLICY_03 Node host_01 Summary Node_down AlertKey
host_01Node_down

nci_trigger
Windows Examples
This example shows how to run a simple policy from the command line that does not process an in-coming
event. In this example, the policy is named POLICY_01, the user is admin, the password is netcool
and the server instance is NCI.
nci_trigger NCI admin netcool POLICY_01
This example shows how to run a policy using an encrypted password. In this example, the password was
previously encrypted using the nci_crypt tool.
nci_trigger NCI_02 -e admin 7E6C7364EFD7CD69 POLICY_02
This example shows how to to run a policy and pass event field values to the policy as the contents of an
incoming event container.
nci_trigger NCI admin netcool POLICY_03 Node host_01 Summary Node_down AlertKey
host_01Node_down


Appendix A: Supplementary Information
98_Appendix.fm December 15, 2004 10:15 am
This appendix contains supplementary information for Netcool/Impact administrators.
• Installation Worksheet on page 162

• Firewall Considerations on page 166
• UNIX Kernel Configuration on page 167

A.1 Installation Worksheet

The installer programs for Netcool/Impact and its related software components prompt you for system
information during the installation process. You should record this information during the course of
installation for later reference.
You can use the tables in this section to record installation information. Each table contains an empty
Answer column that you can fill with the information that you supply to the installer programs.
If you install the components in console mode, you can also record the information electronically using the
UNIX script command.
Netcool License Server

The Netcool License Server installer prompts you for the following information:
Table A1: Netcool Common License Server Installer Prompts
Prompt Answer
Installation directory
Netcool GUI Server

The Netcool GUI Server installer prompts you for the following information:
Table A2: Netcool GUI Server Installer Prompts (1 of 2)
Prompt Answer
Application Registry directory
Shutdown port
HTTP port

Installation Worksheet
Table A2: Netcool GUI Server Installer Prompts (2 of 2)
Prompt Answer
Security Manager host
Security Manager port
License Server host
License Server port
Netcool Security Manager

The Netcool Security Manager installer prompts you for the following information:
Table A3: Netcool Security Manager Installation Prompts
Prompt Answer
HTTP listener port
Server port
Database port
License server host
License server port

Netcool/Impact
The Netcool/Impact installer prompts you for the following information:
Table A4: Netcool/Impact Installer Prompts
Prompt Answer
Version control system
License server host
License server port
Registry host
Registry port
PostgreSQL port
Netcool/Impact Server
The nci_new_server script prompts you for the following information:
Table A5: Netcool/Impact New Server Script Prompts (1 of 2)
Prompt Answer
Instance name
Cluster name

Installation Worksheet
Table A5: Netcool/Impact New Server Script Prompts(Continued) (2 of 2)
Prompt Answer
Command line port
ObjectServer host
ObjectServer port
Impact HTTP port
SMTP host
E-Mail sender name
Version control system

A.2 Firewall Considerations

If you are running Netcool/Impact and its related components in a networked environment where
components are separated by a firewall, or if you are installing them on Windows systems with built-in
firewall software, you can use information in Table A6 to make sure that access is permitted between
components at the designated ports.
Table A6: Netcool/Impact Component Ports
Default Port Description
5104 Netcool/Impact HTTP port. This port is used for communication between Netcool/Impact and the
Netcool GUI Server. This port is also used in a clustered server configuration for communication
between cluster members.
2000 Netcool/Impact command line port.
8080 GUI Server HTTP port. This port is used by the GUI Server to serve the Netcool/Impact GUI and the
Security Manager GUI. This port is also used by the Netcool Application Registry to communicate with
Netcool components.
8077 Security Manager port. This port is used by the Security Manager to communicate with Netcool/Impact
and other Netcool components. This port is also used to serve the Security Manager GUI in standalone
configurations.
27000 License Server port. This port is used by the License Server for communication with other Netcool
components.
4100 Netcool/OMNIbus ObjectServer port. This port is used by the Netcool Security Manager for ObjectServer
authentication and for the default ObjectServer data source.
If you are using Netcool/Impact to access data sources that are located on a separate system (for example, an
SQL database), you must make sure that the data source port is accessible to Netcool/Impact through any
firewall configuration.

UNIX Kernel Configuration
A.3 UNIX Kernel Configuration

The Netcool/Impact database is a customized version of PostgreSQL that has been prepared for use with
this application. Before you install Netcool/Impact on UNIX platforms, you must configure the operating
system kernel so that it fulfills the memory requirements for the PostgreSQL database. In addition, if you
are installing on HP-UX, you must also configure the kernel to accomodate the threading requirements of
Netcool/Impact.
PostgreSQL requires a maximum shared memory setting of at least 32 MB for each instance running on a
system. Micromuse recommends a settting of 64 MB. If you are running both Netcool/Impact and the
Netcool Security Manager on a single system, you should set the maximum shared memory to 128 MB.
For more information, see the official PostgreSQL documentation. This documentation is distributed with
Netcool/Impact and is located in the $IMPACT_HOME/platform/arch/pgsql/doc/html
directory, where arch is the name of the operating system. The HTML file that contains instructions on
configuring the operating system kernel is named kernel-resources.html.
Configuring Solaris
On Solaris platforms, kernel configuration settings are located in the /etc/system file. To configure
shared memory settings on Solaris, you must modify the file so that it contains the following lines:
set shmsys:shminfo_shmmax=max_memory
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=256
set shmsys:shminfo_shmseg=256
set semsys:seminfo_semmap=256
set semsys:seminfo_semmni=512
set semsys:seminfo_semmns=512
set semsys:seminfo_semmsl=32
where max_memory is at least 0x4000000 on systems where you are installing either Netcool/Impact
and the Security Manager or 0x8000000 on systems where you are installing both.
Note: You must reboot the system in order for the new settings to take effect.

Configuring Red Hat Linux

On Red Hat Linux platforms, kernel configuration settings are located in the /etc/sysctl.conf file.
To configure the kernel you must modify the file so that it contains the following line:
kernel.shmmax=max_memory
where max_memory is at least 6710864 on systems where you are installing either Netcool/Impact or
the Security Manager and at least 13421728 on systems where you are installing both.
Note: You must reboot the system in order for the new settings to take effect.
To make the change without rebooting, you can also configure the proc file system. To change the shared
memory, enter the following at a comment line prompt:
echo max_memory >/proc/sys/kernel/shmmax
where max_memory is the new maximum memory setting.
Note that changes to the proc file system are not persistent after reboot.
Configuring HP-UX
Netcool/Impact requires a max_thread_proc setting of at least 500 on HP-UX. Settings of less than
500 can cause the Netcool/Impact server to fail at startup. You can specify the max_thread_proc
setting using the HP-UX Kernel Configuration tool.
Configuring AIX
The default kernel configuration for AIX is adequate for running Netcool/Impact and the Netcool Security
Manager. You do not need to configure kernel settings on AIX platforms.

Appendix B: DSA Reference
99_Appendix.fm December 15, 2004
This appendix contains reference information related to built-in Netcool/Impact DSAs.
• About the Built-In DSAs on page 170

• DB2 DSA on page 172
• Flat File DSA on page 174
• Informix DSA on page 176
• MySQL DSA on page 178
• ObjectServer DSA on page 180
• ODBC DSA on page 182
• Oracle DSA on page 183
• PostgreSQL DSA on page 185
• SQL Server DSA on page 187
• Sybase DSA on page 189

B.1 About the Built-In DSAs

Netcool/Impact provides a standard set of built-in data source adaptors (DSAs) that you can use to access
common SQL database data sources. These DSAs are installed automatically when you install
Netcool/Impact and are only visible in the Netcool/Impact GUI after you have installed licenses for them
in the Netcool Common License Server.
SQL Database DSAs

This chapter provides the following information about SQL database DSAs:
• JDBC driver versions

• Data source configuration properties
• Data type configuration properties
• Supported data types
• Special considerations
JDBC Driver Versions

SQL database DSAs use Java Database Connectivity (JDBC) drivers to connect to underlying data sources.
You can use the information provided on driver versions to debug and troubleshoot DSA performance and
to better understand the scope and scale of functionality provided.
Data Source Configuration Properties

When you create a new data source for use with an SQL database DSA, you must specify a set of
configuration properties. These properties typically include the data source name and connectivity
information for the underlying database (for example, the hostname and port). Some DSAs require
additional information.
Data Type Configuration Properties

When you create a new data type for use with an SQL database data source, you are required to specify the
name of the table (or similar structure) in the underlying data source, as well as field names that correspond
to each column in the table. In most cases, field names can be specified using the auto-discovery tools.

About the Built-In DSAs
Supported Data Types

SQL database DSAs allow you to access information stored in most of the data types in the underlying
database. However, some DSAs exclude rarely-used data types. In most cases, data types representing string
or character values are treated as Netcool/Impact strings, whole number data types are treated as
Netcool/Impact integers and decimal data types are treated as Netcool/Impact floats.
Special Considerations
Some SQL database DSAs require you to perform additional steps or prevent you from accessing
functionality specific to the underlying database.

B.2 DB2 DSA

The DB2 DSA is a built-in component of Netcool/Impact that allows you to access information in an IBM
DB2 database.
JDBC Driver Version

This DSA uses version 7.2 of the DB2 JDBC driver. For more information on this driver, see the DB2
website at http://www.ibm.com/software/data/db2/.

Table B1 shows the configuration properties that you set when you create a DB2 data source.
Table B1: DB2 Data Source Configuration Properties
Data Source Name Name of the DB2 data source.
Username Username to use when accessing the DB2 database.
Password Password to use when accessing the DB2 database.
Maximum SQL Connections Maximum number of simultaneous SQL connections to the DB2 database.
Default is 5.
Primary Hostname Hostname of the system where the primary DB2 database is running.
Primary Port Connection port used by the primary DB2 database. Default is 6789.
Primary Database Name of the primary DB2 database.
Backup Hostname Hostname of the system where the backup DB2 database is running.
Backup Port Connection port used by the backup DB2 database. Default is 6789.
Backup Database Name of the backup DB2 database.
Disable Data Source Failover Specifies that you do not want to use DSA failover with this data source.

DB2 DSA
Data Types
Table B2 shows the supported DB2 data types and their Netcool/Impact equivalents.
Table B2: DB2 DSA Supported Data Types
DB2 Data Type Netcool/Impact Data Type
smallint, integer, bigint Integer
float, real, double, decimal, numeric Float
char, varchar, long varchar, clob String
date, time, timestamp Date
blob, dbclob, graphic, vargraphic Not supported

B.3 Flat File DSA

The Flat File DSA is a built-in component of Netcool/Impact that allows you to read information in a
character-delimited text file. You cannot use the Flat File DSA to write information to a text file.
Note: The Flat File DSA is intended for use in demonstrating and testing Netcool/Impact and for
infrequently accessing small amounts of data stored in a text file. Use of text files and the Flat File DSA is
not an effective substitute for the use of a conventional relational database and an SQL database DSA. The
Flat File DSA offers slow performance when compared to other DSAs.
File Format
The Flat File DSA is capable of reading a character-delimited text file stored on the file system where
Netcool/Impact is running. This text file must be a multi-line file, where the first line specifies the names of
the fields and each subsequent line represents a row of data. Field names can contain any character except
the double quotation mark (") and the space character ( ).
The following is an example of a character-delimited text file. In this example, name, email and
location are the field names.
name,email,location
Mark Gonzalez,mgonzalez@example.com,New York
Anna Singh,asingh@example.com,London
James Chen,jchen@example.com,San Francisco

Table B3 shows the configuration properties for Flat File data sources.
Table B3: Flat File Data Source Configuration Properties
Data Source Name Name of the data source.
Directory Path of the text file that contains the data you want to access using this DSA. You specify the
filename when you create a flat file data type.
Delimiters Delimiter character that separates fields in the text file. The DSA supports the following
delimiters: , ; - + /. You must enclose the delimiter character in single quotation marks
when you define it in the Netcool/Impact GUI.

Flat File DSA
Data Type Configuration Properties

You configure a Flat File data type in the same way that you configure other SQL database data types, with
the exception that, instead of a table name in the Base Table field, you specify the name of the text file that
contains the information you want to access.
The Flat File DSA only supports the use of the equal operatory (=) in SQL filter statements. You use SQL
filters when you call the GetByFilter function in the policy language and when you use filters while
browsing data type contents in the Netcool/Impact GUI. Other operators, like less than (<), greater than
(>) and LIKE, are not supported.

B.4 Informix DSA

The Informix DSA is a built-in component of Netcool/Impact that allows you to access information in an
IBM Informix database.
JDBC Driver Version

This DSA uses version 1.40.JC2 of the Informix JDBC driver. For more information, see the Informix
JDBC website at http://www-306.ibm.com/software/data/informix/tools/jdbc/.

Table B1 shows the configuration properties that you set when you create an Informix data source.
Table B4: Informix Data Source Configuration Properties
Data Source Name Name of the Informix data source.
Username Username to use when accessing the Informix database.
Password Password to use when accessing the Informix database.
Maximum SQL Connections Maximum number of simultaneous SQL connections to the Informix database.
Default is 5.
Primary Hostname Hostname of the system where the primary Informix database is running.
Primary Port Connection port used by the primary Informix database. Default is 1526.
Primary Server Server name where the primary Informix database resides.
Primary Database Name of the primary Informix database.
Backup Hostname Hostname of the system where the backup Informix database is running.
Backup Port Connection port used by the backup Informix database. Default is 1526.
Backup Server Server name where the backup Informix database resides.
Backup Database Name of the backup Informix database.
Disable Data Source Failover Specifies that you do not want to use Informix failover with this data source.

Informix DSA
Data Types
Table B5 shows the supported Informix data types and their Netcool/Impact equivalents.
Table B5: Informix DSA Supported Data Types
Informix Data Type Netcool/Impact Data Type
INT, SMALLINT Integer
FLOAT, SMALLFLOAT, DEC Float
CHAR, VARCHAR String
DATE, DATETIME Date
MONEY String
BLOB, INTERVAL, BYTE Not supported
Netcool/Impact supports the Informix DATETIME data type in YEAR to FRACTIONs format only. If an
Informix table contains datetime columns that use another format, you must convert the column type
before you can access the table using Netcool/Impact. To ensure that Netcool/Impact functions correctly
with this data type, make sure that datetime fields use the format
yyyy-mm-dd hh:mm:ss.nn (for example, 2004-07-01 08:45:01.10).
Netcool/Impact does not support inserts or updates on DATE fields in Informix tables. This means that you
cannot add or update data items in the associated Netcool/Impact data types unless you specify that you
want to exclude the fields from inserts. You can set the exclude from insert option in the Netcool/Impact
GUI when you edit data type fields.
Informix fields of INTERVAL data type are not supported by Netcool/Impact. Attempts to retrieve, insert
or update interval fields may cause runtime errors.

B.5 MySQL DSA

The MySQL DSA is a built-in component of Netcool/Impact that allows you to access information in a
MySQL database.
JDBC Driver Version

This DSA uses version 2.0 of the MySQL Connector/J JDBC driver. For more information, see the MySQL
website at http://www.mysql.org.

Table B6 shows the configuration properties that you set when you create a MySQL data source.
Table B6: MySQL Data Source Configuration Properties
Data Source Name Name of the MySQL data source.
Username Username to use when accessing the MySQL database.
Password Password to use when accessing the MySQL database.
Maximum SQL Connections Maximum number of simultaneous SQL connections to the MySQL database.
Default is 5.
Primary Hostname Hostname of the system where the primary MySQL database is running.
Primary Port Connection port used by the primary MySQL database. Default is 3306.
Primary Database Name of the primary MySQL database.
Backup Hostname Hostname of the system where the backup MySQL database is running.
Backup Port Connection port used by the backup MySQL database. Default is 3306.
Backup Database Name of the backup MySQL database.
Disable Data Source Failover Specifies that you do not want to use MySQL failover with this data source.

MySQL DSA
Data Types
Table B7 shows the supported MySQL data types and their Netcool/Impact equivalents.
Table B7: MySQL DSA Supported Data Types
MySQL Data Type Netcool/Impact Data Type
TINYINT, SMALLINT, MEDIUMINT, BIGINT, INT Integer
FLOAT, DOUBLE, DECIMAL, FIXED Float
CHAR, VARCHAR, TEXT String
DATE, DATETIME, TIMESTAMP Date
TIME, YEAR String
TINYBLOB, BLOB, MEDIUMBLOB, LONGBLOG, SET, ENUM Not supported

B.6 ObjectServer DSA

The ObjectServer DSA is a built-in component of Netcool/Impact that allows you to access information in
a Netcool/OMNIbus ObjectServer.
Note: Use of the ObjectServer DSA is not required for Netcool/Impact to retrieve events from the
ObjectServer using the event reader server or to add, update, or delete events from within a policy using the
ReturnEvent function.
Supported Versions
This DSA supports versions 3.5, 3.6, and v7 of the ObjectServer.

Table B8 shows the configuration properties that you set when you create an ObjectServer data source.
Table B8: ObjectServer Data Source Configuration Properties
Data Source Name Name of the ObjectServer data source.
Username Username to use when accessing the ObjectServer database.
Password Password to use when accessing the ObjectServer database.
Maximum SQL Connections Maximum number of simultaneous SQL connections to the ObjectServer
database. Default is 5.
Primary Hostname Hostname of the system where the primary ObjectServer database is running.
Primary Port Connection port used by the primary ObjectServer database. Default is 1521.
Backup Hostname Hostname of the system where the backup ObjectServer database is running.
Backup Port Connection port used by the backup ObjectServer database. Default is 1521.
Disable Data Source Failover Specifies that you do not want to use ObjectServer failover with this data source.

ObjectServer DSA
Data Types
Table B9 shows the supported ObjectServer data types and their Netcool/Impact equivalents.
Table B9: ObjectServer DSA Supported Data Types
ObjectServer Data Type Netcool/Impact Data Type
INTEGER, UNSIGNED, INCR Integer
REAL Float
CHAR, VARCHAR String
TIME Integer
BOOLEAN String

B.7 ODBC DSA

The ODBC DSA is a built-in component of Netcool/Impact that allows you to access information in an
ODBC data source.
JDBC Version
This DSA uses JDBC/ODBC bridge technology provided by version 1.4 of the Java 2 Software
Development Kit.
Data Types
Generally, ODBC data types are treated as their closest equivalent by Netcool/Impact. For example, all
whole number data types are treated as integers by Netcool/Impact and all decimal data types are treated as
Floats. Similarly, all data types that store text are treated as strings.

Oracle DSA
B.8 Oracle DSA

The Oracle DSA is a built-in component of Netcool/Impact that allows you to access information in an
Oracle database.
JDBC Version
This DSA uses version 9i of the Oracle JDBC driver.

Table B10 shows the configuration properties that you set when you create an Oracle data source.
Table B10: Oracle Data Source Configuration Properties
Data Source Name Name of the Oracle data source.
Username Username to use when accessing the Oracle database.
Password Password to use when accessing the Oracle database.
Maximum SQL Connections Maximum number of simultaneous SQL connections to the Oracle database. Default is
5.
Primary Hostname Hostname of the system where the primary Oracle database is running.
Primary Port Connection port used by the primary Oracle database. Default is 4100.
Primary SID Server ID of the server where the primary Oracle database resides. Default is ORCL.
Backup Hostname Hostname of the system where the backup Oracle database is running.
Backup Port Connection port used by the backup Oracle database. Default is 4100.
Backup SID Server ID of the server where the backup Oracle database resides. Default is ORCL.
Disable Data Source Failover Specifies that you do not want to use Oracle failover with this data source.

Data Types
Table B11 shows the supported Oracle data types and their Netcool/Impact equivalents.
Table B11: Oracle DSA Supported Data Types
Oracle Data Type Netcool/Impact Data Type
NUMBER Integer
FLOAT Float
CHAR, NCHAR, NVARCHAR2 String
CLOB Clob
BLOB, BFILE, RAW, LONG RAW, INTERVAL_YEAR Not supported

PostgreSQL DSA
B.9 PostgreSQL DSA

The PostgreSQL DSA is a built-in component of Netcool/Impact that allows you to access information in
an PostgreSQL database.
JDBC Version
This DSA uses version 7.3 of the PostgreSQL JDBC 3.0 driver. For more information on this driver, visit
the PostregSQL JDBC website at http://jdbc.postgresql.org.

Table B12 shows the configuration properties that you set when you create a PostgreSQL data source.
Table B12: PostgreSQL Data Source Configuration Properties
Data Source Name Name of the PostgreSQL data source.
Username Username to use when accessing the PostgreSQL database.
Password Password to use when accessing the PostgreSQL database.
Maximum SQL Connections Maximum number of simultaneous SQL connections to the PostgreSQL
database. Default is 5.
Primary Hostname Hostname of the system where the primary PostgreSQL database is running.
Primary Port Connection port used by the primary PostgreSQL database. Default is 5432.
Backup Hostname Hostname of the system where the backup PostgreSQL database is running.
Backup Port Connection port used by the backup PostgreSQL database. Default is 5432.
Disable Data Source Failover Specifies that you do not want to use PostgreSQL failover with this data source.

Data Types
Table B13 shows the supported PostgreSQL data types and their Netcool/Impact equivalents.
Table B13: PostgreSQL DSA Supported Data Types
PostgreSQL Data Type Netcool/Impact Data Type
smallint, integer, bigint, serial, bigserial Integer
decimal, numeric, real, double precision Float
char, character, varchar, character varying, text String
boolean Boolean
Inet, macaddr, cidr String
The money data type is deprecated in versions 7.3 and later of PostgreSQL. This data type is not supported
by Netcool/Impact. Micromuse recommends that you use the numeric or decimal data type in
PostgreSQL as a substitute.

SQL Server DSA
B.10 SQL Server DSA

The SQL Server DSA is a built-in component of Netcool/Impact that allows you to access information in a
Microsoft SQL Server database.
JDBC Version
The SQL Server DSA uses version 0.8rc1of the jTDS JDBC driver. For more information on this driver,
visit the jTDS website at http://jtds.sourceforge.net/.

Table B14 shows the configuration properties that you set when you create an SQL Server data source.
Table B14: SQL Server Data Source Configuration Properties
Data Source Name Name of the SQL Server data source.
Username Username to use when accessing the SQL Server database.
Password Password to use when accessing the SQL Server database.
Maximum SQL Connections Maximum number of simultaneous SQL connections to the SQL Server database.
Default is 5.
Primary Hostname Hostname of the system where the primary SQL Server database is running.
Primary Port Connection port used by the primary SQL Server database. Default is 5432.
Backup Hostname Hostname of the system where the backup SQL Server database is running.
Backup Port Connection port used by the backup SQL Server database. Default is 5432.
Disable Data Source Failover Specifies that you do not want to use SQL Server failover with this data source.

Data Types
Table B15 shows the supported SQL Server data types and their Netcool/Impact equivalents.
Table B15: SQL Server DSA Supported Data Types
SQL Server Data Type Netcool/Impact Data Type
tinyint, smallint, int, bigint Integer
decimal, numeric, float, real Float
char, varchar, text, nchar, nvarchar, ntext String
datetime, smalldatetime Date
smallmoney, money, uniqueidentifier String
binary, varbinary, image, cursor Not supported

Sybase DSA
B.11 Sybase DSA

The Sybase DSA is a built-in component of Netcool/Impact that allows you to access information in a
Sybase database.
Supported Versions
This DSA uses version 5.5 of the Sybase jConnect JDBC driver.

Table B16 shows the configuration properties that you set when you create a Sybase data source.
Table B16: Sybase Data Source Configuration Properties
Data Source Name Name of the Sybase data source.
Username Username to use when accessing the Sybase database.
Password Password to use when accessing the Sybase database.
Maximum SQL Connections Maximum number of simultaneous SQL connections to the Sybase database.
Default is 5.
Primary Hostname Hostname of the system where the primary Sybase database is running.
Primary Port Connection port used by the primary Sybase database. Default is 5000.
Backup Hostname Hostname of the system where the backup Sybase database is running.
Backup Port Connection port used by the backup Sybase database. Default is 5000.
Disable Data Source Failover Specifies that you do not want to use Sybase failover with this data source.

Data Types
Table B17 shows the supported Sybase data types and their Netcool/Impact equivalents.
Table B17: Sybase DSA Supported Data Types
Sybase Data Type Netcool/Impact Data Type
TINYINT, SMALLINT, INT Integer
NUMERIC, DECIMAL, REAL, FLOAT Float
CHAR, VARCHAR, TEST, UNICHAR, String

UNIVARCHAR, NCHAR, NVARCHAR
SMALLDATETIME, DATETIME Date
SMALLMONEY, MONEY Float
BINARY, VARBINARY, IMAGE Not supported

Index
MMGuideIX.fm December 15, 2004 10:15 am
Index
A H
authentication 99 host ID (License Server) 39
C I
cygwin IMPACT_HOME 90
Netcool/Impact database limitations 127 ImpactUser role 99
importing Netcool/Impact data 156
D Informix DSA 176
DB2 DSA 172 installing

GUI Server 60
License Server 36
E Netcool/Impact 88
event queue monitoring 144
exporting Netcool/Impact data 155
J
JRExec server 134
F configuring 136
Flat File DSA 174 running 135
G L
GUI Server 54 license files 33
Application Registry 58 License Server 28
architecture 59 architecture 32
components 58 command line tools (UNIX) 43
configuring 66 components 33
environment variables 62 daemons (UNIX) 33
installing 60 environment variables 37
Java Development Kit (AIX and HP-UX) 60 host ID 39
licensing 63 installing 36
logging 77 LMTOOLS (Windows) 45
running 65 running (UNIX) 43
Servlet Engine 58 running (Windows) 45
uninstalling 78 service (Windows) 33
GUI_HOME 62 system requirements 31
uninstalling 51

Index
licenses Netcool/Impact database 126

feature codes 40 configuring 128
host ID 39 managing 130
installing 39 running 129
licensing, quorum 48 Netcool/Impact Server 104
LMTOOLS 45 creating instances 106
deleting instances 110
monitoring instances 109
M running instances (UNIX) 107
memory status monitoring 140 running instances (Windows) 108
MySQL DSA 178 Netcool/Impact server
clustering 112
NETCOOL_LICENSE_PATH 38
N
ncgui_server 65
ncgui_shutdown 65 O
nci_db 129 ObjectServer DSA 180
nci_export 155 ODBC DSA 182
nci_import 156 Oracle DSA 183
nci_jrexec 135
nci_server 107 P
nci_shutdown 107 PostgreSQL DSA 185
NCLICENSE 37
Netcool/Impact 80
Q
architecture 87
backing up and restoring 100 queue size monitoring 144
components 85 quorum licensing 48

configuring registry settings 98 GUI Server 63
CVS 86 License Server 48
DSAs 86 Netcool/Impact 97
environment variables 90
installing 88
R
JRExec server 86
license feature codes 95 runtime parameters,using with nci_trigger 158
licensing 91
Operator View 86 S
server clustering 112
self-monitoring 138
shared memory requirements 88
setting up 147
system requirements 56, 83
viewing information 150
uninstalling 101
upgrading 91 server clustering 112

Index
components 113
shared memory requirements
Netcool/Impact 88
Netcool/Impact database 88
SQL Server DSA 187
Sybase DSA 189
U
uninstalling
GUI Server 78
License Server 51
Netcool/Impact 101
upgrading Netcool/Impact 91
V
version control 122
configuring 124
process 123

Index

Contact Information
backmatter.fm December 15, 2004
Corporate
Region Address Telephone Fax World Wide Web
USA Micromuse Inc. (HQ) 1-800-Netcool (638 2665) +1 415 538 9091 http://www.micromuse.com
139 Townsend Street
+1 415 538 9090
San Francisco
CA 94107
USA
EUROPE Micromuse Ltd. +44 (0) 20 8875 9500 +44 (0) 20 8875 9995 http://www.micromuse.co.uk
Disraeli House
90 Putney Bridge Road
London SW18 1DA
United Kingdom
ASIA-PACIFIC Micromuse Ltd. +61 (0) 8 9213 3400 +61 (0) 8 9486 1116 http://www.micromuse.com.au
Level 2
26 Colin Street
West Perth
Perth WA 6005
Australia
Technical Support
Region Telephone Fax
USA 1-800-Netcool (800 638 2665) +1 415 538 9091
+1 415 538 9090 (San Francisco)
EUROPE +44 (0) 20 8877 0073 (London, UK) +44 (0) 20 8875 0991
ASIA-PACIFIC +61 (0) 8 9213 3470 (Perth, Australia) +61 (0) 8 9486 1116
E-mail World Wide Web
GLOBAL support@micromuse.com http://support.micromuse.com
License Generation Team
E-Mail World Wide Web
licensing@micromuse.com http://support.micromuse.com/helpdesk/licenses

Contact Information

Netcool®/Impact: Frontmatter - FM December 15, 2004

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

Netcool®/Impact: Frontmatter - FM December 15, 2004

Uploaded by

Copyright:

Available Formats

Netcool®/ImpactTM

frontmatter.fm December 15, 2004

MMGuideTOC.fm December 15, 2004 10:15 am

Netcool/Impact User Interface Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Netcool/Impact Policy Reference Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Netcool/Impact Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Netcool/Impact Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Syntax and Example Subheadings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Operating System Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1: Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

How Do I Set Up an Installation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

How Do I Manage an Installation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Netcool Common License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Netcool Security Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Netcool/Impact 3.1 Administration Guide i

Creating a Netcool/Impact Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

How Do I Set Up Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 2: Netcool Common License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

What Are the Supported Configurations?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

What Are the License Server Components? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

How Do I Install Licenses?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

How Do I Run the License Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

How Do I Manage the License Server?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

ii Netcool/Impact 3.1 Administration Guide

License Server Service (Windows Platforms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Command Line Tools (UNIX Platforms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Setting the License Server Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Reading the Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Requesting the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Installing the License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Managing the License Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Viewing License Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Refreshing the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Viewing the License Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Netcool/Impact 3.1 Administration Guide iii

Managing the License Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Viewing License Server Status on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Refreshing the License Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Stopping the License Server on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Viewing the License Host ID on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Using the FLEXlm Command Line Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

How Do I Set Up a Quorum? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

How Do I Configure Netcool/Impact Components to Use a Quorum? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Uninstalling the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 3: Netcool GUI Server ....................................................... 53

How Do I Set Up the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

How Do I License the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Can I Run the GUI Server Under Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

How Do I Administer the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

License Server Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Web Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

iv Netcool/Impact 3.1 Administration Guide

GUI Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

GUI Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Running the GUI Server Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Verifying Port Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Reading the Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Licensing the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Running the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Starting the GUI Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65