Netcool®/ImpactTM

frontmatter.fm December 15, 2004

3.1

Administration Guide

© 2004 Micromuse Inc., Micromuse Ltd. All rights reserved. No part of this work may be reproduced in any form or by any person without prior written permission of the copyright owner. This document is proprietary and confidential to Micromuse, and is subject to a confidentiality agreement, as well as applicable common and statutory law. Micromuse Disclaimer of Warranty and Statement of Limited Liability Micromuse provides this document "as is", without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose or non-infringement. This document may contain technical inaccuracies or typographical errors. Micromuse may make improvements and changes to the programs described in this document or this document at any time without notice. Micromuse assumes no responsibility for the use of the programs or this document except as expressly set forth in the applicable Micromuse agreement(s) and subject to terms and conditions set forth 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 uninterrupted or error-free. Micromuse shall not be liable for any indirect, consequential or incidental damages arising out of the use or the ability to use the programs or this document. Micromuse specifically disclaims any express or implied warranty of fitness for high risk activities. Micromuse programs and this document are not certified for fault tolerance, and are not designed, manufactured or intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems ("High Risk Activities") in which the failure of programs could lead directly to death, personal injury, or severe physical or environmental damage. Compliance with Applicable Laws; Export Control Laws Use of Micromuse programs and documents is governed by all applicable federal, state and local laws. All information therein is subject to U.S. export control laws and may also be subject to the laws of the country where you reside. All Micromuse programs and documents are commercial in nature. Use, 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. Trademarks and Acknowledgements Micromuse and Netcool are registered trademarks of Micromuse. Other Micromuse trademarks include but are not limited to: Netcool/OMNIbus, Netcool/OMNIbus for Voice Networks, Netcool/Reporter, Netcool/Internet Service Monitors, Netcool/ISMs, Netcool/ISM Global Perspective, Netcool/NT Service Monitors, Netcool/Wireless Service Monitors, Netcool/WSMs, Netcool/Usage Service Monitors, Netcool/USMs, Netcool/Telco Service Monitors, Netcool/TSMs, Netcool/Fusion, Netcool/Data Center Monitors, Netcool DCMs, Netcool/Impact, Netcool/Visionary, Netcool/Precision, Netcool Probes & Monitors, Netcool Desktops, Netcool Gateways, Netcool Impact/Data Source Adaptors, Netcool EventList, Netcool Map, Netcool Virtual Operator, Netcool/Precision for IP Networks, Netcool/Precision for Transmission Networks, Netcool/Firewall, Netcool/Wave, Netcool/Webtop, Netcool TopoViz, Netcool/SM Operations, Netcool/SM Configuration, Netcool/OpCenter, Netcool/System Service Monitors, Netcool/SSMs, Netcool/Application Service Monitors, Netcool/ASMs, Netcool/ISM WAM, Netcool/SM Reporter, Netcool for Asset Management, Netcool/Realtime Active Dashboards, Netcool/Dashboards, Netcool/RAD, Netcool for Voice over IP, Netcool for Security Management, Netcool Security Manager, Netcool/Portal 2.0 Premium Edition, Netcool ObjectServer, Netcool/RAD, Netcool/Software Developers Kit, Micromuse Alliance Program, Micromuse Channel Partner, Authorized Netcool Reseller, Netcool Ready, Netcool Solutions, Netcool Certified, Netcool Certified Consultant, Netcool Certified Trainer, Netcool CCAI Methodology, Micromuse

