IBM Tivoli Enterprise Console: Installation Guide - Support

IBM Tivoli Enterprise Console

Installation GuideVersion 3.9

SC32-1233-00

��


Installation GuideVersion 3.9

SC32-1233-00

��

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

First Edition (August 2003)

This edition applies to version 3, release 9 of IBM Tivoli Enterprise Console (product number 5698-TEC) and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2003. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this guide . . . . . . . . . . . vWho should read this guide . . . . . . . . . vPublications . . . . . . . . . . . . . . v

IBM Tivoli Enterprise Console library . . . . . vRelated publications . . . . . . . . . . viAccessing publications online . . . . . . . viOrdering publications . . . . . . . . . . vi

Contacting software support . . . . . . . . viiParticipating in newsgroups. . . . . . . . . viiConventions used in this guide . . . . . . . viii

Typeface conventions . . . . . . . . . . viiiOperating system-dependent variables andpaths . . . . . . . . . . . . . . . viii

IBM Tivoli Enterprise Console icons . . . . . . ix

Chapter 1. Planning for installation . . . 1Understanding IBM Tivoli Enterprise Consolecomponents. . . . . . . . . . . . . . . 1Planning for deployment . . . . . . . . . . 2

Event server and database server on the samemanaged node. . . . . . . . . . . . . 3Event server on a managed node, database serveron a non-Tivoli computer . . . . . . . . . 3Event server and database server on a Tivoliserver. . . . . . . . . . . . . . . . 4Event server on a Tivoli server, database server ona non-Tivoli computer . . . . . . . . . . 5Event server on a managed node, Web console ona non-Tivoli computer . . . . . . . . . . 5Event server and NetView server on differentmanaged nodes . . . . . . . . . . . . 6Event server on a managed node, NetView serveron a Tivoli server, database server on a non-Tivolicomputer . . . . . . . . . . . . . . 6Event server and database server on a Tivoliserver, NetView server on a non-Tivoli computer . 7Event server on a Tivoli server, NetView serverand database server on different non-Tivolicomputers . . . . . . . . . . . . . . 8Tivoli Enterprise Console components in differentTivoli regions . . . . . . . . . . . . . 8

Understanding product requirements . . . . . . 10Hardware requirements . . . . . . . . . 10Software requirements . . . . . . . . . . 14

Tivoli Enterprise Console product images . . . . 16

Chapter 2. Preparing for installation . . 17Performing preinstallation tasks . . . . . . . 17

Installing the Tivoli Management Framework . . 17Installing and configuring the RDBMS . . . . 17

Preparing to install components . . . . . . . 21Tivoli Enterprise Console components . . . . 22Tivoli NetView components . . . . . . . . 28

Preparing to install language packs . . . . . . 31Tivoli Enterprise Console language packs . . . 32

Tivoli NetView language packs . . . . . . . 32Preparing to upgrade from Version 3.6.2 . . . . . 33

Upgrade 3.6.2 components . . . . . . . . 33Install new components . . . . . . . . . 34

Preparing to install components in interconnectedTivoli regions . . . . . . . . . . . . . . 35Preparing to install components in Tivoli regionoperating with non-default port settings . . . . . 35

Chapter 3. Installing, upgrading, anduninstalling using the installationwizard . . . . . . . . . . . . . . . 37Using the installation wizard . . . . . . . . 37Configuring the event database. . . . . . . . 38Installing, upgrading, and uninstalling componentsin a Tivoli environment . . . . . . . . . . 39Installing and upgrading components in anon-Tivoli environment . . . . . . . . . . 40

Installing the event console . . . . . . . . 40Installing the NetView server . . . . . . . 40Installing the NetView Web console . . . . . 41

Installing and uninstalling the Web console. . . . 41Installing the Web console . . . . . . . . 41Uninstalling the Web console . . . . . . . 42

Locating the license files . . . . . . . . . . 43

Chapter 4. Configuring the eventdatabase . . . . . . . . . . . . . . 45Planning for configuration . . . . . . . . . 46

General prerequisites . . . . . . . . . . 46Oracle prerequisites . . . . . . . . . . 47

General event database considerations . . . . . 47DB2 considerations . . . . . . . . . . . 47Informix considerations . . . . . . . . . 48Microsoft SQL Server considerations . . . . . 49Oracle considerations . . . . . . . . . . 49Sybase and Microsoft SQL Server considerations 50Sybase considerations . . . . . . . . . . 50

Sample worksheets for event database installation 50Configuring with the installation wizard . . . . 52

Sourcing the database environment for theinstallation wizard . . . . . . . . . . . 54Examining error logs . . . . . . . . . . 54Tuning the event database . . . . . . . . 55

Understanding RIM object creation . . . . . . 55DB2 . . . . . . . . . . . . . . . . 55Informix . . . . . . . . . . . . . . 56Microsoft SQL Server . . . . . . . . . . 56Oracle . . . . . . . . . . . . . . . 57Sybase . . . . . . . . . . . . . . . 57Ensuring that RIM can connect to the Informixserver event database . . . . . . . . . . 57

Installing the event database using the custommethod . . . . . . . . . . . . . . . . 58

Installing the event database. . . . . . . . 58

© Copyright IBM Corp. 2003 iii

Upgrading the event database . . . . . . . 59Uninstalling the event database. . . . . . . 60

Generating and executing scripts . . . . . . . 61Generate scripts only . . . . . . . . . . 62Generate and execute scripts . . . . . . . 62Execute scripts only . . . . . . . . . . 62

Using the No Change option when generatingscripts . . . . . . . . . . . . . . . . 62Configuration options for improving performance 63

DB2 configuration options . . . . . . . . 63Informix configuration options . . . . . . . 63Microsoft SQL Server configuration options . . 68Oracle configuration options. . . . . . . . 69Sybase configuration options . . . . . . . 73

Enabling language support . . . . . . . . . 75Enabling language support for DB2 . . . . . 75Enabling support for GB18030 character set. . . 75Enabling language support for Microsoft SQLServer, Sybase, and Informix. . . . . . . . 76Enabling language support for Oracle . . . . 76

Chapter 5. Installing, upgrading, anduninstalling using the TivoliManagement Framework tools . . . . 79Before you begin . . . . . . . . . . . . 79

Backing up object databases . . . . . . . . 79Stopping the event server. . . . . . . . . 79

Installing the Tivoli Enterprise Console components 80Selecting an installation method . . . . . . 80Installing components . . . . . . . . . . 80Installing components using the Tivoli desktop 81Installing components using the command line 82Installing components using the Tivoli SoftwareInstallation Service . . . . . . . . . . . 82

Upgrading the Tivoli Enterprise Consolecomponents . . . . . . . . . . . . . . 84

Before you begin upgrading components . . . 84Upgrading from the Tivoli desktop . . . . . 84Upgrading from the command line . . . . . 84Upgrading using the Software Installation Service 85

Uninstalling the Tivoli Enterprise Consolecomponents from the command line . . . . . . 85

Procedure . . . . . . . . . . . . . . 86Example . . . . . . . . . . . . . . 86

Postinstallation tasks . . . . . . . . . . . 87Setting up Tivoli roles and resources in the Tivolidesktop. . . . . . . . . . . . . . . 87Starting the event server . . . . . . . . . 87

Updating the object database . . . . . . . 87Configuring default event groups and consoles 87Deactivating default rule sets . . . . . . . 88

Chapter 6. Troubleshooting commoninstallation problems . . . . . . . . 89Avoiding common problems. . . . . . . . . 89Working with the RIM object . . . . . . . . 89

Obtaining information about RIM objects . . . 89Modifying RIM objects . . . . . . . . . 90Deleting a RIM object . . . . . . . . . . 90Creating a RIM object . . . . . . . . . . 90Testing RIM connectivity . . . . . . . . . 90

Starting the event console as a background process 91Error messages . . . . . . . . . . . . . 91

stty:tcgetattr: a specified file does not supportiotcl system call . . . . . . . . . . . . 91FRWTT0003E An instance named ″TEC39_JRE″ ofresource ″Uninstall″ was not found. . . . . . 91

Restoring a database with a functional objectdispatcher . . . . . . . . . . . . . . . 92Using uninstall scripts . . . . . . . . . . . 92Installing from a remote file system in Windows . . 92Configuring a database to export NetView serverdata to IBM Tivoli Enterprise Data Warehouse. . . 92Upgrading Tivoli Enterprise Console database forSybase and Informix . . . . . . . . . . . 93Using the installation wizard on the HP-UXoperating system . . . . . . . . . . . . 93Removing the event console when migrating fromVersion 3.6. . . . . . . . . . . . . . . 93

Appendix. A sample, step-by-stepinstallation . . . . . . . . . . . . . 95Installing the Tivoli Management Framework . . . 96Configuring the event database. . . . . . . . 97Installing components in a Tivoli environment. . . 98Installing the Web console component . . . . . 99Installing the NetView component . . . . . . 100

On the UNIX operating system . . . . . . 100On the Windows operating system . . . . . 100

Starting the Web console . . . . . . . . . 100

Notices . . . . . . . . . . . . . . 103Trademarks . . . . . . . . . . . . . . 105

Index . . . . . . . . . . . . . . . 107

iv IBM Tivoli Enterprise Console: Installation Guide

About this guide

The IBM® Tivoli Enterprise Console® product is a rule-based, event managementapplication that integrates system, network, database, and application managementto help ensure the optimal availability of an organization’s IT services. The IBMTivoli Enterprise Console Installation Guide describes how to install, upgrade, anduninstall the IBM Tivoli Enterprise Console product.

Who should read this guideThis guide is for administrators who are responsible for installing Tivoli® products.

Readers should be familiar with the following software:v The operating systems that your enterprise usesv The Tivoli Management Framework

PublicationsThis section lists publications in the IBM Tivoli Enterprise Console library andrelated documents. It also describes how to access Tivoli publications online andhow to order Tivoli publications.

IBM Tivoli Enterprise Console libraryThe following documents are available in the IBM Tivoli Enterprise Consolelibrary:v IBM Tivoli Enterprise Console Adapters Guide, SC32-1242

Provides information about supported adapters, including how to install andconfigure these adapters.

v IBM Tivoli Enterprise Console Command and Task Reference, SC32-1232Provides details about IBM Tivoli Enterprise Console commands, predefinedtasks that are shipped in the task library, and the environment variables that areavailable to tasks that run against an event.

v IBM Tivoli Enterprise Console Installation Guide, SC32-1233Describes how to install, upgrade, and uninstall the IBM Tivoli EnterpriseConsole product.

v IBM Tivoli Enterprise Console Release Notes, SC32-1238Provides release-specific information that is not available until just before theproduct is sent to market.

v IBM Tivoli Enterprise Console Rule Developer’s Guide, SC32-1234Describes how to develop rules and integrate them for event correlation andautomated event management.

v IBM Tivoli Enterprise Console Rule Set Reference, SC32-1282Provides reference information about the IBM Tivoli Enterprise Console rule sets.

v IBM Tivoli Enterprise Console User’s Guide, SC32-1235Provides an overview of the IBM Tivoli Enterprise Console product anddescribes how to configure and use the IBM Tivoli Enterprise Console product tomanage events.

© Copyright IBM Corp. 2003 v

v IBM Tivoli Enterprise Console Warehouse Enablement Pack: Implementation Guide,SC32-1236Describes how to install and configure the warehouse enablement pack for theIBM Tivoli Enterprise Console product and describes the data flow andstructures that are used by the warehouse pack.

v Tivoli Event Integration Facility Reference, SC32-1241Describes how to develop your own event adapters that are tailored to yournetwork environment and the specific needs of your enterprise. This referencealso describes how to filter events at the source.

Related publicationsThe Tivoli Software Glossary includes definitions for many of the technical termsrelated to Tivoli software. TheTivoli Software Glossary is available, in English only, atthe following Tivoli software library Web site:

http://www.ibm.com/software/tivoli/library/

Access the glossary by clicking the Glossary link on the left pane of the Tivolisoftware library window.

Accessing publications onlineThe documentation CD contains the publications that are in the product library.The format of the publications is PDF, HTML, or both. Refer to the readme file onthe CD for instructions on how to access the documentation.

IBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Software InformationCenter Web site. Access the Tivoli Software Information Center by first going to theTivoli software library at the following Web address:


Scroll down and click the Product manuals link. In the Tivoli Technical ProductDocuments Alphabetical Listing window, click the IBM Tivoli Enterprise Consolelink to access the product library at the Tivoli Information Center.

Note: If you print PDF documents on other than letter-sized paper, select the Fit topage check box in the Adobe Acrobat Print window. This option is availablewhen you click File → Print. Fit to page ensures that the full dimensions of aletter-sized page print on the paper that you are using.

Ordering publicationsYou can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

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, see the following Web site for a list of telephone numbers:

vi IBM Tivoli Enterprise Console: Installation Guide

http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm




http://www.ibm.com/software/tivoli/order-lit/

Contacting software supportIf you have a problem with any Tivoli product, refer to the following IBM SoftwareSupport Web site:

http://www.ibm.com/software/sysmgmt/products/support/

If you want to contact software support, see the IBM Software Support Guide at thefollowing Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv Information you must have before contacting IBM Software Support

Participating in newsgroupsUser groups provide software professionals with a forum for communicating ideas,technical expertise, and experiences related to the product. They are located on theInternet and are available using standard news reader programs. These groups areprimarily intended for user-to-user communication and are not a replacement forformal support.

To access a newsgroup, use the following instructions.

Use these instructions for a Microsoft Internet Explorer browser.1. Open an Internet Explorer browser.2. From the Tools menu, click Internet Options.3. On the Internet Options window, click the Programs tab.4. In the Newsgroups list, click the Down Arrow and then click Outlook Express.5. Click OK.6. Close your Internet Explorer browser and then open it again.7. Cut and paste the newsgroup address of a product into the browser Address

field, and press Enter to open the newsgroup.

Use these instructions for a Netscape Navigator browser.1. Open a Netscape Navigator browser.2. From the Edit menu, click Preferences. The Preferences window is displayed.3. In the Category view, click Mail & Newsgroups to display the Mail &

Newsgroups settings.4. Select the Use Netscape mail as the default mail application check box.5. Click OK.6. Close your Netscape Navigator browser and then open it again.7. Cut and paste the newsgroup address of a product into the browser Address

field, and press Enter to open the newsgroup.

About this guide vii

http://www.ibm.com/software/tivoli/order-lit/

http://www.ibm.com/software/sysmgmt/products/support/

http://techsupport.services.ibm.com/guides/handbook.html


news://news.software.ibm.com/ibm.software.tivoli.enterprise-console

IBM Tivoli NetView® for UNIX® and IBM Tivoli NetView for Windows®

news://news.software.ibm.com/ibm.software.tivoli.netview-unix-windows

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

Typeface conventionsThis guide uses the following typeface conventions:

Bold

v 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 Column headings in a tablev Keywords and parameters in text

Italic

v Citations (titles of books, diskettes, and CDs)v Words defined in textv Emphasis of words (words as words)v Letters as lettersv New terms in text (except in a definition list)v Variables and values you must provide

Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv 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 guide uses the UNIX convention for specifying environment variables and fordirectory notation.

When using the Windows command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with a backslash ( \) indirectory paths.

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

viii IBM Tivoli Enterprise Console: Installation Guide

news://news.software.ibm.com/ibm.software.tivoli.enterprise-console

news://news.software.ibm.com/ibm.software.tivoli.netview-unix-windows

IBM Tivoli Enterprise Console iconsThe following icons are used in the IBM Tivoli Enterprise Console product.

Icon Represents

Event Server

The red arrow indicates the event serveris running.

A hollow arrow indicates the eventserver is initializing.

Rule Base

The red arrow indicates the rule base isactive.

Profile

A profile is a collection ofapplication-specific data.

About this guide ix

x IBM Tivoli Enterprise Console: Installation Guide

Chapter 1. Planning for installation

Installing the Tivoli Enterprise Console product includes completing severalplanning and preinstallation tasks. Be sure that you have completed these tasksbefore proceeding to the installation.

To prepare for installation properly, you must perform the following planningtasks:v “Planning for deployment” on page 2v “Understanding product requirements” on page 10v “Preparing to install components” on page 21

Before you can begin to install the Tivoli Enterprise Console product, you mustcomplete the following in this order:1. “Installing the Tivoli Management Framework” on page 172. “Installing and configuring the RDBMS” on page 17

Use the Tivoli Enterprise Console installation wizard to install the Tivoli EnterpriseConsole product. The installation wizard helps you do the following tasks:1. Configure an event database2. Install the components3. Uninstall and upgrade components as appropriate

You can also install some components manually using the Tivoli ManagementFramework tools.

Understanding IBM Tivoli Enterprise Console componentsThe IBM Tivoli Enterprise Console product is a rule-based event managementapplication that integrates system, network, database, and application managementto help ensure the optimal availability of an organization’s IT services. It consistsof the following components:

Event serverThe event server is a central server that handles all events in thedistributed system.

User interface (UI) serverThe user interface (UI) server provides conflict management for eventconsole updates.

Event consoleThe Tivoli Enterprise Console product provides two versions of the eventconsole, a Java™ version and a Web version. Both provide a graphical userinterface (GUI) that allows the IT staff to view and respond to dispatchedevents.

Adapter Configuration FacilityThe Adapter Configuration Facility is a profile-based application used toconfigure and distribute TME adapters using a graphical user interface(GUI).

© Copyright IBM Corp. 2003 1

Event adaptersAn event adapter monitors events on a managed source such as adatabase, formats the information, and forwards it to the event server.

Sample event informationSample event information is provided as an example to handle requests foradditional event information that an operator may need.

NetView serverThe Tivoli NetView server is a network management program that usesSNMP to discover, monitor, and configure TCP/IP networks.

NetView Web consoleThe Tivoli NetView Web console is a Java-based graphical user interface(GUI) that allows operators to view the network topology and providesdiagnostic and informational tools to aid in troubleshooting networkproblems.

NetView native consoleThe Tivoli NetView native console is an X/Motif-based (UNIX) orMFC-based (Windows) graphical user interface (GUI) that allowsadministrators to configure the NetView server. It also provides the sameoperator functionality as the Tivoli NetView Web console. This componentis installed automatically when the Tivoli NetView server is installed.

For installation details for these components, see “Preparing to install components”on page 21.

Planning for deploymentA Tivoli environment consists of one or more Tivoli regions. Each Tivoli regionconsists of a Tivoli server, one ofdr more managed nodes, and one ormoreendpoints. The Tivoli regions can be interconnected. Tivoli Enterprise Consolecomponents run in a Tivoli environment. The Tivoli NetView server runs in aTivoli environment on some operating systems. It runs in a non-Tivoli environmenton all supported operating systems.

Tivoli Enterprise Console components require an RDBMS system for theiroperation. The RIM host is a Tivoli component that is available in all managednodes. It provides a common interface for RDBMS servers from multiple vendors.Tivoli Enterprise Console components communicate with supported RDBMSsystems through a RIM host. You can chose any managed node to serve as a RIMhost. However, a RIM host must have connectivity to the RDBMS server. The RIMhost must reside on a computer that has either an RDBMS server or clientinstalled.

A Tivoli environment can be a distributed environment. There are multiple ways ofplacing various components and the RIM host. The following sections provideinformation about possible deployments for the event server and the TivoliNetView server. You can also deploy other components in a distributed manner.Your deployment depends on your business needs and your RDBMS.

Although the sample deployments in the following sections always have the eventserver and RIM host in the same managed node, they can also be placed indifferent managed nodes.

2 IBM Tivoli Enterprise Console: Installation Guide

Event server and database server on the same managed nodeIn this deployment, the Tivoli server is on one managed node and the event server,RIM host, and RDBMS server are on another managed node. The followinggraphic illustrates this deployment:

The advantages of this deployment are as follows:v The Tivoli server computer and the event server computer have more processing

power and separate memory.v This deployment minimizes network congestion because the RDBMS is local to

the event server, and the RIM host and event server are local to the same Tivoliregion.

The disadvantages of this deployment are that it requires two computers, andsome debugging scenarios require comparing two separate Tivoli ManagementFramework logs.

Event server on a managed node, database server on anon-Tivoli computer

In this deployment, the event server, the RIM host, and the RDBMS client are on amanaged node, and the RDBMS server is on a computer not managed by TivoliManagement Framework software. The following graphic illustrates thisdeployment:

Tivoliserver

Managed node

Event server

RIM host

RDBMS server

Figure 1. Event server and database server on the same managed node

Chapter 1. Planning for installation 3

The advantage of this deployment is that it distributes the processing load of theTivoli server, event server, and RDBMS across three computers.

The disadvantages of this deployment are that there are network constraints, threecomputers are required, and some debugging scenarios require comparing twoseparate Tivoli Management Framework logs.

Event server and database server on a Tivoli serverIn this deployment, the event server, the RIM host, and the RDBMS server are onthe Tivoli server. The following graphic illustrates this deployment:

The advantages of this deployment are as follows:v It reduces network congestion and communication delays between the processesv It is less expensive because everything is on one computerv It is easier to debug Tivoli Management Framework-related issues because all

information is in one Tivoli Management Framework log

The disadvantage of this deployment is that it requires significantly more memoryand processor speed for all three servers to reside on one processor. Therefore, itshould not be used for systems that require high-event throughput.

Tivoliserver

Managed node

Event server

RIM host

RDBMS client RDBMS server

Non-Tivolicomputer

Figure 2. Event server on a managed node, database server on a non-Tivoli computer

Tivoliserver

Event server

RIM host

RDBMS server

Figure 3. Event server and database server on a Tivoli server


Event server on a Tivoli server, database server on anon-Tivoli computer

In this deployment, the event server, the RIM host, and the RDBMS client are onthe Tivoli server and the RDBMS server is on a computer not managed by TivoliManagement Framework software. The following graphic illustrates thisdeployment:

The advantage of this deployment is that it off-loads the RDBMS processor load toanother computer.

The disadvantages of this deployment are as follows:v It can produce network congestion to the RDBMS server.v It is more expensive to use a dedicated RDBMS server because it requires a

second computer.

Event server on a managed node, Web console on anon-Tivoli computer

In this deployment, the event server, the RIM host, and the RDBMS server are onone managed node. The Web console running on the WebSphere® ApplicationServer is on a non-Tivoli computer. The following graphic illustrates thisdeployment:

The advantage of this deployment is that, because the event server and theWebSphere Application Server run on different computers, each has moreprocessing power and separate memory.

RDBMS server

Tivoliserver

Non - Tivolicomputer

Event server

RIM host

RDBMS client

Figure 4. Event server on a Tivoli server, database server on a non-Tivoli computer

Managed node Non - Tivolicomputer

Event server

WebSphereApplication Server

Web console

RIM host

RDBMS server

Figure 5. Event server on a managed node, Web console on a non-Tivoli computer


Event server and NetView server on different managed nodesIn this deployment, the Tivoli server is on one managed node and the event server(connected to the NetView server), RIM host, and RDBMS server are on anothermanaged node. The following graphic illustrates this deployment:

The advantages of this deployment are as follows:v The event server computer, which is attached to the NetView server computer,

has more processing power and separate memory.v This deployment minimizes network congestion, because the RDBMS is local to

the event server and the RIM host and event server are local to the Tivoli region.

The disadvantages of this deployment are that it requires three computers, andsome debugging scenarios require comparing three separate Tivoli ManagementFramework logs.

Event server on a managed node, NetView server on a Tivoliserver, database server on a non-Tivoli computer

In this deployment, the event server, the RIM host, and the RDBMS client are on amanaged node and the RDBMS server is on a computer not managed by TivoliManagement Framework software. The event server on the managed node isconnected to the Tivoli server with the Tivoli NetView program. The followinggraphic illustrates this deployment:

Managed node

NetViewServer

Tivoliserver

Managed node

Event server

RIM host

RDBMS server

Figure 6. Event server and NetView server on different managed nodes


The advantage of this deployment is that it distributes the processing load of theTivoli server, event server, and RDBMS across three computers.

The disadvantages of this deployment are that there are network constraints, threecomputers are required, and some debugging scenarios require comparing twoseparate Tivoli Management Framework logs.

Event server and database server on a Tivoli server, NetViewserver on a non-Tivoli computer

In this deployment, the event server, the RIM host, and the RDBMS server are onthe Tivoli server. The event server is connected to the Tivoli NetView server. Thefollowing graphic illustrates this deployment:

The advantages of this deployment are as follows:v It reduces network congestion and communication delays between the processes.v It is less expensive because everything is on one computerv It is easier to debug Tivoli Management Framework-related issues because all

information is in one Tivoli Management Framework log

The disadvantage of this deployment is that it requires significantly more memoryand processor speed for all three servers, including the Tivoli NetView connection,to reside on one processor.

NetViewserver

Managed node

Tivoliserver


Event server

RIM host


Figure 7. Event server on a managed node, NetView server on a Tivoli server, databaseserver on a non-Tivoli computer

NetViewserver

Tivoliserver


Event server

RIM host

RDBMS server

Figure 8. Event server and database server on a Tivoli server, NetView server on a non-Tivolicomputer


Event server on a Tivoli server, NetView server and databaseserver on different non-Tivoli computers

In this deployment, the event server, the RIM host, and the RDBMS client are onthe Tivoli server and the RDBMS server is on a computer not managed by TivoliManagement Framework software. The event server is connected to a TivoliNetView server on a non-Tivoli computer. The following graphic illustrates thisdeployment:

The advantage of this deployment is that it off-loads the RDBMS processor load toanother computer.

