ibm tivoli configuration manager: planning and...

IBM Tivoli Configuration ManagerPlanning and Installation

Version 4.2

GC23-4702-00

September 13, 2002

IBM Tivoli Configuration Manager

Planning and InstallationVersion 4.2

GC23-4702-00

��

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

First Edition (September 2002)

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

Contents

Preface . . . . . . . . . . . . . . . vWho should read this guide . . . . . . . . . vWhat this guide contains . . . . . . . . . . vPublications . . . . . . . . . . . . . . vi

Prerequisite documents . . . . . . . . . viRelated documents . . . . . . . . . . . viAccessing publications online . . . . . . . viiOrdering publications . . . . . . . . . . viiProviding feedback about publications . . . . vii

Contacting customer support . . . . . . . . viiiConventions used in this guide . . . . . . . viii

Chapter 1. Overview of configurationmanagement. . . . . . . . . . . . . 1Basic Tivoli environment . . . . . . . . . . 1Tivoli server components and services . . . . . . 2Managed node components and services . . . . . 3Endpoint components and services . . . . . . . 4Resources in a configuration managementenvironment . . . . . . . . . . . . . . 5

Resources used for inventory scans . . . . . . 5Resources used for software distributions . . . . 5Resources used for resource management. . . . 6Resources used for Web operations . . . . . . 7Resources used for configuration management . . 8

Chapter 2. Planning a configurationmanagement environment . . . . . . 13Creating a deployment plan . . . . . . . . . 13Using RIM and the RDBMS . . . . . . . . . 14

Selecting RIM hosts. . . . . . . . . . . 14Selecting the RDBMS server . . . . . . . . 15Configuring RIM objects . . . . . . . . . 15RIM objects used for configuration management 15Synchronizing RIM objects with RDBMSdatabases . . . . . . . . . . . . . . 16

Software requirements for the Web Gatewaycomponent . . . . . . . . . . . . . . 17

Software requirements for resource management 17Software requirements for Web access . . . . 17

Creating the DB2 users for the Web Gatewaycomponent . . . . . . . . . . . . . . 18

Creating the DB2 users on UNIX operatingsystems. . . . . . . . . . . . . . . 18Creating the DB2 users on Windows operatingsystems. . . . . . . . . . . . . . . 18

Using the Web Gateway component with IBM TivoliAccess Manager . . . . . . . . . . . . . 19

Configuring the Java Runtime Environment . . 19Creating SSL configurations and keystores . . . 19Configuring SSL connections with self-signedcertificates . . . . . . . . . . . . . . 20

Extracting self-signed certificates . . . . . 20Importing self-signed certificates . . . . . 21

Configuring the WebSEAL server . . . . . . 21

Testing the WebSEAL configuration . . . . . 22Choosing where to install components . . . . . 23

Choosing where to install the Inventorycomponents . . . . . . . . . . . . . 23Choosing where to install the Resource Managercomponents . . . . . . . . . . . . . 23Choosing where to install the SoftwareDistribution components . . . . . . . . . 23Choosing where to install the Web Gatewaycomponent . . . . . . . . . . . . . 24

Using configuration management in connectedTivoli regions . . . . . . . . . . . . . . 25

Running inventory scans in connected Tivoliregions . . . . . . . . . . . . . . . 25Distributing software in connected Tivoli regions 26Managing devices and users in connected Tivoliregions . . . . . . . . . . . . . . . 26

Chapter 3. Planning for componentinstallations . . . . . . . . . . . . 27Authorization roles . . . . . . . . . . . . 27Installation sequence for components . . . . . . 27

Installation sequence using IBM TivoliConfiguration Manager mechanisms . . . . . 27Installation sequence using Tivoli ManagementFramework mechanisms . . . . . . . . . 28

Components of IBM Tivoli Configuration Manager 30Components installed from index files . . . . 30Components installed from software packageblocks . . . . . . . . . . . . . . . 31

Software packages for the Java components . 32Software packages for the Web Gatewaycomponents . . . . . . . . . . . . 32Software packages for the Web Infrastructurecomponents . . . . . . . . . . . . 33Software packages for Tivoli endpoints . . . 33Software packages for the Software PackageEditor component . . . . . . . . . . 33Software packages for the Pristine Toolcomponent . . . . . . . . . . . . 34Software packages for the IBM TivoliConfiguration Manager administrativeinterfaces . . . . . . . . . . . . . 34

Installation options . . . . . . . . . . . . 35Activity Planner . . . . . . . . . . . . 35Change Manager . . . . . . . . . . . 37Enterprise Directory Query Facility . . . . . 39Inventory . . . . . . . . . . . . . . 40Inventory Gateway . . . . . . . . . . . 42Resource Manager . . . . . . . . . . . 42Resource Manager Gateway . . . . . . . . 43Scalable Collection Service . . . . . . . . 43Software Distribution . . . . . . . . . . 44Software Distribution Gateway . . . . . . . 44Software Package Editor . . . . . . . . . 44

© Copyright IBM Corp. 2002 iii

Web Gateway. . . . . . . . . . . . . 44Web Gateway database . . . . . . . . 45Web Gateway server . . . . . . . . . 45

Web Infrastructure . . . . . . . . . . . 48

Chapter 4. Installing IBM TivoliConfiguration Manager . . . . . . . . 49Installing components using the installationprogram . . . . . . . . . . . . . . . 49

Locating the installation programs. . . . . . 50Starting the installation programs . . . . . . 51Server installation . . . . . . . . . . . 51

Typical and custom installations . . . . . 52Typical installation . . . . . . . . . . 52Custom installation . . . . . . . . . . 53

Upgrade Plan Generator installation . . . . . 53Web Gateway installation. . . . . . . . . 56

Typical installation . . . . . . . . . . 56Custom installation . . . . . . . . . . 56

Desktop installation . . . . . . . . . . 56Typical installation . . . . . . . . . . 57Custom installation . . . . . . . . . . 57

Installing components using Tivoli SoftwareInstallation Service . . . . . . . . . . . . 57Installing components using the Tivoli desktop . . 58Installing components using the command line . . 58Installing components using software packageblocks . . . . . . . . . . . . . . . . 59Migrating data in repositories . . . . . . . . 61Installing and upgrading query libraries . . . . . 62Registering plug-ins . . . . . . . . . . . 62Uninstalling IBM Tivoli Configuration Manager . . 63

Uninstalling components using Add/Removeprograms . . . . . . . . . . . . . . 63Uninstalling components using the wuninstcommand . . . . . . . . . . . . . . 64Uninstalling component using scripts. . . . . 64Uninstalling software package blocks . . . . . 64Uninstalling Software Distribution from NetWaregateways . . . . . . . . . . . . . . 65

Chapter 5. Working with repositoriesand queries. . . . . . . . . . . . . 67Running the admin scripts . . . . . . . . . 67

Creating DB2 tablespaces . . . . . . . . . 68Creating Microsoft SQL Server tablespaces . . . 69Creating Oracle tablespaces . . . . . . . . 70Creating Sybase tablespaces . . . . . . . . 72

Running the schema scripts . . . . . . . . . 73Installing DB2 schemas . . . . . . . . . 73Installing Informix schemas . . . . . . . . 74Installing Microsoft SQL Server schemas. . . . 74Installing Oracle schemas. . . . . . . . . 75Installing Sybase schemas . . . . . . . . 78

Running Enterprise Directory Query Facility scripts 79

Chapter 6. Maintaining andtroubleshooting a configurationmanagement environment . . . . . . 81

Testing schemas . . . . . . . . . . . . . 81Registering Enterprise Directory Query Facilityresources . . . . . . . . . . . . . . . 83Completing a failed Server installation . . . . . 83Understanding return values for Web Gatewayinstallations . . . . . . . . . . . . . . 83Installing software signatures . . . . . . . . 85Maintaining the Web Gateway component . . . . 85

Changing the enrollment URL . . . . . . . 85Configuring for use with IP addresses . . . . 86Configuring for use with non-standard HTTPports . . . . . . . . . . . . . . . 86Configuring for use with WebSEAL junctions . . 87Increasing tablespace in the Web Gatewaydatabase . . . . . . . . . . . . . . 87Configuring the DB2 client . . . . . . . . 87

Running common RDBMS commands . . . . . 88DB2 commands . . . . . . . . . . . . 88Informix commands . . . . . . . . . . 89Microsoft SQL Server commands . . . . . . 89Oracle commands . . . . . . . . . . . 90Sybase commands . . . . . . . . . . . 90

Appendix A. Planning and installationworksheets . . . . . . . . . . . . . 93Planning worksheet . . . . . . . . . . . 95Server installation worksheets . . . . . . . . 97

Typical path for server installation worksheet . . 99Custom path for server installation worksheet 101Tivoli Management Framework mechanisms forserver installation worksheet . . . . . . . 106

Web Gateway installation worksheets . . . . . 111Typical path for Web Gateway installationworksheet . . . . . . . . . . . . . 113Custom path for Web Gateway installationworksheet . . . . . . . . . . . . . 115

Desktop installation worksheets . . . . . . . 117Typical path for desktop installation worksheet 118Custom path for desktop installation worksheet 118

Tivoli environment upgrade worksheets . . . . 119Installation program for Tivoli environmentupgrade worksheet . . . . . . . . . . 120Tivoli Management Framework mechanisms forTivoli environment upgrade worksheet . . . . 122

Using Tivoli Software Installation Service toupgrade a Tivoli region . . . . . . . . 122Using the Tivoli desktop to upgrade a Tivoliregion . . . . . . . . . . . . . . 122Using Tivoli Management Frameworkcommands to upgrade a Tivoli region . . . 123

Appendix B. Notices . . . . . . . . 125Trademarks . . . . . . . . . . . . . . 126

Index . . . . . . . . . . . . . . . 129

iv IBM Tivoli Configuration Manager: Planning and Installation

Preface

IBM® Tivoli® Configuration Manager Planning and Installation explains how to plan orupgrade your deployment of IBM Tivoli Configuration Manager in a Tivolienvironment as well as how to install, upgrade, and uninstall the components ofIBM Tivoli Configuration Manager using the available installation mechanisms.

This guide provides information about installing and upgrading IBM TivoliConfiguration Manager, provided that your Tivoli environment meets the followingrequirements:v Tivoli Management Framework, Version 3.7 Revision B, or greaterv Tivoli Inventory, Version 4.0, or greaterv Tivoli Software Distribution, Version 4.1, or greater

If you are at an older version than the ones listed, you need to upgrade your Tivolienvironment to this minimum level to use the installation mechanisms andinformation documented in this guide. To get to these levels, see IBM TivoliConfiguration Manager Upgrade Scenarios. You can access this document from theTivoli Field Guides Web site:

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

Who should read this guideThe target audience for this guide is system architects, system administrators, andtechnical specialists who are responsible for the planning and installation of IBMTivoli Configuration Manager. Users of this guide should have knowledge aboutthe following technologies:v PC and UNIX® operating systemsv Database architecture and conceptsv Graphical and command line interfaces

What this guide containsThis guide contains the following sections:v Chapter 1, “Overview of configuration management” on page 1

Introduces the configuration management architecture and how this architectureis used in the context of a Tivoli environment.

v Chapter 2, “Planning a configuration management environment” on page 13Provides the information needed to create a deployment plan and to select theappropriate installation mechanism for installing or upgrading IBM TivoliConfiguration Manager.

v Chapter 3, “Planning for component installations” on page 27Provides planning information for installing each of the IBM TivoliConfiguration Manager installation images.

v Chapter 4, “Installing IBM Tivoli Configuration Manager” on page 49Provides the information required to install, upgrade, and uninstall IBM TivoliConfiguration Manager using the available installation mechanisms.

v Chapter 5, “Working with repositories and queries” on page 67

© Copyright IBM Corp. 2002 v


Provides information about running the admin and schema scripts required bythe relational database management system (RDBMS) Interface Module (RIM)objects created during the installation of the various components of IBM TivoliConfiguration Manager.

v Chapter 6, “Maintaining and troubleshooting a configuration managementenvironment” on page 81Provides information about resolving problems that you might encounter whileinstalling, configuring, or upgrading IBM Tivoli Configuration Manager in aTivoli environment.

v Appendix A, “Planning and installation worksheets” on page 93Provides worksheets that help to guide you through the planning andinstallation processes.

PublicationsThis section lists publications in the IBM Tivoli Configuration Manager library andany other related documents. It also describes how to access publications online,how to order the publications, and how to submit comments on the publications.

Prerequisite documentsThis section lists prerequisite publications in the IBM Tivoli Configuration Managerlibrary and any other related documents.v Tivoli Management Framework Planning for Deployment, GC32-0803

Explains how to plan for deploying your Tivoli environment. It also describesTivoli Management Framework and its services.

v Introducing IBM Tivoli Configuration Manager, GC23-4703Explains the concepts and components of IBM Tivoli Configuration Manager.

v Tivoli Enterprise Installation Guide, GC32-0804Explains how to install and upgrade Tivoli Enterprise™ software within yourTivoli region using the available installation mechanisms provided by TivoliSoftware Installation Service and Tivoli Management Framework. TivoliEnterprise software includes the Tivoli management region server (Tivoli server),managed nodes, gateways, endpoints, and RIM objects. This guide also providesinformation about troubleshooting installation problems.

v IBM Tivoli Configuration Manager Release Notes, GI11-0926Describes the latest installation information, including supported platforms,defects, and limitations for IBM Tivoli Configuration Manager.

v Tivoli Management Framework Release Notes, GI11-0890Describes the latest installation information, including supported platforms,defects, and limitation for Tivoli Management Framework.

Related documentsThis section lists related publications in the IBM Tivoli Configuration Manager libraryand any other related documents.v IBM Tivoli Configuration Manager User’s Guide for Software Distribution, SC23-4711

Explains the concepts and procedures necessary to effectively distribute softwareover networks using the Software Distribution component of IBM TivoliConfiguration Manager.

v IBM Tivoli Configuration Manager User’s Guide for Inventory, SC23-4713

vi IBM Tivoli Configuration Manager: Planning and Installation

Explains the concepts and procedures necessary to effectively use the Inventorycomponent of IBM Tivoli Configuration Manager and provides in-depthinformation about the commands used by the Inventory component.

v IBM Tivoli Configuration Manager User’s Guide for Deployment Services, SC23-4710Explains the concepts and procedure necessary to effectively use the deploymentservices of IBM Tivoli Configuration Manager and provides in-depth informationabout the commands used by the deployment services.

v IBM Tivoli Configuration Manager Reference Manual for Software Distribution,SC23-4712Provides advanced information about how to use and customize the SoftwareDistribution component of IBM Tivoli Configuration Manager.

v Tivoli Management Framework Reference Manual, SC32-0806Provides in-depth information about Tivoli Management Framework commands.This manual is helpful when writing scripts that are later run as Tivoli tasks.This manual also documents default and validation policy scripts used by TivoliManagement Framework.

Accessing publications onlinePublications in the product libraries are included as PDF files on the product CD.

When IBM publishes an updated version of one or more online or hardcopypublications, they are posted to the Tivoli Information Center. You can accessupdated publications in the Tivoli Information Center from the following IBMCustomer Support Web site:

http://www.tivoli.com/support/documents

The Tivoli Information Center contains the most recent version of the books in theproduct library in PDF or HTML formats, or both. Translated documents are alsoavailable for some publications.

Note: If you print PDF documents on other than letter-sized paper, select the Fit topage check box in the Adobe Acrobat Print dialog (which is available whenyou click File → Print) to ensure that the full dimensions of a letter-sizedpage are printed 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

From this Web page, select Publications and follow the instructions.

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968v In other countries, for a list of telephone numbers, see the following Web site:

http://www.tivoli.com/inside/store/lit_order.html

Providing feedback about publicationsIf you have comments or suggestions about Tivoli products and documentation,provide feedback in one of the following ways:

Preface vii

http://www.tivoli.com/support/documents

http://www.elink.ibmlink.ibm.com

http://www.tivoli.com/inside/store/lit_order.html

v Send an e-mail to [email protected] Complete the customer feedback survey at the following Web site:

http://www.tivoli.com/support/survey

Contacting customer supportIf you have a problem with any Tivoli product, you can contact Customer Support.See Tivoli Customer Support Handbook at the following Web site:

http://www.tivoli.com/support/handbook

The handbook provides information about how to contact Tivoli CustomerSupport, depending on the severity of your problem, and the followinginformation:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv What information you should gather before contacting support

Conventions used in this guideThis guide uses several typeface conventions for special terms and actions. Theseconventions have the following meaning:

Bold Commands, keywords, authorization roles, interface controls, and otherinformation that you must use literally are in bold.

Italics Variables for values that you must provide, new terms, and words andphrases that are emphasized are in italics.

MonospaceCode examples, output, and system messages are in a monospace font.

This guide uses the UNIX convention for specifying environment variables and fordirectory notation:v When using the Windows® command line, replace $variable with %variable% for

environment variables and replace each forward slash (/) with a backslash (\) indirectory paths.

v When using the bash shell on Windows, use the UNIX conventions.

viii IBM Tivoli Configuration Manager: Planning and Installation

http://www.tivoli.com/support/survey

http://www.tivoli.com/support/handbook

Chapter 1. Overview of configuration management

The primary components of IBM Tivoli Configuration Manager are Inventory andSoftware Distribution. The other components provided by IBM TivoliConfiguration Manager can be considered subcomponents, or services, of one ofthese components. For information about how these components and servicesinterrelate to create a configuration management environment within a Tivolienvironment, see Introducing IBM Tivoli Configuration Manager.

These components and services can be installed in a Tivoli environment on thefollowing types of Tivoli managed resources in a Tivoli management region (Tivoliregion):v Tivoli management region server (Tivoli server), which is considered to be a

managed nodev Managed node, which can also be configured as a gateway, a repeater, or bothv Endpoint

Note: There is no difference between the software used to create a Tivoli server ormanaged node. The difference between a Tivoli server and a managed nodeis that the Tivoli server maintains the object database for the entire Tivoliregion while each managed node maintains a local object database.

Basic Tivoli environmentThe Tivoli server and managed nodes are created by installing Tivoli ManagementFramework. Endpoints are created by installing the endpoint services and selectTivoli Management Framework software on a system. A single system can be thehost for a managed node, a gateway, a repeater, and multiple endpoints. Whenthese managed resources are installed in your distributed network, they becomeyour Tivoli environment.

Your Tivoli environment can be created before installing IBM Tivoli ConfigurationManager, or it can be started during the installation of IBM Tivoli ConfigurationManager. If you currently are using Tivoli Enterprise software to manage yourdistributed network, you already have a Tivoli environment and can use IBMTivoli Configuration Manager to upgrade your Tivoli environment to the currentlevel.

For information required to understand how to create or upgrade your Tivolienvironment before installing or upgrading IBM Tivoli Configuration Manager, seeTivoli Management Framework Planning for Deployment and Tivoli EnterpriseInstallation Guide.

For information about creating a Tivoli server with the components of IBM TivoliConfiguration Manager on it, use the information and instructions provided in thisdocument. Even if you are using the installation programs provided by IBM TivoliConfiguration Manager to create a Tivoli server, you still need to create theremainder of your Tivoli environment using the information and instructions inTivoli Management Framework Planning for Deployment and Tivoli EnterpriseInstallation Guide.

© Copyright IBM Corp. 2002 1

For information about upgrading your Tivoli environment with the most currentlevel of Tivoli Management Framework and IBM Tivoli Configuration Manager,use the information and instructions provided in this document.

Note: This guide provides information about installing and upgrading IBM TivoliConfiguration Manager, provided that your Tivoli environment meets thefollowing requirements:v Tivoli Management Framework, Version 3.7 Revision B, or greaterv Tivoli Inventory, Version 4.0, or greaterv Tivoli Software Distribution, Version 4.1, or greater

If you are at an older version than the ones listed, you need to upgrade your Tivolienvironment to this minimum level to use the installation mechanisms andinformation documented in this guide. To get to these levels, see IBM TivoliConfiguration Manager Upgrade Scenarios. You can access this document from theTivoli Field Guides Web site:


Tivoli server components and servicesThe following components must be installed on the Tivoli server:

Activity PlannerInstalls the Activity Planner component. This component relies on aRelational Database Management System (RDBMS) Interface Module (RIM)object and relies on configured tablespace in the planner repository.

Change ManagerInstalls the Change Manager component. This component relies on a RIMobject and relies on configured tablespace in the ccm repository.

Enterprise Directory Query FacilityInstalls the Enterprise Directory Query Facility component. Thiscomponent relies on a preconfigured Lightweight Directory Access Protocol(LDAP) directory server. This component is used with the ChangeManager component and enables a Change Manager administrator to useinformation stored in one or more directory servers.

InventoryInstalls the Inventory component. The component relies on RIM objectsand relies on configured tablespace in the configuration repository.

Resource ManagerInstalls the Resource Manager component. This component relies on a RIMobject and relies on configured tables in the configuration repository.

Scalable Collection ServiceInstalls the Scalable Collection Service patch. This patch is required beforeyou install the Inventory components.

Software DistributionInstalls the Software Distribution component. This component includes thesource host capability, the historical database feature, and the IBM TivoliEnterprise Console® integration.

Web InfrastructureInstalls the Web Infrastructure component. This component allowsadministrators to create Web objects that can be used through a Web

2 IBM Tivoli Configuration Manager: Planning and Installation


browser to perform certain configuration management operations. Thiscomponent is used with the Web Interface component that is installed onendpoints.

You must install these components on the Tivoli server before you can install themon a managed node or before you can install the associated gateway component ona gateway. For example, you must install the Software Distribution component onthe Tivoli server before you can install either the Software Distribution or SoftwareDistribution Gateway component on any managed node in the local Tivoli region.

Managed node components and servicesThe following components can be installed on managed nodes:

Activity PlannerInstalls the Activity Planner component. Install this component only onmanaged nodes where you plan to create activity plans, run ActivityPlanner commands, or run the Activity Planner administrative interface.

Change ManagerInstalls the Change Manager component. Install this component only onmanaged nodes where you plan to run the Change Manager administrativeinterface.

InventoryInstalls the inventory component. Install this component on each managednode where you plan to create inventory profiles or run inventorycommands, on the managed node that is the Inventory data handler host,and on the managed node that is the Inventory callback host.

Inventory GatewayInstalls the files that enable a gateway to recognize inventory methods,download these methods to endpoints, and run methods to perform therequested inventory action. Install this component on all gateways.

Resource Manager GatewayInstalls the files that enable a gateway to recognize resource managementmethods, download these methods to endpoints, and run resourcemanagement actions. Install this component on all gateways.

Scalable Collection ServiceInstalls the Scalable Collection Service patch. This patch is required beforeyou install the Inventory components. Install this patch on each gatewaythat connects to endpoints to be scanned, on each repeater that you wantto act as a collector, and on each gateway that connects to the WebGateway components.

Software DistributionInstalls the software distribution component. Install this component onlyonly managed nodes that you plan to be new source hosts.

Software Distribution GatewayInstalls the files that enable a gateway to recognize software distributionmethods, download these methods to endpoints, and run the methods toperform the requested software distribution operation. Install thiscomponent on all gateways.

Chapter 1. Overview of configuration management 3

Software Package EditorInstalls the files that enable the Tivoli desktop to launch the SoftwarePackage Editor. This component enables you to use to create and testsoftware packages.

Note: This component is not supported on NetWare or OS/2® operatingsystems.

Endpoint components and servicesComponents and services installed on endpoints use software package blocks(SPBs) as their installation image. The majority of these components can beinstalled using an interactive session of the provided installation programs. Youcan, however, install these images from the SPBs using a profile distribution fromthe Tivoli server or by installing them locally using a disconnected SPB installation.

The following components can be installed on endpoints:

Software Package EditorInstalls the files that enable you to use the Software Package Editor whennot connected to the Tivoli environment. This component enables you tocreate and test software packages.

Software Distribution Pristine ToolInstalls the files for the Software Distribution Pristine Tool. This toolenables you to create a repository and diskette to remotely install anoperating system.

Note: This tool is supported on OS/2 and Windows operating systemsonly.

Web GatewayInstalls the Web Gateway component. This component enables you toaccess Web objects and perform device management in the extended Tivolienvironment.

Note: Although this component is called Web Gateway, it is installed onan endpoint.

Tivoli desktopInstalls Tivoli Desktop for Windows. When installing this component, youcan also install the required software required by the administrativeinterfaces. These interfaces are used by the following IBM TivoliConfiguration Manager components:v Activity Plannerv Change Managerv Inventoryv Software Distribution

Web InterfacesInstalls the Web Interfaces component. When installing this component,you can also install the associated plug-in software. These plug-ins areused by the following IBM Tivoli Configuration Manager components:v Inventoryv Software Distribution


Resources in a configuration management environmentThe components of IBM Tivoli Configuration Manager rely on the resources andmanagement concepts provided by Tivoli Management Framework. Thesecomponents support the concept of management by subscription, which is managingnetwork resources by creating profiles and distributing them to subscribers(targets). With the use of the Web Interface component, you can perform pulloperations from a Web browser.

The following sections provide overview information and figures about thecomponents and services of IBM Tivoli Configuration Manager, and it combines allthese overviews into a single conceptual resource model.

Resources used for inventory scansWhen inventory profiles are distributed to their targets, inventory scans are doneand the results are collected.

Figure 1 shows the relationship among the Inventory components. An inventoryprofile is distributed through the repeater hierarchy to its targets. The inventoryscan is performed on each target and the information is returned through thecollector hierarchy to the inventory data handler. The data passes from theinventory data handler through the RIM host to the configuration repository on theRDBMS server. Queries can be run against the stored data in the configurationrepository.

Scalable Collection Service (SCS) manages the collection of data in a Tivolienvironment from the endpoint, through the repeater hierarchy, to the RDBMS.

Resources used for software distributionsWhen software packages are distributed to their targets, the software is installedon these systems.

Inventoryserver

Queries

Gatewaycollector

Gatewaycollector

EndpointsEndpoints Endpoints

Gatewaycollector

Managed nodecollector

Datahandler

RDBMSserver

RIM hostRIM hostCallbackobject

Collection path

Collection pathwithout SCS

Query path

Profile path

Figure 1. Inventory components and their relationships


Figure 2 shows the relationship among the Software Distribution components. Asoftware package is created and stored on a source host. A software distributionprofile is distributed through the repeater hierarchy to its targets. The results of thedistribution are returned through the repeater hierarchy to the configurationrepository. Queries can be run against the stored data in the configurationrepository.

Resources used for resource managementWhen software distributions or inventory scans are distributed to pervasivedevices, they need to be processed and handled by the Web Gateway component.

Figure 3 on page 7 shows the relationship among the Resource Manager and WebGateway components. Resource management operations are performed against theresource gateway (the Web Gateway component) that maintains a list of enrolleddevices. Notification of these operations are returned through the repeaterhierarchy using the scalable collection service (as shown in Figure 1 on page 5) tothe configuration repository.

Source host Software Distributionserver

Software PackageEditor

RDMBSserver

Software DistributionGateway

RIM host

Endpoint Endpoint Endpoint

Queries

Figure 2. Software Distribution components and their relationships


Resources used for Web operationsWhen software distributions, inventory scans, or other IBM Tivoli ConfigurationManager operations need to be performed from a Web browser, users can pull thedistributions from a WebSphere® Application Server. Before accessing these Webobjects, a user is authenticated and granted permission to the Web objects throughIBM Tivoli Access Manager WebSEAL.

Figure 4 on page 8 shows the relationship among the Web Gateway and WebInterface components. In this figure, the Web Gateway database, Web Gatewayserver, Web server, WebSphere Application Server, IBM Tivoli Access Manager, andIBM Tivoli Access Manager WebSEAL are on the same system. The DB2 database ison another server. In this figure, the following process flow occurs:1. A Tivoli administrator publishes a Web object using the wweb command.2. A user from a workstation connects to the Web server and is prompted for a