University, Microcorrelation, Acronym, Micromuse Design, Integration Module for Netcool, The Netcool Company, VISIONETCOOL, and Network Slice. Micromuse acknowledges the use of I/O Concepts Inc. X-Direct 3270 terminal emulators and hardware components and documentation in Netcool/Fusion. X-Direct ©1989-1999 I/O Concepts Inc. X-Direct and Win-Direct are trademarks of I/O Concepts Inc. Netcool/Fusion contains IBM Runtime Environment for AIX®, Java™ Technology Edition Runtime Modules © Copyright IBM Corporation 1999. All rights reserved. Micromuse acknowledges the use of the UCD SNMP Library Netcool/ISMs. Copyright © 1989, 1991, 1992 by Carnegie Mellon University. Derivative Work - Copyright © 1996, 1998, 1999, 2000 The Regents of the University of California. All rights reserved. Portions of the Netcool/ISMs code are copyright ©2001, Cambridge Broadband Ltd. All rights reserved. Portions of the Netcool/ISMs code are copyright © 2001, Networks Associates Technology, Inc. All rights reserved. Micromuse acknowledges the use of Viador Inc. software and documentation for Netcool/Reporter. Viador © 1997-1999 is a trademark of Viador Inc. Micromuse acknowledges the use of software developed by the Apache Group for use in the Apache HTTP server project. Copyright © 1995-1999 The Apache Group. Apache Server is a trademark of the Apache Software Foundation (http://www.apache.org/). All rights reserved. Micromuse acknowledges the use of software developed by Edge Technologies, Inc. 2003 Edge Technologies, Inc. and Edge enPortal are trademarks or registered trademarks of Edge Technologies Inc. All rights reserved. Micromuse acknowledges the use of Merant drivers. Copyright © MERANT Solutions Inc., 1991-1998. The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RISC System/6000, Tivoli Management Environment, and TME10. IBM, NetView/6000 and WebSphere are either trademarks or registered trademarks of IBM Corporation. VTAM is a trademark of IBM Corporation. Omegamon is a trademark of Candle Corporation. Netspy is a trademark of Computer Associates International Inc. The Sun logo, Sun Microsystems, SunOS, Solaris, SunNet Manager, Java are trademarks of Sun Microsystems Inc. SPARC is a registered trademark of SPARC International Inc. Programs bearing the SPARC trademark are based on an architecture developed by Sun Microsystems Inc. SPARCstation is a trademark of SPARC International Inc., licensed exclusively to Sun Microsystems Inc. UNIX is a registered trademark of the X/Open Company Ltd. Sybase is a registered trademark of Sybase Inc. Action Request System and Remedy are registered trademarks of Remedy Corporation. Peregrine System and ServiceCenter are registered trademarks of Peregrine Systems Inc. HP, HP-UX and OpenView are trademarks of Hewlett-Packard Company. InstallShield is a registered trademark of InstallShield Software Corporation. Microsoft, Windows 95/98/Me/NT/2000/XP are either registered trademarks or trademarks of Microsoft Corporation. Microsoft Internet Information Server/Services (IIS), Microsoft Exchange Server, Microsoft SQL Server, Microsoft perfmon and Microsoft Cluster Service are registered trademarks of Microsoft Corporation. BEA and WebLogic are registered trademarks of BEA Systems Inc. FireWall-1 is a registered trademark of Check Point Software Technologies Ltd. Netscape and Netscape Navigator are registered trademarks of Netscape

Communications Corporation in the United States and other countries. Netscape's logos and Netscape product and service names are also trademarks of Netscape Communications Corporation, which may be registered in other countries. Micromuse acknowledges the use of Xpm tool kit components. SentinelLM is a trademark of Rainbow Technologies Inc. GLOBEtrotter and FLEXlm are registered trademarks of Globetrotter Software Inc. Red Hat, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat Inc. in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Nokia is a registered trademark of Nokia Corporation. WAP Forum™ and all trademarks, service marks and logos based on these designations (Trademarks) are marks of Wireless Application Protocol Forum Ltd. Micromuse acknowledges the use of InstallAnywhere software in Netcool/WAP Service Monitors. Copyright © Zero G Software Inc. 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

Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Expat Software. Expat's permission is subject to the following conditions: The above 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 software provided by Micromuse hereunder is subject to the applicable license agreement. Micromuse acknowledges that Netcool Security Manager includes Hypersonic SQL. Copyright (c) 2001-2002, The HSQL Development Group. All rights reserved. JABBER® is a registered trademark and its use is granted under a sublicense from the Jabber Software Foundation Micromuse acknowledges the use of MySQL in Netcool/Precision for IP Networks and in Netcool/Precision for Transmission Networks. Copyright © 1995, 1996 TcX AB & Monty Program KB & Detron All other trademarks, registered trademarks and logos are the property of their respective owners. Micromuse Inc., 139 Townsend Street, San Francisco, USA CA 94107 www.micromuse.com Document Version Number: 1.1

. . . . .. . . . . 8 Syntax and Example Subheadings . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 14 Netcool Security Manager . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Associated Publications . . . . . . . . .. . . . . . . . . 4 Netcool/Impact Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Netcool/Impact Online Help. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. 4 Netcool/Impact Web Services Guide . . .. .. . . . . . . . . . .. . .1 Administration Guide . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . 13 Installation Components. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . 4 Netcool/Impact Solutions Guide . . . . . . . . 9 Chapter 1: Getting Started . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . 12 What Are the Supported Installation Types? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Netcool/Impact . . . . . . . . . . . . .. .. . . . . . . . . . . . .. .. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . 14 Installation Architecture . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .Contents MMGuideTOC. . 14 Netcool GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 11 About Netcool/Impact Installations .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Operating System Considerations . . . . . . . 14 Netcool Common License Server.. . . . .. . . . . . . ... . . . . . . . . .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . . . . . . . . . . . . . . . . . . . . . .. . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 How Do I Set Up an Installation? . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . 2 About the Netcool/Impact 3. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . .fm December 15. . . . . ... . . . . . . .. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . and Warning Information . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . Tip. . . . . . . . . . . . . . . . . .. . . .. . . . . . . . . . . . . 1 Audience . . . . . .. . . .. . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . 6 Note. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 What Is a Netcool/Impact Installation? . .. . . . . . . . . . . . . . 15 Netcool/Impact 3.. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . . 5 Typographical Notation . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . 4 Netcool/Impact User Interface Guide . . . . . 2004 10:15 am Contents Preface . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .1 Administration Guide i . . . . 4 Netcool/Impact Policy Reference Guide . .. . . . . . . . .. . 12 How Do I Manage an Installation? . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Managing an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Licensing Components. . . . . 28 What Are the License Server Components? . . . . . . . . . . 18 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 How Do I Install Licenses?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 What Are the Supported Configurations?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 How Do I Set Up Process Control? . . . . . . . . . . 23 Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Installing Components. . . . 16 Setting Up an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 How Do I Run the License Server? . . . . . . . . . . . . . . . . . . . . . . . . 29 Can I Run the License Server Under Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 About the License Server . . . . . . . . . . . . . . . . . . . . . . . . . 20 Configuring Components . . . . . . . . . . . . . . . 19 Creating a Netcool/Impact Server Instance . . . . . . . . . . . . . . . . . . . . 30 ii Netcool/Impact 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Running an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 How Do I Set Up the License Server? . . . . . . . . . . . . . . . . . . . . . . . 16 Distributed Installation . . . . . . . . .1 Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Chapter 2: Netcool Common License Server . . . . . . . . 21 Running an Installation Under Process Control . . . . . 29 How Do I Manage the License Server?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Single System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 What Is the License Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Installation Types . . . . . . . . . . . . . . . . . . 18 Planning an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 What Is Process Control? . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Installing the License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Viewing the License Host ID . . . . . . . . . . . . . . . .1 Administration Guide iii . . . . . . . . . . . . . . . . . . . . 37 Verifying Port Settings. . . . . . . . . . . . . . . . . . . . . . . . .Contents System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Netcool/Impact 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Managing the License Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Installing the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Command Line Tools (UNIX Platforms) . . . . . . . . . . . . . . 39 Generating the License Host ID . . . . . . . . . . . 31 Licensing Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Stopping the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Installing Licenses . . 43 Viewing License Server Status . . . . . . . . . . . . . . . . . . . . . . . 33 License Server Service (Windows Platforms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Exceed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Requesting the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Refreshing the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Running the License Server Installer . . 38 Reading the Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 License Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Hardware Support . . . . . . . . 43 Starting the License Server . . . . 35 LMTOOLS (Windows Platforms). . . . . . . . . . . . . . . 36 Setting the License Server Environment Variables . . . . 39 Obtaining License Feature Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 License Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 License Server Daemons (UNIX Platforms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . .Contents Managing the License Server on Windows .. . . 47 Quorum Licensing . . . . . . . . . . . . . . 56 Java Support. . . . . . . . . 56 License Server Compatibility . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . . . . . . . . . . . . . 45 Starting the License Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . . . . . . 57 iv Netcool/Impact 3. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . 55 How Do I Administer the GUI Server? . . . . . . . . . . . . . . . . . . . . 45 Refreshing the License Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . 56 Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . . . . . . 46 Viewing the License Host ID on Windows . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . 49 Uninstalling the License Server . . . . . . . . . . . . .. . . . . . . 53 About the GUI Server . . . . . . . . . . . . . . . . . . . . . . . 51 Uninstalling on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 57 Hardware Requirements. . . 55 How Do I Run the GUI Server? . . . . . .. . . . . . . 54 How Do I Set Up the GUI Server? . . . . .. . . . 45 Stopping the License Server on Windows. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . 48 What Is Quorum Licensing? . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 How Do I Set Up a Quorum? .. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Uninstalling on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 How Do I Configure Netcool/Impact Components to Use a Quorum? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 54 How Do I License the GUI Server? . . .. . . .. . . 46 Using the FLEXlm Command Line Tools . . . . . . . . . 54 What Is the GUI Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Can I Run the GUI Server Under Process Control? . . . .. . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 57 Web Browser Support . . . . . . 45 Viewing License Server Status on Windows . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Security Manager Requirements. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . . . . . 51 Chapter 3: Netcool GUI Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . .1 Administration Guide . . . . . 57 Exceed Limitations. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 55 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 GUI Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Installing the Java Development Kit (AIX and HP-UX Only) . . . 62 Verifying Port Settings. . . . . . . . . . . . 76 GUI Server Logging . . . . . . . . . . . . . . . . . . 77 Netcool/Impact 3. . . . . . . . . . 60 Setting the GUI Server Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Licensing the GUI Server . . . . . . 60 Running the GUI Server Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 What Is Registry Clustering? . . . . . . . . . . . . . . . . . . . . . . . . 59 Installing the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Configuring Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Configuring Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Licensing Requirements . . . . . . . . . . . 66 Configuring the Registry . . . . . . . . . . . . . . 68 What Are the Clustering Components? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Stopping the GUI Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Starting the GUI Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Administration Guide v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 How Do I View Registry Status? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Configuring the Servlet Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Configuring the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . 58 Servlet Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Registry Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents GUI Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Quorum Licensing. . . . . . . . . . 69 How Do I Run a Registry Cluster?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 How Does Registry Clustering Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Application Registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Reading the Installation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 How Do I Set Up Registry Clustering? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Stopping the GUI Server on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Running the GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Starting the GUI Server on Windows . . . . . . . . . . . . . . . . . . . . .

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

. . . . . . . . . . . . . . . . 101 Uninstalling on Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 What Is the Netcool/Impact Server? . . . . . . . . 90 Verifying Port Settings. . . . 100 Uninstalling Netcool/Impact . . . . . . . . . . . 105 How Do I Run a Server Instance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 95 Licensing Requirements . . . . . . . . . 91 Upgrading from Netcool/Impact 2. . . . . . . . . . 103 About the Netcool/Impact Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Backing Up and Restoring Netcool/Impact . . . . . . . . . . . . .Contents Installing Netcool/Impact . . . . 90 Reading the Installation Log . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 105 How Do I Monitor a Server Instance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Quorum Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 93 Licensing Netcool/Impact . . . . . . . . . . . . . . . . 101 Uninstalling on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Administration Guide vii . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Configuring Licensing . . . . .. . . . . .. . . . .. . . . . . . . . . . . . . . . . 104 How Do I Set Up a Server Instance? . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . . . . . . 104 What Are the Supported Server Configurations? . . . . . . . . . . . . . . . . .. . . . . . . . . . . 101 Chapter 5: Netcool/Impact Server . . . . . . . . . .. . . . . . . . 106 Netcool/Impact 3.. . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 104 What Is a Server Instance? . . . . . . . . . .. . . . . . . . . . . . . . . . . 90 Upgrading Netcool/Impact . . . . . . . .. . . . . . . . . . . 88 Configuring the Operating System Kernel (UNIX Only). . . . . . . . . . .. . . . . 88 Setting the IMPACT_HOME Environment Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Upgrading from Netcool/Impact 3. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . . . . . . . . . . . . . . 98 Configuring Authentication . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Running the Netcool/Impact Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Configuring Registry Settings . . . . . . . .. . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . 105 Creating Server Instances . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .0 . . . . . . . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . .. . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Secondary Servers. . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Event Processing . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 What Is Server Clustering? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Event Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Running the Remove CVS Archives Script. . .. 109 Deleting Server Instances . . . . . . . . . . . . . . . .Contents Running Server Instances on UNIX . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Stopping Netcool/Impact on Windows . . . . . 115 Setting Up a Server Cluster . . . . . . . . . . . . . ... . . . . . 116 Configuring a Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . 112 How Do I Set Up Server Cluster? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Stopping Netcool/Impact on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Installing a Server Cluster. 112 What are the Clustering Components?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Clustering Components . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . 110 Chapter 6: Netcool/Impact Server Clustering . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . 113 Primary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Starting Netcool/Impact on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 116 viii Netcool/Impact 3. . . . . . . . . . . 107 Starting Netcool/Impact on UNIX . . . . . . . . . . . . . . . . . . .. . . . . . . . . 113 How Server Clustering Works. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Monitoring Server Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 About Server Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Running the Remove Server Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . 107 Running Server Instances on Windows . . . . . . . . . . . . . . . . 112 How Does Clustering Work? . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Setting PostgreSQL Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Element Renaming . . . . . 128 Running the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 How Do I License the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Starting a Cluster Member. . . . . . . . . . . . . . . . . . . 124 Chapter 8: Netcool/Impact Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Stopping the Database on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Element Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 What is the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Stopping a Cluster Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 How Version Control Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Stopping the Database on UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Cygwin Limitations . . . . . . . . . . . . . . . . 129 Netcool/Impact 3. . . . . . . . . 119 Chapter 7: Netcool/Impact Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 How Do I Run the Database? . . . . 123 Element Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Starting the Database on UNIX Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Starting the Database on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 How Do I Manage the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Setting the Database Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Administration Guide ix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 How Do I Set Up the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 About the Database. . . . . . . . . . . . . . . . . 121 About Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Check Out. . . . . . . 127 Configuring the Database . . . . . . . . . 123 Check In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Running a Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Configuring Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . .. . . . . . . . . . . . . .. . . . . . . . .. 133 About the JRExec Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Administration Guide . 134 How Do I Run the JRExec Server?. . . . . . . . . . . . . . . . . . . . . . 135 Stopping the JRExec Server on UNIX .. . . . . . . . . . . . . . . . . 139 How Do I Manage Netcool/Impact Events?. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 How Do I Configure the JRExec Server? .. . 131 Chapter 9: Netcool/Impact JRExec Server . . . . . . . . . . . . . . . . . . 135 Starting the JRExec Server on UNIX . . . . . . . . . . . . . . .. . . . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . 130 Resetting the Database . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . . . . . . . . . . . . .. . . .Contents Managing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Starting the JRExec Server on Windows . . 138 How Does Self-Monitoring Work with a Netcool/Impact Cluster? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Viewing the Database Status . . . . . . . . . . 138 How Do I Set Up Self-Monitoring? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Connecting to the Database with the Command Line Client. . . . . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . . 135 Configuring the JRExec Server . . . . . 134 Running the JRExec Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Backing Up the Database . . . . . . .. . . . . . . . . . . . . . . . . . 137 About Netcool/Impact Self-Monitoring .. . . . . . . . . . . . . . . . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Chapter 10: Netcool/Impact Self-Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . 134 How Do I Set Up the JRExec Server?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Can I Run the JRExec Server Under Process Control? . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . 139 x Netcool/Impact 3. . . . . . . . . . . . .. . . . . . . . . 134 What Is the JRExec Server? . . . . . . . . . . 138 How Does Self-Monitoring Work? . . . . . . . . . . . 135 Stopping the JRExec Server on Windows . . . . . . . . . . . . . . .. . . . . . . . . . . 138 What Is Self-Monitoring?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . . . . 131 Restoring the Database. . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 ObjectServer Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Memory Status Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Queue Size Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Memory Status Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Deduplication Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Queue Status History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Netcool/Impact 3. 150 Memory Status History . . . . . . . . . . . . . . . 151 Maximum Required Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Maximum JVM Heap Size. . . . . . . . . . . . . . . . . . . . 152 Chapter 11: Command Line Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Setting Up Self-Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 nci_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Queue Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 nci_crypt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Setting Up Self-Monitoring Using the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Queue Status Event Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Available System Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Viewing Information About Self-Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Monitoring Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Queue Status Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Setting Up Self-Monitoring Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Available JVM Heap Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 nci_import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Administration Guide xi . . . . 141 Memory Event Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 About Memory Status Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Current JVM Heap Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 About Queue Size Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . 168 Configuring AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 UNIX Kernel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Special Considerations . . . . . . . . . . . . . . . . . 174 Data Type Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Data Source Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Appendix B: DSA Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 About the Built-In DSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Windows Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Configuring HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents nci_trigger . . . . . . . . . . . . . . . . . . . . 173 Flat File DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Netcool License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Data Source Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Netcool GUI Server . . . . . . . . . . . . . 164 Netcool/Impact Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Runtime Parameters. . . . . . . . . . . . . . . . 170 DB2 DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Appendix A: Supplementary Information . . . . . . . . . . . 174 File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Firewall Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 UNIX Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Netcool Security Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 SQL Database DSAs . . . . . . . . . . . . 167 Configuring Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 JDBC Driver Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Netcool/Impact . . . . . . . . . . . . . . 175 xii Netcool/Impact 3. . . . . . . . 172 Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Configuring Red Hat Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . 182 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 PostgreSQL DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 ODBC DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 JDBC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 JDBC Driver Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Data Source Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . 183 Data Source Configuration Properties . . . . . . . . . . . . . . . 186 SQL Server DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 ObjectServer DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 JDBC Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Special Considerations . . . . . . . . . . . . . . . . . . 178 Data Source Configuration Properties . . . . . . . 187 Data Types . . . . . . . . . . . . . . . . .1 Administration Guide xiii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Data Source Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 JDBC Version . . .Contents Informix DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Netcool/Impact 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 JDBC Version . . . . . . . . . . . 177 MySQL DSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 JDBC Driver Version . . . . . 176 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Special Considerations . . . . . . . . . . . . . . 180 Supported Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Oracle DSA . . . . . . . 185 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Data Source Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . 180 Data Source Configuration Properties . . . . . . 183 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 xiv Netcool/Impact 3. 190 Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Data Source Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Sybase DSA . . . . . . . . .1 Administration Guide . . . . . . . . . . . . . . 189 Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Supported Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Administration Guide 1 . 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.fm December 15.Preface 00_Preface.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.

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

1 Administration Guide 3 .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 Netcool/Impact 3.1 Administration Guide About the Netcool/Impact 3.

It is intended for users who are responsible for writing and running Netcool/Impact policies. working with services and developing policies. It also provides a complete policy language reference.Preface Associated Publications Netcool/Impact 3. operators and functions. It contains complete information about policy language syntax. It contains information on setting up a data model. It is intended for all Netcool/Impact users. data types. 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.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. This guide is intended for all Netcool/Impact users. Netcool/Impact User Interface Guide This guide provides step-by-step instructions on using the Netcool/Impact user interface. Netcool/Impact Policy Reference Guide This guide contains reference information about the Netcool/Impact Policy Language (IPL). Netcool/Impact Online Help This online help system provides step-by-step instructions on using the Netcool/Impact user interface. 4 Netcool/Impact 3.1 Administration Guide . This guide is intended for Netcool/Impact administrations and for other users who are responsible for implementing Netcool/Impact.

1 Administration Guide 5 . Netcool/Impact 3.Associated Publications Netcool/Impact Release Notes This guide provides information about new features. system requirements and known issues for this version of Netcool/Impact.

path. and graphical user interface (GUI) features. This notation is used throughout this book and other Netcool® publications. 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. -password password. Italic The following are described in an italic font style: • • • • An application window name. the Login window Information that the user must enter The introduction of a new term or definition Emphasized text 6 Netcool/Impact 3. and directory names Italicized monospace text indicates a variable that the user must populate. Table 1: Typographical Notation and Conventions (1 of 2) Example Monospace Description 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. For example. For example.Preface Typographical Notation Table 1 shows the typographical notation and conventions used to describe commands. File→Save. SQL syntax. for example.1 Administration Guide .

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

! 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. 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. or critical information. cautions. For example. when describing an installation process. Tip. For example: CREATE DATABASE database_name. this is for extra data that is important but not vital to the user. there might be a shortcut that could be used instead of following the standard installation instructions. Tip: Tip is used for additional information that might be useful for the user.1 Administration Guide . as they contain information that is vital to the successful use of our products. Essentially. Example Example subheadings describe typical or generic scenarios. For example: [1] [2] [3] [4] [5] [6] <body> <img src="ChartView?template=barchart&format=PNG &request=image&chart=quote&width=800&height=400" border="0" height="400" width="800" alt="Events by Severity" > </body> 8 Netcool/Impact 3. Warning: Warning is used for highlighting vital instructions. or samples of code. Pay close attention to warnings.Preface Note.

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

1 Administration Guide .Preface 10 Netcool/Impact 3.

1 Administration Guide 11 .fm December 15. It contains the following sections: • • • • • • • • 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 Netcool/Impact 3.Chapter 1: Getting Started 01_Getting_Started. 2004 10:15 am This chapter contains the information you need to get started with a Netcool/Impact 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. For more information. You can then plan how you want to install the product based on your requirements. How Do I Set Up an Installation? Before you set up an installation. 12 Netcool/Impact 3. see Installation Components on page 14. After you finish planning. The components of an installation are: • • • • Netcool/Impact Netcool Common License Server Netcool Security Manager Netcool GUI Server For more information. you must first understand your environment and your goals for Netcool/Impact.Chapter 1: Getting Started 1.1 About Netcool/Impact Installations This section contains overview information about Netcool/Impact installations.1 Administration Guide . Single system installations consist of Netcool/Impact and its related software components installed on a single target system. What Are the Supported Installation Types? Netcool/Impact supports both single system and distributed installations. license and configure the installation components on the appropriate target systems. 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. see Installation Types on page 16. For more information. you can install. see Setting Up an Installation on page 18.

Netcool/Impact also provides web-based GUIs that you can use to perform administration tasks. Netcool/Impact 3.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 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. In addition.1 Administration Guide 13 .

you can use Netcool/Impact to integrate Netcool/OMNIbus with a wide variety of third party software. Netcool/Impact is the primary component of the installation. For more information on the Netcool GUI Server. Netcool Security Manager The Netcool Security Manager provides user authentication for Netcool/Impact and the Netcool GUI Server. In addition. Netcool Common License Server The Netcool Common License Server provides licensing functionality for Netcool/Impact. including databases.Chapter 1: Getting Started 1. see the Netcool Security Manager Administration Guide. see Chapter 3: Netcool GUI Server on page 53. messaging systems and network inventory applications. For more information on the Netcool Security Manager. 14 Netcool/Impact 3.1 Administration Guide .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. the Netcool Security Manager and the Netcool GUI Server. 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. see Chapter 2: Netcool Common License Server on page 27. see Chapter 4: Netcool/Impact on page 79. For more information on the Netcool Common License Server. 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 Netcool/Impact. event enrichment and event notification.

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

Chapter 1: Getting Started 1. 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. which can be shared between multiple Netcool products.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. Netcool Security Manager and the Netcool GUI Server. The Netcool Common License Server. 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. 16 Netcool/Impact 3. are located on one or more separate systems. Single server installations are not recommended for live production environments.1 Administration Guide . This type of installation is suitable for testing and demonstrating Netcool/Impact. This type of installation is the most common and offers the highest degree of flexibility and customization for live production environments.

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

For real-life production installations.Chapter 1: Getting Started 1. Planning an Installation After you understand how Netcool/OMNIbus and other Netcool products are installed and used in your environment. devices and applications that exist on the network and how they are monitored by Netcool/OMNIbus. This type of installation requires little planning and is the easiest to create and maintain. It contains the following topics: • • • • • • 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.5 Setting Up an Installation This section contains general information on setting up a Netcool/Impact installation. you must take into account your goals. Micromuse recommends that you install Netcool/Impact and its components on a single system. You must also have an understanding of your network topology. 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. including the types of systems. Specifically. you must have an understanding of how Netcool/OMNIbus and other Netcool products are installed and used in your environment. you can plan your Netcool/Impact installation.1 Administration Guide . requirements and available resources before you install the software. 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. For testing or demonstration purposes. Micromuse recommends that you create a diagram of the installation you want to create before you begin. 18 Netcool/Impact 3.

the Security Manager and the GUI Server are compatible with the Netcool/Impact 2. For more information. 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. You can print and use the sample worksheet included in the Appendix A: Supplementary Information on page 161. In console mode. In GUI mode. 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. you must run the installer in console mode. the installers prompt you for required information from the command line. Netcool/Impact and its components provide installer programs that you can run in GUI mode or in console mode. the installers present a series of graphical windows that guide you through the installation process. Micromuse recommends that you prepare a worksheet and record the information that you provide to the installer programs. you do not need to install another instance for use with Netcool/Impact. Netcool/Impact 3. the Security Manager or the GUI Server for use with another Netcool product. If you are running the installer remotely using telnet or another command line application.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. see Licensing the Security Manager in the Security Manager Administration Guide.3 license server and the Netcool Common License Server. For more information.1 Administration Guide 19 . or create your own. Licensing the GUI Server on page 63 and Upgrading Netcool/Impact on page 91. Installing Netcool/Impact on page 88 Licensing Components Netcool/Impact.

see Creating Server Instances on page 106. you must create a new instance of the Netcool/Impact server.1 Administration Guide . Depending on the component. 20 Netcool/Impact 3. Netcool/Impact provides a program named nci_new_server that guides you through the instance creation process.Chapter 1: Getting Started Creating a Netcool/Impact Server Instance After you have installed Netcool/Impact and its related software components. you might need to stop and restart after making configuration changes. You can change the configuration of a component at any time by manually editing the properties files. 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. Configuring Components The installer programs set the minimum required configuration properties during installation.

1 Administration Guide 21 . Table 3: Netcool/Impact Windows Services (1 of 2) Component License Server GUI Server Security Manager Service Name Netcool License Server Netcool GUI Server Netcool Security RMI. Netcool Database (Security). you must use the Windows Services Administration tools. The following table shows the commands for starting the components on UNIX platforms. Netcool/Impact and its related components run as Windows services. Netcool Security Manager Netcool/Impact 3. Table 2: Netcool/Impact Component Commands Component License Server GUI Server Security Manager Netcool/Impact Command $NCLICENSE/bin/nc_start_license $GUI_HOME/bin/ncgui_server $SM_HOME/bin/ncsm_server $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.Running an Installation 1. To start and stop these programs. The following table shows the names of the Windows services.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 License Server also provides a Windows program called LMTOOLS that you can use to start and stop the server.

Chapter 1: Getting Started Table 3: Netcool/Impact Windows Services (2 of 2) Component Netcool/Impact Service Name Netcool Impact server where server is the name of the server instance. Netcool Database (Impact) 22 Netcool/Impact 3.1 Administration Guide .

the Netcool Common License Server. It contains the following topics: • • • 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. How Do I Set Up Process Control? To set up process control.1 Administration Guide 23 . After you have installed the process control manager. you must install the process control manager on each system in your environment where you are running Netcool/Impact and its related components. For additional information on process control. For instructions on installing the process control manager and setting up process control in your environment.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. see the Netcool/OMNIbus Administration Guide. 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.conf file on each system. see the Netcool/OMNIbus Administration Guide. you must edit the nco_pa. Use of process control with Netcool/Impact is optional. Netcool/Impact. Netcool/Impact 3. the Netcool Security Manager and the Netcool GUI Server run as "non-pa aware" applications.

’ RetryCount=3 ProcessType=PaNOT_PA_AWARE } 24 Netcool/Impact 3. Real-world configuration files will differ depending on how you have installed and configured your installation.1 Administration Guide .’ 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 Impact Server NCI has gone down. 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 GUI Server has gone down.’ AlertMsg=’The Security Manager has gone down.’ RetryCount=3 ProcessType=PaNOT_PA_AWARE } nco_process ’SecurityManager { Command ’$SM_HOME/bin/ncsm_server’ run as impact Host=’HOST_01’ Managed=true RestartMsg=’The Security Manager has restarted.conf configuration file that shows the process definitions for Netcool/Impact and its related components.’ RetryCount=3 ProcessType=PaNOT_PA_AWARE } 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.Chapter 1: Getting Started Sample Configuration File The following is a sample nco_pa.’ AlertMsg=’The License Server has gone down.

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.1 Administration Guide 25 . 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. Netcool/Impact 3. In addition.

1 Administration Guide .Chapter 1: Getting Started 26 Netcool/Impact 3.

It contains the following sections: • • • • • • • • • • • 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 Netcool/Impact 3.fm December 15.0b21.1 Administration Guide 27 .Chapter 2: Netcool Common License Server 02_License_Server. 2004 10:29 am This chapter contains information on the Netcool Common License Server 1.

1 About the License Server This section contains overview information about the License Server. The License Server is based on FLEXlm licensing technology.macrovision.2.com.0 and Netcool Security Manager 1. see the FLEXlm End User’s Guide. What Are the Supported Configurations? Netcool/Impact 3. Version 1.0b21 of the License Server incorporates FLEXlm version 9. For more information on quorum licensing.2 support both single-server and quorum configurations of the License Server. Previous versions of these components supported only single-server configurations. 28 Netcool/Impact 3. FLEXlm is a product of Macrovision Corporation. see Quorum Licensing on page 48.1 Administration Guide . You must also install licenses for Netcool/Impact and for the Security Manager before you run these components. see System Requirements on page 31. This guide is available from the Macrovision website at http://www. For more information. For more information on FLEXlm. The License Server is supported on all the platforms that are supported for Netcool/Impact and the Netcool Security Manager. you do not need to install a new one for use with Netcool/Impact. If you are already running a License Server in your environment.1. Netcool GUI Server 2. It contains the following topics: • • • • • • • • 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.Chapter 2: Netcool Common License Server 2. You must install and configure a License Server before you run Netcool/Impact or the Netcool GUI Server.

Then. The License Server runs as a “non-pa aware” application. How Do I Set Up the License Server? Before you set up the License Server. The installation files include the License Server installer and a README file. you can use the Windows services administration tools or the LMTOOLS program. There is no need to pass the -z command line argument to the startup script as in previous versions. For more information. You can view the installation log to see if the process has completed successfully. The URL for the Micromuse Technical Support website is http://support.1 Administration Guide 29 . For more information. The License Server runs by default as a foreground process.com.micromuse. you copy the license file to the target system and request a license file refresh from the License Server. On UNIX platforms. you must first obtain the installation files from the Micromuse Product CD-ROM or as a download from the Micromuse Technical Support website. you must set the required environment variables after installation. Netcool/Impact 3. Can I Run the License Server Under Process Control? You can run the License Server under process control with no special considerations. How Do I Install Licenses? Before you install licenses in the License Server. see Installing the License Server on page 36. you must first generate the license host ID for the system where the License Server is running. license files and a collection of license tools that you can use to manage licensing in your environment. you run the installer and follow the on-screen prompts. To install the licenses. For more information. For more information. see License Server Components on page 33. see Managing the License Server on UNIX on page 43 and Managing the License Server on Windows on page 45. How Do I Run the License Server? On UNIX platforms.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). On Windows platforms. you request a license file from Micromuse Technical Support. The installer sets all of the required configuration properties. you start and stop the License Server using the server administration scripts. see Installing Licenses on page 39. To install the License Server.

refresh licenses and perform other related tasks. 30 Netcool/Impact 3. see Managing the License Server on UNIX on page 43 and Managing the License Server on Windows on page 45. view license usage. On Windows platforms.Chapter 2: Netcool Common License Server 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 also use the LMTOOLS program. You can use these tools to view the License Server status. This program allows you to perform all of the management functionality provided by the command line tools. For more information.1 Administration Guide .

1 Administration Guide 31 . Platform Support The License Server is supported on the following platforms: • • • • • Sun Microsystems Solaris 7.00 Hardware Support Hardware requirements for the License Server vary depending on your environment and license usage. Netcool/Impact 3. Exceed Issues Micromuse does not recommend the use of Hummingbird Exceed with the License Server installer program.0 and Enterprise Server 3. License files are not backward compatible between versions. This includes the Netcool Common License Server. 8 and 9 Red Hat Linux 9. Micromuse recommends that you use the most recent FLEXlm-enabled license server available. contact your Micromuse account manager or Micromuse Technical Support. the Netcool/Impact 2.System Requirements 2. Under some conditions.1 and 5. For recommendations on hardware sizing for the License Server. the license agreement text displayed by the installer program is not legible when viewed inside Exceed.0 Microsoft Windows 2000 Server.5 and later.2 System Requirements Make sure that the target system fulfills the requirements in this section before installing the License Server.3 license server and the license server distributed with Netcool/OMNIbus 3. Limitations You can run only one FLEXlm-enabled Netcool license server per machine. You must read the full text of the license agreement and accept the terms of the agreement before installing this software. Windows XP and Windows 2003 Server IBM AIX 5L (5.2) Hewlett-Packard HP-UX 11.

other Netcool applications and the License Server.3 Licensing Architecture The following figure shows the relationship between Netcool/Impact.1 Administration Guide .Chapter 2: Netcool Common License Server 2. Netcool/RAD Netcool/OMNIbus Netcool Common License Server Other Netcool Applications Netcool/Impact Figure 3: Netcool Licensing Architecture 32 Netcool/Impact 3.

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. These daemons provide the licensing functionality for the server. License Server Service (Windows Platforms) On Windows platforms. License Files License files are text files that contain licenses for the License Server.exe. Netcool/Impact 3. By default. the License Server runs as a service named lmgrd. You can also run the service using the LMTOOLS program.lic. The default name for license files is license. the FLEXlm daemon and the vendor daemon. The vendor daemon is named netcool. You run the lmgrd and netcool daemons using the License Server script. You run the lmgrd. This daemon is responsible for the core operations of the License Server. following instructions provided in the FLEXlm documentation.1 Administration Guide 33 .License Server Components 2. license files are located in the $NCLICENSE/etc directory. 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.exe daemon using the Services Administration tools provided by Windows.lic as a license file.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. You can also launch the daemons manually from the command line. the License Server has two daemons. The License Server recognizes any file with a name that ends in . The FLEXlm daemon is named lmgrd. The License Server supports an unlimited number of license files.

The ck and SIGN attributes are used by the License Server for license validation. exp_date is the expiration date for the licenses and number is the number of licenses available.Chapter 2: Netcool Common License Server 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. including number of licenses and the license expiration date. 34 Netcool/Impact 3. 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.1 exp_date number ck SIGN where feature is a Netcool license feature code. Vendor Line The vendor line identifies the vendor providing the licenses. Feature lines appear in the license file in the following format: FEATURE feature netcool 3. The license file contains one feature line for each licenseable Netcool component or feature.1 Administration Guide .

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. For more information. see Managing the License Server on UNIX on page 43.0 31-Dec-2005 2 ck=174 \ SIGN=30DC95B86230 FEATURE cro_nci_objserv_dsa netcool 4. You can use LMTOOLS to perform all of the management functionality provided by the command line tools. For more information. the License Server provides a program called LMTOOLS that you can use to manage licensing. These tools are located in the $NCLICENSE/bin directory. You can use these tools to view the server status. see Managing the License Server on Windows on page 45.1 Administration Guide 35 . You can also use LMTOOLS to start and stop the License Server.0 31-Dec-2005 2 ck=185 \ SIGN=C39E61ACFE2D FEATURE cro_nci_mysql_dsa netcool 4.0 31-Dec-2005 2 ck=221 \ SIGN=A2D69708434E FEATURE cro_nci_client netcool 4. LMTOOLS (Windows Platforms) On Windows platforms. refresh licenses and perform other related tasks.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 4 ck=199 \ SIGN=939730F86748 FEATURE cro_nci_eventbroker netcool 4. Netcool/Impact 3. view license usage.

This script automatically restarts the License Server at system startup. the default is /opt/netcool/common/license.1 Administration Guide .gz. you do not need to create a separate installation for use with Netcool/Impact. UNIX only. write and execute permissions to the target directory. The installer is a script named license_install. Running the License Server Installer The License Server installer copies the program files to the target system and sets the minimum required configuration properties.5 Installing the License Server To install the License Server. Copy startup script 36 Netcool/Impact 3. On UNIX platforms. On Solaris. the installer is a setup program named licensemgr. On Windows 2000. where ver is the version and build number of the package. Micromuse recommends that you do not install the License Server as user root.msi. the License Server is distibuted as a zipped tar file named license_ver. On Windows platforms. or to troubleshoot installation errors. the default is /usr/netcool/common/license. 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.tar. You can choose whetherto copy a startup script into the init. If you are already running the License Server in your environment.d directory. Red Hat Linux. On AIX. the default is C:\Program Files\Netcool\Common\License.Chapter 2: Netcool Common License Server 2. This script is located in the root level of the tar file. you can read the installation log to verify that the software has been installed correctly. and HP-UX. The License Server installer prompts you for the following information: Table 4: Netcool Common License Server Installer Prompts Prompt Installation directory Description The directory where you want to install the License Server. You can run the installer as any other user that has read. You can run the installer by double-clicking the program icon in Windows Explorer.

Enter the following: . Setting the License Server Environment Variables If you are installing the License Server on a UNIX platform. On AIX systems. Follow the on-screen prompts. 2.tar. On Solaris. 2. NCLICENSE The NCLICENSE variable specifies the location where you installed the License Server.Installing the License Server To run the License Server installer on UNIX platforms: 1./license_install 4. At a command line prompt. HP-UX and Red Hat Linux systems. Follow the on-screen prompts.gz where ver is the version and build number of the License Server. you must set the NCLICENSE and NETCOOL_LICENSE_FILE environment variables.1 Administration Guide 37 . change the current directory to the directory where the install package is located. Enter the following: tar -xvzf license_ver. The following example shows how to set NCLICENSE using sh or bash: NCLICENSE=/opt/netcool/common/license. the default location is /usr/netcool/common/license. 3. export NCLICENSE The following example shows how to set NCLICENSE using csh: setenv NCLICENSE /opt/netcool/common/license Netcool/Impact 3. the default location is /opt/netcool/common/license.msi by double-clicking the file in Windows Explorer. To run the License Server installer on Windows platforms: 1. Launch licensemgr.

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. 38 Netcool/Impact 3. or you are running the License Server on a Windows machine with a built-in firewall. Reading the Installation Log The License Server installation log is named License_Manager_InstallLog. this location is $NCLICENSE/etc.1 Administration Guide . You can also use it to troubleshoot installation problems. the GUI Server or the Security Manager by a firewall.Chapter 2: Netcool Common License Server NETCOOL_LICENSE_FILE The NETCOOL_LICENSE_FILE specifies the location of Netcool license files on your system. 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. 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.log and is located in the $NCLICENSE directory. By default.

The License Server installer automatically generates a host ID and stores it in a file named hostid. This file is located in the $NCLICENSE/log directory. you must provide the license host ID for the system where the License Server is running. You can generate the host ID at any other time by running the nc_hostid script (UNIX platforms) or the lmhostid command (Windows platforms).04 (15-OCT-2002 11:20:01) ---OUTPUT-BEGIN--Version: v1.1 Administration Guide 39 . The lmhostid command is located by default in the C:\Program Files\netcool\common\license\bin directory. The nc_hostid script is located in the $NCLICENSE/bin directory.6 Installing Licenses To install Netcool licenses.Installing Licenses 2. 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. Sample UNIX License Host ID The following example shows sample output from the nc_hostid script: nco_hostcode v1.out.04 Time: 1046691321 cksum: 0024dcf3 3b25306b35266925050112110401056820544f55783721100d0e1b07043c 5054575746504c50426b2b0616055d1b6d2a505d534c4357594c41554844 535363240b0c14160407166b2517194f02101545040704110e091411174f 020d1f6b362636253e42320f1516004f44516b2a4a52564452580d596d26 090904524851515241030745525a5a0a504f505d534c4357594c41554844 5353455c52564f5654575c53555a5c516c360d51594234595551514e015b 0e0c5f0d0f1b06471d541413001602144b4d075801110707001d5064240d 5b564d31485554525e125c1a0d46050709064d105b110200130104584a13 5918190f1500175d6b2944556b243b2f6c Netcool/Impact 3.

Netcool/Impact License Feature Codes The following table shows the license feature codes for Netcool/Impact. you must provide the code for each feature that you want to license.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. Table 5: Netcool/Impact License Feature Codes (1 of 2) Component Netcool/Impact server Netcool/Impact client Event reader Operator view ObjectServer DSA LDAP DSA Oracle DSA MySQL DSA Microsoft SQL Server DSA Flat File DSA Informix DSA DB2 DSA PostgreSQL DSA Sybase DSA Code cro_nci_server cro_nci_client cro_nci_eventreader cro_nci_opview cro_nci_objserv_dsa cro_nci_ldap_dsa cro_nci_oracle_dsa cro_nci_mysql_dsa cro_nci_freetds_dsa cro_nci_flatfile_dsa cro_nci_informix_dsa cro_nci_db2_dsa cro_nci_postgres_dsa cro_nci_sybase_dsa 40 Netcool/Impact 3.1 Administration Guide .Chapter 2: Netcool Common License Server Sample Windows Host ID The following example shows sample output from the lmhostid command: lmhostid .

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

lic. send an e-mail to Micromuse Technical Support at support@micromuse.1 Administration Guide .lic extension. Micromuse will reply with an e-mail that contains a license file named license.lic already exists. You must attach the license host ID and the license feature codes to the e-mail.com. give the license file a unique name with the . 42 Netcool/Impact 3.lic extension before copying.Chapter 2: Netcool Common License Server Requesting the License File To request a license file. After verifying your license request. Installing the License File Copy the license file to the $NCLICENSE/etc directory. If a file named license. The License Server reads all files in the $NCLICENSE/etc directory that have the .

you run the nc_read_license script.Managing the License Server on UNIX 2. see the Netcool/Impact Reference Guide. Starting the License Server To start the License Server on UNIX platforms. These scripts are located in the $NCLICENSE/bin directory. enter the following at a command line prompt: $NCLICENSE/bin/nc_read_license Netcool/Impact 3. This script launches the License Server and causes it to read all of the license files located in the $NCLICENSE/etc 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. 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. you run the nc_print_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.1 Administration Guide 43 . enter the following at a command line prompt: $NCLICENSE/bin/nc_print_license Refreshing the License Server To refresh the License Server. To run the nc_print_license script. To run the nc_start_license script. This script prints the server status and information on license usage to the standard output.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. you run the nc_start_license script.

you run the nc_hostid script. You use the host ID when you request licenses from Micromuse Technical Support. you run the nc_stop_license script.1 Administration Guide .Chapter 2: Netcool Common License Server Stopping the License Server To stop the License Server. 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. To view the license host ID. To run the nc_hostid script. enter the following at a command line prompt: $NCLICENSE/bin/nc_hostid 44 Netcool/Impact 3. To run the nc_stop_license script.

3. 2. 3. Click the Start Service button. Click the Perform Status Enquiry button. Click the ReRead License File button. 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. Viewing License Server Status on Windows To view the status of the License Server and to view information on license usage: 1. Launch LMTOOLS from the Windows Start Menu. Launch LMTOOLS from the Windows Start Menu.1 Administration Guide 45 . Launch LMTOOLS from the Windows Start Menu.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. 3. 2. Netcool/Impact 3.Managing the License Server on Windows 2. Click the Start → Stop → Reread tab in the LMTOOLS window. Click the Start → Stop → Reread tab. 2. Click the Server Status tab in the LMTOOLS window. Refreshing the License Server on Windows To cause the License Server to re-read the license files in the license path: 1.

Click the Stop Service button. this command is located in the C:\Program Files\netcool\common\license\bin directory. 2. Viewing the License Host ID on Windows To view the license host ID.1 Administration Guide . By default. Launch LMTOOLS from the Windows Start Menu. 3. Click the Start → Stop → Reread tab in the LMTOOLS window. You can use this license host ID when you request licenses from Micromuse Technical Support. you run the lmhostid command from any command prompt.Chapter 2: Netcool Common License Server Stopping the License Server on Windows To start the License Server: 1. 46 Netcool/Impact 3.

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

you must specify that the licenses are for use with a quorum configuration. it produces a single license file that you must install on all instances of the License Server in the quorum. Typically.10 Quorum Licensing This section contains information on quorum licensing. Requesting and Installing Quorum License Files When you request licenses from Micromuse Technical Support. It contains the following topics: • • • 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. You must install all instances of the License Server on systems running the same operating system. The second and third instances are called secondary and tertiary instances. When Micromuse processes your license request. The first instance of the License Server is called the primary instance. 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. Quorum licensing requires exactly three instances of the License Server. secondary and tertiary instances. you install these instances on separate systems in your environment. 48 Netcool/Impact 3.Chapter 2: Netcool Common License Server 2. This configuration provides failover functionality between server instances. This license file specifies the hostnames of each of the license servers and their status as primary. There are no additional steps or special considerations.1 Administration Guide . How Do I Set Up a Quorum? To set up a licensing quorum. You must also provide host IDs for each of the systems where you plan to install the License Server.

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. 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. the Netcool GUI Server and the Netcool Security Manager. When you shut down a single instance of the License Server using the nc_stop_license script or LMTOOLS.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. all other instances in the quorum are also stopped automatically. lic_host_02 is the secondary instance and lic_host_03 is the tertiary instance.Quorum Licensing The following example shows a typical quorum license file. lic_host_01 is the primary License Server instance.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. You must configure Netcool/Impact. 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. How Do I Configure Netcool/Impact Components to Use a Quorum? To configure Netcool/Impact components to use the quorum.1 Administration Guide 49 . you manually edit the contents of each license properties file so that they contain the hostnames and port numbers of the License Server instances. Note: You must explicitly specify the port used by each License Server instance in the license file.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. Netcool/Impact 3.

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

To uninstall the License Server. 2. In the Start Menu. which deletes the program files from the file system and removes License Server information from the Windows registry file. 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. Uninstalling on UNIX When you install the License Server on UNIX platforms. select Control Panel → Add/Remove Programs. Select Netcool License Server from the list of installed applications and click Remove. Netcool/Impact 3. all of the program files are copied to the $NCLICENSE directory. To uninstall the License Server: 1. You must shut down the License Server before you attempt to uninstall. The Add/Remove Programs tool uninstalls the License Server. You can safely uninstall the License Server by deleting this directory and all its contents.Uninstalling the License Server 2.11 Uninstalling the License Server This section contains information on uninstalling the License Server on UNIX and Windows platforms. you should copy any license files to a safe location before uninstalling. If you plan to reinstall the License Server. This tool launches the License Server uninstaller.1 Administration Guide 51 .

Chapter 2: Netcool Common License Server 52 Netcool/Impact 3.1 Administration Guide .

fm December 15. 2004 10:15 am This chapter contains information about the Netcool GUI Server 2.Chapter 3: Netcool GUI Server 03_GUI_Server. It contains the following sections: • • • • • • • • • • • About the GUI Server on page 54 System Requirements on page 56 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 Netcool/Impact 3.1 Administration Guide 53 .0.

Chapter 3: Netcool GUI Server 3. 54 Netcool/Impact 3. To install the GUI Server. see GUI Server Components on page 58. The installer sets all of the required configuration properties. The installation files include the Netcool GUI Server installer and a README file. The GUI Server consists of the Servlet Engine and the Netcool Application Registry. For more information. After you have installed 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 installer creates an installation log that you can view to see if the process completed successfully. On UNIX platforms. How Do I Set Up the GUI Server? Before you set up the GUI Server.1 Administration Guide . you must set the required environment variables after installation. For more information. You must install and configure the GUI Server before you install Netcool/Impact. you can change its configuration at any time by manually editing its properties files. see Installing the GUI Server on page 60. you run the installer program and follow the on-screen prompts. It contains the following topics: • • • • • 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.1 About the GUI Server This section contains overview information about the Netcool GUI Server.

1 Administration Guide 55 . Can I Run the GUI Server Under Process Control? You can run the GUI Server under process control with no special considerations. see Licensing the GUI Server on page 63. For more information. see Running the GUI Server on page 65. The GUI Server runs as a “non-pa aware” application. Netcool/Impact 3.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 can read the GUI Server log. see GUI Server Logging on page 77. When you install the GUI Server. it requires no additional real-time administration. you start and stop the GUI Server using the administration scripts. On Windows platforms. For more information. How Do I Administer the GUI Server? After you have started the GUI Server. How Do I Run the GUI Server? On UNIX platforms. you specify the hostname and port for this license server. you start and stop the GUI Server using the Windows Services administration tools. 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. To check the status of the GUI Server. For more information.

4.0 Microsoft Windows 2000 Server.hp. Micromuse recommends that you use Red Hat Enterprise Server 3. Red Hat no longer officially supports version 9. 8 and 9 Red Hat Linux 9. You do not have to install the J2SDK independently of the software. Note: On AIX and HP-UX platforms. Red Hat Linux and Microsoft Windows platforms.0 and Enterprise Server 3.Chapter 3: Netcool GUI Server 3.x of the Java 2 Software Development Kit (J2SDK).1 Administration Guide . You can obtain the J2SDK for AIX from the IBM website at http://www. the J2SDK is installed automatically when you install the GUI Server.2 System Requirements Make sure that the target system fulfills the following requirements before installing the Netcool GUI Server. Windows XP and Windows 2003 Server IBM AIX 5L (5.11 Note: If you intend to install the GUI Server on a Linux platform.2) Hewlett-Packard HP-UX 11.com/java. 56 Netcool/Impact 3.0. You can obtain the J2SDK for HP-UX from the Hewlett-Packward website at http://www. On AIX and HP-UX platforms.ibm.0. you must download and install a compatible version separately from the GUI Server. Platform Support The GUI Server is supported on the following platforms: • • • • • Sun Microsystems Solaris 7. On Solaris.0b21 or later.1 and 5.com/products1/unix/java. 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. Java Support The GUI Server requires version 1. you must download and install the entire J2SDK.

7 and later Hardware Requirements Hardware requirements for the GUI Server vary depending on your environment. Netcool/Impact 3. Under some conditions. You must read the full text of the license agreement and accept the terms of the agreement before installing this software. contact your Micromuse account manager or Micromuse Technical Support.System Requirements Security Manager Requirements The GUI Server requires Netcool Security Manager 1. Web Browser Support The Netcool/Impact GUI runs on the following web browsers: • • • Microsoft Internet Explorer 5. the license agreement text displayed by the installer program is not legible when viewed inside Exceed.5 and later Netscape 6 and later Mozilla 1. Exceed Limitations Micromuse does not recommend the use of Hummingbird Exceed with the GUI Server installer program.1 or 1.1 Administration Guide 57 . For recommendations on hardware sizing for the GUI Server.2 for user authentication.

see the Tomcat website at http://jakarta. The GUI Server uses the information stored in the registry when brokering HTTP requests between end users’ web browsers and the applications. The Servlet Engine incorporates Apache Tomcat servlet technology.Chapter 3: Netcool GUI Server 3.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. For more information.1. Note: The registry is a set of Java servlets that can be run in any J2EE servlet container. By default. 58 Netcool/Impact 3.1 Administration Guide . The registry is also used by Netcool/Impact and the Netcool Security Manager to store information used in server clustering.apache.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 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. The version of Tomcat used in the Servlet Engine is 4.

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

write and execute permissions to the target directory. Running the GUI Server Installer The GUI Server installer copies the program files to the target system and sets the minimum required configuration properties. where build is the build number of the software and arch is the name of the operating system. Micromuse recommends that you do not install the GUI Server as the root user. the installer presents a series of graphical dialog boxes that guide you through the installation process. You can run the installer as any other user that has read. the installer prompts you for required information from the command line. You can download the J2SDK for HP-UX from the Hewlett-Packard website at http://www. 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) Verify firewall port settings After you have finished installing the GUI Server.com/products1/unix/java.Chapter 3: Netcool GUI Server 3.ibm. The GUI Server is compatible with versions 1. In console mode. You can download the J2SDK for AIX from the IBM website at http://www. or to troubleshoot installation errors. The JRE alone is not sufficient. 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 the entire J2SDK. you must download and install a compatible version of the Java 2 Development Kit (J2SDK) before you install the GUI Server. If you are installing the GUI Server remotely using telnet or another command line application. The installer is named guiserverbuildarch. you can read the installation log to verify that the software has been installed correctly. In GUI mode.1 Administration Guide .x of the J2SDK.4. you must run the installer in console mode.com/java.bin. You can run the installer in GUI mode or in console mode.hp. 60 Netcool/Impact 3.5 Installing the GUI Server To install the GUI Server.

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

You can also use it to troubleshoot installation problems.0_Install_Log.log and is located in the $GUI_HOME directory.Chapter 3: Netcool GUI Server Setting the GUI Server Environment Variables If you are installing the GUI Server on a UNIX platform. this directory is opt/netcoool/guiserver. You can use this log to verify that you have installed the GUI Server successfully. you must set the GUI_HOME environment variable to the directory where you installed the application. 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. The following example shows how to set GUI_HOME using sh or bash: GUI_HOME=/opt/netcool/guiserver.1 Administration Guide . The installation log contains runtime messages generated during the installation process. Reading the Installation Log The GUI Server installation log is named Netcool_GUI_Server_2. export GUI_HOME The following example shows how to set GUI_HOME using csh: setenv GUI_HOME /opt/netcool/guiserver Verifying Port Settings If the GUI Server is seperated from Netcool/Impact. or you are running the GUI Server on a Windows machine with a built-in firewall. the Security Manager or the License Server by a firewall. 62 Netcool/Impact 3. By default.

The following table shows the license properties for the GUI Server: Table 9: Netcool GUI Server License Properties Property license. 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. Netcool/Impact 3. Default is localhost. If you manually edit the properties file. This file is named license. The licensing properties are set automatically when you install the GUI Server.server.props and is located in the $GUI_HOME/etc directory.host Description Hostname or IP address of the license server to be used by the GUI Server.6 Licensing the GUI Server This section contains information on licensing the GUI Server. The license feature code for client licenses is nci_client.port Quorum Licensing To use the GUI Server with a quorum licensing configuration.Licensing the GUI Server 3. you must stop and restart the GUI Server before the change takes effect.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. license. Default is 27000. 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. you can manually edit the license properties file at any time to change the configuration. However.1 Administration Guide 63 . Port of the license server to be used by the GUI Server. Configuring Licensing Licensing properties are located in the license properties file.

Remove all properties currently defined in the file. You must specify the License Servers in the order that they appear in the license file. Add the following property to the file: license.port@host_02.port@host_03 2. This includes the license. 64 Netcool/Impact 3.server=port@host_01.Chapter 3: Netcool GUI Server To edit the license properties file: 1. where host_01.1 Administration Guide . host_02 and host_03 are the primary.host and license. see Quorum Licensing on page 48. For more information on quorum licensing. 27000). secondary and tertiary instances of the License Server and port is the port number used by the servers (by default.port properties.

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 Services window that opens.1 Administration Guide 65 .Running the GUI Server 3. Starting the GUI Server on UNIX You start the GUI Server by running the startup script. right-click on Netcool GUI Server and select Start. 2. Stopping the GUI Server on Windows To stop the GUI Server: 1. In the Services window that opens. To stop 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. In the Start Menu. To start the GUI Server. right-click on Netcool GUI Server and select Stop. select Control Panel / Administrative Tools / Services. select Control Panel / Administrative Tools / Services. Netcool/Impact 3. In the Start Menu. This script is named ncgui_server and is located in the $GUI_HOME/bin directory. This script is named ncgui_shutdown and is located in the $GUI_HOME/bin directory. 2.7 Running the GUI Server This section contains information on starting and stopping the GUI Server on UNIX and Windows platforms.

Chapter 3: Netcool GUI Server 3.org/tomcat. This file is named registry.props and is located in the $GUI_HOME/etc directory.port Description Hostname or IP address of the system where the Security Manager is located.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. Default is admin. You should only modify this file under the supervision of Micromuse Technical Support. Maintained for backward compatibility only.userid Description Registry login username.host security.registry.1 Administration Guide . Configuring the Registry The configuration properties for the Netcool Application Registry are located in the registry properties file. Table 11 shows the registry properties for Netcool/Impact: Table 11: Netcool/Impact Registry Properties (1 of 2) Propery impact. see the Apache Tomcat documentation at http://jakarta.apache. You must stop and restart the GUI Server in order for configuration changes to take effect.props and is located in the $GUI_HOME/etc directory. Configuring Authentication Authentication properties for the GUI Server are located in the server properties file. The following table shows the authentication properties for the GUI Server. This file is named server. For more information on the servlet properties file. Configuring the Servlet Engine Configuration properties for the Servlet Engine are located in the servlet properties file. This file is named server. Port used by the Security Manager. 66 Netcool/Impact 3.8 Configuring the GUI Server You can configure GUI Server components at any time after installation by manually editing their properties files. Table 10: Netcool GUI Server Authentication Properties Property security.

registry. Port used.location For more information on registry properties. where # is an index value that identifies the registry instance.port impact.1 Administration Guide 67 . see Registry Clustering on page 68. which have 8080 as defaults. where # is an index value that identifies the registry instance.count impact. Default is netcool.registry. Default is /registry/services. Maintained for backward compatibility only.registry.#. Number of registry instances in the cluster.registry.#. This is the HTTP port used by the GUI Server or Tomcat.Configuring the GUI Server Table 11: Netcool/Impact Registry Properties (2 of 2) Propery impact. URL location on servlet container where registry is installed.host impact. Hostname of the registry instance.#. where # is an index value that identifies the registry instance. impact.password Description Registry login password.registry. Netcool/Impact 3.

1 Administration Guide . except in the case that the primary registry fails and a secondary registry assumes the role of the primary. It stores information about which instances of these components are running and where they are located on the network.Chapter 3: Netcool GUI Server 3. They do not communicate with the Netcool applications in real time. 68 Netcool/Impact 3. Clustering prevents the registry from acting as a single point of failure in a Netcool/Impact installation. It contains the following topics: • • • • • • 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. The secondary registries are responsible for providing failover functionality for the primary registry. What Are the Clustering Components? A registry cluster consists of a primary registry and one or more secondary registries.9 Registry Clustering This section contains information on registry clustering. 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.

this path must be $CATALINA_HOME/webapps. If you are installing for use with Tomcat. 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. For the GUI Server this file is in the $GUI_HOME/app3p/tomcat/webapps/registry/WEB-INF directory. You install the registry using the standard GUI Server installer. During installation. Netcool/Impact 3. see http://jakarta.1 Administration Guide 69 . this file is in the $CATALINA_HOME/webapps/registry/WEB-INF directory. you must edit the web. this path must be $GUI_HOME/app3p/tomcat/webapps. Micromuse recommends that you use Tomcat for scenarios in which you require a lightweight. To configure the registry instances. you must specify the directory where you want the registry to reside.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.apache. For Tomcat. Each registry must be configured in the exact same way.xml file.org/tomcat. Installing the Registries The next step in setting up clustering is to install the registry in each J2EE servlet container. For more information on Tomcat. 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. The installer prompts you whether to install the GUI Server.xml file so that it contains a set of property settings for each registry in the cluster. choose to install the registry as a standalone component. easily-configurable platform for the registry. the registry or both. Supported containers include the Netcool GUI Server and the standalone Tomcat server. Netcool/Impact. You can run the registry with any J2EE servlet container. If you are installing the registries for use with the GUI Server. If you are installing for use with Tomcat.

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

PORT</param-name> <param-value>8080</param-value> </context-param> <context-param> <param-name>REPLICANT.PORT</param-name> <param-value>8080</param-value> </context-param> <context-param> <param-name>REPLICANT.HOST</param-name> <param-value>registry_host_02</param-value> </context-param> <context-param> <param-name>REPLICANT.LOCATION</param-name> <param-value>/registry/services</param-value> </context-param> <context-param> <param-name>REPLICANT.PORT</param-name> <param-value>8080</param-value> </context-param> <context-param> <param-name>REPLICANT.Registry Clustering The following example shows typically settings for these properties in a clustering scenario with three registry instances: <context-param> <param-name>REPLICANT.HOST</param-name> <param-value>registry_host_01</param-value> </context-param> <context-param> <param-name>REPLICANT.LOCATION</param-name> <param-value>/registry/services</param-value> </context-param> <context-param> <param-name>REPLICANT.1 Administration Guide 71 .HOST</param-name> <param-value>registry_host_03</param-value> </context-param> <context-param> <param-name>REPLICANT.LOCATION</param-name> <param-value>/registry/services</param-value> </context-param> <context-param> <param-name>SELFINDEX</param-name> <param-value>0</param-value> </context-param> Netcool/Impact 3.COUNT</param-name> <param-value>3</param-value> </context-param> <context-param> <param-name>REPLICANT.

This is the HTTP port used by the GUI Server or Tomcat. Hostname of the registry instance.#. Registry properties for Netcool/Impact begin with the impact. Default is admin.#.1 Administration Guide .registry. where # is an index value that identifies the registry instance. $GUI_HOME/etc for the GUI Server and $NCSM_HOME/etc for the Netcool Security Manager. Maintained for backward compatibility only. Registry configuration properties for Netcool components are located in the registry. URL location on servlet container where registry is installed.location 72 Netcool/Impact 3.props file for each component to view property names in the correct format.registry. This directory is $IMPACT_HOME/etc for Netcool/Impact.password impact.xml file. you must specify a set for each registry in the cluster.host impact. Number of registry instances in the cluster. the Netcool GUI Server. This file is located in the etc directory of the component installation. Table 13 shows the registry properties for Netcool/Impact: Table 13: Netcool/Impact Registry Clustering Properties Propery impact.registry prefix.Chapter 3: Netcool GUI Server Configuring the Netcool Applications After you have configured the registry instances.registry. you must configure Netcool/Impact.registry. Registry login password.props file. Port used. which have 8080 as defaults. Note: Property names differ depending on whether you are configuring Netcool/Impact or you are configuring another component. where # is an index value that identifies the registry instance.registry. Default is netcool. impact.registry. Maintained for backward compatibility only. Default is /registry/services.port impact. where # is an index value that identifies the registry instance.userid Description Registry login username. Registry properties for other components begin with the registry prefix. See the default values in the registry.#. As with the clustering properties in the web. the Netcool Security Manager and any other Netcool components that use the registry cluster.count impact.

Number of registry instances in the cluster. Registry login password.1 Administration Guide 73 . URL location on servlet container where registry is installed.password registry.host registry. Default is admin. This is the HTTP port used by the GUI Server or Tomcat.#. where # is an index value that identifies the registry instance. Default is /registry/services. Hostname of the registry instance.#. which have 8080 as defaults.#. where # is an index value that identifies the registry instance. where # is an index value that identifies the registry instance. Maintained for backward compatibility only.location Netcool/Impact 3. Default is netcool.userid Description Registry login username. Port used.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 registry. registry.count registry.port registry. Maintained for backward compatibility only.

location=/registry/services impact.port=8888 impact.registry.1.registry.168.registry.1.port=8890 impact.2.2.registry.password=netcool impact. The command to start Tomcat is $CATALINA_HOME/bin/startup.168.0.120 impact.168.location=/registry/services impact.Chapter 3: Netcool GUI Server The following example shows a typical registry.registry.host=192.props file for the GUI Server or Security Manager: impact.count=3 impact.1.registry.2.registry.0.host=192.registry.location=/registry/services impact.1.registry.1.password=netcool impact.120 impact.userid=admin impact.1.2.registry. start each J2EE servlet container where the registry is installed. you can start the instances using the standard GUI Server startup script.2. This script is called ncgui_server and is located in the $GUI_HOME/bin directory.0.location=/registry/services impact.2.1. 74 Netcool/Impact 3.1.host=192.registry.registry.registry.location=/registry/services The following example shows a typical registry.userid=admin impact.host=192.registry.host=192.port=8889 impact.registry.1.1.props file for Netcool/Impact: impact.168.168.registry.location=/registry/services How Do I Run a Registry Cluster? To run a registry cluster. You can start the servlet container applications in any order.1 Administration Guide .0.registry.registry.122 impact.sh.port=8889 impact.port=8890 impact.registry.1.host=192.0.registry.121 impact.registry. If registry instances are part of a GUI Server installation.168.registry.registry.0.registry.122 impact.port=8888 impact.121 impact.count=3 impact.1.

it will execute the command and then publish the command to every other registry in the cluster. Command Replication When you start and stop Netcool/Impact and the Netcool Security Manager.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. the cluster member queries the other cluster members at intervals to determine their status and to synchronize registry data between them. each registry cluster member reads the ordered cluster member list and its position on that list from its web. • Failure and Recovery When a cluster member fails.1 Administration Guide 75 . Netcool/Impact 3. they issue registration and un-registration commands to the registry cluster members. The registry stores this information internally and uses it to determine its behavior during runtime. it forwards the command to the primary without executing it. Once a failure has been detected. The primary then executes the command as described above.xml file. the other members detect the failure during normal runtime operation. it does one of the following: • If the member is the primary registry instance. the other members detect the recovery and notify it that it needs to re-synchronize its registry data. When a cluster member receives such a command. the other members update their clustering information and do not attempt to synchronize data with the failed member. Runtime During runtime. When a cluster member recovers. If the member is not the primary registry instance. The other registries then execute the command and update their registration information.

This information is then read by the cluster member at startup.xml file. 76 Netcool/Impact 3. 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.1 Administration Guide . If PERSIST_ENABLED is set to true. it determines whether to save its registry information to disk by reading the PERSIST_ENABLED property in the web. This tool displays the currently-defined registry instances and whether they are running or stopped.Chapter 3: Netcool GUI Server Shutdown When you shut down a cluster member. it saves its registry information in the directory specified by the PERSIST_PATH property. 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.

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

all of the program files are copied to the $GUI_HOME directory. Uninstalling on UNIX When you install the GUI Server on UNIX platforms.Chapter 3: Netcool GUI Server 3.11 Uninstalling the GUI Server This section contains information on uninstalling the GUI Server on UNIX and Windows platforms.1 Administration Guide .bat and is located by default in the C:\Program Files\netcool\guiserver\UninstallerData directory.bat 78 Netcool/Impact 3. enter the following at a command prompt: cd C:\Program Files\netcool\guiserver\UninstallerData uninstall. 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. To uninstall the GUI Server. To uninstall the GUI Server. You can safely uninstall the GUI Server by deleting this directory and all its contents. You must shut down the GUI Server before you attempt to uninstall.

1 Administration Guide 79 . 2004 10:15 am This chapter contains information on Netcool/Impact.fm December 15. It contains the following sections: • • • • • • • • • • • About Netcool/Impact on page 80 System Requirements on page 83 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 Netcool/Impact 3.Chapter 4: Netcool/Impact 04_Impact.

messaging systems and network inventory applications. In addition.Chapter 4: Netcool/Impact 4. 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.1 About Netcool/Impact This section contains overview information about Netcool/Impact. event enrichment and event notification.1 Administration Guide . It contains the following topics: • • • • • • 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. including databases. you can use Netcool/Impact to integrate Netcool/OMNIbus with a wide variety of third party software. see Netcool/Impact Components on page 85 80 Netcool/Impact 3.

The global properties files control configuration settings for all instances of the Netcool/Impact server in a configuration. When you install Netcool/Impact. The installation files include the Netcool/Impact installer and a README file. After you have installed 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. For more information.micromuse. On UNIX platforms.1 Administration Guide 81 .com. see Upgrading Netcool/Impact on page 91.About Netcool/Impact How Do I Set Up Netcool/Impact? Before you set up Netcool/Impact. The URL for the Micromuse Technical Support website is http://support. you must set the required environment variables after installation. 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. you specify the host and port for this license server. you can change its configuration at any time by manually editing its properties files. Netcool/Impact 3. The installer creates an installation log that you can view to see if the process completed succesfully. The server properties files control configuration settings for each instance of the Netcool/Impact server. you run the installer and follow the on-screen prompts. How Do I Configure Netcool/Impact? Netcool/Impact provides two sets of properties files. To install Netcool/Impact. For more information. The installer sets all of the required configuration properties.

You can also use these tools to manage other aspects of Netcool/Impact.1 Administration Guide . policies and services. such as data types. Netcool/Impact also provides a set of logs that you can read to view the status of components or to troubleshoot problems. 82 Netcool/Impact 3.Chapter 4: Netcool/Impact 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.

11 Note: If you intend to install Netcool/Impact on a Linux platform.x of the Java 2 Runtime Environment (JRE).1 is compatible with the Netcool Common License Server 1. License Server Compatibility Netcool/Impact 3. Micromuse recommends that you use Red Hat Enterprise Server 3.System Requirements 4.0b21 or later. Platform Support Netcool/Impact 3.0 and Enterprise Server 3. Netcool/Impact 3.4.0. Red Hat no longer officially supports version 9.2) Hewlett-Packard HP-UX 11.1 or 1. You do not need to install the JRE independently.2 System Requirements Make sure that the target system fulfills the following requirements before installing Netcool/Impact.1 Administration Guide 83 . Windows XP and Windows 2003 Server IBM AIX 5L (5. Security Manager Requirements Netcool/Impact 3.2 for user authentication.1 requires version 1. 8 and 9 Red Hat Linux 9. Java Support Netcool/Impact 3.0 of the Netcool GUI Server.0 Microsoft Windows 2000 Server. GUI Server Requirements Netcool/Impact 3.1 and 5.1 requires version 2.0.1 is supported on the following platforms: • • • • • Sun Microsystems Solaris 7.1 requires Netcool Security Manager 1. The JRE is installed automatically when you install Netcool/Impact.

Chapter 4: Netcool/Impact

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 agreement before installing this software.

84

Netcool/Impact 3.1 Administration Guide

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 CVS Netcool/Impact JRExec server Netcool/Impact Operator View Netcool/Impact GUI

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 3.1 Administration Guide

85

Chapter 4: Netcool/Impact

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.

86

Netcool/Impact 3.1 Administration Guide

Netcool/Impact Architecture

4.4

Netcool/Impact Architecture
The following figure shows the architecture of Netcool/Impact and its components.

Netcool/ Impact GUI

Netcool/ Impact DSAs

Netcool/ Impact

Netcool/ Impact Database Netcool/ Impact JRExec Server

Netcool/ Impact CVS

Figure 5: Netcool/Impact Architecture

Netcool/Impact 3.1 Administration Guide

87

The Netcool/Impact database requires a maximum shared memory setting of at least 32 MB. If you are running Netcool/Impact on the same machine as the Security Manager. the installer presents a series of graphical dialog boxes that guide you through the installation process. where build is the build number and arch is the name of the operating system. For more information. write and execute permissions to the target directory. Running the Netcool/Impact Installer The Netcool/Impact installer copies the program files to the target system and sets the minimum required configuration properties. Configuring the Operating System Kernel (UNIX Only) If you plan to use the Netcool/Impact reporting features on a UNIX platform. you do the following: • • • • Configure the operating system kernel (UNIX only) Run the Netcool/Impact installer Set the Netcool/Impact environment variables (UNIX only) Verify firewall port settings After you have finished installing Netcool/Impact. If you are installing Netcool/Impact remotely using telnet or another command line application.bin.5 Installing Netcool/Impact To install Netcool/Impact. you must also increase the shared memory setting to accomodate the Security Manager database. the installer prompts you for required information from the command line. Micromuse recommends 64 MB. you must first configure the operating system kernel so that the shared memory settings fulfill the requirements of the Netcool/Impact database. 88 Netcool/Impact 3. The installer is named impactbuildarch. you can read the installation log to verify that the software has been installed correctly. see UNIX Kernel Configuration on page 167. You can run the installer as any other user that has read.. you must run the installer in console mode. or to troubleshoot installation errors.1 Administration Guide . In GUI mode. You cannot run the installer as user root. You can run the installer in GUI mode or in console mode. In console mode.Chapter 4: Netcool/Impact 4.

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

export IMPACT_HOME The following example shows how to set IMPACT_HOME using csh: setenv IMPACT_HOME /opt/netcool/impact Verifying Port Settings If Netcool/Impact is seperated from the GUI Server. Reading the Installation Log The Netcool/Impact installation log is named Netcool_Impact_3. the Security Manager or the License Server by a firewall.log and is located in the $IMPACT_HOME directory. The installation log contains runtime messages generated during the installation process. 90 Netcool/Impact 3.Chapter 4: Netcool/Impact Setting the IMPACT_HOME Environment Variable If you are installing Netcool/Impact on a UNIX platform. You can also use it to troubleshoot installation problems.1_InstallLog. The following example shows how to set IMPACT_HOME using sh or bash: IMPACT_HOME=/opt/netcool/impact. You can use this log to verify that you have installed Netcool/Impact successfully. you must set the IMPACT_HOME environment variable to the directory where you installed the application. 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.1 Administration Guide . By default. or you are running Netcool/Impact on a Windows machine with a built-in firewall. this directory is /opt/netcool/impact.

Netcool/Impact 3.0 Upgrading from Netcool/Impact 2.1. Creating a New Server Instance After installing Netcool/Impact 3.1 Installing Netcool/Impact 3.1 on the target system.0 Manually export project data from Netcool/Impact 3.3 are not supported. you must create a new server instance with the same name and same cluster name as the instance you are upgrading from version 3.6 Upgrading Netcool/Impact This section contains information on upgrading Netcool/Impact from previous versions.0.0 installation.1.1 (optional) Import data into Netcool/Impact 3.0 is installed.Upgrading Netcool/Impact 4.1 Administration Guide 91 . Note: Do not attempt to install in the same directory as an existing Netcool/Impact 3. Upgrading from Netcool/Impact 3. make sure that you install into a separate directory.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 is to install Netcool/Impact 3.0.1 The first step in upgrading from version 3. It contains the following topics: • • Upgrading from Netcool/Impact 3. For instructions on installing Netcool/Impact 3. see Installing Netcool/Impact on page 88.0 To upgrade from Netcool/Impact 3. You can create this server instance following the instructions in Creating Server Instances on page 106. If the target is the same system as the one where Netcool/Impact 3. You can install the application to upgrade with no special considerations.3 Upgrades from versions previous to Netcool/Impact 2. you perform the following steps: • • • • • • Install Netcool/Impact 3.

This directory must be named Projects.0.1 After you have exported the data from Netcool/Impact 3. you can start it using the server startup script. The project files are imported automatically when you run the import script. For more information on starting server instances.0 The next step in upgrading is to run the export command from the Netcool/Impact 3. Create a subdirectory of the directory where you exported data in the previous step. Manually copy the project list file from the version 3. you can then import it into the version 3.Chapter 4: Netcool/Impact Starting the New Server Instance Once you have created the new server instance.1 Administration Guide . Exporting Data from Netcool/Impact 3. Copy each project file into the directory you created and rename the file to omit the servername prefix. If you want to re-use version 3. 3. Manually Exporting Project Data from Netcool/Impact 3.0 server must be running when you run this command. where servername is the name of the Netcool/Impact server instance and projname is the name of the project. you must manually export them. 2. data type. 92 Netcool/Impact 3. This file is named servername_projectlist. where servername is the name of the Netcool/Impact server instance.1 installation. To export projects from the version 3. The export command is named nci_export and is located in $IMPACT_HOME/bin directory.0 project has an associated project definition file named servername_projname. You do not need to manually import the project data into the version 3.proj. service and policy information from the Netcool/Impact server and stores it in a directory you specify.0 projects in the new installation. Then. omitting the servername prefix.0 installation into the directory you created.0 installation: 1.0 installation directory. Each version 3. The export script extracts data source.1 installation. This script is named nci_server and is located in the $IMPACT_HOME/bin directory.0 projects are not automatically exported by the nci_export script.0 Netcool/Impact 3. see Running Server Instances on UNIX on page 107 or Running Server Instances on Windows on page 108. The Netcool/Impact 3. rename the file to projectlist. Importing Data into Netcool/Impact 3.

data type.3.1 only supports CVS for version control after upgrading from version 2.3 Server Before you upgrade to Netcool/Impact 3.3 server. Upgrading from Netcool/Impact 2. To stop the server. You can stop the server by running the shutdown script. you must install the Security Manager.1 components. Stopping the Netcool/Impact 2. service and policy information into the specified version 3. The import command is named nci_import and is located in the $IMPACT_HOME/bin directory. Installing the Netcool/Impact 3. If you want to use another version control system. you run the import script and specify the location of this directory.3 server Install Netcool/Impact 3.3 To upgrade from Netcool/Impact 2.1 Administration Guide 93 .3 server.1 server instance. Netcool/Impact 3.0 installation. GUI Server and Netcool/Impact at this time.1. Then.1 upgrade script Start Netcool/Impact 3. you must copy the directory created by the export script to a location on the file system accessible to the Netcool/Impact 3.3.1 components Start the Netcool GUI Server Run the Netcool/Impact 3. you must stop and restart the Netcool/Impact 3. At minimum.1 Components After you have stopped the version 2. Note: Do not attempt to install in the same directory as an existing Netcool/Impact 3. This script is named nci_shutdown and is located in the $IMPACT_HOME/bin directory.1 Note: Netcool/Impact 3. you can install the Netcool/Impact 3. The import script inserts the extracted data source.1 installation. you must stop the version 2. you do the following: • • • • • Stop the Netcool/Impact 2. you must use a completely new installation of Netcool/Impact.Upgrading Netcool/Impact To import the data.1 server instance. 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. After you have imported the the data.

Name of the 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. Starting Netcool/Impact 3. The upgrade script prompts you for the following information: Table 18: Netcool/Impact Upgrade Script Prompts Prompt Version 2.3 server name.1 server instance.1 Upgrade Script The upgrade script creates a new Netcool/Impact 3. 94 Netcool/Impact 3.1 components.3 of Netcool/Impact is installed. Security Manager port Version control system.1 After you have run the upgrade script.1 server instance. You can start the GUI Server using the server startup script. The upgrade script requires the Netcool Application Registry to be running.1 $IMPACT_HOME/upgrade directory. The upgrade script is named nci_upgrade and is located in the version 3.1 of Netcool/Impact. Version control system to be used by version 3. Running the Netcool/Impact 3. you must start the GUI Server.3 server.1 server instance using the configuration properties from the specified Netcool/Impact 2. Port where the Security Manager is running. Security Manager host.3 installation directory Version 2.Chapter 4: Netcool/Impact Starting the Netcool GUI Server After you have installed the Netcool/Impact 3. The Application Registry is installed and run by default with the GUI Server. This script is named ncgui_server and is located in the $GUI_HOME/bin directory. Hostname or IP address where the Netcool Security Manager is located.3 server instance that you want to upgrade. you can start the new Netcool/Impact 3. This instance has the same name as in version 2. Description Directory on the system where version 2.1 Administration Guide .

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. 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.1 Administration Guide 95 .Licensing Netcool/Impact 4.7 Licensing Netcool/Impact This section contains information on licensing Netcool/Impact. The license feature code for the Operator View is cro_nci_opview. 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 clients is cro_nci_client. 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 3.

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

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

Maintained for backward compatibility only. Default is admin.registry. Maintained for backward compatibility only.registry.registry.#. which have 8080 as defaults.registry.#. Registry settings are located in the registry properties file.1 Administration Guide . impact.port impact. The Application Registry is a component of the Netcool GUI Server.8 Configuring Registry Settings Netcool/Impact uses the Netcool Application Registry to store information used in server clustering. Hostname of the registry instance. You can change the registry configuration at any other time by modifying the properties in this file.registry. Table 21 shows the registry properties for Netcool/Impact: Table 21: Netcool/Impact Registry Clustering Properties Propery impact. Default is netcool. Registry login password.password impact. Number of registry instances in the cluster.#. The required registry properties are set automatically when you install Netcool/Impact. where # is an index value that identifies the registry instance. where # is an index value that identifies the registry instance.registry.Chapter 4: Netcool/Impact 4. This file is named registry.location For more information on working with the Netcool Application Registry. URL location on servlet container where registry is installed. This is the HTTP port used by the GUI Server or Tomcat. You must stop and restart the Netcool/Impact server for the changes to take effect.host impact.count impact. where # is an index value that identifies the registry instance. Port used. Default is /registry/services.userid Description Registry login username. 98 Netcool/Impact 3.props and is located in the $IMPACT_HOME/etc directory. see Chapter 3: Netcool GUI Server on page 53.

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

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

bat Netcool/Impact 3. all of the program files are copied to the $IMPACT_HOME directory. Uninstalling on UNIX When you install Netcool/Impact on UNIX platforms.1 Administration Guide 101 . You can safely uninstall the Netcool/Impact by deleting this directory and all its contents.bat and is located by default in the C:\Program Files\netcool\impact\UninstallerData directory.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.Uninstalling Netcool/Impact 4. 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. To uninstall the Netcool/Impact. This batch file is named uninstall. enter the following at a command prompt: cd C:\Program Files\netcool\impact\UninstallerData uninstall. To uninstall the Netcool/Impact.

Chapter 4: Netcool/Impact 102 Netcool/Impact 3.1 Administration Guide .

Chapter 5: Netcool/Impact Server 05_Impact_Server.1 Administration Guide 103 . 2004 10:15 am This chapter contains information about the Netcool/Impact server. It contains the following sections: • • • • • • 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 Netcool/Impact 3.fm December 15.

Chapter 5: Netcool/Impact Server

5.1

About the Netcool/Impact Server
This section contains overview information about the Netcool/Impact server. It contains the following topics: • • • • • • 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.

104

Netcool/Impact 3.1 Administration Guide

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.

Netcool/Impact 3.1 Administration Guide

105

Chapter 5: Netcool/Impact Server

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 Instance name Cluster name Description Name of the new instance. Default is NCI. 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. Port used by the command line service for the new instance. Hostname or IP address for the primary ObjectServer in your environment. Port used by the ObjectServer. Port used by the HTTP service for Netcol/Impact. Default is 5104. Host to be used by the e-mail sender service. Name of the user associated with the e-mail sender service. Specifies which version control system to use with Netcool/Impact. Default is Netcool/Impact CVS, which is installed automatically with the product.

Command line port ObjectServer host ObjectServer port Impact HTTP port SMTP host E-Mail sender name Version control system

To create a server instance:
1.

Enter the following at a command line prompt: $IMPACT_HOME/install/nci_new_server

2.

Follow the on-screen prompts.

106

Netcool/Impact 3.1 Administration Guide

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 where server is the name of the Netcool/Impact server instance.

Netcool/Impact 3.1 Administration Guide

107

Chapter 5: Netcool/Impact 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. 2.

In the Start Menu, select Control Panel→Administrative Tools→Services. 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:
1. 2.

In the Start Menu, select Control Panel→Administrative Tools→Services. 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.

108

Netcool/Impact 3.1 Administration Guide

The server log files are located in the $IMPACT_HOME/log directory.5 Monitoring Server Instances You can monitor instances of the Netcool/Impact server by reading the server log files.1 Administration Guide 109 . Server log files are named servername_server.log. where servername is the name of the server instance and n is a number that identifies the log file.Monitoring Server Instances 5. 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.n. Netcool/Impact 3.

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. you can run the remove CVS archives script to completely remove all archives related to a server instance. the remove server script does not delete information on policies. The script checks to see if the server instance is running before removing it from the installation. To run the remove server script. If the instance is running.1 Administration Guide . The remove CVS archives script is named nci_cvs_remove and is located in the $IMPACT_HOME/bin directory. 110 Netcool/Impact 3. If you are using CVS as your version control system. Running the Remove CVS Archives Script By default. To run the remove CVS archives script. data sources. 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. the script automatically shuts it down before continuing with operations.6 Deleting Server Instances To delete a server instance. data types and services from the version control system.Chapter 5: Netcool/Impact Server 5. This script is named nci_removeserver and is located in the $IMPACT_HOME/bin directory. 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. It contains the following sections: • • • • • 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 Netcool/Impact 3.fm December 15.1 Administration Guide 111 . 2004 10:15 am This chapter contains information about Netcool/Impact server clustering.

For more information. Manual changes made to the server properties files are not automatically propagated. When you run the installer program. How Does Clustering Work? For information on the server clustering process. 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.3 and earlier of Netcool/Impact. Secondary servers do not connect directly to the ObjectServer. What are the Clustering Components? A Netcool/Impact server cluster consists of the primary server. You can configure cluster members in the same way you configure single server configurations of Netcool/Impact. The previous functionality is no longer supported in Netcool/Impact 3. see Setting Up a Server Cluster on page 116. For more information. Server clustering replaces the failover functionality provided in versions 2. Both primary and secondary servers are responsible for processing the events.1. It contains the following topics: • • • • 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. Changes made to the server configuration using the Netcool/Impact GUI are propagated automatically to other cluster members. You use this feature to add failover and load-balancing functionality to a Netcool/Impact installation. 112 Netcool/Impact 3. which is responsible for monitoring the Netcool/OMNIbus ObjectServer and making events available to secondary cluster members.Chapter 6: Netcool/Impact Server Clustering 6.1 Administration Guide . see How Server Clustering Works on page 114. see Clustering Components on page 113.1 About Server Clustering This section contains overview information about Netcool/Impact server clustering. you specify the same cluster name for each server in the cluster. and secondary servers.

Clustering Components 6. Secondary servers function solely as event-processing services in the cluster. If the primary server fails or is shut down. The first cluster member that is started automatically becomes the primary server.1 Administration Guide 113 . 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. as well as processing events on its own. The following services are not disabled: • • • • Event processor Basic servlet service Policy logger Self-monitoring service Netcool/Impact 3. Most services are disabled in the secondary servers. one of the secondary servers automatically becomes the primary.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.

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

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

This file is named registry.registry. Setting Registry Properties Properties related to the Netcool Application Registry are located in the registry properties file. you install a separate instance of the Netcool/Impact server on each target system. This name can be any unique identifying string.host 116 Netcool/Impact 3.Chapter 6: Netcool/Impact Server Clustering 6. Default is admin.#.registry. Maintained for backward compatibility only.4 Setting Up a Server Cluster To set up a server cluster. Maintained for backward compatibility only. which is used to identify the members of the server cluster at startup in the Netcool Application Registry. You can set other configuration options manually at any time. where # is an index value that identifies the registry instance.password impact. impact. The Netcool/Impact installer prompts you for the cluster name.count impact. You must stop and restart the Netcool/Impact server instance in order for any changes to take effect. Table 23 shows the registry properties for Netcool/Impact Table 23: Netcool/Impact Registry Properties (1 of 2) Propery impact.registry.userid Description Registry login username. Number of registry instances in the cluster. Registry login password. All servers in a cluster must have the same cluster name. you do the following: • • Install the cluster Configure the cluster Installing a Server Cluster To install a server cluster. Note that configuration changes are propagated from the primary server to the secondary servers.props and is located in the $IMPACT_HOME/etc directory. Hostname of the registry instance.1 Administration Guide . Default is netcool.registry. Configuring a Server Cluster The Netcool/Impact installer prompts you for the name of the server cluster during installation. Changes made to secondary server instances are not propagated back to the primary.

pinginterval Description Name of the server cluster. URL location on servlet container where registry is installed.#.resyncbeforestandby true impact. Time in milliseconds to wait before retrying ping. Specifies whether to synchronize hibernations.for.1 Administration Guide 117 .Setting Up a Server Cluster Table 23: Netcool/Impact Registry Properties (2 of 2) Propery impact. Number of times to retry ping if the first fails.location For more information on registry properties.replication. see Configuring the Registry on page 66. Setting Server Properties Properties related to server clustering are located in the server properties file. Specifies whether to synchronize the OrgNode cache. where # is an index value that identifies the registry instance.#.for. ServiceStates true true true Netcool/Impact 3.receiveupdates.replication.registry.cluster. which have 8080 as defaults.registry. Default NCICLUSTER 6000 impact. where # is an index value that identifies the registry instance.for.cluster. This file is named servername_server. OrgNodes impact.port Description Port used.receiveupdates. Default is /registry/services.name impact. The following table shows the server clustering properties: Table 24: Server Clustering Properties (1 of 2) Name impact. where servername is the name of the server instance The server properties file is located in the $IMPACT_HOME/etc directory.cluster.props. Interval in milliseconds at which to ping other cluster members.pingtimeout 6000 impact. impact.replication.cluster.repingcount 3 impact. Hibernations impact. Specifies whether the server synchronizes data with the primary at startup before becoming active.receiveupdates. Specifies whether to synchronize service states.cluster. This is the HTTP port used by the GUI Server or Tomcat.

replication.receiveupdates. Default true true Interval at which servers synchronize data. 0 118 Netcool/Impact 3.1 Administration Guide . Specifies whether to synchronize policies.statusinterval Description Specifies whether to synchronize data types.receiveupdates.replication. ActionTrees impact.for.replication. Types impact.Chapter 6: Netcool/Impact Server Clustering Table 24: Server Clustering Properties(Continued) (2 of 2) Name impact.for.

Netcool/Impact 3. 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.1 Administration Guide 119 . enter the following at a command prompt: $IMPACT_HOME/bin/nci_shutdown name where name is the name of the server instance. Stopping a Cluster Member You stop the Netcool/Impact server using the server shutdown script. To start the Netcool/Impact server. This script is named nci_shutdown and is located in the $IMPACT_HOME/bin directory.Running a Server Cluster 6. This script is named nci_server and is located in the $IMPACT_HOME/bin directory. To stop the Netcool/Impact server. The default is NCI.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.

1 Administration Guide .Chapter 6: Netcool/Impact Server Clustering 120 Netcool/Impact 3.

fm December 15. 2004 10:15 am This chapter contains information about Netcool/Impact version control.1 Administration Guide 121 .Chapter 7: Netcool/Impact Version Control 07_Version_Control. • • • About Version Control on page 122 How Version Control Works on page 123 Configuring Version Control on page 124 Netcool/Impact 3.

data types and configuration properties as revisions in a source control archive.Chapter 7: Netcool/Impact Version Control 7. This version of CVS is installed automatically when you install Netcool/Impact and is used as the default version control system. data sources. RCS or another version of CVS. If you want to use ClearCase. Version control is enabled for Netcool/Impact by default and cannot be disabled.1 Administration Guide .1 About Version Control Netcool/Impact provides a version control interface that allows you to save Netcool/Impact policies. you must install and configure it before installing Netcool/Impact. 122 Netcool/Impact 3. This interface supports the following version control systems: • • • • Netcool/Impact CVS 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.

including all revisions. Netcool/Impact creates a new element in the revision database. Element Deletion Element deletion occurs when you delete a policy. data source.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.1 Administration Guide 123 . Check In Check in occurs when you save a policy. where filename is the name of the policy script file. Netcool/Impact creates a new archive file named filename. Only the user who has currently checked out the element can modify it. When you rename an element. When an element is locked. Check Out Check out occurs when you open an existing policy. Netcool/Impact checks the corresponding file in as a new revision and removes the lock. data source or data type using the Netcool/Impact GUI or CLI.How Version Control Works 7. In CVS and RCS. data source or data type using the Netcool/Impact GUI or CLI. Netcool/Impact completely removes the entire element or archive from the version control system. data source or data type using the Netcool/Impact GUI or CLI. The old element with the previous name is not deleted. data type or properties file.v. Element Renaming Element renaming occurs when you rename a policy. Netcool/Impact checks out and locks the most recent revision in the version control system. At check out. In ClearCase. At check in. the locked icon appears in the Netcool/Impact GUI. At element deletion. Netcool/Impact 3. Netcool/Impact creates a new element using the new name in the version control system.

1 Administration Guide .versioncontrol.versioncontrol.systemid impact. where server is the name of the instance of the Netcool/Impact server.Chapter 7: Netcool/Impact Version Control 7. The following table shows the version control configuration properties: Table 25: Version Control Configuration Properties Property impact.cvs. Path to the version control executable (CVS and RCS only) Location of the version control archive (CVS only) 124 Netcool/Impact 3. Reserved for internal use.cvsroot Description Integer that represents the type of version control system.versioncontrol.debug impact.versioncontrol.props.path impact.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 located in $IMPACT_HOME/etc directory. This file is named server_versioncontrol.

2004 10:15 am This chapter contains information about the Netcool/Impact database.fm December 15.Chapter 8: Netcool/Impact Database 08_Database.1 Administration Guide 125 . It contains the following sections: • • • • About the Database on page 126 Configuring the Database on page 128 Running the Database on page 129 Managing the Database on page 130 Netcool/Impact 3.

If you are running them from multiple directories. The HTML version of the documentation is distributed with Netcool/Impact and is located in the $IMPACT_HOME/platform/arch/pgsql/doc/html directory. 126 Netcool/Impact 3.1 About the Database This section contains general information about the Netcool/Impact database. 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. 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. see the official PostgreSQL documentation. If you are running multiple instances of the Netcool/Impact server from one directory on a system. you do not need to run the database. all of the instances will use the same Netcool/Impact database. You can also use the database as a local SQL database data source. Netcool/Impact uses one instance of the database for each installation. The home directory for the database is $IMPACT_HOME/platform/arch/pgsql. each instance will use the Netcool/Impact database installed in $IMPACT_HOME. It contains the following topics: • • • • • • 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. For more information on PostgreSQL. If you do not plan to use the database for this functionality.Chapter 8: Netcool/Impact Database 8. where arch is the name of the local operating system. Netcool/Impact uses the database to store the underlying data used by the GUI reporting tools.1 Administration Guide .

For information on licensing Netcool/Impact. Cygwin Limitations Micromuse recommends that you do not use Cygwin on Windows systems where you are running the Netcool/Impact database. connecting to the database using the PostgreSQL command line client.5. This version may conflict with other versions on the machine. The database uses version 1. These tasks include viewing the database status.About the Database How Do I License the Database? Netcool/Impact requires a PostgreSQL DSA license in order to access the database.3 of the Cygwin runtime. you request this license when you request other Netcool/Impact licenses from Micromuse Technical Support. For more information. How Do I Run the Database? You can start and stop the Netcool/Impact database using the database administration script. Generally. Netcool/Impact 3. see Managing the Database on page 130.1 Administration Guide 127 . The database is not automatically started when you start Netcool/Impact. 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. For more information. and backing up and restoring the database. The license feature code for the PostgreSQL DSA is nci_postgresql_dsa. see Licensing Netcool/Impact on page 95.

This port number is specified in the . To change the database port. The PostgreSQL properties files are described in the official PostgreSQL documentation.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. 128 Netcool/Impact 3. The .1 Administration Guide .nci_dbwrapper script.Chapter 8: Netcool/Impact Database 8. which is called by nci_db. where arch is the platform where Netcool/Impact is installed. You should only modify these files under the supervision of Micromuse Technical Support. 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. the Netcool/Impact database uses port 5700.nci_dbwrapper script is located in the $IMPACT_HOME/bin directory. Setting the Database Port By default.

The database does not start and stop automatically when you start and stop Netcool/Impact.Running the Database 8. To start and stop the database on Windows platforms. In the Start Menu. you use the database administration script. 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: 1. 2. right-click on Netcool Database (Impact) and select Start. 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. Stopping the Database on UNIX Platforms To stop the Netcool/Impact database. Netcool/Impact 3. 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. Before you run the database for the first time.1 Administration Guide 129 . right-click on Netcool Database (Impact) and select Stop. check to see if it is already running. select Control Panel→Administrative Tools→Services. In the Services window that opens. In the Start Menu. select Control Panel→Administrative Tools→Services.3 Running the Database To start and stop the Netcool/Impact database on UNIX platforms. Stopping the Database on Windows To stop the Netcool/Impact database: 1. you use the Windows Services Administration tools. 2. This script is named nci_db and is located in the $IMPACT_HOME/bin directory. In the Services window that opens.

To reset the database. these error messages do not indicate a problem with resetting the database. 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. enter the following at a command line prompt: $IMPACT_HOME/bin/nci_db connect 130 Netcool/Impact 3.Chapter 8: Netcool/Impact Database 8. To connect to the database with the client. Connecting to the Database with the Command Line Client The command line client is a SQL tool that is distributed with the PostgreSQL database.log Viewing the Database Status To view the database status.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.1 Administration Guide . In most cases. 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. 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.

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. see the official PostgreSQL documentation. Backing Up the Database To back up the database. Netcool/Impact 3.1 Administration Guide 131 .Managing the Database You can use the client to run SQL statements against the database in real time. 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. For more information.

Chapter 8: Netcool/Impact Database 132 Netcool/Impact 3.1 Administration Guide .

fm December 15. 2004 10:15 am This chapter contains information about the Netcool/Impact JRExec server.Chapter 9: Netcool/Impact JRExec Server 09_JRExec. It contains the following sections: • • • About the JRExec Server on page 134 Running the JRExec Server on page 135 Configuring the JRExec Server on page 136 Netcool/Impact 3.1 Administration Guide 133 .

Chapter 9: Netcool/Impact JRExec Server 9.props. you run the JRExec server using the JRExec server script. scripts and applications from within a policy. see the following sections in this chapter. The Windows service is called Netcool/Impact JRExec Server.1 About the JRExec Server This section contain overview information about the Netcool/Impact JRExec server. see the Netcool/Impact Policy Reference Guide. For more information on JRExecAction.1 Administration Guide . This file is located in the $IMPACT_HOME/etc directory and contains the port number used by the JRExec server. How Do I Configure the JRExec Server? The JRExec server provides a properties file named jrexecserver. Can I Run the JRExec Server Under Process Control? You can run the JRExec server under process control with no special considerations. On Windows platforms. How Do I Run the JRExec Server? On UNIX platforms. The JRExec server runs as a “non-pa aware” application. You use the JRExec server with the JRExecAction function. 134 Netcool/Impact 3. you can start and stop the server using the Windows Service Administration tools. How Do I Set Up the JRExec Server? The JRExec server is automatically installed when you install Netcool/Impact. 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. For detailed information.

1 Administration Guide 135 . In the Services window that opens. select Control Panel→Administrative Tools→Services. This script is named nci_jrexec and is located in the $IMPACT_HOME/bin directory. In the Services window that opens. select Control Panel→Administrative Tools→Services. right-click on Netcool JRExec Server and select Start. 2. In the Start Menu.Running the JRExec Server 9. In the Start Menu. 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. enter the following at a command line prompt: kill -15 pid where pid is the process ID of the JRExec Server. Stopping the JRExec Server on Windows To stop Netcool/Impact: 1. Netcool/Impact 3. Starting the JRExec Server on Windows To start Netcool/Impact: 1. Starting the JRExec Server on UNIX You start JRExec Server by running the JRExec Server startup script. 2. To manually terminate the process.2 Running the JRExec Server This section contains information on starting and stopping the JRExec server on UNIX and Windows platforms. right-click on Netcool JRExec Server and select Stop.

you must also change the value of the impact.jrexecserver.jrexec.Chapter 9: Netcool/Impact JRExec Server 9. where server is the name of the Netcool/Impact server instance. If you change this property. To change the port number used by the JRExec server.3 Configuring the JRExec Server The JRExec server provides a properties file named jrexecserver.1 Administration Guide .props file. 136 Netcool/Impact 3.port property in the server_server. This file is located in the $IMPACT_HOME/etc directory and contains the port number used by the JRExec server.port property. open the properties file in any text editor and change the value of the impact.props.

2004 This chapter contains information about Netcool/Impact self-monitoring.Chapter 10: Netcool/Impact Self-Monitoring 11_Self-Monitoring. It contains the following sections: • • • • • 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 Netcool/Impact 3.fm December 15.1 Administration Guide 137 .

Service configuration information is not propagated between members of the cluster. self-monitoring operates on a per-server basis. If you are running one or more event readers. How Does Self-Monitoring Work with a Netcool/Impact Cluster? If you are running multiple Netcool/Impact servers in a cluster. This allows you to customize self-monitoring to accomodate each system where you are running Netcool/Impact. 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.1 About Netcool/Impact Self-Monitoring This section provides overview information about the self-monitoring feature. and event queue size and sends events to the Netcool/OMNIbus ObjectServer regarding memory and queue status. 138 Netcool/Impact 3. This means that you must configure each server instance seperately and that each server runs the self-monitoring feature independent of other cluster members. It contains the following topics: • • • • • 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. The severity of events sent to the ObjectServer varies depending on the severity of the memory or event queue status. How Does Self-Monitoring Work? At intervals.1 Administration Guide . You can configure the service to deduplicate the Netcool/Impact events or to send a new event to the ObjectServer at each interval.Chapter 10: Netcool/Impact Self-Monitoring 10. 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. the self-monitoring service also checks the size of the event queues and sends events to the ObjectServer related to the event queue status.

You can also configure the event reader in Netcool/Impact to launch custom policies that are designed to respond to these events. For single-server configurations of Netcool/Impact. 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. For a clustered server configuration.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). Netcool/Impact 3. These events can be viewed by Netcool operators in an event list and managed according to the normal event handling procedures in your environment. using the GUI is recommended.1 Administration Guide 139 . you must set up self-monitoring using the properties file or the CLI.