The disadvantages of this deployment are as follows:v It can produce network congestion to the RDBMS server.v It is more expensive because it requires two additional computers: one for the

RDBMS server and one for the NetView server.

Tivoli Enterprise Console components in different Tivoliregions

The Tivoli environment uses Tivoli regions to meet the needs and demands ofmanaging resources that are geographically dispersed across networks. Each Tivoliregion has its own server for managing local clients and a set of distributedreplicated services for performing management operations. Tivoli regions can beconnected to coordinate activities across the network, enabling large-scale systemmanagement and remote-site management and operation.

Tivoli region connections can be either one-way or two-way connection types.One-way connections are useful when a central site is responsible foradministering several remote sites, but when none of the remote sites need tomanage resources at the central site or other remote sites. Each remote site couldalso have its own local operator. This person can be responsible for managingday-to-day operations on local resources, while the connection from the central siteis used for more global updates, such as a new version of an application.

NetViewserver

Tivoliserver



Event server

RIM host


Figure 9. Event server on a Tivoli server, NetView server and database server on differentnon-Tivoli computers


Two-way connections are useful in a variety of situations, including that of a verylarge local area network (LAN) that is logically partitioned. This allows forspreading the management server load across multiple Tivoli servers. In addition,two-way connections are needed when two or more Tivoli regions have systemmanagement staff who need to have access to and manage resources on otherTivoli regions.

Planning the partitioning of your network into a set of connected Tivoli regionsdepends on several factors, including the following:v Network topologyv Organizational and management responsibilitiesv Geographyv Security concerns

In general, Tivoli region connections are highly flexible and can be set up to mapto any arbitrary set of connections. Some items to think about during this processinclude the following:v Physical considerations, such as floors within a buildingv Multiple building locations, perhaps spread out over a cityv Organizational considerations (for example, groups such as Marketing,

Accounting, and Sales)v Large geographic distances between networks in different cities and statesv The number of systems to be managed (for example, distributing the workload

for managing 1000 computers)v Using Tivoli regions as failure domains for performance and reliability issues

In this deployment, the Tivoli Enterprise Console components are in interconnectedTivoli regions. In some cases, installing the event server and the event consoletogether in a separate Tivoli region relieves process contention.

Although you have the capability to interconnect Tivoli regions and share the otherresources, Tivoli regions cannot share an event console. If you want to run anevent console on a computer, an event console should be installed on thatcomputer.

In this deployment, consider having an operator set up as an administrator on theTivoli region that has all of the Tivoli Enterprise Console components installed.

You can create a Tivoli region containing only the event server, the event console,the RIM host, and the RDBMS server. In another Tivoli region, you install anyremaining Tivoli Enterprise Console components and any Tivoli Enterprise™

software needed in your Tivoli environment.

Note: When you have two Tivoli regions on the same subnet, you have the samenetwork congestion as if you used only one Tivoli region.

The following graphic illustrates this deployment:


Note: For a Tivoli environment that already uses multiple Tivoli regions, or for aTivoli environment that uses multiple Tivoli Enterprise Console installationsfor failovers, this deployment can serve your business needs.

Understanding product requirementsThis section lists the hardware and software requirements for the IBM TivoliEnterprise Console product. For the most current information, see the IBM TivoliEnterprise Console Release Notes.

For the most current information on the requirements of Tivoli NetViewcomponents, see IBM Tivoli NetView for UNIX Release Notes and IBM Tivoli NetViewfor Windows Release Notes.

Hardware requirements

Hardware requirements for IBM Tivoli Enterprise ConsolecomponentsThe following table describes hardware requirements for the IBM Tivoli EnterpriseConsole components. The following list provides a few notes about the informationin the table:v Minimum system requirements reflect reasonable performance for event rates of

5 per second or fewer, with fewer than five event consoles running, and asimple rule base

v Recommended system requirements reflect reasonable performance for eventrates of 20 per second, with five to ten event consoles running, and a moderatelycomplex rule base

Tivoliserver

Tivoliserver

Operator console

RIM host

Event server

RDBMS server

wregister -i -r EventServer

Tivoli regionA

Tivoli regionB

Figure 10. Tivoli Enterprise Console components in different Tivoli regions


Table 1. Hardware requirements for the Tivoli Enterprise Console product

Platform Component

RecommendedProcessingRequirement

MinimumProcessingRequirement

RecommendedMemoryRequirement

MinimumMemoryRequirement

Disk SpaceRequire–ment

UNIX/RISC

Event server installed onone machine and eventdatabase and RIMinstalled on anothermachine

Twoprocessors,SPECint_rate2000 of 10 orbetter

Singleprocessor,SPECint2000of 5 or better

1 GB 512 MB 512 MB

Event server with RIM,event database, andWebSphere ApplicationServer installed on thesame machine

Fourprocessors,SPECint_rate2000 of 30 orbetter

Twoprocessors,SPECint_rate2000 of 10 orbetter

4 GB 2 GB 8 GB

WebSphere ApplicationServer install on amachine by itself

Singleprocessor,SPECint_rate2000 of 10 orbetter

Singleprocessor,SPECint_rate2000 of 5 orbetter

2 GB 2 GB 2 GB

UI server on a separatemanaged node

Singleprocessor,SPECint2000of 150 orbetter


512 MB 256 MB 256 MB

Tivoli Enterprise Consolegateway

Singleprocessor,SPECint2000of 150 orbetter


512 MB 256 MB 256 MB

Event console Singleprocessor,SPECint2000of 90 or better

Singleprocessor,SPECint95 of 7

256 MB 128 MB 64 MB


Table 1. Hardware requirements for the Tivoli Enterprise Console product (continued)

Platform Component

RecommendedProcessingRequirement

MinimumProcessingRequirement

RecommendedMemoryRequirement

MinimumMemoryRequirement

Disk SpaceRequire–ment

WindowsandLinux/Intel

Event server withoutRIM and event databaseinstalled on machine

Twoprocessors, 1.8GHz P4

Singleprocessor, 1.8GHz P4

1 GB 512 MB 512 MB

Event server with RIM,event database, andWebSphere ApplicationServer installed on thesame machine

Fourprocessors, 1.8GHz Pentium4

Twoprocessors, 1.8GHz Pentium4

4 GB 2 GB 8 GB

WebSphere ApplicationServer install on amachine by itself

Uniprocessor1.8 GHzPentium® 4

Uniprocessor933 MHzPentium 4

2 GB 2 GB 2 GB

UI server on a separatemanaged node

Singleprocessor, 933MHz PentiumIII


512 MB 256 MB 256 MB

Tivoli Enterprise Consolegateway



512 MB 256 MB 256 MB

Event console Singleprocessor, 733MHz PentiumIII


256 MB 128 MB 64 MB

Disk space requirements for adaptersThe tables in the following sections describe disk space requirements for supportedIBM Tivoli Enterprise Console adapters.

Disk space requirements for TME adapters: The following table describes diskspace requirements for TME® adapters by platform type. A table cell is empty ifthe adapter is not supported on that platform.

Table 2. Disk space requirements for TME adapters

Operating System Endpoint AdapterHP OpenViewAdapter SNMP Adapter

AIX® 4.3.3, 5.1 2 MB 2 MB

Compaq/Digital Tru64 UNIX 5.0, 5.1 5 MB 1 MB

HP-UX 11.0 Service Pack 1, 11i 2 MB1 2 MB 2 MB

NetWare 5.0, 5.1 2 MB

OS/2® Warp 4.5.1 server for eBusiness 1 MB

Red Hat Linux for Intel 7.1, 7.2 2 MB 1 MB

SCO UnixWare 7.0.1, 7.1.1 2 MB 1 MB

Sequent® DYNIX/ptx® 4.5.1 3 MB 1 MB

SGI IRIX 6.5 3 MB 1 MB

Solaris Operating Environment 7, 8 on Solaris-x86 3 MB 1 MB

Solaris Operating Environment 7, 8 onSolaris-SPARC

2 MB 2 2 MB


Table 2. Disk space requirements for TME adapters (continued)

Operating System Endpoint AdapterHP OpenViewAdapter SNMP Adapter

SuSE Linux for Intel 7.0, 7.1 2 MB 1 MB

SuSE Linux for S/390® 7.0 3 MB 1 MB

TurboLinux for Intel 7.0 2 MB 1 MB

Windows 2000 Server, Advanced Server,ProfessionalService Pack 1

1 MB 1 MB 1 MB

Windows XP Professional 1 MB

Disk space requirements for non-TME adapters: The following table describesdisk space requirements for non-TME adapters. A table cell is empty if the adapteris not supported on that platform.

Table 3. Disk space requirements for non-TME adapters

Operating SystemEndpointAdapter

HP OpenViewAdapter SNMP Adapter

AIX 4.3.3, 5.1 4 MB 3 MB

Compaq/Digital Tru64 UNIX 5.0, 5.1 5 MB 4 MB

HP-UX 11.0 Service Pack 1, 11i 4 MB1 3 MB 3 MB

NetWare 5.0, 5.1 3 MB

OS/2 Warp 4.5.1 server for eBusiness 2 MB

Red Hat Linux for Intel 7.1, 7.2 4 MB 3 MB

SCO UnixWare 7.0.1, 7.1.1 4 MB 3 MB

Sequent DYNIX/ptx 4.5.1 4 MB 3 MB

SGI IRIX 6.5 4 MB 3 MB

Siemens Nixdorf (Pyramid) Reliant UNIX 5.45 5 MB 4 MB

Solaris Operating Environment 7, 8 on Solaris-x86 4 MB 3 MB

Solaris Operating Environment 7, 8 on Solaris-SPARC 4 MB 3 MB 3 MB

SuSE Linux for Intel 7.0, 7.1 4 MB 3 MB

SuSE Linux for S/390 7.0 4 MB 3 MB

TurboLinux for Intel 7.0 4 MB 3 MB

Windows 2000 Server, Advanced Server,ProfessionalService Pack 1

1 MB 1 MB 1 MB

Windows XP Professional 1 MB

Disk space requirements for AS/400 Adapters: The following table describes diskspace requirements for AS/400® adapters.

Table 4. Disk space requirements for AS/400 adapters

AdapterDisk SpaceRequirement

AS/400 Alert 6 MB

AS/400 Message 7 MB


Table 4. Disk space requirements for AS/400 adapters (continued)

AdapterDisk SpaceRequirement

AS/400 Alert and Message (both adapters on the same machine) 8 MB

Software requirements

Operating system requirementsTivoli Enterprise Console software supports the following operating systems:

Table 5. Operating system requirements for the Tivoli Enterprise Console product

Operating system Version Eventserver

NetViewserver

AdapterConfigura–tionFacility

UI Server Eventconsole (Javaversion)

Endpoint

IBM AIX 4.3.3, 5.1,5L, 5.2

U U U U U U

Sun SolarisOperatingEnvironment(Solaris)

8, 9 U U U U U U

HP-UX (PA-RISC) 11.0 spl, 11i U U U U U

Windows XP Pro, 2000Pro

U U

Windows 2000 Server U U U U U U

Windows 2000Datacenter

U

Windows 2003 Server U U U U U U

Windows 2003AdvancedServer

U U U U U U

IBM zOS V1R2, V1R3,V1R4

U

SuSE LinuxEnterprise Server forIA32

7 (7.2 base) U U U U U U

SuSE LinuxEnterprise Server foriSeries™

7 (7.2 base) U

SuSE LinuxEnterprise Server forzSeries™

7 (7.2 base) U U U U U

SuSE LinuxEnterprise Server forpSeries™

7 (7.2 base) U

United Linux forIA32 (SLES 8)

1.0 U U U U U U

United Linux foriSeries (SLES 8)

1.0 U

United Linux forpSeries

1.0 U


Table 5. Operating system requirements for the Tivoli Enterprise Console product (continued)

Operating system Version Eventserver

NetViewserver

AdapterConfigura–tionFacility

UI Server Eventconsole (Javaversion)

Endpoint

United Linux forzSeries (SLES 8)

1.0 U U U U U

Redhat Linux forzSeries

7.2 U U U U U

Redhat Linux foriSeries

7.2 U

Redhat Linux forpSeries

7.2 U

Redhat LinuxAdvanced Server 2.1for IA32

2.1 U U U U U U

NetWare 5.1, 6.0 U

OS/400® V5R1, V5R2 U

OS/2 Warp 4.5 U

OS/2 Server foreBus

4.5.1 U

Compaq Tru64 5.1, 6.0 U

Reliant UNIX 5.4.5 U

SCO Unixware 7.1.1, Open,UNIX 8

U

Irix SGI 6.5.x U

Solaris ix86 7,8 U

Sequent Dynix/PTX 4.6.1 U

Database requirementsTivoli Enterprise Console software supports the following databases for the eventdatabase:

Table 6. Database requirements for the Tivoli Enterprise Console product

Database Version

DB2 Universal Database 7.2 (fix pack 7) WE, EE, EEE; 8.1 WSE, ESE

Oracle 8.1.7, 9i, 9i V2, 9i for Linux

Microsoft® SQL Server 7.0 SP2, SP3; SQL Server 2000

Informix® 9.3 Dynamic Server 2000

Sybase 11.9.2, 12.0, 12.5 (Adaptive Server Enterprisefor Linux)

For information on configuring databases with RIM, refer to the latest TivoliManagement Framework Release Notes.


Note: The Tivoli Enterprise Console product does not support a database that ison the native z/OS partition. The Tivoli Enterprise Console database can beused on a z/OS system only if a supported database is running on a Linuxz/OS partition.

Tivoli Management Framework requirementsTivoli Enterprise Console Version 3.9 requires Tivoli Management FrameworkVersion 3.7.1 or later. For required Tivoli Management Framework patches, see theIBM Tivoli Enterprise Console Release Notes.

WebSphere Application Server requirementsThe Tivoli Enterprise Console Version 3.9 Web console component requiresWebSphere Application Server Version 5.0 Base Edition. This product is requiredfor the Web console and can be installed during the installation of the Web console.Other editions of the WebSphere Application Server Version 5.0 are not supported.

Web browser requirementsThe Web console requires one of the following browsers:v Microsoft Internet Explorer 6.0 or laterv Netscape 6.x beginning with 6.2. Netscape 7.x is not supported.

Tivoli Enterprise Console upgrade requirementsTo upgrade Tivoli Enterprise Console components, you must have Tivoli EnterpriseConsole components of version 3.6.2 or later.

To upgrade Tivoli NetView components, you must have Tivoli NetViewcomponents of version 6.0 or later.

Additional requirementsBecause the Tivoli Enterprise Console installation wizard is a GUI-based program,it requires an X server environment on the UNIX operating system.

On UNIX operating systems, you must install the compress and uncompressutilities before you install the Tivoli Enterprise Console product. For all UNIXoperating systems except Linux, these utilities are installed with the operatingsystem. For Linux, you must install the compress and uncompress utilitiesseparately.

For a complete list of other software requirements, see the IBM Tivoli EnterpriseConsole Release Notes.

Tivoli Enterprise Console product imagesFor a list of product images, see the IBM Tivoli Enterprise Console Release Notes.


Chapter 2. Preparing for installation

Before you can begin to install the Tivoli Enterprise Console product, you mustcomplete the following:v “Installing the Tivoli Management Framework”v “Installing and configuring the RDBMS”v “Preparing to install components” on page 21

You may also need to complete these tasks, depending upon your situation:v “Preparing to upgrade from Version 3.6.2” on page 33v “Preparing to install components in interconnected Tivoli regions” on page 35v “Preparing to install language packs” on page 31

Performing preinstallation tasksBefore you install the Tivoli Enterprise Console product, you must completeseveral preinstallation tasks. This section outlines the steps and provides the detailsthat you need to complete these tasks.

Before you install the Tivoli Enterprise Console product, you must complete thefollowing tasks:1. “Installing the Tivoli Management Framework”2. “Installing and configuring the RDBMS”

Installing the Tivoli Management FrameworkBefore you install the Tivoli Enterprise Console product, you must install the TivoliManagement Framework Version 3.7.1 or later. For information on how to installthis product, see the Tivoli Enterprise Installation Guide. For an example of how toinstall Tivoli Management Framework, see “Installing the Tivoli ManagementFramework” on page 96.

Installing and configuring the RDBMSFor the Tivoli Enterprise Console product to work within your Tivoli environment,you must install and configure a supported RDBMS before installing any TivoliEnterprise Console component:v In a client/server configuration:

– The RDBMS client software and the RIM host must be on the same managednode.

– The RDBMS server can be on any computer. It does not need to be amanaged node.

v In a server-only RDBMS configuration, the RDBMS server must be installed on amanaged node. The RIM host must be on this same managed node.

For additional information about the RIM host, see the Tivoli Enterprise InstallationGuide.

The following sections include information about installing and configuring thesupported RDBMS databases (DB2®, Informix, Microsoft SQL Server, Oracle, andSybase).


Note: It is important to read the Tivoli Management Framework Release Notes andany Tivoli Management Framework patch readme files for information aboutthe RIM requirements for your RDBMS. Information contained in thereadme files may contain RIM changes that supersede the Tivoli ManagementFramework User’s Guide and the Tivoli Management Framework Release Notes.

Back up your database server before initiating any of the changes described in thefollowing sections.

Choosing the RDBMS serverThe RDBMS server hosts the event repository schema. Consider the followingwhen you determine which computer is to be your RDBMS server:v This computer must have a TCP/IP connection to the RIM host.v This computer does not need to be a managed node in the Tivoli region, but it

must be on the same subnet as the Tivoli region.v This computer must have enough available disk space to support the amount of

information that you plan to store in the event repository.

Choosing the RIM hostThe RIM host provides communication with the RDBMS database in a common,database-independent manner. Consider the following when you determine whichcomputer is to be your RIM host:v The RIM host must be a managed node.v The RIM host must have the RDBMS client or server software installed.v In most Tivoli environments using the Tivoli Enterprise Console product, the

most efficient place for the RIM host is on the event server.v When the RIM host is an HP-UX or Windows computer, the tmersrvd user

account must be defined on that computer. For additional information about thetmersrvd account, refer to the Tivoli Enterprise Installation Guide.

Installing and configuring DB2From a DB2 perspective, the RIM host is a database client. Therefore, the RIM hostmust have access to a DB2 server. Either a DB2 server or a DB2 client must beinstalled on the RIM host.

The following information provides an overview of the steps required to configurea DB2 database for use with the RIM host. The installation process andconsiderations for a DB2 database are independent of this documentation.Therefore, you should follow the installation and configuration informationprovided in your IBM DB2 documentation.

Note: When you install a DB2 database on a UNIX operating system, yourenvironment variables are created in the .profile file of the instance owner.

These variables can be set by running the .db2profile script (bash, Bourne,or Korn shell) or the .db2cshrc script (C shell).

For RIM, you must name the DB2 user the same as the DB2 instance name. For aDB2 database, the DB2 user name must be eight characters or fewer.

Note: In the UNIX operating system, the DB2 user name is the same as theinstance name by default. However, in Windows you must ensure that auser with the same name as the instance name exists.


Configuring the DB2 server for remote client access: If the RIM host is the samecomputer as your DB2 server, no additional configuration is required. If you wantremote DB2 clients to access your DB2 server, perform the following procedure:1. Add the DB2COMM environment variable with the value tcpip.2. Configure the DB2 server to accept TCP/IP clients. Edit the /etc/services file,

and add an entry for the connection port. For example, add the following linesto the services file:TEC 3700/tcp #DB2 connection service port

3. From the command line, enter the following:db2 update database manager configuration using svcename TEC

This command updates the service name with the connection port name (TEC),which is also the instance name in this example.

Configuring the DB2 client: To configure the DB2 client, perform the followingprocedure:1. Configure the client to use TCP/IP to connect to the server. Edit the

/etc/services file and add the entry for the connection port. For example, addthe following line to the services file:TEC 3700/tcp #DB2 connection service port

2. Add the DB2COMM environment variable with the value tcpip.3. Catalog the server node and perform the following steps to update the remote

database:a. Start the DB2 interactive structured query language (SQL) utility by

entering the following:db2

b. Catalog the server node:catalog tcpip node db2node remote hostname \

server service_name

where:

db2nodeSpecifies the name of the computer where the DB2 client isinstalled. This name must be unique in your node directory list.

hostnameSpecifies the name of the computer where the DB2 server isinstalled.

service_nameSpecifies the connection port name as defined in the services file.

Installing and configuring InformixBefore you begin creating an Informix event repository, review the followingprerequisites:v The Informix Client must be installed on the RIM host and the .odbc.ini file

must be installed in the directory where the Informix software is installed($INFORMIXDIR).

v It is recommended that you use unbuffered logging with all Informix databases.The Tivoli Enterprise Console database for Informix is created with unbufferedlogging. Do not use American National Standards Institute (ANSI) modelogging, because it can cause problems with database locks that can result instopping the Tivoli application programs.

Chapter 2. Preparing for installation 19

Note: Testing has shown that Informix databases can have concurrencyproblems in high transaction or high volume Tivoli environments. Underthese types of conditions, tune your Informix server carefully to ensureyou do not have locking problems that result in data loss. In certainconditions, enabling row-level locking may resolve locking problems withthe Tivoli Enterprise Console product. Consult your Informix databaseadministrator to determine the best lock mode for your environment.

For additional installation information specific to an Informix database, see yourInformix documentation.

Installing and configuring Microsoft SQL ServerInstall the Microsoft SQL Server on the RDBMS server. For installation details, referto your Microsoft SQL Server documentation.

Note: The Install Options dialog box displayed during Microsoft SQL Serverinstallation includes a Sort Order option. To use Microsoft SQL Server foryour event repository, you must select the Dictionary order, case-sensitiveoption at installation.

Select a Windows managed node to be the RIM host. The Microsoft SQL Serverclient or the Microsoft SQL Server must be installed on the RIM host computer.

For additional installation information specific to Microsoft SQL Server, see yourMicrosoft SQL Server documentation.

Installing and configuring OracleInstall the Oracle RDBMS and SQL*Plus on the RDBMS server. For installationdetails, refer to your Oracle documentation.

Select a managed node to be the RIM host.

Complete the following steps to configure the RIM host as an Oracle client usingSQL*Plus. Refer to your Oracle documentation if you want to use Oracle names.1. Install the Oracle client software, which includes SQL*Plus, on the RIM host.2. If the Oracle server is on a separate computer than the client, copy the

tnsnames.ora file from the %ORACLE_HOME%\network\admin directory onthe RDBMS server to the %ORACLE_HOME%\network\admin directory on theRIM host where ORACLE_HOME is the environment variable equating to thepath to the directory where your Oracle server or client installation resides.

3. Verify that the tnsnames.ora file is properly updated to reflect yourconfiguration. In other words, check that the host name of the server, theOracle instance ID, the port SQL*Plus is connected to, and the communicationprotocol are accurate.

For additional installation information specific to Oracle, see your Oracledocumentation.

Installing and configuring SybaseInstall the Sybase RDBMS. For installation details, refer to your Sybasedocumentation for instructions.

Select a managed node to be the RIM host, and complete the following steps toconfigure the RIM host as a client of the RDBMS server:1. Install the Sybase client software, which includes isql, on the RIM host.


2. If your RIM host is a Windows computer, perform the following:a. Ensure that the PATH variable includes the directory where the Sybase DLL

files are installed.b. Ensure that the SQL.INI file is in the %SYBASE%\INI directory on the RIM

host where SYBASE is the environment variable equating to the path to thedirectory where your Sybase installation resides.

If your RIM host is a UNIX computer, copy the interfaces file from the RDBMSserver to the directory on the RIM host where the Sybase client software isinstalled.

Note: If the RDBMS server runs on a computer with a Solaris OperatingEnvironment, and your RIM host is not a Solaris computer, or vice versa,do not copy the interfaces file to your RIM host. The interfaces filefor Solaris Operating Environments is not compatible with otheroperating systems. You must create a new interfaces file that iscompatible. Consult your database administrator for assistance.

For additional installation information specific to Sybase, see your Sybasedocumentation.

Preparing to install componentsThe following sections describe the components and provide important installationdetails that you should understand before installing components, as shown in thefollowing table.

Table 7. Explanation of tables

Table category Explanation Options

Environment: Which environment thiscomponent can exist in

Tivoli—requires computersthat contain TivoliManagement Frameworksoftware

non-Tivoli—does not requirecomputers that contain TivoliManagement Frameworksoftware; if the TivoliManagement Frameworksoftware is on the computer, itis not used

Supported operatingsystems:

Which operating systems thiscomponent can be installed on

In general, Windows, AIX,Solaris, HP-UX, Linux, andzLinux. For details, see“Operating systemrequirements” on page 14

Instances: How many instances of thiscomponent can exist in aTivoli region or in a non-Tivolienvironment

One or multiple


Table 7. Explanation of tables (continued)

Table category Explanation Options

Applicable installation,upgrade, oruninstallation method:

What method you can use toinstall, upgrade, or uninstallthis component

The installation wizard orTivoli ManagementFramework tools. For detailson using the installationwizard, see Chapter 3,“Installing, upgrading, anduninstalling using theinstallation wizard”, onpage 37

Tivoli Enterprise Console componentsThe Tivoli Enterprise Console components provide the event managementcapability of the product and are described in the following sections.

Tivoli Enterprise Console JREDescription: The Tivoli Enterprise Console JRE is an installable component and isa requirement for the event server, the UI server, the event console, and theAdapter Configuration Facility. This component makes the Java Runtimeenvironment available for use. As appropriate, the installation wizard installs anduninstalls the Tivoli Enterprise Console JRE automatically. However, if you areusing the Tivoli Management Framework tools, you must perform these operationsmanually.