user ID and password.3. The user provides these options and the request is forwarded for validation.4. If the user is authenticated and authorized, a Web page is displayed that

contains the available Web objects.

Resource Managergateway

WebGateway

WebGateway

Resource Managergateway

ResourceManager server

RDBMSserver

DB2server

RIM host

pervasive devices

Figure 3. Resource Manager and Web Gateway components and their relationships


Resources used for configuration managementUnderstanding the components and services of IBM Tivoli Configuration Managerand their relationships is important to the planning and installation processes.Figure 5 on page 9 combines the resources used for the following operations:v Inventory scansv Software distributionsv Resource managementv Web operations

In addition to combining these operations, Figure 5 on page 9 adds the followingcomponents:v Activity Planner used for defining, scheduling, and monitoring activity plansv Change Manager with Activity Planner used for software distributions and

change managementv Enterprise Directory Query Facility with an LDAP server used for user

management

Web Gateway/Web InterfacesHTTP/WebSphere server

Access Manager/WebSEAL server

DB2 server

Tivoliserver

Browser

wweb publish

Figure 4. Web Interface components and their relationships


To support this example configuration shown in Figure 5, the software listed inTable 1 on page 10 is installed and configured on the listed systems.

Tivoli server

MN1

EP1 EP2

GW1 GW2

MN2 MN3

GatewayCollector

GatewayCollector

EndpointWeb Gateway

Resource collectorWeb server

WebSphere serverDB2 client

EndpointWeb Gateway

Resource collectorWeb server

WebSphere serverDB2 client

Web InterfacesAccess Manager

WebSEAL

Managed nodeSource host

Software package editor

Managed nodeData handler

Callback object

Queries

RDBMSserver

DB2 server

LDAPserver

Managed nodeRIM host

Pervasive devices Web browser

Figure 5. IBM Tivoli Configuration Manager resources and their relationships


Table 1. Resources used by IBM Tivoli Configuration Manager and their required software by system

Label Resources Installed Software Comments

Tivoliserver

Tivoli server v Tivoli ManagementFramework

v Java 1.3 for Tivoli

v Java Help 1.0 for Tivoli

v Java Client Framework forTivoli

v Distribution Status console

v Activity Planner

v Change Manager

v Enterprise Directory QueryFacility

v Inventory

v Resource Manager

v Scalable Collection Service

v Software Distribution

v Web Infrastructure

The installation of this software creates theRIM objects on the RIM host (MN3). For thisinstallation to complete successfully, MN3must exist before installing any softwarewhich requires one of these RIM objects.

The Web Infrastructure component that isinstalled on the Tivoli server is the WebInterfaces component.

MN1 Managed nodeSource host

v Tivoli ManagementFramework

v Java 1.3 for Tivoli

v Java Client Framework forTivoli

v Java RDBMS Interface Module

v Activity Planner

v Change Manager

v Software Distribution

v Software Package Editor

Installing the Software Distributioncomponent enables this system to be asource host.

MN2 Managed nodeData handlerCallback object


v Inventory


Installing the Inventory and ScalableCollection Service components enable thismanaged node to be defined as theinventory data handler and callback object.

MN3 Managed nodeRIM host


v RDBMS client software

This managed node is the RIM host for thefollowing RIM objects needed IBM TivoliConfiguration Manager:

v planner

v ccm

v invdh_1

v inv_query

v trm

v mdist2

GW1 Managed nodeGateway


v Inventory Gateway

v Resource Manager Gateway


v Software Distribution Gateway

Run the wcrtgate command or use the Tivolidesktop to create the gateway.


Table 1. Resources used by IBM Tivoli Configuration Manager and their required software by system (continued)

Label Resources Installed Software Comments

GW2 Managed nodeGateway


v Inventory Gateway


v Software Distribution Gateway

Run the wcrtgate command or use the Tivolidesktop to create the gateway.

EP1 Endpoint v Tivoli endpoint

v DB2 client

v IBM HTTP Server

v WebSphere Application Server

v Web Gateway database

v Web Gateway server

The software on this endpoint supportresource management of pervasive devices.Support of pervasive devices is handledthrough an enrollment process.

EP2 Endpoint v Tivoli endpoint

v DB2 client

v IBM HTTP Server

v WebSphere Application Server

v Access Manager

v Access Manager WebSEAL

v Web Gateway database

v Web Gateway server

v Web Interfaces

v Inventory plug-in

v Software Distribution plug-in

The software installed on this endpointsupport Web operations from a browser.Before being granted access to the Webobjects, a user must be authenticated andauthorized through IBM Tivoli AccessManager and WebSEAL.


Chapter 2. Planning a configuration management environment

The considerations that apply to planning a Tivoli environment, as documented inTivoli Management Framework Planning for Deployment, apply to planning aconfiguration management environment. This chapter provides additionalconsiderations that might require changes to your overall deployment plan.Depending on the contents of your overall deployment plan, different installationand upgrade procedures might be required to create or maintain your Tivolienvironment.

Creating a deployment planCreating a deployment plan is essential to creating and installing a configurationmanagement environment. The basic considerations for creating a deployment planfor a Tivoli environment are provided in Tivoli Management Framework Planning forDeployment. This document covers all the planning considerations and providesscenarios for creating a comprehensive deployment plan. At a minimum, you needto gather the following information before installing any software:v Base hardware and software requirements for Tivoli Management Framework

and IBM Tivoli Configuration Manager.This information is provided in Tivoli Management Framework Release Notes andIBM Tivoli Configuration Manager Release Notes.

v Whether the computer systems in your distributed network can support thisnew software, whether these systems can be upgraded to meet your businessneeds, or whether new systems need to be obtained.

v Which IBM Tivoli Configuration Manager components to install on whichcomputer systems in your distributed network to support your business needsand whether they have additional third-party software requirements.This information is provided in IBM Tivoli Configuration Manager Release Notes,Introducing IBM Tivoli Configuration Manager, and this document.

For each system where you plan to install components of IBM Tivoli ConfigurationManager, you should also provide the following information:v Host namev Operating systemv Available memory and available disk spacev Which components of IBM Tivoli Configuration Manager to install

To help you create your deployment plan, you can use the information in“Planning worksheet” on page 95.

After creating your deployment plan and before starting the installation of IBMTivoli Configuration Manager or the upgrade of any IBM Tivoli ConfigurationManager component, complete the following steps:1. Read Tivoli Management Framework Release Notes and IBM Tivoli Configuration

Manager Release Notes to ensure that all systems where you plan to install orupgrade components of IBM Tivoli Configuration Manager meet the hardwareand software requirements and meet the software prerequisites.

2. If you are upgrading components of IBM Tivoli Configuration Manager, Version4.2, or you already installed Tivoli Management Framework, back up the Tivoli


object database for all managed nodes, including the Tivoli management regionserver (Tivoli server) in the Tivoli management region (Tivoli region).Having a backup enables you to return the Tivoli object database on the Tivoliserver and all managed nodes to a preinstallation state if non-recoverableproblems are encountered during an installation or upgrade. For additionalinformation on backing up a Tivoli environment, see Tivoli ManagementFramework Maintenance and Troubleshooting Guide.

Using RIM and the RDBMSSeveral IBM Tivoli Configuration Manager components store information in aRelational Database Management System (RDBMS). During the installation of IBMTivoli Configuration Manager, several databases, known as repositories, are createdin the RDBMS by running SQL admin scripts:v The ccm repository, which is used by the Change Manager component.v The inv_db database, which is used by the Inventory, Resource Manager, and

Software Distribution components. If the Resource Manager component isinstalled before Inventory component, the trm database is created for use by theResource Manager component.

v The planner repository, which is used by the Activity Planner component.

These repositories can be created in a single database (the cm_db database) or eachrepository can be created in separate databases.

During the installation of Tivoli Management Framework, the mdist2 repository iscreated. This repository is used to track software distributions and other profiledistributions. For information about this repository, see Tivoli Enterprise InstallationGuide.

The connection and communication between IBM Tivoli Configuration Managerand tablespaces in the repositories use RDBMS Interface Module (RIM) objects. Bydefault, all the RIM objects are created on the same managed node (the Tivoliserver).

For additional information about using RIM objects, see Tivoli Enterprise InstallationGuide and Tivoli Management Framework Release Notes.

Selecting RIM hostsA RIM host is a managed node where the RIM object is created. RIM objects arecreated during installation. When deciding which managed nodes are to be RIMhosts, consider the following requirements:v The managed node must be local to the Tivoli region.v The managed node must be preconfigured with the RDBMS client or server

software.

Note: Do not install the RDBMS server software on the RIM host unless thismachine is designated solely for RDBMS usage and no other Tivolioperations. When you add the number of transactions performed on theRDBMS server to those performed on the RIM host, the number of overalltransactions might impact the optimal performance of your Tivolienvironment by exceeding network throughput.

Although RIM objects are created during installation, you can create additionalRIM objects using the wcrtrim command or move a RIM object from one managed


node to another using the wmvrim command. For information on these and otherRIM commands, see Tivoli Management Framework Reference Manual. For informationabout using RIM objects with the Inventory component, see IBM TivoliConfiguration Manager User’s Guide for Inventory.

Selecting the RDBMS serverThe RDBMS server contains the repositories that are used to store and retrieveconfiguration management data. When deciding on which machine to install theRDBMS server, consider the following requirements:v There must be a TCP/IP connection between the RIM host and the RDBMS

server.v The RDBMS server does not need to be on a machine managed by Tivoli

Management Framework.v The RDBMS server must be in the same network as the Tivoli region.v There must be enough disk space in the RDBMS to handle the amount of data

stored in the repositories.v Multiple Tivoli regions can use a single RDBMS.

Configuring RIM objectsDuring installation, you are asked to provide RIM configuration options. Thisinformation is used to create the RIM object and register it in the Tivoli objectdatabase. Therefore, you should install and configure the RDBMS before installingIBM Tivoli Configuration Manager. For general details, see the RIM objectinformation in Tivoli Enterprise Installation Guide and Tivoli Management FrameworkRelease Notes. For information about using RIM objects with the Inventorycomponent, see IBM Tivoli Configuration Manager User’s Guide for Inventory.

When using a single RDBMS for multiple Tivoli regions, you need to ensure thatthe settings for each of the RIM objects that are local to each Tivoli region are thesame. The only exception is the name of the RIM host. If the settings are not thesame, use the wgetrim, wsetrim, and wsetrimpw commands to synchronize allrequired RIM objects. For information on these commands, see Tivoli ManagementFramework Reference Manual.

RIM objects used for configuration managementRIM objects are associated with or used by the following IBM Tivoli ConfigurationManager components:v Activity Plannerv Change Managerv Inventoryv Resource Managerv Software Distribution

Table 2 shows the default RIM objects and passwords for each of thesecomponents.

Table 2. RIM objects and passwords for IBM Tivoli Configuration Manager components

Component RIM objectDefault user

nameDefault

passwordComments

ActivityPlanner

planner planner planner

Chapter 2. Planning a configuration management environment 15

Table 2. RIM objects and passwords for IBM Tivoli Configuration Managercomponents (continued)

Component RIM objectDefault user

nameDefault

passwordComments

ChangeManager

ccm tivoli tivoli

DistributionStatus

mdist2 mdstatus mdstatus

Inventory invdh_1 invtiv tivoli Used by the inventory datahandler to write scan datato the RDBMS.

This RIM object uses theinv_db database.

inv_query invtiv tivoli Used to perform queriesagainst the RDBMS. Thewinvfilter, winvpackage,winvrmnode, winvsig, andwinvupdatesid commandsand the Inventoryadministrative interface usethis RIM object.

This RIM object uses theinv_db database.

ResourceManager

trm tivoli tivoli Created only if theinv_query RIM object doesnot exist in the local Tivoliregion. If inv_query isdefined, the ResourceManager component usesthe inv_query RIM object.Otherwise, the trm RIMobject is created.

For additional information about these RIM objects and their associatedrepositories, see Chapter 5, “Working with repositories and queries” on page 67.

Synchronizing RIM objects with RDBMS databasesThe password and user for each RIM object must be the same as the password anduser of the RDBMS database that it accesses. In other words, the RIM passwordand the RDBMS database password need to be the same, and the user name forthe RIM object and the user name for the RDBMS must also match. Therefore, youmust change the password and user of each RIM object to match that of itsrepository.

When you change the RDBMS database password or user, you must also changethe password for the RIM object.

To change the password for a RIM object, use the wsetrimpw command. To changethe user for a RIM object, use the wsetrim command. For information about thesecommands, see Tivoli Management Framework Reference Manual.


Software requirements for the Web Gateway componentThe Web Gateway component uses an IBM DB2® database to store and retrievedevice information used by the components of IBM Tivoli Configuration Manager.The Web Gateway component does not require a RIM object to connect to the DB2server. The Web Gateway component uses native DB2 services.

Depending on whether you are using the Web Gateway component for resourcemanagement of devices or for Web object access, there are different softwareprerequisites.

Software requirements for resource managementBefore installing the Web Gateway component for resource management of devices,you must install and configure the following software:v IBM DB2v IBM WebSphere® Application Server (with IBM HTTP Server)

To optionally protect device management resources, you can use IBM Tivoli AccessManager WebSEAL.

Install and configure IBM DB2 and IBM WebSphere Application Server followingthe product documentation. If you are protecting device management resources,install and configure IBM Tivoli Access Manager and IBM Tivoli Access ManagerWebSEAL following the product documentation. Installation and generalconfiguration information is not provided in this document.

Note: During the installation of the Web Gateway server, do not specify any IBMTivoli Access Manager or WebSEAL information.

For the latest information about supported versions and required software updates,see IBM Tivoli Configuration Manager Release Notes.

Software requirements for Web access

Before installing the Web Gateway component for Web access, you need to installand configure the following software:v IBM DB2v IBM WebSphere Application Server (with IBM HTTP Server)v IBM Tivoli Access Managerv IBM Tivoli Access Manager WebSEAL

Install and configure DB2, WebSphere Application Server, Tivoli Access Manager,and Tivoli Access Manager WebSEAL following the product documentation.

Note: Only the PDJRTE component of IBM Tivoli Access Manager is required onthe same machine as the Web Gateway.

Installation and general configuration information is not provided in thisdocument. For the latest information about supported versions and requiredsoftware updates, see IBM Tivoli Configuration Manager Release Notes.


Creating the DB2 users for the Web Gateway componentThe Web Gateway component requires that the following users exist on any systemwhere the Web Gateway database is installed:

dmsadminThe DB2 user who owns the database tables in the Web Gateway database

dmsuserThe DB2 user who accesses and queries the database tables in the WebGateway database

Creating the DB2 users on UNIX operating systemsUse the following instructions to create the DB2 users for each of the supportedUNIX operating systems:

For AIX®

Issue the following commands:mkuser pgrp=’db2iadm1’ home=’/home/dmsadmin’ shell=’/bin/ksh’ dmsadminmkuser pgrp=’db2iadm1’ home=’/home/dmsuser’ shell=’/bin/ksh’ dmsuser

For Linux on IntelIssue the following commands:adduser -d /home/dmsadmin -g db2iadm1 -s /bin/ksh dmsadminadduser -d /home/dmsuser -g db2iadm1 -s /bin/ksh dmsuser

For SolarisIssue the following commands:useradd -d /home/dmsadmin -g db2iadm1 -s /bin/ksh dmsadminuseradd -d /home/dmsuser -g db2iadm1 -s /bin/ksh dmsuser

After creating these users, add the following lines to the $HOME/.profile file foreach of these users:

if [ -f ~db2inst1/sqllib/db2profile ]then. ~db2inst1/sqllib/db2profilefi

Creating the DB2 users on Windows operating systemsUse the following instructions to create the DB2 users on each of the supportedWindows operating systems:

For Windows 2000

1. From the Start menu, select Programs → Administrative Tools →Computer Management.

2. Select Local Users and Groups.3. Right-click the Users folder;4. Create the new local users as follows:

v The dmsadmin user with Administrative privilegesv The dmsuser user with User privileges

For details about User Rights, see the Windows documentation.

For Windows NT

1. From the Start menu, select Programs → Administrative Tools(Common) → User Management to display the User Manager window.


2. From the User menu, select New User to display the New Userwindow.

3. Create the new local users as follows:v The dmsadmin user with Administrative privilegesv The dmsuser user with User privileges

For details about User Rights, see the Windows documentation.

Using the Web Gateway component with IBM Tivoli Access ManagerWhen using the Web Gateway component to access Web objects, you must installand configure IBM Tivoli Access Manager and IBM Tivoli Access ManagerWebSEAL. To optionally use the Web Gateway component to protect devicemanagement resources, you must install and configure IBM Tivoli Access Managerand IBM Tivoli Access Manager WebSEAL

When installing the Web Gateway server for accessing Web objects, enable theWebSEAL security manager by setting the Enable security field to true. Wheninstalling the Web Gateway server for protecting device management resources, donot enable the WebSEAL security manager or specify any IBM Tivoli AccessManager or IBM Tivoli Access Manager WebSEAL configuration information.

For information about installing IBM Tivoli Access Manager and IBM Tivoli AccessManager WebSEAL, use the instruction in IBM Tivoli Access Manager BaseInstallation Guide and IBM Tivoli Access Manager WebSEAL Installation Guide.

Configuring the Java Runtime EnvironmentYou need to install and configure the Java Runtime Environment provided by IBMTivoli Access Manager. For each Web Gateway server, enter the followingcommand:

For Windows operating systemspdjrtecfg -action config -java_home drive:%WAS_HOME%\java\jre

For UNIX operating systemspdjrtecfg -action config -java_home $WAS_HOME/java/jre

Note: To successfully run the pdjrtecfg command, a Java binary at the 1.3.1 level,the Java binary for the WebSphere Application Server must be the first entryin your PATH statement. On AIX operating systems for example, enter thefollowing command:export PATH=$WAS_HOME/java/jre/bin:$PATH

Creating SSL configurations and keystoresTo create the SSL configurations file and keystores, run the following command oneach Web Gateway server:java com.tivoli.mts.SvrSslCfg application_name security_password

policy_server_hostname authorization_server_hostname policy_server_portauthorization_server_port configuration_file keystore_file operation

where:

application_nameThe name of the Access Manager application to create and associate withthe SSL communication. The application name must be unique. Otherinstances of the application, which are running on this or other systems,


must each be given a unique name. A distinguished name can be usedwhen an LDAP-based user registry is used with Access Manager.

security_passwordThe password associated with master security user.

policy_server_hostnameThe name of the system where the Access Manager policy server process,ivmgrd, is running.

authorization_server_hostnameThe name of the system where the Access Manager authorization serverprocess, ivacld, is running. This can be the same system as the policyserver.

policy_server_portThe port used for SSL communication with the policy server. The default is7135.

authorization_server_portThe port used for SSL communication with the authorization server. Thedefault is 7136.

configuration_fileThe URL to the configuration file. The URL must use the file:/// format.The default is java_home/PdPerm.properties. The PDPerm.properties andPdPerm.ks files must be in the same directory.

keystore_fileThe URL to the keystore file. The URL must use the file:/// format. Thedefault is java_home/PdPerm.ks. The PDPerm.properties and PdPerm.ksfiles must be in the same directory.

operationThe operation to perform. Valid operations are create, replace, or unconfig.

Note: To successfully run this command, ensure that $WAS_HOME/java/jre/binis the first entry for the PATH environment variable. On AIX operatingsystems for example, enter the following command:export PATH=$WAS_HOME/java/jre/bin:$PATH

For additional information, see IBM Tivoli Access Manager Authorization Java ClassesDeveloper’s Reference.

Configuring SSL connections with self-signed certificatesThe Change Manager component can use self-signed certificates for establishingSSL connections. Establishing an HTTPS connection to an SSL protocol server issuccessful only when the server certificate can be recognized. By default,certificates provided by Certificate Authorities (CA) are recognized by theWebSphere certificate repository. Self-signed certificates, however, might not berecognized. For an SSL connection using self-signed certificates to be establishedbetween the WebSEAL server and the WebSphere server, you need to extract theWebSEAL certificate and import this WebSEAL certificate into the WebSpherekeystore.

Extracting self-signed certificatesYou can extract certificates using Microsoft Internet Explorer or using the iKeymanutility. Independent of how you extract the certificate, use Base 64 encoding.

When using Internet Explorer to extract the certificate, perform the following steps:


1. Connect to the Web site that opens the requested SSL connected.2. Double-click the padlock icon in the status bar to open the Certificate window.3. Click the Details tab to display the current certificate.4. Click Copy to File to open the Certificate Manager Export Wizard.5. Use this wizard to extract the certificate to the hard drive.

When using the iKeyman key management utility, perform the following steps:1. On the Web server, locate the SSL certificate repository. The default file name is

the key.kdb database file.

Note: To determine the name of this database file, open the httpd.conf file, Thevalue for the Keyfile keyword in the VirtualHost definition is the nameof the database file.

2. Extract the self-signed certificate for the SSL connection using the iKeymanutility.

For information about using the iKeyman, see Secure Socket Layer Introduction andiKeyman User’s Guide. This documented is shipped only on the IBM Tivoli AccessManager documentation CD.

Importing self-signed certificatesUse the keytool utility to import the certificate to the WebSphere keystore byperforming the following steps:1. On the WebSphere server, change to the $WAS_HOME/java/jre/lib/security

directory.2. Run the following command:

keytool -import -file extracted_certificate -keystore cacerts

Configuring the WebSEAL serverIf you are using WebSEAL to protect both Web objects (required) and devicemanagement resources (optional), you need to maintain two WebSEAL instancesbecause of the different authentication requirements. For information aboutcreating and configuring multiple WebSEAL instances on a single machine, seeIBM Tivoli Access Manager WebSEAL Administration Guide.

Web access uses forms authentication, and resource management uses basicauthentication. To configure the WebSEAL server, complete the following steps:1. Modify the webseald.conf file.

For Web accessEnsure that the file contains the following entries:ba-auth=noneforms-auth=httpsuse-same-session=yes

For resource managementEnsure that the file contains the following entries:ba-auth=httpforms-auth=none

If you change any values in the webseald.conf file, you must restart theWebSEAL server.

2. Find the host name of the WebSEAL server by entering the followingcommands:


pdadmin -a sec_master -p passwordserver listexit

3. Configure query_contents on the Web Gateway server using the instruction inIBM Tivoli Access Manager WebSEAL Administration Guide. The basic steps, byoperating system, are as follows:

For Windows operating systems

a. Copy the query_contents.exe file from the WebSEAL server to thec:\Program Files\IBM HTTP Server\cgi-bin directory.

b. Copy the query_contents.cfg file from the WebSEAL server to the%SystemRoot% directory.

c. Edit the query_contents.cfg to ensure that the docroot parameter isas follows:docroot="c:\Program Files\IBM HTTP Server\htdocs"

For UNIX operating systems

a. Copy the query_contents.sh file from the WebSEAL server to the/cgi-bin subdirectory on the Web server:

For Solaris/opt/IBMHTTPD/cgi-bin

For Linux/opt/IBMHTTPServer/cgi-bin

For AIX/usr/HTTPServer/cgi-bin

b. Rename query_contents.sh to query_contents by entering thefollowing command:mv query_contents.sh query_contents

c. Change access control to the query_contents file by entering thefollowing command:chmod 755 query_contents

d. Edit the query_contents file to ensure that the DOCROOTDIRvariable is as follows:DOCROOTDIR=’pwd’/../htdocs/en_US

This variable is set on line 83 of this filee. Edit the query_contents file to add the following entry after line 77:

SERVER_SOFTWARE=Apache

Note: Although the Web server is IBM HTTP Server, thedesignation for this Web server is Apache.

4. Create a junction for the WebSEAL server returned in step 2 on page 21:pdadmin -a sec_master -p passwordserver task WebSEAL_server create -j -c all -t tcp -h Web_Gateway_host

-p Web_Gateway_http_port junction_pointexit

Testing the WebSEAL configurationYou can test the WebSEAL configuration using either a browser or the pdadmincommand. To test from a browser, enter the following URL:http://localhost/cgi-bin/query_contents?dirlist=/


where localhost is the host name of the Web Gateway server. Running thisoperation should return a 100 return code and a list of the directories and files inthe document root directory of the Web server.

To test with the pdadmin command, enter the following commands:pdadmin -a sec_master -p passwordobject list /WebSEAL/host_name/junction_point

where host_name is the name of WebSEAL server and junction_point is the junctionpoint created in step 4 of “Configuring the WebSEAL server” on page 21. Runningthis command should return a list of protected directories and files.

Choosing where to install componentsBefore installing the components of IBM Tivoli Configuration Manager, you needto decide where to install the different components and services of IBM TivoliConfiguration Manager. The following sections provide guidelines for determiningwhere you need to install these components and services.

Choosing where to install the Inventory componentsOn managed nodes, you can install the Scalable Collection Service component, theInventory component, and the Inventory Gateway components. However, use thefollowing guidelines for creating your deployment plan:v Install both the Scalable Collection Service component and the Inventory

component on a managed node in the following situations:– An administrator uses the managed node to create or distribute inventory

profiles.– An administrator uses the managed node to run inventory commands.– The managed node hosts the inventory callback object.– The managed node hosts the inventory data handler.

v Install the Inventory Gateway component on any gateway that communicateswith endpoints that will be scanned.

Choosing where to install the Resource Manager componentsOn managed nodes, you can install both the Resource Manager and the ResourceManager Gateway components. However, use the following guidelines for creatingyour deployment plan:v Install the Resource Manager component on a managed node when an

administrator uses the managed node to run Resource Manager commands.v Install the Resource Manager Gateway component on any gateway that

communicates with endpoints where the Web Gateway component is installed.Endpoints where the Web Gateway component is installed are referred to asresource gateways.

Choosing where to install the Software Distributioncomponents

On managed nodes, you can install both the Software Distribution and theSoftware Distribution Gateway components. However, use the following guidelinesfor creating your deployment plan:v Install the Software Distribution component on a managed node in the following

situations:


– An administrator uses the managed node to run software distributioncommands.

– The managed node is used as a source host. To operate as a source host, themanaged node must fulfill the following requirements:- It must either be a gateway or configured as a standalone repeater.

Tivoli Management Framework provides the mechanisms for creating andconfiguring gateways and repeaters. For details, refer to Tivoli ManagementFramework Planning for Deployment and Tivoli Enterprise Installation Guide.

- It has sufficient disk space to store the software package blocks and filereferences in the software packages to be distributed.

- It cannot be an OS/2 or NetWare managed node.v Install the Software Distribution Gateway component on any gateway that

communicates with endpoints that receive a software distribution.

Choosing where to install the Web Gateway componentThe Web Gateway component can be installed on any endpoint in the Tivoliregion. The endpoint must have sufficient disk space and memory for thiscomponent. This information is provided in IBM Tivoli Configuration ManagerRelease Notes. You can use the Web Gateway component for two primary purposes:v Connect devices and users in the extended Tivoli environment for configuration

managementv Access Web objects in the Tivoli environment from a Web browser

The Web Gateway component has two separate installation images, the WebGateway database and the Web Gateway server. Before installing a Web Gatewayserver, you must install a Web Gateway database.

Web Gateway servers can function independently or as a cluster.v To function independently, each Web Gateway server must have its own Web

Gateway database. In this configuration, no information stored in the database isshared with any other installation of the Web Gateway component.

v To function as a cluster, a single Web Gateway database is shared by multipleinstallations of Web Gateway servers. The first installation of the Web Gatewayserver is the primary server in the cluster. Additional installations of WebGateway servers are secondary servers in the cluster. All secondary servers sharethe Web Gateway database of the primary server. In this configuration,communication among the Tivoli applications is performed by the primaryserver while the secondary servers can process incoming requests. On the Tivoliserver or a managed node where the Resource Manager component is installed,you must run the wresgw command to configure and enable auto-enrollment forthe primary Web Gateway server in the cluster. For details about the wresgwcommand, see IBM Tivoli Configuration Manager User’s Guide for DeploymentServices.