The memory status is significant because Netcool/Impact will fail and report an out-of-memory error if the maximum available memory is exceeded. Netcool/Impact monitors available memory in both the Java heap and in the system as a whole. Netcool/Impact checks the current heap size at intervals and compares it to the maximum size specified by the XMX variable. the values for these flags are specified using the XMS and XMX variables in the runtime definition file.2 Memory Status Monitoring This section contains information on monitoring the Netcool/Impact memory status. you can specify a minimum and maximum heap size using the -Xms and -Xmx flags. In order to effectively report on the memory status for the system.Chapter 10: Netcool/Impact Self-Monitoring 10. At maximum. The minimum and maximum values are passed to the JVM by the Netcool/Impact startup script. Java Memory Status When you start an instance of the JVM. 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. The -Xms flag specifies the minimum size of the memory heap and -Xmx specifies the maximum size. 140 Netcool/Impact 3. System Memory Status In addition to Java heap memory. This file is named runtime_def_14 and is located in the $IMPACT_HOME/platform/arch directory. It contains the following topics: • • • 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. With Netcool/Impact. 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. the memory monitoring feature also monitors available system memory as a whole. Netcool/Impact then calculates the severity of the JVM memory status using the rules in Table 26. The default value of XMS is 64M and the default value of XMX is 1000M. where arch is the name of the operating system where Netcool/Impact is installed.1 Administration Guide . When you enable the self-monitoring feature.