Note: If you are uninstalling the Tivoli Enterprise Console components using theinstallation wizard and receive the following error message, ignore this errormessage. The error occurs when installation wizard attempts to remove theTivoli Enterprise Console JRE component from a managed node in whichthis component has been already uninstalled:FRWTT0003E An instance named "TEC39_JRE" ofresource "Uninstall" was not found.Not an Uninstallable Application:TEC39_JRE

Event serverDescription: The event server is a central server that handles all events in thedistributed system. The event server creates an entry in an RDBMS for eachincoming event and then evaluates these events against a set of rules to determineif it should respond to or modify the event automatically.

Table 8. Event server details

Environment: Tivoli

Supported operating systems: All supported operating systems

Instances: One per Tivoli region

Applicable installation method: Installation wizard or Tivoli ManagementFramework tools

Applicable upgrade method: Installation wizard or Tivoli ManagementFramework tools

Applicable uninstallation method: Installation wizard or Tivoli ManagementFramework command line

Installation notes: The event database must be configured before you install thiscomponent. You must install the Tivoli Enterprise Console JRE before installing this


component. The installation wizard does this automatically. However, if you areusing the Tivoli Management Framework tools, you must install the TivoliEnterprise Console JRE manually.

When you install using the installation wizard, as part of the installation processyou are given the opportunity to deactivate any of the default active rule sets.When you install using Tivoli Management Framework tools, you can deactivateany of the default active rule sets manually using the wrb_default_rb command.The default rule base contains many rule sets that you can customize afterinstallation. For more information, see the IBM Tivoli Enterprise Console Rule SetReference.

Note: The dependency rule set is active by default, but its activity is linked to theebusiness rule set and can only be changed by changing the activity of theebusiness rule set. In other words, when you deactivate the ebusiness ruleset, you also deactivate the dependency rule set.

Upgrade notes: The event database must be upgraded before you upgrade thiscomponent. After you upgrade, you must reload your rule base because the .barocfiles have been modified. You must install the Tivoli Enterprise Console JRE beforeupgrading this component. The installation wizard does this automatically.However, if you are using the Tivoli Management Framework tools, you mustinstall the Tivoli Enterprise Console JRE manually.

When you upgrade using the installation wizard, as part of the upgrade processyou are given the opportunity to deactivate any of the default active rule sets.When you upgrade using Tivoli Management Framework tools, you can deactivateany of the default active rule sets manually using the wrb_default_rb command.The default rule base contains many rule sets that you can customize afterupgrading. For more information, see IBM Tivoli Enterprise Console Rule SetReference.

Note: The dependency rule set is active by default, but its activity is linked to theebusiness rule set and can only be changed by changing the activity of theebusiness rule set. In other words, when you deactivate the ebusiness ruleset, you also deactivate the dependency rule set.

If you used any customized parameters, you must preserve the file$BINDIR/TME/TEC/.tec_config file before you upgrade the event server. Youmust then reapply the customizations to that file after the upgrade is completed.

Uninstallation notes: It is recommended that you uninstall the event server afteruninstalling all other components.

User interface (UI) serverDescription: The user interface (UI) server provides conflict management for eventconsole updates and prevents multiple event consoles from attempting tosimultaneously update identical events. This is achieved by warning the secondaryuser that the event is locked for updates by another console.

Table 9. User interface (UI) details

Environment: Tivoli


Instances: One per region


Table 9. User interface (UI) details (continued)




Installation notes: The event database must be configured before you install thiscomponent so that the default event groups and consoles can be configured in thedatabase. To reduce the network traffic, install the UI server on the same computeras the event server; this component communicates with the event server.

In most situations, the user interface server configures default event groups andconsoles automatically during installation. However, if you are using theinstallation wizard and installing this component on the AIX operating system, youmust specify the user name and password for the computer where you install theuser interface server. If you are manually installing this component on the AIXoperating system, you must run the wcrtteccfg command after installing the userinterface server.

You must install the Tivoli Enterprise Console JRE before installing this component.The installation wizard does this automatically. However, if you are using theTivoli Management Framework tools, you must install the Tivoli EnterpriseConsole JRE manually.

Upgrade notes: The event database must be upgraded before you upgrade thiscomponent.

You must install the Tivoli Enterprise Console JRE before upgrading thiscomponent. The installation wizard does this automatically. However, if you areusing the Tivoli Management Framework tools, you must install the TivoliEnterprise Console JRE manually.

Event consoleDescription: An event console provides a graphical user interface (GUI) thatoperators can use to view and respond to events. A senior administrator configuresmultiple event consoles based on the responsibilities of the IT staff. Operators canhave independent or shared views of events. The Tivoli Enterprise Console productprovides two versions of the event console, a Java version and a Web version.Administrators and operators can use the Java version or the Web version, or both,to manage events. Administrators must use the Java version to performconfiguration tasks, and administrators or operators must use the Java version tostart Tivoli NetView functions.

The event console can be installed on a Tivoli managed node or on a non-Tivolicomputer. The non-Tivoli version of the event console does not use the TivoliManagement Framework services during installation.

Java version:

Table 10. Event console (Java version) details

Environment: Tivoli, non-Tivoli


Table 10. Event console (Java version) details (continued)

Supported operating systems: For a Tivoli environment: all supportedoperating systems. For a non-Tivolienvironment, all supported operating systemsexcept zLinux.

Instances: One or more per region

Applicable installation method: For a Tivoli environment: installation wizard orTivoli Management Framework tools. For anon-Tivoli environment: installation wizard.

Applicable upgrade method: For a Tivoli environment: installation wizard orTivoli Management Framework tools.

Applicable uninstallation method: For a Tivoli environment: installation wizard orTivoli Management Framework command line.For a non-Tivoli environment: Uninstallprogram.

Installation notes: For the event console to operate properly, the Tivoli servername must be a fully-qualified domain name. For each computer that the eventconsole is installed on, ensure that the domain name service (DNS) is properlyconfigured in your environment to resolve the domain name for the Tivoli server.If you are unsure about your configuration, contact your system administrator.

You can install the event console in a Tivoli environment on zLinux. However, onlynon-GUI console commands are available. The event console GUI is not available.


Upgrade notes: For a non-Tivoli environment, no upgrade is necessary. Uninstallthe previous version, and install a new version.

For a Tivoli environment, you must install the Tivoli Enterprise Console JRE beforeupgrading this component. The installation wizard does this automatically.However, if you are using the Tivoli Management Framework tools, you mustinstall the Tivoli Enterprise Console JRE manually.

Uninstallation notes: For a non-Tivoli environment, on Windows, use the Uninstallprogram (Start —> IBM Tivoli Enterprise Console —> Uninstall); on all otheroperating systems, run this uninstallation script:installation_directory/tec_console/uninst_tecconsole, whereinstallation_directory is the directory where the event console is installed.

Web version:

Table 11. Event console (Web version) details

Environment: Non-Tivoli (WebSphere Application Server)

Supported operating systems: Windows, AIX, Solaris, HP-UX, Linux, zLinux(for the most current list of supported operatingsystems, see the WebSphere Application Serverdocumentation)

Instances: One or more


Table 11. Event console (Web version) details (continued)

Applicable installation method: Installation wizard

Applicable uninstallation method: Installation wizard

Installation notes: During installation, the Web console is configured to work withthe specified Tivoli regions. To add additional Tivoli regions or to edit the WebConsole configuration, use the WebSphere Application Server administrativeconsole. For more information, see the IBM Tivoli Enterprise Console User’s Guide.

Adapter Configuration FacilityDescription: The Adapter Configuration Facility is a profile-based application usedto configure and distribute TME adapters using a GUI. The Adapter ConfigurationFacility allows you to create profiles for adapters and set configuration anddistribution options. The adapters can then be distributed to the profile’ssubscribers using menu options or drag-and-drop functionality. This feature allowsyou to make changes in a central location and then distribute them to the remotecomputers.

Table 12. Adapter Configuration Facility details

Environment: Tivoli


Instances: One in the Tivoli server and one in everymanaged node that is configured as a Tivoligateway




Installation notes: If you use the Adapter Configuration Facility, you must install iton the following computers in the following order:1. The Tivoli server—it must be installed first before the managed nodes2. All managed nodes that are endpoint gateways


Non-TME operations of the Adapter Configuration Facility are not supported inHP-UX operating systems.

Upgrade notes: You must install the Tivoli Enterprise Console JRE beforeupgrading this component. The installation wizard does this automatically.However, if you are using the Tivoli Management Framework tools, you mustinstall the Tivoli Enterprise Console JRE manually.

Uninstallation notes: You must uninstall from the managed nodes first beforeuninstalling from the Tivoli server.


Event adaptersDescription: Event adapters are processes that typically reside on the same host asa managed source. A source is an application (such as a database) or a systemresource (such as available disk space). When an event adapter receivesinformation from its source, the adapter formats the information and forwards it tothe event server. For information on how to install adapters, see the IBM TivoliEnterprise Console Adapters Guide.

HP OpenView adapterDescription: The HP OpenView adapter is the Tivoli Enterprise Console adapterfor the HP OpenView product that forwards events from OpenView to the eventserver.

Table 13. HP OpenView adapter details

Environment: Tivoli

Supported operating systems: HP-UX, Windows, and Solaris

Instances: One or more per region




Installation notes: This adapter must be installed on the computer containing theHP OpenView product.

Sample event informationDescription: Sample event information is provided as an example to handlerequests for additional event information that an operator may need. Each eventclass has a template, which can be modified to include additional informationabout an event and the action required to resolve the problem. This facilitates thecreation of a comprehensive online system of event information andtroubleshooting.

Table 14. Sample event information details

Environment: Tivoli


Instances: One per region, usually on a Tivoli server; seeinstallation notes

Applicable installation method: Installation wizard or Tivoli ManagementFramework tools.



Installation notes: The sample event information can be used as a template todevelop an online guide for describing and troubleshooting events. After thesample event information is installed, an administrator can modify the eventinformation templates to provide guidance to operators with regard to variousevent types.


The sample event information must be installed on the Tivoli server to use theTivoli-supplied spider Web server. The installation process configures your spiderserver to handle requests for event information. As part of the installation process,a Perl script, a Perl library, and several HTML files are installed. The tec_help.plPerl script and the cgi-lib.pl library are installed in the $BINDIR/TAS/HTTPd/cgi-bin directory. The event information HTML files are installed in the$BINDIR/../generic/HTTPd/Tec directory. Translated event information isinstalled in the locale-specific $BINDIR/../generic/HTTPd/Tec/your_localedirectory.

If you are using Tivoli Management Framework 4.1, the spider Web server is notautomatically started. You must start the spider Web server before using thesample event information. To start the spider Web server, use the wstarthttpdcommand.

To install the sample event help files on a Web server that is not the Tivoli server,perform the following steps:1. Install the sample event help files on a managed node.2. Copy the tec_help.pl and cgi-lib.pl files to your cgi-bin directory.3. Copy the HTML files to a specified directory configured to access the Web

server.4. Start the event console.5. Click Window —> Configuration.6. Right-click Consoles node and click Preferences to open the Console

Preferences window.7. Expand the Web server node.8. Click Use Other Web Server, and type the new Web server URL and port

number.9. Optionally to change the event information perl script, click Event

Information, click Enable, and type the event information perl script in theProgram Path.

10. You can then optionally use the tec_help.pl Perl script for an example toprocess event attribute information. Administrators can use this script ormodify it to implement the event information strategy that best complementstheir company’s availability strategy.

Tivoli Event Integration FacilityThe Tivoli Event Integration Facility is no longer an installable component of theTivoli Enterprise Console product. This facility is a toolkit that is available on theproduct images but does not need to be installed. Existing Tivoli Event IntegrationFacility components can be uninstalled using the installation wizard or the TivoliManagement Framework command line. It is recommended that you uninstall theTivoli Event Integration Facility from all managed nodes. For more information,see the Tivoli Event Integration Facility Reference.

Tivoli NetView componentsThe Tivoli NetView components provide the network management capabilities ofthe product and are described in the following sections. For more information onthe installation of Tivoli NetView components, see IBM Tivoli NetView for UNIXRelease Notes and IBM Tivoli NetView for Windows Release Notes.


NetView serverDescription: The NetView server is a network management program that usesSNMP to discover, monitor, and configure TCP/IP networks. Network topologyand event information are stored in an internal database. The NetView serverprovides a default set of significant network events that are forwarded to the TivoliEnterprise Console product. These events include status events, selected SNMPdata collection threshold events, and router fault isolation events.

Table 15. NetView server details


Supported operating systems: For a non-Tivoli environment: Windows, AIX,Solaris, Linux, and zLinux. For Tivolienvironment: AIX, Solaris.


Applicable installation method: For a non-Tivoli environment, on Windows, theTivoli NetView installation program forWindows; on all other operating systems, theinstallation wizard.

For a Tivoli environment, installation wizard orTivoli Management Framework tools.

Applicable upgrade method: For a non-Tivoli environment, on Windows, theTivoli NetView installation program forWindows; on all other operating systems, theinstallation wizard.

For a Tivoli environment, installation wizard orTivoli Management Framework tools.

Applicable uninstallation method: Uninstallation programs

Installation notes: The NetView Web console is installed automatically when theNetView server is installed. The NetView server requires an SNMP agent, whichshould be installed prior to installing NetView server.

For Tivoli environments, you must configure the NetView server manually byrunning the /usr/OV/bin/nvits_config script after installation.

For non-Tivoli environments, the installation wizard installs the NetView server onSolaris, Linux, zLinux, and AIX operating systems. To install the NetView serveron Windows, use the installation program on the NetView for Windows CD. OnUNIX, the installation wizard configures the NetView server for non-Tivoli-basedcommunication with the event server during installation.

The NetView server can communicate with the event server using eitherTivoli-based communication or non-Tivoli-based (socket-based) communication. Toconfigure the NetView server for Tivoli-based communication, after installation ina Tivoli or non-Tivoli environment, use the /usr/OV/bin/serversetup commandfrom the command line.

The Tivoli-based communication requires the following:v An endpoint must be installed on the computer where NetView server is

installed.v A Tivoli Enterprise Console gateway must exist between the NetView server and

the event server.


Even though there can be multiple endpoints on a single computer that areconnected to different gateways, the NetView server can forward events to onlyone event server at a time.

On UNIX, to configure the NetView server for Tivoli-based communication, afterinstallation in a Tivoli or non-Tivoli environment, complete the following:1. Type /usr/OV/bin/serversetup from the command line to start the NetView

Server Setup application.2. Click Configure —> Configure event forwarding to IBM Tivoli Enterprise

Console.3. Ensure that Forward events to IBM Tivoli Enterprise Console is set to yes.4. If you want to configure event forwarding to an event server, type the Tivoli

event server host name, and type the server port number if the event server isrunning on Windows or if the portmapper is not being used on the eventserver computer. If the portmapper is being used on the event servercomputer, set the server port number to 0 for a UNIX event server or 5529 fora Windows event server.If you want to configure event forwarding to the registered event server, type@EventServer for the Tivoli event server host name without specifying theport number.

5. From the NetView rule name menu, select TEC_ITS.rs.6. Click Yes for Use TME transport mechanism.7. Type the TME endpoint instance number to use or select it from the list.8. Click Okay or Apply. The Setup:Output window appears that logs the action.9. Click Close when the operation is complete.

10. Click Cancel to exit the Setup:Options window.11. Click File —> Quit to exit the Setup:Menu window.

On Windows, to configure the NetView server for Tivoli-based communication,after installation, see the IBM Tivoli NetView for Windows Release Notes.

Upgrade notes: For non-Tivoli environments, the installation wizard upgrades theNetView server on Solaris, Linux, zLinux, and AIX operating systems. To upgradethe NetView server on Windows, use the installation program on the NetView forWindows CD.

For Tivoli environments, you must configure the NetView server manually byrunning the /usr/OV/bin/nvits_config script after upgrade.

To configure the NetView server for Tivoli-based communication, after upgrade ina Tivoli or non-Tivoli environment, use the /usr/OV/bin/serversetup commandfrom the command line as explained in the Installation notes.

Uninstallation notes: On Windows, use the Uninstall Tivoli NetView program(Start —> Tivoli NetView —> Installation —> Uninstall NetView).

On all other operating systems, complete the following:1. Close the NetView graphical user interfaces on this server and any clients or

applications that reference this server.2. Type /usr/OV/bin/serversetup from the command line to start the NetView

Server Setup application.3. Click Maintain —> Deinstall IBM Tivoli NetView


4. Click either Deinstall Tivoli NetView (if no dependent products installed) orDeinstall Tivoli NetView (leave dependent products installed), depending onwhether you want to uninstall Tivoli NetView even if there are dependentproducts installed. Refer to the online help for information on these twooptions.

5. Click OK on the verification message dialog to start the removal. The NetViewcode is removed from the server machine.

6. Close the Server Setup application window when removal is complete to shutdown the Server Setup Application.

In a Tivoli environment, you can also use the NetView Framework menus in theTivoli Desktop to uninstall the NetView server: click Maintain —> Deinstall IBMTivoli NetView and then click either Deinstall Tivoli NetView (if no dependentproducts installed) or Deinstall Tivoli NetView (leave dependent productsinstalled).

NetView Web consoleDescription: The NetView Web console is a Java-based graphical user interface(GUI) that allows operators to view the network topology and provides diagnosticand informational tools to aid in troubleshooting network problems.

Table 16. NetView Web console details

Environment: Non-Tivoli

Supported operating systems: All supported operating systems except zLinux


Applicable installation method: On Windows, the Tivoli NetView installationprogram for Windows; on all other operatingsystems, the installation wizard.

Applicable uninstallation method: Uninstallation program

Installation notes: For the NetView Web console to work, it must be installed inthe same computer as the event console (Java version).

The NetView Web console can only be installed in non-Tivoli environments. Inthese environments the installation wizard installs the NetView Web console onSolaris, Linux, zLinux, and AIX operating systems. To install the NetView Webconsole on Windows, use the installation program on the NetView for WindowsCD.

Upgrade notes: No upgrade is necessary. Uninstall the previous version and installa new version.

Uninstallation notes: Run this uninstallation script:installation_directory/nvwc/uninstall_nvwc, where installation_directory is thedirectory where the NetView Web console is installed.

Preparing to install language packsThe Tivoli Enterprise Console product comes set up for English. If you want to useanother language you must install a language pack.


Tivoli Enterprise Console language packsDescription: Language packs for these languages are available for the TivoliEnterprise Console component:v Germanv Spanishv Frenchv Italianv Japanesev Koreanv Portuguese (Brazilian)v Chinese Simplifiedv Chinese Traditional

Table 17. Language packs for Tivoli Enterprise Console details




Applicable installation method: For a Tivoli environment, installation wizard orTivoli Management Framework tools.

For a non-Tivoli event console, the installationprogram in the language pack CD

Installation notes: Using the installation wizard, you can install language packs asyou install Tivoli Enterprise Console components or later after you have installedthe components. There is no separate language pack installation required for theWeb console.

Upgrade notes: No upgrade is necessary. Install the new version.

Uninstallation notes: No uninstallation program is available.

Tivoli NetView language packsDescription: Language packs for these languages are available for the TivoliNetView component:v Japanese SJIS (available for AIX only)v Japanese EUCv Koreanv Chinese (Simplified)

For more information, see the ″Installing and Using the Tivoli NetView LanguageKits″ section of the IBM Tivoli NetView for UNIX Release Notes and IBM TivoliNetView for Windows Release Notes.

Table 18. Language packs for Tivoli NetView details





Table 18. Language packs for Tivoli NetView details (continued)

Applicable installation method: On Windows, the Tivoli NetView installationprogram for Windows; on all other operatingsystems whether Tivoli or non-Tivolienvironment, the installation wizard.

For a Tivoli environment, you can also use theTivoli Framework tools.

Applicable uninstallation method: Uninstallation program

Installation notes: There is no separate language pack installation required for theNetView Web console.

Upgrade notes: No upgrade is necessary. Install a new version.

Uninstallation notes: To uninstall the NetView language kit in Tivoli or non-Tivolienvironments, use the following uninstall scripts provided in the TOOLS directoryof the Tivoli NetView language support directory:v deinstal.ja_sjis uninstalls the NetView Japanese SJIS server kitv deinstal.ja_euc uninstalls the NetView Japanese EUC server kitv deinstal.ko uninstalls the NetView Korean sever kitv deinstal.zh uninstalls the Simplified Chinese server kit

Uninstalling NetView server also uninstalls the language packs associated with it.

Preparing to upgrade from Version 3.6.2Upgrading Tivoli Enterprise Console components from Version 3.6.2 requiresspecial procedures. Because the event server, Adapter Configuration Facility, andHP OpenView adapter were components of 3.6.2, you can upgrade thesecomponents. However, because the event console (Java version), the UI server, andthe sample event information are components that were introduced later, you mustinstall these components, not upgrade them.

For Version 3.9, you must install Tivoli Enterprise Console JRE before you caninstall or upgrade the event server, the UI server, the event console, and theAdapter Configuration Facility. As appropriate, the installation wizard installs anduninstalls the Tivoli Enterprise Console JRE automatically. However, if you areusing the Tivoli Management Framework tools, you must perform these operationsmanually.

Note: If you are upgrading from Version 3.6.2 and you want to maintain yourcurrent event consoles, event groups, and console operators’ existingconsoles, you must also perform the migration step manually using thewmigcon command. Event consoles are automatically migrated in theupgrade process with versions greater than 3.6.2.

Upgrade 3.6.2 componentsThe following components are components of Version 3.6.2 and should beupgraded:


Event serverSpecial instructions: If any customized parameters were used, the.tec_config file, under $BINDIR/TME/TEC, must be preserved before thecomponent is upgraded.

Adapter Configuration FacilitySpecial instructions: none.

HP OpenViewSpecial instructions: none.

Rule base and compiler

Special instructions: Although the existing 3.6.x rule base runs withoutmodifications in the upgraded Tivoli Enterprise Console Version 3.9environment, it cannot use any of the new features and functionality.Furthermore, a recompilation of the rule base, due to additions ormodifications, would require that the rule base be upgraded to conform tothe latest specifications. Use the $BINDIR/TME/TEC/wrbupgradecommand to upgrade the 3.6.x rule base.

Install new componentsThe following components are new components since Version 3.6.2 and should beinstalled:

Tivoli Enterprise Console JRESpecial instructions: none.

User interface (UI) serverSpecial instructions: none.

Event console

Special instructions: The event console can be installed in a non-Tivolienvironment or on one or more managed nodes in the Tivoli region.

Once this component is installed, the 3.6.x console (also known as theenterprise client) definitions can be migrated using command wmigcon.This command converts each 3.6.x console, event group and filterdefinitions to the latest definitions and stores the result in the eventdatabase under table TEC_T_CONSOLES and related tables. Any AEFcustomizations are not migrated by the wmigcon command.

If there are only a few consoles to convert, it may be quicker to createthose using the wconsole command.

Review all converted console definitions for completeness once wmigconhas completed the operation. There are known limitations with thewmigcon command.

Note: Once the new event consoles are defined and in use, the 3.6.x eventconsoles become redundant and should be deleted from the Tivoliregion. Do not use 3.6.x event consoles in a Tivoli Enterprise Console3.9 configuration because it causes unpredictable results. Use the$BINDIR/TME/TEC/tec-client3.6-remove.sh command to delete3.6.x event consoles.

Database schema

Special instructions: Although not a component, the 3.6.2 event databasemust be upgraded to 3.9 schema prior to the installation or upgrade of


Tivoli Enterprise Console components. To upgrade the database, see“Upgrading the event database” on page 59.

Sample event informationSpecial instructions: none.

Preparing to install components in interconnected Tivoli regionsFor interconnected Tivoli regions to work with the Tivoli Enterprise Consoleproduct, you must provide a two-way connection between the Tivoli regions. Inthe primary Tivoli region, you must register the resource for the event server(EventServer) with the name registry. Assuming you have two Tivoli regionsnamed A and B, use the following procedure to create this type of configuration:1. Install the event server in Tivoli region B.2. On the Tivoli server of Tivoli region A, register the Tivoli Enterprise Console

resources using the following commands:wregister -i -r EventServer

3. Exchange all resources on Tivoli region A and Tivoli region B.4. Install non-Tivoli event consoles as needed on computers in Tivoli region A to

have event consoles that access the event server in Tivoli region B.

After registering the objects in the primary Tivoli region, you must update theresources either from the Tivoli desktop or with the wupdate command.

For additional information about the wregister command and the wupdatecommand, refer to the Tivoli Management Framework Reference Manual.

Preparing to install components in Tivoli region operating withnon-default port settings

In Windows, when the Tivoli Management Framework is operating with anon-default port, (that is, a port other than 94), you must perform the followingsteps manually before using the installation wizard:1. Open the file %SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd. The

value of the variable o_dispatch is set to 94.2. Change the value of o_dispatch to the Tivoli port value that is being used.

For example, if the Tivoli port being used is 777, change set o_dispatch=94 toset o_dispatch=777

After completing this procedure, you can now use the installation wizard to installthe Tivoli Enterprise Console product.



Chapter 3. Installing, upgrading, and uninstalling using theinstallation wizard

The installation wizard is a program that helps you install the Tivoli EnterpriseConsole product. Specifically, it can do the following things:v Configure the event databasev Install, upgrade, and uninstall Tivoli Enterprise Console components in a Tivoli

and non-Tivoli environment.v Install and upgrade Tivoli NetView components in a Tivoli and non-Tivoli

environment.v Install language packs.

