Administration Guide - Impact

Netcool/ImpactVersion 6.1.0.1

Administration Guide

SC23-8829-04

!"#

NoteBefore using this information and the product it supports, read the information in Notices.

Edition notice

This edition applies to version 6.1.0.1 of IBM Tivoli Netcool/Impact and to all subsequent releases andmodifications until otherwise indicated in new editions.

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

ContentsAbout this publication . . . . . . . . viiIntended audience . . . . . . . . . . . . viiPublications . . . . . . . . . . . . . . vii

Netcool/Impact library . . . . . . . . . viiAccessing terminology online . . . . . . . viiAccessing publications online . . . . . . . viiiOrdering publications . . . . . . . . . viii

Accessibility . . . . . . . . . . . . . . viiiTivoli technical training . . . . . . . . . . viiiSupport for problem solving . . . . . . . . . ix

Obtaining fixes . . . . . . . . . . . . ixReceiving weekly support updates . . . . . . ixContacting IBM Software Support . . . . . . x

Conventions used in this publication . . . . . . xiiTypeface conventions . . . . . . . . . . xiiOperating system-dependent variables and paths xii

Chapter 1. Introduction . . . . . . . . 1Overview of deployments . . . . . . . . . . 1Deployment components . . . . . . . . . . 1

The Impact Server overview . . . . . . . . 1The Name Server overview . . . . . . . . 2The GUI Server overview . . . . . . . . . 2

Deployment types . . . . . . . . . . . . 3Setting up a deployment . . . . . . . . . . 3

Planning an installation. . . . . . . . . . 3Prerequisite scanner . . . . . . . . . . . 3Downloading the scanner . . . . . . . . . 4Running the scanner for Netcool/Impact . . . . 4Hardware requirements. . . . . . . . . . 5Assigning ports . . . . . . . . . . . . 6Installing components . . . . . . . . . . 10Configuring components . . . . . . . . . 10

Chapter 2. Installation and migration . . 11Before you start the installation . . . . . . . . 11Running the installer in the launchpad . . . . . 12Running the installer in GUI and console mode . . 12

Starting the installation . . . . . . . . . 14Selecting the installation directory . . . . . . 14Selecting the type of installation . . . . . . 15Configuring the Tivoli Integrated Portal profile 15Selecting installation components . . . . . . 15Configuring the user registry . . . . . . . 16Configuring the event source . . . . . . . 16Configuring WebSphere profile ports . . . . . 17Configuring Impact Server WebSphere profileports . . . . . . . . . . . . . . . 17Configuring the Name Server . . . . . . . 18Configuring the Impact Server instance . . . . 18Selecting and configuring a version control . . . 19

Silent mode . . . . . . . . . . . . . . 19Running the installer in silent mode . . . . . 20Silent installation response file . . . . . . . 20

Installing in a shared environment. . . . . . . 23

Installing the GUI Server into an existing TIPinstallation . . . . . . . . . . . . . 23Installing both components into an existing TIPinstallation . . . . . . . . . . . . . 24

Post installation steps . . . . . . . . . . . 25Updating the wimconfig.xml file . . . . . . 25Restoring the system from backup. . . . . . 26Increasing the memory for the Java VirtualMachine on the Impact profile . . . . . . . 26Configuring the default ObjectServer data source 27Adding JDBC drivers to the shared library . . . 27Creating the JRExec service . . . . . . . . 27Post installation utility. . . . . . . . . . 28

Migrating to version 6.1 . . . . . . . . . . 28The migration script . . . . . . . . . . 28Scenario 1: Migrating 5.x servers to version 6.1that is installed on the same machine . . . . . 29Scenario 2: Migrating 5.x servers to version 6.1,with both 6.1 servers installed on differentmachines . . . . . . . . . . . . . . 30Post migration steps . . . . . . . . . . 33

Installation logs . . . . . . . . . . . . . 34Uninstalling the deployment. . . . . . . . . 34

Uninstalling the deployment on Windowsplatforms . . . . . . . . . . . . . . 34Uninstalling the deployment on UNIX platforms 35

Chapter 3. Managing the Impact Server 37Creating Impact Server instances . . . . . . . 37Using Impact Server administration scripts . . . . 37Configuring RMI ports . . . . . . . . . . 37Monitoring deployment components . . . . . . 38

Monitoring server instances . . . . . . . . 38Log4j properties file . . . . . . . . . . 39Monitoring services. . . . . . . . . . . 39

Deleting Impact Server instances . . . . . . . 39Read-only mode . . . . . . . . . . . . . 40

Enabling read-only mode . . . . . . . . . 40Stopping and starting the Impact Server . . . . . 40Connection request to mail server . . . . . . . 41

Changing the time interval on a connectionrequest to the mail server. . . . . . . . . 41

The Impact EAR file . . . . . . . . . . . 41FIPS Compliance . . . . . . . . . . . . 42

Enabling FIPS on the Impact Server . . . . . 42

Chapter 4. Managing the GUI Server . . 45Stopping and starting the GUI Server. . . . . . 45Enabling FIPS on the GUI Server . . . . . . . 45Central user registry . . . . . . . . . . . 47

Adding an external LDAP repository . . . . . 48Configuring an external LDAP repository . . . 49Managing LDAP users in the console. . . . . 51Configuring an SSL connection to an LDAPserver . . . . . . . . . . . . . . . 52

Copyright IBM Corp. 2006, 2011 iii

Configuring an SSL connection to theObjectServer . . . . . . . . . . . . . 53

Configuring LDAP or Active Directory . . . . . 54Single sign-on . . . . . . . . . . . . . 56

Configuring single sign-on . . . . . . . . 57

Chapter 5. Server clustering . . . . . 59Server clustering overview . . . . . . . . . 59The Impact Server cluster components . . . . . 59The Name Server cluster components. . . . . . 60Setting up a cluster . . . . . . . . . . . . 60Sharing nameservers with TBSM . . . . . . . 62

Configuring shared name servers with TivoliBusiness Service Manager . . . . . . . . 62

The Impact Server clustering process . . . . . . 64Startup in an Impact Server cluster . . . . . 65Failback in an Impact Server cluster . . . . . 65

The Name Server clustering process overview . . . 65Command replication in a Name Server cluster 66Failure and recovery in a Name Server cluster. . 66

Runtime analysis of the server logs . . . . . . 66Checking the cluster status in the browser . . . . 67The nameserver.props configuration file . . . . . 67The web.xml configuration file . . . . . . . . 68The Impact Server properties file . . . . . . . 70Configuring the secondary server to wait for theprimary server . . . . . . . . . . . . . 71Configuring the event processor service in a cluster 71

Chapter 6. Version control . . . . . . 73Version control overview . . . . . . . . . . 73Version control process . . . . . . . . . . 73Configuring version control . . . . . . . . . 73Version control script . . . . . . . . . . . 74

Checking out files . . . . . . . . . . . 74Checking in files. . . . . . . . . . . . 75Adding files . . . . . . . . . . . . . 75Unchecking out files . . . . . . . . . . 75Creating a checkpoint . . . . . . . . . . 75Updating the sandbox . . . . . . . . . . 76

Chapter 7. Managing the databaseserver . . . . . . . . . . . . . . . 77The database server overview . . . . . . . . 77Setting the database port . . . . . . . . . . 77Running the database server. . . . . . . . . 77Resetting the database . . . . . . . . . . . 78Connecting to the database with the command lineclient . . . . . . . . . . . . . . . . 78Backing up the database . . . . . . . . . . 78Restoring the database. . . . . . . . . . . 78

Chapter 8. JRExec server. . . . . . . 79Overview of the JRExec server . . . . . . . . 79Starting the JRExec server . . . . . . . . . 79Stopping the JRExec server . . . . . . . . . 79The JRExec server configuration properties . . . . 80JRExec server logging . . . . . . . . . . . 80

Chapter 9. Self-monitoring . . . . . . 81

Self-monitoring overview . . . . . . . . . . 81Self-monitoring in a server cluster . . . . . . . 81Setting up self-monitoring using the GUI . . . . 81Running self-monitoring using the GUI . . . . . 83Running self-monitoring using the command lineinterface . . . . . . . . . . . . . . . 83Setting the ObjectServer Data Source for monitoringevents . . . . . . . . . . . . . . . . 83Memory status monitoring . . . . . . . . . 83

Disabling buffer and cache size reporting in freememory calculations on Linux . . . . . . . 84Configuring available system memory for selfmonitoring . . . . . . . . . . . . . 84Setting the memory for the Java Virtual Machineon the Impact profile . . . . . . . . . . 84Setting Java Virtual Machine memory forTIPProfile . . . . . . . . . . . . . . 86System memory status. . . . . . . . . . 86Combined memory status . . . . . . . . 87Memory status severity . . . . . . . . . 87Memory event fields . . . . . . . . . . 87Checking if memory status monitoring is enabled 88Enabling memory status monitoring . . . . . 88Disabling memory status monitoring . . . . . 88Viewing current memory status. . . . . . . 88Viewing memory status history. . . . . . . 89Viewing the total JVM heap size . . . . . . 89Viewing the maximum JVM heap size . . . . 89Viewing the free system memory . . . . . . 89Checking if memory status events arededuplicated . . . . . . . . . . . . . 89Disabling memory status event deduplication . . 89Viewing memory status event intervals . . . . 90Changing memory status event intervals . . . 90