During the installation of a primary Web Gateway server, whether in anindependent configuration or in a cluster configuration, specify the location of theWeb Gateway database. During the installation of additional Web Gateway serversin a cluster configuration, specify the same location of the Web Gateway databaseas specified during the installation of the primary server. When prompted whetherthis server installation is for a cluster environment, specify false for the primaryserver and true for each secondary server. When used within a cluster, only theprimary server should have auto-enrollment enabled.


Using configuration management in connected Tivoli regionsThis section discusses the requirements for running inventory scans, distributingsoftware, and managing devices and users in connected Tivoli regions. If you planto use IBM Tivoli Configuration Manager among Tivoli regions, the followingconditions must be met:v You must install the IBM Tivoli Configuration Manager components in each

Tivoli region.v Each Tivoli region must have a local RIM host.v Each local RIM host in each Tivoli region must point to the same database. In

other words, each RIM host must have the same configuration settings.

Running inventory scans in connected Tivoli regions

Scalable Collection Service (SCS) uses the MDist 2 repeater hierarchy to obtainentry point information. Consider the scenario shown in Figure 6. You might havetwo Tivoli regions connected by a wide area network (WAN): Region A and RegionB. Region A contains the inventory data handler. A profile is distributed fromRegion A to endpoints in Region B. The gateway for the endpoints in Region Bcollects scan results from these endpoints. Next, the WAN entry point collectornode in Region A collects the scan results from the gateway in Region B and sendsthe data to the inventory data handler.

Profile distribution

Collection by gateway in Region B

Collection by collector node in Region A

Tivoli

Region B

Server

WAN

GatewayCollectorGatewayCollector

Endpoints

RIM HostInventory

Data Handler

Tivoli

Region A

Server

RDBMSServer

Managed NodeCollector

Endpoints


Endpoints


Figure 6. Using Inventory across Tivoli region boundaries


For information about connecting Tivoli regions and exchanging and updatingresources, see Tivoli Management Framework Planning for Deployment.

Distributing software in connected Tivoli regionsSoftware Distribution uses the MDist 2 repeater hierarchy. Ensure that the repeatersand switches in this hierarchy are correctly tuned to handle the softwaredistributions.

Although you might have the Software Distribution Gateway component installedin each Tivoli region, you must also install the Software Distribution component onthe Tivoli server in each region. When the targets of a software distribution are notin the local region, the gateway in the remote region does not know how tomanage the dependencies for the targets. Because software dependencies are notTivoli managed resources, they cannot be exchanged between connected Tivoliregions.

For information about connecting Tivoli regions and about exchanging andupdating resources, see Tivoli Management Framework Planning for Deployment.

Managing devices and users in connected Tivoli regionsResource management of devices and users can be used in connected Tivoliregions. In this configuration, you install Resource Manager in each Tivoli region,and share one database. With this approach, an administrator in the local Tivoliregion can perform the following operations:v Discover resources managed by remote endpoints and resource groupsv Create resources managed by remote endpoints and resource groupsv Modify resources managed by remote endpoints and resource groupsv Delete resources managed by remote endpoints and resource groups


Chapter 3. Planning for component installations

This chapter provides the following information:v Authorization roles required to install IBM Tivoli Configuration Managerv Installation sequence when installing the components of IBM Tivoli

Configuration Manager when using installation mechanisms other than the onesprovided by IBM Tivoli Configuration Manager

v The components of IBM Tivoli Configuration Manager and their availableinstallation image formats

v Installation options, prerequisites, and other installation concerns for eachcomponent of IBM Tivoli Configuration Manager

Authorization rolesTable 3 provides the context and authorization roles required to install any product.

Table 3. Required authorization roles for installing Tivoli Enterprise products

Activity Context Required Role

Install the installation imagesdirectly from the CD

Machine root access (on UNIX operating systems) ora member of the Administrators group (onWindows operating systems)

Install from the Tivolidesktop or command line

Tivoli region install_product or super

Install using Tivoli SoftwareInstallation Service

Tivoli region user plus one of the following roles: super,senior, or install_product

Installation sequence for componentsDepending on whether you use installation programs provided by IBM TivoliConfiguration Manager or the installation mechanisms provided by TivoliManagement Framework, the installation sequence is different.

Installation sequence using IBM Tivoli Configuration Managermechanisms

If you plan to use the installation programs provided by IBM Tivoli ConfigurationManager, follow your deployment plan and install the components in the followingsequence:1. Use the Server installation program provided by IBM Tivoli Configuration

Manager to perform the following operations:v Create the Tivoli management region server (Tivoli server)v Creates a gateway on the Tivoli serverv Install the required Java packages on the Tivoli serverv Install the required IBM Tivoli Configuration Manager components and

services on the Tivoli serverv Run the scripts to create and configure the RIM databases used by IBM

Tivoli Configuration Managerv Install the Inventory software signatures


2. On the Tivoli server or different system, use the Desktop installation programprovided by IBM Tivoli Configuration Manager to perform the followingoperations:v Install Tivoli Desktop for Windowsv Install the required IBM Tivoli Configuration Manager administrative

interfaces

At this point, you have a working Tivoli environment with a complete installationof IBM Tivoli Configuration Manager. You can now create managed nodes,gateways, and endpoints to create the remainder of your Tivoli region. Instructionsfor creating these resources are in Tivoli Enterprise Installation Guide.3. If you need to manage devices or have intranet access to Tivoli Web profiles,

use the Web Gateway installation program provided by IBM TivoliConfiguration Manager to perform the following operations:v Installs the required IBM Tivoli Configuration Manager on the required

endpoint and connects to designated gateway.v Run the scripts to create and configure the Web Gateway databasev Run the registration scripts to register the plug-ins

4. Use the Tivoli Management Framework installation mechanisms to install IBMTivoli Configuration Manager components on managed nodes and gateways.

Installation sequence using Tivoli Management Frameworkmechanisms

If you plan to manually install the components provided by IBM TivoliConfiguration Manager, follow your deployment plan and install the componentsin the following sequence:1. Create the Tivoli management region (Tivoli region) by first installing and

configuring Tivoli Management Framework on a server, which creates theTivoli management region server (Tivoli server), and then creating andconfiguring the remainder of the Tivoli region by creating managed nodes,gateways, repeaters, and endpoints. For planning information, see TivoliManagement Framework Planning for Deployment. For installation andconfiguration information, see Tivoli Enterprise Installation Guide.

2. Install the Java components:a. Install the Java 1.3.0 for Tivoli component on the Tivoli server and each

required managed node and endpoint.b. Install the Java Client Framework for Tivoli component on the Tivoli server

and each required managed node and endpoint.c. Install the Java RDBMS Interface Module on each required managed node.d. Install the JavaHelp component on each required managed node and

endpoint.3. Install the Inventory components:

a. Install the Scalable Collection Service patch as follows:v On the Tivoli serverv On each managed node where the Inventory component will be installedv On all gatewaysv On each managed node will be configured as a repeater

b. Install the Inventory component on the Tivoli server and each requiredmanaged node.

c. Install the Inventory Gateway component on each required gateway.


d. Install the software signatures. For details, see IBM Tivoli ConfigurationManager User’s Guide for Inventory.

4. Install the Software Distribution components:a. Install the Software Distribution component on the Tivoli server and each

required managed node.b. Install the Software Distribution Gateway component on each required

gateway.5. Install the Deployment Services components:

a. Install the Activity Planner component on the Tivoli server and eachrequired managed node.

b. Install the Change Manager component on the Tivoli server and eachrequired managed node.

c. Install the Resource Manager component on the Tivoli server for resourcemanagement on users.

d. Install the Resource Manager Gateway component and the ScalableCollection Service component on each required gateway for resourcemanagement of users.

e. Install the Enterprise Directory Query Facility component on the Tivoliserver.

6. Install the Web Gateway components to support Web object management:a. Install the Web Infrastructure component on the Tivoli server.b. Install the Web Gateway Database component on each required endpoint.c. Install the Web Gateway Server component on each required endpoint.d. Install the Web (Interface) Infrastructure on each required endpoint.e. Install the Inventory plug-in for Web Infrastructure on each required

endpoint.f. Install the Software Distribution plug-in for Web Infrastructure on each

required endpoint.

Ensure that Scalable Collection Service is installed on each gateway thatcommunicates with the endpoint where the Web Gateway component isinstalled.

7. Install the Web Gateway components to support device management:a. Install the Resource Manager component on the Tivoli server, if not already

installed for resource management of users.b. Install the Resource Manager Gateway component on each required

gateway, if not already installed for resource management of users.c. Install the Web Gateway Database component on each required endpoint, if

not already installed for Web object management.d. Install the Web Gateway Server component on each required endpoint, if

not already installed for Web object management.

Ensure that Scalable Collection Service is installed on each gateway thatcommunicates with the endpoint where the Web Gateway component isinstalled.

8. Install the Software Package Editor component an each required managed nodeor endpoint.

9. Install the Pristine Tool component on each required endpoint.

Chapter 3. Planning for component installations 29

Before installing several of these components, you might need to install one ormore Java components. The details about the combination of the Java componentswith the IBM Tivoli Configuration Manager components are detailed in“Installation options” on page 35.

Components of IBM Tivoli Configuration ManagerThe components of IBM Tivoli Configuration Manager can be installed throughmultiple mechanisms using different image formats. The primary image formatsare index files (.IND files) and software package blocks (SPBs).

Components installed from index filesTable 4 describes the components, used for installing IBM Tivoli ConfigurationManager, that are shipped on the IBM Tivoli Configuration Manager Server CD.

Table 4. Index files and tags used to install and uninstall components of IBM TivoliConfiguration Manager

.IND file Component name Tag

APM Activity Planner, Version 4.2 apm

CCM Change Manager, Version 4.2 ccm

QUERYDIR Enterprise Directory Query Facility, Version 4.2 directory_query_4.2

42_INV_F Inventory, Version 4.2 InventoryServer

42_GW_FR Inventory Gateway, Version 4.2 InventoryGateway

ALI_TRM Resource Manager, Version 4.2 TMF_TRM

LCF_TRM Resource Manager Gateway, Version 4.2 TMF_TRM_GW

MCOLLECT Scalable Collection Service, Version 4.1 TMF_DDC_4.1

SWDIS Software Distribution, Version 4.2 swdis

SWDISGW Software Distribution Gateway, Version 4.2 swdisgw

SWDISJPS Software Package Editor, Version 4.2 swdisjps

WEBUI Web Interface, Version 4.2 webui

Table 4 contains the following information:

.IND fileThe name of the index file that you use to install the component from thecommand line.

Component nameThe name of the component that is displayed when you install the productusing the Tivoli desktop or Tivoli Software Installation Service.

Tag The registered product tag that you use to uninstall the component withthe wuninst command as documented in “Uninstalling components usingthe wuninst command” on page 64.

Table 5 on page 31 describes the components, used for upgrading IBM TivoliConfiguration Manager, that are on the IBM Tivoli Configuration ManagerUpgrade CD.


Table 5. Index files and tags used to upgrade and uninstall components of IBM TivoliConfiguration Manager

.IND file Component name Tag

SWDAPMU Activity Planner Server Upgrade, Version 4.1 toVersion 4.2

apm_4.2

SWDAPMGU Activity Planner Upgrade, Version 4.1 to Version 4.2 apm_42

SWDCCMU Change Manager Server Upgrade, Version 4.1 toVersion 4.2

ccm_4.2

SWDCCMGU Change Manager Upgrade, Version 4.1 to 4.2 ccm_4.2

42_INV Inventory Upgrade, Version 4.0 to Version 4.2 InventoryServer

42_GW Inventory Gateway Upgrade, Version 4.0 to Version4.2

InventoryGateway

SWDSRVU Software Distribution Upgrade, Version 4.1 toVersion 4.2

swdis_4.2

SWDGWU Software Distribution Gateway Upgrade, Version 4.1to Version 4.2

swdisgw_4.2

SWDSHU Software Distribution Upgrade, Source Host Version4.1 to Version 4.2

swdis_4.2

SWDJPSU Software Package Editor Upgrade, Version 4.1 toVersion 4.2

swdisjps_4.2

Table 5 contains the following information:

.IND fileThe name of the index file that you use to upgrade the component fromthe command line.

Component nameThe name of the component that is displayed when you upgrade theproduct using the Tivoli desktop or Tivoli Software Installation Service.

Tag The registered product tag that you use to uninstall the component withthe wuninst command as documented in “Uninstalling components usingthe wuninst command” on page 64. The tag for uninstalling a productinstallation and a patch installation are the same. For some components,you can uninstall only the patch installation. To uninstall only the patchinstallation, use the information as documented in “Uninstallingcomponent using scripts” on page 64.

For information about reading and modifying index files, see Tivoli EnterpriseInstallation Guide.

Components installed from software package blocksSeveral IBM Tivoli Configuration Manager components can be installed usingsoftware package blocks (SPBs). These components are in the /SPB subdirectory onthe IBM Tivoli Configuration Manager CDs:v Java componentsv Web Gateway componentv Web Infrastructure componentv Tivoli endpointv Software Package Editor


v Pristine Toolv IBM Tivoli Configuration Manager administrative interfaces

These SPBs can be installed on endpoints in one of the following ways:v Using one of the provided installation programsv Distributing the SPB to the endpointv Using Software Distribution commands

Software packages for the Java componentsTable 6 lists the SPBs used to install the Java components used by the IBM TivoliConfiguration Manager components and services. These SPBs are located in the/SPB subdirectory on the IBM Tivoli Configuration Manager Desktop CD.

Table 6. Software packages for installing the Java components

.SPB file Description

Tivoli_JCF The software package for Java Client Framework

Tivoli_JHelp The software package for JavaHelp

Tivoli_JRE_AIX The software package for the Java RuntimeEnvironment for AIX operating systems

Tivoli_JRE_HP The software package for the Java RuntimeEnvironment for HP-UX operating environments

Tivoli_JRE_LINUX_IX86 The software package for the Java RuntimeEnvironment for Linux for Intel®

Tivoli_JRE_NT The software package for the Java RuntimeEnvironment for Windows operating systems

Tivoli_JRE_SOLARIS The software package for the Java RuntimeEnvironment for Solaris operating environments

Tivoli_JRIM The software package for the Java RDBMS InterfaceModule (Java RIM) object

You can also install these Java components using Tivoli Management Frameworkor Tivoli Software Installation Service. The index files used for installing thesecomponents are in the /JAVA subdirectory on the Tivoli Management FrameworkCD (2 of 2). For information about installing these components using TivoliManagement Framework or Tivoli Software Installation Service, see Tivoli EnterpriseInstallation Guide and Tivoli Management Framework Release Notes.

Software packages for the Web Gateway componentsTable 7 lists the software package blocks used to install the Web Gatewaycomponents. These SPBs are located in the /SPB subdirectory on the IBM TivoliConfiguration Manager Web Gateway CD.

Table 7. Software packages for installing the Web Gateway component


Tivoli_Web_Gateway_DB The software package for installing the Web Gatewaydatabase

Tivoli_Web_Gateway_SRV The software package for installing the Web Gatewayserver

Tivoli_Web_Gateway_L10N The software package for installinginternationalization support for the Web Gatewaycomponent


Software packages for the Web Infrastructure componentsTable 8 lists the software package blocks used to install the Web Infrastructurecomponent. These SPBs are located in the /SPB subdirectory on the IBM TivoliConfiguration Manager Web Gateway CD.

Table 8. Software packages for installing the Web Interfaces component


Tivoli_WebUI The software package for installing the Web Interfacecomponent

Tivoli_WebUI_L10N The software package for installinginternationalization support for the Web Interfacecomponent

Tivoli_INV_WebUI_plugin The software package installing the Inventory Plug-incomponent used by the Web Interface component

Tivoli_INV_WebUI_plugin_L10N The software package for installinginternationalization support for the Inventory Plug-incomponent

Tivoli_SWD_WebUI_plugin The software package installing the SoftwareDistribution Plug-in component used by the WebInterface component

Tivoli_SWD_WebUI_plugin_L10N The software package for installinginternationalization support for the SoftwareDistribution Plug-in component

Software packages for Tivoli endpointsTable 9 lists the software package blocks used to install a Tivoli endpoint. TheseSPBs are located in the /SPB subdirectory on the IBM Tivoli ConfigurationManager Web Gateway CD.

Table 9. Software packages for installing a Tivoli endpoint


Tivoli_TMA_solaris2 The software package for installing an endpoint on aSolaris operating environment

Tivoli_TMA_w32-ix86 The software package for installing an endpoint on aWindows operating system

Tivoli_TMA_linux-ix86 The software package for installing an endpoint on aLinux for Intel

Tivoli_TMA_aix-r1 The software package for installing an endpoint onan AIX operating system

Software packages for the Software Package Editor componentTable 10 lists the software package blocks used to install the Software PackageEditor component. These SPBs are located in the /SPB subdirectory on the IBMTivoli Configuration Manager Desktop CD.

Table 10. Software packages for installing the Software Package Editor component


Tivoli_SWDEP_400PS The software package for the OS/400 preparation site

Tivoli_SWDEP_AIX The software package for AIX operating systems

Tivoli_SWDEP_HP The software package for HP-UX operatingenvironments


Table 10. Software packages for installing the Software Package Editorcomponent (continued)


Tivoli_SWDEP_LINUX_IX86 The software package for Linux for Intel

Tivoli_SWDEP_LINUX_S390 The software package for Linux for S/390®

Note: This SPB install only the support for theSoftware Package Editor command line interface.

Tivoli_SWDEP_L10N The language support packages for Software PackageEditor

Tivoli_SWDEP_NT The software package for Windows operatingsystems, except Windows 98

Tivoli_SWDEP_NTAS400 The software package used on a Windows operatingsystem (except Windows 98) for creating OS/400®

software packagesNote: The Windows operating system that receivesthe distribution must have a TCP/IP connection tothe OS/400 preparation site where theSWDEP_400PS.spb is installed

Tivoli_SWDEP_NW The software package for NetWare operating systemsNote: This SPB install only the support for theSoftware Package Editor command line interface.

Tivoli_SWDEP_WIN95 The software package for Windows 98 operatingsystems

Tivoli_SWDEP_OS2 The software package for OS/2 operating systems

Tivoli_SWDEP_SOLARIS The software package for Solaris operatingenvironments

Software packages for the Pristine Tool componentTable 11 lists the software package blocks used to install the Pristine toolcomponent. These SPBs are located in the /SPB subdirectory on the IBM TivoliConfiguration Manager Desktop CD.

Table 11. Software packages for installing the Pristine Tool component


Tivoli_Pristine_L10N The language support packages for Pristine Tool

Tivoli_Pristine_NT The software package for Windows operating systems

Tivoli_Pristine_OS2 The software package for OS/2 operating systems

Software packages for the IBM Tivoli Configuration Manageradministrative interfacesTable 12 lists the software package blocks used to install the IBM TivoliConfiguration Manager administrative interfaces. These SPBs are located in the/SPB subdirectory on the IBM Tivoli Configuration Manager Desktop CD.

Table 12. Software packages for installing the administrative interfaces


Tivoli_APM_GUI The software package for the Activity Planneradministrative interface

Tivoli_APM_GUI_L10N The language support packages for the ActivityPlanner administrative interface


Table 12. Software packages for installing the administrative interfaces (continued)


Tivoli_CCM_GUI The software package for the Change Manageradministrative interface

Tivoli_CCM_GUI_L10N The language support packages for the ChangeManager administrative interface

Tivoli_INV_GUI The software package for the Inventoryadministrative interface

Tivoli_INV_GUI_L10N The language support packages for the Inventoryadministrative interface

Tivoli_MD2GUI The software package for the Distribution Statusconsole

Tivoli_MD2GUI_L10N The language support packages for the DistributionStatus console

Installation optionsThis section contains the installation options for installing the components of IBMTivoli Configuration Manager, as follows:v Activity Planner, see page 35v Change Manager, see page 37v Enterprise Directory Query Facility, see page 39v Inventory, see page 40v Inventory Gateway, see page 42v Resource Manager, see page 42v Resource Manager Gateway, see page 43v Scalable Collection Service, see page 43v Software Distribution, see page 44v Software Distribution Gateway, see page 44v Software Package Editor, see page 44v Web Gateway, see page 44v Web Infrastructure, see page 48

Activity PlannerThe Activity Planner components depends on the previous installation of thefollowing software:v Tivoli Management Frameworkv Java Client Framework for Tivoliv Java 1.3.0 for Tivoliv Java RDBMS Interface Module

When you install Activity Planner on the Tivoli server, the Activity Planner servercode, commands, and administrative interface are installed. When you installActivity Planner on any other managed node, the Activity Planner commands andadministrative interface are installed.

Table 13 on page 36 provides the installation options that you can specify whenyou install the Activity Planner component.


Table 13. Installation options for the Activity Planner component

Field Name CLI Option

Description

v Database vendor @RDBMS_Vendor@

Specifies the vendor name of the RDBMS that you are using for the plannerrepository.

v For DB2®, use DB2.

v For Informix®, use Informix.

v For Microsoft® SQL Server, use MS_SQL.

v For Oracle, use Oracle.

v For Sybase, use Sybase.

v RIM host @RDBMS_Host@

Specifies the name of the managed node that you have configured to be the RIM hostof the Tivoli region. If you want the Tivoli server to be the RIM host, leave the defaultentry, ALI_host.

v Database ID @RDBMS_DB_Name@

Specifies the name of the planner repository in the RDBMS.

v For DB2, use the name of the DB2 server database created for Activity Planner. Ifyou created a remote client that uses an alias, use the alias name.

v For Informix, use the name of the Informix server database created for ActivityPlanner. If you created a remote client that uses an alias, use the alias name.

v For Microsoft SQL Server, use planner.

v For Oracle, use the value of the ORACLE_SID variable. This value is the Oracleinstance ID and is located in the tnsnames.ora file in the$ORACLE_HOME/network/admin directory. The default value that is set duringthe installation is ORCL.

v For Sybase, use planner.

v Database home @RDBMS_DB_Home@

Specifies the path to the directory where the RDBMS server or client software isinstalled on the RIM host.

v For DB2, use the value of the DB2DIR variable.

v For Informix, use the value of the INFORMIXDIR variable on a UNIX RIM host, oruse the path to the RDBMS server or client software on a Windows RIM host.

v For Microsoft SQL Server, use the path to the RDBMS server or client software.

v For Oracle, use the value of the ORACLE_HOME variable.

v For Sybase, use the value of the SYBASE variable. If the RIM host is on a differentmachine than the RDBMS server, the value of SYBASE is the directory on the RIMhost where the interfaces file is located.

v Server ID @RDBMS_DB_Param_one@

Specifies the vendor-specific information that enables the RDBMS to connect to theRIM host.

v For DB2, use tcpip.

v For Informix, use the value of the INFORMIXDIR variable.

v For Microsoft SQL Server, use the host name of the machine where Microsoft SQLServer is installed.

v For Oracle, use the value of the TWO_TASK variable that is located in thetnsnames.ora file in the $ORACLE_HOME/network/admin directory.

v For Sybase, use the value of the DSQUERY variable in the interfaces file.


Table 13. Installation options for the Activity Planner component (continued)


Description

v Database user name @RDBMS_DB_UserName@

Specifies the name of the owner of the planner repository. The default is planner.

v For DB2, use the name of the instance owner of the configuration repository.

v For Informix, use planner.

v For Microsoft SQL Server, use the name of the user that owns the plannerrepository.

v For Oracle, use planner for a UNIX RIM host but use planner@two_task for aWindows RIM host, where two_task is the value of the TWO_TASK variable.

v For Sybase, use planner or the name of the user that owns the planner repository.

v Instance name (DB2 only) @RDBMS_DB_Param_two@

Specifies the name of the DB2 instance.

v Activity Planner user name @Username@

Specifies the Tivoli administrator (with the associated system accounts) who usesActivity Planner. The default is tivapm.

v Activity Planner password @Password@

Specifies the password for the provided user.Note: When installing from the command line, you must add the @From@=CLIoption to the command.

Change ManagerThe Change Manager component depends on the previous installation of thefollowing software:v Tivoli Management Frameworkv Java Client Framework for Tivoliv Java 1.3.0 for Tivoliv Java RDBMS Interface Modulev Activity Planner

Table 14 provides the installation options that you can specify when you install theChange Manager component.

Table 14. Installation options for the Change Manager component


Description


Specifies the vendor name of the RDBMS that you are using for the ccm repository.

v For DB2, use DB2.

v For Informix, use Informix.

v For Microsoft SQL Server, use MS_SQL.




Table 14. Installation options for the Change Manager component (continued)


Description




Specifies the name of the ccm repository in the RDBMS.

v For DB2, use the name of the DB2 server database created for Change Manager. Ifyou created a remote client that uses an alias, use the alias name.

v For Informix, use the name of the Informix server database created for ChangeManager. If you created a remote client that uses an alias, use the alias name.

v For Microsoft SQL Server, use ccm.

v For Oracle, use the value of the ORACLE_SID variable. This value is the Oracleinstance ID and is located in the tnsnames.ora file in the$ORACLE_HOME/network/admin directory. The default value that is set duringthe installation is ORCL.

v For Sybase, use ccm.







v For Sybase, use the value of the SYBASE variable. If the RIM host is on a differentmachine than the RDBMS server, the value of SYBASE is the directory on the RIMhost where the interfaces file is located.






v For Oracle, use the value of the TWO_TASK variable that is located in thetnsnames.ora file in the $ORACLE_HOME/network/admin directory.


v Database user name @RDBMS_DB_UserName@

Specifies the name of the owner of the ccm repository. The default is tivoli.

v For DB2, use the name of the instance owner of the configuration repository.

v For Informix, use tivoli.

v For Microsoft SQL Server, use the name of the user that owns the ccm repository.

v For Oracle, use tivoli for a UNIX RIM host but use tivoli@two_task for a WindowsRIM host, where two_task is the value of the TWO_TASK variable.

v For Sybase, use tivoli or the name of the user that owns the configurationrepository.


Table 14. Installation options for the Change Manager component (continued)


Description



Enterprise Directory Query FacilityThe Enterprise Directory Query Facility component depends on the previousinstallation of the following software:v Tivoli Management Frameworkv Java 1.3.0 for Tivoliv Resource Manager, for resource management of usersv An installed and configured LDAP directory server. For a list of supported

LDAP directory servers, see IBM Tivoli Configuration Manager Release Notes.

Table 15 provides the installation options that you can specify when you install theEnterprise Directory Query Facility component.

Table 15. Installation options for the Enterprise Directory Query Facility component


Description

v Server host name @ServerUrl@

Specifies the host name of the LDAP server.

v Server port @Server_port@

Specifies the port that is used to connect to Enterprise Directory Query Facility. Thedefault is 389.

v Server SSL port @Server_ssl_port@

Specifies the port that is used to connect to Enterprise Directory Query Facility whenusing SSL. The default is 636.

v Distinguished name @Username@

Specifies the distinguished name of the user with LDAP Administrator privileges. Forexample, the LDAP administrator for Microsoft Active Directory in the .swd.comdomain would be specified as follows:

CN=Administrator,CN=Users,dc=SWD,dc=COM

v Password @Password@

Specifies the password for the LDAP user.

v Access protocol @Provider@

Specifies the protocol used for enterprise directory connections. The default iscom.sun.jndi.ldap.LdapCtxFactory.

v Naming context @Context_name@

Specifies the naming context in the enterprise directory tree level used to retrieveinformation with a query. For example, the naming context within Microsoft ActiveDirectory that is required to make a query to obtain a list of users in the .swd.comdomain would be specified as follows:

CN=Users,dc=SWD,dc=COM


Table 15. Installation options for the Enterprise Directory Query Facilitycomponent (continued)


Description

v Keystore path @Keystore_path@

Specifies the patch contain the certification repository (the keystore) that is used forSSL connections.