The total severity of the event is the highest severity between the JVM and system memory status. Maximum heap limit is less than 1.4 and 1. This event contains the fields described in Table 28.6 and 2 times the current heap size. Maximum heap limit is between 1. Combined Memory Status After calculating the severity of the JVM and system memory status. Netcool/Impact 3. Maximum heap limit is between 1. Netcool/Impact determines its maximum allocated memory to be 1150 megabytes. Table 26: Severity Criteria for JVM Memory Events Severity 1 2 3 4 5 Criteria Maximum heap limit is greater than twice the current help size.2 times the current heap size.2 and 1. Netcool/Impact sends the event to the ObjectServer. 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. if the XMX variable is set to 1000M. Netcool/Impact then calculates the severity of the system memory status using the rules in Table 26.1 Administration Guide 141 .Memory Status Monitoring When you enable the self-monitoring feature.6 times the current heap size.4 times the current heap size. For example. Memory Status Severity Table 26 shows the criteria used by Netcool/Impact to determine the severity of the JVM memory status. Maximum heap limit is between 1.

including information about JVM heap usage and system memory usage. Detailed information about the memory status. Node NodeAlias Severity Summary Class Type AlertGroup FirstOccurrence 142 Netcool/Impact 3. IP address of the system where the Netcool/Impact server is running. Table 28: Memory Event Fields (1 of 2) Field Identifier Description Impact Memory Status for server. Available system memory is between 1. Note: The total severity of any memory event sent to the ObjectServer is the highest severity between the JVM and the system memory status.Chapter 10: Netcool/Impact Self-Monitoring Table 27 shows the criteria used by Netcool/Impact to determine the severity of the systen memory status. Available system memory is between 2 and 1.65 and 1. Hostname of the system where the Netcool/Impact server is running. where server is the name of the Netcool/Impact server instance.65 times the maximum required memory.5 times the maximum required memory. 10500 13 ImpactStatus Timestamp for the first occurrence of this event. Available system memory is between 1. Memory Event Fields Table 28 shows the fields in memory events sent to the ObjectServer. Severity calculated according to the rules in Table 26 and Table 27.8 and 1. Table 27: Severity Criteria for System Memory Events Severity 1 2 3 4 5 Criteria Available system memory is greater than twice the maximum required memory.5 the maximum required memory.8 times the maximum required memory.1 Administration Guide . Available system memory is less than 1.