The installation wizard also automatically performs the following as appropriate:v Installs and uninstalls Tivoli Enterprise Console JRE, as appropriate. The Tivoli

Enterprise Console JRE is a requirement for the event server, the UI server, theevent console, and the Adapter Configuration Facility.

v Backs up object database to the backups subdirectory of the Tivoli Databasedirectory

v Stops the event server before upgradingv Sets up Tivoli Enterprise Console roles and resourcesv Starts the event server after installing or upgrading the event serverv Updates the object databasev Starts and stops the WebSphere Application Server

During installation the installation wizard generates two log files and places themin the temporary directory of your system: tec_install.log andtec_install_summary.log. tec_install.log contains a log of the installation sequenceand tec_install_summary.log contains all the installation commands and the resultsof those commands. Refer to these log files after installation for information relatedto any installation problems.

Using the installation wizardBefore you start the installation wizard, ensure that you are running it in thecorrect computer and that you are set up correctly:v To install components in a Tivoli environment, you must be a Tivoli root

Administrator with all available roles, and you must run the installation wizardon a managed node or a Tivoli server. For more information on how to becomea Tivoli root Administrator, see Tivoli Management Framework User’s Guide. Toinstall components in a non-Tivoli environment, you can run the installationwizard on any supported computer.

v To install the NetView server in a non-Tivoli environment, you must be the rootuser. If you want to configure the NetView server for Tivoli Enterprise DataWarehouse integration, the root user must be added to the db2group. For moreinformation on Tivoli Enterprise Data Warehouse integration, see page 40.

v To install the Web console, run the installation wizard on the computer whereyou want to run the Web console and the WebSphere Application Server.

v To configure the event database, run the installation wizard on the RIM host.


Note: During the installation process you are prompted to insert variousinstallation CDs, UNIX users should be prepared to unmount CDs.

To use the installation wizard, complete the following:1. Insert the installation wizard CD.2. Find one of the following files in the CD, and run the appropriate file:

v For a Windows system, tec_install.bat

v For a UNIX system, tec_install.sh

3. Specify a temporary location to copy the installation files to. The installationwizard copies several files from the CD to the temporary directory that youspecify here. After copying the files, the installation wizard stops itself andrestarts from the temporary location.

4. Agree to the required terms of the license agreement. After the installationprocess is completed, the license files are copied to a specific location asexplained in “Locating the license files” on page 43.

5. At this point, you are presented with four choices. If this is a new installationor upgrade from previous supported versions except Version 3.8, selectConfigure the event database. For more information on this procedure, see“Configuring the event database”. If you have already configured thisdatabase, continue to the next step.

6. Select one of the following:v Install components in a Tivoli environment. For information on this

procedure, see “Installing, upgrading, and uninstalling components in aTivoli environment” on page 39

v Install components in a non-Tivoli environment. For information on thisprocedure, see “Installing and upgrading components in a non-Tivolienvironment” on page 40

v Install the Web console component. For information on this procedure, see“Installing and uninstalling the Web console” on page 41

7. Select the components you want to install.8. Answer the questions pertaining to particular components.9. View the summary window to review your choices. After you have approved

your choices, the installation proceeds, during which you are prompted toinsert the CD that contains the installation image of the components youchose to install.

10. When the installation finishes, the results appear for review. After you havefinished reviewing these results, you are returned to the window described instep 6. If needed, install additional components. Otherwise, click Finish.

Configuring the event databaseIf this is a new installation, you must configure the event database before installingthe Tivoli Enterprise Console components. If you are upgrading from previoussupported versions except Version 3.8, you must first upgrade the event database.For Version 3.8 there is no need for upgrading the event database. For moreinformation on configuring the event database, see Chapter 4, “Configuring theevent database”, on page 45.

For a step-by-step example of how to configure an event database using theinstallation wizard, see “Configuring the event database” on page 97.


Installing, upgrading, and uninstalling components in a Tivolienvironment

These are the Tivoli Enterprise Console components that you can install, upgrade,and uninstall in the Tivoli region where the installation wizard is running:v Event serverv UI serverv Event console (Java version)v Sample event informationv Adapter Configuration Facilityv HP OpenView adapterv Tivoli Enterprise Console language pack

These are the Tivoli NetView components that you can install and upgrade in theTivoli region where the installation wizard is running:v NetView serverv Tivoli NetView language pack

Note: In a Tivoli environment, the NetView server can only be installed on AIXand Solaris managed nodes only.

Before upgrading Tivoli Enterprise Console components, you must stop the UIserver, all event consoles, and all adapters. If any Tivoli Enterprise Consoleprocesses are still running, stop them manually.

The wizard performs a discovery of the components in your Tivoli region. Theresults of this discovery appear, and depending on the results, you are presentedwith a list of appropriate choices to install, upgrade, and uninstall components.

After you have selected the type of installation you want, the wizard displays a listof appropriate components. Select the components and the managed nodes foreach component on which you want to install, upgrade, or uninstall. If there isonly one managed node in the system, the installation wizard, by default,automatically selects the only managed node available for installation withoutpresenting you with a list of managed nodes to choose from.

When you install or upgrade the event server, you are given the opportunity todeactivate any of the default active rule sets.

When you are installing components, you can also select the language packs youwant to install. Selected language packs will be installed in the managed nodeswhere Tivoli Enterprise Console components are installed. Language packs can alsobe installed later after the Tivoli Enterprise Console components have beeninstalled.

For a step-by-step example of how to install components in a Tivoli environmentusing the installation wizard, see “Installing components in a Tivoli environment”on page 98.

Chapter 3. Installing, upgrading, and uninstalling using the installation wizard 39

Installing and upgrading components in a non-Tivoli environmentThese are the components that you can install in a non-Tivoli environment:v Event console (non-Tivoli Java version)v NetView server (can be upgraded as well using the installation wizard)v NetView Web console

For a step-by-step example of how to install the NetView server using theinstallation wizard, see “Installing the NetView component” on page 100.

Installing the event consoleWhen installing the event console, you specify the location where you want toinstall the event console.

Installing the NetView serverTo install the NetView server, you must specify a number of installation andconfiguration parameters:

Automatic discovery rangeTo specify the type of automatic network discovery to be performed by theNetView server, which determines how much of the network is discovered,select one of the following ranges for automatic discovery: local subnetonly, backbone-only, or all networks. If you select the local subnet onlyoption, the NetView component discovers the local subnet only. If youselect the backbone-only option, the NetView component discoversconnectors only (primarily routers and switches) and subnetworks. If youselect the all networks option, the NetView component performsunbounded network discovery.

SNMP community namesType up to six community names used for network discovery; if this is notspecified, discovery might be limited if community names other thanpublic are in use because public is the default if no other communitynames are specified.

Event server detailsTo have NetView server forward events to an event server using thenon-Tivoli-based communication method, type the name, port and theoperating system of that event server. Port is used for communication withthe event server. If the port used by the event server has not beencustomized, use the default value (5529 for Windows event server; and 0for a UNIX event server); if it has been customized, use the customizedport values.

IBM Tivoli Monitoring parametersYou can configure NetView server for querying IBM Tivoli Monitoringservers for information that can be used to escalate the severity of eventsrelated to IBM Tivoli Monitoring nodes. To do so, type the information ofthe IBM Tivoli Monitoring server: host name of the Monitoring server aswell as the user ID and password for that server. You can add moreservers by clicking Add.

Tivoli Enterprise Data Warehouse parametersYou can configure the NetView server for integration with the TivoliEnterprise Data Warehouse.


v To do so for a local DB2 server on AIX, type the information for thelocal DB2 server to which the NetView server exports data: name ofdatabase, user, password, and port, which is used for cataloging.

v For all other local DB2 servers, type the information for the local DB2server to which the NetView server exports data: name of database, user,password.

v If the DB2 server is remote, type the remote server’s node name, hostname, port, user, and password. If the DB2 client is on AIX, a local DB2user is also required.

You can choose to create a new database or use the specified existingdatabase.

To upgrade the NetView server, you can specify only the IBM Tivoli Monitoringparameters and Tivoli Enterprise Data Warehouse parameters. To configure theseparameters after installation or upgrade, use the /usr/OV/bin/nvits_config script.For more information on this command, see the IBM Tivoli NetView for UNIXVersion 7.1.4 release notes and IBM Tivoli NetView for Windows Version 7.1.4release notes.

You can also install language packs for the NetView server in a non-Tivolienvironment. When you are installing components, you can also select thelanguage packs you want to install. Language packs can also be installed later afterthe NetView server has been installed.

Installing the NetView Web consoleThe NetView Web console should be installed on the computer containing theevent console (Java version). You must specify the directory where you want toinstall the NetView Web console. The installation wizard attempts to detect theexistence of the event console. If it does not find the event console, you can chooseto install the event console at that time or to specify the directory where the eventconsole is installed.

Installing and uninstalling the Web consoleFor a step-by-step example of how to install components in a non-Tivolienvironment using the installation wizard, see “Installing the Web consolecomponent” on page 99.

Installing the Web console

Installing the WebSphere Application ServerThe Tivoli Enterprise Console Web console requires WebSphere Application Server,Version 5.0 Base Edition. If you have already installed WebSphere ApplicationServer, Version 5.0 Base Edition, specify its location during installation. The Webconsole must be run on a dedicated WebSphere Application Server environment. Ifyou have not already installed the WebSphere Application Server, the installationwizard can help you install this program. The wizard does this by starting theWebSphere Application Server installation program and providing customizeddefault settings. After the WebSphere Application Server has been installed, theinstallation wizard starts the WebSphere Application Server and continues.

Notes:

1. As part of the installation process, the installation wizard prompts you to insertthe WebSphere Application Server installation CD. If you are using Windows,the WebSphere Application Server installation program then starts


automatically. At this point, close the WebSphere Application Server installationprogram, and click OK in the installation wizard. The installation wizard thenstarts the WebSphere Application Server installation program as part of itsprocess. Running the WebSphere Application Server installation programindependently may cause confusion and interfere with proper installation of theWeb console.

2. To improve performance and to avoid any potential problems with theoperation of the Web console, it is recommended that you do not install thesample applications that are shipped with the WebSphere Application Server.

3. If the WebSphere Application Server has already been installed and is operatingin a secure mode, specify this on the installation wizard panel and provide theuser ID and password for the WebSphere Application Server.

For more information on WebSphere Application Server installation, see theWebSphere Application Server installation documentation.

After you complete the previous steps, you must then set up the Web console.

Setting up the Web consoleAs part of installing the Web console, you must set up the Web console so thatoperators can use the Web console to monitor events in the event servers in Tivoliregions.1. To add a Tivoli region to the list of Tivoli regions that Web console can operate

with, click Add.2. Type the host name, port number, user name, and password for the region’s

Tivoli Server. The Web console uses this information to access the eventdatabase.

3. Type the timeout values for the Web console, and click Next.When an operator requests information on events, event summary, and tasks,the Web console stores this information in caches. With these values, youdetermine how long this information remains in the caches before it is deleted.The shorter the timeouts the more up-to-date the information is but the morethe database server and the WebSphere Application Server use resources.

4. Select the managed nodes.The Web console can be configured to connect to any managed node withinthat Tivoli region so that operators defined in that managed node can log onand view events. The installation wizard displays all the managed nodes forthe specified Tivoli server. Select the managed nodes you want the web consoleto connect to for connectivity.

By default, the Web console is not configured to operate in SSL mode. If yourequire SSL for the Web console, you must configure the WebSphere ApplicationServer to activate SSL. For instructions, refer to the WebSphere Application Serverdocumentation.

For more information on adding and configuring regions after installation, see IBMTivoli Enterprise Console User’s Guide.

Uninstalling the Web consoleYou can uninstall the Web console using the installation wizard. During thisprocess, you must specify the location of the WebSphere Application Serverproduct. At the end, the WebSphere Application Server product is stopped andrestarted.


Locating the license filesDuring installation, after you have accepted the terms of the license agreement, theinstallation wizard places the license agreement in one of the following directoriesdepending on what components you have installed. This license agreement isavailable in thirteen languages.

Table 19. Location of the license file

Situation Location of license files

Components are installed or upgraded in aTivoli environment

$BINDIR/TME/TEC/license

The NetView server is installed or upgradedin a non-Tivoli environment

/usr/OV/license

The NetView Web console is installed in anon-Tivoli environment

NetView_Web_console_installation_directory/nvwc/license

The event console is installed in a non-Tivolienvironment

Event_console_installation_directory/tec_console/license

The Web console is installed WebSphere_installation_directory/TEC/license



Chapter 4. Configuring the event database

This chapter describes installing and configuring the event database using thesimple or custom installation method. The custom method allows you to assignvalues for configuration parameters that are set by the installation wizard, whereasthe simple method installs the event database with basic parameters selected bythe installation wizard. The simple installation method can only be used forcreating a new event database. The custom installation methods can be used forcreating, upgrading, and removing the event database.

For both the simple and the custom installation method, the installation wizardprompts you for information specific to the installation of your databaseenvironment. The simple method completes the installation using the basicdatabase criteria you supply and then uses default configuration values for thedatabase configuration parameters to complete the installation process. The custommethod presents additional windows to select options to configure your databasefor optimal performance. The installation wizard creates the event database, tablespaces, tables, and indexes, and database configuration parameters.

Configure an event database using the installation wizard before installing TivoliEnterprise Console components. If you are upgrading from previous supportedversions except Version 3.8, you must first upgrade the event database. For Version3.8, there is no need for upgrading the event database. There are four choicesavailable. All involve SQL scripts, which are used for configuring the eventdatabase:

SimpleThis option generates and runs the SQL scripts using default configurationvalues and can only be used for creating a new event database

Custom-Generate onlyThis option generates the SQL scripts, which can be reviewed andmodified by a database administrator and then can be run later

Custom-Execute onlyThis option runs the previously generated SQL scripts, which may havebeen reviewed and modified by a database administrator

Custom-Generate and executeThis option generates and runs the SQL scripts using customizedconfiguration values

This chapter details the following:v “Planning for configuration” on page 46v “General event database considerations” on page 47v “Sample worksheets for event database installation” on page 50v “Installing the event database using the custom method” on page 58v “Generating and executing scripts” on page 61v “Using the No Change option when generating scripts” on page 62v “Configuration options for improving performance” on page 63v “Enabling language support” on page 75


Planning for configurationUse the following questions to determine the size and location of the database:v How much memory is available to the event database server? Allocating more

physical memory to the event database server improves the performance of theTivoli Enterprise Console.

v How many input/output devices are available to the event database server?Spreading input/output across multiple input/output devices can significantlyimprove the performance of the Tivoli Enterprise Console.

v How large do you need to configure the event database, temporary work area,and transaction logs?

For additional information to consider before running the installation wizard, seethe sample worksheets provided in “Sample worksheets for event databaseinstallation” on page 50.

Note: It is recommended that you contact your database administrator beforemaking changes to your database environment.

General prerequisitesFor all databases, the following prerequisites must be met before you begin usingthe installation wizard:v You have backed up your database server using standard database procedures.v You are performing your installation on a system that meets the hardware and

software requirements, such as using a supported RDBMS on a supportedoperating system, as shown in the IBM Tivoli Enterprise Console Release Notes.

v You have the appropriate version of the Tivoli Management Framework product,and any associated patches, installed. For the most current information, see theTivoli Management Framework Release Notes.

The following items should be considered for all database types before beginningyour event database configuration:v For databases other than the Oracle database, installing, upgrading, or removing

the event database requires that the event database server be stopped andrestarted before your new configuration settings take effect. Ensure that there areno users with active sessions on the same event database server that the eventdatabase is to be installed on. The scripts shut down the event database serveras needed to run the event database configuration scripts. When the databaseclient is installed on the RIM host instead of the database server, you may beprompted to stop or restart the event database server and then click Next tocontinue.

v It is recommended that you check with your database administrator anddatabase vendor documentation if your database environment uses mirroreddatabase devices. You may have the ability to edit the database schema scripts toadd the mirroring capability to the product schema for your site.

v When defining device sizes and directory paths in the installation wizardwindows, ensure that the device size specified is available in the directory pathor raw partition specified for that device and that the permissions are set toallow the directory to be written to by the database server. The devices anddirectory paths specified must be available to the database server computerwhere they will be allocated.

v You must source your database environment to use any of the following optionsoffered by the installation wizard:


– The Simple option– The Custom-Generate and execute option.– The Custom-Execute only option

For more information, see “Sourcing the database environment for theinstallation wizard” on page 54.

Oracle prerequisitesFor an Oracle database, the following prerequisites must be met before using theinstallation wizard:v Because it utilizes an existing instance to run, an Oracle instance must be created

before running the installation wizard.You must create the required Oracle database instance using the UTF-8 characterset in order to support multiple languages. For more information about UTF-8support, see “Enabling language support for Oracle” on page 76.

v If you install the event database from an Oracle client, the client must beconfigured to communicate with the existing Oracle instance. For moreinformation about configuring the Oracle client and the database instance, seethe Oracle 9i Net Service Reference Guide.

General event database considerations

DB2 considerationsWhen the DB2 client is installed on the RIM host, the node to be used by the DB2client to attach or connect to the DB2 server must previously be cataloged andready for use.

DB2 considerations for new installations and upgradesIf you are using a DB2 client connection, you must ensure that there are no activeconnections to the Tivoli Enterprise Console database instance before running thescripts generated by the installation wizard. You must also catalog the DB2 serverin order to upgrade. For additional DB2 information about cataloging the DB2node, see the catalog tcpip node command in the DB2 Universal Database CommandReference.

You can use the following command from the DB2 database server to force activeconnections off before running the generated scripts:dbs2stop force

db2start

Cataloging the DB2 node for a new installationUse the following DB2 command to catalog the DB2 node:db2 catalog tcpip node node_name remote server_name server

instance_port_#

–OR–service_name

Cataloging the DB2 node for an upgradeWhen the DB2 client is installed on the RIM host, the node must be cataloged andthe event database must be cataloged.

Use the following DB2 command to catalog the DB2 database:

Chapter 4. Configuring the event database 47

db2 catalog database tec_database_name as tec_database_alias_name

at node node_name

Changing the size of transaction log files for an upgradeIf your event repository is using circular logging, the total size of the transactionlog files must be sufficient for the upgrade process to complete successfully.

For each table in the event repository, the upgrade process creates a new table inthe event repository that has the new database structure. The entire contents ofeach original table in the event repository are copied from the original table to thenew table in a single database transaction. The more data that is being copied, themore transaction log space is required.

To determine if your event repository is using circular logging, which is thedefault, use the following command:db2 get db cfg for dbname

Where dbname is the name of the event repository database.

If the LOGRETAIN value is set to OFF, your event repository is using circularlogging.

The following configuration parameters configure the total size of the transactionlogs:v LOGFILSIZ, which is number of 4K pages for each log filev LOGPRIMARY, which is the number of primary log files that will be created,

each LOGFILSIZ in sizev LOGSECOND, which is the number of secondary log files that will be created, if

needed, each LOGFILSIZ in size

The amount of space (in bytes) required for log files can range from (logprimary *(logfilsiz + 2) * 4096) + 8192 to ((logprimary + logsecond) * (logfilsiz +2) * 4096) + 8192

To change the log space, complete the following:1. Change the LOGFILSIZ, LOGPRIMARY, and LOGSECOND configuration

parameters using the following command:db2 update db cfg for dbname using parameter newvalue

where dbname is the name of the event repository database, parameter is theconfiguration parameter being set, and newvalue is the new value for theconfiguration parameter.

2. Use the following command to apply the changes made in step 1:db2 force application all

Informix considerationsBecause Informix logical dbspace names are created at the database server level,the names must be unique for a database created on the Informix server. If morethan one event server is installed on the Informix server, you must assign uniquelogical dbspace names for each database.

If you select to move the DBSPACETEMP work area from the rootdbs device to anew dbspace or new dbspaces instead of selecting the No Change button on theDBSPACETEMP window in the installation wizard, the DBSPACETEMP dbspaces


are not removed when the Tivoli Enterprise Console product is removed. This is arecommended permanent change to the DBSPACETEMP dbspaces for your eventdatabase server configuration. If you are not specifying new dbspaces whenreinstalling the event database, select the No Change button on theDBSPACETEMP window.

Note: For Informix, the scripts generated by the installation wizard must be runfrom the Informix database server.

When specifying new dbspaces for DBSPACETEMP from the installation wizardpanels, ensure that you also update your Informix onconfig file with the newdbspace names for the DBSPACETEMP configuration option.

For Informix, when an event database is upgraded to the version 3.9 schema andthen removed with the version 3.9 SQL scripts, the version 3.9 schema is not awareof the previously defined dbspaces. The dbspaces defined for the original eventdatabase (any that existed prior to the version 3.9 upgrade) must be manuallyremoved.

Microsoft SQL Server considerationsThe installation wizard prompts you for the event database server name and theservice name. The service name is mssqlserver for Microsoft SQL Server 7 andMicrosoft SQL Server 2000 with the default server instance. The server name canbe found in the SQL Server Enterprise Manager.

The service name has the following format for a Microsoft SQL Server 2000 namedinstance:mssql$instancename

For additional MS SQL Server considerations, see “Sybase and Microsoft SQLServer considerations” on page 50.

TEMPDB settingsThe original TEMPDB file is deleted when you select the option to alter theTEMPDB settings. When a database client is installed on the RIM host, a messageappears indicating that the TEMPDB file should be deleted on the computer wherethe event server is installed. Deleting the TEMPDB file on this computer ensuresthat all TEMPDB space resides on its own device and does not share the masterdevice.

The installation wizard and the wdbconfig.sh script only stop and restart, orprompt you to stop and restart the event database server if the TEMPDB settingsare altered. The event database server does not need to be stopped and restartedduring the event database installation or upgrade process if you select the NoChange option for the TEMPDB settings.

Oracle considerationsBecause the Oracle database is often installed using the Oracle installation to createthe event database, you must use unique names for all table spaces within thedatabase. If more than one event server is installed on the Oracle server, you mustassign unique table space names for each database

The Install Database Objects and Remove Database Objects options are notavailable for Oracle in the installation wizard. Unlike other operating systems, theOracle database installation uses an existing database instance for event data and


does not change settings in the existing instance. Options for other databases areavailable because they create new databases for the event data.

Installing or removing the Oracle database does not cause the Oracle instance to bestopped and restarted, as with other databases.

Sybase and Microsoft SQL Server considerationsYou can choose to change the TEMPDB settings one time, which moves theTEMPDB database from its default location on the master device to the device andsize specified in the installation wizard panels. If this action has already beeninitiated in your environment by your database administrator or by running theinstallation wizard scripts, click the No Change button on the correspondingwindow to ensure the changes are not attempted again and fail. If the TEMPDBsettings are run more than one time, you receive error messages.

When your event database is newly-created or upgraded to version 3.9, the devicelabeled rest_data is chosen to be the default device. When the event database isremoved, the default device is set to Master for Sybase.

If the TEMPDB database is moved to a new device instead of selecting the NoChange button, it is not changed when the event database is removed. Oncestopped, Sybase or MS SQL Server servers is not able to start again if the TEMPDBdatabase is removed.

For Microsoft SQL Server and Sybase, if the client is installed on the RIM host, youneed to be able to stop and start the event database server when prompted to doso by the running the installation wizard or the wdbconfig.sh script beforecontinuing with the next step.

For Microsoft SQL Server and Sybase, the user login must be unique for eachdatabase installed on the event database server.

Sybase considerationsBecause Sybase logical device names are created at the database server level, thedevice names must be unique for databases created on the Sybase server. If morethan one event server is installed on the Sybase server, unique logical devicenames must be given for each logical device name created for each database.

For Sybase, when an event database is upgraded to the version 3.9 schema andthen removed with the version 3.9 SQL scripts, the version 3.9 schema is not awareof the previously defined devices. The devices defined for the original eventdatabase (any that existed prior to the version 3.9 upgrade) must be manuallyremoved.

Sample worksheets for event database installationUse the sample worksheets in this section to plan your event database installation.You need this information for both simple and custom installations. For a custominstallation, you are offered additional database configuration options specific toyour environment, such as selecting table space size and memory allocations. Theworksheets also ensure that you have the information you need before starting theinstallation wizard.

You should use a different directory for the generated SQL scripts besides thatused for the installation wizard. Using a different directory keeps the files separate


and therefore makes it easier to copy the scripts to another computer if necessary.In addition, you should retain the generated scripts because some can be used toto uninstall the Tivoli Enterprise Console database.

Table 20. Worksheet for DB2

DB2 Sample Worksheet

Directory for generated scripts

RDBMS user ID

Event database name

Is the RIM host a database client or server?

Host name of remote DB2 server if the RIMhost is a database client

Disk space to allocate

Memory to allocate for buffer pools

Directory names containing table spaces,transaction logs, and temporary space

Table 21. Worksheet for Informix

Informix Sample Worksheet


RDBMS user ID

Event database name

Is RIM host database client or server?

Informix server name

Directory names containing dbspaces,physical logs, and temporary space

Table 22. Worksheet for MS SQL Server

Microsoft SQL Server Sample Worksheet


RDBMS user ID

Event database name


System administrator (SA) password

Directory names containing data files andtransaction logs

Table 23. Worksheet for Oracle

Oracle Sample Worksheet


RDBMS user ID

Database session identifier (SID)


Oracle home directory

Oracle SYS password


Table 23. Worksheet for Oracle (continued)

Oracle Sample Worksheet

Directory names containing table spaces

Table 24. Worksheet for Sybase

Sybase Sample Worksheet


RDBMS user ID

Event database name