v Keystore password @Keystore_passwd@

Specifies the password associated with the keystore.

After installing the Enterprise Directory Query Facility component, you must runthe LDAP-specific script to extend the schema. For details, see “Running EnterpriseDirectory Query Facility scripts” on page 79.

InventoryThe Inventory component depends on the previous installation of the followingsoftware:v Tivoli Management Frameworkv Scalable Collection Servicev Java 1.3.0 for Tivoliv Java Client Framework for Tivoli

Table 16 provides the installation options that you can specify when you install theInventory component.

Table 16. Installation options for the Inventory component


Description

v Data handler host @INV_DATA_HOST@

Specifies the name of the managed node that is the Inventory Data handler.

v MDist 2 callback host @INV_CB_HOST@

Specifies the name of the managed node that is the Inventory callback host.


Specifies the vendor name of the RDBMS that you are using for the configurationrepository.

v For DB2, use DB2.








Table 16. Installation options for the Inventory component (continued)


Description


Specifies the name of the configuration repository in the RDBMS.

v For DB2, the name of the DB2 database; for a remote client that uses an alias, thealias name.

v For Informix, the name of the Informix server database created for Inventory. If youcreate a remote client that uses an alias, use the alias name.

v For Microsoft SQL Server, use inv_db.

v For Oracle, the value of the ORACLE_SID variable, which is located in thetnsnames.ora file in the $ORACLE_HOME/network/admin directory. The defaultvalue that is set during the installation is ORCL.

v For Sybase, use inv_db.







v For Sybase, use the value of the SYBASE variable. When the RIM host and RDBMSserver are on different machines, the value of SYBASE is the directory on the RIMhost where the interfaces file is located.






v For Oracle, use the value of the TWO_TASK variable in the tnsnames.ora file in the$ORACLE_HOME/network/admin directory.


v User name @RDBMS_DB_UserName@

Specifies the name of the owner of the configuration repository.

v For DB2, use the name of the instance owner.

v For Informix, use informix.

v For Microsoft SQL Server, use the name of the user that owns the configurationrepository.

v For Oracle, use invtiv for a UNIX RIM host and invtiv@two_task for a WindowsRIM host, where two_task is the value of the TWO_TASK variable.

v For Sybase, use invtiv or the name of the user who owns the configurationrepository.




Inventory GatewayThe Inventory Gateway component depends on the previous installation of thefollowing software:v Tivoli Management Framework

During the installation of this component, you are not prompted for anyinstallation options.

Resource ManagerTable 17 provides the installation options that you can specify when you install theResource Manager component when Inventory is not currently installed in thelocal Tivoli region. Resource Manager and Inventory share the same tablespace(inv_ts). When Resource Manager and Inventory do not share the same tablespace(because Resource Manager has its own tablespace), the repository used byResource Manager is the trm repository. This information is reflected in Table 17.

Note: If you provide values when Inventory is already installed, these values areignored.

Table 17. Installation options for the Resource Manager component


Description


Specifies the vendor name of the RDBMS that you are using for the trm repository.

v For DB2, use DB2.








Specifies the name of the configuration repository in the RDBMS.

v For DB2, use the name of the DB2 database; for a remote client that uses an alias,the alias name.

v For Informix, use the name of the Informix server database created for Inventory. Ifyou create a remote client that uses an alias, use the alias name.

v For Microsoft SQL Server, use trm.

v For Oracle, use the value of the ORACLE_SID variable, which is located in thetnsnames.ora file in the $ORACLE_HOME/network/admin directory. Theinstallation default is ORCL.

v For Sybase, use trm.


Table 17. Installation options for the Resource Manager component (continued)


Description







v For Sybase, use the value of the SYBASE variable. When the RIM host and RDBMSserver are on different machines, the value of SYBASE is the directory on the RIMhost where the interfaces file is located.






v For Oracle, use the value of the TWO_TASK variable in the tnsnames.ora file in the$ORACLE_HOME/network/admin directory.


v User name @RDBMS_DB_UserName@

Specifies the name of the owner of the configuration repository.

v For DB2, the name of the instance owner.

v For Informix, informix.

v For Microsoft SQL Server, use the name of the user that owns the configurationrepository.

v For Oracle, tivoli for a UNIX RIM host and tivoli@two_task for a Windows RIMhost, where two_task is the value of the TWO_TASK variable.

v For Sybase, tivoli or the name of the user who owns the configuration repository.

v Instance home (DB2 only) @RDBMS_DB_Param_two@


Resource Manager GatewayThe Resource Manager Gateway component depends on the previous installationof the following software:v Tivoli Management Framework


Scalable Collection ServiceThe Scalable Collection Service component depends on the previous installation ofthe following software:v Tivoli Management Framework


This component is a patch image, not a product image.


Software DistributionThe Inventory component depends on the previous installation of the followingsoftware:v Tivoli Management Frameworkv Scalable Collection Servicev Java 1.3.0 for Tivoliv Java Client Framework for Tivoliv Inventory


Software Distribution GatewayThe Software Distribution Gateway component depends on the previousinstallation of the following software:v Tivoli Management Framework


Software Package EditorThe Software Package Editor component depends on the previous installation ofthe following software:v Tivoli Management Frameworkv Scalable Collection Servicev Java 1.3.0 for Tivoliv Java Client Framework for Tivoliv Inventoryv Software Distribution


Web GatewayThe Web Gateway component can be installed using the installation programprovided by IBM Tivoli Configuration Manager or using SPBs. The installationimages for the Web Gateway component are on the IBM Tivoli ConfigurationManager Web Gateway CD. The Web Gateway component consists of twoinstallations: the Web Gateway database and the Web Gateway server.

You must install the Web Gateway database before installing the Web Gatewayserver. These installations, however, can be on the same or different systems. If youinstall the Web Gateway database and the Web Gateway server on differentsystems, you must install the DB2 client with the JDBC 2.0 driver on each systemwhere the Web Gateway server is installed. For information about configuring aDB2 client, see “Configuring the DB2 client” on page 87.


Web Gateway databaseBefore installing the Web Gateway database, you must create the dmsadmin anddmsuser DB2 users. The dmsadmin DB2 user owns the database tables in the WebGateway database. The dmsuser DB2 user accesses and queries the database tablesin the Web Gateway database. For details about creating the dmsadmin anddmsuser users, see “Creating the DB2 users for the Web Gateway component” onpage 18.

Table 18 lists the installation options that you can specify when you install the WebGateway database.

Note: The defaults shown in Table 18 are the defaults when using the WebGateway installation program.

Table 18. Installation options for the Web Gateway database

Field Name SPB Keyword

Description

v Destination directory For UNIX, targetdir.UNIX

For Windows, targetdir.PC

The fully qualified path of the temporary directory where you want the Web Gatewaydatabase files. The defaults are:

v For UNIX, /tmp/TWG

v For Windows, c:\temp\TWG

v DB2 instance dbAdmin

The DB2 instance ID. The default is db2inst1.

v DB2 port dbServerPort

The communication port between the database client and the database server. Thedefault is 50000.

v Password for dmsadmin dmsDBAdminPW

The password used by the dmsadmin user.

v Password for dmsuser dmsDBUserPW

The password used by the dmsuser user.

v Database home dbHome

The directory on the local system for the database files. If this directory does not exist,it is created. The default is /db/db2.Note: This option is displayed during installation on UNIX operating systems.

v Database container home dbFiles

The directory on the local system for the container files. If this directory does notexist, it is created. The default is /dmsdb.Note: This option is displayed during installation on UNIX operating systems.

Web Gateway serverWhen installing the server for resource management of devices only, do not specifyany IBM Tivoli Access Manager or IBM Tivoli Access Manager WebSEALinformation. When installing for Web object access, you must specify thisinformation. For additional information about configuring and using the WebInterfaces component with the Web Gateway component, see “Using the WebGateway component with IBM Tivoli Access Manager” on page 19.


Note: Before installing the Web Gateway server, you need to ensure that theWebSphere Application Service is running.

Table 19 lists the installation options that you can specify when you install the WebGateway server.

Note: The defaults shown in Table 19 are the defaults when using the WebGateway installation program.

Table 19. Installation options for the Web Gateway server


Description

v Destination directory DMS.Destination

The fully qualified path of the directory where you want the Web Gateway serverfiles. The defaults are:

v For Solaris and Linux, /opt/TivTwg

v For AIX, /usr/TivTwg

v For Windows, c:\Program Files\TivTwg

v Web server home WebSrvHomeDir

The fully qualified path to the home directory for Web server (IBM HTTP Server)files. The Web Gateway component uses this path to locate the httpd.conf file andretrieve values for configuration. The defaults are:

v For Solaris, /opt/IBMHTTPD

v For Linux, /opt/IBMHTTPServer

v For AIX, /usr/HTTPServer

v For Windows, use c:\IBM HTTP Server

v JDBC driver home JDBCDriver

The fully qualified path for the DB2 JDBC 2.0 driver used by the Web Gateway serverto communicate with the Web Gateway database. The defaults are:

v For UNIX, /home/db2inst1/sqllib/java12/db2java.zip

v For Windows, c:\Program Files\SQLLIB\java12\db2java.zip

v Database host name

The fully qualified host name of the DB2 server used to store device data.

v Web server port

The port number for communication from the Web Gateway server to the Web serverand application server. This value is always 80.

v Database port DatabasePort

The database port that is used by the Java applications to communicate with the DB2database. The default is 6789.

v Cluster environment CLUSTER_ENV

Specifies whether the single Web Gateway server (false) or a cluster of Web Gatewayservers (true) are used with the DB2 database. In a cluster environment, all WebGateway servers share the same DB2 database. The default is false.Note: During the installation of the first Web Gateway server, select false. This serverwill be your primary Web Gateway server. For each additional installation of the WebGateway server, select true so that this Web Gateway server shares the same DB2database as the primary Web gateway server.

v Database password Password

The password used by the dmsadmin user.


Table 19. Installation options for the Web Gateway server (continued)


Description

v Web Gateway Database name DatabaseName

The unique name, the DB2 database ID, of the Web Gateway database, which is usedto store device information. The default is dms.

v RDBMS database name DatabaseAlias

The alias for the DB2 database name. The default is dms.

v Database administrator name UserID

The name of the user who owns the DB2 instance. The default is dmsadmin.

v Enable security WEBSEAL_ENABLED

Specifies whether to enable (true) or disable (false) the WebSEAL security managerfor Web-based resources. The default is false.

v Host name WEBSEAL_HOST_NAME

The fully qualified local or remote host name of the WebSEAL server. The format ishostname.domain.

v Junction point WEBSEAL_MOUNT_POINT

The TCP/IP connection between the WebSEAL server and the Web application server.This option enables WebSEAL to protect the Web resources located on the Webapplication server.

To determine the host name for the WebSEAL server, start the pdadmin utility andenter the following command:

object list /WebSEAL

Using the host name of the WebSEAL server, enter the following command to find thejunction points:

object list /WebSEAL/hostname

Use the exact output, both format and case, to specify the appropriate junction point.The format of this field is as follows:

/WebSEAL/hostname/junction_point

v Access Manager user name PD_ADMIN_USERID

The user name of the IBM Tivoli Access Manager administrator that was specifiedduring the installation of the IBM Tivoli Access Manager server. The default issec_master.

v Password PD_ADMIN_PW

The password associated with the user name of the IBM Tivoli Access Manageradministrator.

v WebSEAL protocol WEBSEAL_PROTOCOL

The protocol used by WebSEAL. The default is https.

v WebSEAL port WEBSEAL_PORT

The port number used by the WebSEAL protocol. The default is 443.


Table 19. Installation options for the Web Gateway server (continued)


Description

v Access Manager configuration file PD_CONFIG_FILE

The configuration file that is installed with the Access Manager Java Runtime Client.This file provides information on how to connect to the IBM Tivoli Access Managerserver. The default is jdk_home/jre/PDPerm.properties.

For infomation about creating this file, see “Creating SSL configurations andkeystores” on page 19.

v Access Manager JAR home PDJRTE_JARS_HOME

The home directory of JAR file used by the IBM Tivoli Access Manager Java RuntimeClient. The default is /opt/PolicyDirector/java/export/pdjrte.

Web InfrastructureDuring the installation of this component, you are not prompted for anyinstallation options.

The Web Infrastructure component that is installed on the Tivoli server is usedwith the plug-ins installed using the Web Gateway installation program. Webaccess depends on the previous installation of the following software:v A Tivoli endpoint at the Tivoli Management Framework, Version 4.1, levelv IBM Tivoli Access Manager and IBM Tivoli Access Manager WebSEALv IBM DB2v IBM WebSphere Application Serverv Web Gateway database and Web Gateway server

Notes:

1. Before the Web Interfaces component becomes operational, you must install theWeb Infrastructure component on the Tivoli server. This component can beinstalled during the Server installation program or included in the UpgradePlan Generator program.

2. You can install the endpoint and the Web Gateway database and server usingthe Web Gateway installation program.


Chapter 4. Installing IBM Tivoli Configuration Manager

This chapter describes how to install, upgrade, and uninstall the components ofIBM Tivoli Configuration Manager. You can install and upgrade the components ofIBM Tivoli Configuration Manager using any of the following different installationmechanisms:v Using the installation program, which creates a new Tivoli management region

server (Tivoli server) and installs the appropriate IBM Tivoli ConfigurationManager components or upgrades the entire Tivoli management region (Tivoliregion) using a activity plans. See “Installing components using the installationprogram”.

v Using Tivoli Software Installation Service, where you select which products toinstall on which machines. See “Installing components using Tivoli SoftwareInstallation Service” on page 57.

v Using the Tivoli desktop, where you select which product and patches to installon which machine. See “Installing components using the Tivoli desktop” onpage 58.

v Using winstall and wpatch commands provided by Tivoli ManagementFramework, where you specify which products and patches to install on whichmachine. See “Installing components using the command line” on page 58.

To help you determine your installation mechanism as well as know what isrequired during the installation depending on installation mechanism, use theinformation in Appendix A, “Planning and installation worksheets” on page 93.

Installing components using the installation programIBM Tivoli Configuration Manager provides four local installation programs. Eachinstallation program, except the Upgrade Plan Generator, has a typical and acustom option. During a typical installation, the default values for manyinstallation options are assumed, and fields for these options are not presented.During a custom installation, you can change the default values for the installationoptions. Independent of whether you select a typical or custom installation, not allthe installation options shown in the tables in “Installation options” on page 35 arepresented.

Using the installation program, you can install directly from the CDs or copy theCD to a file system and mount that file system. During the installation you areprompted to locate the installation images. Use this window to navigate to theinstallation images or type the location of the installation images.

These installation programs are as follows:

Server installationThis installation program creates a Tivoli server for your configurationmanagement environment by installing the required (typical) or selected(custom) components, creating the required RIM objects, and optionallycreating the databases used by the components of IBM Tivoli ConfigurationManager. The installation program cannot create the databases unless theRDBMS software is installed and configured on this system.

Because this program optionally creates the required databases, theinstaller is asked for the password for the database administrator (DBA) so


that the admin and schema scripts can be run by the installation program.If the installer is not the DBA, when asked the level of databaseconfiguration, select No configuration and click Next.

Note: Even if you select No configuration, the RDBMS software must beinstalled and configured on this system. If the installation programdoes not find the RDBMS client software, the installation cannotcomplete.

Even when the installer has the DBA password, you might need toperform some manual database operations before running the adminscripts to create the users and tablespaces. For information about whichadmin scripts require manual work, see Chapter 5, “Working withrepositories and queries” on page 67.

Note: Do not use this installation mechanism if you use or plan to use ahigh-availability (HA) environment. To install in an HAenvironment, use the instructions as documented in Tivoli EnterpriseInstallation Guide.

To use this installation program, see “Server installation” on page 51.

Upgrade Plan GeneratorThis installation program creates activity plans for a Tivoli region in yourTivoli environment. If you have multiple Tivoli regions in your Tivolienvironment, run this installation program on the Tivoli server in eachTivoli region. The generated activity plans can be saved, edited withActivity Plan Editor, and run at a later date, or the generated plans can berun, without modification, by the Activity Planner component.

To use this installation program, see “Upgrade Plan Generator installation”on page 53.

Web Gateway installationThis installation program installs a Tivoli endpoint, the Web Gatewaycomponents (database and server) to perform device management, and theWeb Interface components (the interface and component plug-ins) toperform configuration management operations from a Web browser.

To use this installation program, see “Web Gateway installation” onpage 56.

Desktop installationThis installation program installs Tivoli Desktop for Windows and theadministrative interfaces provided by IBM Tivoli Configuration Manager.The Tivoli desktop contains icons that are used to launch theseadministrative interfaces.

To use this installation program, see “Desktop installation” on page 56.

Locating the installation programsThe installation programs are located on the following CDs:

Server installationThe installation programs are located in the /FRESH subdirectory of theIBM Tivoli Configuration Manager Installation CD.


Upgrade Plan Generator installationThe installation programs are located in the /UPGRADE subdirectory ofthe IBM Tivoli Configuration Manager Installation CD.

Web Gateway installationThe installation programs are located in the root directory of the IBMTivoli Configuration Manager Web Gateway CD.

Desktop installationThe installation program (setup.exe) is located in the root directory of theIBM Tivoli Configuration Manager Desktop CD.

Starting the installation programsBefore starting the installation program, read the information about the installationyou are planning to perform. The installation program uses a Java Virtual Machineand requires 120 megabytes of available disk space in the /temp directory.

The general procedure for starting the installation programs are as follows:

For UNIXFrom the CD listed in “Locating the installation programs” on page 50, useone of the following procedures:v To download the Java Virtual Machine to the /temp directory:

1. Change to the directory containing the installation program.2. Enter:

./file.bin

where file is the name of the file that starts the installation program.For each UNIX operating system, there is a different installationprogram.

v To download the Java Virtual Machine to a directory other than the/temp directory:1. Change to the directory containing the installation program.2. Enter:

./file.bin -is:tempdir directory

where file is the name of the file that starts the installation program,and directory is the directory to where you to download the JavaVirtual Machine.

For WindowsFrom the CD listed in “Locating the installation programs” on page 50, runthe listed *.exe file.

Server installationThe Server installation program installs Tivoli Management Framework, whichcreates the Tivoli server and installs select components of IBM Tivoli ConfigurationManager. With the exception of Tivoli Management Framework and ScalableCollection Service, this installation wrappers the winstall command. TivoliManagement Framework, depending on the platform, uses either the wservercommand (for a UNIX operating system) or the silent install of the Tivoli server(for a Windows operating system). Scalable Collection Service uses the wpatchcommand. For additional information on these commands, see Tivoli ManagementFramework Reference Manual.

Chapter 4. Installing IBM Tivoli Configuration Manager 51

This installation program can be used on all platforms supported as a Tivoli server.For details about which platforms are supported as a Tivoli server, see TivoliManagement Framework Release Notes.

The installation images used by this installation are on the IBM TivoliConfiguration Manager Server CD , Tivoli Management Framework CD (1 of 2),and Tivoli Management Framework CD (2 of 2).

Typical and custom installationsWhen using this installation, the following components are always installed,configured, or created:v Tivoli Management Framework

To support a single server installation, a Tivoli gateway is also created on thismachine. This gateway is automatically configured as a repeater. The installationof Tivoli Management Framework created the Tivoli server.

v Resource Manager and Resource Manager Gatewayv Enterprise Directory Query Facilityv Scalable Collection Service

Scalable Collection Service is considered part of Tivoli Management Framework.It is used to collect inventory scan results and all results for the Web Gatewaycomponent.

v Distribution Status consoleThe Distribution Status console tracks software distributions and other profiledistributions. The installation of the Distribution Status console requires thefollowing Java components that are provided by Tivoli Management Framework:– Java 1.3 for Tivoli– Java RDBMS Interface Module– Java Client Framework for Tivoli

These Java components are used by several of the other IBM TivoliConfiguration Manager components that are installed during a typical or custominstallation.

The installation of the Distribution Status console creates the mdist2 RIM object.This RIM object can be on the Tivoli server. To move it to another managednode, use the wmvrim command as documented in Tivoli Management FrameworkReference Manual.

Typical installationDuring a typical installation, the following additional components are installed,configured, or created:v Activity Planner

This installation creates the planner RIM object. This RIM object can be on theTivoli server. To move it to another managed node, use the wmvrim commandas documented in Tivoli Management Framework Reference Manual.

v Change ManagerThis installation creates the ccm RIM object. This RIM object can be on the Tivoliserver. To move it to another managed node, use the wmvrim command asdocumented in Tivoli Management Framework Reference Manual.

v Inventory and Inventory GatewayThe installation of the Inventory component creates the inv_query and invdh_1RIM objects. These RIM objects should not be on the Tivoli server. Move them to


another managed node after you this managed node using the wmvrimcommand as documented in Tivoli Management Framework Reference Manual.

v Software Distribution and Software Distribution Gatewayv Software Package Editorv Web Interfaces

To help you through this installation, use the information in “Typical path forserver installation worksheet” on page 99.

Custom installationWhen you select Inventory during a custom installation, all the components listedfor a typical installation are installed with the exception of the SoftwareDistribution, Software Distribution Gateway, and Software Package Editorcomponents. However, when you select Software Distribution, which requires theselection of Inventory, all the additional components are installed.

To help you through this installation, use the information in “Custom path forserver installation worksheet” on page 101.

Upgrade Plan Generator installationThe Upgrade Plan Generator installation program generates Activity Planneractivity definitions in XML files that you can use to upgrade your Tivolienvironment to the most current version of both Tivoli Management Frameworkand IBM Tivoli Configuration Manager.

During the activity plan generation process, the installation program can optionallycopy all required installation images to the local system. When you select the copyall files check box on the Locate the Installation Image window, ensure that youhave enough disk space for these copies and the installed images. For the amountof required disk space, see IBM Tivoli Configuration Manager Release Notes.

Note: If you do not have a local copy of the files used during the upgrade process,the installation cannot complete. If installing from CD or file system, ensurethat these resources remain mapped in their original location.

This installation can be used on all platforms supported as a Tivoli server, exceptLinux for S/390.

Reminder: Before starting the upgrade process, back up the object database on theTivoli server. Before running each generated activity plan, back up theobject database on the Tivoli server and each affected managed node.For details about performing backup operations, see Tivoli ManagementFramework Maintenance and Troubleshooting Guide.

At the beginning of the installation, you must select the Backup donecheck box on the Before You Upgrade the Tivoli Environment windowbefore you can continue to the next window in the installationprogram.

To help you through this installation, use the information in “Installation programfor Tivoli environment upgrade worksheet” on page 120.

Before generating the activity definitions, the installation program installs orupgrades the following components on the Tivoli server:v Tivoli Management Framework


v Java 1.3 for Tivoliv Java RDBMS Interface Modulev Java Client Framework for Tivoliv Activity Planner

Note: If a previous installation of the Activity Planner component exists in thelocal Tivoli region, you must migrate the database following theinstruction in “Migrating data in repositories” on page 61 before runningthe generated activity plans.

v Any selected component that does not currently exist in the local Tivoli region

Note: If a selected component needs to be upgraded in the Tivoli environment,this component is not upgraded before generating the activity definitions.This component is upgraded when you run the generated activity plan.

The installation images used by this installation program are on various IBM TivoliConfiguration Manager and Tivoli Management Framework CDs. You areprompted to locate the appropriate CD and appropriate installation image duringthe installation.

Use the information in Table 20 to know which components will be installed orupgraded when the activity plans are run. While Activity Planner is running thegenerated activity plans, Activity Planner runs Tivoli tasks on the Tivoli server thatwill run the winstall and wpatch commands on the affected managed nodes.

Table 20. Managed resource state after a component is selected during the upgrade plangeneration process

Tivoli server Managed node Gateway Java ClientFramework

Tivoli ManagementFramework

Upgraded Upgraded

Java 1.3 for Tivoli Installed Installed

Java Help 1.0 for Tivoli Installed orupgraded

Installed orupgraded

Java Client Frameworkfor Tivoli

Installed Installed

Java RDBMS InterfaceModule

Installed Installed

Distribution Statusconsole

Upgraded Upgraded

Activity Planner Installed orupgraded

Upgraded

Scalable CollectionService

Installed Installed

Inventory Installed orupgraded

UpgradedwhenInventory,Version 4.0, isdetected

Inventory Gateway Installed orupgraded


Table 20. Managed resource state after a component is selected during the upgrade plangeneration process (continued)

Tivoli server Managed node Gateway Java ClientFramework

Software Distribution Installed orupgraded

Installed whenSoftwarePackage Editor,Version 4.1 orVersion 4.2, isdetected

Software DistributionGateway


Software DistributionUpgrade

Upgradedwhen the 4.1version of thesource hostsoftware isdetected

Software PackageEditor


Upgraded

Change Manager Installed orupgraded

Upgraded

Resource Manager Installed

Resource ManagerGateway

Installed

Web Interfaces Installed

Enterprise DirectoryQuery Facility

Installed

The information in Table 20 on page 54 is the default activity definitions. You canmodify any generated plan using the Activity Plan Editor. If you edit a generatedactivity plan, do not change the identification number.

Reminder: After running the activity plans and if you selected Manually recyclethe object dispatcher, you need to stop and restart the objectdispatcher on any upgraded managed node (including the Tivoliserver) using the odadmin reexec command. For details about thiscommand, see Tivoli Management Framework Reference Manual.

Before upgrading components that maintain databases, you mustmigrate the data in the repositories to have a working Tivolienvironment. For details about these migrations scripts, see “Migratingdata in repositories” on page 61.

If you generate multiple activity plans, only the first one is submitted. Theremaining activity plans are not queued. The generated plans must be submittedone at a time in the same sequence in which they were generated. If an activityplan fails, you can restart it using the instructions for the Activity Plannercomponent as documented in IBM Tivoli Configuration Manager User’s Guide forDeployment Services.


Web Gateway installationThe Web Gateway installation program installs a Tivoli endpoint, the Web Gatewaycomponent, the Web Infrastructure component, and the Inventory and SoftwareDistribution plug-ins.

Before you can use the Web Gateway component to manage devices, you need toinstall the device agent programs. The device agent programs communicate withthe Web Gateway component. These programs run on the devices supported byIBM Tivoli Configuration Manager. For details about installing the device agentprograms, see IBM Tivoli Configuration Manager User’s Guide for Deployment Services.

This installation can be used on Windows NT®operating systems, Windows 2000operating systems, AIX operating systems, Solaris operating environments, orLinux Red Hat operating systems.

Typical installationDuring a typical installation, the following components are installed:v Tivoli endpoint for Tivoli Management Frameworkv Web Gateway, including database and server supportv Web Infrastructurev Inventory plug-in for Web Infrastructurev Software Distribution plug-in for Web Infrastructure

To help you through this installation, use the information in “Typical path for WebGateway installation worksheet” on page 113.

Custom installationDuring a custom installation, you can install any combination of the listedcomponents. Because of software dependencies, you might need to makeadditional selections. You are prompted when additional selections are required.

The installation images used by this installation are on the IBM TivoliConfiguration Manager Web Gateway CD.

Note: The only way to install the Web Gateway component is using the providedinstallation program or installing the SPBs. That is, you cannot use theinstallation mechanism provided by Tivoli Management Framework orTivoli Software Installation Service to install the Web Gateway component.

To help you through this installation, use the information in “Custom path for WebGateway installation worksheet” on page 115.

Desktop installationThe Desktop installation program installs Tivoli Desktop for Windows and the IBMTivoli Configuration Manager administrative interfaces. This installation can beused on Windows operating systems only, except for Windows 98.

The images used by this installation program are on the IBM Tivoli ConfigurationManager Desktop CD.

To install Tivoli Desktop for Windows on OS/2 and Windows 98 operatingsystems, see Tivoli Enterprise Installation Guide. Although the Tivoli desktop on an


OS/2 or Windows 98 operating system shows the icons for the administrativeinterfaces, selecting one of these icons does not launch the selected administrativeinterface.