Queue status monitoring . . . . . . . . . . 90Changing the sampling frequency for the queuemonitoring . . . . . . . . . . . . . 90Queue status severity . . . . . . . . . . 91Queue status event fields . . . . . . . . . 91Checking if queue status monitoring is enabled 92Enabling queue status monitoring . . . . . . 92Disabling queue status monitoring. . . . . . 92Viewing the current queue status . . . . . . 92Viewing the queue status history . . . . . . 93Checking if queue status event deduplication isenabled. . . . . . . . . . . . . . . 93Enabling queue status event deduplication . . . 93Disabling queue status event deduplication. . . 93Viewing queue status event intervals . . . . . 93Changing queue status event intervals . . . . 93

Data source status monitoring . . . . . . . . 94Data source status events . . . . . . . . . 94Data source status event fields . . . . . . . 95Checking if data source status monitoring isenabled. . . . . . . . . . . . . . . 96Enabling data source status monitoring . . . . 96Disabling data source status monitoring . . . . 97Viewing the current data source status . . . . 97Viewing the data source status history . . . . 97Deduplication of data source monitoring events 97Pairing problem and resolution events together 98

iv Netcool/Impact: Administration Guide

Verbose mode in data source monitoring . . . 99Cluster Status Monitoring . . . . . . . . . 99

Starting self-monitoring on a secondary clustermember . . . . . . . . . . . . . . 99Cluster status events . . . . . . . . . . 99Cluster status event fields . . . . . . . . 100Checking if cluster status monitoring is enabled 101Enabling cluster status monitoring . . . . . 101Disabling cluster status monitoring . . . . . 101Viewing the current cluster status . . . . . 102Viewing the cluster status history . . . . . 102Enabling deduplicating of cluster monitoringevents . . . . . . . . . . . . . . . 102

Service status monitoring . . . . . . . . . 102Service status events . . . . . . . . . . 102Self monitoring service configuration window 103Deduplication of service monitoring events . . 103Viewing the total time a service ran for servicemonitoring . . . . . . . . . . . . . 104Service status event fields . . . . . . . . 104Checking if service status monitoring is enabled 105Enabling service status monitoring . . . . . 105Disabling service status monitoring . . . . . 105Viewing the current service status . . . . . 105Viewing the service status history . . . . . 105

Chapter 10. Secure communication 107Setting up SSL communication . . . . . . . 107

Enabling SSL on the Impact Server . . . . . 108Enabling SSL on the GUI Server . . . . . . 108Enabling SSL on the Name Server . . . . . 109Exchanging certificates between the GUI Serverand the Impact Server . . . . . . . . . 109Exchanging certificates between Impact Servers 110Disabling nonsecure interfaces . . . . . . . 111Enabling SSL for the command line interface . . 111Enabling SSL communication with theObjectServer . . . . . . . . . . . . . 111

Generating a self signed certificate . . . . . . 112Adding a certificate to the application server truststore . . . . . . . . . . . . . . . . 113

Chapter 11. Command-line tools . . . 115nci_crypt . . . . . . . . . . . . . . . 115nci_export . . . . . . . . . . . . . . 115nci_import . . . . . . . . . . . . . . 116nci_trigger . . . . . . . . . . . . . . 116nci_policy . . . . . . . . . . . . . . 117

nci_removeserver . . . . . . . . . . . . 118Using the command-line manager . . . . . . 119JavaScript in the command-line manager . . . . 120Event Processor commands. . . . . . . . . 120Email Reader commands . . . . . . . . . 122Email Sender commands . . . . . . . . . 123Policy Activator commands. . . . . . . . . 123Hibernating Policy Activator commands . . . . 124Policy Logger commands . . . . . . . . . 124OMNIbus Event Reader commands . . . . . . 126Database Event Reader commands . . . . . . 128Database Event Listener commands . . . . . . 130JMS Message Listener commands. . . . . . . 131Using WebServices through the command line . . 132

Creating groups, and users . . . . . . . . 133Mapping groups, and users to roles . . . . . 134

Appendix A. Accessibility . . . . . . 135

Appendix B. Notices . . . . . . . . 137Trademarks . . . . . . . . . . . . . . 139

Glossary . . . . . . . . . . . . . 141A . . . . . . . . . . . . . . . . . 141B . . . . . . . . . . . . . . . . . 141C . . . . . . . . . . . . . . . . . 141D . . . . . . . . . . . . . . . . . 141E . . . . . . . . . . . . . . . . . 142F . . . . . . . . . . . . . . . . . 143G . . . . . . . . . . . . . . . . . 143H . . . . . . . . . . . . . . . . . 143I. . . . . . . . . . . . . . . . . . 143J. . . . . . . . . . . . . . . . . . 144K . . . . . . . . . . . . . . . . . 144L . . . . . . . . . . . . . . . . . 144M . . . . . . . . . . . . . . . . . 145N . . . . . . . . . . . . . . . . . 145O . . . . . . . . . . . . . . . . . 145P . . . . . . . . . . . . . . . . . 145S . . . . . . . . . . . . . . . . . 145U . . . . . . . . . . . . . . . . . 147V . . . . . . . . . . . . . . . . . 147W . . . . . . . . . . . . . . . . . 147X . . . . . . . . . . . . . . . . . 147

Index . . . . . . . . . . . . . . . 149

Contents v

vi Netcool/Impact: Administration Guide

About this publicationThe Netcool/Impact Administration Guide contains instructions on installing,configuring, running, and monitoring Netcool/Impact.

Intended audienceThis publication is for users who are responsible for installing, configuring,running and monitoring Netcool/Impact.

PublicationsThis section lists publications in the Netcool/Impact library and relateddocuments. The section also describes how to access Tivoli publications onlineand how to order Tivoli publications.

Netcool/Impact libraryv Quick Start Guide, CF39PMLProvides concise information about installing and running Netcool/Impact forthe first time.

v Administration Guide, SC23882904Provides information about installing, running and monitoring the product.

v User Interface Guide, SC23883004Provides instructions for using the Graphical User Interface (GUI).

v Policy Reference Guide, SC23883104Contains complete description and reference information for the Impact PolicyLanguage (IPL).

v DSA Reference Guide, SC23883204Provides information about data source adaptors (DSAs).

v Operator View Guide, SC23885104Provides information about creating operator views.

v Solutions Guide, SC23883404Provides end-to-end information about using features of Netcool/Impact.

v Integrations Guide, SC27283402Contains instructions for integrating Netcool/Impact with other IBM softwareand other vendor software.

v Troubleshooting Guide, GC27283302Provides information about troubleshooting the installation, customization,starting, and maintaining Netcool/Impact.

Accessing terminology onlineThe IBM Terminology Web site consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology Web site at thefollowing Web address:

http://www.ibm.com/software/globalization/terminology

Copyright IBM Corp. 2006, 2011 vii

Accessing publications onlinePublications are available from the following locations:v The Quick Start DVD contains the publications that are in the product library.The format of the publications is PDF, HTML, or both. Refer to the readme fileon the DVD for instructions on how to access the documentation.

v Tivoli Information Center web site at http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcoolimpact.doc6.1/welcome.html. IBM postspublications for all Tivoli products, as they become available and whenever theyare updated to the Tivoli Information Center Web site.

Note: If you print PDF documents on paper other than letter-sized paper, setthe option in the File Print window that allows Adobe Reader to printletter-sized pages on your local paper.

v Tivoli Documentation Central at http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Impact. You can also access publications of theprevious and current versions of Netcool/Impact from Tivoli DocumentationCentral.

v The Netcool/Impact wiki contains additional short documents and additionalinformation and is available at https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Netcool%20Impact.

Ordering publicationsYou can order many Tivoli publications online at http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivolipublications. To locate the telephone number of your local representative, performthe following steps:1. Go to http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.2. Select your country from the list and click Go.3. Click About this site in the main panel to see an information page that

includes the telephone number of your local representative.

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

For additional information, see Appendix A, Accessibility, on page 135.

Tivoli technical trainingFor Tivoli technical training information, refer to the following IBM TivoliEducation Web site at http://www.ibm.com/software/tivoli/education.

viii Netcool/Impact: Administration Guide

Support for problem solvingIf you have a problem with your IBM software, you want to resolve it quickly. Thissection describes the following options for obtaining support for IBM softwareproducts:v Obtaining fixesv Receiving weekly support updatesv Contacting IBM Software Support on page x

Obtaining fixesA product fix might be available to resolve your problem. To determine whichfixes are available for your Tivoli software product, follow these steps:1. Go to the IBM Software Support Web site at http://www.ibm.com/software/

support.2. Navigate to the Downloads page.3. Follow the instructions to locate the fix you want to download.4. If there is no Download heading for your product, supply a search term, error

code, or APAR number in the search field.