System administrator (SA) password

Directory names containing data files andtransaction logs

Device IDs in use

Actual number of the first device for theTivoli Enterprise Console event database

Amount of memory to allocate for the eventdatabase

For additional information about the RIM host and RDBMS settings for the RIMhost, see “Choosing the RIM host” on page 18.

Configuring with the installation wizardTo configure the event database, you must use the installation wizard. SeeChapter 3, “Installing, upgrading, and uninstalling using the installation wizard”,on page 37 for information on starting the installation wizard.

The installation wizard should typically be run on the RIM Host. The RIM hosttypically has the database client software installed that the installation programneeds to connect to the RDBMS and to create the event database. Scripts generatedby the installation wizard must also be generated to a directory on the samecomputer with the RIM host

For an Informix database, the installation requires the use of dbaccess, which isgenerally only available on the Informix Server. Therefore, generated scripts shouldbe run on the Informix server, which may or may not be the RIM host. If the RIMhost is on the same computer as the Informix server, the user can perform aSimple or a Custom-Generate and execute installation. Otherwise, the user mustgenerate scripts only, copy the scripts to the Informix server, and run the scripts onthe Informix server. Generated scripts are run using the wdbconfig.sh script, whichis generated with the SQL scripts. For more information on this command, see theIBM Tivoli Enterprise Console Command and Task Reference.

To configure the event database, you must have the authority to do the following:v To run commands in the Tivoli environmentv To create and work with databases

You must have authority to run commands in the Tivoli environment because theinstallation wizard creates the RIM object named tec, which is needed by the


Tivoli Enterprise Console components. In the Custom-Generate only andCustom-Execute only modes, you have the option as to whether the RIM objectshould be created or not. If a RIM object named tec already exists in the systemwhere the installation wizard is run, the installation wizard displays the defaultvalues associated with it.

Note: If you are using Tivoli Management Framework 4.1 in the Windowsenvionment and using Oracle 9i for the event database, you must add thetmersvrd user to the Windows Administrators group before configuring theevent database. The tmersvrd user is created during the installation of TivoliManagement Framework.

In addition, you must have the database authority as listed in the following table:

Table 25. Authorized users by database

Database Users who have required databaseauthority

DB2 Any user that has SYSADM or SYSCTRLauthority to the DB2 instance. On UNIX, thisis the instance owner, which is db2inst1 bydefault. Any user can be added to db2groupto be authorized to work on the database. Inthe default DB2 installation on Windows,users in the Administrators group (the DBAcan change which user group has SYSADMand SYSCTRL by changing the DB2SYSADM_GROUP and SYSCTRL_GROUPconfiguration parameters).

Oracle Any user that can access the Oracle homedirectory. The database installationautomatically sets the ORACLE_HOME andPATH environment variables so that theOracle SQL*Plus program can be run

Informix On UNIX, any user that is in the informixgroup, typically informix or root. On aWindows operating system, users in theInformix-Admin group.

SQL Server Any user that has access to the SQL Serverosql program. The osql program must be inthe user’s PATH. Users in the Administratorsgroups are good candidates. The installationscripts use the sa user ID to perform someinstallation tasks. The user running theinstallation wizard therefore must know thesa password.


Table 25. Authorized users by database (continued)

Database Users who have required databaseauthority

Sybase The user must be the user ID that was usedto install the database server.Note: For example, configuring the databaseas the root user causes the device to beowned by the root user and prevents theserver from initializing the database.

The installation wizard uses the isqlprogram to run SQL scripts.

For some installation tasks, the installationwizard uses the sa user ID. The userrunning the installation wizard thereforemust know the sa password.

Sourcing the database environment for the installation wizardIn many cases, the environment in which the installation wizard is run must besourced so that the wizard can execute product-specific database commands andSQL scripts. Before running the installation wizard, you must source your databaseenvironment so that the installation wizard can configure the event database.v For a DB2 database on Windows, the environment is available to the installation

wizard and does not require being sourced. The installation wizard uses the DB2command db2cmd to initialize the DB2 environment.

v For a DB2 database on UNIX, you must run the db2profile script in the sameUNIX shell prior to starting the installation wizard.

v For Informix on Windows, the Informix product provides a shortcut on theWindows Start Menu for each Informix server. This shortcut opens up acommand environment in which the Informix environment is properly setup.The installation wizard should be run from this command environment.

v For an Oracle database on any operating system, SQL *Plus must be available.The Oracle environment does not need to be sourced. The generated scripts setthe ORACLE_HOME environment variable and add ORACLE_HOME/bin to thePATH.

Examining error logsThe installation wizard generates SQL scripts and shell scripts required to create,upgrade, and remove the event database. A log file is automatically created in thesame directory you designated for the generated scripts. If the generated eventdatabase scripts are run from the installation wizard, the log file also contains theoutput from running the scripts. You can examine the log file to view results.

The log file is named DbInstalltimestamp.log, as shown in the following example.The timestamp variable is replaced by the current system time when the log isgenerated.DbInstall2002-07-12-57_03PM.log

You can also check for replies from the event database server to each configurationstatement in the SQL scripts, as well as any error messages. Error messages can beseen in a file named similarly to the log file (with an .err ending) found in thesame generated script directory. Examine both the log file and the error log for


complete output from running the database scripts. For example, a file calledDbInstall2002-07-12-57_03PM.err is also created that may contain error installationinformation.

Note: No error logs are generated if the wdbdconfig.sh script is used to performan install, upgrade, or remove function. Instead the script output is returnedto the command line from which the script was run and is visible as thescript runs.

Tuning the event databaseThe event database configuration enables you to tune the database as follows:v Physically separate the database tables and indexes across various devices so

that more than one input/output device is servicing read and write (R/W)requests.

v Separate data tables from their corresponding index tables.v Use buffer pools and prefetching techniques effectively to ensure that a specified

row remains in memory instead of on disk.v Tune vendor-specific database configuration parameters.v Avoid disk contention by moving transaction logs and temporary work areas to

their own disk device.

Understanding RIM object creationTivoli Enterprise Console components communicate with the database using theRDBMS Interface module (RIM). The RIM is an integral part of the TivoliFramework. Whenever an application that utilizes the RIM needs to connect to adatabase, the RIM starts the RIM agent process. A RIM agent process uses theRDBMS client libraries to communicate with the database and issue SQLstatements.

A RIM object is a Tivoli environment object that contains essential informationabout a specific database, such as the database name, database user ID.

A RIM host is a managed node where the RIM object is created. The RIM agentprocesses run on the RIM host. The database client libraries that are required bythe RIM agents must be installed on the RIM host. The RIM host uses a RIM objectto determine the database to communicate with.

The installation wizard creates a RIM object named tec, which contains the detailsof connecting to the event database. The RIM object values are detailed in thefollowing tables. The Tivoli Enterprise Console components locate the tec RIMobject to obtain details to connect to the event database. The RIM object named tecmust exist on the Tivoli region where the event server is to be installed. If youneed to create a RIM object manually on the Tivoli region where the event server isto be installed, see “Creating a RIM object” on page 90.

The following tables list the mandatory database information needed forconfiguring the event database. This information is also stored in the RIM object.

DB2Table 26. DB2 values

Database Vendor DB2


Table 26. DB2 values (continued)

Database Home Full path to the directory where the RDBMS server orclient software is installed. Equates to the value in the$DB2DIR environment variable.

Database Name The DB2 database alias name that event database uses.

Database User ID The DB2 instance owner. The DB2 instance owner nameand the user name should be the same, and equate to, thevalue in the $DB2INSTANCE environment variable. ForRIM, this should also be the login name of the instanceowner. The default on UNIX is db2inst1 and, forWindows, the default is DB2.

Database Password The password for the database user.

Database Server ID The value in the DB2COMM environment variable.Generally, this is tcpip.

Instance Home (required forDB2 databases only)

Home directory where the instance was created.

For UNIX, it is the value of the $INSTHOME environmentvariable. For Windows, it is usually the same value as theDatabase Home option.

InformixTable 27. Informix values

Database Vendor Informix

Database Home Full path to the directory where the Informix CLI isinstalled. Equates to the value in the $INFORMIXDIRenvironment variable.

Database Name For UNIX, the name of the data source defined by the linedatabase=name in the .odbc.ini file.

For Windows, the name of the System DSN that wascreated using the ODBC Data Source Administratorapplication in the Windows Control Panel. Thisinformation is stored in the Windows registry.

Database User ID Must be informix or an ID that exists as a valid login onthe Informix database server.


Database Server ID The name of the Informix server defined in the$INFORMIXDIR/etc/sqlhosts file. Equates to the value inthe $INFORMIXSERVER environment variable.

Instance Name Not required, DB2 databases only.

Microsoft SQL ServerTable 28. MS SQL Server values

Database Vendor Microsoft SQL Server

Database Home The directory where the Microsoft SQL Server is installed.

Database Name The name of the database that the application uses.

Database User ID The RDBMS user that owns the application database. Thedefault is tec.


Table 28. MS SQL Server values (continued)


Database Server ID The name of the host running MS SQL Server.


OracleWhen installing the event server component from the Install Options dialog, enterthe following database values:

Table 29. Oracle values

Database Vendor Oracle

Database Home Equates to the value in the $ORACLE_HOMEenvironment variable.




Database Server ID The name of the Oracle listener service in thetnsnames.ora file. Equates to the value in the$TWO_TASK environment variable for a client or$ORACLE_SID on the database server or client.


SybaseTable 30. Sybase values

Database Vendor Sybase

Database Home The directory that contains the interfaces file. Equates tothe $SYBASE environment variable.




Database Server ID The name of the Sybase server. Equates to the value in the$DSQUERY environment variable. It is also the servername specified in the SQL.INI file on Windows or in theUNIX interfaces file.


Ensuring that RIM can connect to the Informix server eventdatabase

The following must be done to ensure RIM can connect to the Informix serverevent database. This procedure is for configuring a UNIX Informix client.1. Copy $INFORMIXDIR/etc/odbc.ini to $INFORMIXDIR/.odbc.ini on the

Informix client.2. Copy $INFORMIXDIR/etc/odbcinst.ini to $INFORMIXDIR/.odbcinst.ini on the

Informix client.


3. Modify .odbc.ini and .odbcinst.ini to point to the correct $INFORMIXDIR.4. Add the Tivoli Enterprise Console datasource to the .odbc.ini file:

Example of .odbc.ini file:[ODBC Data Sources]tec=INFORMIX 3.81 32-BIT

[tec]Driver=/opt/informix/lib/cli/iclit09b.soDescription=INFORMIX 3.81 32-BITDatabase=tecLogonID=informixpwd=informix Servername=myserver

Note: The ODBC data source name must be the same as the name of the Informixdatabase that contains the Tivoli Enterprise Console tables. Otherwise,commands such as wtdbclear do not work properly.

For Windows, you add the data source for the Informix client by clicking Start —>Control Panel —> Administrative Tools —> Data Sources (ODBC)

Installing the event database using the custom methodThe following sections guide you through the database installation using thecustom method. Selecting the custom installation gives you more configurationoptions to optimize database performance, such as maximizing memory usage andmanaging the physical layout of data on the disk. For additional information aboutconfiguration options, you can also use the field-level help available in each of thewindows in the installation wizard.

Installing the event databaseChoose to install the event database when creating it for the first time, or after ithas been completely removed. With the exception of Oracle, installing the eventdatabase for the first time, or installing the event database after removal, requiresthat the database server be stopped and restarted to use the new configurationsettings.

The Informix installation procedure must be performed on the Informix server. Youcan use the installation wizard to install if the RIM host and the Informix serverreside on the same computer. If they do not, you must install the event databaseusing the wdbconfig.sh script.

Note: During installation of the event database, the installation wizard createsscripts that are needed in order for the installation wizard to be able touninstall the event database. These scripts are stored in the directory$TEMP\tecdb on Windows, or /tmp/tecdb on UNIX. If these scripts aredeleted, you cannot uninstall the event database using the installationwizard.

The Informix installation procedure must be performed on the Informix server. Youcan use the installation wizard to install if the RIM host and the Informix serverreside on the same computer. If they do not, you must install the event databaseusing the wdbconfig.sh script.

Use the following steps to install the event database using the wdbconfig.sh script:


1. Run the installation wizard on the RIM host using the Generate Only option.2. Copy the generated scripts to the Informix server.3. Run the wdbconfig.sh script in the generated scripts directory on the Informix

server.

For more information about the wdbconfig.sh script, see the IBM Tivoli EnterpriseConsole Command and Task Reference.

Installing only the event database objectsChoose to install only the event database objects when you want to install only theevent database tables, indexes, views; and, for Sybase and MS SQL Server 7,triggers. This is only done after you have removed the event database objects andthe event database itself still exists.

Note: Oracle does not have the option to install only the event database objects

You can choose to install only the event database objects if you have removed onlythe database objects. You can select this option in the installation wizard withoutthe usual requirement of stopping and restarting the database server instance ordatabase server. Choose this option if you want to start with new database objectsand have the event database remain in place.

Running the wdbconfig.sh scriptThe wdbconfig.sh script is generated by the installation wizard and runs the SQLscripts generated by the installation wizard and determines the database type fromthe SQL scripts located in the generated script directory. The wdbconfig.sh scriptmust only be run from the directory where the scripts were generated on the RIMhost.

See the IBM Tivoli Enterprise Console Command and Task Reference for moreinformation about the wdbconfig.sh script.

For DB2 and Informix databases, you must be logged in as the same user as theRIM user ID specified for the event database RIM object. This user should havedatabase administrator (DBA) access with authority to create, modify, and deletedatabase objects. The user must also have a login ID as a Tivoli managementenvironment administrator.

Ensure the following prerequisites are met before running the wdbconfig.sh scriptin an Informix environment:v You have generated the event database installation scripts, as outlined in

“Generate scripts only” on page 62 and copied them to your Informix server.v You run the script directly on the Informix server instead of the RIM host when

the Informix server is not the same machine as the RIM host.v You are able to run scripts in a non-Tivoli environment.

For Informix only, if the Informix database server is installed on a non-Tivolicomputer, the wdbconfig.sh script can be run on that computer.

Upgrading the event databaseYou can use the installation wizard to upgrade the event database from a version3.6.2 or 3.7.1 configuration to a version 3.9 configuration. The upgrade scriptsgenerated by running the installation wizard upgrade your event data.

Note: You must backup your event database prior to performing an upgrade.


For each event database type, when an upgrade is performed, the prior data deviceused by the Tivoli Enterprise Console product remains in place. This is becausemost databases require a database system area and this already resides on thisdevice and cannot be moved. Also, other application data may reside on thisdevice and are not removed. After changing configuration options, you shouldcheck triggers or views associated with the application tables to ensure that theyare intact. The event database tables are renamed in this process, which may causetriggers or views that are based on these names to be dropped by the databaseserver. If you do not want to leave the original devices in place, you can select toremove and reinstall the event database. If you want to completely remove yourevent database devices, you must completely remove the Tivoli Enterprise Consoleevent database and the devices created for the database. You must then install theversion 3.9 database schema as a new database installation.

Consider the following items before upgrading your event database:v Before you upgrade, run the wtdbclear command to purge events that do not

need to be migrated. For more information on this command, see the IBM TivoliEnterprise Console Command and Task Reference

v With the exception of Oracle, upgrading the event database requires that allusers are logged off because the event database server processes are stopped.The server must be restarted for changes to take effect.For Oracle, you are not required to stop and restart the database server;however, you must ensure that any users that may be accessing the databasebeing upgraded are logged off.For all event database upgrades, you must specify the upgraded database size tobe at least as large as the current event database size. You can use thewtdbspace command to see the current database size. For more informationabout using the wtdbspace command, see the IBM Tivoli Enterprise ConsoleCommand and Task Reference.

v It is recommended that you increase your database transaction logs beforeupgrading to enable the insertion of the Tivoli Enterprise Console records fromthe original tables into the new tables. You can alternately export the data fromthe original tables and then import the data to the new tables.

v For recovery purposes, back up or export your event database to save yourevent data.

v If other Tivoli applications previously used database objects from the originaldatabase schema, you may need to reinstall the database objects, such as triggersor views, because they may no longer exist after the upgrade.

v When using a DB2 client connection, see “DB2 considerations” on page 47 beforerunning the installation wizard.

Note: Tivoli Enterprise Console Version 3.8 databases do not need to be upgradedfor use with Tivoli Enterprise Console Version 3.9.

Uninstalling the event databaseChoosing to remove the event database completely removes the event database aswell as all Tivoli Enterprise Console event database objects. Completely removingthe event database does not undo the configuration settings that have beenchanged at the database server or instance level, such as database serverconfiguration options.


Notes:

1. With the exception of Oracle and MS SQL Server, removing the event databaserequires that the database server be stopped and restarted to reset deviceconfiguration settings.

2. Uninstalling the event database using the installation wizard requires scriptsthat were generated during database installation. These scripts are stored in thedirectory $TEMP\tecdb on Windows, or /tmp/tecdb on UNIX. If these scriptsdo not exist, attempting to uninstall the event database does result in an error.To uninstall the event database without using the installation wizard, use thewdbconfig.sh script. See the IBM Tivoli Enterprise Console Command and TaskReference for more information about the wdbconfig.sh script.

Uninstalling only the event database objectsThe event database objects include tables, indexes, and views. For Sybase and MSSQL Server, the event database objects also include MS SQL Server 7 and Sybasetriggers.

Note: Removing the event database objects deletes all events in the database.

Choose to remove only the event database objects when you want to remove onlythe event database tables, indexes and views and, for Sybase and MS SQL Server 7,triggers. After removing the event database objects, you can choose to reinstall thedatabase objects at a later time if you want to start with empty database tables.

Note: Because the Oracle database already exists before the event database isinstalled, Oracle does not have the option to remove the event databaseobjects. The Oracle installation and uninstallation of the event databasealready installed or removes just the event database objects, leaving thedatabase in place.

Uninstalling the event database in an Informix environmentThe Informix uninstall procedure must be performed on the Informix server. Youcan use the installation wizard to uninstall if the RIM host and the Informix serverreside on the same computer. If they do not, you must uninstall the event databaseusing the wdbconfig.sh script.

To uninstall the event database using the wdbconfig.sh script, use the scriptsgenerated when the database was created or upgraded, and run the wdbconfig.shscript in the generated scripts directory on the Informix server. Run the installationwizard on the RIM host using the Generate Only option.

For more information about the wdbconfig.sh script, see the IBM Tivoli EnterpriseConsole Command and Task Reference.

Generating and executing scriptsThe scripts generated by the installation wizard must be run by starting theinstallation wizard or by running the wdbconfig.sh script from the command line.With the exception of Informix, the recommended method of executing thegenerated scripts is by using the installation wizard. When running thewdbconfig.sh script from the command line, you must run it from the samedirectory as the generated scripts. The directory must have write permissionbecause the generated scripts create temporary files in this directory.

When running the installation wizard, you can select one of the following options:v “Generate scripts only” on page 62


v “Generate and execute scripts”v “Execute scripts only”

Generate scripts onlyThe Generate Scripts Only option is only available if you selected the custom eventdatabase installation method. The generated scripts must be written to a directoryon the RIM host or copied to the same directory on the RIM host computer.

Choose this option if you will later run the scripts from the command line usingthe wdbconfig.sh script.

If your database administrator plans to make additional modifications to the SQLscripts before they are run, choose to only generate the scripts.

You can run the scripts from a client or server on all databases other thanInformix. For Informix, select to generate scripts only if the database server is on adifferent computer than the RIM host. The generated script directory must exist onthe Informix database server and have write permissions because the generatedscripts create temporary files in this directory. You can alternatively choose to storethe files in a different directory on the RIM host or Informix database server. Youcan then edit the generated scripts and change the SCRIPTDIR variable to thedirectory on the RIM host or Informix database server computer that the scriptsare run from.

To run the generated scripts on a computer other than the RIM host, copy all ofthe files from the directory where the scripts were generated to the directory onthe computer where the scripts are run. You can choose a different directory if youchange the SCRIPTDIR variable in each script that begins with the namedbConfigure. Run the wdbconfig.sh script with parameters that enable you toinstall, upgrade, or remove.

See “Running the wdbconfig.sh script” on page 59 and the IBM Tivoli EnterpriseConsole Command and Task Reference for more information about the wdbconfig.shscript.

Generate and execute scriptsChoose this option to generate and run the scripts immediately after specifyingoptions in the installation wizard. If you selected the simple database configurationmethod, this option is chosen automatically.

Execute scripts onlyChoose this option if you previously generated the scripts from the installationwizard and are now ready to run them. You can select this option when usingeither the simple or the custom database installation method. For the simpleinstallation option, once you have generated and run the scripts to create orupgrade your database, you can then use the generated scripts with this option torun the scripts as needed.

Using the No Change option when generating scriptsA No Change button that allows you to generate the scripts without changing thepreviously selected parameters is available on some windows in the installationwizard.


Notes:

1. You should only select this configuration change one time. If you perform anew installation or an upgrade for a second time selecting the No Changeoption, run-time errors occur and may affect your event database.For example, in a first-time installation of a Sybase event database, you canchoose to change the TEMPDB configuration settings. Since this is a one-timeconfiguration change, the next time a complete reinstallation of the eventdatabase is performed, the installation wizard should be used to generate thescripts a second time. For the second generation of the scripts, select the NoChange option on the TEMPDB settings window in the installation wizard.

2. Do not select the No Change option for DB2 databases.

Configuration options for improving performanceThe following sections describe configuration options that can be changed for yourdatabase environment that may further improve performance. If you have sharedmultiprocessor (SMP) environment, consult your database manuals forconfiguration options that enhance the database server performance when runningmultiple processors.

The installation wizard sets the initial values and you can edit each option byfollowing the procedures outlined in your database vendor documentation.

DB2 configuration optionsFor recommended DB2 configuration options, see the help in the installationwizard dialogs.

Informix configuration optionsThe following table lists additional options to improve event databaseperformance. If you choose to make the changes in the onconfig configuration file,the Informix universal server needs to be restarted. You can edit the onconfig filewhile the Informix server is online or offline and the new values are in place whenrestarted. The event database scripts stops and restarts the Informix databaseserver to make the binary large object (BLOB) space available when you install orupgrade your event database. You can choose to run the SQL scripts after anydevices are prepared and the onconfig file has been updated with the newparameters. Then when the SQL scripts are run, the Informix database server isstopped and restarted and the new configuration parameters are put into effect.

Note: When editing the onconfig file, parameter names are in uppercase and, ifthe parameter value is a string, the value is case-sensitive. You must also useblank spaces to separate the parameter name from the parameter value andthe optional comment following the value.


Table 31. Informix configuration options

Configuration Option Description

SHMADD Specifies the size of the memory segment to be dynamicallyadded to the virtual portion of the shared memory of theInformix universal server.

Recommended settings:

Physical memory SHMADD value

< 256MB 8192 KB

> 256MB and < 512MB 16384 KB

> 512MB 32768 KB

onconfig file setting recommendation: SHMADD 32768

SHMTOTAL Specifies the maximum shared memory size for the Informixdatabase server. A value of zero (0) allows the sharedmemory to continue to take segments from the operatingsystem as needed. The value should be set to 0 unless youneed to restrict the access of the event database server to allthe memory because of other applications running on thesame computer.

onconfig file setting recommendation: SHMTOTAL 0

SHMVIRTSIZE Specifies the initial size of the virtual part of the Informixdatabase server shared memory. The virtual memory canhave memory segments added dynamically but if the size isnot the size needed for daily operating requirements,processes may take longer while waiting on memorysegments to be added. Use the larger of 8000 KB or thenumber of all network connection types specified in theInformix sqlhosts file multiplied by 350.

onconfig file setting recommendation: SHMVIRTSIZE 8000

RESIDENT Specifies that the resident part of the shared memory ofInformix cannot be swapped by the operating system if theoperating supports forced residency of memory segments. Bynot allowing the resident portion to be swapped out, the datacontained in the event database remains in memory insteadof swapped out to disk and performance benefits. If theoperating system does not have the forced residency option,the Informix Universal server issues an error message andthen ignores the parameter. The RESIDENT value should beset to 1.

onconfig file setting recommendation: RESIDENT 1

DBSPACETEMP Specifies a list of dbspace names used for the temporarywork area for the event database server. If you entered one ormore dbspaces for the DBSPACETEMP window in theinstallation wizard, then this list of dbspaces must be enteredin the onconfig file for this parameter. The list should beentered as a string of values less than 255 characters, with thedbspaces separated by a colon or comma with no blankspaces.

onconfig file setting recommendation: DBSPACETEMP

temp_dbspace1,temp_dbspace2,temp_dbspace3


Table 31. Informix configuration options (continued)


MAX_PDQPRIORITY Specifies the percent of database resources a processperforming parallel database queries is allowed to take fromthe percent it requested to use. The database resources usedin parallel are memory, disk I/O, and scan threads that scantables for rows requested.

onconfig file setting recommendation: MAX_PDQPRIORITY50

DS_MAX_QUERIES Specifies the number of decision support type queries thatcan run simultaneously. Decision support queries are large,complex queries that scan the event database tables andrequire a large amount of database resources.

onconfig file setting recommendation: DS_MAX_QUERIES 10

DS_MAX_SCANS Specifies the limit to the number of parallel database queryscan threads a decision support query can run concurrently.Decision support queries are large, complex queries that scanevent database tables and require a large amount of databaseresources.

onconfig file setting recommendation: DS_MAX_ SCANS 20