Memory Status Monitoring Table 28: Memory Event Fields (2 of 2) Field LastOccurrence Description Timestamp for the most recent occurrence of this event. Netcool/Impact 3.1 Administration Guide 143 .

144 Netcool/Impact 3. Table 30 shows the value of fields in the events sent to the ObjectServer. 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. Number of events in queue is between 2 and 3 times the number of events at previous interval. Number of events in queue is more than 5 times the number of events at previous interval. Table 29: Severity Criteria for Queue Status Events Severity 1 2 3 4 5 Criteria Number of events in queue is less than or equal to 1.5 and 2. Queue Status Severity Table 29 shows the criteria used by Netcool/Impact to determine the severity of the event queue status.Chapter 10: Netcool/Impact Self-Monitoring 10.times the number of events at previous interval. Queue size monitoring only works when one or more event readers is running in Netcool/Impact.5 times the number of events at previous interval. Table 29 shows the rules used to determine the severity. For each event.3 Queue Size Monitoring This section contains information on monitoring the status of Netcool/Impact event reader event queues. It contains the following topics: • • • 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. Number of events in queue is between 1.1 Administration Guide . Number of events in queue is between 3 and 5 times the number of events at previous interval.

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

Chapter 10: Netcool/Impact Self-Monitoring Table 31: Queue Status Summary Field (2 of 2) Value Gap Description Time difference between the StateChange of the earliest event in queue and the current time.1 Administration Guide . 146 Netcool/Impact 3.