For more information about the types of fixes that are available, see the IBMSoftware Support Handbook at http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html.

Receiving weekly support updatesTo receive weekly e-mail notifications about fixes and other software support news,follow these steps:1. Go to the IBM Software Support Web site at http://www.ibm.com/software/

support.2. Click the My IBM in the toobar. Click My technical support.3. If you have already registered for My technical support, sign in and skip to

the next step. If you have not registered, click register now. Complete theregistration form using your e-mail address as your IBM ID and click Submit.

4. The Edit profile tab is displayed.5. In the first list under Products, select Software. In the second list, select a

product category (for example, Systems and Asset Management). In the thirdlist, select a product sub-category (for example, Application Performance &Availability or Systems Performance). A list of applicable products isdisplayed.

6. Select the products for which you want to receive updates.7. Click Add products.8. After selecting all products that are of interest to you, click Subscribe to email

on the Edit profile tab.9. In the Documents list, select Software.

10. Select Please send these documents by weekly email.11. Update your e-mail address as needed.12. Select the types of documents you want to receive.13. Click Update.

If you experience problems with the My technical support feature, you can obtainhelp in one of the following ways:

About this publication ix

OnlineSend an e-mail message to [email protected], describing your problem.

By phoneCall 1-800-IBM-4You (1-800-426-4409).

World Wide Registration Help deskFor word wide support information check the details in the following link:https://www.ibm.com/account/profile/us?page=reghelpdesk

Contacting IBM Software SupportBefore contacting IBM Software Support, your company must have an active IBMsoftware maintenance contract, and you must be authorized to submit problems toIBM. The type of software maintenance contract that you need depends on thetype of product you have:v For IBM distributed software products (including, but not limited to, Tivoli,Lotus, and Rational products, and DB2 and WebSphere products that run onWindows or UNIX operating systems), enroll in Passport Advantage in one ofthe following ways:

OnlineGo to the Passport Advantage Web site at http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm .

By phoneFor the phone number to call in your country, go to the IBM WorldwideIBM Registration Helpdesk Web site at https://www.ibm.com/account/profile/us?page=reghelpdesk.

v For customers with Subscription and Support (S & S) contracts, go to theSoftware Service Request Web site at https://techsupport.services.ibm.com/ssr/login.

v For customers with IBMLink, CATIA, Linux, OS/390, iSeries, pSeries,zSeries, and other support agreements, go to the IBM Support Line Web site athttp://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.

v For IBM eServer software products (including, but not limited to, DB2 andWebSphere products that run in zSeries, pSeries, and iSeries environments), youcan purchase a software maintenance agreement by working directly with anIBM sales representative or an IBM Business Partner. For more informationabout support for eServer software products, go to the IBM Technical SupportAdvantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go tothe contacts page of the IBM Software Support Handbook on the Web athttp://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html andclick the name of your geographic region for phone numbers of people whoprovide support for your location.

To contact IBM Software support, follow these steps:1. Determining the business impact on page xi2. Describing problems and gathering information on page xi3. Submitting problems on page xi

x Netcool/Impact: Administration Guide

Determining the business impactWhen you report a problem to IBM, you are asked to supply a severity level. Usethe following criteria to understand and assess the business impact of the problemthat you are reporting:

Severity 1The problem has a critical business impact. You are unable to use theprogram, resulting in a critical impact on operations. This conditionrequires an immediate solution.

Severity 2The problem has a significant business impact. The program is usable, butit is severely limited.

Severity 3The problem has some business impact. The program is usable, but lesssignificant features (not critical to operations) are unavailable.

Severity 4The problem has minimal business impact. The problem causes little impacton operations, or a reasonable circumvention to the problem wasimplemented.

Describing problems and gathering informationWhen describing a problem to IBM, be as specific as possible. Include all relevantbackground information so that IBM Software Support specialists can help yousolve the problem efficiently. To save time, know the answers to these questions:v Which software versions were you running when the problem occurred?v Do you have logs, traces, and messages that are related to the problemsymptoms? IBM Software Support is likely to ask for this information.

v Can you re-create the problem? If so, what steps were performed to re-create theproblem?

v Did you make any changes to the system? For example, did you make changesto the hardware, operating system, networking software, and so on.

v Are you currently using a workaround for the problem? If so, be prepared toexplain the workaround when you report the problem.

Submitting problemsYou can submit your problem to IBM Software Support in one of two ways:

OnlineClick Submit and track problems on the IBM Software Support site athttp://www.ibm.com/software/support/probsub.html. Type yourinformation into the appropriate problem submission form.

By phoneFor the phone number to call in your country, go to the contacts page ofthe IBM Software Support Handbook at http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html and click the name of yourgeographic region.

If the problem you submit is for a software defect or for missing or inaccuratedocumentation, IBM Software Support creates an Authorized Program AnalysisReport (APAR). The APAR describes the problem in detail. Whenever possible,IBM Software Support provides a workaround that you can implement until theAPAR is resolved and a fix is delivered. IBM publishes resolved APARs on theSoftware Support Web site daily, so that other users who experience the sameproblem can benefit from the same resolution.

About this publication xi

Conventions used in this publicationThis publication uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and margin graphics.

Typeface conventionsThis publication uses the following typeface conventions:

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

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

v Keywords and parameters in textItalic