Typical installationDuring a typical installation, the following components are installed:v Tivoli Desktop for Windowsv Java components, which installs the following components:

– Java 1.3 for Tivoli– Java RDBMS Interface Module– Java Client Framework for Tivoli– JavaHelp 1.0 for Tivoli

v Activity Planner GUIv Distribution Status consolev Change Manager GUIv Inventory GUI

To help you through this installation, use the information in “Typical path fordesktop installation worksheet” on page 118.

Custom installationDuring a custom installation, you can install components as follows:v Any combination of listed components. Because of software dependencies, you

might need to make additional selections. You are prompted when additionalselections are required.

v The Software Package Editor component, if the Tivoli endpoint currently is selector if the endpoint previously was installed.

Note: If the installation program does not detect a Tivoli endpoint, the checkbox for Software Package Editor cannot be selected.

To help you through this installation, use the information in “Custom path fordesktop installation worksheet” on page 118.

Installing components using Tivoli Software Installation ServiceWhen installing products using Tivoli Software Installation Service, select theproducts to be installed using the component name shown in Table 4 on page 30.When installing patches using Tivoli Software Installation Service, select thepatches to be installed using the component name shown in Table 5 on page 31.

Tivoli Software Installation Service does not distinguish between products andpatches. Independent of whether the installation image is used for an installationor upgrade, Tivoli Software Installation Service refers to all installation images asproducts.

Tivoli Software Installation Service can install multiple products on multiplemachines in parallel. This software can install more products on more computersystems in less time than using the installation mechanisms provided by TivoliManagement Framework.

The basic procedure for using Tivoli Software Installation Service to installproducts is as follows:


1. Import the product images into the Tivoli Software Installation Service depot.2. Select the components to be installed.3. Select the machines where each component is to be installed.4. Click Install.

During the installation procedure, you are asked to provide installation options,when applicable. These options are listed by component in “Installation options”on page 35. There should be no installation options required during an upgrade

procedure.

For detailed information about using Tivoli Software Installation Service, see TivoliEnterprise Installation Guide.

Installing components using the Tivoli desktopWhen installing products using the Tivoli desktop, select the products to beinstalled using the component name shown in Table 4 on page 30. When installingpatches using the Tivoli desktop, select the patches to be installed using thecomponent name shown in Table 5 on page 31.

The Tivoli desktop can install or upgrade the same product on multiple machinesserially.

The basic procedure for using the Tivoli desktop to install a product is as follows:1. From the Tivoli desktop, select Install → Install Product from the Desktop

menu.2. Select the media and component to be installed.3. Select the machines where the component is to be installed.4. Click Install.

The basic procedure for using the Tivoli desktop to upgrade a product is asfollows:1. From the Tivoli desktop, select Install → Install Patch from the Desktop menu.2. Select the media and component to be upgraded.3. Select the machines where the component is to be upgraded.4. Click Install.

During the installation procedure, you are asked to provide installation options,when applicable. These options are listed by component in “Installation options”on page 35. There should be no installation options required during an upgrade

procedure.

For detailed information about using the Tivoli desktop to install or upgradeproducts, see Tivoli Enterprise Installation Guide.

Installing components using the command lineWhen installing products using the winstall command, specify the name of theindex file (.IND) using the file shown in Table 4 on page 30. When upgradingproducts using the wpatch command, specify the name of the index file using thefile shown in Table 5 on page 31.


When using the winstall command to install a product or when using the wpatchcommand to upgrade a product, you specify the following information on thecommand line:v The location of the image on the installation media.v The name of the index file associated with the product to be installed or

upgraded.v Installation options associated with the image, when applicable. These options

are listed by component in “Installation options” on page 35.v The machines where the image is to be installed.

If you do not specify a machine when running the winstall command, the image isinstalled on all managed nodes in the Tivoli region.

If you do not specify a machine when running the wpatch command, the image isinstalled on all managed nodes in the Tivoli region when there is a prior version ofthis image.

For detailed information about using the winstall and wpatch commands, seeTivoli Management Framework Reference Manual.

Installing components using software package blocksBefore installing images from software package blocks, the Tivoli environmentmust be created and IBM Tivoli Configuration Manager must be fully deployed.

To install an image from software package blocks, perform the following steps:1. From the Tivoli desktop, double-click the appropriate policy region icon to

display the Policy Region window.2. In the Policy Region window, double-click the appropriate profile manager

icon to display the Profile Manager window.3. Select Profile from the Create menu to display the Create Profile window.4. Create a software package profile.5. Insert the IBM Tivoli Configuration Manager Desktop CD into the CD-ROM

drive.6. Right-click the new software package profile, and select Import to display the

Import window.7. In the Location of Input File group box, select one of the following from the

drop-down list:v Managed Node, if the machine in step 5 is a managed node.v Endpoint, if the machine in step 5 is an endpoint, and type the name of the

endpoint in the Endpoint Name text box.8. Click the Browse (...) button to display the Select Input File window.9. In the Select Input File window, perform the following steps:

a. In the Managed Node list, select the machine where you inserted the CD.b. In the Input File Path list, select the /spb directory.c. Select the image to import.d. In the Location of Source Host group box, perform the following steps:

1) Ensure that the Build check box is selected.2) In the Source Host Name text box, type the source host name.3) In the SPB Path text box, type the path to the software package block.


e. Click Import & Close to return to the Profile Manager window.10. Right-click the software package profile, and select Install to display the

Install Software Package window.11. In the Available Subscribers list, select the endpoint where you want to

install the image.12. To change default values, select Default Variables from the Advanced

Options menu to display the Default Variables window. In this window,modify the values as appropriate.

13. Click Install & Close to begin the installation. The window remains openuntil the operation is submitted.

For complete details about creating and distributing software package profiles, seeIBM Tivoli Configuration Manager User’s Guide for Software Distribution and IBMTivoli Configuration Manager Reference Manual for Software Distribution.

For several of the provided SPBs, there is additional information required for asuccessful installation. This information is as follows:

Software Package EditorAfter installing Software Package Editor, the speditor_dir key is created inthe swdis.ini file. The path where the image is installed is:

speditor_path/interp

where speditor_path is the directory where Java Software Package Editor isinstalled on the local machine and interp is the interpreter type, the Tivoliinternal representation for operating systems. For details about whichinterpreter type represents which operating system, see Tivoli ManagementFramework Release Notes.

Web Gateway and Web InterfacesWhen using SPBs to install the Web Gateway and Web Interfacescomponent, the name of the software packages, that is, the names of thesoftware profiles, must be as follows:

SPB file name Package name with version

Tivoli_Web_Gateway_DB Tivoli_Web_Gateway_DB.4.2

Tivoli_Web_Gateway_SRV Tivoli_Web_Gateway_SRV.4.2

Tivoli_WebUI Tivoli_WebUI.4.2

Tivoli_SWD_WebUI_plugin Tivoli_SWD_WebUI_plugin.4.2

Tivoli_INV_WebUI_plugin Tivoli_INV_WebUI_plugin.4.2

If the package name does not include the package version or is a differentpackage name, the installation will fail. The complete package name isstored in the software distribution catalog, and this information is used toperform dependency checking.

Administrative interfaces for the Tivoli desktopWhen using SPBs to install to install the administrative interfaces for usefrom the Tivoli desktop, the names of the software packages, that is, thenames of the software profiles, must be as follows:


Tivoli_JRE_NT Tivoli_JRE_NT.1.3.0

Tivoli_JRIM Tivoli_JRIM.4.1



Tivoli_JCF Tivoli_JCF.4.1

Tivoli_JHelp Tivoli_JHelp.1.0

Tivoli_APM_GUI Tivoli_APM_GUI.4.2

Tivoli_CCM_GUI Tivoli_CCM_GUI.4.2

Tivoli_MD2GUI Tivoli_MD2GUI.4.1

If the package name does not include the package version or is a differentpackage name, the installation will fail. The complete package name isstored in the software distribution catalog, and this information is used toperform dependency checking.

Migrating data in repositoriesWhen you upgrade components of IBM Tivoli Configuration Manager, you need toupgrade the database schemas, which migrates data in pre-existing repositories.You must upgrade the schemas using the provided scripts before upgrading yourTivoli environment to IBM Tivoli Configuration Manager, Version 4.2. These scriptsare on the IBM Tivoli Configuration Manager Installation CD in theUPGRADE/SQL/migr directory. The following scripts are provided:

inv_vendor_upgrade_42.sqlUpdates the schema for the Inventory component of IBM TivoliConfiguration Manager.

h_inv_vendor_upgrade_42.sqlUpdates the historical schema for the Inventory component of IBM TivoliConfiguration Manager.

swdis_vendor_migr_42.sqlMigrates the software distribution data in the configuration repository tothose used by the Software Distribution component of IBM TivoliConfiguration Manager.

swdistecsrvr_inst.shUpgrades the rule base used by the IBM Tivoli Enterprise Consoleintegration portion of the Software Distribution component.

Note: Run this script so that events generated by a software distributioncan be written to the IBM Tivoli Enterprise Console event database.If you do not run this script, the available rule base cannot recognizeall the classes used by the Software Distribution component.

swdis_vendor_view_42.sqlDeletes the database views for the previous release and creates the newviews used by this release. Run this script is you created queries thataddress the database tables from the previous release.

Note: Before running this script, read the comments embedded in thescript and rework as necessary.

plans_vendor_migr_42.sqlUpdates the schema for Activity Planner. After running this script, run thefollowing shell script to upgrade the information about the ActivityPlanner plug-in:upgr_plugins.sh


ccm_vendor_migr_42.sqlUpdates the schema for Change Manager. After running this script, run thefollowing shell script to register the Change Manager plug-in as anadministrator with the CCM_Admin Tivoli region authorization role:reg_swd_plugin.sh

Installing and upgrading query librariesThe scripts used to create and upgrade query libraries with their predefinedqueries are located in the $BINDIR/../generic/inv/SCRIPTS/QUERIES directory.For details about these queries, see IBM Tivoli Configuration Manager DatabaseSchema Reference.

The installation scripts are as follows:

h_pervasive_query.shInstalls the H_PERVASIVE_QUERY query library and its related queries.

h_subscription_query.shInstalls the H_SUBSCRIPTION_QUERY query library and its relatedqueries.

inventory_query.shInstalls the INVENTORY_QUERY query library and its related queries.

pervasive_query.shInstalls the PERVASIVE_QUERY query library and its related queries.

subscription_query.shInstalls the SUBSCRIPTION_QUERY query library and its related queries.

The upgrade scripts must be run after upgrading to IBM Tivoli ConfigurationManager, Version 4.2. These scripts are as follows:

h_inventory_query_upgrade_42.shUpgrades the H_INVENTORY_QUERY query library.

inventory_query_upgrade_42.shUpgrades the INVENTORY_QUERY query library.

subscription_query_upgrade_42.shUpgrades the SUBSCRIPTION_QUERY query library.

Registering plug-insDepending on the installation mechanism that you used to install IBM TivoliConfiguration Manager, you might need to register Activity Planner plug-ins orChange Manager plug-ins.

If you installed the Activity Planner or Change Manager component using theprovided Server installation program, you do not need to run these scripts unlessyou selected No Configuration during a custom installation. Additionally if theplanner, ccm, or inv_query RIM objects are not correctly configured, you must runthese scripts manually.

If you installed the Activity Planner or Change Manager component using anyother installation mechanism, you need to one the following scripts afterinstallation:


For Activity PlannerRun the reg_swd_plugin.sh and reg_inv_plugin.sh scripts. After installingthe Activity Planner component, these scripts are in the$BINDIR/TME/APM/SCRIPTS directory.

To run these scripts, you need the APM_Admin Tivoli region authorizationrole.

For Change ManagerRun the reg_swd_plugin.sh and reg_invscan_plugin.sh scripts. Afterinstalling the Change Manager component, these scripts are in the$BINDIR/TME/CCM/SCRIPTS directory.

To run these scripts, you need the CCM_Admin Tivoli region authorizationrole.

For detailed information about these scripts and registering resources, see IBMTivoli Configuration Manager User’s Guide for Deployment Services.

Uninstalling IBM Tivoli Configuration ManagerTo uninstall IBM Tivoli Configuration Manager, use one of the following processes:v Use the Add/Remove program feature on Windows operating systems.v Use the wuninst command to remove components from specific machines.v Use an application-specific script to selectively remove components.v Use the wremovsp or wdrmvsp commands to remove software package blocks

(SPBs) in connected and disconnected mode, respectively.

Uninstalling components using Add/Remove programsFor Server installations performed using the provided installation program, youcan uninstall the components using the Add/Remove program feature onWindows operating systems. This feature is available only for the Serverinstallation program on Windows operating systems. For UNIX operating systemsand software installed using any of the other provided installation programs, youneed to use the Tivoli Management Framework commands or utilities to uninstallproducts and resources.

You can also use the Add/Remove program feature to uninstall Tivoli Desktop forWindows. Running this program only uninstalls Tivoli Desktop for Windows, notthe administrative interfaces used by IBM Tivoli Configuration Manager. Touninstall the administrative interfaces after removing Tivoli Desktop for Windows,perform one of the following procedures depending on whether an endpoint isinstalled on this machine:

Endpoint not installedDelete the following directories, assuming default installation locations:v c:\Program Files\Tivoli\JavaToolsv c:\Program Files\Tivoli\Desktopv c:\swdis

Endpoint installedRemove the installed SPBs using the information in “Uninstalling softwarepackage blocks” on page 64.

When using the Add/Remove programs feature on Windows operating systems,only those components installed using the provided installation program are


removed. In other words, if you created managed nodes or other Tivoli resourcesand installed components on these resources, they are not removed from thosesystems.

Uninstalling components using the wuninst commandThe wuninst command calls the application-specific script. This command removesthe component for the specified machines in your Tivoli environment or from theentire local Tivoli region. To uninstall the component using the wuninst command,specify the component tag listed in Table 4 on page 30. The syntax for thiscommand is as follows:wuninst tag [-rmfiles] [hostname...]

For details on the wuninst command, see Tivoli Management Framework ReferenceManual.

Uninstalling component using scriptsTo manually remove a component from the local machine using the providedscript file, enter the following command:sh script_name -rmfiles

where:

script_nameThe name of the script file as follows:v The Inventory scripts are in the $BINDIR/TAS/UNINST/INVENTORY

directory on each managed node on which the component was installed.v The Software Distribution scripts are in the

$BINDIR/TME/SWDIS/SCRIPTS directory on each managed node onwhich the component was installed. The name of the script file is thesame as the tag listed in Table 4 on page 30.

v The Change Manager scripts are in the $BINDIR/TME/CCM/SCRIPTSdirectory. Use the ccm_uninst.sh script if Change Manager was installed,or use the ccm_upgr_uninst.sh script if Change Manager was upgraded.

v The Activity Planner scripts are in the $BINDIR/TME/APM/SCRIPTSdirectory. Use the apm_uninst.sh script if Activity Planner was installed,or use the apm_upgr_uninst.sh script if Activity Planner was upgraded.

–rmfilesRemoves all product files associated with the component.

Uninstalling software package blocksWhen you install software from SPBs, you can uninstall these SPBs using one ofthe following commands:

wremovspUninstalls an SPB when the target can communicate with a managed node.

wdrmvspUninstalls an SPB from a disconnected target.

Use one of these commands, depending on your connectivity to the Tivolienvironment, to uninstall any software installed from SPBs. For the lists ofsoftware installed from SPBs, see the tables in “Components installed from


software package blocks” on page 31. For additional information on thesecommands, see IBM Tivoli Configuration Manager Reference Manual for SoftwareDistribution.

Uninstalling Software Distribution from NetWare gatewaysTo uninstall the Software Distribution components from a NetWare gateway, youneed to delete the files manually by performing the following steps. Delete onlythe files, not the directories, because they might be used for other Tivoli Enterpriseapplications. This procedure uses SYS:\TIVOLI as the installation directory.1. From the $BINDIR/TME/SWDIS/SCRIPTS directory on the Tivoli server, run

the swdisNW_uninst.sh script to remove the components in the Tivoli regionfrom the Tivoli object database. Because this is a script, use the followingcommand:sh swdisNW_unist.sh NetWare_gateway_name

2. Delete all files in the installation directory that match the spd_eng pattern.3. Delete all files in the installation directory that match the libe*.* pattern.4. Delete the follow files, listed in bold typeface, from the

sys:\Tivoli\bin\lcf_bundle.40 directory:v INSTALLED\SWDISGW_LCFNEW

v nw4\resinit.nlm

v os2–ix86\resinit.exe

v w32–ix86\resinit.exe

v w32–ix86\wdusrprf.exe

v win95\resinit.exe

v os400\resinit

v os400\wdbldspb


Chapter 5. Working with repositories and queries

To store data in an RDBMS, you need to create a repository. To create repositories,you run admin and schema scripts. The applications communicate with theRDBMS through RIM objects. When you install IBM Tivoli Configuration Manager,you create the required RIM objects on systems that become known as RIM hosts.

Depending on your installation approach and your RDBMS choice, you might needto manually create the databases (the tablespaces and view) in the RDBMS. Youcan create the databases before or after creating the RIM objects. If therequirements for the admin scripts are fulfilled, you will create the database usingthe installation program to install or upgrade IBM Tivoli Configuration Manager.

The procedure and requirements for creating databases for each supported RDBMSis discussed in Tivoli Enterprise Installation Guide. For a list of supported RDBMSvendors, see Tivoli Management Framework Release Notes.

Running the admin scriptsRunning an admin script creates the container for all the logical objects (users,views, and so forth) and creates the tablespace that stores all the physical data inthe tables. The admin scripts used by IBM Tivoli Configuration Manager arelocated on IBM Tivoli Configuration Manager Installation CD in theFRESH/SQL/admin directory.

The names of the admin script have the following format:component_vendor_admin.sql

where:

componentOne of the following abbreviations for an IBM Tivoli ConfigurationManager component:

cm The abbreviation used by the admin scripts to create all thetablespaces required by all the components of IBM TivoliConfiguration Manager. Running this script creates a singledatabase with the required tablespaces for each component. Bydefault, this database is cm_db. Having a single admin scriptallows the database administrator (DBA) to manage storage spaceon a component-by-component basis.

ccm The abbreviation used by the admin scripts for the ChangeManager database. The admin script creates the requiredtablespaces for the ccm repository.

inv The abbreviation used by the admin scripts for the Inventory andResource Manager databases. The admin script creates the requiredtablespaces for the configuration repository.

mdist The abbreviation used by the admin scripts for the DistributionStatus database. The admin script creates the required tablespacesfor the mdstatus repository.


plans The abbreviation used by the admin scripts for the Activity Plannerdatabase. The admin script creates the required tablespaces for theplanner repository.

vendor One of the following abbreviations for a supported RDBMS vendors:

db2 IBM DB2

ms_sqlMicrosoft SQL Server

ora Oracle

syb Sybase

Note: There is currently no admin script provided for Informix.

Table 21 contains the databases and tablespaces created by running the individualadmin scripts. You can run the cm_vendor_admin.sql script to create all thedatabases and tablespaces in a single database or modify this script to create only asubset of the databases and tablespaces.

For example, to create the ccm database on a separate server, that is anotherdatabase, the DBA can remove or comment out the SQL command related to theccm database from the cm_vendor_admin.sql script. The DBA can then run thecm_vendor_admin.sql script and the ccm_vendor_admin.sql script against theappropriate RDBMS servers or databases.

Table 21. The databases and tablespaces created by running the admin scripts

Component Inventory ChangeManager

Activity Planner DistributionStatus

Database name inv_db ccm planner mdist2

Tablespace name inv_ts ccm_ts planner_ts mdist2_ts

Tablespace size 1024 MB 128 MB 128 MB 128 MB

Log file size1 128 MB 16 MB 16 MB 16 MB

User name invtiv tivoli planner mdstatus

Password tivoli tivoli planner mdstatus

1 The log file size for an Oracle database uses the system default size instead of thesize listed in the table. An Oracle database allocates sufficient system log spacewhen the CREATE DATABASE command is run. The provided admin scripts donot create any additional log space.

The cm_vendor_admin.sql script, without modification, creates all the tablespacesshown in Table 21, creates a single log file of 176 MB, and creates all the users inthe cm_db database. Each RDBMS provides utilities to move tables to differenttablespaces after they are created. If you want to move tables to differenttablespaces, see the vendor documentation.

The log files are created at 12.5% of the size of the database. The recommendationof database vendors is that the log files should be from 10% to 25% of the databasesize. If necessary, the DBA can allocate additional log space after installation.

Creating DB2 tablespacesThe DB2 admin scripts create the required tablespaces.


Requirement: The db2 admin scripts do not create the default databases. Youmust use the CREATE DATABASE command to create thedatabases, and use the CATALOG DATABASE command to catalogthe database before running the admin script.

The db2 admin scripts create the tablespace and allocate the log space. The adminscripts do not create or catalog the databases. The size of the DB2 log file ismeasured in 4 KB pages. Therefore, 4 MB of log space would be as follows:4 MB * 1024 KB/MB * 4 KB/page = 1024 pages

Requirement:

In DB2 databases, users are operating system users. The provided admin scripts donot create the required users. Although the admin scripts are to be run by a userwith DB2 administration privileges. The default users with the default passwords,as listed in Table 21 on page 68, must exist on the local system exactly as listed orinstallation using the provided installation program will not fully complete.

Additionally, these users must be either:v Previously defined on the system running the DB2 server as an authorized user

(using the user management tool)v Added as the user on the GRANT statement in the admin script.

If you did not run the admin scripts during the installation, complete the followingsteps:1. From the IBM Tivoli Configuration Manager Installation CD, copy the

following files from the FRESH/SQL/admin directory to a temporary directoryon the RIM host:v inv_db2_admin.sqlv plan_db2_admin.sqlv ccm_db2_admin.sqlv mdist_db2_admin.sql

2. Connect to the RDBMS server:db2 connect to database user name using password

where database is the name or alias of the database in the system databasedirectory, name is the user name of the instance owner of the database, andpassword is the password associated with the user.

3. Run the database admin scripts to create the database, to write output to thescreen, and to write the output to the associated log files:db2 -f script_name.sql -o -t -z log_name.log

where script_name is the name of the admin script and log_name is the name ofthe log file. Repeat this step for each admin script.

Creating Microsoft SQL Server tablespacesThe Microsoft SQL Server admin scripts create the required tablespaces.

Requirement: Before running the ms_sql admin scripts, ensure that the directorywhere the database is to be created already exists and that it hassufficient space. You can edit the admin script by changing thedefault directory to an existing directory with sufficient space in thedatabase.

Chapter 5. Working with repositories and queries 69

The ms_sql admin scripts create files for the db_name.mdf database object, thecomponent_ts.ndf file group, and the component_log.ldf log file. These files arecreated in the default data directory (c:\Program Files\Microsoft SQLServer\MSSQL\data). The admin scripts create the database and default users.

The database automatically grows when space is needed and available. The adminscript must be run by the sa user.


following files from the /FRESH/SQL/admin directory to a temporarydirectory on the RIM host:v inv_ms_sql_admin.sqlv plan_ms_sql_admin.sqlv ccm_ms_sql_admin.sqlv mdist_ms_sql_admin.sql

2. From the temporary directory on the RIM host, run the schema scripts and logthe output:isql -U sa -P password -i inv_ms_sql_admin.sql -o inv_ms_sql_admin.logisql -U sa -P password -i plan_ms_sql_admin.sql -o plan_ms_sql_admin.logisql -U sa -P password -i ccm_ms_sql_admin.sql -o ccm_ms_sql_admin.logisql -U sa -P password -i mdist_ms_sql_admin.sql -o mdist_ms_sql_admin.log

where password is the password for the sa user.

Creating Oracle tablespacesThe Oracle admin scripts create the required tablespaces.

Requirement: The ora admin scripts do not create the default databases. Oracledatabases are created using environment variables and initializationfiles. The admin scripts cannot discover the values for these settings.Therefore, you must create the databases, using the CREATEDATABASE command, with the appropriate name before runningthe admin scripts.

The ora admin scripts use the Oracle defaults to create the needed tablespaces andusers, but not the default databases. The admin scripts create the component_ts.dbfdata files in the default Oracle directories. Note that these directories varydepending on the operating system.

The admin script must be run by the sys user.

The sys user must log in as sysdba. Therefore the admin script is run as follows:sqlplus "sys/sys_password@server as sysdba" @script_name

where:

sys_passwordThe password for the sys user.

server The name of the Oracle server

script_nameThe name of the admin script to run.


The quotation marks (″) are important.

Note: For Oracle 8.x, the password for the sys user cannot be the Oracle defaultpassword. When using the default password, you will receive an unrelatederror.


following files from the /FRESH/SQL/admin directory to a temporarydirectory on the computer system where the Oracle client is installed:v inv_ora_admin.sqlv plan_ora_admin.sqlv ccm_ora_admin.sql

2. From this directory, start a SQL*Plus session:sqlplus sys/password

where password is the RDBMS password set for the RDBMS user sys.3. Run the admin scripts associated with the Inventory components by completing

the following steps:a. Specify which log file to write information:

spool inv_ora_admin.log

b. Run the script to create the users and tablespaces:@inv_ora_admin.sql

The script creates the users and tablespaces. The success and failure of theSQL statements are written to the log.

4. Run the admin scripts associated with the Activity Planner components bycompleting the following steps:a. Specify which log file to write information:

spool plan_ora_admin.log

b. Run the script to create the users and tablespaces:@plan_ora_admin.sql

The script create the users and tablespaces. The success and failure of theSQL statements are written to the log.

5. Run the admin scripts associated with the Change Manager components bycompleting the following steps:a. Specify which log file to write information:

spool ccm_ora_admin.log

b. Run the script to create the users and tablespaces:@ccm_ora_admin.sql

The script create the table and views. The success and failure of the SQLstatements are written to the log.

6. Run the admin scripts associated with the Distribution Status console bycompleting the following steps:a. Specify which log file to write information:

spool mdist_ora_admin.log

b. Run the script to create the users and tablespaces:


@mdist_ora_admin.sql

The script create the table and views. The success and failure of the SQLstatements are written to the log.

7. Log out of the SQL*Plus session:quit

Creating Sybase tablespacesThe Sybase admin scripts create the required tablespaces.

Requirement: Before running the syb admin scripts, ensure that the directorywhere the database is to be created already exists and that it hassufficient space. You can edit the admin script by changing thedefault directory to an existing directory with sufficient space in thedatabase.

The syb admin scripts create devices where the tablespaces, database, and usersare created. In Sybase, the devices are numbered. The admin scripts uses twodevices. The admin script reads the last number used and increments it by one. Bydefault, there are 10 available devices, so ensure that there are enough availabledevices for use by the admin scripts.

Device sizes are specified in 2 kilobyte (KB) pages, so a device of 128 megabytes(MB) is calculated as follows:128 MB * 1024 KB/MB * 1 page/2 KB = 65536 pages

The tablespace files created are as follows:v component_ts.dat

v component_log.dat

The default data directory depends on the operating system. The following is thedefault by operating system:

For Windows operating systemsc:\sybase\data

For UNIX operating systems/data/sybase

This directory must exist on the database server before the creation of the database,or the directory is edited in the admin script to an existing directory with sufficientspace.

The admin script also creates the database and default users.

The admin script must be run by the sa user.


following files from the /FRESH/SQL/admin directory to a temporarydirectory on the RIM host:v inv_ms_sql_admin.sqlv plan_ms_sql_admin.sql


v ccm_ms_sql_admin.sqlv mdist_ms_sql_admin.sql

2. From the temporary directory on the RIM host, run the schema scripts and logthe output:isql -U sa -P password -i inv_syb_admin.sql -o inv_syb_admin.logisql -U sa -P password -i plan_syb_admin.sql -o plan_syb_admin.logisql -U sa -P password -i ccm_syb_admin.sql -o ccm_syb_admin.logisql -U sa -P password -i mdist_syb_admin.sql -o mdist_syb_admin.log