DS_TOTAL_MEMORY Specifies the total percent of the Informix universal servermemory that should be used for parallel database queries. Setthis value between 50% and 80% for applications that have alarge number of decision support type queries.

onconfig file setting recommendation: DS_ TOTAL_MEMORY50

OPTCOMPIND Helps the Informix database optimizer choose the best dataaccess method.

onconfig file setting recommendation: OPTCOMPIND 1

LOGFILES Specifies the number of logical logs.

onconfig file setting recommendation: LOGFILES 5

LOGSIZE Specifies the logical log size.

onconfig file setting recommendation: LOGSIZE 10000

LOGSMAX Specifies the maximum number of transaction logs.

onconfig file setting recommendation: LOGSMAX 7

See also “Informix logical logs” on page 67.

PHYSDBS The name of the physical log dbspace.

onconfig file setting recommendation: PHYSDBSphys_log_dbspace




PHYSFILE Specifies the location of the physical log. To minimizecontention to the root dbspace, move the physical logs out ofthe root dbspace, where they are created by default. Due tothe value of the critical data that it contains, create thephysical log on its own I/O device and mirror it. Changethese configuration variables to their new settings and thenchange the Informix universal server to quiet mode with theInformix onmode –ky command and then run the onparamscommand to set up the new physical log.

onconfig file setting recommendation: PHYSDBSphys_log_dbspace

LOCKS Sets the number of locks available on the event databaseserver for all users. Each lock takes up 44 bytes of residentmemory.

onconfig file setting recommendation: LOCKS 10000

DEADLOCK_TIMEOUT Specifies the number of seconds a thread waits to acquire alock. This parameter is used by distributed queries accessinga remote server.

onconfig file setting recommendation:DEADLOCK_TIMEOUT 60

BUFFERS Specifies the amount of physical memory allocated to thebuffers. Calculate all other shared memory parameters afterdeciding the space required for the buffers parameter. If aftersetting the values for the other shared memory parametersthere is memory left to be allocated, assign more memory tothe buffers using a maximum of 25%. You can find howmany buffers to allocate by taking 25% of the physicalmemory available and dividing the number by the Informixpage size setting for the operating system. You can also runthe oncheck –pr command to acquire the number of buffersto set.

onconfig file setting recommendation: BUFFERS 200

LOGBUFF Defines the size of the logical-log buffers in shared memory.

onconfig file setting recommendation: LOGBUFF 64

PHYSBUFF Defines the size of the two physical log buffers inshared-memory. Choose a size that is evenly divisible by thepage size. You can run the oncheck –pr command to get thepage size.

onconfig file setting recommendation: PHYSBUFF 16

CKPTINTVL Defines the frequency, in number of seconds, at which theevent database server checks to see if a checkpoint should betaken.

onconfig file setting recommendation: CKPTINTVL 120

CLEANERS Specifies the number of page cleaners to allocate. You shoulduse one page cleaner per disk drive allocated to the eventdatabase server. Cleaners write changed pages to disk.Additional cleaners has no effect on shared memory settings.

onconfig file setting recommendation: CLEANERS 7




LRUS Defines the number of least-recently-used (LRU) queues inshared memory the buffer pool used to track the oldestpages. They can then be replaced, leaving pages that weremore recently used in memory. Set this value to 4 for auniprocessor computer. A formula is provided in yourInformix database documentation for calculating values formultiprocessor computers. Monitor the LRU queues with theonstat –R command and make adjustments as needed.

onconfig file setting recommendation: LRUS 4

LRU_MAX_DIRTY Specifies that, when an LRU queue has the specifiedpercentage of its page buffers modified, the cleaners shouldwrite the changes to disk to ensure that the queue does notfill up.

onconfig file setting recommendation: LRU_MAX_DIRTY 70

NOAGE Informational parameter preventing an operating system fromlowering the run-time priority of a processes as it runs forlonger periods of time. You can check to see if your operatingsystem lowers the priority of processes as they accumulateprocessing time and, if it does, set this parameter to 1.

onconfig file setting recommendation: NOAGE 1

RA_PAGES Defines the number of disk pages to attempt to read aheadduring sequential scans of either data or index tables. Thisfeature can greatly speed up database processing by alreadyhaving the required data in memory before it is needed bythe application.

onconfig file setting recommendation: RA_PAGES 10

RA_THRESHOLD Defines the number of disk pages remaining unprocessed inmemory before the event database server is signaled to readmore pages into memory.

onconfig file setting recommendation: RA_ THRESHOLD 5

SINGLE_CPU_VP Defines the number of virtual processors the event databaseserver is running on. Set the value to 1 if the event databaseserver runs on one virtual processor, as different code pathsare followed with this setting that avoid the changes that areset when running on a multiprocessor computer.

onconfig file setting recommendation: SINGLE_CPU_VP 1

Informix logical logsThere are three configuration parameters that you can set in the onconfigconfiguration file for Informix logical logs. Evaluate the number and size of yourlogical log configuration parameters to ensure they are adequate for the peakprocessing periods experienced by your event database server.

The following three configuration parameters are available in the onconfigconfiguration file for Informix logical logs:


Table 32. Informix logical log configuration parameters

Configuration Parameter Definition

LOGFILES Specifies the total number of logical logs

LOGSIZE Specifies the size of the logical logs

LOGSMAX Specifies the maximum number of logical logs

For more information about Informix logical log configuration parameters, see “Informixconfiguration options” on page 63

The size and number of the logical logs should be large enough to ensure sufficientlogical log space. If the size of the logical logs is set too small, user activity isblocked until space is available. Update the configuration file with new values forthe configuration parameters as needed. You must have a minimum number ofthree logical logs with a minimum size of 200 KB.

Logical logs are initialized in the root dbspace by default. To minimize contention,move the logical logs and physical log out of the root dbspace to their ownseparate dbspaces on separate I/O devices. You can create two dbspaces onseparate I/O devices for the logical logs and split them between the two dbspaces.For optimal performance, the new dbspaces should not contain other data.

To create new logical logs on separate dbspaces, create your dbspace afterinitializing the device, or cooked file, as outlined in the Informix Universal ServerAdministration Guide. Raw devices are faster than cooked files because the operatingsystem’s input/output subsystem does not interact with the input/output to theraw device.

Note: A cooked file refers to a specific type of UNIX file. Although Informixmanages the contents of cooked files, the UNIX operating system managesall I/O to cooked files. Unlike raw disk space, the logically contiguousblocks of a cooked file may not be physically contiguous.

See the Informix Administrator’s Guide for information about how to move thelogical logs out of the root dbspace and create them in the new dbspaces.

Microsoft SQL Server configuration optionsThis section describes Microsoft SQL Server database and server configurationoptions that can be set in the installation wizard or manually changed by adatabase administrator. Only a database administrator should change these settingsas Microsoft SQL Server frequently monitors the state of memory allocations andother configuration settings and then dynamically reconfigures them.

Refer to your Microsoft SQL Server database manuals for information aboutconfiguration options that best fit your environment.

The following parameters can be activated for the event database:

Table 33. MS SQL Server database parameters


ANSI null default Default parameter, set to on for the event database.

trunc. log on chkpt Parameter set to on for the event database


The default device is changed to the device that is specified in the windows of theinstallation wizard as rest_data.

Triggers are created to support Microsoft SQL Server versions that do not have ONDELETE CASCADE functionality.

The following event database server configuration options can be modified:

Table 34. Microsoft SQL Server database server configuration options


Minimum memory per query Value is set to 4096.

Maximum async IO Value set to 100 for MS SQL Server 7.Note: This value is set for Microsoft SQL Server 7 only, asMS SQL Server 2000 does not offer the maximum asyncinput/output configuration option.

Oracle configuration optionsTo minimize disk contention when using an Oracle database, you can physicallyseparate disk space for the following:v Database system table spacev Temporary table spacev Rollback segmentsv Application datav Application indexes

The Oracle System Global Area (SGA) is the memory area allocated at startup byOracle that contains memory structures to store data and control information. TheSGA should always be in non-paged, non-swapped memory.

The following table defines the Oracle memory structure types:

Table 35. Oracle memory structure types

Type Definition

Shared Pool Resides in the Oracle Instance SGA and contains the Shared SQLareas and the Data Dictionary.

Database Buffer Cache The buffer cache holds copies of data blocks read from disk

Redo Log Buffer A buffer in the SGA that contains a history of committedchanges.

The values defined for the following parameters have the largest impact on theSGA size:v LARGE_POOL_SIZEv SHARED_POOL_SIZEv DB_CACHE_SIZEv LOG_BUFFER

For additional detailed information about Oracle database performance, see theOracle Database Performance Guide and Reference.


Tuning Oracle rollback segmentsRollback segments store the changes made by transactions and should be properlyallocated for optimal database performance. The size and number of the rollbacksegments are application dependant and a size can be determined by monitoringthe log writer (LGWR) trace file and the database’s ALERT file to see if the LGWRprocess frequently waits to write to the redo log. The size multiplied by thenumber of redo logs must be large enough to hold the maximum number ofchanges that are recorded for the largest transaction’s changes before they arecommitted.

Note: When tuning Oracle rollback segments, the database must be in manual undomanagement mode. You cannot tune the rollback segments if the database isin automatic mode because Oracle handles the operation of the rollbacksegments internally.

There is always one rollback segment called SYSTEM in the SYSTEM table space.At least one extra rollback segment is needed if multiple table spaces are defined.Defining multiple rollback segments improves event database performance bydistributing rollback segment usage and contention across multiple rollbacksegments.

In general, rollback segments should be sized according to the size of transactionsmade by the application. Short transactions tend to have better performance withmany smaller rollback segments while longer transactions tend to have improvedperformance with larger rollback segments. For improved rollback I/Operformance, each rollback segment for an instance should have 10 – 20 equallysized extents. Create a table space to contain all rollback segments except the twoSYSTEM rollback segments. The benefits of this design are that the rollbacksegments are not stored with other types of data and data access contention iseliminated. Also, the table space can be kept online at all times to ensure thatrollback segments do not fragment the data table spaces by frequently allocatingand deallocating extents.

Oracle redo log buffer and files tuningThe Oracle redo log buffer and the online redo log files contain the history ofcommitted changes made to the event database. Their purpose is to protect theevent database in the event of an instance failure. The Oracle redo log buffer is abuffer in the SGA and is written to in a circular fashion. The records are thenwritten to the redo log files on disk, also written to in circular fashion. Theyshould be multiplexed, meaning each should have a backup copy to ensure backupsof each log. The multiplexed redo log files are called redo log file groups. The logand its backup copy are members of the log file group and should be placed ondistinct I/O devices to avoid a single point of failure for the Oracle database. Atleast two redo logs or log groups are required to be defined and they should beplaced on the fastest, least busy, I/O devices.

Oracle configuration optionsThe following table defines some Oracle configuration options that can enhancerun-time performance:

Follow the procedure outlined in your Oracle database vendor documentation toimplement these and other beneficial configuration options.


Table 36. Oracle configuration options


DB_BLOCK_BUFFERS This parameter defines the number ofbuffers in the System Global Area (SGA)buffer cache. The buffer cache holdscopies of data blocks read from disk.Setting this value affects theperformance of the buffer cache.Defining this setting correctly promotesthe chances of getting requested datafrom memory instead of disk, greatlyimproving run-time performance. Youshould estimate the number of datablocks the Tivoli Enterprise Consoleapplication accesses most often for thetables, indexes, and rollback segmentsand provide an estimation of theminimum number of buffers thatshould be defined to the buffer cache.Usually 1000 — 2000 is a goodminimum value for the number ofbuffers to define. The buffer cacheshould equal the memory left aftertuning the SQL and PL/SQL areas andthe shared pool.

DB_BLOCK_MULTIBLOCK_READ_COUNT This parameter specifies the maximumnumber of blocks read during asequential table scan for one I/Ooperation. It can help to minimize thenumber of I/O’s required during tablescans.

DB_CACHE_SIZE This parameter specifies the size of thedefault buffer pool for buffers using theblock size specified by theDB_BLOCK_SIZE parameter.

LARGE_POOL_SIZE Allocate a large pool so Oracle has aseparate pool to request large memoryallocations and lessen the impact on theSGA as a whole. You should also set theLARGE_POOL_MIN_ALLOCparameter.

PARALLEL_AUTOMATIC_TUNING Setting this parameter allows Oracle toautomatically determine the requireddefault parameters for parallelexecution. Since parallel execution usesonly the large pool, if thelarge_pool_size is unset it determines adefault size for it. To enable thisparameter you must also define thetarget tables as PARALLEL.


Table 36. Oracle configuration options (continued)


SHARED_POOL_SIZE The shared pool resides in the OracleInstance SGA and contains the SharedSQL areas and the Data Dictionary. TheShared SQL area contains theinformation required to run single SQLstatements. The Data Dictionarycontains the Oracle server’s user names,privileges and roles, the names anddefinitions of database objects, integrityconstraints, database object spaceallocations, auditing information, storedprocedures, and triggers.

SORT_AREA_SIZE When large sorting functions occurregularly, this parameter should beincreased from its default value. Settingthis value appropriately can increase thenumber of sorting procedures that canbe carried out completely in memoryand can speed up those sorting thatcannot be carried out completely inmemory.

SORT_DIRECT_WRITES Set this value to AUTO. When it is setto auto and the sort_area_size is morethan 10 times the buffer size, thisparameter can cause the buffer cache tobe bypassed and potentially improvesorts by a factor of 3.

SORT_AREA_RETAINED_SIZE A large sort_area_size value should beoffset with a minimalsort_area_retained_size value to allowthe sort memory to be released before auser’s session ends. If memory is notreleased until you disconnects fromOracle, a large sort work area couldcause problems instead of performancegains.

LOG_BUFFER An application that generates many logscommonly has a size of 3 — 5 MB forthe log buffer size. Check the redobuffer allocation retries statistic in theV$SYSSTAT view to see if this value ishigh. A high value indicates that the logbuffer size should be increased. Ensurethe logs are on high performance I/Odevices with low I/O contention rates.

DB_WRITER_PROCESSES This parameter specifies the startupnumber of database writer processes foran instance. It is helpful to set this valuehigher for applications, such as theTivoli Enterprise Console product, thatrequire frequent and heavy updates tothe database


Table 36. Oracle configuration options (continued)


ALWAYS_ANTI_JOIN Set this parameter to the value HASHto enable the NOT IN operator to beevaluated in parallel using a parallelhash anti-join. Otherwise, it uses asequential correlated subquery.

LOCK_SGA This parameter locks the SGA memoryallocation into physical memory whenset to true. This avoids the eventdatabase server memory buffers frombeing swapped in and out to disk. Theparameter is ignored if the operatingsystem operating system this is set ondoes not support it. You can also chooseto lock only certain SGA areas intophysical memory with theLOCK_SGA_AREAS configurationoption.

OPTIMIZER_MODE This parameter sets the access methodused for the instance when retrievingrows from event database tables. Whenset to choose, the optimizer chooses thebest method between a rule-basedapproach and a cost-based approach.The cost-based approach involvesanalyzing the statistics, if they areupdated. Since the event database mayhave the wdbmaint.sh statistics andwdbmaint.sh reorg run on a regularbasis, the choose mode should bebeneficial for the Tivoli EnterpriseConsole application.

OPTIMIZER_INDEX_COST_ADJ This parameter allows you to add aweighting factor to cost-based approachwhen indexes are being evaluatedversus table scans. Using this parameterfor the Tivoli Enterprise Consoleapplication would be beneficial to giveadvantage to the indexes weightingsinstead of using table scans.

Sybase configuration optionsSybase offers many configuration options to tune the performance of the eventdatabase.

The following table lists configuration options that are automatically configured forthe event database by the SQL scripts:


Table 37. Sybase configuration options


total memory Total memory is configured from user input values anddefines the total memory, in 2K units, allocated from theoperating system available memory to the event databaseserver. Higher values allow more event database serverallocations to internal buffers and caches, therefore reducingthe number of I/Os to disk and can improve performance.Note: The event database server must be able to acquire thefull amount of total memory defined at startup or it may notstart. If the server does not start, set the value in theconfiguration file for the server to a lower value and restartthe server.

number of index trips The number of index trips is set to 1 in SQL scripts. Thisparameter defines the number of times a changed index pageis skipped when considering which pages to swap, and inwhat order.

procedure cache percent Procedure cache percent is set to 25%. This number specifiesthe percent of memory allocated to the procedure cache. Thispercent is derived from the memory remaining after theAdaptive Server takes the memory needed for locks, userconnections, and the server code itself. The remainingmemory is then used by the data cache. The procedure cacheis used when running stored procedures and compilingqueries.

cis cursor rows CIS cursor rows is set to 100. This is the number of rowsretrieved with open cursor and cursor fetch operations.

number of devices Number of devices is set to 25. This sets the number ofdevices that can be defined with disk init. The initial settingsfor the device numbers are 0 — 9. The event databaseconfigures up to 11 additional devices so that a new value of25 is set. Change this value higher if a setting of 25 does notallow 11 new devices to be added.

number of large I/Obuffers

Number of large I/O devices is set to 12. This sets thenumber of 16K buffers available for large I/O utilities such asload database, create database, and alter database.

number of locks Number of locks is set to 10000. This sets the number of locksavailable on the event database server for all users.

deadlock checking period Deadlock checking period is set to 2 seconds, or 2000milliseconds. Setting a higher value frees processor cycles forapplications that do not often deadlock.

lock hash table size Lock hash table size is set to 4096 bytes. This number definesthe number of bytes in the lock hash table that are allocatedto hold the number of locks currently in use.

lock schema Lock schema is set to data rows. This setting defines thedefault locking schema and changes it to row-level locking.

row lock promotion HWM Row lock promotion HWM is set to 8000. This numberdefines the top threshold of locks that can be acquired duringa single scan of a table or index before the server escalatesfrom row-level locking to table-level locking schema.

max SQL text monitored Max SQL text monitored is set to 1024 bytes. This valuedefines the amount of memory per user connection set asideto save shared SQL text.


The following parameters are activated for the event database only:

Table 38. Sybase parameters activated for event database only

Parameter Description

selectinto/bulkcopy/pllsort

The select into/bulkcopy/pllsort parameter is set to ON for theevent database and the TEMPDB database.

trunc. log on chkpt The trunc. log on chkpt parameter is set to ON for the eventdatabase.

allow nulls by default The allow nulls by default parameter is set to ON for theevent database.

Enabling language supportThe Tivoli Enterprise Console product supports the processing of event data thatoriginates from a wide variety of code sets. This is achieved by converting allevent data to the UTF-8 code set when the event is created. After the conversion,the event data remains in UTF-8 format throughout the remaining processes, withthe exception of storage of the data in the database. The data is stored in RDBMSformat. The code set is most commonly the code set of the operating system thatthe RDBMS is running on.

Enabling language support is different for each database. The installation wizarddoes not directly create databases that support UTF-8, but generates scripts thatmanipulate the table spaces that support UTF-8 encoding. See the followingsections for considerations when enabling language support for your databasetype.

Enabling language support for DB2For DB2 support of UTF-8 encoding, a set of parameters is required when thedatabase is created. The USING CODESET UTF-8 TERRITORY parameter isadded to create commands in order for a DB2 database to support event datareceived from heterogeneous code sets.

Select the appropriate two-letter territory identifier in the pull-down menu byinteracting with the installation wizard. The event database created from theinstallation wizard supports the UTF-8 data selected.

For more information about enabling language support for a DB2 database, see theIBM DB2 Universal Database Administration Guide: Planning.

Enabling support for GB18030 character setTo enable support for the 4–byte GB18030 Chinese character set, complete thefollowing:1. Run odadmin environ get > temporary_file.2. Add the following to the file (set LANG, LC, ALL to your locale):

LANG=Zh_CN.GB18030LC_ALL-Zh_CN.GB18030DB2CODEPAGE=1208

3. Run obadmin environ set > temporary_file.4. Run obadmin reexec.


Enabling language support for Microsoft SQL Server, Sybase,and Informix

If event data has been generated from a variety of code sets, it may not be possibleto correctly store data that originated from one code set in a database that supportsa different code set. For this reason, the event-related tables in the event databasesupport UTF-8 by default where possible. Since database systems have varyingsupport for internationalized data, support for this option varies among vendors.See your database vendor’s documentation for procedures specific to yourdatabase.

Note: Microsoft SQL Server, Sybase, and Informix are not affected by thisconfiguration change because they do not support storing data in UTF-8format. Oracle and DB2 databases are affected, as they both support storingUTF-8 data.

Enabling language support for OracleOracle has provisions for defining code set storage when the database is createdusing the NATIONAL CHARACTER SET parameter. The parameter must be setto UTF-8 when creating the database to support processing of event data in aheterogeneous code set environment.

Note: The installation wizard does not directly create databases for Oracle, butgenerates scripts that manipulate table spaces. The responsibility for creatingthe database that supports UTF-8 encoding lies with the databaseadministrator that created the event database.

Adjusting the Tivoli server environment to incorporate the propersettings for UTF8 codingTivoli Enterprise Console 3.9 uses UTF8 encoding for data exchanged with theOracle server. The Tivoli server environment must be adjusted to incorporate theproper Oracle settings for UTF8 encoding. Complete the following instructions onthe Tivoli server by a user with permissions to change the Tivoli environmentsettings:1. Source the Tivoli environment, using one of the following methods:

v UNIX: from the command line, run the following script:/etc/Tivoli/setup_env.sh.

v Windows: from the command line, run the following script:%SystemRoot%\WINNT\system32\drivers\etc\Tivoli\setup_env.cmd

2. Run odadmin environ get > tempfile to get the Tivoli environment settings toa file.

3. Edit tempfile to incorporate the following parameter:NLS_LANG=language_territory.AL32UTF8

where language and territory mean the local language and territory for yourOracle client. See the Oracle8i National Language Support Guide or the Oracle9iDatabase Globalization Support Guide to choose the appropriate settings for thesetwo parameters. For instance, for US English, the proper setting would beAMERICAN_AMERICA.AL32UTF8, whereas for Japanese, the proper setting would beJAPANESE_JAPAN.AL32UTF8.

4. Run odadmin environ set < tempfile to import the new Tivoli settings.5. Restart the Tivoli server with the odadmin reexec all command.


Note that on UNIX computers, the absence of the LANG setting in tempfile maycause the odadmin environ set command to fail. See the Tivoli Enterprise InstallationGuide for information on the proper values for this setting.



Chapter 5. Installing, upgrading, and uninstalling using theTivoli Management Framework tools

To successfully install the Tivoli Enterprise Console product for the first time, youmust complete the following tasks:1. Select the managed node for the RIM host.2. Verify the appropriate version of the Tivoli Management Framework product.3. Back up your Tivoli object databases for the affected computers before and after

each product installation.4. Install and configure the RDBMS for the event database, ensuring that the

server or a client resides on the RIM host.5. Select an installation method for installing the Tivoli Enterprise Console

components. You can use one, or a combination of available methods.6. Install the Tivoli Enterprise Console components.

Note: To install, upgrade, or uninstall components in a Tivoli environment, youmust be a Tivoli root Administrator with all available roles. For moreinformation on how to become a Tivoli root Administrator, see the TivoliManagement Framework User’s Guide.

Before you begin

Backing up object databasesBefore installing, upgrading, or uninstalling any Tivoli Enterprise Consolecomponents, you should back up the Tivoli object databases for all affectedcomputers in your Tivoli region. This backup enables you to return to a knownworking state. Having a backup is useful if you encounter problems whileinstalling the Tivoli Enterprise Console product.

From the Tivoli desktop, select Desktop —> Backup to perform a backup of theobject database for the Tivoli region server and managed nodes. You can also usethe wbkupdb command.

For example, to back up the object database for all managed nodes in a Tivoliregion, to the user-defined file /usr/backups/TMR1.bk, run the followingcommand:wbkupdb -d /usr/backups/TMR1.bk

For more information on this command, see the Tivoli Management FrameworkReference Manual.

Stopping the event serverTo upgrade the event server you must stop the event server before upgrading.

To stop the event server, right-click the Event Server icon on the Tivoli desktop,and click Shut Down.

You can also stop the event server manually using the wstopesvr command.


Installing the Tivoli Enterprise Console componentsBefore you install any Tivoli Enterprise Console components, you must configurethe event database. For more information on configuring the event database, seeChapter 4, “Configuring the event database”, on page 45.

Selecting an installation methodYou can use one of the procedures provided in the following sections to install thecomponents of the Tivoli Enterprise Console product:v “Installing components using the Tivoli desktop” on page 81v “Installing components using the command line” on page 82v “Installing components using the Tivoli Software Installation Service” on page 82

For more information on how to use the Framework tools to install Tivolicomponents, see the Tivoli Management Framework Reference Manual.

Installing componentsIndex (.IND) File Name

To install or upgrade Tivoli Enterprise Console components from thecommand line, you need the index file name for each component. Indexfile names for installation are different from those used for upgrading.Index files are ASCII files containing the component-specific instructionsfor each installation image. Index files specify the registered product tagfor a product component, dependency statements, and the informationrequired to install that component on each of its supported operatingsystems.

Registered Product TagTo uninstall Tivoli Enterprise Console components from the command line,you need the registered product tag for each component. The registeredproduct tag is the name assigned to the component contained in aninstallation image and is the first value on each line of the componentindex file.

Required componentTo install certain Tivoli Enterprise Console components on a managednode, you must install this specified component beforehand on thatmanaged node or the installation fails.

The following table shows the components, the registered product tags, theinstallation index file names, the upgrade index file names, and the requiredcomponent for the components.

Table 39. Product tags and file names for Tivoli Enterprise Console components