Netcool/Impact 3.1 Administration Guide 147 . Figure 6: Self-Monitoring Configuration Window 3. 2. Select a data source from the ObjectServer Data Source list. Setting Up Self-Monitoring Using the GUI To set up self-monitoring using the Netcool/Impact GUI: 1. In the Service Status panel. This is the ObjectServer where any new events will be sent. The Self-Monitoring Configuration window opens.4 Setting Up Self-Monitoring You can set up event monitoring using the following: • • • Netcool/Impact GUI Netcool/Impact CLI Netcool/Impact self-monitoring service properties file If you are running Netcool/Impact in a clustered server configuration. Open the GUI in a web browser.Setting Up Self-Monitoring 10. select SelfMonitoring. you must set up self-monitoring using the CLI or the service properties file.

Enable or disable the Startup option. 6. If you change the deduplication option while the service is running. In the Service Status panel. This is the number of seconds at which you want Netcool/Impact to check memory status and the event queue size. Enter an interval in seconds in the Interval field. 4. you must stop and restart it before the change takes effect. 5. Enable or disable the Depulication option. 8. 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’. 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’. click the Start button for the SelfMonitoring service. This option specifies whether this service starts automatically when you start the Netcool/Impact server. This options specifies whether Netcool/Impact should deduplicate events it sends to the ObjectServer. This option specifies whether to print the service log to file. where data_source is the name of an ObjectServer data source. The default port is 2000. 7.1 Administration Guide . where seconds is the number of seconds in the interval. 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’. 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. where dedup_option is true or false. 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.Chapter 10: Netcool/Impact Self-Monitoring 4. 2. 3. Enable or disable the Service Log option. Click OK. 148 Netcool/Impact 3. To set up self-monitoring using the CLI: 1. 9.

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