where password is the password for the sa user.

Running the schema scriptsRunning the schema scripts creates the tables and views in the allocatedtablespaces created by running the provided or modified admin scripts. Theschema scripts are located on IBM Tivoli Configuration Manager Installation CD inthe /FRESH/SQL/schema directory.

Installing DB2 schemasConfiguring the DB2 RDBMS consists of running several schema scripts, eachcreating tables in the DB2 RDBMS. The schema scripts are as follows:

inv_db2_schema.sqlInstalls the inv_db repository schema, which defines its tables and views.

h_inv_db2_schema.sqlInstalls the inventory history tables for the configuration repository(optional).

plan_db2_schema.sqlInstalls the planner repository schema, which defines its tables and views.

ccm_db2_schema.sqlInstalls the ccm repository schema, which defines its tables and views.

mdist_db2_schema.sqlInstalls the mdist2 repository schema, which defines its tables and views.

If you did not run the schema scripts during the installation, complete thefollowing steps:1. From the IBM Tivoli Configuration Manager Installation CD, copy the

following files from the FRESH/SQL/schema directory to a temporarydirectory on the RIM host:v inv_db2_schema.sqlv h_inv_db2_schema.sqlv plan_db2_schema.sqlv ccm_db2_schema.sqlv mdist2_db2_schema.sql

2. Connect to the RDBMS server:db2 connect to database user name using password

where database is the name or alias of the database in the system databasedirectory, name is the user name of the instance owner of the database, andpassword is the password associated with the user.

3. Run the database schema scripts to create the database and write output to thescreen and to associated log files:


db2 -f script_name.sql -o -t -z log_name.log

where script_name is the name of the schema script and log_name is the name ofthe log file. Repeat this step for each schema script.

4. Test that the schema was installed.

Installing Informix schemasConfiguring the Informix RDBMS consists of running several schema scripts aswell as creating the database and the database user. When determining the size ofthe database, allow 1 MB for each machine to be scanned. For details aboutcreating databases and database users, see the Informix documentation.

The schema scripts for installing the configuration repository are as follows:

inv_infx_schema.sqlInstalls the inv_db repository schema, which defines its tables and views.

h_inv_infx_schema.sqlInstalls the inventory history tables for the configuration repository(optional).

plan_infx_schema.sqlInstalls the planner repository schema, which defines its tables and views.

ccm_infx_schema.sqlInstalls the ccm repository schema, which defines its tables and views.

mdist_infx_schema.sqlInstalls the mdist2 repository schema, which defines its tables and views.

After creating the repositories in the Informix RDBMS, complete the followingsteps:1. Verify that you have at least 20,000 locks in the onconfig file before running the

schema script. This is the minimum required locks.2. From the IBM Tivoli Configuration Manager Installation CD, copy the

following files from the /FRESH/SQL/schema directory to a temporarydirectory on the RIM host:v inv_infx_schema.sqlv h_inv_infx_schema.sqlv plan_infx_schema.sqlv ccm_infx_schema.sqlv mdist_infx_schema.sql

3. From the temporary directory on the RIM host, run the schema scripts:dbaccess db@$INFORMIXSERVER script_name.sql >> log_name.log $2>$1

where db is the name of the repository, script_name is the name of the schemascript, and log_name is the name of the log file. Repeat for each schema script.


Installing Microsoft SQL Server schemasConfiguring the Microsoft SQL Server RDBMS consists of running several schemascripts, each creating tables in the SQL Server RDBMS. The schema scripts are asfollows:


inv_ms_sql_schema.sqlInstalls the inv_db repository schema, which defines its tables and views.

h_inv_ms_sql_schema.sqlInstalls the inventory history tables for the configuration repository(optional).

plan_ms_sql_schema.sqlInstalls the planner repository schema, which defines its tables and views.

ccm_ms_sql_schema.sqlInstalls the ccm repository schema, which defines its tables and views.

mdist_ms_sql_schema.sqlInstalls the mdist2 repository schema, which defines its tables and views.


following files from the /FRESH/SQL/schema directory to a temporarydirectory on the RIM host:v inv_ms_sql_schema.sqlv h_inv_ms_sql_schema.sqlv plan_ms_sql_schema.sqlv ccm_ms_sql_schema.sqlv mdist_ms_sql_schema.sql

2. From the temporary directory on the RIM host, run the schema scripts and logthe output:isql -U invtiv -P tivoli -i inv_ms_sql_schema.sql -o inv_ms_sql_schema.logisql -U invtiv -P tivoli -i h_inv_ms_sql_schema.sql -o h_inv_ms_sql_schema.logisql -U planner -P planner -i plan_ms_sql_schema.sql -o plan_ms_sql_schema.logisql -U ccm -P tivoli -i ccm_ms_sql_schema.sql -o ccm_ms_sql_schema.logisql -U mdstatus -P mdstatus -i mdist_ms_sql_schema.sql

-o mdist_ms_sql_schema.log

Note: The users specified using the –U option were created when the adminscripts were run.

3. Change the passwords for invtiv, planner, ccm, and mdstatus users. Use theappropriate isql command to change the user password for the database, anduse the wsetrimpw command to change the passwords in the RIM object.These two passwords must be the same. For information about using isql, seethe Microsoft SQL Server documentation.

4. Test that the schema was installed.5. Log out of the isql session:

exit

Installing Oracle schemasConfiguring the Oracle RDBMS consists of running several schema scripts, eachcreating required tables in the Oracle RDBMS. The schema scripts are as follows:

inv_ora_schema.sqlInstalls the inv_db repository schema, which defines its tables and views.

h_inv_ora_schema.sqlInstalls the inventory history tables for the configuration repository(optional).


plan_ora_schema.sqlInstalls the planner repository schema, which defines its tables and views.

ccm_ora_schema.sqlInstalls the ccm repository schema, which defines its tables and views.

mdist_ora_schema.sqlInstalls the mdist2 repository schema, which defines its tables and views.


following files from the /FRESH/SQL/schema directory to a temporarydirectory on the computer system where the Oracle client is installed:v inv_ora_schema.sqlv h_inv_ora_schema.sqlv plan_ora_schema.sqlv ccm_ora_schema.sqlv mdist_ora_schema.sql

2. Run the schema scripts associated with the Inventory components bycompleting the following steps:a. From this directory, start a SQL*Plus session:

sqlplus invtiv/password

where password is the RDBMS password set for the RDBMS user invtiv.b. Change the password for the user invtiv. Use the appropriate SQL*Plus

command to change the password. Use the wsetrimpw command to notifythe RIM object of this password change. For information about usingSQL*Plus, see the Oracle documentation.

c. Specify which log file to write information:spool inv_ora_schema.log

d. Run the script to install the tables and views:@inv_ora_schema.sql

The script installs the tables and views. The success and failure of the SQLstatements are written to the log.

e. Specify which log file to write information:spool h_inv_ora_schema.log

f. Run the script to install the tables and views:@h_inv_ora_schema.sql


g. Log out of the SQL*Plus session:quit

3. Run the schema scripts associated with the Activity Planner components bycompleting the following steps:a. From this directory, start a SQL*Plus session:

sqlplus planner/password

where password is the RDBMS password set for the RDBMS user planner.


b. Change the password for the user planner. Use the appropriate SQL*Pluscommand to change the password. Use the wsetrimpw command to notifythe RIM object of this password change. For information about usingSQL*Plus, see the Oracle documentation.

c. Specify which log file to write information:spool plan_ora_schema.log

d. Run the script to install the tables and views:@plan_ora_schema.sql


e. Log out of the SQL*Plus session:quit

4. Run the schema scripts associated with the Change Manager components bycompleting the following steps:a. From this directory, start a SQL*Plus session:

sqlplus ccm/password

where password is the RDBMS password set for the RDBMS user planner.b. Change the password for the user ccm. Use the appropriate SQL*Plus


c. Specify which log file to write information:spool ccm_ora_schema.log

d. Run the script to install the tables and views:@ccm_ora_schema.sql


e. Log out of the SQL*Plus session:quit

5. Run the schema scripts associated with the Distribution Status console bycompleting the following steps:a. From this directory, start a SQL*Plus session:

sqlplus mdstatus/password

where password is the RDBMS password set for the RDBMS user planner.b. Change the password for the user mdstatus. Use the appropriate SQL*Plus


c. Specify which log file to write information:spool mdist_ora_schema.log

d. Run the script to install the tables and views:@mdist_ora_schema.sql


e. Log out of the SQL*Plus session:


quit


Installing Sybase schemasConfiguring the Sybase RDBMS consists of running several schema scripts, eachcreating required tables in the Sybase RDBMS. The schema scripts are as follows:

inv_syb_schema.sqlInstalls the configuration repository schema, which defines its tables andviews.

h_inv_syb_schema.sqlInstalls the inventory history tables for the configuration repository(optional).

plan_syb_schema.sqlInstalls the planner repository schema, which defines its tables and views.

ccm_syb_schema.sqlInstalls the ccm repository schema, which defines its tables and views.

mdist_syb_schema.sqlInstalls the mdist2 repository schema, which defines its tables and views.

In you did not run the schema scripts during the installation, complete thefollowing steps:1. From the IBM Tivoli Configuration Manager Installation CD, copy the

following files from the /FRESH/SQL/schema directory to a temporarydirectory on the RIM host:v inv_syb_schema.sqlv h_inv_syb_schema.sqlv plan_syb_schema.sqlv ccm_syb_schema.sqlv mdist_syb_schema.sql

2. From the temporary directory on the RIM host, run the schema scripts and logthe output:isql -U invtiv -P tivoli -i inv_syb_schema.sql -o inv_syb_schema.logisql -U invtiv -P tivoli -i h_inv_syb_schema.sql -o h_inv_syb_schema.logisql -U planner -P planner -i plan_syb_schema.sql -o plan_syb_schema.logisql -U ccm -P tivoli -i ccm_syb_schema.sql -o ccm_syb_schema.logisql -U mdstatus -P mdstatus -i mdist_syb_schema.sql -o mdist_syb_schema.log

Note: The users specified using the –U option were created when the adminscripts were run.

3. Change the passwords for invtiv, planner, ccm, and mdstatus users. Use theappropriate isql command to change the user password for the database, anduse the wsetrimpw command to change the passwords in the RIM object.These two passwords must be the same. For information about using isql, seethe Sybase documentation.

4. Test that the schema was installed.5. Log out of the isql session:

exit


Running Enterprise Directory Query Facility scriptsTo enable Enterprise Directory Query Facility user management, you must run theLightweight Directory Access Protocol (LDAP) script after installing the EnterpriseDirectory Query Facility component. These LDAP scripts are in LDAP DataInterchange Format (LDIF). A directory server uses files in LDIF to describe adirectory and directory entries in text format. LDIF is used to exchange data andsynchronize data between LDAP servers. For additional information, see yourLDAP documentation.

Each of the LDAP scripts extends the enterprise directory schema. These scripts arelocated in the $BINDIR/TAS/DirQuery/SCRIPTS directory on the Tivoli server.You must copy the file from the Tivoli server to the LDAP server and run thescript locally so that you can run queries from the LDAP server against EnterpriseDirectory Query Facility.

For Microsoft Active DirectoryAdupd.ldf

For IBM SecureWayIBMupd.ldf

For Novell Directory ServerNDSupd.ldf


Chapter 6. Maintaining and troubleshooting a configurationmanagement environment

This chapter includes information that helps you manage your configurationmanagement environment as well as perform routine maintenance. This chaptercontains the following topics:v “Testing schemas”

Provides information about SQL scripts that you can run to test the installationof the IBM Tivoli Configuration Manager schemas

v “Registering Enterprise Directory Query Facility resources” on page 83Provides information about registering Enterprise Directory Query Facilityresources.

v “Completing a failed Server installation” on page 83Provides information about how to complete the Server installation in case offailure.

v “Understanding return values for Web Gateway installations” on page 83Provides the return values generated during the installation of the Web Gatewaycomponents.

v “Installing software signatures” on page 85Provides information about installing and updating software signatures.

v “Maintaining the Web Gateway component” on page 85Provides information about common maintenance tasks when using the WebGateway component. This section includes the following topics:– Changing the enrollment URL– Configuring for use with IP addresses– Configuring for use with non-standard ports– Configuring for use with WebSEAL junctions– Increase tablespace in the Web Gateway database– Configure the DB2 client

v “Running common RDBMS commands” on page 88Provides information about the common commands used by the supportedRDBMS server and client software.

Testing schemasExcept for the Web Gateway component, the installation program provided by IBMTivoli Configuration Manager tests for the successful installation of the schemaobjects and reports success or failure using the following process:1. Parses the CREATE TABLE, VIEW, and COLUMN statements from each

provided schema script2. Compiles a list of all successfully created schema objects3. Compares the lists (expected versus actual)4. Displays a notice of success or failure for the objects

When installing the schema outside of the provided installation program, you cancheck the log file for success or failure. The log file, however, contains many SQL


messages. Some of these messages are harmless, but some could indicate potentialproblems. Additionally, you could run the following RDBMS commands, andmanually compare these against those documented in IBM Tivoli ConfigurationManager Database Schema Reference.

For DB2Run the following scripts, as required:

Tables select name from sysibm.systables where type=’T’

Views select name from sysibm.systables where type=’V’

Triggers select name from sysibm.systriggers

All select name from sysibm.systables where type in(’T’,’V’) union select name from sysibm.systriggers

For Informix

Run the following scripts, as required:

Tables select tabname from systables where tabtype=’T’

Views select tabname from systables where tabtype=’V’

Triggers select trigname from systriggers

All select tabname from systables where tabtype in(’T’,’V’) union select trigname from systrigger

Note: When tables names are created in the Informix database, the namesare changed to lowercase. When performing the compare operation,use a case-insensitive compare operation.

For Microsoft SQL ServerRun the following scripts, as required:

Tables select name from sysobjects where xtype=’U’

Views select name from sysobjects where xtype=’V’

Triggers select name from sysobjects where xtype=’TR’

All select name from sysobjects where type in(’U’,’V’,’TR’)

For OracleRun the following scripts, as required:

Tables select object_name from sys.user_objects whereobject_type=’TABLE’

Views select object_name from sys.user_objects whereobject_type=’VIEW’

Triggers select object_name from sys.user_objects whereobject_type=’TRIGGER’

All select object_name from sys.user_objects whereobject_type in (’TABLE’,’VIEW’,’TRIGGER’)

For SybaseRun the following scripts, as required:

Tables select name from sysobjects where xtype=’U’

Views select name from sysobjects where xtype=’V’


Triggers select name from sysobjects where xtype=’TR’

All select name from sysobjects where type in(’U’,’V’,’TR’)

Registering Enterprise Directory Query Facility resourcesFor resource management of endpoints as users, you need to install both theResource Manager and Enterprise Directory Query Facility components. Becausethe installation of the Enterprise Directory Query Facility component runs thewresource command, you should install the Resource Manager component beforeinstalling the Enterprise Directory Query Facility component. If you installed theEnterprise Directory Query Facility component before installing the ResourceManager component, you must run the wresource command as follows:wresource add TMF_Query QueryDirectory OBJECT_NIL User

For additional information about the wresource command, see IBM TivoliConfiguration Manager User’s Guide for Deployment Services.

Completing a failed Server installationIf you selected No Configuration during a custom Server installation or if theplanner, ccm, or inventory RIM object is not working, you need to perform thefollowing steps:1. Ensure that the RIM object is working.2. Register the Activity Planner plug-ins by running the reg_swd_plugin.sh and

reg_inv_plugin.sh scripts in the $BINDIR/TME/APM/SCRIPTS subdirectory.3. Register the Change Manager plug-ins by running the reg_swd_plugin.sh and

reg_invscan_plugin.sh scripts in the $BINDIR/TME/CCM/SCRIPTSsubdirectory.

4. Register the pervasive and user Resource Manager resource types by runningthe RegisterPervasive.sh and RegisterUser.sh scripts in the $BINDIR/TRMsubdirectory.

5. Install the Inventory software signatures

For additional information about the running these registration scripts, see IBMTivoli Configuration Manager User’s Guide for Deployment Services. For informationabout installing Inventory signatures, see IBM Tivoli Configuration Manager User’sGuide for Inventory.

Understanding return values for Web Gateway installationsWhen you install either the Web Gateway server or the Web Gateway database, theinstallation log file contains return values.

The following table lists the mappings between the return values associated withan installation of the Web Gateway database and what they mean.

Table 22. Return values associated with the installation of the Web Gateway database

Value Description

0 The installation was successful.

100 There was a general error during the installation. Check the installation logfile.

101 The user stopped the installation before completion.

Chapter 6. Maintaining and troubleshooting a configuration management environment 83

Table 22. Return values associated with the installation of the Web Gatewaydatabase (continued)

Value Description

102 The installation failed. The installation requires a user withroot/Administrator authority. Restart the installation as a user with theappropriate authorization.

103 The installation failed. The values specified in the Database home and theDatabase container home fields must be different.

109 The installation failed. The DB2 db2iadm1 group is not defined. Create thisgroup and restart the installation.

112 The installation failed. Either the dmsadmin user or the dmsuser user is notdefined. Ensure that these users are created and restart the installation.

115 The installation failed. The dmsadmin user is not defined. Create this user andrestart the installation.

117 The installation failed. There is no .profile file associated with the valuespecified in the DB2 instance field. Create this file and restart the installation.

118 The installation failed. There is no .profile file associated with the dmsadminuser. Create this file and restart the installation.

200 The installation failed. The database was not found or is invalid. Verify theinstallation of the RDBMS server and restart the installation.

201 The installation of the schema failed. Ensure that there is enough availabledisk space on the RDBMS server and run the schema script again.

The following table lists the mappings between the return values associated withan installation of the Web Gateway server and what they mean.

Table 23. Return values associated with the installation of the Web Gateway server

Value Description

0 The installation was successful.

2 The installation failed. The installation requires a user withroot/Administrator authority. Restart the installation as a user with theappropriate authorization.

3 The installation failed. One or more specified values are invalid. Restart theinstallation and ensure that these values are in correct format

10 The installation failed. The database was not found or is invalid. Verify theinstallation of the RDBMS server and the RDBMS client, and restart theinstallation.

11 The installation failed. The WebSphere Application Server installation was notfound or is invalid. Ensure that the http.conf file exists and contains recordsfor the plug-ins.

12 The installation failed. The value specified in the Web server home field isinvalid. Restart the installation and ensure that this value is correct.

13 The installation failed. The value specified in the JDBC driver home field isinvalid. Restart the installation and ensure that this value is correct.

14 The installation failed. The data directory for the endpoint is invalid. Ensurethat an endpoint is installed and restart the installation.

15 The installation failed. The library directory for the endpoint is invalid. Ensurethat an endpoint is installed and restart the installation.


Table 23. Return values associated with the installation of the Web Gatewayserver (continued)

Value Description

100 The installation failed. The directory structure for WebSphere ApplicationServer cannot be created. Ensure that there is enough available disk space,that this space has write access, and restart the installation.

101 This installation failed. WebSphere Application Server is not running or isincorrectly configured. Start the WebSphere Application server and restart theinstallation.

102 The installation failed. Ensure that this operating system is supported. If it issupported, restart the installation.

103 The directory specified as the destination directory could not be created.Ensure that there is enough available disk space, that this space has writeaccess, and restart the installation.

200 A Java exception occurred while configuring the device plug-in. Check theinstallation log file for additional exceptions.

201 An error occurred while configuring the device plug-in. Check the installationlog for additional errors.

210 The installation failed. The endpoint installation is invalid. Ensure that anendpoint is installed and restart the installation.

220 The installation failed. Unable to configure the WebSphere Application Server.Remove the hostname_DMS_WebApp from the application server, stop andrestart WebSphere Application Server, and restart the installation.

Installing software signaturesAfter installing or upgrading IBM Tivoli Configuration Manager, you need toinstall or upgrade the software signatures used by the Inventory component. Thesesoftware signatures are required for performing inventory scans. Softwaresignatures are updated quarterly and are available of the Support Web site.Additionally, you can create and maintain your own set of custom softwaresignatures. For details about installing and updating software signatures andcreating and maintaining custom software signatures, see IBM Tivoli ConfigurationManager User’s Guide for Inventory.

Maintaining the Web Gateway componentThis section discusses common tasks that you might need to perform while usingthe Web Gateway component.

Changing the enrollment URLDuring the installation of the Web Gateway component, the default enrollmentURL as defined is as follows:http://hostname/dmserver/DeviceEnrollmentServlet

where hostname is the host name, fully qualified host name, or IP address of theWeb application server.

For example, if the WebSphere Web server is on monolake.ibm.com and uses port8080, change directory to where the deviceclass command is located and modifythe enrollment by entering the following commands:

For UNIX


cd $TWG_HOME/bindeviceclass.sh -modify Palm

-enroll http://monolake.ibm.com:8080/dmserver/DeviceEnrollmentServletdeviceclass.sh -modify Wince

-enroll http://monolake.ibm.com:8080/dmserver/DeviceEnrollmentServletdeviceclass.sh -modify Nokia9200Series

-enroll http://monolake.ibm.com:8080/dmserver/DeviceEnrollmentServlet

For Windowscd /Program Files/TivTWG/bindeviceclass.bat -modify Palm

-enroll http://monolake.ibm.com:8080/dmserver/DeviceEnrollmentServletdeviceclass.bat -modify Wince

-enroll http://monolake.ibm.com:8080/dmserver/DeviceEnrollmentServletdeviceclass.bat -modify Nokia9200Series

-enroll http://monolake.ibm.com:8080/dmserver/DeviceEnrollmentServlet

Configuring for use with IP addressesTo configure the Web Gateway component to use IP addresses instead of a domainname service (DNS), you need to perform the following steps:1. Run the enrollment comments listed in “Changing the enrollment URL” on

page 85. Instead of specifying the host name of the Web Gateway server,specify its IP address.

2. Modify the web.xml file in the$WAS_HOME/installedApps/hostname_DMS_Webapp.ear/dmserver.war/WEB-INF directory. In the web.xml file, change the value of the InitParam_1keyword to the IP address of the Web Gateway server.

3. Edit the twgConfig.properties file in$WAS_HOME/installedApps/hostname_DMS_Webapp.ear/dmserver.war/WEB-INF/classes directory. In the twgConfig.properties file, change the value of theTWG_HOSTNAME keyword to your local IP address.

Configuring for use with non-standard HTTP portsTo configure the Web Gateway to use non-standard HTTP ports, ports other than80, perform the following steps:1. Change the Web server listening port by modifying the httpd.conf file that

corresponds with the Web Server installation.2. Change the port number in WebSphere Application Server.

a. Start the WebSphere adminclient utility.b. Select Virtual Hosts.c. For each virtual host:

1) Modify the host alias from *.80 to *.x where x is the port to use insteadof port 80.

2) Select Apply.3) Right-click on the name of the host name, and select Regen Web Server

Plugin.d. Exit the adminclient utility.

3. Edit the web.xml file in the$WAS_HOME/installedApps/hostname_DMS_Webapp.ear/dmserver.war/WEB-INF directory. Change the value of the InitParam_2 keyword to the new portnumber.

4. Edit the twg.cfg file in $LCF_DATDIR. Change the port number to the newport number.


5. Edit the twgConfig.properties file in$WAS_HOME/installedApps/hostname_DMS_Webapp.ear/dmserver.war/WEB-INF/classes directory. Change the value of the WEB_SERVER_PORT keywordto the new port number.

6. Edit the enrollment URLs using the procedure in “Changing the enrollmentURL” on page 85.

Configuring for use with WebSEAL junctionsWebSEAL junctions can be used to protect device management URLs. If youconfigured a junction, perform the following steps:1. Configure the enrollment URL using the procedure in “Changing the

enrollment URL” on page 85.2. Edit the web.xml file in the

$WAS_HOME/installedApps/hostname_DMS_Webapp.ear/dmserver.war/WEB-INF directory. Add the following stanza after thefullyQualifiedHostNameOfServer parameter definition:<init-param>

<param-name>authProxyDmsUrl</param-name><param-value>URL</param-value>

</init-param>

where URL is the Web address of your WebSEAL junction in the format:

http://WebSEAL_host/WebSEAL_junction

Increasing tablespace in the Web Gateway databaseBy default, the installation of the Web Gateway database creates enough tablespacefor 200 devices to have outstanding job requests at one time in the Web Gatewaydatabase (ISPB_DATA tablespace). To allow more pending jobs, increase thetablespace size.

The Web Gateway database also has database indexes (ISPB_INDEX tablespace).You might need to increase this tablespace as well.

For example, you can use the following command to increase the tablespace forISPB_DATA by adding to the /dmsdb/dms/data003 file:alter tablespace ISPB_DATA add (file ’/dmsdb/dms/data003’ 50000)

Configuring the DB2 clientIf the Web Gateway component is using the DB2 client locally to connect to aremote DB2 server, you need to perform the following steps:1. Catalog the database server node, if remote:

db2 catalog tcpip node db2node remote hostname server service_name

where db2node is the name of the system where the DB2 client is installed(which must be unique in your node directory list), hostname is the fullyqualified name of the system where the DB2 server is installed, andservice_name is the connection port name as defined in the services file.

2. Catalog the database:db2 catalog database dms at db2node authentication server

where db2node is the name of system where the DB2 client is installed.3. Test connectivity:


db2 connect to dms user dmsadmin using password

where password is the password for the dmsadmin user. If the databaseconnects, a similar message to the following message is displayed:Database server = DB2/system_databaseSQL authorization ID = DMSADMINLocal database alias = DMS

where system_database is the operating system and level of your database serversoftware; for example, LINUX 7.2.3.

Running common RDBMS commandsThis section provides information about common RDBMS commands, by RDBMS.These commands can be run from either the RDBMS client or server. Thesecommands are useful while working with the RDBMS software to create andmaintain databases. These commands are not comprehensive, but are those forperforming basic, but necessary, operations against the database. For a completelisting of commands and additional details about the provided comments, see theRDBMS documentation.

DB2 commandsThere are several commands that are important when using the DB2 RDBMS. Foradditional information about these and other database commands, see the DB2documentation. These commands are used for the following operations:

Start a DB2 interactive sessionTo start an interactive session, enter the follow command:db2

Catalog the DB2 server nodeTo catalog the DB2 server node, enter the following command:db2 catalog tcpip node db2node remote hostname server service_name

where db2node is the name of the system where the DB2 client is installed(which must be unique in your node directory list), hostname is the fullyqualified name of the system where the DB2 server is installed, andservice_name is the connection port name as defined in the services file.

Catalog remote DB2 databasesTo catalog a remote database, enter the following command:db2 catalog database db_name as alias_name at node db2node

where db_name is the name of the remote database, alias_name is the nameof the client instance, and db2node is the name of the system where the DB2client is installed.

Connect to the DB2 serverTo connect to a DB2 server, enter the following command:db2 connect to database user name using password

where database is the name or alias of the database in the system databasedirectory, name is the user name of the instance owner of the database, andpassword is the password for the previous user.

Run scriptsTo run a script, enter the following command:


db2 -f script_name -o -t -z log_name

where script_name is the name of the script and log_name is the name of thelog file.

End a DB2 sessionTo log out of an interactive session, enter the following command:quit

Informix commandsThere are several commands that are important when using the Informix RDBMS.For additional information about these and other database commands, see theInformix documentation.

To run a script, enter the following command:dbaccess db@$INFORMIXSERVER script_name >> log_name $2>$1

where db is the name of the database, script_name is the name of the script, andlog_name is the name of the log file.

Microsoft SQL Server commandsThere are several commands that are important when using the Microsoft SQLServer RDBMS. For additional information about these and other databasecommands, see the Microsoft SQL Server documentation. These commands areused to perform the following operations:

Start an isql interactive sessionTo start an interactive session, enter the following command:isql