Component Name anddescription

RegisteredProduct Tag

Installation IndexFile Name

Upgrade IndexFile Name

Requiredcomponent

TivoliEnterpriseConsole JRE

Tivoli EnterpriseConsole JRE 3.9

TEC39_JRE TECJRE.IND none none

Eventserver

Tivoli EnterpriseConsole Server 3.9 .

TEC_SERVER SERVER.IND SERVER_U.IND Tivoli EnterpriseConsole JRE

UI server Tivoli EnterpriseConsole UserInterface Server 3.9

TEC_UI_SRVR UI_SRVR.IND UI_SVR_U.IND Tivoli EnterpriseConsole JRE


Table 39. Product tags and file names for Tivoli Enterprise Console components (continued)

Component Name anddescription

RegisteredProduct Tag

Installation IndexFile Name

Upgrade IndexFile Name

Requiredcomponent

Eventconsole

Tivoli EnterpriseConsole Console 3.9

TEC_JCONSOLE CONSOLE.IND CONSOL_U.IND Tivoli EnterpriseConsole JRE

AdapterConfigurat-ion Facility

Tivoli EnterpriseConsole AdapterConfigurationFacility 3.9

ACF ACF.IND ACF_UPG.IND Tivoli EnterpriseConsole JRE

HPOpenViewAdapters

Tivoli EnterpriseConsole HPOpenView Adapter3.9

HPOV HPOV.IND HPOV_UPG.IND none

Sampleeventinformation

Tivoli EnterpriseConsole SampleEvent Information3.9

TEC_EVTHELP EVTHELP.IND EVTHLP_U.IND none

EventIntegrationFacility

Event IntegrationFacility is no longersupported as aninstallablecomponent. Thiscomponent can onlybe uninstalled.

EIF none none none

NetViewserver

Tivoli NetViewserver 7.1.4

none NVSERVFR.IND NVSERVUP.IND none (see thefollowing note)

Notes:

1. Before you install event server, UI server, event console, and the AdapterConfiguration Facility on a managed node , you must install Tivoli EnterpriseConsole JRE on that managed node or the installation fails.

2. Before you install the NetView server, you must install Tivoli NetViewFramework Patch — 7.1 (index file name: NVTMP31)

For information about installing adapters, see the IBM Tivoli Enterprise ConsoleAdapters Guide.

Installing components using the Tivoli desktopComplete the following steps to install Tivoli Enterprise Console components fromthe Tivoli desktop provided with the Tivoli Management Framework productservices:1. Click Desktop —> Install —> Install Product.2. Click Select Media.3. Select the location where the Tivoli Enterprise Console media is located (for

example, the path where the installation image is located).4. Click Set Media & Close. A list of Tivoli Enterprise Console components

appears.5. Click the components you want to install.

Chapter 5. Installing, upgrading, and uninstalling using the Tivoli Management Framework tools 81

Note: Before you install the event server, the UI server, the event console, andthe Adapter Configuration Facility on a managed node, you must installTivoli Enterprise Console JRE on that managed node or the installationwill fail.

6. Click the managed nodes where you want to install the components.7. Click Install & Close.

Installing components using the command lineYou can also install Tivoli Enterprise Console components from the command lineusing the winstall command.

ProcedureTo install components from the command line, use all necessary parameters:winstall -c /cdmount -i COMPONENT node

where:

-c /cdmountSpecifies the path to the installation image.

COMPONENTSpecifies the product index file for the component you want to install. Usethe following index file names for the following components:

Note: Before you install the event server, the UI server, the event console,and the Adapter Configuration Facility on a managed node, youmust install Tivoli Enterprise Console JRE on that managed node orthe installation will fail.

Table 40. Index file names for installing components

Component Index file name Required component

Tivoli Enterprise Console JRE TECJRE.IND none

Event server SERVER.IND Tivoli Enterprise Console JRE

User interface server UI_SRVR.IND Tivoli Enterprise Console JRE

Event console CONSOLE.IND Tivoli Enterprise Console JRE

Adapter ConfigurationFacility

ACF.IND Tivoli Enterprise Console JRE

HP OpenView adapter HPOV.IND none

Sample event information EVTHELP.IND none

NetView server NVSERVFR.IND none

node Indicates that the component is to be installed on this managed node.

ExampleFor example, to install the Tivoli Enterprise Console JRE and then the event serveron the managed node acadia type the following:winstall -c /cdmount -i TECJRE acadiawinstall -c /cdmount -i SERVER acadia

Installing components using the Tivoli Software InstallationService

You can install Tivoli Enterprise Console components using the Tivoli SoftwareInstallation Service provided by the Tivoli Management Framework product


services. By using the Software Installation Service to install components, you caninstall all required components in less time than using either the Tivoli desktop orinstalling from the command line.

Before installing Tivoli Enterprise Console components, the Software InstallationService product performs prerequisite checking to ensure that the component caninstall successfully. The Software Installation Service product can therefore reducethe number of installation failures.

Before you beginBefore you can install components using the Software Installation Service, youmust import the appropriate installation images from the product CD images intothe Install Repository. When using the Software Installation Service product, youshould import only the images associated with operating system type used withinyour Tivoli environment. By importing only the needed operating system types,the time required to import the images is reduced and disk space is saved. You canimport images into the Install Repository by the using the wimport command orthe Tivoli Software Installation Service console.

See the Tivoli Enterprise Installation Guide for procedures used to import images tothe Install Repository of the Software Installation Service. For detailed informationabout using the wimport command, see the Tivoli Management Framework ReferenceManual.

Importing imagesTo import images into the Install Repository from the Software Installation Serviceconsole, you must start the Software Installation Service console from the Tivolidesktop.

The following table provides variable data you need to use when installing TivoliEnterprise Console products using the dialogs provided with the Tivoli SoftwareInstallation Service.

Table 41. Software Installation Service GUI labels

Software Installation Service GUI Label Tivoli Enterprise Console Variable

Select Product Import CD Images

Locate CD images Use the file browser to navigate to thedirectory containing the index files for theappropriate components.

Index files have an .IND extension. A tablecontaining the index file name for eachTivoli Enterprise Console can be found in“Installing components” on page 80.

Install Repository - Import Product Select the appropriate components from theAvailable Products list.

Select interps Clear the operating system types that youdo not need.

Install Repository - Select Product Select the newly imported Tivoli EnterpriseConsole components to be installed.

Select Machine Select the appropriate computer in theMachine Name column.

See the Tivoli Enterprise Installation Guide for procedures used to install Tivoliproducts using the Tivoli Software Installation Service.


Note: Before you install the event server, the UI server, the event console, and theAdapter Configuration Facility on a managed node, you must install TivoliEnterprise Console JRE on that managed node or the installation will fail.

Upgrading the Tivoli Enterprise Console componentsWhen you upgrade components of the Tivoli Enterprise Console product from aprevious release, you install the upgrade image for that component. You canupgrade these components using either the Software Installation Service, the Tivolidesktop, or the command line.

Note: Upgrading from 3.6.2 requires special procedures. See “Preparing to upgradefrom Version 3.6.2” on page 33 for more information.

Before you begin upgrading componentsBefore you upgrade any Tivoli Enterprise Console components, you must stop theevent server, UI server, all event consoles, and all adapters. If any Tivoli EnterpriseConsole processes are still running, stop them manually.

If you are upgrading from any previous supported version except Version 3.8, youmust also upgrade the event database. For more information on configuring theevent database, see Chapter 4, “Configuring the event database”, on page 45.

Upgrading to Tivoli Enterprise Console, Version 3.9 is done on a per-Tivoli regionbasis. You must perform the upgrade from the Tivoli server in each Tivoli regionyou want to upgrade.

Note: Before you upgrade the event server, the UI server, the event console, andthe Adapter Configuration Facility on a managed node, you must installTivoli Enterprise Console JRE on that managed node or the upgrade fails.For information on how to install this component, see “Installingcomponents” on page 80.

Upgrading from the Tivoli desktopComplete the following steps to upgrade Tivoli Enterprise Console componentsfrom the Tivoli desktop provided with the Tivoli Management Framework productservices:1. Click Desktop —> Install —>Install Patch.2. Click Select Media.3. Select the location where the Tivoli Enterprise Console media is located (for

example, the path where the upgrade image is located).4. Click Set Media & Close. A list of components that are available for upgrading

appears.5. Select the components you want to upgrade.6. Select the managed nodes where you want to upgrade the components.7. Click Install & Close.

Upgrading from the command lineYou can also upgrade Tivoli Enterprise Console components from the commandline using the wpatch command.


ProcedureTo install components from the command line, type the following:wpatch -c /cdmount -i COMPONENT node

where:

-c /cdmountSpecifies the path to the upgrade image.

COMPONENTSpecifies the product index file for the component you want to install. Usethe following index file names for the following components:

Table 42. Index file names for upgrading components

Component Index file name Component that must beinstalled first

Event server SERVER_U Tivoli Enterprise Console JRE

User interface server UI_SVR_U Tivoli Enterprise Console JRE

Event console CONSOL_U Tivoli Enterprise Console JRE

Adapter ConfigurationFacility

ACF_UPG Tivoli Enterprise Console JRE

HP OpenView adapter HPOV_UPG none

Sample event information EVTHLP_U none

NetView server NVSERVUP.IND none

node Indicates that the component is to be upgraded on this managed node.

ExampleFor example, to install the Tivoli Enterprise Console JRE and then upgrade theevent server on the managed node acadia type the following:winstall -c /cdmount -i TECJRE acadiawpatch -c /cdmount -i SERVER_U acadia

Upgrading using the Software Installation ServiceYou can upgrade any Tivoli product or Tivoli Enterprise Console component usingthe Tivoli Software Installation Service. Use the installation procedures for newcomponents in “Importing images” on page 83, as the Software Installation Servicedoes not differentiate between installation and upgrade images. See the TivoliEnterprise Installation Guide for procedures used to install the Software InstallationService client before you begin. You must first import the upgrade images into theInstall Repository and select which computers are to be upgraded with whichcomponents.

Uninstalling the Tivoli Enterprise Console components from thecommand line

To uninstall the Tivoli Enterprise Console product from a managed node or froman entire Tivoli region, use the wuninst command. You cannot uninstall TivoliEnterprise Console components from the Tivoli desktop or by using the SoftwareInstallation Service.

To view the wuninst usage statement used for a specific Tivoli Enterprise Consolecomponent, enter the following command:


wuninst COMPONENT

where:

COMPONENTis the registered product tag for that component.

You can view the registered product tags for the installed components using thewuninst -list command.

Note: Before you uninstall Tivoli Enterprise Console JRE from a managed node,you must first uninstall the event server, the UI server, the event console,and the Adapter Configuration Facility from that managed node or theuninstallation fails.

ProcedureTo uninstall the component from the command line, use the following commandformat:wuninst COMPONENT node -rmfiles [-all]

where:

COMPONENTSpecifies the product tag for the component you want to uninstall. Use thefollowing keywords for the following components:

Table 43. Index file names for uninstalling components

Component Tag

Tivoli Enterprise Console JRE TEC39_JRE

Event server TEC_SERVER

User interface server TEC_UI_SRVR

Event console TEC_JCONSOLE

Adapter Configuration Facility ACF

HP OpenView adapter HPOV

Sample event information TEC_EVTHELP

Event Integration Facility EIF

node Indicates that the component is to be uninstalled on this managed node. Ifthis managed node is a Tivoli server, the component is removed from theentire Tivoli region except for Adapter Configuration Facility and HPOpenView components. If you want to remove the Adapter ConfigurationFacility and HP OpenView components from the Tivoli region, you mustuse the [-all] option. You must uninstall Adapter Configuration Facilityfrom the managed nodes first before uninstalling it from the Tivoli server.

ExampleFor example, to uninstall the event server from the managed node acadia, type thefollowing:wuninst TEC_SERVER acadia -rmfiles

As another example, to uninstall the Adapter Configuration Facility from the Tivoliregion where acadia is the Tivoli server, type the following:wuninst ACF acadia -rmfiles -all


Postinstallation tasks

Setting up Tivoli roles and resources in the Tivoli desktop1. From the Tivoli desktop, double-click the Administrators icon.2. Right-click the Root_TMRServerName-region icon (where TMRServerName is

the name of the Tivoli server) and click Edit TMR Roles.3. Move all roles from Available Roles to Current Roles.4. Click Change & Close.5. Right-click the Root_TMRServerName-region icon and click Edit Resource

Roles.6. For each resource, select and move all roles from Available Roles to Current

Roles. Each time you move roles, click Change, otherwise your change is notsaved. Click Close after you move all the roles for each resource.

7. Right-click the TMRServerName-region icon and click Managed Resources.8. Select and move all resources from Available Resources to Current

Resources.9. Click Set & Close.

10. Exit the Tivoli desktop.

Starting the event serverAfter you have installed or upgraded the event server, you must start the eventserver. To start the event server, right-click the Event Server icon on the Tivolidesktop and click Start-up.

You can also start the event server manually using the wstartesvr command.

Updating the object databaseAfter installing, upgrading, or uninstalling components you must update the objectdatabase. To update the object database use the wchkdb –u command

The wchkdb command verifies and repairs problems in the Tivoli database. Thiscommand does not affect any system files; it only modifies resources within theTivoli environment.

The –u option updates the database, fixing any discrepancies found in the Tivoliresource database.

Configuring default event groups and consolesIn most situations, the user interface server configures default event groups andconsoles automatically during installation. On the the AIX operating system, youmust run the wcrtteccfg command on the system where the user interface server isinstalled.

To configure default event groups and consoles manually, use the followingcommand format:wcrtteccfg hostname user password [operator]

where:

hostnameSpecifies the host where the UI server is installed.


[operator]Optionally designates an operator as the owner of the console. Thisoperator must be a Tivoli root Administrator and must not own any otherconsoles. If an operator is not specified, the current user is automaticallydesignated as the owner of the console.

user Specifies the user ID of the system.

passwordSpecifies the password of the user.

For more information on wcrtteccfg, see IBM Tivoli Enterprise Console Command andTask Reference.

Note: If the automatic configuration fails, ensure that you have properauthorization, and configure the defaults manually.

Deactivating default rule setsWhen you install or upgrade the event server, the following rule sets in the defaultrule base are activated by default:v maintenance_mode

v netview

v ebusiness

v heartbeat

v cleanup

The dependency rule set is also active by default, but its activity is linked to theebusiness rule set and can only be changed by changing the activity of theebusiness rule set. In other words, when you deactivate the ebusiness rule set,you also deactivate the dependency rule set.

To deactivate any of these rule sets, use the wrb_default_rb command. For moreinformation, see IBM Tivoli Enterprise Console Rule Set Reference.

To deactivate the rule sets of default rule base, use the following command format:wrb_default_rb -inactivate rulesets

where:

rulesetsSpecifies the names of the rule sets to be deactivated. If you want todeactivate more than one rule set, insert blank spaces between the names.

For example, to deactivate the netview and heartbeat rule sets, type the following:wrb_default_rb -inactivate netview heartbeat


Chapter 6. Troubleshooting common installation problems

Avoiding common problemsv To avoid causing the installation process to fail on the UNIX systems, you must

install the utilities compress/uncompress before installing Tivoli EnterpriseConsole.

v If you are using a DB2 database as the event database, you must name the DB2user the same as the DB2 instance name.

Note: In UNIX, the DB2 user name is the same as the instance name by default.However, in Windows you must ensure that a user with the same nameas the instance name exists.

v Ensure that you have started your RDBMS server.v Ensure that you have set the database environment for use with the installation

wizard.v When you are installing in a Tivoli environment, ensure that you are a Tivoli

root Administrator with all available roles.v If you are using Tivoli Management Framework 4.1 in the Windows

environment and using Oracle 9i for the event database, ensure that you haveadded the tmersvrd user to the Windows Administrators group beforeconfiguring the event database. The tmersvrd user is created during theinstallation of Tivoli Management Framework. The RIM named tec does notwork without this setup in the environment.

v In Windows, if the user Everyone does not have permission to read, write andmodify the %DBDIR%/tmp Tivoli directory, the installation of the event serverfails. Ensure that Full Control permission is available for the user Everyone forthe %DBDIR%/tmp directory. Restoring Tivoli directories from an archive filecould cause incorrect file permissions to be set for the Tivoli directories.

Working with the RIM objectDuring installation, the installation wizard creates a RIM object named tec.However, if you need to change that RIM object, here are the procedures.

When a Tivoli Management Framework product uses a RIM object, you canperform several actions with the RIM object. These actions are as follows:v Obtain information about the RIM objectv Modify the RIM objectv Delete the RIM objectv Test RIM connectivity

Obtaining information about RIM objectsTo list all RIM objects in your Tivoli environment, enter the following command onthe command line:wlookup -ar RIM

To display configuration information for a specific RIM object, enter the followingcommand on the command line:wgetrim RIM_object_name


Modifying RIM objectsYou can use the wsetrim command to modify attributes for a RIM object. With thiscommand, you cannot change the following:v The database vendor associated with the RIM objectv The computer hosting the RIM objectv The RIM password

To change the database vendor or the computer hosting the RIM object, you mustdelete and re-create the RIM object using the wdel command and the wcrtrimcommand, respectively. To change the RIM password, you must use thewsetrimpw command.

For details about the wsetrim, wdel, wcrtrim, and wsetrimpw commands, refer tothe Tivoli Management Framework Reference Manual.

Deleting a RIM objectWhen you need to delete a RIM object, use the wdel command. The basic syntaxfor this command is as follows:wdel @RIM:RIM_object_name

For details about using the wdel command, refer to the Tivoli ManagementFramework Reference Manual.

Creating a RIM objectWhen you need to create a RIM object, use the wcrtrim command.

For details about using the wcrtrim command, refer to the Tivoli ManagementFramework Reference Manual.

Testing RIM connectivityThe RIM object relies on the underlying database client to connect to the databaseserver. The database client must be able to connect to the database server for theRIM object to communicate properly.

After the event repository is created for your database, perform the followingprocedure to verify RIM connectivity:1. Test connectivity with the database server using the native database client.

When you test client connectivity, you should use the same name andpassword that the RIM object uses. For information about obtaining the RIMconfiguration information, refer to “Obtaining information about RIM objects”on page 89.

The following table summarizes the native database clients for each supporteddatabase.

Table 44. Supported native database clients

Database Database Interactive SQL Access

DB2 db2

Informix dbaccess

Microsoft SQL Server isql

Oracle sqlplus

Sybase isql


2. Test connectivity through the RIM object using the following wrimtestcommand:wrimtest -l RIM_object_name

3. If you see a Session opened Enter option message, you have successfullyconnected to the database server. Enter x to select the exit option and exit.

For additional information about the wrimtest command, refer to the IBM TivoliEnterprise Console Command and Task Reference. (RIM tracing is not helpful forconnection problems because a connection to the database server must exist forRIM to show tracing.)

Starting the event console as a background processIn AIX 4.3.3 with maintenance level 10, Launching Event Console as a backgroundprocess using ’tec_console &’ results in an error. To successfully launch the eventconsole as a background process, follow the steps:1. Run tec_console.2. Press Ctrl+z.3. Run bg.

Error messages

stty:tcgetattr: a specified file does not support iotcl systemcall

Problem: The message ″stty:tcgetattr: A specified file does not support iotcl systemcall″ appears multiple times during component installation

Cause: This occurs because there are stty settings in root’s .kshrc file. The .kshrc isrun when any child shell process is spawned, and stty settings should not be runon child shell processes. AIX 3.x ignored (or did not report errors for) these sttycommands in the .kshrc, but this is not true for AIX 4.x, which reports the aboveerror.

Solution: Move any stty commands from the .kshrc to a file that is run only onlogin sessions (not child shells) such as the .profile.

FRWTT0003E An instance named ″TEC39_JRE″ of resource″Uninstall″ was not found.

If you are uninstalling the Tivoli Enterprise Console components using theinstallation wizard and receive the following error message, ignore this errormessage. The error occurs when installation wizard attempts to remove the TivoliEnterprise Console JRE component from a managed node in which this componenthas been already uninstalled:FRWTT0003E An instance named "TEC39_JRE" of resource "Uninstall" was not found.Not an Uninstallable Application:TEC39_JRE

Chapter 6. Troubleshooting common installation problems 91

Restoring a database with a functional object dispatcherThe wbkupdb command not only backs up but also restores Tivoli databases. Youcan provide a list of managed node names as options to the wbkupdb command.The following command example restores a single managed node, fuji. The backupfile used to restore the managed node is /usr/backups/TMR1.bk:% wbkupdb -r -d /usr/backups/TMR1.bk fuji

For more information about restoring a Tivoli database, see the wbkupdbcommand in the Tivoli Management Framework Reference Manual.

Using uninstall scriptsIn a Tivoli environment, Tivoli Enterprise Console components can be uninstalledusing the installation wizard or the wuninst command. However, in somesituations the installation does not succeed. In those situations you cannot uninstallthe component using the command line. To remove all the Tivoli definitions andfiles associated with the component, you need to run the corresponding uninstallscript on the computer where you installed the component.

The following table shows the uninstallation scripts associated with eachcomponent:

Table 45. Uninstallation scripts for Tivoli Enterprise Console components

Component Uninstall script

Event server $BINDIR/TME/TEC/tec-remove.sh

User interface (UI) server $BINDIR/TME/TEC/tec-uisvr-remove.sh

Event console $BINDIR/TME/TEC/tec-jconsole-remove.sh

Adapter Configuration Facility $BINDIR/TME/ACP/tec-acf-remove.sh

HP OpenView adapter $BINDIR/TME/TEC/adapters/bin/tecad-remove-hpov.sh

Sample event information $BINDIR/TME/TEC/tec-help-remove.sh

Installing from a remote file system in WindowsIf you are installing from Windows and want to install components in a Tivolienvironment from a remote file system, you need to set up the Tivoli ManagementFramework to allow access to remote file systems. To do so, use the wsettapcommand. For information on how to use the wsettap command, see the TivoliManagement Framework Reference Manual.

If you are using the installation wizard to install components and have not set upthe remote file system properly, an error message displays and you are not able toproceed. If you encounter an error message, set up the Tivoli ManagementFramework to allow access to remote file systems and continue.

Configuring a database to export NetView server data to IBM TivoliEnterprise Data Warehouse

Problem: Installation wizard fails to create a database for exporting data from theNetView server to IBM Tivoli Enterprise Data Warehouse.


Solution: check the /usr/OV/logs/nvcreatedb.log log file for problems, resolve theproblems, and then run the /usr/OV/bin/nvits_config script to configure thedatabase.

Upgrading Tivoli Enterprise Console database for Sybase and InformixProblem: If you are upgrading a Tivoli Enterprise Console 3.7.1 or 3.6.2 database toa 3.9 database using the installation wizard, the wizard may stop during theupgrade process if the Tivoli Enterprise Console database is a Sybase or Informixdatabase.

Workaround: To successfully upgrade a Sybase or Informix Tivoli EnterpriseConsole database, complete the following:1. In the installation wizard, select Generate Only. This will generate the database

upgrade scripts in the specified script output directory, but not execute thescripts.

2. After the scripts have been generated, exit the Tivoli Enterprise Consoleinstallation wizard.

3. Make the current directory the script output directory you specified in theinstallation wizard.

4. If you are upgrading a 3.6.2 database, issue the command: ./wdbconfig.shupg_362. If you are upgrading a 3.7.1 database, issue the command:./wdbconfig.sh upg

The wdbconfig.sh script then prompts you for values such as passwords and thenperforms the database upgrade.

Using the installation wizard on the HP-UX operating systemProblem: Using the Installation wizard on the HP-UX operating system has certainlimitations. Attempting to complete the following procedure causes someinstallation steps to be skipped in the HP-UX operating system:1. Proceed to install any component.2. When the installation wizard prompts you to insert the appropriate CD, click

Cancel.3. The results of the installation appear. Click Next to continue the installation4. Proceed to install the same component.

In other words, the window that prompts for the appropriate CD does not appearand the installation process is not performed

Solution: Close the installation wizard, and start it again to complete theinstallation.

Removing the event console when migrating from Version 3.6After using the wmigcon command to migrate to the Version 3.9 event console,you must remove the Version 3.6 event console using the tec-client3.6-remove.shscript. This script removes the icons, information about the Version 3.6 Tivolimanagement environment installation, menu entries, and binaries.

To remove the Version 3.6 event console from the Tivoli server and all managednodes, follow these steps:

Chapter 6. Troubleshooting common installation problems 93

1. Back up your event database.2. Ensure that your Tivoli environment is properly sourced to run the

/etc/Tivoli/setup shell script.3. Start a bash shell in your Tivoli region.4. Copy the tec-client3.6-remove.sh script from the $BINDIR/TME/TEC directory

to a working directory, such as the tmp subdirectory.5. From your designated working directory, run the tec-client3.6-remove.sh script

as follows to uninstall Version 3.6 event console:./tec-client3.6-remove.sh –rmfiles

Where:

–rmfilesRemoves local database objects and attempts to remove all filesassociated with the database, regardless of whether they are sharedfiles.

–usagePrints a usage statement.

6. Run the wchkdb command to verify and modify database resources in yourTivoli environment.Running the wchkdb command ensures database synchronization.

For more information about the wchkdb command, refer to the Tivoli ManagementFramework Reference Manual.


Appendix. A sample, step-by-step installation

This appendix describes a sample step-by-step installation of all IBM TivoliEnterprise Console components. This sample installation yields a simple workingdeployment, which you can use for evaluation, demonstration, and educationalpurposes. In this deployment, all components are installed on one computer,named acadia, which acts as the Tivoli server. The following graphic illustrates thisdeployment.