including the queue size. To view the memory status history enter the following at a Netcool/Impact CLI prompt: SELECT MemoryStatusHistory from Service WHERE Name = ’SelfMonitoring". the change in queue size since the previous interval. 150 Netcool/Impact 3. and the rate of queue size change.Chapter 10: Netcool/Impact Self-Monitoring 10.1 Administration Guide . Queue Status The status of an event queue.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 queue status enter the following at a Netcool/Impact CLI prompt: SELECT QueueStatus 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 queue status history enter the following at a Netcool/Impact CLI prompt: SELECT QueueStatusHistory from Service WHERE Name = ’SelfMonitoring". enter the following at a Netcool/Impact CLI prompt: SELECT MaxVMHeapSize 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. Netcool/Impact 3. To view the maximum required memory. You can use this information to analyze trends in the queue status. To view the available JVM heap size enter the following at a Netcool/Impact CLI prompt: SELECT FreeVMHeapSize from Service WHERE Name = ’SelfMonitoring". To view the current JVM heap size. To view the maximum JVM heap size.1 Administration Guide 151 . enter the following at a Netcool/Impact CLI prompt: SELECT TotalVMHeapSize 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. Available JVM Heap Size The available JVM heap size is the amount of memory in the Java heap that is unused by Netcool/Impact. 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. enter the following at a Netcool/Impact CLI prompt: SELECT MaxVMSize from Service WHERE Name = ’SelfMonitoring".

Chapter 10: Netcool/Impact Self-Monitoring Available System Memory The available system memory is the total free memory on the system unused by Netcool/Impact and other applications.1 Administration Guide . 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 available system memory. enter the following at a Netcool/Impact CLI prompt: SELECT DataSource from Service WHERE Name = ’SelfMonitoring". enter the following at a Netcool/Impact CLI prompt: SELECT FreeSystemMemory from Service WHERE Name = ’SelfMonitoring". 152 Netcool/Impact 3. enter the following at a Netcool/Impact CLI prompt: SELECT Interval from Service WHERE Name = ’SelfMonitoring". To view the monitoring interval. To view the deduplication status. To view the name of the ObjectServer data source. enter the following at a Netcool/Impact CLI prompt: SELECT Deduplication 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. ObjectServer Data Source This is the ObjectServer where Netcool/Impact is sending self-monitoring events.

• • • • nci_crypt on page 154 nci_export on page 155 nci_import on page 156 nci_trigger on page 157 Netcool/Impact 3. 2004 10:15 am This chapter contains information about the Netcool/Impact command line tools.fm December 15.1 Administration Guide 153 .Chapter 11: Command Line Tools 10_Command_Line_Tools.

154 Netcool/Impact 3. To run this tool. You can use this tool to encrypt passwords passed to Netcool/Impact from the command line with nci_trigger. enter the following at a command prompt: $IMPACT_HOME/bin/nci_crypt string where string is the string you want to encrypt.1 nci_crypt The nci_crypt tool encrypts a string using the Netcool/Impact encryption algorithm.1 Administration Guide . This tool is located in the $IMPACT_HOME/bin directory.Chapter 11: Command Line Tools 11.

1 Administration Guide 155 . Netcool/Impact 3.nci_export 11. This tool is located in the $IMPACT_HOME/bin directory. To run this tool. 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. enter the following at a command prompt: $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. data type.2 nci_export The nci_export tool exports data source. service and policy information from an instance of the Netcool/Impact server to a specified directory.

This data includes all data sources. To run this tool.Chapter 11: Command Line Tools 11.3 nci_import The nci_import tool imports data that was previously exported from an instance of the Netcool/Impact server. enter the following at a command prompt: $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. data types.1 Administration Guide . Note: Make sure that the target instance of the Netcool/Impact server is running before you use nci_import. This tool is located in the $IMPACT_HOME/bin directory. 156 Netcool/Impact 3. policies and services currently defined in the server instance.

Name of a field in the event container passed to the policy. Windows only. Name of the policy to run. Windows only.nci_trigger 11. Username and encrypted password of a valid Netcool Security Manager user who has access to Netcool/Impact. Username and password of a valid Netcool Security Manager user who has access to Netcool/Impact. Note: If no password is defined for the user. You can encrypt passwords using the nci_crypt tool.. Table 32: nci_trigger Command Line Arguements Arguments -version Description Causes nci_trigger to print the Netcool/Impact version number. To run this tool. Optional. Username and password of a valid Netcool Security Manager user who has access to Netcool/Impact. Instance of the Netcool/Impact server where you want the policy to run. platform and command syntax to standard output and then exit. Value of a field in the event container passed to the policy. you must specify the password as NULL when you execute the command.4 nci_trigger The nci_trigger tool allows you to start a policy from the command line. Table 32 shows the command line arguments for nci_trigger. You can encrypt passwords using the nci_crypt tool. UNIX only. Optional. Username and encrypted password of a valid Netcool Security Manager user who has access to Netcool/Impact. server_name user_id/password user_id password -e/user_id/encrypted_password -e user_id encrypted_password policy_name field value Netcool/Impact 3. This tool is located in the $IMPACT_HOME/bin directory. enter the following at a command prompt: $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 . UNIX only..1 Administration Guide 157 .

the user is admin. In this example. To run this policy using nci_trigger. you must include Identifier and Serial fields in the event container passed to policy. nci_trigger NCI admin/netcool POLICY_01 This example shows how to run a policy using an encrypted password. the policy is named POLICY_01 Log(@Value1).Chapter 11: Command Line Tools Note: If you want to run a policy that contains a call to the ReturnEvent function. In this example.1 Administration Guide . 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. you must make sure that you specify the parameters as variables in the policy using the @ notation. the password was previously encrypted using the nci_crypt tool. the policy is named POLICY_01. the password is netcool and the server instance is NCI. 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. Log(@Value2). The following example shows how to use this notation in a policy. Runtime Parameters If you are using nci_trigger to pass runtime parameters to a policy. In this example. nci_trigger NCI admin/netcool POLICY_03 Node host_01 Summary Node_down AlertKey host_01Node_down 158 Netcool/Impact 3.