Run scriptsTo run a script, enter the following command:isql -U user -P password -i script_name.sql -o log_name.log

where:

user The owner of the database. To run admin scripts, the user is the sauser. The admin script creates the database owner for therepository. When you run the schema scripts, the user must be thedatabase owner.

passwordThe password for the sa user.

script_nameThe name of the script.

log_nameThe name of the log file.

End an isql sessionTo log out of an isql session, enter the following command:exit


Oracle commandsThere are several commands that are important when using the Oracle RDBMS.For additional information about these and other database commands, see theOracle documentation. These commands are used to perform the followingoperations:

Start a SQL*Plus interactive sessionTo start an interactive SQL*Plus session, enter the following command:sqlplus system/password

where password is the RDBMS password set for the RDBMS user system.

Specify log filesTo specify a log file, enter the following command:spool log_file.log

where log_file is the name of the log file. You must specify a log file beforerunning an SQL script if you want to retain log history.

Run scriptsTo run a script, enter the following command:@script_name.sql

where script_name is the name of the script.

End a SQL*Plus sessionTo log out of a SQL*Plus session, enter the following command:quit

Sybase commandsThere are several commands that are important when using the Sybase RDBMS.For additional information about these and other database commands, see theSybase documentation. These commands are used to perform the followingoperations:

Start an isql interactive sessionTo start an interactive session, enter the following command:isql

Run scriptsTo run a script, enter the following command:isql -U user -P password -i script_name.sql -o log_name.log

where:

user The owner of the database. To run admin scripts, the user is the sauser. The admin script creates the database owner for therepository. When you run the schema scripts, the user must be thedatabase owner.

passwordThe password for the sa user.

script_nameThe name of the script.

log_nameThe name of the log file.


End an isql sessionTo log out of an isql session, enter the following command:exit


Appendix A. Planning and installation worksheets

This appendix contains the following worksheets that are designed to help youthrough the planning and installation processes. The provided worksheets are asfollows:

PlanningCompleting this worksheet will help to guide you through the planningprocess. Completing this worksheet will help you determine which of theinstallation mechanisms to use to meet the desired deploymentrequirements of your configuration management environment. Thisworksheet should be used when creating your overall Tivoli environmentdeployment plan. The information presented in this worksheet is for IBMTivoli Configuration Manager.

See “Planning worksheet” on page 95.

Server installationCompleting these worksheets will help to guide you through theinstallation of a Tivoli server with IBM Tivoli Configuration Manager andTivoli Management Framework. Completing these worksheets will helpyou determine which of the installation mechanisms to use to meet thedesired deployment requirements of your configuration managementenvironment.

See “Server installation worksheets” on page 97.

Web Gateway installationCompleting these worksheets will help to guide you through theinstallation of the Web Gateway component and its associated IBM TivoliConfiguration Manager services. Completing these worksheets will helpyou meet the desired deployment requirements of your configurationmanagement environment.

See “Web Gateway installation worksheets” on page 111.

Desktop installationCompleting these worksheets will help to guide you through theinstallation of Tivoli Desktop for Windows and its associated IBM TivoliConfiguration Manager administrative interfaces. Completing theseworksheets will help you the desired deployment requirements of yourconfiguration management environment.

See “Desktop installation worksheets” on page 117.

Tivoli environment upgradeCompleting these worksheets will help to guide you through theinstallation and upgrade of the IBM Tivoli Configuration Manager andTivoli Management Framework components on all systems in a Tivoliregion. Completing these worksheets will help you determine which of theinstallation mechanisms to use to meet the desired deploymentrequirements of your configuration management environment.

See “Tivoli environment upgrade worksheets” on page 119.


Planning worksheetComplete the following worksheet to help guide you through the planningprocess. Completing this worksheet will help you during the installation of IBMTivoli Configuration Manager.1. Do you have a previous installation of IBM Tivoli Configuration Manager? A

previous installation would be Tivoli Management Framework, TivoliInventory, or Tivoli Software Distribution.__ Yes__ No

If Yes, you need to upgrade your Tivoli environment. Use the “Tivolienvironment upgrade worksheets” on page 119. If No, you need to install theTivoli server to create your Tivoli environment. Use the “Server installationworksheets” on page 97.

2. Which RDBMS software are you using?__ DB2, the only supported RDBMS for the Web Gateway component__ Informix__ Microsoft SQL Server__ Oracle__ Sybase

Which version?

See Tivoli Management Framework Release Notes for a list of supported RDBMSversions to ensure that your RDBMS software is at a supported level.

3. Which operating system are you running?__ UNIX__ Windows__ Linux

Which version?

Does it have enough memory?__ Yes__ No

Does it have enough available disk space?__ Yes__ No

See Tivoli Management Framework Release Notes and IBM Tivoli ConfigurationManager Release Notes for a list of supported versions, hardware, and softwarerequirements to ensure that your operating system meets these systemrequirements. You might need to purchase new hardware.

4. Which primary configuration management features do you plan to use?__ Inventory scans of machines__ Software distributions to machines

Appendix A. Planning and installation worksheets 95

__ Create, schedule, and run activity plans__ Manage configurations using reference models

If you selected any of the previous configuration management features, use the“Server installation worksheets” on page 97 or the “Tivoli environment upgradeworksheets” on page 119 depending on whether you have an existing Tivolienvironment.

__ Inventory scan of devices__ Software distribution to devices__ Access Web objects

If you selected any of the previous configuration management features, use the“Web Gateway installation worksheets” on page 111.

__ Run the Inventory administrative interface from the Tivoli desktop__ Run the Change Manager administrative interface from the Tivoli

desktop__ Run the Distribution Status console from the Tivoli desktop__ Run the Activity Planner administrative interface from the Tivoli desktop

If you selected any of the previous features, use the “Desktop installationworksheets” on page 117.

5. Do you need this software to operate in languages other than English?__ Yes__ No

If Yes, which languages?__ Chinese, Simplified__ Chinese, Traditional__ French__ German__ Italian__ Japanese__ Korean__ Portuguese, Brazilian__ Spanish

Depending on the IBM Tivoli Configuration Manager component or service andthe installation mechanisms, you might need to install one or more languagepackages.


Server installation worksheetsComplete the following worksheet to help guide you through the installation ofthe server components of IBM Tivoli Configuration Manager.1. For which type of Tivoli environment are you creating the Tivoli server?

__ Simple—An environment for device management or other simpleconfigurations, a testing or demonstration environment, or a trainingenvironment.

__ Complex—An environment managing hundreds to thousands ofendpoints.

For a simple environment, use the installation program provided by IBM TivoliConfiguration Manager.

For a complex environment, use either the installation program provided byIBM Tivoli Configuration Manager or the installation mechanisms provided byTivoli Management Framework or Tivoli Software Installation Service. Whenusing the installation program provided by IBM Tivoli Configuration Manageryou might need to uninstall components and services of IBM TivoliConfiguration Manager as move RIM object to other managed nodes after thesemanaged nodes are created.

2. Install and configure the RDBMS software denoted in step 2 on page 95.

Depending on the RDBMS selected, you will need to perform additionalconfiguration for the installation program to complete successfully. For details, seeChapter 5, “Working with repositories and queries” on page 67.3. Did you complete the additional RDBMS configuration?

__ Yes__ No

If you selected No, review the specific requirements in one of the followingsections:v “Creating DB2 tablespaces” on page 68, which discusses requirements for

databases, users, and passwordsv “Creating Microsoft SQL Server tablespaces” on page 69, which discusses

directory and file space requirements.v “Creating Oracle tablespaces” on page 70, which discusses database

requirements.v “Creating Sybase tablespaces” on page 72, which discusses directory, file

space, and device requirements.

Note: If you are using an Informix RDBMS, you must create the admin scriptbefore performing this installation.

4. Which components and services do you need to install?__ Inventory__ Software Distribution__ Scalable Collection Service, always installed by provided installation

program__ Resource Manager, always installed by provided installation program__ Activity Planner, always installed by provided installation program


__ Change Manager, always installed by provided installation program__ Enterprise Directory Query Facility, always installed by provided

installation program__ Web Interfaces, always installed by provided installation program

If you selected all of these components and services and plan to have a simpleenvironment, use the provided installation program and install through thetypical path.

If you select some of these components and services and plan to have a simpleenvironment, use the provided installation program and install through thecustom path.

If you selected any of these components and services and have a complexenvironment, use the provided installation program and install through theappropriate path or use the installation mechanisms provided by TivoliManagement Framework.

5. Which installation mechanism do you plan to use?__ Typical path of provided installation program__ Custom path of provided installation program__ Tivoli Management Framework

For the typical path, go to “Typical path for server installation worksheet” onpage 99.

For the custom path, go to “Custom path for server installation worksheet” onpage 101.

For Tivoli Management Framework, go to “Tivoli Management Frameworkmechanisms for server installation worksheet” on page 106.


Typical path for server installation worksheetThe following information is required during a typical installation.1. Select the language in which you want the wizard to be displayed, and click

OK. English and the language selected are installed. For language support inother locales, you might need to install them.

2. Read the welcome information and click Next.

3. Read the license agreement, select the acceptance radio button, and click Next.

4. Click the Typical radio button, and click Next.

5. If desired, click the Browse button to select a different destination directory,and click Next.

6. Provide the following information:

Table 24. Field labels and values for the Specify the Repository ConfigurationInformation window

Field label Input value

Database vendor

Database client interface home—Thedirectory where the commands used bythe RDBMS client are located

Specify this information in the appropriate fields and click Next.


Table 25. Field labels and values for Specify Database Configuration Information


Database path—The directory on the RIMhost where the RDBMS software isinstalled

Database vendorNote: This field is not active.

Server ID—Specifies the vendor-specificinformation that enables the RDBMS toconnect to the RIM host.


v For Informix, use the value of theINFORMIXDIR variable.

v For Microsoft SQL Server, use the hostname of the machine where MicrosoftSQL Server is installed.

v For Oracle, use the value of theTWO_TASK variable that is located inthe tnsnames.ora file in the$ORACLE_HOME/network/admindirectory.

v For Sybase, use the value of theDSQUERY variable in the interfacesfile.


Table 25. Field labels and values for Specify Database ConfigurationInformation (continued)


DB2 instance name

Database administrator name

Database administrator password


8. Review the installation settings and click Next. The installation has started.

Note: If the installation cannot find required installation images, you areprompted with a Locate Images window where you specify the locationof the required installation image. If this window is displayed, locatethe image and click OK to continue the installation.

On Windows operating systems, complete the following steps. On UNIX operatingsystems, go to step 12.

9. When this portion of the installation completes on Windows operatingsystems, Select When to Reboot to Complete the Installation is displayed.

10. Click Now and then click Next to reboot the system.

11. After the system reboots, select the installation language again, and click OKto continue the installation.

12. When the installation completes, Installation Complete is displayed. Thisinformation show a successful installation or contains a list of which itemsfailed to install and the reasons for those failures.

13. Click Finish.


Custom path for server installation worksheetThe following information is required during a custom installation.1. Select the language in which you want the wizard to be displayed, and click

OK.



4. Click the Custom radio button, and click Next.

5. Select the components to install and click Next.

6. Select the additional languages to install and click Next.


Table 26. Field labels and values for the Specify Tivoli Server Information window


Destination directory

Gateway name

Gateway port


8. Provide the following information:a. Select the appropriate level of database configuration:

__ No configuration—do not run the admin scripts to create the usersand tablespaces, and do not run the schema scripts

__ Run schema scripts only, tablespaces already created

__ Create default tablespaces and run schema scripts

__ Create custom tablespaces and run schema scripts—click Browse tolocate the custom admin script

b. Provide the following information in the appropriate fields:

Table 27. Field labels and values for the Specify the Repository ConfigurationInformation window


Database vendor

Database client interface home—Thedirectory where the commands used bythe RDBMS client are locatedNote: This field is not active unless youspecify a configuration option otherthan No configuration.

c. Click Next.



Table 28. Field labels and values for the Specify the Repository Information forDistribution Status Console window


Database name—Maps to the Database IDoption

RIM user name—Maps to the User nameoption

RIM password—The password associatedwith the specified RIM user

Database path—Maps to the Databasehome option


Server ID

Database instance name—Maps to theInstance name (DB2 only) option

Database administrator name—Notavailable when No configurationspecified

Database administrator password—Notavailable when No configurationspecified



Table 29. Field labels and values for the Specify Activity Planner Information window


User name

Password



Table 30. Field labels and values for the Specify the Repository Information for ActivityPlanner window








Table 30. Field labels and values for the Specify the Repository Information for ActivityPlanner window (continued)


Server ID






Table 31. Field labels and values for the Specify the Repository Information forInventory window







Server ID






Table 32. Field labels and values for the Specify the Repository Information forChange Manager window





Table 32. Field labels and values for the Specify the Repository Information forChange Manager window (continued)





Server ID





14. Provide the following information:a. Select whether an LDAP is to be configured:

__ Do not configure Enterprise Directory Query Facility

__ Configure LDAP access for Enterprise Directory Query Facility

b. If you select Configure LDAP access for Enterprise Directory QueryFacility, provide the following information in the appropriate fields:

Table 33. Field labels and values for the Specify the Repository Information forEnterprise Directory Query Facility window


LDAP server host name

LDAP distinguished user name—Thedistinguished name of the user withLDAP Administrator privileges

LDAP password—The password for thespecified distinguished user

LDAP naming context—The namingcontext in the enterprise directory treelevel used to retrieve information with aquery

c. Click Next.


Note: If the installation cannot find required installation images, you areprompted with a Locate Images window where you specify the locationof the required installation image. If this window is displayed, locate


the image and click OK to continue the installation.

On Windows operating systems, complete the following steps. On UNIX operatingsystems, go to step 19.

16. When this portion of the installation completes on Windows operatingsystems, Select When to Reboot to Complete the Installation is displayed.

17. Click Now and then click Next to reboot the system.

18. After the system reboots, select the installation language again, and click OKto continue the installation.

19. When the installation completes, Installation Complete is displayed. Thisinformation show a successful installation or contains a list of which itemsfailed to install and the reasons for those failures.

20. Click Finish.

21. If you selected No configuration in step 8 on page 101, run the admin andschema scripts as documented in Chapter 5, “Working with repositories andqueries” on page 67.

22. Create the remainder of your Tivoli region using the “Tivoli ManagementFramework mechanisms for server installation worksheet” on page 106.


Tivoli Management Framework mechanisms for serverinstallation worksheet

Complete the following worksheet to help guide you through the installation of aconfiguration management environment.1. Install the Tivoli server following the instructions in Tivoli Enterprise

Installation Guide.

2. Create your Tivoli region (managed nodes and gateways) following theinstructions in Tivoli Enterprise Installation Guide.

3. Which IBM Tivoli Configuration Manager components selected in step 4 onpage 97 are to be installed on the Tivoli server?__ Scalable Collection Service (required by Inventory)__ Inventory__ Inventory Gateway__ Software Distribution__ Software Distribution Gateway__ Resource Manager__ Resource Manager Gateway__ Activity Planner__ Change Manager__ Enterprise Directory Query Facility__ Web Interfaces

4. If you selected Scalable Collection Service in step 3, install this patchfollowing the instructions in Tivoli Enterprise Installation Guide.

5. If you selected Inventory in step 3:a. Follow the installation instruction in Tivoli Enterprise Installation Guide.b. Specify the following installation options in the Installation Options

window.

Table 34. Field labels and values for the Inventory component


Data handler host

MDist 2 callback host

Database vendor

RIM host

Database ID

Database home

Server ID

User name

Instance name (DB2 only)

For details about the installation options, see “Inventory” on page 40.


6. If you selected Inventory Gateway in step 3 on page 106, install thiscomponent following the instructions in Tivoli Enterprise Installation Guide.

7. If you selected Software Distribution in step 3 on page 106, install this productfollowing the instructions in Tivoli Enterprise Installation Guide.

8. If you selected Software Distribution in step 3 on page 106, install this productfollowing the instructions in Tivoli Enterprise Installation Guide.

9. If you selected Resource Manager in step 3 on page 106:a. Follow the installation instruction in Tivoli Enterprise Installation Guide.b. When prompted, specify the following installation options in the

Installation Options window.

Table 35. Field labels and values for the Resource Manager component


Database vendor

RIM host

Database ID

Database home

Server ID

User name


For details about the installation options, see “Resource Manager” onpage 42.

10. If you selected Resource Manager Gateway in step 3 on page 106, install thisproduct following the instructions in Tivoli Enterprise Installation Guide.

11. If you selected Activity Planner in step 3 on page 106:a. Follow the installation instruction in Tivoli Enterprise Installation Guide.b. When prompted, specify the following installation options in the


Table 36. Field labels and values for the Activity Planner component


Database vendor

RIM host

Database ID

Database home

Server ID

User name


Activity Planner user name

Activity Planner password


For details about the installation options, see “Activity Planner” onpage 35.

12. If you selected Change Manager in step 3 on page 106:a. Follow the installation instruction in Tivoli Enterprise Installation Guide.b. When prompted, specify the following installation options in the


Table 37. Field labels and values for the Change Manager component


Database vendor

RIM host

Database ID

Database home

Server ID

User name


For details about the installation options, see “Change Manager” onpage 37.

13. If you selected Enterprise Directory Query Facility in step 3 on page 106:a. Follow the installation instruction in Tivoli Enterprise Installation Guide.b. When prompted, specify the following installation options in the


Table 38. Field labels and values for the Enterprise Directory Query Facilitycomponent


Server host name

Server port

Server SSL port

Distinguished name

Password

Access protocol

Naming context

Keystore path

Keystore password

For details about the installation options, see “Enterprise Directory QueryFacility” on page 39.

14. If you selected Web Interfaces in step 3 on page 106, install this productfollowing the instructions in Tivoli Enterprise Installation Guide.


15. Run the appropriate admin scripts as the database administrator. For detailsabout these admin scripts and any required modification, see Chapter 5,“Working with repositories and queries” on page 67.

16. Run the appropriate schema scripts as the RIM administrator. For detailsabout these schema scripts, see Chapter 5, “Working with repositories andqueries” on page 67.


Web Gateway installation worksheetsComplete the following worksheet to help guide you through the installation ofthe Web Gateway components of IBM Tivoli Configuration Manager.1. On which operating system are you running?

__ UNIX__ Windows__ Linux

a. Which version?

b. Does it have enough memory?__ Yes__ No

c. Does it have enough available disk space?__ Yes__ No

2. Did you create the dmsadmin and dmsuser system accounts on this computersystem?__ Yes__ No

If you selected No, create these system accounts using the information in“Creating the DB2 users for the Web Gateway component” on page 18.

3. Which features of the Web Gateway component do you plan to use?v Resource management of devicesv Web access to Inventory profilesv Web access to Software Distribution profiles

If you selected resource management of devices, install and configure:v IBM DB2v IBM WebSphere Application Server

If you selected either Web access feature or if you selected resourcemanagement of devices and want to optionally protect enrollment URLs, alsoinstall and configure:v IBM Tivoli Access Managerv IBM Tivoli Access Manager WebSEAL

If you selected all of the previous features, use the “Typical path for WebGateway installation worksheet” on page 113.

If you selected a subset of these features, use the “Custom path for WebGateway installation worksheet” on page 115.


4. What are the host name for the machines where the following software isinstalled.

Table 39. Machines for the components of IBM Tivoli Configuration Manager andprerequisite software

Software Machine host name

Endpoint

DB2 server

WebSphere server

Access Manager server

WebSEAL server

Web Gateway database

Web Gateway server

5. Are the host names specified in 4 the same?__ Yes__ No

If No, ensure that the appropriate client software is installed on the machinewhere the endpoint and Web Gateway server are installed.

6. Do you need this software to operate in languages other than English?__ Yes__ No

7. If you selected Yes in step 6, install language support by installing the SPBsprovided on the IBM Tivoli Configuration Manager Web Gateway CD. TheseSPBs are:v Tivoli_Web_Gateway_L10Nv Tivoli_WebUI_L10Nv Tivoli_INV_WebUI_plugin_L10Nv Tivoli_SWD_WebUI_plugin_L10N

Note: These SPBs install language support for all supported locales.


Typical path for Web Gateway installation worksheetThe following information is required during a typical installation.1. Select the language in which you want the wizard to be displayed, and click

OK.





Table 40. Field labels and values for the Specify Tivoli Endpoint window




Table 41. Field labels and values for the Specify Web Gateway Server window



Web server home

JDBC driver home


Table 42. Field labels and values for the Specify Web Gateway Database window



Database type

Database instance

Password

Confirm password




9. When the installation completes, Installation Complete is displayed. Thisinformation shows a successful installation or contains a list of which itemsfailed to install and the reasons for those failures.


10. Click Finish.

11. On Windows operating systems, reboot the system.


Custom path for Web Gateway installation worksheetThe following information is required during a custom installation. To determinewhich values for the installation options, use the information for the Web Gatewaydatabase in Table 18 on page 45 and the information for Web Gateway server inTable 19 on page 46.1. Select the language in which you want the wizard to be displayed, and click

OK.






Table 43. Field labels and values for the Information for the Tivoli Endpoint window



Gateway port

Endpoint port

Endpoint options



Table 44. Field labels and values for the Information for the Web Gateway Databasewindow



DB2 instance

DB2 port

Password for dmsadmin

Password for dmsuser



Table 45. Field labels and values for the Information for the Web Gateway Serverwindow



Web server home

JDBC driver home

Specify this information in the appropriate fields and click Next



Table 46. Field labels and values for the Specify Web Gateway Server ConfigurationInformation window


Host name of RDBMS server

Web server port

Web Gateway database name

RDBMS database name

Database port

Cluster environment

Database administrator name

Password

Specify this information in the appropriate fields and click Next


Table 47. Field labels and values for the Specify Access Manager Information window


Enable security

Host name

Junction point

Access Manager user name

Password

WebSEAL protocol

WebSEAL port

Access Manager configuration file

Access Manager JAR files home





13. Click Finish.

14. On Windows operating systems, reboot the system.


Desktop installation worksheetsComplete the following worksheet to help guide you through the installation ofTivoli Desktop for Windows and the required Tivoli desktop components of IBMTivoli Configuration Manager.1. On which operating system and version are you installing this software?

2. Do you need this software to operate in languages other than English?__ No__ Yes

If Yes, what additional languages?

3. Which installation mechanism are you using?__ The installation program provided by IBM Tivoli Configuration Manager__ The Tivoli Desktop for Windows installation following by the installation

of components using software package blocks (SPBs)

4. If you selected Yes in step 2, install language support as follows:v For Tivoli Desktop for Windows, install the additional language support by

installing the index files provided on the Tivoli Management FrameworkLanguage Support CD.

v For the components and services of IBM Tivoli Configuration Manager,install the additional language support by installing the SPBs provided onIBM Tivoli Configuration Manager Server CD.

Note: If you performed a custom installation and selected all languages, youdo not need to install these SPBs.


Typical path for desktop installation worksheetThe following information is required during a typical installation.1. Select the language in which you want the wizard to be displayed, and click

OK. Although you select a language other than English, only English supportis added. To add additional language support, you need to install them.






7. Click Finish.

Custom path for desktop installation worksheet1. Select the language in which you want the wizard to be displayed, and click

OK. Although you select a language other than English, only English supportis added. To add additional language support, you need to install them.







8. Click Finish.


Tivoli environment upgrade worksheetsComplete the following worksheet to help guide you through the upgrade of IBMTivoli Configuration Manager in your Tivoli environment.1. On which operating system and version are you installing this software?

2. Do you need this software to operate in languages other than English?__ No__ Yes

If Yes, what additional languages?

3. Which components need to be upgraded and which components need to beinstalled?

Table 48. Whether components need to be upgraded or installed.

Component Install Upgrade

Tivoli Management Framework

Inventory

Inventory Gateway

Software Distribution

Software Distribution Gateway

Resource Manager

Activity Planner

Change Manager

Web Interfaces

Enterprise Directory Query Facility

Note: You need to know which machines in your Tivoli environment requirean installation or an upgrade.

4. Which installation mechanism are you using?__ The installation program provided by IBM Tivoli Configuration Manager__ Tivoli Management Framework mechanisms and software package blocks

(SPBs)

5. If you selected Yes in step 2, install language support as follows:v For the Tivoli server and Tivoli Desktop for Windows, install the additional

language support by installing the index files provided on the TivoliManagement Framework Language Support CD.

v For the components and services of IBM Tivoli Configuration Manager,install the additional language support by installing the SPBs provided onIBM Tivoli Configuration Manager Upgrade CD.


Installation program for Tivoli environment upgrade worksheet1. Select the language in which you want the wizard to be displayed, and click

OK.


3. Read the information about performing backup operations.If you have a backup copy, select Backup done, and click Next.If you do not have a backup copy, click Cancel, make a backup copy, andrestart the installation.


5. Specify the directory where you want to store the upgrade plans, and clickNext.

6. Select the components you want to install or upgrade, and click Next.

7. Select additional language you want to install, and click Next.

8. Review the installation summary, and click Next.

9. Specify the location where you want to store the installation images, and clickNext.

Depending on whether components and services need to be installed or upgrades,you might be presented with one or more repository information windows. If oneof these windows is displayed, use the window-specific information from “Custompath for server installation worksheet” on page 101.

If the installation cannot find required installation images, you are prompted witha Locate Images window where you specify the location of the required installationimage. If this window is displayed, locate the image and click OK to continue theinstallation. On this window is a copy all files check box. Select this check boxwhen you want the installation images copied to this machine, which copies theimages to a depot on the machine.

Note: If you do not select the copy all files check box, Activity Planner tries tolocate these images from the original installation location (CD or mountedfile system). If these images are not in this location, the installation fails.When there is a local depot, Activity Planner can locate these images andsuccessfully complete the upgrade.

10. Review the installation settings, and click Next.

At this point, Tivoli Management Framework is upgraded, the Java componentsand the Activity Planner component are installed or upgraded, and any componentthat is selected to be upgrade that is not already in the environment is installed onthe Tivoli server.

11. When the installation or upgrade of these components complete, click Next.


12. Review the summary of the upgrade plan, and click Next.

13. Specify whether you want to create a single activity plan or individual activityplans for each component, and click Next.

14. Save or schedule the activity plan, and click Next.

15. When the plan is saved, click Finish.

At this point, the first activity plan is submitted or scheduled. If you created asingle activity plan, the upgrade is complete after the plan successfully completes.If you created individual plans, you need to run each one created in its originalorder manually using Activity Planner.

Note: If you did not select the copy all files check box, Activity Planner tries tolocate the required installation images from the original installation location(CD or mounted file system). If these images are not in this location, theinstallation will fail. If you created a local depot, Activity Planner can locatethese images and successfully complete the installation.

For details about using Activity Planner to create, modify, and schedule activityplans, see IBM Tivoli Configuration Manager User’s Guide for Deployment Services.


Tivoli Management Framework mechanisms for Tivolienvironment upgrade worksheet

The installation mechanisms provided by Tivoli Management Framework generallyuse the installation options provided in the index file for the component or service.These installation mechanisms are as follows:v Tivoli Software Installation Servicev Tivoli desktopv Tivoli Management Framework commands

Because of the packaging of the installation images, you might need to use acombination of index file-base images and software package block-based images.

Using Tivoli Software Installation Service to upgrade a TivoliregionYou can use Tivoli Software Installation Service to install and upgrade many of theIBM Tivoli Configuration Manager and Tivoli Management Frameworkcomponents and services in each Tivoli region. After determining whichcomponents and services need to be upgraded and which components needs to beinstalled, you can use Tivoli Software Installation Service to upgrade and installthese components and services.

For details about which images are installed using index files and SPBs, see“Components installed from index files” on page 30 and the appropriate section in“Components installed from software package blocks” on page 31.

For details about the installation options for each installation image, see theappropriate section in “Installation options” on page 35.

For high-level information about using Tivoli Software Installation Service, see“Installing components using Tivoli Software Installation Service” on page 57. Forcomplete details about using these commands, see Tivoli Enterprise InstallationGuide.