To produce this deployment, this appendix explains specifically how to completethe following sequential tasks:1. “Installing the Tivoli Management Framework” on page 962. “Configuring the event database” on page 973. “Installing components in a Tivoli environment” on page 984. “Installing the Web console component” on page 995. “Installing the NetView component” on page 100

Before you proceed with this appendix, you must do the following to set upacadia:v Ensure that acadia conforms to all software and hardware requirements. For

more information, see “Understanding product requirements” on page 10.v Install the DB2 database.

Note: You must name the DB2 user the same as the DB2 instance name. InUNIX, the DB2 user name is the same as the instance name by default.However, in Windows you must ensure that a user with the same nameas the instance name exists.

v Install SNMP and run it.v Enable the SNMP community name public for read access on devices in the

local subnet.

Tivoli server

Event Server

RIM Host

DB2 server

NetView server

WebSphereApplication server

Web console

Figure 11. All components on one Tivoli computer


v Ensure that the person performing this installation is the Administrator or rootuser for the computer where you want to perform the installation and is set upas a Tivoli root Administrator.

Installing the Tivoli Management Framework1. Install Tivoli Management Framework, Version 4.1:

a. On the UNIX operating system:1) Create a local temporary directory, for example /tmp_install.2) Change to that directory.3) Run the WPREINST.SH script from the Tivoli Management

Framework, Version 4.1 CD.4) Run the command displayed at the end of the preinstallation script

output. For example, the following command is used:./wserver –c /cdrom/cdrom0

5) Select When installing, create “Specified Directories” if missing andArrange for start of the Tivoli daemon at system (re)boot time.Accept the default locations. Click Set.

6) Accept all other default values, except do not enter information for theInstallation Password.

7) Click Install & Close and Continue to Install to complete theinstallation.

Messages are displayed in the window indicating the status andcompletion of the installation. Although the Tivoli desktop is automaticallylaunched, wait until the installation completes before using it.

b. On the Windows operating system:1) Using Windows Explorer, navigate to the root directory on the Tivoli

Management Framework, Version 4.1 CD.2) Double-click the setup.exe file to start the wizard.3) Accept all prompts and default values, except do not enter information

in the Installation Password or Remote Access Account dialog boxes.4) Select the Typical setup.5) Complete the installation by clicking Next on the remaining dialog

boxes.2. Install and launch the Tivoli desktop, Version 4.1:

a. Source the Tivoli environment:1) UNIX:

a) Run the /etc/Tivoli/setup_env.sh script.b) Start the bash shell by typing bash.

2) Windows:a) From the command line, run the following script:

%SystemRoot%\system32\drivers\etc\Tivoli\ setup_env.cmd

b) Start the bash shell by typing bash.b. Start the Tivoli desktop:

1) UNIX:a) Launch the Tivoli desktop with the tivoli command.b) The Tivoli desktop is displayed.

2) Windows:


a) From Windows Explorer, navigate to the \DESKTOP\NT_95directory on the Tivoli Management Framework, Version 4.1 CD.

b) Double-click the setup.exe file to start the wizard.c) Accept all prompts to complete the installation.d) To launch the Tivoli desktop, select Start —> Programs —> Tivoli

—> Tivoli Desktop.3. Install patches for Tivoli Management Framework, Version 4.1:

a. Review the IBM Tivoli Enterprise Console Release Notes for the list ofrequired patches and download them.

b. Extract the files to a temporary directory.c. From the Tivoli desktop, select Desktop —> Install —> Install Patch. The

Install Patch window is displayed.d. If the Select Product to Install list contains the correct patch, go to step

3h; otherwise, continue to step 3e.e. Click Select Media. The File Browser dialog box is displayed.f. Navigate to the directory that contains the installation image. The

installation directory contains the product index (.IND) file.g. Click Set Media & Close to save the new media path and return to the

Install Patch dialog box.h. Select the patch.i. Click Install & Close and Continue to Install. Messages are displayed in

the window indicating the status and completion of the installation.j. Repeat this procedure for each required patch.k. Restart the oserv process with the odadmin reexec command.

Configuring the event databaseTo start the installation wizard, complete the following:1. Insert the installation wizard CD.2. Find one of the following files in the CD, and run the appropriate file:

v For a Windows system, run tec_install.bat

v For a UNIX system, add root user to db2group, open a UNIX shell, rundb2profile script, and run tec_install.sh in the same shell

3. When the welcome window appears, click Next.4. Specify a temporary location to copy the installation files to, and click Next.

The wizard copies several files from the CD to a temporary directory that youspecify.

5. After the wizard copies the files, click Next to stop and restart the wizardfrom the temporary location.

6. Accept to the required terms of the license agreement, and click Next.7. Click Configure the event database and click Next.8. Click Simple and click Next.9. Type the directory where you want to store or read generated scripts (for

example, /tmp/tecscripts, and click Next.10. Fill in the fields as shown in the following table, and click Next.

Table 46. Database values for quick start

Database Vendor DB2

Appendix. A sample, step-by-step installation 97

Table 46. Database values for quick start (continued)

Database Home Type the full path to the directory where the RDBMSserver or client software is installed.

UNIX example: /usr/lpp/db2_07_01

Windows example: C:\progra~1\sqllib

Database Name Type a unique alias name of the event database

Example: tecdb

Database User ID Type a user name of the DB2 instance owner for theevent database.

UNIX example: db2inst1

Windows example: db2

Database Password Type the password for the database user.

Verify Password Retype the password for the database user.

Database Server ID Type the name of host where the database is installed(value of the DB2COMM environment variable).

Example: acadia

Instance Home Type the home directory where the instance wascreated. For UNIX, it is the value of the $INSTHOMEenvironment variable. For Windows, it is usually thesame value as the Database Home option.

UNIX example: /home/db2inst1

Windows example: c:\db2

11. To accept the default values, click Next.12. After you have reviewed the summary window, click Next.13. After you have reviewed the results, click Next. The main installation window

appears.

Installing components in a Tivoli environment1. Click Install, upgrade or uninstall components in a Tivoli environment, and

click Next.2. After the wizard searches for installed components (it will find none), click

Next.3. Click Install IBM Tivoli Enterprise Console 3.9 components, and click Next.4. Click all of the following and then click Next:

v Event server

v User interface server

v Event console

v Sample event information

v Adapter Configuration Facility

5. If you were in an environment that contained more than one managed node,the installation wizard would present you with several managed nodes tochoose from. However, because this installation is for a single machine, you


do not see these steps. At this point you see a list of rule sets to be activated.All are currently selected. To proceed without deactivating any rule sets, clickNext.

6. To proceed without changing any of the event server start options, click Next.7. To proceed without selecting language packs, click Next.8. After reviewing your selections, click Next.9. When prompted, insert the CD containing Tivoli Enterprise Console

installation images, and click Next.10. After reviewing the installation messages, click Next. The main installation

window appears.

Installing the Web console component1. Click Install the Web console component, and click Next.2. When a message appears explaining that the WebSphere Application Server

will be restarted during installation, click Continue.3. Click Install IBM Tivoli Enterprise Console Web component, and click Next.4. Click Install the IBM WebSphere Application Server now, and click Next.5. After reviewing your selections, click Next.6. When prompted, insert the WebSphere Application Server installation CD, and

click OK.

Note: If you are using Windows, the WebSphere Application Serverinstallation program starts automatically. When this happens, close theWebSphere Application Server installation program, and click OK in theinstallation wizard. The installation wizard then starts the WebSphereApplication Server installation program as part of its process. Runningthe WebSphere Application Server installation program independentlymay cause confusion and interfere with proper installation of the Webconsole.

7. Select the language you want to use, and click OK.8. Accept to the required terms of the license agreement, and click Next.9. Click Custom installation and complete the WebSphere Application Server

installation, by clicking Next and accepting the default values.10. When you complete installation of the WebSphere Application Server, you are

asked if the installation was successful. Click The IBM WebSphereApplication Server was successfully installed, and click Next.

11. Click Add to add a Tivoli region.12. Type acadia for Host name, Administrator or root for User name, and the

password for that user. Then click Next.13. Click all of the managed nodes (only acadia appears in this deployment), and

click Finish.14. Click Next to proceed.15. After reviewing your selections, click Next.16. When prompted, insert the CD containing the Web console installation image,

and click OK to install the Web console.17. After reviewing the installation messages, click Next. The main installation

window appears.


Installing the NetView component

On the UNIX operating system1. Click Install components in a non-Tivoli environment, and click Next.2. Click Install one of the following IBM Tivoli NetView components.3. Click IBM Tivoli NetView server and console, and click Next.4. Click Discover only the local subnet, and click Next.5. Leave the SNMP community names blank, and click Next.6. Type acadia for Host name of the event server.7. Type 0 for a UNIX event server or 5529 for a Windows event server for

Listening port of the event server.8. Click the appropriate operating system of the event server, and click Next.9. To proceed without configuring the NetView server further, click Next.

10. To proceed without selecting language packs, click Next.11. After reviewing your selections, click Next.12. When prompted, insert the CD containing the NetView server installation

image, and click OK to install the NetView server.13. After reviewing the results, click Finish.14. To exit, click Yes.

On the Windows operating system1. From Windows Explorer, navigate to the root directory on the NetView for

Windows installation CD.2. Double-click the setup.exe file to start the wizard.3. Accept the prompts, and click Next to proceed through the wizard.4. For installation mode, click Server, and click Next.5. Type a password for the NetView account, and click Next.6. Click the Discover Local Subnet Only option, and click Next.7. Leave the SNMP community names blank, and click Next.8. Click Configure Event Forwarding, and click Next.9. Click a non-TME adapter, and click Next.

10. Click Close to close the IBM Tivoli Monitoring Servers window.11. Click Skip, and click Next.12. Type the name of the host where the event server is located, and click Next.13. Click the appropriate operating system of the event server, and click Next.14. Type 0 for a UNIX event server or 5529 for a Windows event server for

Listening port of the event server, and click Next.15. Complete the installation by clicking Next.

Starting the Web consoleTo start the Tivoli Enterprise Console Web console and view events, complete thefollowing:1. Start a browser and go to http://acadia:9080/TecConsoleWeb.2. Type Administrator or root for User name.3. Type the password for that user.


4. Select the managed node acadia.5. Click OK.

You can then view events.



Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment to


IBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM‘s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksThe following terms are trademarks of International Business MachinesCorporation in the United States, other countries, or both:

IBM iSeries SequentIBM Logo OpenEdition Tivoli EnterpriseTivoli NetView Tivoli Enterprise ConsoleTivoli Logo OS/2 WebSphereAIX OS/390 zSeriesDB2 OS/400Informix pSeries

Java and all Java-based trademarks and logos aretrademarks or registered trademarks of SunMicrosystems, Inc. in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.

Notices 105


Index

Special characters.db2cshrc file 18.db2profile file 18.odbc.ini file 19, 56.profile file 18

Aaccounts

Informix 56adapter

disk space requirementsadapter 13

Adapter Configuration Facilitydescription 1installation details 26uninstall script 92uninstallation product tag 86upgrade index file name 85

adaptersdisk space requirements

adapters 13adding Tivoli region

for Web console 42AIX

requirements 14arrow, event server icon ixautomatic discovery range

setting for NetView server 40

Bbacking up

object database 79books

see publications v, vi

Ccataloging

DB2 server 19command line

registering resources 35using to install 82using to uninstall 85using to upgrade 84

commandswbkupdb 79, 92wchkdb 87wcrtrim 90wcrtteccfg 87wdel 90wimport 83winstall 82wpatch 84wregister 35wrimtest 91wsetrim 90wsetrimpw 90

commands (continued)wsettap 92wstartesvr 87wstopesvr 79wuninst 85, 86, 92wupdate 35

communication, for DB2 56configuration

failover 10managed node deployment 3multi-Tivoli region 8NetView managed node

deployment 6Tivoli server deployment 4, 5, 7Tivoli server with NetView

deployment 8configuration options 70configuration options table 70configuring

default consoles 87default event groups 87event database 45event database, custom 58RDBMS 17

configuring the event databaseusing installation wizard 38

consolesconfiguring default 87

conventionstypeface viii

customevent database configuration 58

customer supportsee software support vii

Ddatabase

problems created for exporting fromNetView 92

restoring with a functional objectdispatcher 92

database configuration 64, 68, 69, 70, 73DB2 63enabling language support 75Informix 63Microsoft SQL Server 68Oracle 69, 70performance enhancements 63

database considerations 47Informix 48MS SQL Server 49, 50Oracle 49Sybase 50

Database Home fieldDB2 56Informix 56MS SQL Server 56Oracle 57Sybase 57

database requirements 15

Database User ID fieldDB2 56Informix 56MS SQL Server 56Oracle 57Sybase 57

databasesconfiguring Microsoft SQL Server 20configuring Oracle 20configuring Sybase 20DB2 18DB2 configuring 18Informix configuring 19Informix installing 19installing Microsoft SQL Server 20installing Oracle 20installing Sybase 20

DB2active instance 19, 56assigning ports 19cataloging

server 19communication 19, 56configuring 18configuring client 19configuring for remote client

access 19database configuration 63Database Home field 56Database User ID 56enabling foreign language support

for 75installing 18instance home 56instance owner 56interactive SQL utility 19options 63requirements 15server-only configuration 19

DB2 considerations 47DB2 considerations using wizard 47DB2 installation problems

avoiding 89DB2 server options table 69DB2COMM environment variable 19, 56DB2INSTANCE environment

variable 19, 56directory names, notation viiidisk space

requirements 13DSQUERY environment variable 57

Eenabling

foreign language support 75enabling for DB2 75enabling for GB18030 character set 75enabling using installation wizard 75environment variables

DB2COMM 19, 56


environment variables (continued)DB2INSTANCE 19, 56DSQUERY 57INFORMIXDIR 19, 56INSTHOME 56ORACLE_HOME 20SYBASE 21, 57TWO_TASK 57

environment variables, notation viiievent adapters

description 2installation details 27

event consoledescription 1installation details 24installation index file name 82installing using installation

wizard 40launching as background process

error 91uninstall script 92uninstallation product tag 86upgrade index file name 85

event database 45custom 58execute scripts only 62generate and execute scripts 62generating scripts 62

generating 61no change option 62

installing components usingwizard 61

sample configuration usinginstallation wizard 97

uninstalling 60upgrading event server 60

event groupsconfiguring default 87

event integration facilityinstallation details 28

Event Integration Facilityuninstallation product tag 86

event serveravoiding installation problems on

Windows 89description 1installation details 22installation index file name 82starting 87stopping 79uninstall script 92uninstallation product tag 86upgrade index file name 85

event server detailssetting for NetView server 40

EventServer resource 35Everyone

giving user permissions 89exporting database from NetView

problems created 92

Ffailovers 10foreign language

enabling support 75

functional object dispatcherusing to restore database 92

GGB18030 character set

enabling support for 75generating scripts using 62

Hhardware

requirements 10home directory, DB2 instance 56HP OpenView adapter

installation details 27installation index file name 82uninstall script 92uninstallation product tag 86upgrade index file name 85

HP-UXproblems using the installation wizard

on 93

IIBM Tivoli Monitoring parameters

setting for NetView server 40icons ix

Event Server ixProfile ixRulebase ix

index files nameexplanation 80

Informixaccount 56configuring 19considerations using wizard 48database configuration 63Database Home field 56Database User ID 56enabling foreign language support

for 76installation directory 19installing 19logical logs 67options 63problems upgrading Tivoli Enterprise

Console database for 93requirements 15sqlhosts file 56

Informix options table 64INFORMIXDIR environment variable 19INFORMIXSERVER environment

variable 56installation

process 17sample using installation wizard 95

installation directoryInformix 19Oracle 20

installation index file nameevent console 82event server 82for all components 80, 81HP OpenView adapter 82

installation index file name (continued)sample event information 82Tivoli Enterprise Console JRE 82Tivoli NetView server 82user interface server 82

installation problemsavoiding 89

installation wizard 45advantages of using 37changing non-default port settings

before using 35event database configuration 45installation procedure 38problems upgrading Tivoli Enterprise

Console database for Sybase andInformix databases 93

problems using on the HP-UXoperating system 93

requirements 16sample configuration of event

database 97sample installation 95sample installation in Tivoli

environment 98sample installation of NetView in

UNIX 100sample installation of NetView in

Windows 100sample installation of Tivoli

Management Framework 96sample installation of Web

console 99using the correct computer 37using to add Tivoli region for Web

console 42using to configure event database 38using to install event console 40using to install in a non-Tivoli

environment 40using to install in Tivoli

environment 39using to install NetView server 40using to install NetView Web

console 41using to install Web console 41using to install WebSphere

Application Server 41using to setting up Web console 42using to uninstall in a Tivoli

environment 39using to uninstall Web console 42using to upgrade in a non-Tivoli

environment 40using to upgrade in Tivoli

environment 39installing

components in Tivoli environmentusing installation wizard 39

DB2 18in non-Tivoli environment using

installation wizard 40NetView Web console using

installation wizard 41RDBMS 17Tivoli Management Framework 17using event database installation

wizard 45


installing (continued)using the installation wizard 37using Tivoli desktop 81using Tivoli Management Framework

command line 82using Tivoli Management Framework

methods 80using Tivoli Software Installation

Service 82Web console using installation

wizard 41WebSphere Application Server using

installation wizard 41installing event console

using installation wizard 40installing NetView server

using installation wizard 40instance home, DB2 56Instance Name field 18

Informix 56MS SQL Server 57Oracle 57Sybase 57

instance ownerDB2 56

INSTHOME environment variable 56interconnect Tivoli regions, with Tivoli

Enterprise Console 8interconnected Tivoli regions

preparing to install componentsin 35

interfaces file 21iotcl system call

problem 91ITM parameters

setting for NetView server 40

Llanguage packs

Tivoli Enterprise Console installationdetails 32

Tivoli NetView installation details 32language support 75

enabling for Microsoft SQL Server 76enabling for Oracle 76Informix 76Sybase 76

licenseagreeing to 38locating files 43

Linuxrequirements 14

listener service, Oracle 57logical logs

Informix 67

Mmanuals

see publications v, vimemory structure table

Oracle 69Microsoft SQL Server

configuring 20database configuration 68

Microsoft SQL Server (continued)Dictionary order 20enabling foreign language support

for 76installing 20options 68requirements 15Sort Order 20

MS SQL Serverconsiderations using wizard 49, 50Database Home field 56Database User ID 56

MS SQL Server parameters table 68

Nname registry, Tivoli 35NetView

deployment with Tivoli server 8managed node deployment 6sample UNIX installation using

installation wizard 100sample Windows installation using

installation wizard 100NetView native console

description 2NetView server

description 2installation details 29installing using installation

wizard 40setting automatic discovery range

for 40setting event server details 40setting IBM Tivoli Monitoring

parameters 40setting SNMP community names 40setting Tivoli Enterprise Data

Warehouse parameters 40NetView Web console

description 2installation details 31installing using installation

wizard 41newsgroups viino change option 62non-default port settings

changing when using TivoliManagement Framework andinstallation wizard 35

non-Tivoli environmentinstalling in using installation

wizard 40upgrading in using installation

wizard 40notation

environment variables viiipath names viiitypeface viii

Oobject database

backing up 79updating 87

online publicationsaccessing vi

operating system requirements 14Oracle 70

avoiding problems on Windows 89configuring 20considerations using wizard 49database configuration 69database configuration options 70Database Home field 57Database User ID 57enabling language support for 76installation directory 20installing 20instance ID 20listener service 57memory structure table 69options 69redo log buffer 70requirements 15rollback segments 70SQL*Plus 20

ORACLE_HOME environmentvariable 20

ordering publications vi

Ppath names, notation viiiperformance enhancements

database configuration 63port settings

changing non-default when usingTivoli Management Framework andinstallation wizard 35

ports, for DB2 19product images

Tivoli Enterprise Console 16publications v

accessing online viordering vi

RRDBMS

choosing server 18configuring 17installing 17

redo log buffer and files 70registered product tag

explanation 80for all components 80, 81

registering resources 35remote client

configuring DB2 for access 19remote file system

allowing access on Windows 92problems installing from

Windows 92requirements

additional 16AIX 14database 15DB2 15disk space 13hardware 10

Index 109

requirements (continued)Informix 15installation wizard 16Linux 14Microsoft SQL Server 15operating system 14Oracle 15software 14Solaris 14Sybase 15Tivoli Enterprise Console upgrade 16Tivoli Management Framework 16Web browser 16WebSphere Application Server 16Windows 14

resources, EventServer 35RIM

with Sybase 20RIM host

choosing 18RIM object

creating 90creation 89deleting 90modifying 90obtaining information about 89testing connectivity 90

rollback segmentsOracle 70

running 59wdbconfig.sh script for Informix 59

Ssample event information

description 2installation details 27installation index file name 82uninstall script 92uninstallation product tag 86upgrade index file name 85

scriptwdbconfig.sh 59

scriptsusing uninstall 92

serviceOracle listener 57

services file 19setting up Tivoli roles and resources

using Tivoli desktop 87setting up Web console

adding Tivoli region for Webconsole 42

using installation wizard 42SNMP community names

setting for NetView server 40software requirements 14software support

contacting viiSolaris

requirements 14SQL.INI file 21SQL*Plus 20sqlhosts file 56starting

event server 87

stoppingevent server 79

stty:tcgetattr problem 91Sybase 73

configuring 20considerations using wizard 50database configuration options 73Database Home field 57Database User ID 57enabling foreign language support

for 76installing 20problems upgrading Tivoli Enterprise

Console database for 93requirements 15SQL.INI file 21

Sybase configuration options table 73SYBASE environment variable 21, 57

TTEDW parameters

setting for NetView server 40Tivoli

name registry 35Tivoli desk top

using to install components 81using to set up Tivoli roles and

resources 87using to upgrade components 84

Tivoli Enterprise Consolecomponent description 1component installation details 22product images 16

Tivoli Enterprise Console JREinstallation details 22installation index file name 82uninstallation product tag 86

Tivoli Enterprise Console language packsinstallation details 32

Tivoli Enterprise Console upgraderequirements 16

Tivoli Enterprise Data Warehouseparameters

setting for NetView server 40Tivoli environment

installing components in usinginstallation wizard 39

sample installation using installationwizard 98

uninstalling components in using theinstallation wizard 39

upgrading components in usinginstallation wizard 39

Tivoli Management Frameworkavoiding problems on Windows 89changing non-default port settings

before using installation wizardwith 35

installing 17sample installation using installation

wizard 96Tivoli Management Framework command

lineinstallation methods 80using to install 82using to uninstall 85

Tivoli Management Framework commandline (continued)

using to upgrade 84Tivoli Management Framework

requirements 16Tivoli NetView language packs

installation details 32Tivoli NetView server

installation index file name 82upgrade index file name 85

Tivoli server environmentadjusting to incorporate the proper

settings for UTF8 coding 76Tivoli Software Information Center viTivoli Software Installation Service

using to install components 82using to upgrade components 85

tmersrvd account 18tmersvrd

adding user to the WindowsAdministrators group 89

tnsnames.ora file 20, 57tuning

Oracle redo log buffer and files 70Oracle rollback segments 70

TWO_TASK environment variable 57typeface conventions viii

Uuninstall script

Adapter Configuration Facility 92event console 92event server 92HP OpenView adapter 92sample event information 92user interface server 92

uninstall scriptsusing 92

uninstallation product tagAdapter Configuration Facility 86event console 86Event Integration Facility 86event server 86HP OpenView adapter 86sample event information 86Tivoli Enterprise Console JRE 86user interface server 86

uninstallingcomponents in a Tivoli environment

using the installation wizard 39event database objects only 61using Tivoli Management Framework

command line 85uninstalling Web console

using installation wizard 42updating

object database 87upgrade index file name

Adapter Configuration Facility 85event console 85event server 85for all components 80, 81HP OpenView adapter 85sample event information 85Tivoli NetView server 85user interface server 85


upgradingcomponents in a Tivoli environment

using installation wizard 39from Version 3.6.2 33in non-Tivoli environment using

installation wizard 40requirements for Tivoli Enterprise

Console 16using Tivoli desktop 84using Tivoli Management Framework

command line 84using Tivoli Software Installation

Service 85Upgrading Tivoli Enterprise Console

databaseproblems using the installation wizard

on Solaris for Sybase databases 93user accounts

Informix 56user interface server

description 1installation details 23installation index file name 82uninstall script 92uninstallation product tag 86upgrade index file name 85

UTF8 codingadjusting the Tivoli server

environment to incorporate theproper settings for 76

Vvariables, notation for viiiVersion 3.6.2

upgrading details 33

Wwbkupdb 79, 92wchkdb 87wcrtrim 90wcrtteccfg 87wdbconfig.sh 59

for DB2 59for Informix 59

wdbconfig.sh script 59wdbconfig.sh script for DB2 59wdel 90Web browser requirements 16Web console

adding Tivoli region for 42installing using installation

wizard 41sample installation using installation

wizard 99setting up using installation

wizard 42uninstalling using installation

wizard 42WebSphere Application Server

installing using installationwizard 41

WebSphere Application Serverrequirements 16

wimport 83

Windowsrequirements 14

Windows installation problemsavoiding 89

winstall 82wpatch 84wregister 35wrimtest 91wsetrim 90wsetrimpw 90wsettap 92wstartesvr 87wstopesvr 79wuninst 85, 86, 92wupdate 35

Index 111


��

Printed in U.S.A.

SC32-1233-00