nci_trigger NCI admin netcool POLICY_01 This example shows how to run a policy using an encrypted password. In this example.1 Administration Guide 159 .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. the policy is named POLICY_01. In this example. the password was previously encrypted using the nci_crypt tool. the user is admin. the password is netcool and the server instance is NCI. nci_trigger NCI admin netcool POLICY_03 Node host_01 Summary Node_down AlertKey host_01Node_down Netcool/Impact 3. 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.

1 Administration Guide .Chapter 11: Command Line Tools 160 Netcool/Impact 3.

1 Administration Guide 161 .fm December 15.Appendix A: Supplementary Information 98_Appendix. It contains the following sections: • • • Installation Worksheet on page 162 Firewall Considerations on page 166 UNIX Kernel Configuration on page 167 Netcool/Impact 3. 2004 10:15 am This appendix contains supplementary information for Netcool/Impact administrators.

1 Administration Guide . If you install the components in console mode. Netcool License Server The Netcool License Server installer prompts you for the following information: Table A1: Netcool Common License Server Installer Prompts Prompt Installation directory Answer 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 Installation directory Answer Application Registry directory Shutdown port HTTP port 162 Netcool/Impact 3. you can also record the information electronically using the UNIX script command. You can use the tables in this section to record installation information. You should record this information during the course of installation for later reference. Each table contains an empty Answer column that you can fill with the information that you supply to the installer programs.Appendix A: Supplementary Information A.1 Installation Worksheet The installer programs for Netcool/Impact and its related software components prompt you for system information during the installation process.

1 Administration Guide 163 .Installation Worksheet Table A2: Netcool GUI Server Installer Prompts (2 of 2) Prompt Security Manager host Answer 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 Installation directory Answer HTTP listener port Server port Database port License server host License server port Netcool/Impact 3.

Appendix A: Supplementary Information Netcool/Impact The Netcool/Impact installer prompts you for the following information: Table A4: Netcool/Impact Installer Prompts Prompt Installation directory 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 Instance name Answer Cluster name 164 Netcool/Impact 3.1 Administration Guide .

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

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

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

You do not need to configure kernel settings on AIX platforms. You can specify the max_thread_proc setting using the HP-UX Kernel Configuration tool.1 Administration Guide . To change the shared memory. Configuring AIX The default kernel configuration for AIX is adequate for running Netcool/Impact and the Netcool Security Manager. 168 Netcool/Impact 3. Note: You must reboot the system in order for the new settings to take effect. To configure the kernel you must modify the file so that it contains the following line: kernel. 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. To make the change without rebooting. Settings of less than 500 can cause the Netcool/Impact server to fail at startup. kernel configuration settings are located in the /etc/sysctl. enter the following at a comment line prompt: echo max_memory >/proc/sys/kernel/shmmax where max_memory is the new maximum memory setting. you can also configure the proc file system.conf file.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.Appendix A: Supplementary Information Configuring Red Hat Linux On Red Hat Linux platforms.

Appendix B: DSA Reference 99_Appendix. 2004 This appendix contains reference information related to built-in Netcool/Impact DSAs. It contains the following sections: • • • • • • • • • • • 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 Netcool/Impact 3.fm December 15.1 Administration Guide 169 .

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.Appendix B: DSA Reference B. In most cases. Data Type Configuration Properties When you create a new data type for use with an SQL database data source. 170 Netcool/Impact 3. 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.1 Administration Guide . 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. as well as field names that correspond to each column in the table. the hostname and port). you are required to specify the name of the table (or similar structure) in the underlying data source. field names can be specified using the auto-discovery tools. Some DSAs require additional information. These properties typically include the data source name and connectivity information for the underlying database (for example. 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.

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. Netcool/Impact 3. 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. In most cases. data types representing string or character values are treated as Netcool/Impact strings.1 Administration Guide 171 . However. some DSAs exclude rarely-used data types.

Password to use when accessing the DB2 database.2 of the DB2 JDBC driver. see the DB2 website at http://www. JDBC Driver Version This DSA uses version 7. Username to use when accessing the DB2 database. Name of the primary DB2 database. Default is 6789.Appendix B: DSA Reference B. Connection port used by the primary DB2 database. Default is 6789. Default is 5.1 Administration Guide . Name of the backup DB2 database.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. Specifies that you do not want to use DSA failover with this data source. Primary Hostname Primary Port Primary Database Backup Hostname Backup Port Backup Database Disable Data Source Failover 172 Netcool/Impact 3. Connection port used by the backup DB2 database. Hostname of the system where the primary DB2 database is running. Data Source Configuration Properties Table B1 shows the configuration properties that you set when you create a DB2 data source. Table B1: DB2 Data Source Configuration Properties Property Data Source Name Username Password Maximum SQL Connections Description Name of the DB2 data source. Hostname of the system where the backup DB2 database is running. Maximum number of simultaneous SQL connections to the DB2 database.ibm. For more information on this driver.com/software/data/db2/.

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

London James Chen. 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 DSA supports the following delimiters: . The Flat File DSA offers slow performance when compared to other DSAs.San Francisco Data Source Configuration Properties Table B3 shows the configuration properties for Flat File data sources. You specify the filename when you create a flat file data type. where the first line specifies the names of the fields and each subsequent line represents a row of data. 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. Path of the text file that contains the data you want to access using this DSA. name.+ /.1 Administration Guide . . Field names can contain any character except the double quotation mark (") and the space character ( ). Table B3: Flat File Data Source Configuration Properties Property Data Source Name Directory Description Name of the data source.email.asingh@example.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. In this example.Appendix B: DSA Reference B.com. This text file must be a multi-line file.com. The following is an example of a character-delimited text file.com.New York Anna Singh.location Mark Gonzalez. Delimiters 174 Netcool/Impact 3. email and location are the field names. You must enclose the delimiter character in single quotation marks when you define it in the Netcool/Impact GUI.mgonzalez@example.jchen@example. name. 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. Delimiter character that separates fields in the text file. You cannot use the Flat File DSA to write information to a text file.

1 Administration Guide 175 . greater than (>) and LIKE.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. 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. you specify the name of the text file that contains the information you want to access. Special Considerations The Flat File DSA only supports the use of the equal operatory (=) in SQL filter statements. are not supported. like less than (<). Other operators. instead of a table name in the Base Table field. with the exception that. Netcool/Impact 3.

Name of the primary Informix database. Default is 1526. Specifies that you do not want to use Informix failover with this data source. see the Informix JDBC website at http://www-306.1 Administration Guide . Connection port used by the backup Informix database. Data Source Configuration Properties Table B1 shows the configuration properties that you set when you create an Informix data source. Server name where the backup Informix database resides. Default is 1526. Default is 5. Table B4: Informix Data Source Configuration Properties Property Data Source Name Username Password Maximum SQL Connections Description Name of the Informix data source. Server name where the primary Informix database resides. Primary Hostname Primary Port Primary Server Primary Database Backup Hostname Backup Port Backup Server Backup Database Disable Data Source Failover 176 Netcool/Impact 3.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. Hostname of the system where the backup Informix database is running. Password to use when accessing the Informix database. For more information.JC2 of the Informix JDBC driver. Name of the backup Informix database.com/software/data/informix/tools/jdbc/.40. Username to use when accessing the Informix database. Maximum number of simultaneous SQL connections to the Informix database.ibm. Hostname of the system where the primary Informix database is running. JDBC Driver Version This DSA uses version 1.Appendix B: DSA Reference B. Connection port used by the primary Informix database.

Table B5: Informix DSA Supported Data Types Informix Data Type INT.nn (for example. SMALLFLOAT. Netcool/Impact 3. 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. DEC CHAR. To ensure that Netcool/Impact functions correctly with this data type.Informix DSA Data Types Table B5 shows the supported Informix data types and their Netcool/Impact equivalents. VARCHAR DATE. If an Informix table contains datetime columns that use another format.10).1 Administration Guide 177 . INTERVAL. insert or update interval fields may cause runtime errors. make sure that datetime fields use the format yyyy-mm-dd hh:mm:ss. SMALLINT FLOAT. 2004-07-01 08:45:01. BYTE Netcool/Impact Data Type Integer Float String Date String Not supported Special Considerations Netcool/Impact supports the Informix DATETIME data type in YEAR to FRACTIONs format only. you must convert the column type before you can access the table using Netcool/Impact. 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. DATETIME MONEY BLOB.

JDBC Driver Version This DSA uses version 2. Connection port used by the primary MySQL database. Username to use when accessing the MySQL database. Specifies that you do not want to use MySQL failover with this data source. see the MySQL website at http://www.1 Administration Guide . Primary Hostname Primary Port Primary Database Backup Hostname Backup Port Backup Database Disable Data Source Failover 178 Netcool/Impact 3. Password to use when accessing the MySQL database. Default is 3306.5 MySQL DSA The MySQL DSA is a built-in component of Netcool/Impact that allows you to access information in a MySQL database.0 of the MySQL Connector/J JDBC driver. Hostname of the system where the backup MySQL database is running. Hostname of the system where the primary MySQL database is running.Appendix B: DSA Reference B. Name of the primary MySQL database. Name of the backup MySQL database. Table B6: MySQL Data Source Configuration Properties Property Data Source Name Username Password Maximum SQL Connections Description Name of the MySQL data source. Default is 5. Default is 3306. Data Source Configuration Properties Table B6 shows the configuration properties that you set when you create a MySQL data source. Maximum number of simultaneous SQL connections to the MySQL database.mysql. For more information. Connection port used by the backup MySQL database.org.

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

Appendix B: DSA Reference

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.

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

Primary Hostname Primary Port Backup Hostname Backup Port Disable Data Source Failover

180

Netcool/Impact 3.1 Administration Guide

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 INTEGER, UNSIGNED, INCR REAL CHAR, VARCHAR TIME BOOLEAN Netcool/Impact Data Type Integer Float String Integer String

Netcool/Impact 3.1 Administration Guide

181

Appendix B: DSA Reference

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.

182

Netcool/Impact 3.1 Administration Guide

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.

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

Primary Hostname Primary Port Primary SID Backup Hostname Backup Port Backup SID Disable Data Source Failover

Netcool/Impact 3.1 Administration Guide

183

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

PostgreSQL DSA B. Primary Hostname Primary Port Backup Hostname Backup Port Disable Data Source Failover Netcool/Impact 3. Connection port used by the primary PostgreSQL database. Hostname of the system where the backup PostgreSQL database is running.1 Administration Guide 185 . For more information on this driver.3 of the PostgreSQL JDBC 3. Specifies that you do not want to use PostgreSQL failover with this data source. Connection port used by the backup PostgreSQL database. Default is 5432. Default is 5432. Maximum number of simultaneous SQL connections to the PostgreSQL database. visit the PostregSQL JDBC website at http://jdbc.0 driver. Table B12: PostgreSQL Data Source Configuration Properties Property Data Source Name Username Password Maximum SQL Connections Description Name of the PostgreSQL data source. Username to use when accessing the PostgreSQL database. Hostname of the system where the primary PostgreSQL database is running.postgresql. Password to use when accessing the PostgreSQL database. Data Source Configuration Properties Table B12 shows the configuration properties that you set when you create a PostgreSQL data source. JDBC Version This DSA uses version 7.9 PostgreSQL DSA The PostgreSQL DSA is a built-in component of Netcool/Impact that allows you to access information in an PostgreSQL database. Default is 5.org.

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

JDBC Version The SQL Server DSA uses version 0.sourceforge. visit the jTDS website at http://jtds. Table B14: SQL Server Data Source Configuration Properties Property Data Source Name Username Password Maximum SQL Connections Description Name of the SQL Server data source.SQL Server DSA B. Hostname of the system where the primary SQL Server database is running. Maximum number of simultaneous SQL connections to the SQL Server database. Connection port used by the primary SQL Server database.net/. Username to use when accessing the SQL Server database. Primary Hostname Primary Port Backup Hostname Backup Port Disable Data Source Failover Netcool/Impact 3.8rc1of the jTDS JDBC driver. Connection port used by the backup SQL Server database.1 Administration Guide 187 . Default is 5432. Data Source Configuration Properties Table B14 shows the configuration properties that you set when you create an SQL Server data source. Password to use when accessing the SQL Server database. Default is 5. Specifies that you do not want to use SQL Server failover with this data source. For more information on this driver. Default is 5432.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. Hostname of the system where the backup SQL Server database is running.

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

Table B16: Sybase Data Source Configuration Properties Property Data Source Name Username Password Maximum SQL Connections Description Name of the Sybase data source. Maximum number of simultaneous SQL connections to the Sybase database.1 Administration Guide 189 . Specifies that you do not want to use Sybase failover with this data source. Default is 5000.5 of the Sybase jConnect JDBC driver. Password to use when accessing the Sybase database. Username to use when accessing the Sybase database. Default is 5.11 Sybase DSA The Sybase DSA is a built-in component of Netcool/Impact that allows you to access information in a Sybase database. Data Source Configuration Properties Table B16 shows the configuration properties that you set when you create a Sybase data source.Sybase DSA B. Default is 5000. Hostname of the system where the backup Sybase database is running. Supported Versions This DSA uses version 5. Hostname of the system where the primary Sybase database is running. Connection port used by the primary Sybase database. Connection port used by the backup Sybase database. Primary Hostname Primary Port Backup Hostname Backup Port Disable Data Source Failover Netcool/Impact 3.

Table B17: Sybase DSA Supported Data Types Sybase Data Type TINYINT. VARCHAR. MONEY BINARY. SMALLINT. INT NUMERIC. NVARCHAR SMALLDATETIME. VARBINARY. UNIVARCHAR.Appendix B: DSA Reference Data Types Table B17 shows the supported Sybase data types and their Netcool/Impact equivalents. FLOAT CHAR.1 Administration Guide . DECIMAL. IMAGE Netcool/Impact Data Type Integer Float String Date Float Not supported 190 Netcool/Impact 3. NCHAR. TEST. DATETIME SMALLMONEY. UNICHAR. REAL.

fm December 15.1 Administration Guide 191 .Index MMGuideIX. 2004 10:15 am Index A authentication 99 H host ID (License Server) 39 C cygwin Netcool/Impact database limitations 127 I IMPACT_HOME 90 ImpactUser role 99 importing Netcool/Impact data 156 D DB2 DSA 172 Informix DSA 176 installing GUI Server 60 License Server 36 Netcool/Impact 88 E event queue monitoring 144 exporting Netcool/Impact data 155 J JRExec server 134 configuring 136 running 135 F Flat File DSA 174 G GUI Server 54 Application Registry 58 architecture 59 components 58 configuring 66 environment variables 62 installing 60 Java Development Kit (AIX and HP-UX) 60 licensing 63 logging 77 running 65 Servlet Engine 58 uninstalling 78 GUI_HOME 62 L license files 33 License Server 28 architecture 32 command line tools (UNIX) 43 components 33 daemons (UNIX) 33 environment variables 37 host ID 39 installing 36 LMTOOLS (Windows) 45 running (UNIX) 43 running (Windows) 45 service (Windows) 33 system requirements 31 uninstalling 51 Netcool/Impact 3.

83 uninstalling 101 upgrading 91 O ObjectServer DSA 180 ODBC DSA 182 Oracle DSA 183 P PostgreSQL DSA 185 Q queue size monitoring 144 quorum licensing 48 GUI Server 63 License Server 48 Netcool/Impact 97 R runtime parameters.Index licenses feature codes 40 host ID 39 installing 39 licensing.1 Administration Guide . quorum 48 LMTOOLS 45 Netcool/Impact database 126 configuring 128 managing 130 running 129 Netcool/Impact Server 104 creating instances 106 deleting instances 110 monitoring instances 109 running instances (UNIX) 107 running instances (Windows) 108 Netcool/Impact server clustering 112 NETCOOL_LICENSE_PATH 38 M memory status monitoring 140 MySQL DSA 178 N ncgui_server 65 ncgui_shutdown 65 nci_db 129 nci_export 155 nci_import 156 nci_jrexec 135 nci_server 107 nci_shutdown 107 NCLICENSE 37 Netcool/Impact 80 architecture 87 backing up and restoring 100 components 85 configuring registry settings 98 CVS 86 DSAs 86 environment variables 90 installing 88 JRExec server 86 license feature codes 95 licensing 91 Operator View 86 server clustering 112 shared memory requirements 88 system requirements 56.using with nci_trigger 158 S self-monitoring 138 setting up 147 viewing information 150 server clustering 112 192 Netcool/Impact 3.

1 Administration Guide 193 .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 Netcool/Impact 3.

Index 194 Netcool/Impact 3.1 Administration Guide .

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

Contact Information 196 Netcool/Impact 3.1 Administration Guide .

Sign up to vote on this title
UsefulNot useful