For high-level information about using SPBs as installation images, see “Installingcomponents using software package blocks” on page 59. For complete details, seeIBM Tivoli Configuration Manager User’s Guide for Software Distribution and IBMTivoli Configuration Manager Reference Manual for Software Distribution.

Using the Tivoli desktop to upgrade a Tivoli regionYou can use the Tivoli desktop to install and upgrade many of the IBM TivoliConfiguration Manager and Tivoli Management Framework components andservices in each Tivoli region. After determining which components and servicesneed to be upgraded and which components needs to be installed, you can use theTivoli desktop to upgrade and install these components and services.



For high-level information about using the Tivoli desktop, see “Installingcomponents using the Tivoli desktop” on page 58. For complete details about usingthese commands, see Tivoli Enterprise Installation Guide.



Using Tivoli Management Framework commands to upgrade aTivoli regionYou can use the Tivoli Management Framework winstall and wpatch commandsto install and upgrade many of the IBM Tivoli Configuration Manager and TivoliManagement Framework components and services in each Tivoli region. Afterdetermining which components and services need to be upgraded and whichcomponents needs to be installed, you can use these commands to upgrade andinstall these components and services.



For high-level information about using these commands, see “Installingcomponents using the command line” on page 58. For complete details about usingthese commands, see Tivoli Management Framework Reference Manual and TivoliEnterprise Installation Guide.



Appendix B. 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.

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.

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.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

TrademarksAIX, DB2, IBM, OS/2, OS/400, S/390, Tivoli, Tivoli Enterprise, TME, andWebSphere are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both.

Microsoft and Windows NT are registered trademarks of Microsoft Corporation inthe United States, other countries, or both.

ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of IntelCorporation in the United States, other countries, or both. For a complete list ofIntel trademarks, see http://www.intel.com/sites/corporate/tradmarx.htm..

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.


http://www.intel.com/sites/corporate/tradmarx.htm.

Other company, product, and service names may be trademarks or service marksof others.

Appendix B. Notices 127

Index

Special characters.dbf data files (Oracle) 70.IND files 31.LDF files 79.ldf log files (Microsoft SQL Server) 69.mdf database objects (Microsoft SQL Server) 69.ndf file group (Microsoft SQL Server) 69.profile file (UNIX) 18<component>_log.dat file 72<component>_ts.dat file 72

Aabbreviations

IBM Tivoli Configuration Manager components 67vendors 68

Access Managerconfiguration file 20integration 19keystore file 20

Activity Planneradmin scripts 67installation options 35managed node component 3managed resource state 54planner database 14prerequisites 35RIM object 15Tivoli server component 2uninstallation script 64

Activity Planner interfaceinternationalization support 34software package blocks 34

Add/Remove programuninstalling Desktop installation 63uninstalling Server installation 63

adduser command (Linux) 18admin scripts

ccm_<vendor>_admin.sql 67cm_<vendor>_admin.sql 67inv_<vendor>_admin.sql 67mdist_<vendor>_admin.sql 67plans_<vendor>_admin.sql 67requirements for Oracle 70running 67

adminclient command (WebSphere) 86administrative interfaces

Activity Planner 34Change Manager 34Distribution Status console 34installing 56internationalization support 34Inventory 34software package blocks 34software requirements 4SPB considerations 60

Adupd.ldf file 79alter tablespaces command (DB2) 87apm_uninst.sh script 64apm_upgr_uninst.sh script 64

architecture, Tivoli environment 1audience, for this publication vauthentication server (WebSEAL) 21authorization roles

APM_Admin 62CCM_Admin 62installation 27registering plug-ins 62

authorization server (Access Manager)ivacld process 20port 20

Bbackup operation, for Tivoli environment 13basic architecture, Tivoli environment 1basic authentication (WebSEAL) 21bold typeface, meaning of viiibooks

online access viiordering viiproviding feedback vii

Ccatalog command (DB2) 88ccm

database 14, 68repository 67RIM object 15

ccm_<vendor>_admin.sql 67, 68ccm_<vendor>_migr_42.sql scripts 62CCM_Admin authorization role 62ccm_ts tablespace 68ccm_uninst.sh script 64ccm_upgr_uninst.sh script 64Certificate Authorities (CA) 20Change Manager

admin scripts 67ccm database 14installation options 37managed node component 3prerequisites 37requirement of Lightweight Directory Access Protocol 2RIM object 15self-signed certificates 20SSL connections 20Tivoli server component 2uninstallation script 64

Change Manager interfaceinternationalization support 34software package blocks 34

cm repository 67cm_<vendor>_admin.sql 67, 68cm_db database 14, 68cm_ts 68collector hierarchy 5com.tivoli.mts.SvrSslCfg 19command line, installing from 58


commandsadduser (Linux) 18adminclient (WebSphere) 86alter tablespace (DB2) 87catalog (DB2) 88connect (DB2) 88CREATE DATABASE (Oracle) 70db2 (DB2) 88dbaccess (Informix) 89deviceclass 85exit (Microsoft SQL Server) 89exit (Sybase) 91isql (Microsoft SQL Server) 89isql (Sybase) 90mkuser (AIX) 18pdadmin (WebSEAL) 21, 22pdjrtecfg (Access Manager) 19quit (DB2) 89quit (Oracle) 90spool (Oracle) 90sqlplus (Oracle) 90used by DB2 88used by Informix 89used by Microsoft SQL Server 89used by Oracle 90used by Sybase 90useradd (Solaris) 18wcrtgate 52wcrtrim 14wdrmvsp 64wgateway 52wgetrim 15winstall 51, 58winvfilter 15winvpackage 15winvrmnode 15winvsig 15winvupdatesid 15wmcast 52wmdist 52wmvrim 14wpatch 51, 58wremovsp 64wresgw 24wresource 83wrpt 52wserver 51wsetrim 15wsetrimpw 15, 16wuninst 64wweb 7

componentsIBM Tivoli Configuration Manager 1, 4index file names 30installed on endpoints 4installed on managed nodes 3installed on Tivoli server 2Inventory 5, 23Inventory Gateway 23Resource Manager 6, 23Resource Manager Gateway 23Software Distribution 5, 23Software Distribution Gateway 23software package block names 31Web Gateway 24Web Interface 7

configurationDB2 client 87Java Runtime Environment 19RIM objects 15WebSEAL server 21

configuration filesAccess Manager 20using with SSL 19WebSEAL 21

configuration managementinstallation mechanisms 30maintenance and problem determination 81overview 1planning for 13resources 5storing and retrieving RDBMS server data 15using in connected Tivoli regions 25using RIM objects 15where to install components 23

configuration repository 67connect command (DB2) 88contents, of this publication vCREATE DATABASE command (Oracle) 70custom installation

Desktop 118server 101Web Gateway 115

Customer Support viii

Ddata handler, inventory 5data migration, within repositories 61database administrator (DBA) 67database objects, .mdf files (Microsoft SQL Server) 69databases

ccm 68cm_db 68inv_db 68mdist2 68planner 68

DB2alter tablespace command 87catalog command 88cataloging a remote database 88cataloging a server node 88configuring for Web Gateway 87connect command 88connecting to the server 88creating repositories 73creating tablespaces 68creating users for Web Gateway 18creating users on UNIX operating systems 18creating users on Windows operating systems 18db2 command 88DB2DIR variable 36ending interactive session 89general commands 88log file considerations 68quit command 89running scripts 88scripts for testing 82starting interactive session 88

DB2 client configuration for Web Gateway 87db2 command (DB2) 88DB2DIR variable (DB2) 36db2profile file (UNIX) 18


dbaccess command (Informix) 89default enrollment URL 85default passwords, RIM objects 15deployment plan, creating 13Desktop installation program

custom installation details 57general 56locating 50overview 49typical installation details 57

Desktop installation worksheetcustom path 118general 117typical path 118

device agents, installing 56deviceclass command 85devices (Sybase) 72devices, managing 26Distribution Status console

admin scripts 67internationalization support 34mdist2 database 14software package blocks 32, 34

dmsadmin user 18, 45dmsuser user 18, 45docroot variable (WebSEAL) 22DOCROOTDIR variable (WebSEAL) 22DSQUERY variable (Sybase) 36

Ee-mail contact viiendpoints

components installed on 4installed in a Tivoli environment 1installing the Web Gateway component 24resource 1services installed on 4

enrollment URL 85Enterprise Directory Query Facility

installation options 39installation sequence 83prerequisites 39registering resources 83scripts 79Tivoli server component 2

exit command (Microsoft SQL Server) 89exit command (Sybase) 91

Ffeedback about publications viifile groups, .ndf files (Microsoft SQL Server) 69files

.LDF (LDAP) 79

.profile 18Adupd.ldf 79db2profile 18deviceclass.bat (Windows) 86deviceclass.sh (UNIX) 85httpd.conf 20, 86IMBupd.ldf 79interfaces (Sybase) 36key.kdb 20LDIF 79NDSupd.ldf 79

files (continued)PdPerm.ks (Access Manager) 20PdPerm.properties (Access Manager) 20query_contents.cfg 22query_contents.sh 22resinit 65resinit.exe 65setup.exe file 51SWDISGW_LCFNEW 65tnsnames.ora (Oracle) 36twg.cfg 86twg.properties 86wdbldspb 65wdusrprf.exe 65web.xml 86, 87webseald.conf (WebSEAL) 21

forms authentication (WebSEAL) 21

Ggateways

installed in a Tivoli environment 1managed node configuration 1resource 1software programs 3

graphical user interfaces 34guides


Hh_inv_<vendor>_upgrade_42.sql 61h_inventory_query_upgrade_42.sh script 62h_pervasive_query.sh script 62h_subscriber_query.sh script 62httpd.conf file 20, 86

IIBM SecureWay LDIF file 79IBM Tivoli Configuration Manager

cm_db database 14component abbreviations 67installation 49prerequisites 13

IBM Tivoli Enterprise Consoleintegration 2updating rule base 61

IBMupd.ldf file 79iKeyman utility 20index files, components installed from 30Informix

creating repositories 74dbaccess command 89general commands 89INFORMIXDIR variable 36onconfig file 74running scripts 89scripts for testing 82

INFORMIXDIR variable (Informix) 36installation

authorization roles 27device agent programs 56Inventory components 23

Index 131

installation (continued)Inventory Gateway component 23overview 49Resource Manager components 23Resource Manager Gateway component 23Software Distribution components 23Software Distribution Gateway component 23using command line 58using installation program 49using software package blocks 59using Tivoli desktop 58using Tivoli Software Installation Service 57Web Gateway components 24

installation optionsActivity Planner 35Change Manager 37Enterprise Directory Query Facility 39Inventory 40Inventory Gateway 42Resource Manager 42, 43Scalable Collection Service 43Software Distribution 44Software Distribution Gateway 44Software Package Editor 44Web Gateway 44

installation programsDesktop 49, 56locating 50required RIM passwords 68Server 49, 51starting 51Upgrade Plan Generator 49, 53Web Gateway 49, 56

installation sequenceof components 27using IBM Tivoli Configuration Manager mechanisms 27using Tivoli Management Framework mechanisms 28

installation worksheetsSee worksheets

internationalizationActivity Planner interface 34Change Manager interface 34Distribution Status console 34Inventory interface 34Inventory plug-in 33Software Distribution plug-in 33Web Gateway 32Web Infrastructure 33

inv_<vendor>_admin.sql 67inv_<vendor>_schema.sql 78inv_<vendor>_upgrade_42.sql 61inv_db database 14, 68inv_query, RIM object 15inv_ts tablespace 68invdh_1, RIM object 15Inventory

admin scripts 67choosing where to install 23components of 5installation options 40installing software signatures 83, 85inv_db database 14managed node component 3requirement for RIM object 2RIM objects 15Tivoli server component 2uninstallation scripts 64

inventory data handler 5Inventory Gateway

choosing where to install 23installation options 42managed node component 3

Inventory interfaceinternationalization support 34software package blocks 34

Inventory plug-ininternationalization support 33software package blocks 33

inventory scans, running 25inventory_query_upgrade_42.sh script 62inventory_query.sh script 62ISPB_DATA tablespace 87ISPB_INDEX tablespace 87isql command (Informix) 89isql command (Sybase) 90isql interactive session, starting 89italic typeface, meaning of viiiivacld process (Access Manager) 20ivmgrd process (Access Manager) 20

JJava components 32Java Runtime Environment, configuring for Access

Manager 19junctions (WebSEAL)

creating 22testing 22

Kkey.kdb file 20keystore files

for Access Manager 20using with SSL 19

keytool utility 21

LLDAP

See Lightweight Directory Access ProtocolLDAP Data Interchange Format files

See LDIF filesLDIF files

for IBM SecureWay 79for Microsoft Active Directory 79for Novell Directory Server 79

legal notices 125Lightweight Directory Access Protocol

for user management 2scripts 79with Enterprise Directory Query Facility 39

locks, with Informix 74log files

.ldf files (Microsoft SQL Server) 69from admin script 68

Mmaintenance 81managed nodes

components installed on 3


managed nodes (continued)installing the Inventory components 23installing the Resource Manager components 23installing the Software Distribution components 23resource 1selecting as RDBMS host 15selecting as RIM host 14services installed on 3

management by subscription 5manuals


MCOLLECTSee Scalable Collection Service

MDist 2 repeater 26mdist_<vendor>_admin.sql 67mdist2 database 14, 68mdist2_ts tablespace 68mdstatus repository 67Microsoft Active Directory LDIF file 79Microsoft SQL Server

.ldf log files 69

.mdf database objects 69

.ndf file groups 69creating repositories 74ending interactive session 89exit command 89general commands 89isql command 89running scripts 89scripts for testing 82starting interactive session 89tablespace creation 69

migration of repository data 61migration scripts

h_inv_<vendor>_upgrade_42.sql 61inv_<vendor>_upgrade_42.sql 61swdis_<vendor>_migr_42.sql 61swdis_<vendor>_view_42.sql 61swdistecsrvr_inst.sh 61

mkuser command (AIX) 18monospace font, meaning of viii

Nname

DB2 82Informix 82Sybase 82

NDSupd.ldf file 79NetWare Gateway, uninstalling components 65notices 125Novell Directory Server LDIF file 79

Oobject_name (Oracle) 82object_type (Oracle) 82onconfig file (Informix) 74online publications viiOracle

.dbf data files 70admin script requirements 70CREATE DATABASE command 70creating repositories 75

Oracle (continued)ending interactive session 90general commands 90ORACLE_HOME variable 36ORACLE_SID variable 36quit command 90scripts for testing 82specifying log file 90spool command 90sqlplus command 90starting interactive session 90sys user 70sysdba user 70tablespace creation 70tnsnames.ora file 36TWO_TASK variable 36

ORACLE_HOME variable (Oracle) 36ORACLE_SID variables (Oracle) 36overview

configuration management 1installation 49RDBMS 14repositories 67RIM 14

Ppasswords

for RDBMS 16for RIM objects 15, 16required by installation programs 68

pdadmin command (WebSEAL) 21, 22pdjrtecfg command (Access Manager) 19PDPerm.ks file (Access Manager) 20PdPerm.properties file (Access Manager) 20pervasive_query.sh script 62plan for deployment 13planner

database 14, 68repository 67RIM object 15tablespace 68

planner_ts tablespace 68plans_<vendor>_admin.sql 67plans_<vendor>_migr_42.sql script 61plug-in software for Web Infrastructure 4plug-in, registering 62policy server

ivmgrd process (Access Manager) 20policy server (Access Manager)

port 20ports

Access Manager authorization server 20Access Manager policy server 20

prerequisite publications viprerequisites

Activity Planner 35Change Manager 37distributing software in connected Tivoli regions 26Enterprise Directory Query Facility 39IBM Tivoli Configuration Manager 13inventory scans in connected Tivoli regions 25managed node as a source host 23managing devices in connected Tivoli regions 26RDBMS server 15resource management 17RIM host 14

Index 133

prerequisites (continued)Scalable Collection Service 43Software Distribution 44Software Distribution Gateway 44Software Package Editor 44Tivoli Management Framework 13Web access 17Web Gateway 17, 44Web Gateway database 45Web Gateway server 45Web Infrastructure 48

Pristine Toolinternationalization support 34software package blocks 34

problem determination 81processes

ivacld (Access Manager) 20ivmgrd (Access Manager) 20

publicationsaudience vcontents of vonline access viiordering viiprerequisite viproviding feedback viirelated vi

Qquery libraries, installing and upgrading 62query library scripts

h_pervasive_query.sh 62h_subscribter_query.sh 62inventory_query.sh 62pervasive_query.sh 62subscriber_query.sh 62

query_contents.cfg file 22query_contents.sh file 22quit command (DB2) 89quit command (Oracle) 90

RRDBMS

abbreviations for vendors 68DB2 general commands 88general commands 88IBM Tivoli Configuration Manager component 67Informix general commands 89Microsoft SQL Server general commands 89Oracle general commands 90overview 14passwords 16requirements for selecting 15selecting host 15Sybase general commands 90

RDBMS Interface Module (RIM) 2reg_inv_plugin.sh script 62reg_swd_plugin.sh script 62registered product tag 30RegisterPervasive.sh script 83RegisterUser.sh script 83related publications viRelational Database Management System (RDBMS) 2repeater hierarchy 5

repeatersmanaged node configuration 1resource 1used within a Tivoli environment 5

repositoriesccm for Change Manager 67cm for IBM Tivoli Configuration Manager 67configuration for Inventory and Resource Manager 67creating 67creating for DB2 73creating for Informix 74creating for Microsoft SQL Server 74creating for Oracle 75creating for Sybase 78for Activity Planner (planner) 14for Change Manager (ccm) 14for Distribution Status console (mdist2) 14for IBM Tivoli Configuration Manager (cm_db) 14for Inventory (inv_db) 14for Resource Manager (inv_db) 14for Resource Manager (trm) 14for Software Distribution (inv_db) 14mdstatus for Distribution Status 67migrating data 61overview 67planner for Activity Planner 67

requirementsSee prerequisites

resinit file 65resinit.exe file 65resource gateways 23resource management authentication 21Resource Manager

choosing where to install 23components of 6installation options 42installation sequence 83inv 67inv_db database 14registering resource types 83RegisterPervasive.sh script 83RegisterUser.sh script 83requirement for RIM object 2RIM object 15Tivoli server component 2trm database 14

Resource Manager Gatewaychoosing where to install 23installation options 43managed node component 3

resourcesconfiguration management environment 5endpoint 1gateway 1managed node 1repeater 1Tivoli region 1

return values, Web Gateway installation 83RIM hosts

See also RIM objectsrequirements 14selecting 14

RIM objectsccm 15configuring 15for Activity Planner 15for Change Manager 15


RIM objects (continued)for Inventory 15for Resource Manager 15inv_query 15invdh_1 15overview 14passwords 16planner 15required passwords 68trm 15

rule base, upgrading 61

SScalable Collection Service

choosing where to install 23in connected Tivoli regions 25in repeater hierarchy 5installation options 43manage node component 3prerequisites 43Tivoli server component 2

scans, running 25schema scripts

location of 73running for DB2 73running for Informix 74running for Microsoft SQL Server 70running for Sybase 73

schemasinstalling for DB2 73installing for Informix 74installing for Microsoft SQL Server 74installing for Oracle 75installing for Sybase 78testing 81

scriptsadmin, running 67apm_uninst.sh 64apm_upgr_uninst.sh 64ccm_<vendor>_admin.sql 67ccm_<vendor>_migr_42.sql 62ccm_uninst.sh 64ccm_upgr_uninst.sh 64cm_<vendor>_admin.sql 67for Enterprise Directory Query Facility 79for Lightweight Directory Access Protocol 79h_inv_<vendor>_upgrade_42.sql 61h_inventory_query_upgrade_42.sh 62h_pervasive_query.sh 62h_subscriber_query.sh 62inv_<vendor>_admin.sql 67inv_<vendor>_upgrade_42.sql 61inventory_query_upgrade_42.sh 62inventory_query.sh 62mdist_<vendor>_admin.sql 67pervasive_query.sh 62plans_<vendor>_admin.sql 67plans_<vendor>_migr_42.sql 61reg_invscan_plugin.sh 62reg_swd_plugin.sh 62RegisterPervasive.sh 83RegisterUser.sh 83subscriber_query.sh 62subscription_query_upgrade_42.sh 62swdis_<vendor>_migr_42.sql 61swdis_<vendor>_view_42.sql 61

scripts (continued)swdisNW_uninst.sh 65swdistecsrvr_inst.sh 61testing for DB2 82testing for Informix 82testing for Microsoft SQL Server 82testing for Oracle 82testing for Sybase 82upgr_plugins.sh 61using to uninstall components 64

self-signed certificatesextracting 20importing 21

sequence of component installation 27Server installation program

custom installation details 53general 51locating 50overview 49required system users 68typical and custom details 52typical installation details 52

Server installation worksheetcustom path 101general 97typical path 99using Tivoli Management Framework mechanisms 106

servicesinstalled on endpoints 4installed on managed nodes 3installed on Tivoli server 2

setup.exe file 51shell scripts

See see scriptssignatures, software 85Software Distribution

choosing where to install 23components of 5historical database 2installation options 44integration with IBM Tivoli Enterprise Console 2inv_db database 14managed node component 3Tivoli server component 2uninstallation scripts 64

Software Distribution Gatewaychoosing where to install 23installation options 44managed node component 3

Software Distribution plug-ininternationalization support 33software package blocks 33

Software Distribution Pristine Toolendpoint component 4supported platforms 4

software package blocksadministrative interfaces 34components installed from 31consideration for Web Gateway 60considerations for administrative interfaces 60considerations for Software Package Editor 60considerations for Web Interfaces 60endpoint 33installing from 59Inventory plug-in 33Java components 32Pristine Tool 34

Index 135

software package blocks (continued)Software Distribution plug-in 33Software Package Editor 33using commands 64Web Gateway 32Web Infrastructure 33

Software Package Editorendpoint component 4installation options 44internationalization support 33managed node component 4software package blocks 33SPB considerations 60supported platforms 4

software signatures 85software, distributing 26SPB

See software package blocksspool command (Oracle) 90SQL scripts

See scriptsSQL*Plus session 71sqlplus command (Oracle) 90SSL

Certificate Authorities (CA) 20certificate repository, WebSphere 20configuration files 19extracting self-signed certificates 20importing self-signed certificates 21keystore files 19self-signed certificates 20

subscriber_query.sh script 62subscribers 5subscription_query_upgrade_42.sh script 62support, contacting viiisupported platforms

Software Distribution Pristine Tool 4Software Package Editor 4

SvrSslCfg 19swdis_<vendor>_migr_42.sql 61swdis_<vendor>_view_42.sql 61SWDISGW_LCFNEW file 65swdisNW_uninst.sh script 65swdistecsrvr_inst.sh script 61Sybase

allocating devices 72creating repositories 78DSQUERY variable 36ending interactive session 91exit command 91general commands 90interfaces file 36isql command 90requirements for admin scripts 72running scripts 90scripts for testing 82starting interactive session 90SYBASE variable 36tablespace creation 72

SYBASE variable (Sybase) 36sys user (Oracle) 70sys.user_objects (Oracle) 82sysdba user (Oracle) 70sysibm.systables (DB2) 82sysibm.systriggers (DB2) 82sysobjects (Informix) 82sysobjects (Sybase) 82

systables (Informix) 82systriggers (Informix) 82

Ttablespaces

ccm_ts 68cm_ts 68creating for DB2 68creating for Microsoft SQL Server 69creating for Oracle 70creating for Sybase 72in Web Gateway database 87inv_ts 68mdist2_ts 68planner_ts 68

tabname (Informix) 82tabtype (Informix) 82targets 5Tivoli Customer Support viiiTivoli desktop

installing endpoint components and services 4installing from 58

Tivoli environmentarchitecture 1backing up 13planning 13

Tivoli environment upgrade worksheetsgeneral 119using installation program 120using Tivoli desktop 122using Tivoli Management Framework commands 123using Tivoli Management Framework mechanisms 122using Tivoli Software Installation Service 122

Tivoli Management Frameworkhardware requirements 13installation commands 58software requirements 13

Tivoli regionsbasic resources 1connecting 25creating 27distributing software 26managing devices 26running inventory scans 25using multiples 15

Tivoli servercomponents installed on 2resource 1selecting as RDBMS host 15selecting as RIM host 14services installed on 2

Tivoli Software Installation Service, installing from 57tnsnames.ora file (Oracle) 36trigname (Informix) 82trm

database 14RIM object 15

twg.cfg file 86twg.properties file 86TWO_TASK variable (Oracle) 36type

DB2 82Informix 82Sybase 82

typeface conventions viii


typical installationDesktop 118server 99Web Gateway 113

Uuninstallation

overview 63Software Distribution from NetWare gateways 65software package blocks 64using Add/Remove programs 63using script files 64using wuninst command 64

upgr_plugins.sh script 61upgrade operation, for Tivoli environment 13Upgrade Plan Generator installation program

general 53locating 50overview 49

upgrade scriptsh_inventory_query_upgrade_42.sh 62inventory_query_upgrade_42.sh 62subscription_query_upgrade_42.sh 62

user creation, DB2for Web Gateway 18on UNIX operating systems 18on Windows operating systems 18

User Rights, Windows operating systems 18useradd command (Solaris) 18

Vvariables

DB2DIR (DB2) 36docroot (WebSEAL) 22DOCROOTDIR (WebSEAL) 22DSQUERY (Sybase) 36INFORMIXDIR (Informix) 36notation for viiiORACLE_HOME (Oracle) 36ORACLE_SID (Oracle) 36SYBASE variable (Sybase) 36TWO_TASK (Oracle) 36

vendor abbreviations 68

Wwcrtgate command 52wcrtrim command 14wdbldspb file 65wdrmvsp command 64wdusrprf.exe file 65Web access authentication 21Web Gateway

choosing where to install 24cluster configuration 24components of 6configuring DB2 client 87DB2 user accounts created 45device enrollment 85endpoint component 4enrolling using IP addresses 86increasing tablespace 87independent configuration 24installation options 44

Web Gateway (continued)installation program

custom installation details 56general 56locating 50overview 49typical installation details 56

installation worksheetcustom path 115general 111typical path 113

integration with Access Manager 19internationalization support 32ISPB_DATA tablespace 87ISPB_INDEX tablespace 87maintenance tasks 85planning for 17return values for SPB installation 83server

configuring the Java Runtime Environment 19configuring WebSEAL 22SSL configuration 19SSL keystores 19

software package blocks 32software prerequisites 17SPB considerations 60using non-standard HTTP ports 86using WebSEAL junctions 87

Web InfrastructureSee also Web Interfacesinternationalization support 33prerequisites 48software package blocks 33Tivoli server component 2

Web InterfacesSee also Web Infrastructurecomponents of 7endpoint components and plug-ins 4software requirements 7SPB consideration 60

web.xml file 86, 87WebSEAL server

authentication 21basic authentication 21configuring 21creating junctions 22defining SSL characteristics 19forms authentication 21integration 19testing configuration 22

webseald.conf file 21wgateway command 52wgetrim command 15winstall command 51, 58winvfilter command 15winvpackage command 15winvrmnode command 15winvsig command 15winvupdatesid command 15wmcast command 52wmdist command 52wmvrim command 14worksheets

Desktop installation 117planning 95Server installation 97Tivoli environment upgrade 119

Index 137

worksheets (continued)Web Gateway installation 111

wpatch command 51, 58wremovsp command 64wresgw command 24wresource command 83wrpt command 52wserver command 51wsetrim command 15wsetrimpw command 15, 16wuninst command 64wweb command 7

Xxtype (Informix) 82


��

Part Number: CT1CXIE

Printed in U.S.A.

GC23-4702-00

(1P)

P/N:

CT1CXIE

ibm tivoli configuration manager: planning and...

Documents