v Citations (examples: titles of publications, diskettes, and CDsv Words defined in text (example: a nonswitched line is called a

point-to-point line)v Emphasis of words and letters (words as words example: "Use the word

that to introduce a restrictive clause."; letters as letters example: "TheLUN address must start with the letter L.")

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

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

v Examples and code examplesv File names, programming keywords, and other elements that are difficultto distinguish from surrounding text

v Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Operating system-dependent variables and pathsThis publication uses the UNIX convention for specifying environment variablesand for directory notation.

When using the Windows command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with a backslash (\) indirectory paths. The names of environment variables are not always the same inthe Windows and UNIX environments. For example, %TEMP% in Windowsenvironments is equivalent to $TMPDIR in UNIX environments.

Note: If you are using the bash shell on a Windows system, you can use the UNIXconventions.

xii Netcool/Impact: Administration Guide

Chapter 1. IntroductionA Netcool/Impact deployment is an installation of theNetcool/Impact componentsin your environment.

Overview of deploymentsNetcool/Impact can be deployed as a single system installation, or a distributedinstallation.

To set up the deployment, you run the installer programs on systems in yourenvironment. The installer copies the program files to the systems, and sets theminimal required configuration options. After a successful installation of all thecomponents, you can then customize the configuration according to your needs. Torun the deployment, you use a set of administration scripts, or servicesadministration tools, depending on your operating system.

A centralized logging feature is provided that is used by both the Impact Serverand the GUI Server, to monitor application events and status during applicationruntime. In addition, you can use application subcomponents, like for exampleservices, to configure them to log their activity to files.

You can use the ObjectServer as an external authentication and authorizationsource for your deployment.

Deployment componentsA Netcool/Impact deployment consists of the Impact Server, Name Server, and theGUI Server.

Impact ServerThe Impact Server is responsible for managing the data model, runningservices, and policies that make up your Netcool/Impact implementation,and runs the policies in real time in response to events that occur in yourenvironment.

Name ServerThe Name Server is a subcomponent of the Impact Server that providesregistration functionality for the GUI Server and the Impact Server.

GUI ServerThe GUI Server is responsible for generating the dynamic Web-based userinterface of Netcool/Impact.

The Impact Server overviewThe Impact Server is responsible for managing the data model, running services,and policies that make up your Netcool/Impact implementation, and runs thepolicies in real time in response to events that occur in your environment.

The Impact Server runs as an application instance inside a Java application server,by default the embedded version of WebSphere Application Server. The applicationserver is deployed automatically as part of the Netcool/Impact installation.

Copyright IBM Corp. 2006, 2011 1

Important: It is possible to run multiple Impact Server instances per system fortesting and validation purposes. In a production environment it is recommended torun one instance per system to achieve better resiliency and performance.

You can run Impact Servers in a clustered server configuration. Such aconfiguration consists of multiple instances of the Impact Server installed onseparate systems but configured in such a way that they act as a single server. Thistype of configurations provides failover, failback, replication, and load balancingfunctions.

Although the Impact Server starts and stops automatically when the applicationserver, where it resides, is started or stopped, you can also start and stop itindependently of the application server. You change the configuration of theImpact Server by editing its properties file.

A subcomponent of the Impact Server, the Name Server, provides applicationregistry functionality for the Netcool/Impact components. You can use its anothersubcomponent, the JRExec Server, to run external commands, scripts, andapplications from within a policy.

The Impact Server uses a centralized logging feature, that incorporates ApacheLog4j logging functionality.

The Name Server overviewThe Name Server is a subcomponent of the Impact Server that providesregistration functionality for the GUI Server and the Impact Server.

Applications that use the GUI Server register with the Name Server at startup. TheGUI Server uses the information stored in the Name Server when brokering HTTPrequests between users' Web browsers and the applications. The Name Server alsoplays a central role in server clustering.

The GUI Server overviewThe GUI Server is responsible for generating the dynamic Web-based user interfaceof Netcool/Impact.

It brokers requests between end users' web browsers and Netcool/Impact, andreturns the graphical views that you use to work with the data model, services,and policies.

The default GUI Server for Netcool/Impact 6.1 and later is the Tivoli IntegratedPortal server.

An instance of the Tivoli Integrated Portal server is created during the installation,if you chose to install the GUI Server as one of the deployment components. Theinstaller sets all of the default configuration properties for the server. After theinstallation, you can change the configuration of the GUI Server by editing itsproperties files.

The Tivoli Integrated Portal server starts and stops automatically when theapplication server, where it resides, is started or stopped, but you can also start,and stop it independently of the application server.

2 Netcool/Impact: Administration Guide

Deployment typesThe supported deployment types are a single-system deployment, and adistributed deployment.

Single-system deployment

A single-system deployment consists of the Impact Server and the GUIServer installed on a single system in your environment. A single-systemdeployment is suitable for testing and demonstration purposes.

Distributed deployment

A distributed deployment consists of one or more instances of the ImpactServer and the GUI Server installed across different systems in yourenvironment. A distributed deployment is suitable for most real-worldimplementations of Netcool/Impact.

A typical distributed deployment can consist of two or more instances ofthe Impact Server installed on separate systems and configured as part of aserver cluster, and an instance of the GUI Server installed on a system thatis configured to allow users' Web browsers to access the GUI. Serverclustering provides failover and load-balancing functionality for the ImpactServer instances.

Setting up a deploymentBefore you start setting up Netcool/Impact, you must have an understanding ofhow Netcool/OMNIbus and other Netcool products are installed and used in yourenvironment.

Specifically, you must know what type of alerts are collected by Netcool probesand monitors, and how the alerts are stored in the Netcool/OMNIbus ObjectServerdatabase. You must also have an understanding of your network topology,including the types of systems, devices, and applications that exist on the networkand how they are monitored by Netcool/OMNIbus.

Planning an installationAfter you understand how Netcool/Impact, and Netcool OMNIbus are installedand used in your environment, you can plan your deployment.

For testing or demonstration purposes, a good practice is to installNetcool/Impact, and its components on a single system. This type of deploymentrequires little planning and is the easiest to create and maintain.

For real life production deployments, you must take into account your goals,requirements, and available resources before you install the software. One bestpractice is to create a diagram of the installation you want to create before youbegin. IBM technical support can help you determine what type of hardware youneed to run the deployment and how to configure it to fit your requirements.

Prerequisite scannerDownload and run the IBM Prerequisite Scanner as part of your installationplanning.

Chapter 1. Introduction 3

IBM Prerequisite Scanner is a stand-alone prerequisite checking tool that analyzessystem environments before the installation or upgrade of a Tivoli product or IBMsolution. The scanner includes configuration files for Netcool/Impact.

Downloading the scannerDownload the scanner for your operating system.

About this task

This procedure describes where to find the scanner and the information needed toinstall the scanner.

Procedure1. Download the scanner version for your operating system from this page:

http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Prerequisite+Scanner&release=All&platform=All&function=all You can also download the scannerfrom the link on the launchpad.

2. For general instructions on downloading, installing, and running the scanner,click More Information for the version you are downloading.

3. Extract the scanner files to a location on your Netcool/Impact host. Thislocation is called the ips_root directory in this topic.

What to do next

Run the scanner on your host system.

Running the scanner for Netcool/ImpactYou need to use the Netcool/Impact specific options described here when you runthe scanner.

Procedure

Open a command window and enter one of the following commands:v Windows: prereq_checker.bat "NCI_06200000" detailv UNIX: prereq_checker.sh "NCI_06200000" detail

Results

There are two possible results:

FAIL: If the target server does not meet the prerequisites specified in the cfgfiles, the scanner returns FAIL for the Netcool/Impact check. The failedprerequisites are displayed in the screen output. To resolve the failure, takethe appropriate actions, for example, install the missing operating systempackages, or increase disk space.

PASS:If the target server has all the prerequisite specified in the cfg files, thescanner returns PASS for the Netcool/Impact check. If the scanner returnsPASS for the Netcool/Impactcheck you can install, configure and start theproduct on the target server.

v For more information about the prerequisite scanner, see the IBM PrerequisiteScanner Information Center, available from the following URL:


http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=%2Fcom.ibm.ips.doc_1.1.1.7%2Fips_ic-homepage.html

Hardware requirementsMinimum hardware requirements for Netcool/Impact configurations when the TIPand Impact profiles run on the same machines, different machines, and minimumhardware requirements for a development environment.

CAUTION: On UNIX and Linux platforms, before installing Netcool/Impact orNetcool/Impact, ensure that there is no tmp subdirectory under the /tmp directory.Otherwise the installation will fail.

Netcool/Impact requires a minimum Dual Core 3.0. GHZ processor.

Minimum hardware requirements for a TIP profile and an Impact profilerunning on the same physical machinev Bitness: 64 bit hardwarev Minimum Memory: 6 GBv Memory: TIP Profile: 2 GB Impact Profile: 2 GB

v AIX, Linux, and Solaris, hard disk space: 5 GB free space.v Windows, hard disk space: 8 GB free space.

Minimum hardware requirements for a TIP profile and an Impact Profilerunning on different physical machinesv Bitness: 32 or 64 bitv Minimum Memory: 3 GBv Memory: TIP Profile: 2 GB Impact Profile: 2 GB

v AIX, Linux, and Solaris, hard disk space: 5 GB free space.v Windows, hard disk space: 8 GB free space.

If extensive report collection is enabled, additional hardware requirements areneeded. A minimum of 2-GB additional hard disk space is required for the ImpactProfile.

Minimum hardware requirements for a development environment

In a development environment, where Netcool/Impact is used and you want totest the policies before moving into production, the following list shows theminimum hardware required:

The TIP profile and the Impact profile can be installed on the same system.v Bitness: 32 or 64 bitv Minimum Memory: 3 GBv Memory: TIP Profile: 521 MB Memory: Impact Profile: 1.2 GB


v AIX, Linux, and Solaris, hard disk space: 5 GB free space.v Windows, hard disk space: 8 GB free space.As additional policies are added to the Impact Server, more hard disk space isrequired.

For information about software and operating system requirements forNetcool/Impact see the following wiki, Netcool/Impact: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Netcool%20Impact

For information about increasing memory heap size, and to modify the heapmemory on the ImpactProfile, see Setting the memory for the Java VirtualMachine on the Impact profile on page 84 and on the TIPProfile, see SettingJava Virtual Machine memory for TIPProfile on page 86.

Important: Installing on RHEL 6.x.

There are two installer programs for each operating system supported, one for 32bit platforms and one for 64 bit platforms. This means that the WebSphere

Application Server, Netcool/Impact, and Tivoli Business Service Manager productsfor the 32 bit installer are 32 bit and for the 64 bit installer are 64 bit.

However, the actual installer program itself is 32 bit regardless of the 32 bit or 64bit package.

When installing RHEL 6.x 64 bit, the Netcool/Impact and Tivoli Business ServiceManager installer requires 32 bit libraries to run the installer program.

RHEL 6.x does not install 32 bit libraries by default.

Install libstdc++.so.5 in RHEL 6 and above, this library is supplied in thecompat-libstdc++-33.i686 package for 32 bit and compat-libstdc++33.x86_64package for 64-bit.

For more information about preparing Linux systems for a WebSphere

Application Server installation, see the following URL: http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.base.doc/info/aes/ae/welcome_base.html.

Navigate to the section, WebSphere Application Server (Distributed operating systems),Version 7.0 > Installing your application serving environment > Distributed operatingsystems > Preparing the operating system for product installation > Preparing Linuxsystems for installation.

Assigning portsMethods to assign ports in a Netcool/Impact installation.

The Netcool/Impact installer checks for port availability in the following ways:v GUI and console mode: Simple installation: The Netcool/Impact installer has an internal default start

port address (9080) for the Impact Server and (16310) for the GUI Server andgenerates the other port addresses. In a simple installation, if the default startports are not available, the Netcool/Impact installer checks incrementally for


the next available port and uses this port as the new starting port. TheNetcool/Impact installer generates the remaining ports from the new startingport.

Advanced installation: You can assign the starting address for the ports forthe Impact Server and for the GUI Server. The Netcool/Impact installer usesthese ports to generate the ports to be used. If any of the provided ports arealready in use the Netcool/Impact installer checks incrementally for the nextavailable port and uses this port as the new starting port. TheNetcool/Impact installer generates the remaining ports from the new startingport.

v Silent installation: The Netcool/Impact installer requires a set of sequentiallynumbered ports. The sequence of ports is supplied during installation in theresponse file. The Netcool/Impact installer checks that the number of requiredports (starting with the initial port value) are available before assigning them. Ifone of the ports in the sequence is already in use, the Netcool/Impact installerautomatically terminates the installation process. You must specify a differentrange of ports in the response file.

Ports used by Netcool/Impact and Tivoli Integrated PortalUse the following tables to identify the ports required to install Netcool/Impactand the Tivoli Integrated Portal.

Default ports to be defined for the Impact Server (Impact Profile) are shown in theImpact Server silent response file installSilent_response.txt. Default ports forthe Impact Server apply to all operating systems except where otherwise stated.

Table 1. Default ports to be defined for Netcool/Impact

ParameterPortNumber

IAGLOBAL_EWAS_HTTP_PORT

Note: The Netcool/Impact installer uses port 9080 for nameserverconfiguration by default for all operating systems except AIX. When thewsmserver is running on AIX it uses port 9090. The Netcool/Impact installerdoes not use the default port 9080 for nameserver configuration but the nextavailable port which is 9110. In the nameserver panel, chooselocalhost:9110 as the nameserver port.

Before you install Netcool/Impact, you can check if the wsmserver is usingport 9090. Execute nestat -na | grep wsmserver. If port 9090 is not beingused, the Netcool/Impact installer can use port 9080 as the default port.

9080

IAGLOBAL_EWAS_WC_defaulthost_secure 9081

IAGLOBAL_EWAS_BOOTSTRAP_ADDRESS 9082

IAGLOBAL_EWAS_SOAP_CONNECTOR_ADDRESS 9083

IAGLOBAL_EWAS_IPC_CONNECTOR_ADDRESS 9084

IAGLOBAL_EWAS_ADMIN_PORT 9085

IAGLOBAL_EWAS_WC_adminhost_secure. Use this port to import SSLcertificates to be used in the Impact Server.

9086

IAGLOBAL_EWAS_DCS_UNICAST_ADDRESS 9088

IAGLOBAL_EWAS_ORB_LISTENER_ADDRESS 9090

IAGLOBAL_EWAS_SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 9091

IAGLOBAL_EWAS_CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 9092


Table 1. Default ports to be defined for Netcool/Impact (continued)

ParameterPortNumber

IAGLOBAL_EWAS_CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 9093

IAGLOBAL_EWAS_REST_NOTIFICATION_PORT 9094

For information about viewing the assigned ports, see Viewing the Impact Serverprofile.

The following default ports are defined for the GUI Server (Tivoli Integrated PortalProfile) and are shown in the GUI Server silent response file:

Table 2. Default ports to be defined for the GUI Server

ParameterPortNumber

IAGLOBAL_WC_defaulthost 16310

IAGLOBAL_WC_defaulthost_secure. Make sure this port is open because theNetcool/Impact UI is accessed through http://hostname:16311/ibm/console.

16311

IAGLOBAL_BOOTSTRAP_ADDRESS 16312

IAGLOBAL_SOAP_CONNECTOR_ADDRESS 16313

IAGLOBAL_IPC_CONNECTOR_ADDRESS 16314

IAGLOBAL_WC_adminhost 16315

IAGLOBAL_WC_adminhost_secure. This port is used when you launch theadministration console from the TIP profile.

16316

IAGLOBAL_DCS_UNICAST_ADDRESS 16318

IAGLOBAL_ORB_LISTENER_ADDRESS 16320

IAGLOBAL_SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 16321

IAGLOBAL_CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 16322

IAGLOBAL_CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 16323

IAGLOBAL_REST_NOTIFICATION_PORT 16324

For information about viewing the assigned ports, see Viewing the applicationserver profile on page 9.

Viewing the Impact Server profileThe Impact Server profile lists the ports assigned and provides additionalinformation about the profile.

About this task

Open the Impact Server profile to review the port number assignments and otherinformation. The profile is available as a text file on the computer where it isinstalled. To view the ports assigned to Netcool/Impact:

Procedure1. Go to the tip_home_dir\profiles\ImpactProfile\logs directory.2. Open AboutThisProfile.txt in a text editor.


Example

The profile for an installation on in a Windows environment as it appears in theImpact Server profile tip_home_dir\profiles\ImpactProfile\logs\AboutThisProfile.txt:Application server environment to create: Application serverLocation: C:\Program Files\IBM\tivoli\Disk space required: 200 MBProfile name: ImpactProfileMake this profile the default: TrueNode name: ImpactNodeHost name: Enable administrative security (recommended): TrueAdministrative console port: 9085Administrative console secure port: 9086HTTP transport port: 9080HTTPS transport port: 9081Bootstrap port: 9082SOAP connector port: 9083Run application server as a service: FalseCreate a Web server definition: FalsePerformance tuning setting: Standard

What to do next

To see the complete list of defined ports on the Impact Server:1. Go to tip_home_dir\profiles\ImpactProfile\properties\portdef.props.2. Open portdef.props in a text editor:#Create the required WAS port properties for ImpactWC_defaulthost=9080WC_adminhost=9085WC_defaulthost_secure=9081WC_adminhost_secure=9086BOOTSTRAP_ADDRESS=9082SOAP_CONNECTOR_ADDRESS=9083IPC_CONNECTOR_ADDRESS=9084SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9091CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9093CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9092ORB_LISTENER_ADDRESS=9090DCS_UNICAST_ADDRESS=9088REST_NOTIFICATION_PORT=9094

Viewing the application server profileOpen the application server profile to review the port number assignments andother information.

About this task

The profile of the application server is available as a text file on the computerwhere it is installed.

Procedure1. Locate the tip_home_dir/profiles/TIPProfile/logs directory.2. Open AboutThisProfile.txt in a text editor.

Example

This is the profile for an installation on in a Windows environment as it appears intip_home_dir\profiles\TIPProfile\logs\AboutThisProfile.txt:


Application server environment to create: Application serverLocation: C:\IBM\tivoli\tipv2\profiles\TIPProfileDisk space required: 200 MBProfile name: TIPProfileMake this profile the default: TrueNode name: TIPNode Host name: tivoliadmin.usca.ibm.comEnable administrative security (recommended): TrueAdministrative consoleport: 16315Administrative console secure port: 16316HTTP transport port: 16310HTTPS transport port: 16311Bootstrap port: 16312SOAP connector port: 16313Run application server as a service: FalseCreate a Web server definition: False

What to do next

If you want to see the complete list of defined ports on the application server, youcan open tip_home_dir/properties/TIPPortDef.properties in a text editor:#Create the required WAS port properties for TIP#Mon Oct 06 09:26:30 PDT 2008CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=16323WC_adminhost=16315DCS_UNICAST_ADDRESS=16318BOOTSTRAP_ADDRESS=16312SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=16321SOAP_CONNECTOR_ADDRESS=16313ORB_LISTENER_ADDRESS=16320WC_defaulthost_secure=16311CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=16322WC_defaulthost=16310WC_adminhost_secure=16316

Installing componentsYou use the Netcool/Impact installer to install the Impact Server and the GUIServer.

The installer is a program that can be run in GUI mode, console mode, and silentmode. In GUI mode a series of windows guide you through the installationprocess. In console mode, the installer prompts you to enter the requiredinformation from the command line. If you are running the installers remotelyusing telnet or another command line application, you must run the installer inconsole mode.

Configuring componentsThe installer program sets the minimum required configuration properties duringinstallation.

You can change the configuration of a component at any time by manually editingthe properties files. Depending on the component, you might need to stop andrestart after making configuration changes.


Chapter 2. Installation and migrationThe Netcool/Impact installer is an application that copies the program files to thetarget system and sets the minimum required configuration properties.

The installer deploys the Impact Server, and the GUI Server files into theembedded version of WebSphere Application Server on the target system.

You can choose between the GUI, console, and silent mode of the installation. Ifyou are installing Netcool/Impact remotely using telnet or another command-lineapplication, you must run the installer in console mode. The silent mode, whereyou need to edit an installation properties file before the installation, isrecommended for advanced users.

Using the launchpad is a convenient way to run the Netcool/Impact installer inGUI mode, especially if you are planning the integration with Tivoli BusinessService Manager. For more information, see Running the installer in thelaunchpad on page 12

The installer will not migrate earlier versions of Netcool/Impact to version 6.1. Youuse a dedicated migration script for that. For more information, see Migrating toversion 6.1 on page 28.

Before you start the installationBefore you start the installation, make sure you meet the minimum systemrequirements, and that there is sufficient space on the temp volume.

The self extractor checks for free disk space 3 times the size of the installer on thevolume where the temp directory is located. If there is not enough free space, theinstaller prompts you for an alternative location for the extraction. The value ofthe temp directory path is resolved based on the system environment variable,IATEMPDIR on UNIX platforms and TEMP on Windows platforms. Set thisenvironment variable before running the installer to redirect the temporarydirectories of the installer to the location where there is sufficient disk space.

On UNIX systems, you can run the installer as any user that has read, write, andexecute permissions to the target directory.

Remember: Once you installed a Tivoli Integrated Portal product using a certainuser account, you must use the same user account to install, uninstall, or modifyevery subsequent Tivoli Integrated Portal product on that system.

On Windows systems the userid used for the installation must have administratorpermissions to be able to create a Windows Service entry.

Restriction: There is a known limitation on Windows, that you cannot successfullyinstall Netcool/Impact under an administrator account that has national charactersin its name. For the purpose of the installation use an administrator account with aname consisting only of ASCII characters, for example impact_administrator.

Copyright IBM Corp. 2006, 2011 11

Running the installer in the launchpadUse the launchpad to install Netcool/Impact, and other software componentsrequired for the integration with Tivoli Business Service Manager (TBSM).

Procedure1. Start the launchpad.

Use one of the following methods to start the launchpad:v UNIX systems.From the directory containing launchpad.sh, issue the command:./launchpad.sh

Important: You need the X Window System to run the launchpad on UNIXsystems.

v Windows systems.Using the Windows Explorer, navigate to the directory containing theinstallation image, and double click the launchpad.exe file.

2. Select Install IBM Tivoli Netcool/Impact 6.1 > Run the Netcool/Impact 6.1Installation Program from the launchpad navigator.This will start the installation in GUI mode. Complete the installation, using theprocedure outlined in Running the installer in GUI and console mode.

3. Optional: Install the Discovery Library support.If you are planning to integrate Netcool/Impact with TBSM, the DiscoveryLibrary support provides a means of importing resource information intoTBSM.a. Install the required database schema by clicking Install DB2 Schema > Run

the DB2 schema installation program from the launchpad navigator.Attention: In a z/Linux environment, you cannot install the DB2 schemafrom the launchpad. Instead, you must use this command from thecommand line:launchpad/zlinux/setup-dbconfig-zlinux.bin

b. Install the Discovery Library support, by selecting Install Discovery Librarysupport > Run the Discovery Library installation program from thelaunchpad navigator.

Running the installer in GUI and console modeThis procedure provides a quick overview of the installation steps in the GUI andconsole mode.

Procedure1. Start the installation.

You can start the installation from any place in the file system by providingthe full path to the installation file. For more information, see Starting theinstallation on page 14.

2. Select the language that will be used during the installation and continue withthe installation.You can only choose from those languages that the system can support, notthe full translated set.

3. Read the introduction and proceed with the installation.4. Read and accept the license agreement.


5. If a Deployment Engine (DE) is installed on the machine, and it is older thanthe one on the installation image, the installer will prompt you for a directoryto backup the old DE before upgrading it to the newer version.

6. Select the installation directory.Accept the default installation directory or type an absolute path of adirectory you want to install to. For more information, see Selecting theinstallation directory on page 14.

7. Choose the type of installation.Select the simple or advanced installation. For more information, seeSelecting the type of installation on page 15.

8. Configure the Tivoli Integrated Portal profile.For more information, see Configuring the Tivoli Integrated Portal profileon page 15.

9. (Advanced) Select the Netcool/Impact components that you want to install.For more information, see Selecting installation components on page 15.

10. (Advanced) Configure the user registry.Select the type of user registry that will be used for user management andauthentication. You can choose between a local file based, or ObjectServerbased user registry. For more information, see Configuring the user registryon page 16. You will have to go through this configuration step only if youselect the advanced installation option.

11. (Advanced) Configure the event source.Netcool/Impact will need an event source and initially it will try to connect tothe Netcool/OMNIbus ObjectServer. For more information, see Configuringthe event source on page 16.

12. (Advanced) Configure the embedded version of WebSphere Application Serverports for the TIP profile.These ports will be used by the GUI Server to communicate with TIP. Formore information, see Configuring WebSphere profile ports on page 17.

13. (Advanced) Configure embedded version of WebSphere Application Serverports for the Impact profile.The Impact profile ports will be used for communication with the ImpactServer. For more information, see Configuring Impact Server WebSphereprofile ports on page 17.

14. (Advanced) Configure the Name Server.This configuration step is only required if you chose to install the GUI Serveras one of the deployment components. For more information, seeConfiguring the Name Server on page 18.

15. (Advanced) Configure the Impact Server instance.You will need to perform this configuration step only if you are installing theImpact Server as one of the installation components. For more information,see Configuring the Impact Server instance on page 18.

16. (Advanced) Select and configure a version control system.The version control manager uses Impact Subversion (SVN) as the defaultversion control which is installed automatically with the Impact Server if youleave the default selection. For more information, see Selecting andconfiguring a version control on page 19.

17. If you are installing into an existing directory (reuse scenario), the installationprogram will prompt you for a directory to backup the existing directory into.

18. Review the pre-installation summary.

Chapter 2. Installation and migration 13

Make sure that the pre-installation summary reflect your choices and proceedwith the installation.

19. Finish the installation.Make sure the installation completed without errors. It may be a good idea toreview the installation logs.

Starting the installationYou can start the installation from any place in the file system by providing thefull path to the installation file.

Procedurev To start the installation in GUI mode: UNIX systems

Run launchpad.sh to start Launchpad, and select Install IBM TivoliNetcool/Impact 6.1. > Run the Netcool/Impact 6.1 Installation Program.

Windows systemsDouble click launchpad.exe to start Launchpad, and select Install IBM TivoliNetcool/Impact 6.1. > Run the Netcool/Impact 6.1 Installation Program.

v To start the installation in console mode: UNIX systems

Use the following command syntax to start the installation:./setup.bin -i console

or/path/setupsystem.bin -i console

path is a fully qualified path to the installation file, and system is the name ofthe operating system. An example of the command on Linux:./setuplinux.bin -i console

Windows systemsUse the following command syntax to start the installation:path\setupwin.exe -i console

For example:E:\6.1.0.0-TIV-NCI-win\Impact\setupwin.exe -i console

The installer will only ask you to provide values for some installationparameters, and it will use default values for others, like for example the JVMmemory allocated to the application server. Still, you can modify any otherdefault installation parameter even at the installation stage. To do that, use the-D attribute followed by the installation parameter and its new value on thecommand line. For example:setupwin.exe -i console -D$IAGLOBAL_EWAS_MIN_HEAP_SIZE$=512

This command will set the minimum JVM heap size for the application server to512 MB (half of the default size, 1200, for 1.2 GB). For more information aboutwhat installation parameters you can modify, see Silent installation responsefile on page 20.

Selecting the installation directoryAccept the default installation directory, C:\Program Files\IBM\tivoli onWindows systems, and /opt/IBM/tivoli on UNIX systems, or type an absolutepath of a directory you want to install to.


If you are running a new installation you cannot install into a directory that has aninstance of Netcool/Impact. On UNIX systems you can install into any directory towhich you have write privileges (+755 rights on UNIX platforms).

In case of the default location on UNIX, however, note that even if you have +755(drwxr-xr-x) permissions to /opt the installer will not create IBM/tivoli in it. To beable to use the default directory go to the /opt directory, create the IBM directoryand give it permissions of 777 (drwxrwxrwx). After that the installer will be able tocreate the /opt/IBM/tivoli directory. An alternative method, is to add the non-rootuser to run the installer to an appropriate group that allows them to create thedefault directory.

Restriction: On UNIX systems do not use special characters or spaces in the installpath name. Do not specify an installation directory path that includes parenthesis,such as c:\Program Files (x86). The install may succeed with this path, but otherutilities and components will fail when you attempt to run the application using apath with parenthesis.

Selecting the type of installationChoose between the simple or advanced type of installation.

The simple installation is not recommended for production environments. If youselect the simple installation, after the TIP Information the installer takes youdirectly to the pre-installation summary and runs the installation with a default setof values.

Important: If you select the simple installation, you will not be able to configurethe primary event source for Netcool/Impact. Still, the installation program willcreate a default ObjectServer data source file that you have to configure after theinstallation. For more information about configuring the default ObjectServer datasource, see Configuring the default ObjectServer data source on page 27.

The advanced installation is recommended for production environments. It givesyou an opportunity to choose which deployment components to install, and also tochange other default values. If you select the advanced mode, you need to beprepared to go through a series of advanced configuration steps, and to providethe installer with some answers.

Configuring the Tivoli Integrated Portal profileProvide a user id and a password for your Tivoli Integrated Portal profile.

You use these credentials to log on to Netcool/Impact in Tivoli Integrated Portal,and to manage Netcool/Impact. The default user name is tipadmin, but you canchange it.

Restriction: The installation will fail, if you use the Object Server based userregistry, with the tipadmin user already existing on the Object Server. To preventthat, you can either remove the tipadmin user from the Object Server beforerunning the installation, or you can use a different user name for your TIP profile.

Selecting installation componentsSelect the components of Netcool/Impact that you would like to install.


If you accept the default selection, both the GUI Server and the Impact Server willbe installed on the same computer. In production environments the Impact Serverand GUI Server are usually installed on separate computers. So, for example, ifyou already installed the Impact Server on another machine, you can choose toinstall the GUI Server alone.

Configuring the user registrySelect the type of user management and authentication.

During the installation, you can choose either the ObjectServer based user registry,or the file-based user registry (default).

ObjectServer

Select this option to use the Netcool/OMNIbus ObjectServer as you userregistry.

If you are familiar with the ObjectServer as a user registry, you may wantto use this option.

You can use this option with failover or single sign-on installations.

Local File BasedUseful for proof-of-concept installation. Cannot be used with failover, loadbalancing, or single sign-on installations.

Important: If you selected the ObjectServer based user registry, the installer willrun successfully even if the ObjectServer information you provided is incorrect.However, the ObjectServer users may not get created in Netcool/Impact. To fix thisrun the $TIP_HOME/bin/confvmm4ncos script after the installation, and restart theserver.

Configuring the event sourceNetcool/Impact will need an event source and initially it will try to connect to theNetcool/OMNIbus ObjectServer.

Other types of event sources require manual configuration.

Important: To use the ObjectServer as an event source for Netcool/Impact youneed to install it separately. The Netcool/Impact installer will not install it.

You can keep the default values or use a different fully qualified host name of thehost that will be used as the ObjectServer host.

You can choose not to use a password as it is valid for an ObjectServer not to havea password.

ObjectServer NameThe name of the event source server. Default is NCOMS.

ObjectServer HostBy default the installer uses the current host name as the ObjectServer hostand its default port.

ObjectServer PortThe ObjectServer port. Default is 4100.


ObjectServer UserThe user name, that Netcool/Impact uses to authenticate to theObjectServer. Default is root.

ObjectServer PasswordPassword used to authenticate. No password by default

Important: The default ObjectServer user name, and password are typical valuesthat the Netcool/OMNIbus ObjectServer is installed with. For better security,consider changing these values after the ObjectServer installation.

Configuring WebSphere profile portsConfigure the embedded version of WebSphere Application Server ports for theTivoli Integrated Portal (TIP) profile.

These ports will be used by the GUI Server to communicate with TIP.

Starting port number provided

Use the starting port number provided if you want the installer to reservea set of ports for the TIP profile automatically. After you select this optionyou can use the starting port number value, that the installer suggests, orchange it according to your preferences in the screen that follows.

Modified port value file

If you select the modified port value file, you have to have a file with yourpreferred port values located on your disk, and point the installer to thislocation in the screen that follows. Because the installer cannot verify ifthese ports are available, you need to ensure all your preferred ports areavailable.

Attention: Your configuration is saved in the /tipv2/profiles/TIPProfile/properties/portdef.props file.

Configuring Impact Server WebSphere profile portsConfigure the embedded version of WebSphere Application Server (eWAS) portsfor the Impact profile.

The Impact profile ports are used for communication with the Impact Server. Bydefault, eWAS uses port 9080 for the HTTP port (GUI Server) and 9085 for theadministrator port (administration console). If these ports are available the installerreserves them. If not it reserves the next vacant port.

Restriction: On AIX system, wsmserver uses port 9090. You can check that byrunning the command nestat -na | grep wsmserver. In this situation, the installercannot reserve the default set of ports starting from 9080 so a next available portwill be used as the starting port. If this is the case, use the next available port,9110, for your Name Server HTTP port.

Starting port number provided

Use the starting port number provided if you want the installer to reservea set of ports for the Impact profile automatically. After you select thisoption you can use the starting port number value, that the installersuggests, or change it according to your preferences in the screen thatfollows.

Modified port value file


If you select the modified port value file, you need a file with yourpreferred port values located on your disk, and point the installer to thislocation in the screen that follows. Because the installer cannot verify ifthese ports are available, you need to ensure all your preferred ports areavailable.

Remember: Your configuration is saved in the $TIP_HOME/profiles/ImpactProfile/properties/portdef.props file.

Configuring the Name ServerConfigure the Name Server to provide registration functionality for thedeployment components.

You can define multiple Name Server-port pairs and then associate your currentinstallation to multiple Name Servers. Each Name Server port that you providewill be tested to check if it is active. If the port is active you will proceed to thenext step of the installation. If the port is not active you will see a messageindicating that the port is not active but you will still be able to continue with theinstallation. For the installation to be successful, however, make sure that theserver-port pair as you have defined is available.

Important: If you are defining an Impact Server, the current host name and portnumber must be in the list. You will get an error if it is not in the list.

The Name Server is also used to store information used for server clustering. In aclustered configuration all cluster members should be added to the list, the firstserver in the list acting as the primary. For each member that you are installing thelist must be exactly the same.

If you have a file that contains a list of your defined Name Servers, you canimport that list. The file must be well-formed, so the best option is to use thenameserver.props file that is created in the $IMPACT_HOME/etc directory during thefirst installation.

Attention: Do not rename the nameserver.props file. Provide a fully qualifiedpath to the file.

You can update the Name Server list after the installation by runningnci_configuration_utility. For more information, see Post installation utility onpage 28.

Configuring the Impact Server instanceConfigure the instance of Impact Server that you are installing.

You will need to perform this configuration step only if you are installing theImpact Server as one of the installation components.

You may need to modify the default instance name, and cluster group if you areinstalling a member of a cluster. If you are installing a stand-alone Impact Serveryou can go with the default values.

Instance Name

The name of the Impact Server instance. You can use any uniqueidentifying string.


Cluster Group

If you are installing a member of a cluster provide the name of theinstance and the cluster group to which you want it to belong.

Command Line Port

The command-line manager service tool allows you to access the ImpactServer from the command-line interface to start and stop services as wellas configure their parameters. The default value of the command-lineservice port is 2000.

DB Port

The DB port is the port that you can use to access the Netcool/Impactdatabase and by default it is 5435.

Selecting and configuring a version controlThe version control manager uses Impact Subversion (SVN) as the default versioncontrol which is installed automatically with the Impact Server if you leave thedefault selection.

No additional configuration steps will be required if you decide to go with thedefault setting and immediately after the installation you will be able to savepolicies, data sources, data types, and configuration properties as revisions in asource control archive.

Choose another option if you want to use a different version control system. Beprepared to provide additional configuration information in the steps to follow:

Version Control Path

Provide the path to your version control. You have to provide thisinformation if the Impact Server or both the Impact Server and the GUIServer are selected together from the components to be installed andSubversion, or CVS, or RCS or ClearCase is selected in the version ChooseVersion Control System step.

Version Control Repository

Set the repository for your version control. You have to provide thisinformation if the Impact Server or both the Impact Server and the GUIServer are selected together from the components to be installed andSubversion or CVS is selected in the Version Control System step.

Silent modeYou use the silent installation mode in an environment where neither the GUImode, or console mode is available.

Before running the installer in silent mode you need to edit the installationproperties file. A template of the properties file, installSilent_response.txt, isprovided with the installation file and you can edit it with your favorite text editor.The following rules apply to the response file:v The path to the installer properties file can be either absolute, or relative to thedirectory in which the installer resides.

v Use the response file, installSilent_response.txt, shipped with the installer.You can change the name of the file.


v If an installer properties file is specified but does not exist, the default propertiesfile, if present, is used. Otherwise, any supplied command-line options are used,or if no additional options are specified, the installer is run using the defaultsettings.

Running the installer in silent modeUse this procedure to install Netcool/Impact in silent mode.

Procedure1. Copy the installation properties file to a directory on your file system alongside

the installation files.2. The command you use to start the installation in silent mode has the following

syntax:v UNIX systems:./setup.bin -i silent -f or

//setup.bin -i silent -f

where path is a fully qualified path to the installer properties file, and systemis the name of the operating system. An example of the command on Linux:./setuplinux.bin -i silent -f installer.properties

v Windows systems: setupwin.exe -i silent -f /

For example:setupwin.exe -i silent -f E:\6.1.0.0-TIV-NCI-win\Impact\installer.properties

3. (Optional) Follow the installation progress by viewing the installation logs.The installation log files, IMPACT6.1_install-xx.log (where xx can be 00 or 01or 02) are created in your home directory. The installation program also createsa lock file, IMPACT6.1_install-xx.log.lck, that is removed when theinstallation is complete.

Silent installation response fileYou can use the silent installation response file template,installSilent_response.txt that is shipped with the installation image, to createyour silent installation response file.

The following table explains the silent installation response file parameters:

Table 3. Silent installation parametersParameter Description

LICENSE_ACCEPTED Uncomment this parameter and change its valueto true to accept the license agreement.

IAGLOBAL_EWAS_MIN_HEAP_SIZE

IAGLOBAL_EWAS_MAX_HEAP_SIZE

The minimum and maximum JVM heap sizevalue for the Impact Server. The default value is256 and 1200 (1.2GB), respectively. To change thedefaults uncomment the parameter and provideyour values.

IAGLOBAL_TIP_EWAS_MIN_HEAP_SIZE

IAGLOBAL_TIP_EWAS_MAX_HEAP_SIZE

The minimum and maximum JVM heap sizevalue for the GUI Server (TIP server). Thedefault value is 256 and 512, respectively. Tochange the defaults uncomment the parameterand provide your values.

NO_BACKUP Set this parameter to false to backup yourexisting installation.


Table 3. Silent installation parameters (continued)Parameter Description

BACKUP_DIR A directory on the system to backup the existingapplication to. Used with NO_BACKUP=false. Thedirectory must already exist.

USER_INSTALL_DIR The installation directory. Default is/opt/IBM/tivoli on UNIX systems andC:\Program Files\IBM\tivoli on Windowssystems.

IAGLOBAL_INSTALL_LOCATION_SELECTION Set this parameter to reuse if you are reusing anexisting TIP installation. In this case you mustalso set USER_INSTALL_DIR to the location wherethe TIP instance is installed.

IAGLOBAL_WASUserID The user id for accessing Netcool/Impact in TIP.The default user name is tipadmin.Restriction: The installation will fail, if you usethe Object Server based user registry, with thetipadmin user already existing on the ObjectServer. To prevent that, you can either removethe tipadmin user from the Object Serverbefore running the installation, or you can use adifferent user name for your TIP profile.

IALOCAL_WASPassword The password to use with IAGLOBAL_WASUserID.

CHOSEN_INSTALL_SET_S To change the default values of the installationset this parameter to advanced, to use thedefault values set it to default.

IAGLOBAL_GUI_SERVER_RESULT Set to 1 to install the GUI Server.

IAGLOBAL_IMPACT_SERVER_RESULT Set to 1 to install the Impact Server.

IAGLOBAL_WC_defaulthost ...

IAGLOBAL_REST_NOTIFICATION_PORT

A set of ports that are used by the GUI Server.Used with IAGLOBAL_GUI_SERVER_RESULT=1.

IAGLOBAL_IMPORT_NAMESERVER_FILE Set this parameter to true to import a list ofNameservers from an external file. Set to false tomanually provide a list of Nameservers. Usedwith IAGLOBAL_IMPACT_SERVER_RESULT=1.

IAGLOBAL_NAMESERVER_PROPS_FILE Provide a qualified path to a file that contains alist of your Nameservers. The file must be valid,so the best option is to use the nameserver.propsfile that is created in the $IMPACT_HOME/etcdirectory during the first installation. Used withIAGLOBAL_IMPORT_NAMESERVER_FILE=true andIAGLOBAL_IMPACT_SERVER_RESULT=1.

IAGLOBAL_NAMESERVER_HP Provide a list of your Nameservers host name(or IP address), port number pairs. A host name(or IP address) must be separated from a portwith a colon. A Nameserver host name (or IPaddress), and port entry, must be separated fromanother entry with a comma. Used withIAGLOBAL_IMPORT_NAMESERVER_FILE=false, andIAGLOBAL_IMPACT_SERVER_RESULT=1.


Table 3. Silent installation parameters (continued)Parameter Description

IAGLOBAL_USER_REGISTRY_FILE_SELECTED Set the value to 1 for the file based user registry,and 0 for the ObjectServer based user registry.Important: If you selected the ObjectServerbased user registry, the installer will runsuccessfully even if the ObjectServer informationyou provided is incorrect. However, theObjectServer users may not get created inNetcool/Impact. To fix this run the$TIP_HOME/bin/confvmm4ncos script after theinstallation, and restart the server.

IAGLOBAL_OBJSERV_NAME The name of the ObjectServer that is used asyour event source. By default, it is theNetcool/OMNIbus server, NCOMS.

IAGLOBAL_OBJSERV_HOST_NAME A fully qualified host name (or IP address) ofyour ObjectServer. This parameter has no defaultvalue, so you have to provide some value.

IAGLOBAL_OBJSERV_PORT The ObjectServer port. The default is 4100.

IAGLOBAL_OBJSERV_USER The user account used to connect as to theObjectServer. The default is root.

IAGLOBAL_OBJSERV_PASSWORD_S The password used with IAGLOBAL_OBJSERV_USER.

IAGLOBAL_EWAS_HTTP_PORT ...

IAGLOBAL_EWAS_REST_NOTIFICATION_PORT

A set of ports that are used by the Impact Server.Used with IAGLOBAL_IMPACT_SERVER_RESULT=1.

IAGLOBAL_NCI_INSTANCE_NAME The name of the Impact Server being installed.The default is NCI. Used withIAGLOBAL_IMPACT_SERVER_RESULT=1.

IAGLOBAL_NCI_CLUSTER_GROUP The name of the cluster that the Impact Server isto join. The default is NCICLUSTER. Used withIAGLOBAL_IMPACT_SERVER_RESULT=1.

IAGLOBAL_NCI_CMD_LINE_PORT The port used by the command line service forthe new instance. The default is 2000. Used withIAGLOBAL_IMPACT_SERVER_RESULT=1.

IAGLOBAL_NCI_DB_PORT The port used by the database server. Thedefault is 5435. Used withIAGLOBAL_IMPACT_SERVER_RESULT=1.

IAGLOBAL_VERSION_CONTROL_TYPE Specify which version control system you wantto use. The default value is Impact Subversion,NCI_VCS_IMPACTSVN. This is installedautomatically with the product.

VERCTLPATH The version control path. You must provide afully qualified path, because there is no defaultvalue. Required ifIAGLOBAL_VERSION_CONTROL_TYPE is not of theIMPACT_SVN value.

VERCTL_REPOSITORY The version control repository. You must providesome value, because there is no default value.Required if IAGLOBAL_VERSION_CONTROL_TYPE isnot of the IMPACT_SVN value.


Installing in a shared environmentIf you have an installed product, for example TBSM, that uses Tivoli IntegratedPortal (TIP), you can install Netcool/Impact 6.1 into the existing TIP.

Netcool/Impact requires TIP version 2.2 or better. If your existing TIP environmentis using TIP 2.1, you must install the TIP Feature Pack 2.2.0.1, before you caninstall Netcool/Impact.

Netcool/Impact 6.1.0.1 requires TIP version 2.2.0.7 or better.

See the Tivoli Netcool/Impact wiki for information about obtaining the TIP featurepacks.

Typical scenarios where an existing TIP installation is reused are the following:v Installing the Impact Server on a dedicated machine, and the GUI Server on themachine, where TIP is already installed. This scenario is recommended for mostproduction environments.

v Installing both Netcool/Impact components on the machine, where TIP isalready installed.

Important: If you are installing on a Windows system, where the TivoliMonitoring Agent is installed, you must stop the agent before starting theinstallation.

Installing the GUI Server into an existing TIP installationUse this procedure to install the Impact Server on a dedicated machine, and theGUI Server onto a machine where TIP is already installed.

Before you begin

It is recommended to back up any components that are already installed on TIP. Toback up the Tivoli Business Service Manager component, follow the guidelines inthe Performing advanced installations, and Restoring system from a backup sections, oftheTivoli Business Service Manager 6.1 Installation Guide.

Restriction: If you are installing the GUI Server into a Tivoli Integrated Portalserver with WebGUI, the Impact Server does not function until the wimconfig.xmlfile is updated after the installation. For information about updating thewimconfig.xml file see Updating the wimconfig.xml file on page 25.

Procedure1. Install the Impact Server on a dedicated machine.

Use the procedure Running the installer in GUI and console mode on page12.a. Select the advanced type of installation.b. Install the Impact Server component only.

2. Install the GUI Server on the machine where TIP is installed.Use the procedure Running the installer in GUI and console mode on page12.a. The installer will detect an existing TIP installation. Choose to reuse an

existing installation directory, and point the installer to the directory whereTIP is installed.


b. Select the advanced type of installation.c. Choose to install the GUI Server component only.

Restriction: If TBSM is already installed on TIP, you will not be able toinstall the GUI Server because it is installed as part of the TBSM dashboard.

Remember: The TIP user name and password used must match the TIPuser name and password of the existing TIP installation for reuse.

d. When asked about the Name Server point to the machine where the ImpactServer is installed.

Note: If you provide incorrect Name Server information, you canreconfigure it after the installation, using the nci_configuration_utilitytool. For more information, see Post installation utility on page 28.

3. After the installation is finished, restart the TIP server to pick up the newinstalled component.

What to do next

If you installed Netcool/Impact to be a part of a TBSM solution, they need to beconfigured to share their nameservers. Both the TBSM data server and the ImpactServer are running nameservers independently but they can be configured togetheras a cluster, with the TIP server a member of the cluster. To do that, you must runthe nci_configuration_utility tool on all the servers. For more information, seeSharing nameservers with TBSM on page 62.

Installing both components into an existing TIP installationUse this procedure to install the Impact Server, and the GUI Server onto a machinewhere TIP is already installed.

Before you begin

It is recommended to back up any components that are already installed on TIP. Toback up the Tivoli Business Service Manager component, follow the guidelines inthe Performing advanced installations, and Restoring system from a backup sections, oftheTivoli Business Service Manager 6.1 Installation Guide.

Restriction: If you are installing the GUI Server into a Tivoli Integrated Portalserver with WebGUI, the Impact Server does not function until the wimconfig.xmlfile is updated after the installation. For information about updating thewimconfig.xml file see Updating the wimconfig.xml file on page 25.

Procedure1. Run the Netcool/Impact installer on the machine where TIP is installed.

Use the procedure Running the installer in GUI and console mode on page12.a. The installer will detect an existing TIP installation. Choose to reuse an

existing installation directory, and point the installer to the directory whereTIP is installed.

b. Select the advanced type of installation.c. Choose to install the Impact Server, and the GUI Server component.


Restriction: If T

Administration Guide - Impact

Documents

Transcript of Administration Guide - Impact