Deploying rational applications with ibm tivoli configuration manager redp4171

Front cover

Deploying Rational
Applications with IBM Tivoli
Configuration Manager

Learn how to use Tivoli Configuration
Manager to deploy Rational products

Follow step-by-step examples

Simplify management of
Rational environments

Pascal Chauffour
Corey Jenks
Petra Unglaub-Lloyd
Bart Jacob

ibm.com/redbooks Redpaper

International Technical Support Organization

Deploying Rational Applications with IBM Tivoli
Configuration Manager

July 2006

Note: Before using this information and the product it supports, read the information in
“Notices” on page v.

First Edition (July 2006)

This edition applies to Version 4, Release 2 of IBM Tivoli Configuration Manager and Version 7 of
IBM Rational Products.

© Copyright International Business Machines Corporation 2006. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
The team that wrote this Redpaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Rational applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 IBM Tivoli Configuration Manager components and services . . . . . . . . . . . 4
1.2.1 Software Distribution component . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2.2 Inventory component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2.3 Other features and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Target Tivoli Configuration Manager environment . . . . . . . . . . . . . . . . . . . 8
1.3.1 Installation of Tivoli Configuration Manager . . . . . . . . . . . . . . . . . . . . 8
1.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Preparing Rational products for IBM Tivoli Configuration
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.1 Rational product release area creation . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.1.1 Method for creating a Rational product release area . . . . . . . . . . . . 12
2.1.2 ClearQuest example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2 Product release area modification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2.1 Modifying an existing configuration file . . . . . . . . . . . . . . . . . . . . . . . 25
2.3 Creating another configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3.1 Create a new configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3.2 Duplicate an existing configuration file . . . . . . . . . . . . . . . . . . . . . . . 31
2.3.3 Clone an existing configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4 Installing from a Rational product release area. . . . . . . . . . . . . . . . . . . . . 32

Chapter 3. Creation of packages to install Rational products . . . . . . . . . 33
3.1 Software package formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.1.1 Choosing a software package format . . . . . . . . . . . . . . . . . . . . . . . . 34
3.2 Creating the Rational PurifyPlus software package . . . . . . . . . . . . . . . . . 39
3.3 Editing the software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.4 Creating a .spb package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.4.1 Adding an Inventory signature to a native software package . . . . . . 48
3.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

© Copyright IBM Corp. 2006. All rights reserved. iii

Chapter 4. Deployment of Rational packages . . . . . . . . . . . . . . . . . . . . . . 51
4.1 Creating a Software Distribution profile. . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.1.1 Setting the profile subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.1.2 Importing a software package into the Tivoli environment . . . . . . . . 59
4.1.3 Using software signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.1.4 Installing a software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.1.5 Checking the outcome of a distribution . . . . . . . . . . . . . . . . . . . . . . . 65
4.2 Installing product upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Appendix A. Tivoli Configuration Manager environment installation . . . 71
General components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installing DB2 UDB Enterprise Server Edition . . . . . . . . . . . . . . . . . . . . . . 73
Installing Fixpack 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Creating the Configuration Manager database . . . . . . . . . . . . . . . . . . . . . . 85
Create a RIM user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Installing IBM Tivoli Configuration Manager 4.2.3. . . . . . . . . . . . . . . . . . . . 91
General procedure for dealing with installation failures . . . . . . . . . . . . . . . 97
Creating a Tivoli command prompt window shortcut . . . . . . . . . . . . . . . . . 99
Installing the Tivoli Endpoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Installing the CM 4.2.3 Windows Desktop. . . . . . . . . . . . . . . . . . . . . . . . . 106

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

iv Deploying Rational Applications with IBM Tivoli Configuration Manager

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 in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product 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 it believes appropriate without
incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

© Copyright IBM Corp. 2006. All rights reserved. v

Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:

ClearCase® Purify® RequisitePro®
ClearQuest® PurifyPlus™ SoDA®
DB2® Rational® Tivoli®
DB2 Universal Database™ Rational Rose® Tivoli Enterprise™
IBM® Redbooks™ WebSphere®
ProjectConsole™ Redbooks (logo) ™

The following terms are trademarks of other companies:

Java, JavaHelp, J2EE, J2SE, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in
the United States, other countries, or both.

ActiveX, Microsoft, Visual Basic, Visual C++, Visual Studio, Windows Server, Windows, and the Windows
logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

vi Deploying Rational Applications with IBM Tivoli Configuration Manager

Preface

The IBM® Redpaper provides an overview of the Rational® product installation
process, describes how to create IBM Tivoli® Configuration Manager software
packages for the Rational products, and demonstrates how these packages can
be used to distribute Rational products to a large number of systems. The paper
can be used as a reference document to enable clients to perform unattended
installations of Rational products.

The installation process applies to a Microsoft® Windows®-based target
environment.

Although some information about IBM Tivoli Configuration Manager is provided,
this paper assumes that readers are already familiar with the product.

The team that wrote this Redpaper
This Redpaper was produced by a team of specialists from around the world
working at the International Technical Support Organization, Austin Center.

Bart Jacob is a Senior Consulting IT Specialist at IBM in the International
Technical Support Organization, Austin Center. He has more than 25 years of
experience providing technical support across a variety of IBM products and
technologies, including communications, object-oriented software development,
and systems management. He has more than 14 years of experience at the
ITSO, where he has been writing IBM Redbooks™ and creating and teaching
workshops around the world on a variety of topics. He holds a Masters degree in
Numerical Analysis from Syracuse University.

Pascal Chauffour is a Test Manager in La Gaude, France. He has worked at
IBM for 22 years in different areas, including 15 years on Telecommunication
Hardware Development and the last seven years shared on testing and
deploying IT solutions (Universal Server Farm, Software Distribution). He has
published 11 patents. He has a Telecommunication Engineer degree from
ENSTBr (Brest, France).

Corey Jenks is a Software Engineer in Austin, Texas. He has five years of
experience in the software verification and test field. He holds a degree in
Management Information Systems from the University of Notre Dame. His areas
of expertise include software testing and information development.

© Copyright IBM Corp. 2006. All rights reserved. vii

Petra Unglaub-Lloyd is a Level 2 Software Engineer in Austin, Texas. She has
10 years of experience in the Tivoli Support field. She holds a degree from
Hardin-Simmons University and the University of Bayreuth, Germany. Her areas
of expertise include Level 2 defect support for IBM Tivoli Framework and IBM
Tivoli Configuration Manager.

Thanks to the following people for their contributions to this project:

Bruce Katz
IBM Rational, Lexington

Kent Seith

David Zygadlo

Become a published author
Join us for a two- to six-week residency program! Help write an IBM Redbook
dealing with specific products or solutions, while getting hands-on experience
with leading-edge technologies. You'll team with IBM technical professionals,
Business Partners, and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. As
a bonus, you'll develop a network of contacts in IBM development labs, and
increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and
apply online at:
ibm.com/redbooks/residencies.html

Comments welcome
Your comments are important to us!

We want our papers to be as helpful as possible. Send us your comments about
this Redpaper or other Redbooks in one of the following ways:
Use the online Contact us review redbook form found at:
ibm.com/redbooks

viii Deploying Rational Applications with IBM Tivoli Configuration Manager

Send your comments in an e-mail to:
redbook@us.ibm.com
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400

Preface ix

x Deploying Rational Applications with IBM Tivoli Configuration Manager

1

Chapter 1. Introduction
Rational solutions help organizations achieve their business goals. Rational
software enables organizations to automate and integrate the core business
process of software development. Rational products, services, and best practices
power the IBM Software Development Platform, the premier platform for teams
who discover, develop, and deploy software assets in business applications,
embedded systems, and software products. This modular and complete solution
enables teams to adopt a business-driven development approach based on open
standards, including the Eclipse open source framework.

IBM Tivoli Configuration Manager controls software distribution and asset
management inventory in a multi-platform environment. It is designed for
configuration, distribution, change, version, and asset management in a
distributed computing environment. Working on top of IBM Tivoli Management
Framework, Tivoli Configuration Manager provides an integrated solution for
managing complex, distributed enterprise environments.

© Copyright IBM Corp. 2006. All rights reserved. 1

1.1 Rational applications
Table 1-1 lists the various Rational applications that have been installed using the
techniques and processes described in this Redpaper.

Table 1-1 IBM Rational products
Rational product Feature description

IBM Rational Complete software configuration management system for
ClearCase® LT project workgroups. IBM Rational ClearCase LT server should
be installed on a single, dedicated server machine that is
accessible by all ClearCase LT clients.

IBM Rational Comprehensive software configuration management that helps
ClearCase teams control everything that evolves in the development
process. Features Snapshot and Dynamic Views, advanced
build management, and Unified Change Management.

IBM Rational A flexible defect and change tracking system that captures and
ClearQuest® tracks all types of change for any type of project.

IBM Rational A Web-based artifact and measurement reporting tool.
ProjectConsole™

IBM Rational Test An optional add-on to IBM Rational TestManager that installs
Agent Windows Playback Agents on Windows computers in order to
enable execution of Virtual Testers. IBM Rational Windows
Playback Agents are freely distributable, although Virtual
Testers must be licensed.

IBM Rational Purify® Advanced runtime and memory management error detection.
for Windows Does not require access to source code and can thus be used
with third-party libraries in addition to home-grown code.
For software developers working with Java™, Visual C++®,
and all VS.NET managed languages (including C# and
VB.NET).

IBM Rational Complete set of automated runtime analysis tools for improving
PurifyPlus™ for Windows-based application reliability and performance.
Windows Designed for Java, Visual C/C++, C#, VB.NET, and Visual
Basic® applications.

IBM Rational An easy-to-use requirements management tool that lets you
RequisitePro® maintain the way you document requirements, using Microsoft
Word, while leveraging analytical capabilities such as
requirements analysis, coverage, and change impact.

2 Deploying Rational Applications with IBM Tivoli Configuration Manager


IBM Rational Robot A functional and performance test tool for software quality
teams that want to automate performance, regression, and
smoke testing of Java, .NET, Web, VB, ERP, and client/server
applications in a mixture of Windows and UNIX®
environments.

IBM Rational Rose® A UML-based, model-driven development tool for Ada83 and
Professional Ada Ada95 developers and teams. Features complete visual
Edition modeling and round-trip engineering support, plus seamless
integration with Rational Apex.

IBM Rational Rose A UML-based, model-driven development tool for C++
Professional C++ developers and teams. It features visual modeling, round-trip
Edition engineering, and seamless integration with Microsoft Visual
C++ 6.0.

IBM Rational Rose A UML-based, model-driven development tool for developers,
Enterprise Edition architects, and analysts. Rational Rose Enterprise provides
visual and data modeling, round-trip engineering, and
component testing across a broad set of supported platforms.

IBM Rational Rose A UML-based, model-driven development tool for Java
Professional J developers and teams. It provides visual modeling and
Edition round-trip engineering on Java, J2SE™, and J2EE™ platforms.

IBM Rational Rose A UML-based, model-driven development tool for developers,
Professional architects, and analysts. It provides visual modeling support
Modeler Edition across a broad range of platforms.

IBM Rational Rose A UML-based, model-driven development tool for data
Professional Data modelers, analysts, and developers, provides visual modeling,
Modeler Edition data modeling, and round-trip engineering support across a
broad set of supported platforms.

IBM Rational Rose A complete model-driven development environment built for
RealTime embedded systems; enables architects, developers, and
testers to use a common high-level notation to capture,
generate, communicate, and test the design of event-driven
and real-time applications.

IBM Rational Rose A UML-based, model-driven development tool for Microsoft
Visual Basic Edition Visual Basic developers and teams. It features visual modeling,
round-trip engineering, and seamless integration with Microsoft
VB IDEs.

IBM Rational SoDA® SoDA for Word enables documentors and project managers to
for Word automate the creation of project documents from multiple
sources.

Chapter 1. Introduction 3


IBM Rational Test A freely distributable add-on to IBM Rational Robot that installs
Enablers the components you need to enable ObjectTesting on a
developer or tester system. It enables testing of ActiveX®,
Java, and Visual Basic 4 without installing the full IBM Rational
Robot product.

IBM Rational Test A test management and control tool for the entire team. This
Manager open and extensible tool enables teams to plan, execute, and
assess all testing activities, and manage both IBM Rational and
third-party test assets.

1.2 IBM Tivoli Configuration Manager components and
services
IBM Tivoli Configuration Manager is an integrated software distribution and asset
management suite that consists of two main components, Software Distribution
and Inventory. In addition there are various services and features. Not all of the
features described here are required for the installation of Rational products as
described in this paper.

1.2.1 Software Distribution component
Using the Software Distribution component, you can install, configure, and
update software remotely within your network, eliminating the need to update
software manually on numerous systems. You can:
Distribute client/server applications and applications for desktops, laptops,
and pervasive devices across multi-platform networks.
Update existing software with later versions.
Synchronize software on distributed systems.

Multicast distribution
Multicast is a feature of Tivoli Management Framework 4.1. Traditionally, the data
distribution component of the Tivoli Framework (known as MDist2) has a
one-to-one TCP connection with each target. Therefore, if there are 50 targets,
MDist2 would send the distribution data 50 times.

However, using multicast, the distribution data is sent only once, regardless of
the amount of receivers. This is due to the fact that multicast uses UDP
broadcast packets. All of the targets read from the same data stream.


The benefit to using multicast is the decrease in the distribution time and network
traffic. This is very useful when sending data to multiple targets over satellite or
slow network links.

Figure 1-1 Multicast

For large software packages such as those required when installing software
suites such as Rational, multicast can significantly improve performance and
reduce network overhead.

1.2.2 Inventory component
Using the Inventory component of IBM Tivoli Configuration Manager, you can
gather and maintain up-to-date inventory information in a distributed environment
quickly, accurately, and easily. This helps system administrators and accounting
personnel manage complex, distributed enterprises.

Administrators and accounting personnel can perform the following tasks:
Manage all enterprise systems centrally.
Determine the installed software base.
Confirm a software distribution.
Supplement and replace physical inventory function.
Assist in procurement planning.
Check software requirements.
Control assets.

For example, you can combine inventory and software distribution operations to
determine whether any critical files are missing, then re-establish the proper
configuration. After creating and deploying management-ready applications, you
can continually maintain the desired state of your systems by synchronizing
applications and system configurations on an enterprise scale.


1.2.3 Other features and services
This section describes other features and services of IBM Tivoli Configuration
Manager.

Activity Planner
Activity Planner is a deployment service that enables you to:
Define a group of activities to be submitted as an activity plan.
Submit or schedule the plan for running.
Monitor the plan while it runs.

Activities are tasks that can be scheduled to be performed on a set of targets at
specified times. Operations can include software distribution, inventory
operations, and other Tivoli tasks.

Activities contained in a plan can have dependencies associated with them that
define circumstances under which the activity should be run. The running of the
operation defined in the activity is performed by the application to which the
operation belongs. The group of activities forms the activity plan.

Activity Planner is made up of two components, the Activity Plan Editor and the
Activity Plan Monitor.

Activity Plan Editor
You can use the Activity Plan Editor to:
Manage a group of activities originating from different applications as a single
activity from a single machine in the network.
Schedule the activity plan to run on a specific day and time, to repeat at
specific time intervals, or repeat indefinitely.
Schedule activities to run at specific time intervals during the week.
Set conditions on activities so that the execution of one activity is dependent
on the completion result of other activities.
Save activity plans in a database to resubmit them at any future time.

Activity Plan Monitor
You can use the Activity Plan Monitor to:
Submit activity plans to be run.
View all submitted activity plans along with their status, start time, and
completion time.
View the list of activities contained in the plan.


View a graphical representation of the plan in the Activity Plan Editor window.
For each activity, view the targets (gateways, depots) assigned to it.
Perform operations such as pause, cancel, and resume.
Restart an activity on an endpoint where the operation was unsuccessful.
Delete the status information of a plan from the activity plan database.
Launch the Distribution Status console to monitor and control software
distributions submitted using the Activity Planner.

Change Manager
Change Manager (previously called Change Configuration Manager) is a
deployment service that, together with Activity Planner, supports software
distribution, inventory, and change management in a large network.

Activity Planner is a prerequisite of Change Manager. Change Manager works
with the Activity Plan Monitor to manage specified groups of users, workstations,
or devices as single subscribers. Subscribers can be users, groups of users,
endpoints, a profile manager, the results of a query, or pervasive devices.

Change Manager uses reference models, which contain an association of
configuration elements and subscribers, to simplify the management of your
network environment.

Resource Manager
A Tivoli management region is a three-tier architecture, including servers,
gateways, and endpoints, that is created using Tivoli Management Framework.
By using the Resource Manager deployment service, you can extend the Tivoli
region to a fourth tier: pervasive devices such as PDAs.

Web Interface
The Web Interface (Web UI) enables software distribution and inventory to be
initiated by users. By using the Web Interface, users can access a Web site and
install software on their own machine, or generate an inventory scan by
themselves.

Web Gateway component
The Web Gateway component supports the Resource Manager deployment
service and the Web Interface (Web UI) deployment service.

The Web Gateway, which uses IBM WebSphere® technology, provides improved
security by leveraging Access Manager for authentication and the HTTPS
protocol for secure communications.


Enterprise Directory Query Facility service
The Enterprise Directory Query Facility is a deployment service that enables an
administrator to use information stored in enterprise directories inside a Tivoli
environment. The administrator can select a specific directory object, or
container of directory objects, as subscribers for a reference model or an activity
plan. The subscribers can then be targets for software distribution or inventory
scans.

Data Moving component
Data Moving is a Tivoli Configuration Manager component used to send, retrieve,
and delete data from endpoint to endpoint or managed node without creating a
software package.

Pristine Manager component
Pristine Manager is a component of Tivoli Configuration Manager available with
Version 4.2.1. Pristine Manager enables Tivoli Configuration Manager to manage
machines that have no operating systems installed (bare-metal machines). It
does not perform the real pristine setup; it leverages third-party products.

1.3 Target Tivoli Configuration Manager environment
For the sake of this Redpaper, only a subset of the features we just described will
be installed. Although it might be valuable to use more features to manage the
installation of Rational products across an enterprise, the focus of this Redpaper
is primarily on the packaging of the Rational installation files to ease the
installation of Rational products using Tivoli Configuration Manager.

For this purpose, the Tivoli Configuration Manager environment that we will
install includes only the following components:
Inventory Server and Gateway, Version 4.2.3
Software Distribution Server and Gateway, Version 4.2.3
Software packages
Activity Planner, Version 4.2.3
Endpoint Software Package Editor, Version 4.2.3

1.3.1 Installation of Tivoli Configuration Manager
Figure 1-2 on page 9 represents the environment used for the examples in this
Redpaper. We have created a simple Tivoli environment including a Tivoli
management region (TMR) server, gateway, and three Tivoli endpoints.


In our simple environment, the TMR server and gateway reside on the same
physical machine (prov003). In our environment, prov003 is running Windows
Server® 2003.

The endpoints include:
prov002: An endpoint that will be used to create and store the software
package definitions for distributing Rational software products. This system is
based on Windows 2003 Server.
ratep1: A system representing a typical target for distributing Rational
software applications. Operating system is Windows XP.
ratep2: A system representing a typical target for distributing Rational
software applications. Operating system is Windows Win2k.

Aside from the systems listed with Tivoli components installed, there is also a
machine named Theta that has a shared directory that will contain the actual
Rational software to be installed. The Tivoli software packages to be installed will
reference this shared directory to access the code to be installed.

prov003 theta
(Windows 2003) ------
------- File server
TMR Server
------ Rational product images
Gateway (Release Areas)

ratep1 ratep2 prov002
------ ------ ------
Tivoli Endpoint Tivoli Endpoint Tivoli Endpoint
(Endpoint
Software
Package Editor)

Target systems for Rational product installation
Figure 1-2 Environment used in the creation of this paper

For more details about the exact Tivoli components that were installed on the
systems in our environment, see Appendix A, “Tivoli Configuration Manager
environment installation” on page 71.


1.4 Summary
This chapter has introduced the Rational product suite and the IBM Tivoli
Configuration Manager, which can be used to install the Rational products to a
large number of systems. We have also briefly described the basic IBM Tivoli
Configuration Manager environment that was used in the development of this
Redpaper. For a step-by-step description of how we installed the environment,
refer to Appendix A, “Tivoli Configuration Manager environment installation” on
page 71.

After such an environment is installed, you are ready to create the packages that
are required to install the various Rational software products using Tivoli
Configuration Manager as described in the following chapters.


2

Chapter 2. Preparing Rational products
for IBM Tivoli Configuration
Manager
Before creating Tivoli Configuration Manager software packages to install
Rational products, it is important to understand the native method of installation
of the Rational products. To deploy the Rational products at an enterprise level,
Rational provides a method that utilizes a file repository called a release area.

This chapter explains the steps that are required to create a Rational product
release area and the files that will be referenced by Tivoli Configuration Manager
when defining and distributing a software package.


2.1 Rational product release area creation
A Rational product release area is a network shared drive that contains
installation files that you install by using the Setup wizard from the Rational
product CDs you are deploying and that you configure for easy and consistent
installation by users. These files include one or more site defaults files, which
contain default settings that apply to all users who perform a standard installation
from the release area.

2.1.1 Method for creating a Rational product release area
This section provides examples of creating and populating release areas for IBM
Rational PurifyPlus and IBM Rational ClearQuest using the Setup wizard. The
Rational product release area is a directory containing all the required files for
the installation of a Rational product. It not only contains the product files as
shipped on the product CDs, but it may also contain site definition files, which are
basically response files that allow for use of pre-defined options during
installation, therefore enabling a silent or unattended installation process.

The default site defaults file is named sitedefs.dat. If you execute the product’s
setup.exe command with no arguments, the settings as defined in sitedefs.dat (if
it exists) will be used.

You can generate multiple site defaults files (as described in this chapter) that are
specific to different products or teams and assign them meaningful names, such
as developers.dat or qualityengr.dat.

Restriction: When creating a site defaults file, do not add a file name
extension, such as sitedefs.developers.dat.

Users can install the product with the configurations you create by specifying the
site defaults file with the setup.exe command, for example:
setup.exe developers.dat

Or you can prepare shortcuts for these files, such as developers or
developers.lnk, which users can run from their desktops.
1. Log in as a user with administrator rights on the file server computer that will
host the release area.
2. Create a directory to host the release area using a meaningful name such as
C:RelAreaPurifyPlus.


Restriction: The maximum length of the path for the release area of an
Enterprise Deployment installation is approximately 30-35 characters. This
limit changes, depending on the product being installed and the length of
the paths of the files that each product installs. You might also see different
error messages when the root path exceeds the maximum length.

3. Make the release area directory shareable. Even if the drive that contains the
directory is already shareable, making the directory itself shareable makes it
easier to map directly to the appropriate release area for the product being
installed.
a. In Windows Explorer, right-click the Rational product Release Area
subdirectory and click the Sharing menu.
b. On the Sharing page of the properties window, click SHARE this folder
and provide a meaningful name, such as RAPurifyPlus.

Restriction: The share name should be less than 12 characters long to
be accessible by older systems such as Windows 98 or NT.

4. Insert the product CD into the computer’s CD drive. If you have downloaded
the software, click Setup.exe after you extract the files.
5. If autorun is enabled on your computer, the LaunchPad starts. If autorun is
disabled on your computer, click Start → Run and enter
cd_drive:Setup.exe, where cd_drive is the letter of the CD drive.

Chapter 2. Preparing Rational products for IBM Tivoli Configuration Manager 13

6. You should see the window shown in Figure 2-1. Select Install IBM Rational
PurifyPlus for Windows.

Figure 2-1 IBM Rational PurifyPlus setup: initial screen


7. The Deployment Method window opens. Select the Enterprise deployment
method and follow the instructions in the LaunchPad and Setup wizard.
The Setup wizard guides you through the selection of various options. Enter
the required information on each page of the wizard.

Figure 2-2 IBM Rational PurifyPlus deployment method selection


8. You will reach the window shown in Figure 2-3. Use the following instructions
to use the Deployment Method, Features, and Windows IDE pages of the
Setup wizard to configure the installation process

Figure 2-3 IBM Rational PurifyPlus launchpad and setup wizard


a. On the Installation Directory page, you can modify the default directory
setting, if required, as shown in Figure 2-4.

Figure 2-4 IBM Rational PurifyPlus installation directory setup


b. On the IBM Rational PurifyPlus for Windows page, you can specify
whether to integrate with Microsoft Visual Studio® .NET 7.0, Microsoft
Visual Studio .NET 7.1, with both, or with neither. The IDE must be
installed before you can integrate it with other products.
If you need information about entering data on other wizard pages, press
the F1 key for help.

Figure 2-5 IBM Rational PurifyPlus IDEs selection


c. On the IBM Rational License Server page, supply a license server name if
you are using floating licenses.

Figure 2-6 IBM Rational PurifyPlus license server setting

d. On the Description page, you are required to enter description text for this
installation configuration, as shown in Figure 2-7.

Figure 2-7 IBM Rational PurifyPlus installation configuration description


e. On the Create Release Area page, you are required to set release area
data including the path and the name of the site definition .dat file that by
default is set to sitedefs.dat. In our example (Figure 2-8) we have changed
the site definition file to PurifyPlussitedefs.dat

Figure 2-8 IBM Rational PurifyPlus Release Area path and site definition file settings

f. After completing the wizard settings that are needed to create the Rational
product release area and clicking Done, a prompted appears stating that a
link file was created to run the setup with the configured sitedefs.dat file.
We will not use this file, so just click OK to dismiss it.

Figure 2-9 IBM Rational PurifyPlus release area link file creation


g. The Rational product release area creation starts, and the software
license agreement prompts to be accepted.

Figure 2-10 IBM Rational PurifyPlus software license agreement

h. After creating the Rational product release area, the final window appears.

Figure 2-11 IBM Rational PurifyPlus setup complete


i. Now that the release area has been created, you are ready to create a
software distribution package to install this software using the
sitedefes.dat file that you created (in our case PurifyPlussitedefs.dat) on
other systems. This is described in detail in Chapter 3, “Creation of
packages to install Rational products” on page 33.

2.1.2 ClearQuest example
All Rational product release areas are created as demonstrated in the last
section for IBM Rational PurifyPlus. However, each product might have unique
configuration options. In this section, we highlight some of the unique options
that are associated with IBM Rational ClearQuest to provide a second example
for your reference. Each Rational product has a unique release area.
1. In this second example, because it is a different product, we are required to
choose a different product release area subdirectory with a different name,
such as C:RelAreaClearQuest, that will have a different share name such as
RAClearQuest.
2. The LaunchPad and Setup wizard displays a different set of links on the left
navigator panel, such as Default Connection Profile.

Figure 2-12 IBM Rational ClearQuest setup wizard


3. On the Features page, we have chosen to use the default features.

Figure 2-13 IBM Rational ClearQuest features page

4. On the Default Connection Profile page we have also kept the default settings.

Figure 2-14 IBM Rational ClearQuest default connection profile page


5. For e-mail notification, we have also kept the default settings.

Figure 2-15 IBM Rational ClearQuest default Email Notification page

6. Finally the release areas settings reflect the different shared directory used
and a product-specific configuration file: ClearQuestsitedefs.dat.

Figure 2-16 IBM Rational ClearQuest Release Area page


2.2 Product release area modification
In the previous section we created a Rational product release area that consists
of a shared directory including all of the Rational product software and an initial
<sitedefsname>.dat configuration file. After completing this, you might want to
modify the <sitedefsname>.dat configuration file to choose different options or to
customize it for a different set of users.

2.2.1 Modifying an existing configuration file
To modify an existing <sitedefsname>.dat configuration file, follow the procedure
described in the following steps:
1. Log on with administrative rights on the server where the release area has
been created.
2. Open an Explorer window and access the release area directory. Double-click
the siteprep.exe program.

Figure 2-17 Run the siteprep.exe program from the release area directory


3. A dialog window opens (Figure 2-18). Click Open.

Figure 2-18 Initial dialog for siteprep.exe

4. Select an existing <sitedefsname>.dat configuration file that you want to
modify. In our example, we select ClearQuestsitedefs.dat.

Figure 2-19 Configuration file selection


5. The siteprep.exe program opens the configuration wizard window, enabling
you to change the configuration settings that are required for the installation.

Figure 2-20 Configuration wizard window

6. For example, if we want to set the e-mail configuration parameters that were
not set when we initially created the release area, click Email Notification on
the left navigation panel and fill in the required parameter (Figure 2-21).

Figure 2-21 Email Notification setting change


7. When changes are complete on any of the various configuration wizard
pages, click Finish. The siteprep.exe program terminates, showing a last
pop-up window that indicates that a new shortcut was created.

Figure 2-22 Shortcut creation message

8. Click OK and ignore the shortcut creation message because we will not use
it. However, the modified configuration file has now been saved.

2.3 Creating another configuration file
To create a new <sitedefsname>.dat configuration file, you have three
alternatives:
1. Create a new file from scratch.
2. Duplicate an existing file and modify it.
3. Open an existing file, modify it, and save it under a different name.

This section briefly describes these three alternatives.

2.3.1 Create a new configuration file
To create a new <sitedefsname>.dat configuration file, you can run the
siteprep.exe program as described in 2.2.1, “Modifying an existing configuration
file” on page 25.
1. Select New (Figure 2-23 on page 29) instead of selecting an existing
configuration file as described in step 4 on page 26.


Figure 2-23 siteprep.exe program new configuration

2. You are prompted to select the appropriate product. Because each product
has its own release area and you are executing siteprep.exe from the product
specific release area, the dialog will only ever display one product. In
Figure 2-24, the dialog is shown listing the IBM Rational ClearQuest product.

Figure 2-24 New configuration product selection


3. As in step 5 on page 27, the siteprep.exe program configuration wizard is
almost identical, except for the default settings. (The Description is
highlighted in red.) After setting the required options, click Finish.

Figure 2-25 New configuration wizard

4. You are prompted to save the new configuration file with the name of your
choice.

Figure 2-26 Save As dialog for new configuration


2.3.2 Duplicate an existing configuration file
If you want to create another <sitedefsname>.dat configuration file and you think
you could reuse a large part of an existing file, it might be worth copying the
existing file under a different name in the same release area directory, then
modifying the duplicated configuration file using the siteprep.exe program as
described in 2.2.1, “Modifying an existing configuration file” on page 25.

2.3.3 Clone an existing configuration file
Another method similar to the previous one is to modify an existing configuration
file using the siteprep.exe program and saving the existing (and newly modified)
configuration file under a different name.
1. Open the existing file that you want to clone under a different name as shown
in step 5 on page 27.
2. We suggest that you first save the configuration file under a different name by
clicking the Save As icon in the siteprep.exe program configuration wizard
(shown in Figure 2-27).

Figure 2-27 siteprep.exe program configuration wizard Save As icon

3. Set the new configuration file name.

Now, all further changes you apply in the siteprep.exe program configuration
wizard will be saved in the new configuration file.


2.4 Installing from a Rational product release area
After a Rational product release area and a <sitedefsname>.dat configuration file
have been created, the Rational product can now be installed. If the configuration
file has all desired options specified, then the installation can be invoked in silent
mode. That is, it can be launched and the installation will complete with no further
input required by the user. This silent mode capability will be utilized within Tivoli
Configuration Manager to install the Rational products on a large number of
systems utilizing the defaults as specified in one or more configuration files. The
next chapter details the method for doing this with Tivoli Configuration Manager.

To install from a Rational product release area using a customized
<sitedefsname>.dat configuration file, a user with administrative rights on the
client system can simply open a standard DOS window and switch to the
Rational product release area (which typically resides on a shared file system of
a server).

From the release area, the user can issue the following command:
setup.exe /g <sitedefsname>.dat /lv <mylogfilename>.log

In this command, the arguments have the following meanings:
/g Option used to run the setup in silent mode (using the sitedefsname.dat
file to obtain the various installation options.
/lv Option used to specify a verbose logfile where all of the details of the
installation will be recorded.

This Rational native command is used to create the Tivoli Configuration Manager
software package as described in the next chapter.


3

Chapter 3. Creation of packages to
install Rational products
This chapter describes how to package the various files that are required for
installing Rational products such that IBM Tivoli Configuration Manager can
distribute and install these Rational products on chosen endpoints. To create the
packages, the Software Package Editor must be installed on a Tivoli endpoint.

We provide a representative example in this chapter for creating a package to
install Rational PurifyPlus. For this application, we show how to create a software
package when the release area and sitedefs file are set up on a remote file
server. Other deployment options are also described.


3.1 Software package formats
IBM Tivoli Configuration Manager distributes and installs software using a
construct called a software package. A software package generally defines the
files to be distributed and any commands to be executed. Software packages are
created using the Software Package Editor.

After software packages are defined, they can be distributed to large numbers of
endpoints to carry out product installations.

There are actually three different formats of software packages. The following
sections will help in determining how to choose the right package format for each
individual customer environment.

Regardless of the method used to create a software package, the output can be
saved in any of the following formats:
Software package file (.sp)
Software package definition file (.spd)
Software package block (.spb)

Note: A software package can be opened in the Software Package Editor
regardless of the format. You can then choose to save it in any of the other file
types available. For more information about software package definition
parameters, keywords, and formats, refer to the IBM Tivoli Configuration
Manager: Reference Manual for Software Distribution.

3.1.1 Choosing a software package format
If you have created a software package using the Software Package Editor on an
endpoint or on a managed node, you must choose one of the following software
package formats:
The built format: a software package block (.spb file), using the files on the
local machine. A built format package, is a zipped file that physically contains
all of the related files. This zipped file is created when you define the software
package. If any files must be changed after the package has been created but
before it is distributed, then the package must be re-created.
The not-built format: a software package file (.sp file) or software package
definition file (.spd file). The not-built format is a package that contains
references to the files to be included, instead of the actual files themselves. In
this case, if the files that are referenced are changed or updated before
distribution, then the new files are distributed without having to re-create the
package.


Each format has its advantages. For example, if you maintain the software
package in the not-built format, you can revise the software package until the
moment of distribution. The consolidation of the actions with the files and
resources does not occur until distribution, and the most current files on the
source host are used to build the package. Also, because a software package in
the not-built format does not contain the files and resources to be distributed, it
occupies a smaller amount of disk space than a software package block.

Alternatively, if you build the software package to create a software package
block, you ensure that the data in the software package remains static between
distributions at different times. At this point, the package could possibly be
pushed to the gateways or individual file servers throughout the respective
regions where the package could be kept closer to their targets. This might be
the option to choose when a package is rather large and has to be distributed to
targets across country and region boundaries.

The first option we describe is also the option that we primarily illustrate
throughout this chapter. With each distribution option, we also illustrate a
possible environment setup of the distribution.

Software package (.sp) file
This includes a software package saved as an .sp file. It is a format that is a
zipped form of an .spd file. It contains only a description of the actions to be
performed on the target system and not the files and resources necessary to
execute the actions. The files and resources reside on the source host. The
software package file format is the default format used by the Software Package
Editor. Because the software package in this format is only a description of the
software package, it is in the not-built format.

The push would be performed from the TMR server (as always), pushing a small
package through the gateway that then fans the package out to the different
targets. This method requires little bandwidth for the push of the package itself.
When choosing this option, you should consider that the individual targets will all
have to pull the files to be installed from a file server. That is, the software
package contains only references to the files and those references would
typically point to a common file server that contains them. In the case of Rational
products, the file server and directory being referenced would be the release
area as described and created in Chapter 2, “Preparing Rational products for
IBM Tivoli Configuration Manager” on page 11.

Because each client will pull the files to be installed from a file server, multicast
distribution is not used and bandwidth considerations should be taken into
account. Of course, this depends on the size of the products being installed and
the network being used.

Chapter 3. Creation of packages to install Rational products 35

This method might be recommended when pushing to a small number of targets.

Figure 3-1 The software package (.sp) is pushed in a not-built form

Figure 3-2 on page 37 describes distribution of another package in not-built form.
This distribution calls a before script that then mounts a drive to the respective
file server. Based on the endpoint’s IP address or other similar information, the
simple script could mount a file server local to the endpoint. If this logic were
added, then the release areas could be distributed to multiple locations (using
Tivoli Configuration Manager), and then actual installations would be able to
access local servers instead of accessing the installation files over a possibly
slower-speed WAN.

In this figure, the TMR server and the gateways could be UNIX servers. For
Rational packages, the file servers as well as the targets must be Windows
based because Rational product release areas are being accessed.


Figure 3-2 Software package is pushed in a not-built form with unique file servers for
different regions

For more software package configuration options, consult the IBM Tivoli
Configuration Manager Reference Manual for Software Distribution Version
4.2.3, SC23-4712.

Software package block (.spb)
A software package block bundles all of the resources that are needed to execute
the actions contained in the software package into a standard zipped format. At
distribution time, the resources do not have to be collected from the source host;
they are already contained in the software package block.

In this case, the entire installation image (release area) is distributed to the
targets. Although the package is much larger than the not-built format, multicast
distribution can be used to limit the effect on the network and to improve
performance.

This format can be used to distribute the release area (and installation
commands to be executed) to each endpoint.


A hybrid solution could also be developed to use this format of package to copy
or create a release area on various file servers, and then use a second step to
send packages in the not-built format to reference the appropriate file server to
perform the installation.

A software package that contains all of its resources is in the built format. The
maximum size of a software package block is 2 GB.

In the example below, the full package has been distributed to the respective
gateways. After the gateways have received the package, the release area will be
installed on the gateway system itself. From there, the target endpoints can
simply pull the code from the local gateways. This eliminates the need for all
targets to go to one file server, as illustrated in Figure 3-1 on page 36.

This setup is recommended for larger distributions of the Rational code by way of
Tivoli Configuration Manager.

Figure 3-3 The software package is pushed in a built form, first to regional gateways, then to endpoints

Note: In this example, for Rational installation purposes, the gateways must
be Windows based.


3.2 Creating the Rational PurifyPlus software package
This section describes how to create a software package when deploying a
single product using a remote file server. For this type of deployment, we would
use the non-built format to create a software package (.sp) file. Refer to
Figure 3-1 on page 36 for an example of the environment used in this scenario.
1. Launch the Software Package Editor by clicking the Software Package Editor
icon on the desktop of your system that has the endpoint software package
editor installed.
2. In the Software Package Editor Selector window (Figure 3-4), select Native
Package Technology and click OK.

Figure 3-4 Select type of software package


3. The Native Package Technology window opens (Figure 3-5). Select
Microsoft Setup and click OK.

Figure 3-5 Select the Native Package Technology

4. The Microsoft Setup Program Builder window opens. Type setup.exe in the
Program field, and select the Self-extracting executable check box. Type
the path where the product installation code is located (likely the Rational
PurifyPlus release area) in the Target image path field, and select the
Redirected installation check box. Click Next. (Figure 3-6).

Note: If you have mapped the network drive of the release area, you can
click the ellipsis button (...) to the right of the field and choose the path of
the release area. Otherwise, you have to type in the path using UNC
syntax as in Figure 3-6 (for example, ServernameSharename).

Figure 3-6 Point to the file and path of the setup file


5. The next page of the Microsoft Setup Program Builder window appears. Type
/g sitedefsfile in the Arguments field. In the Working directory field, type
the path where the site definitions (.dat) file is located. This is likely to be the
same location as in the previous step, that of the Rational PurifyPlus release
area. Select the User input required check box, and click Finish (Figure 3-7).

Note: The site definitions file chosen in the Arguments field is the file that
was created in Chapter 2, “Preparing Rational products for IBM Tivoli
Configuration Manager” on page 11. Be sure to choose the correct
definitions file based on the features and options you want installed.

Figure 3-7 Point to the file and path of the site definitions file


6. The Software Package Editor window opens. Click File → Save As.

Figure 3-8 New software package is created

7. The Save window opens. In the Look in field, choose a local directory, and
type a name in the File name field. In the Files of Type field, be sure that
Software Package (.sp) is selected. Click Save.

Figure 3-9 Save the software package file

The software package file for Rational PurifyPlus has been created successfully.
In Chapter 4, “Deployment of Rational packages” on page 51, we describe how
this package gets distributed to targeted endpoints.


3.3 Editing the software package
Follow these steps to edit an existing software package.
1. Launch the Software Package Editor by clicking the Software Package Editor
icon on the desktop of your ESPE machine.
2. In the Software Package Editor Selector window, select Open an existing
software package, click the ellipsis button (...) to the right of the field, and
choose the path where the software package was saved. Find the .sp file you
want to edit, click it, and click Open.
3. The software package opens. Right-click the object you want to edit (for
example, setup.exe) and click Properties.
4. The Advanced Properties window opens (Figure 3-10). Here, you can modify
the arguments, working directory, and so on. When you are finished, click OK.

Figure 3-10 The Advanced Properties for the object in the software package

5. Click OK on the Properties window, and click File → Save. The software
package file is edited and saved.

3.4 Creating a .spb package
In the previous example, the PurifyPlussetup software package created in the
Software Package Editor displays only a description of the objects contained in
the package. That is, it contains a sequential list of actions to be performed on the
target machine and not the objects or resources themselves such as files and
programs to be executed. Actions require resources to be executed. When the
actions are consolidated with the actual resources (files, directories, registry keys,
and so on), the software package is considered to be in a built format (.spb).


To create a software package block, complete the following steps:
1. Start creating the package as in 3.3, “Editing the software package” on
page 43. Follow the same steps until the File → Save in step 5 on page 43.
2. Use the add directory object action to add directories, files, and links and to
set file system object attributes related to the target operating system. In this
scenario we again use PurifyPlus as an example: You add an action that adds
all files contained in a directory called PurifyPlus to the software package.
Begin by adding a directory action to the PurifyPlussetup software package:
a. Select the PurifyPlussetup software package icon in the left pane.
b. Select the Add object tab in the right toolbar and click the Directory icon.
3. The Add Directory Properties dialog appears (Figure 3-11). Enter the
following information in the Source section:
– In the Location text box, enter c:PurifyPlus or click browse (...) to display
a file system browser dialog.
– In the Name text box, enter *.* to specify that all files contained in the
PurifyPlus directory are to be added to the package. The files are installed
with their original name into the target directory at installation time.

Figure 3-11 Add Directory Properties dialog


4. The Destination box also asks for location and name. You can specify a
specific directory or, as in our case, use a variable to render this operation
more generic for use on different operating systems or different locations. You
can right-click the Location text box to display the Variable List Editor
(Figure 3-12).
5. Define a new variable and assign a default value.
a. In the Name text box, enter target_dir.
b. In the Value text box, enter $(system_drive)PurifyPlus.
c. Click Set to add the new variable and its value to the list.

Figure 3-12 Add a variable to the Variable List Editor

You can reuse this variable anywhere in your software package. To modify the
variable, update it in the Variable List Editor and it will change all occurrences
in the software package. Refer to the IBM Tivoli Configuration Manager:
Reference Manual for Software Distribution for more detailed information
about using variables. To render the value of this variable dynamically, you
can use a before script to set the value of this variable on individual endpoints.
Click OK.
6. This returns you to the Add Directory Properties dialog (Figure 3-11 on
page 44). Delete *.* in the Destination - Name text box, because it is


unnecessary in this case. The files are installed with their original name into
the target directory at installation time.
7. Set the check boxes in the Add Directory Properties dialog:
– Stop on failure (selected by default): Leave selected to stop the execution
of the action if the action fails or if the condition is not met. The execution
of the remaining actions in the package continues, provided that the Stop
on failure option at the package level is not selected. If the Stop on failure
check box is selected at the package level and an error occurs, the
remaining actions are not performed and the execution of the package is
not completed.
– Replace if target is newer: Select this to replace a target object even if
the target object is newer than the source object. On Windows platforms,
to determine which file is newer, Software Distribution evaluates the
version of the file. If the version of the target file is newer than the source
file, the target file is replaced. If the version is not set, or on platforms other
than Windows, Software Distribution evaluates the modification time. If the
modification time of the target object is more recent than the source
object, the target object is replaced. File version support is available if the
source host is a Windows machine or if the software package containing
the file in question has been built on a Windows machine and imported in
the software package block (built) format.
– Replace if existing (selected by default): Leave selected to replace an
object that already exists on the target.
– Remove if modified: Select to flag this object for a subsequent remove
operation. During a remove operation of the same software package, the
flag indicates to remove the object even if the target object has been
modified since the last install operation.
– Create if not existing: Select this check box to create the directory if it
does not already exist on the target system.
8. Click Advanced to specify platform-specific file system attributes using the
Add File System Objects Properties - Advanced dialog (Figure 3-13 on
page 47):
– Leave Create directories selected to create directories if they do not
already exist on the target system. If you know that the directory already
exists, clear this check box so that during an installation the directory is not
created and during an undo operation the directory is not removed.
– Leave Remove empty directories selected to remove empty directories
when performing a subsequent remove operation of this software
package.


– Select Descend directories to add the entire directory tree to the
software package. If it is not selected, only the files listed below the
top-level directory are added.

Note: If the Descend directories check box is selected and its inventory
signature is set to Restricted, you will receive a warning message for
each invalid file that is present in the nested directories.

– Select Rename if locked to temporarily rename files that are in use by
another application. For Windows platforms, during an installation an
attempt is made to replace or rename the file under the same directory as
the locked file and the distribution completes successfully without having
to wait for a reboot of the system. The temporary file is removed during the
next system reboot. During a remove operation, the locked file is removed
during the next system reboot.
Click OK to confirm the selection of the file system object properties.

Figure 3-13 Add File System Objects advanced properties

For more information about the file system attributes in this dialog, refer to the
online help documentation or the IBM Tivoli Configuration Manager:
Reference Manual for Software Distribution.


9. Click OK to add this action to the software package. Select the software
package icon in Software Package Editor window to display the Add directory
object action.
10.Now it is time to save the package. To consolidate the actions with the
resources into a zipped file, you will need to save the software package as a
software package block, selecting .spb as the file type.

3.4.1 Adding an Inventory signature to a native software package
An Inventory signature is the set of information that identifies a certain software
application, such as the name and size of the executable file for the software
application. It is typically used with the Inventory application of Tivoli
Configuration Manager. Signature data includes the name, size, and usually a
checksum value of the file that is used to identify the software product. This
identifying file tends to be the primary executable file for the product. The
signature data collected during a scan is stored in the configuration repository in
the MATCHED_SWARE table.

We now add an Inventory signature for our PurifyPlus package. This enables us
to check whether PurifyPlus (or any other Rational product that we create a
signature for) is already installed, or to validate that it has become installed after
a distribution. In order to do so, and to be able to actually retrieve the data,
Inventory must first be integrated with Software Distribution. This integration
occurs through this Tivoli Configuration Manager command:
wsetinvswd y

When this is done, we can proceed as follows:
1. To add an Inventory signature, click the System action tab of the Software
Package Editor as shown in Figure 3-14 on page 49.


Figure 3-14 The System action tab allows for an Inventory Signature to be created

2. In this example we associate the setup.exe PurifyPlus executable file, size
2281472 bytes, to our PurifyPlus software package, version 7.0.0. If the file
does not have a proper description (check the properties), you should add a
description and version number for identification reference in the tables.

Figure 3-15 Setting the inventory signature


3. After adding the inventory signature, save the package. This has to be done in
the built form (.spb) of the software package.

Figure 3-16 Save the package after the Inventory Signature object is created

The Inventory signature information is updated in the RDBMS because we
selected the “Add if not existing” option when adding the signature.

The updated signature information can be verified using the wsigmapsp -a
command. This command can be used to list the mapping between software and
the file signatures.

3.5 Summary
This chapter has described the basic steps for creating a software package for a
Rational product. In the next chapter we describe the steps for actually
distributing this package to a large number of systems. The Rational product that
is associated with the software package will be installed when it is distributed.


4

Chapter 4. Deployment of Rational
packages
This chapter uses the packages created in the previous chapter to provide
step-by-step examples of deploying Rational products utilizing Tivoli
Configuration Manager.

We also demonstrate the Tivoli Configuration Manager Inventory feature to track
deployed packages, and provide examples of the use of Tivoli Configuration
Manager’s activity planner to deploy a suite of Rational products.


4.1 Creating a Software Distribution profile
Tivoli management is typically performed by defining profiles and sets of
subscribers to those profiles. In the case of software distribution, a software
package as was created in Chapter 3, “Creation of packages to install Rational
products” on page 33, is associated with a profile and then distributed to the
Rational user systems.

You create a Software Distribution profile within a Tivoli profile manager that has
been defined in a Tivoli policy region. You then import software packages into
Software Distribution profiles.

The following scenario creates a Software Distribution profile from the Tivoli
desktop and imports the different Rational software packages. In this scenario,
the distribution environment consists of:
An administrator: Root_prov003-region
A policy region: prov003-region
A subregion: rational-region
A managed node: prov003
A profile manager that contains an Tivoli Configuration Manager profile for
SoftwareDistribution

Log in to the Tivoli desktop using an administrator with the appropriate rights to
perform software distribution actions. (Refer to Tivoli Management Framework:
User's Guide for more information about administrators.)

From The Tivoli Desktop main window:
1. Double-click the prov003-region icon to display the contents of the policy
region. Select Create → Subregion.

Figure 4-1 Selecting the subregion


2. The Create Policy Region dialog opens. Specify the subregion name (in our
case, Rational). Click Create & Close.

Figure 4-2 Create policy region

3. Navigate to the new subregion. In the Policy Region: rational-region dialog,
select Create → ProfileManager to create a profile manager in which the
Rational Software Distribution software package profile will reside.
4. The Create Profile Manager dialog, in which you define the name of the
profile manager, is displayed. In the Name/Icon Label text box, type the name
of your choice. In our case we chose SoftwareDistribution.
5. Select Dataless Endpoint Mode to enable the profile manager to distribute
software package profiles to Tivoli endpoints.

Figure 4-3 Create profile manager

6. Click Create & Close to return to the Policy Region: rational-region dialog,
which now shows the SoftwareDistribution profile manager.

Chapter 4. Deployment of Rational packages 53

4.1.1 Setting the profile subscribers
Before you can perform an operation on the profile, you must set the subscribers
for the profile manager in which the profile resides. Subscribers can include other
profile managers, endpoints, or resource groups. In our case, we will distribute to
endpoints that represent the workstations of our Rational users.
1. Choose Profile Manager → Subscribers as shown in Figure 4-4.

Figure 4-4 Add subscribers

This displays a dialog for selecting subscribers (Figure 4-5 on page 55).


Figure 4-5 Subscribers dialog

2. In the following scenario we add seven endpoints as the subscribers to the
SoftwareDistribution profile manager.

Figure 4-6 Choosing potential targets for the distribution


a. Again, select Profile Manager → Subscribers to display the Subscribers
dialog.
b. To move a subscriber to the Current Subscribers list, select one or more
subscribers from the “Available to become Subscribers” list, then click the
left arrow button. Select Set Subscriptions & Close to save the list.
By default, all subscribers in the profile manager are displayed in the Available
to become Subscribers list.
To remove a subscriber, select one or more subscribers from the Current
Subscribers list and click the right arrow button to move them to the Available
to become Subscribers list.
3. Now it is time to create a profile in the SoftwareDistribution profile manager.
Double-click the SoftwareDistribution icon to open the Profile Manager dialog.
4. Select Create → Profile to display the Create Profile dialog. In this dialog you
create a software package profile for the Rational software package.

Figure 4-7 Opening the dialog to create a new profile

5. In the Name/Icon Label text box, type the Rational profile name.


6. Select SoftwarePackage resource type from the Type scrolling list.

Note: If the resource type is not available in the scrolling list, you must add
it as a managed resource of your policy region by moving it from the
Available Resources to the Current Resources in the policy region. Each
policy region maintains a list of managed resource types that are valid or
defined for that specific policy region.

Figure 4-8 Entering the profile name and type

7. Click Create & Close to create the new profile and return to the Profile
Manager dialog. An icon representing the newly created software package
profile is displayed in the SoftwareDistribution profile manager. In our case,
we call this package PurifyPlusSWD.pm.
The software package profile at this point is empty.


8. Double-click the SoftwareDistribution profile manager dialog. The profile now
appears with all of its subscribers (Figure 4-9).

Figure 4-9 Profile manager with (empty) profile and subscribers


4.1.2 Importing a software package into the Tivoli environment
Before you can use a software package profile to distribute a software package
to a target system, you must import the software package into the Tivoli
environment where it is cataloged as a software package object in the Tivoli
object database. The software package profile is only a definition of the
information that each profile item includes. The profile items must be populated
with the database objects in order to be distributed.

Figure 4-10 Selecting Import to populate the profile

You can import an existing software package located on either an endpoint or
managed node into the software package profile, or you can create a new
software package within the software package profile.


Figure 4-11 Import dialog

Importing an existing software package
An existing software package can be imported in a built format (.spd) or in a
not-built format (.sp). Before it is built, a software package contains only a
description of the objects contained in the package: that is, a sequential list of
actions to be performed on the target system and not the actual resources
themselves, such as files and programs. The resources reside on the source
host. A software package in the built format already contains all objects and
resources that are required by the actions in a zipped file format.

In this scenario, the PurifyPlusSWD.pm profile is populated with the
PurifyPlussetup.sp software package, which is in the not-built format. (We
created this package in Chapter 3, “Creation of packages to install Rational
products” on page 33.)
1. Right-click the PurifyPlusSWD.pm profile from the Profile Manager dialog,
then select Import from the pop-up menu.The Import dialog imports a
software package file into a software package profile.
2. In the Location of Input File box, specify the machine type where the software
package exists from the drop-down list. Again, the options are Managed Node
and Endpoint. If you select Endpoint, type the name of the endpoint in the


Endpoint Name text box and click the ellipsis (...) button.In our case, we use
Endpoint.
3. Click the ellipsis (...) button to display the Select Input File dialog. The dialog
displays the file system hierarchy for the prov002 endpoint. The file you select
in this browser dialog is the file that is imported into the PurifyPlusSWD.pm
software package profile.
4. Trace the path to the PurifyPlusSetup.sp file in the Directories and Files
boxes. Click Set File & Close to return to the Import dialog.

You can import the software package either in the built format or in the not-built
format:
To import the PurifyPlusSetup software package in the not-built format,
perform the following steps:
a. Deselect the Build check box in the Location of Source Host box.
b. In the Source Host Name text box, type the name of the source host. The
package is built at distribution time, and the resources referenced in the
software package are collected from the specified source host. Ensure
that, when a package is being built at distribution time or imported to the
built format, the Software Distribution component is installed on the source
host. If not, an error occurs.

Figure 4-12 Importing our package from endpoint prov002


To import the PurifyPlusSetup software package in the built format:
a. Select the Build check box.
b. Type the SPB path in the SPB Path text box. If the input file is a software
package or software package definition file, it is imported into a software
package block. If the input file is a software package block, it is copied
from the managed node or endpoint specified in the Location of Input File
box to the specified software package block path on the source host.

Note: Always select the Build check box when importing a software
package block.

Selecting Build enables the Overwrite check box. Select Overwrite to
overwrite the software package block should it already exist on the
source host.

In this scenario, deselect the Build check box.

c. In the Source Host Name text box, type the source host from which the
files in the software package block are to be obtained, if it is not already
defined in the input file.

Note: The source host can be any of the available managed nodes on
which the Software Distribution component is installed.

d. Click Import & Close. The software package profile icon in the Profile
Manager dialog is now in the not-built format.

4.1.3 Using software signatures
A signature is the set of information that identifies a certain software application,
such as the name and size of the executable file for the software application.
Tivoli Configuration Manager Inventory provides a default set of signatures that
you can use to collect information about the software installed on the endpoints
in your enterprise. These signatures are stored in the
$BINDIR/../generic/inv/SIGNATURES directory in the SWSIGS.INI file. To use
these signatures, you must install them with the winvsig command as shown in
the following example:
winvsig -a -f $BINDIR/../generic/inv/SIGNATURES/SWSIGS.INI

This command installs the signatures in the configuration repository in the
SWARE_SIG table.


You can edit or delete the signatures provided with Inventory, or you can add your
own signatures. For example, you can add a signature that is not currently
provided with Inventory or for an application that was developed in-house.

Inventory uses signatures to determine which software applications are installed
on the machines you scan. When you run a signature scan on an endpoint,
Inventory distributes the signatures to the endpoint, and then compares each file
on the endpoint to the list of signatures. When a file matches a signature, the
signature data for that file is sent to the configuration repository. Because only
data for matching files is sent, this scan returns less data to the configuration
repository than scans for basic file information or header information.

Signature data includes the name, size, and usually a checksum value of the file
that is used to identify the software product. This identifying file is usually the
primary executable file for the product (for example, PurifyPlusSetup.exe). The
signature data collected during a scan is stored in the configuration repository in
the MATCHED_SWARE table. You can use the INVENTORY_SWARE query to
return all software information about a machine.

Signature scans return data only for matching files. Therefore, if you scan your
enterprise using only signature scans, the configuration repository contains data
only for matched files, not for all files on each scanned system. After you create a
new signature or edit an existing one, you must then rescan your enterprise to
gather the new or revised signature data.

However, if you have performed a scan for basic information, the configuration
repository contains information about all files on scanned systems, not just those
that match signature data. In this instance, you can write a query to view the
desired file information, rather than modify the signatures and then rescan your
enterprise.

To use software signature matching, you must enable Inventory to integrate with
Software Distribution by running the following command:
wsetinvswd y

Also, as noted in Chapter 3, the package has to be saved in built format (.spd) if a
signature is added. In the example above, no signature was added, so we were
able to save the package in not-built format (sp).

4.1.4 Installing a software package

Note: As with most other software applications as well as the Tivoli base
product install, this package installation must be performed with administrative
privileges.


The install operation performs the actions contained in the software package.

Figure 4-13 Installing a software package associated with a profile

To perform an install operation from the command line, see the winstsp
command in the IBM Tivoli Configuration Manager: Reference Manual for
Software Distribution.

The following command shows how to install a software package on multiple
targets. The -cr flag is added and recommended for Windows systems when
installing Rational products. This flag automatically reboots the machine after the


installation of the software package is finished. If several targets are specified,
separate each target with spaces.
winstsp @<SoftwarePackage> @target1 @target2
winstsp -cr @PurifyPlusSetup.sp @ratep1 @prov002

To perform an uninstall operation from the command line, see the wundosp
command in the IBM Tivoli Configuration Manager: Reference Manual for
Software Distribution.

If in any case the installation of the software package must be rolled back, you
can use the wundosp command, which returns the system to its state prior to the
execution of the previous operation. The wundosp command returns either:
0 Indicates that wundosp started successfully.
-1 Indicates that wundosp failed due to an error.

You can roll back the entire package with the following command. This means
that if no subscriber is specified, the package will be removed from all
subscribers. The -cr flag is added to automatically reboot the system after
removal. This flag is recommended on Windows machines only.
wundosp -cr @<SoftwarePackageName>
wundosp -cr @PurifyPlusSetup.sp

Or the package can be removed from only one subscriber with the following
command:
wundosp @<SoftwarePackageName> @target1
wundosp -cr @PurifyPlusSetup.sp @ratep1

Multiple targets are specified by using spaces:
wundosp -cr @PurifyPlusSetup.sp @target1 @target2
wundosp -cr @PurifyPlusSetup.sp @ratep1 @prov003

4.1.5 Checking the outcome of a distribution
You can check the outcome of a distribution in the following ways:
Check the MDist2 status using the wmdist command or checking the MDist 2
Distribution Status console (Figure 4-14 on page 66).


Figure 4-14 MDist2 status console

See the Software Distribution message or message ID reported in the
Message table of the MDist 2 database.
This can also be checked with the command line interface. Use the wmdist -l
command to retrieve the individual distribution IDs. In our example in
Figure 4-15 on page 67, distribution IDs 1021223264.148 and
1021223264.149 are being used. Follow up with the wmdist -q
<distributionID> command to ensure that the distribution has completed
successfully.


Figure 4-15 wmdist example

Software Distribution log
Several log files on the TMR server and endpoint client can be also be viewed
for verification.
Errors are logged in the Software Distribution log file, which is available on the
Tivoli server in the $BINDIR/../swdis/work path.
Other logs to be examined are:
– %DBDIR%/oservlog
– %DBDIR%/gatelog
On the endpoint, unless software distribution tracing has been enabled, only
the following log file will be available:
– <install_dir>Tivolilcfdat1lcfd.log
By default, this lcfd.log has trace level 0. It is recommended that you set
debug level on this file from 1 to 3. To do so, modify the
<install_dir>Tivolilcfdat1last.cfg file, setting log_theshold=3.

Example 4-1 Setting the log threshold
lcfd_port=9495
lcfd_preferred_port=9495
gateway_port=9494
protocol=TCPIP
log_threshold=3
start_timeout=120
run_timeout=120


lcfd_version=41134
logfile=C:Program FilesTivolilcfdat1lcfd.log
config_path=C:Program FilesTivolilcfdat1last.cfg
run_dir=C:Program FilesTivolilcfdat1
load_dir=C:Program FilesTivolilcfbinw32-ix86mrt
lib_dir=C:Program FilesTivolilcfbinw32-ix86mrt
cache_loc=C:Program FilesTivolilcfdat1cache
cache_index=C:Program FilesTivolilcfdat1cacheIndex.v5
cache_limit=20480000
log_queue_size=1024
log_size=1024000
udp_interval=300
udp_attempts=6
login_interval=1800
lcs.machine_name=prov003
lcs.crypt_mode=196608
lcfd_alternate_port=9496
recvDataTimeout=2
recvDataNumAttempts=10
recvDataQMaxNum=50
login_timeout=300
login_attempts=3
detect_address_delay=30
upcall_pool_size=100
upcall_pool_timeout=300

Check results logged into the Software Distribution 4 notice group.
If needed, further trace logs can be created the following way:
wswdcfg -s trace_level=5
The files will be written to the directory specified in the working_dir in the
output of wswdcfg -s, typically $BINDIR/../swdis/work.

4.2 Installing product upgrades
Rational products are refreshed periodically with patches or upgrades. To
maintain the latest version of the Rational software products on the client
systems, IBM Tivoli Configuration Manager can be used as well.


Rational updates typically are distributed in two ways:
As a complete replacement, in which the upgrade is enabled by creating a
new Rational product release area. In this case, the Rational administrator
can create a new release area on the server and create new software
packages as described in this paper to distribute the new version of the
product.
In some cases, Rational software can be updated by replacing just a few files.
If so, Rational will provide a mechanism to update an existing release area.
Installing the upgrade to the user’s systems will be handled differently if you
are using built or non-built software packages.
For non-built software packages, the updated files will be included
automatically in the next distribution that occurs after having updated the
release area. This is because the non-built packages include only references
to files, not the files themselves.
For built packages, the packages will have to be rebuilt in order to include the
latest versions of the files from the release area.

There are some things to consider when planning how to handle an upgrade.

If you want to keep all users at the same level of Rational products, you should
redistribute the product to all users after updating the release areas, software
packages, or both. By using the non-built format, you increase the risk that some
users might get a distribution that has a different set of files than other users.

You can also take advantage of the software signature capability of Tivoli
Configuration Manager Inventory to help track and report what Rational product
versions are installed on users’ systems.


A

Appendix A. Tivoli Configuration
Manager environment
installation
This appendix describes the Tivoli environment we used when testing the
procedures that are documented in this book and provides step-by-step
instructions for installing the various Tivoli components.


General components
Our environment consisted of a single Tivoli management region (TMR) server.
That same system also was configured as a Tivoli management gateway.

TMR server components
The following components are prerequisites to the Tivoli Configuration Manager
4.2.3 application installation. These components are all provided on the
framework 4.1.1 CDs 1 and 2.
Tivoli Management Framework 4.1.1
Tivoli Framework Patch 4.1.1-LCF-0008 or above
Tivoli Java Client Framework 4.1.1
Java 1.3 for Tivoli
JavaHelp™ 1.0 for Tivoli
Tivoli Java RDBMS Interface Module (JRIM) 4.1.1
Tivoli Java Client Framework 4.1.1 Patch JCF411-0003
Tivoli Desktop For Windows 4.1.1

TMR server and gateway configuration
In addition to the above, the following Tivoli Configuration Manager components
were also installed on the TMR server and gateway.
Activity Planner, Version 4.2.3,
Scalable Collection Service, Version 4.2.3
Inventory, Version 4.2.3
Inventory Gateway, Version 4.2.3
Software Distribution Software Package Editor, Version 4.2.3
Software Distribution, Version 4.2.3

Endpoint configuration
Tivoli endpoints typically only require the endpoint agent (and appropriate
patches) to be installed. In our case, one of our endpoints was also used to
create the software packages to distribute Rational products. This requires the
Endpoint Software Package Editor as listed below.
Tivoli Framework Patch 4.1.1-LCF-0008 or above
Endpoint Software Package Editor, Version 4.2.3


Installation overview
To install the Tivoli environment, we installed the components in the following
recommended order, as described in detail in this appendix:
1. RDBMS (this can be a non-Tivoli environment system)
For this example we use DB/2.
2. Tivoli Management Framework server and components
3. Tivoli gateway and components
4. Tivoli endpoint client and Endpoint Software Package Editor

The following documents also provide useful information related to Tivoli
Management Framework installation and deployment:
Tivoli Framework Planning for Deployment Guide, GC32-0393
Explains how to plan for deploying your Tivoli environment and describes
Tivoli Management Framework and its services.
Tivoli Framework User’s Guide, GC31-8433
Describes the concepts and procedures for using Tivoli Management
Framework services. Provides instructions for performing tasks from the Tivoli
desktop and from the command line.
Tivoli Enterprise Installation Guide, GC32-0395
Explains how to install and upgrade Tivoli Enterprise™ software within your
Tivoli management region using the available installation mechanisms
provided by Tivoli.

Installing DB2 UDB Enterprise Server Edition
The first step in a new installation is to install a supported relational database
product. We chose to use the IBM DB2 Universal Database™ (UDB) product.
The database is used to store the Inventory and other databases used by
Configuration Manager 4.2.3. Customers are now licensed to use DB®2 as their
inventory database at no extra charge by virtue of being licensed for
Configuration Manager 4.2.3.

If DB2 UDB V8.1 is to be used with Configuration Manager, it must be at Fixpack
6 or higher (as of the time this paper was written). We use this version of DB2
UDB for this paper. We first install the base DB2 UDB, then install the fix pack.
1. Insert the DB2 UDB installation CD, or browse to the DB2 install image
directory, and execute the setup.exe executable. After unpacking the
contents, you should see the window in Figure A-1 on page 74. Click Install
Products.

Appendix A. Tivoli Configuration Manager environment installation 73

Figure A-1 Installation of DB2 UDB

2. The following window appears. Make sure that DB2 UDB Enterprise Server
Edition is selected, and click Next to continue.

Figure A-2 DB2 product selection panel


3. The wizard welcome window appears. Click Next.

Figure A-3 DB2 setup wizard welcome

4. Select I accept the terms in the license agreement, and click Next.

Figure A-4 Terms and conditions window


5. Under Additional functions, select Satellite administration capability. Click
Next to accept a Typical install and continue.

Figure A-5 DB2 installation type selection

6. Click OK to the warning shown in Figure A-6.

Figure A-6 DB2 APPC warning panel


7. On the Select the installation action window, click Next.

Figure A-7 Select installation action

8. In the Select installation folder window, we have changed the default install
location, taking it out from under the Program Files directory. (This is a
personal preference.) Click Next to continue.

Figure A-8 Select installation folder


9. Supply and confirm the password you would like to use for the db2admin user
ID. In our example, we use the password smartway. Click Next to continue.

Figure A-9 DB2 administrator information panel

10.We will not bother with e-mail notification in this example, so just click Next to
continue, then click OK to acknowledge the warning that follows.

Figure A-10 Administrator contact information


11.Click Next to create the DB2 instance and continue.

Figure A-11 DB2 instance creation

12.Click Next to continue.

Figure A-12 Instance configuration


13.Select Do not prepare the DB2 tools catalog on this computer, and click
Next.

Figure A-13 Tools catalog creation

14.We defer the identification of a contact person, and click Next to continue.

Figure A-14 Health monitor notification


15.The confirmation window in Figure A-15 appears. Click Install to begin the
installation.

Figure A-15 Installation confirmation window

16.A status window shows the progress of the installation. At the end of the
installation, the window in Figure A-16 appears. Click Finish.

Figure A-16 Setup complete panel


17.Click the Exit First Steps option on the left.

Figure A-17 Installation success panel

Installing Fixpack 6
We now install Fixpack 6 for DB2 UDB V8.1.
1. Start a DB2 command window by selecting Start → Programs → IBM
DB2 → Command Line Tools → Command Window. In the window that
appears, issue the following commands.
db2admin stop
db2stop
2. Open your Windows Services window, and stop all DB2-related services.
3. In the directory for DB2 8.1 Fixpack 6, run the fix pack executable
DB2_8.1_FP6_WR21340_ESE.exe.


4. After the contents are extracted, the window in Figure A-18 appears. Click the
Install Product option on the left side.

Figure A-18 DB2 patch installation

5. The product selection window appears. Click Next to continue.

Figure A-19 Product selection


6. At the InstallShield wizard window, click Next to continue.

Figure A-20 Installation wizard

7. A status window shows the progress of the installation.
When the installation is finished, the setup completion window appears. Click
Finish.

Figure A-21 Setup complete


8. At the congratulatory window, click Exit First Steps.

Figure A-22 Patch installation complete

Creating the Configuration Manager database
The next step is to create a database to be used by MDIST2, Inventory, Activity
Planner, Change Manager, and the Pristine Manager feature. Our database user
for this task is db2admin and password is smartway. For this example, we create a
single database called cm_db to contain all of these tablespaces. This is the
database name expected by the Typical installation of Configuration Manager
4.2.3 that we will perform later.

For DB2 only, it is required that the cm_db database exist before the
Configuration Manager installation wizard is run. For other RDBMS products, the
installation routine creates the database automatically. This is documented in the
IBM Tivoli Configuration Manager: Planning and Installation Guide, GC23-4702.

We use the DB2 Control Center to create our database:
1. From your Windows Start menu, select Start → Programs → IBM DB2 →
General Administration Tools → Control Center. This opens the window in
Figure A-23 on page 86.


Figure A-23 DB2 Control Center

2. In the left pane, expand the options until you reach Databases, as shown in
Figure A-24. Right-click Databases and, from the context menu, select
Create → Database Using Wizard.

Figure A-24 Navigating to databases


3. The window in Figure A-25 appears. Enter CM_DB for the Database name, and
click Finish. You do not need any further customization. Watch the DB2 gears
go around as DB2 times itself creating your database.

Figure A-25 Database creation wizard

4. When the database is created, a success window appears. For this
demonstration database we do not need to worry about tuning, so click No.

Figure A-26 Database creation completion message

5. The CM_DB database should now appear in your Control Center window. You
can close the Control Center window and proceed to the next step.


Create a RIM user ID
Tivoli software accesses relational databases through a module called Relational
Database Interface Module (RIM). We now create a user ID that will be used by
the RIM function to access the database:
1. We define the RIM user ID cm_user to Windows. The Typical installation path
for Configuration Manager 4.2.3, which we will follow, allows for the use of a
single RIM user ID for all database tables.
From your Windows Start menu, select, Start → Programs →
Administrative Tools → Computer Management.
2. The window in Figure A-27 appears. In the left pane, expand Local Users
and Groups, right-click Users, and select New User.

Figure A-27 Computer management facility


3. In the New User window, fill in the user ID and password fields:
User name cm_user
Password tivoli
Also, click to de-select the option User must change password at next
logon, and click to select the option Password never expires.

Figure A-28 Defining a new user


4. Figure A-29 shows the options set correctly for the cm_user user ID. Click
Create to create the user ID, then click Close.

Figure A-29 Setting the user ID and password

Your Computer Management window should now show the new user ID. You can
close the Computer Management window.

Figure A-30 Verifying user ID has been created


Installing IBM Tivoli Configuration Manager 4.2.3

Note: We assume that the Tivoli Framework has already been installed. It is a
prerequisite for the IBM Tivoli Configuration Manager. It is beyond the scope of
this paper to describe the installation of the Tivoli Framework.

1. Browse to the root directory of your Configuration Manager 4.2.3 Installation
CD image, and execute setup.exe. The window in Figure A-31 appears.
Accept English as your language, and click OK to continue.

Figure A-31 IBM Tivoli Configuration Manager installation

2. The introduction window appears. Click Next to continue.

Figure A-32 Introduction window


3. The license agreement appears. Click I accept the terms in the license
agreement, and click Next to continue.

Figure A-33 Terms and conditions

4. In this example, we change the destination directory to C:Tivoli as shown
above, and click Next to continue.

Figure A-34 Destination directory


5. Accept the Typical installation and click Next to continue.

Figure A-35 Choosing installation type

6. Here we need to change the default setting for the Database client interface
home field to match our installation of DB2, and click Next to continue.

Figure A-36 Selecting database manager to use


7. In our example, we enter tivoli as both the RIM password and the Database
administrator password fields. Note that the RIM user name used by default is
cm_user. Click Next to continue.

Figure A-37 Setting database access information

8. Review the installation settings and click Next to continue.

Figure A-38 Verify installation options


9. The installation routine prompts for the location of the installation media. Use
the browse buttons at the top of the window to select the parent directory of
your installation CD image directories. Click Open.

Figure A-39 Browse for installation media

10.The installation steps proceed. After some time, a success window appears.
Click Next to continue.

Figure A-40 Successful installation message


11.Save any work you have open, and click Finish to reboot your system and
continue the installation.

Figure A-41 Reboot prompt

12.After your system reboots and you have logged back in as administrator, the
installation continues with the window in Figure A-42. Accept English as your
language and click OK to continue.

Figure A-42 Restart of installation process


13.At the end of a successful installation, the summary window is displayed.
Click Finish.

Figure A-43 Installation complete

General procedure for dealing with installation failures
This paper shows a successful installation of the product, but you might
encounter failures during your installation. Configuration Manager has a very
nice installation step management interface that becomes visible if you have a
failure. Depending on the problem, you might be able to correct the problem and
continue the installation. The following general examples show some of the
windows you will work with if this happens.
1. If you have a failure in your installation, the window in Figure A-44 on page 98
is displayed. Click Next to continue.


Figure A-44 Installation failure message

2. The next window shows you the installation steps that have succeeded, and
what step has failed. In this example, it is the step of registering the Activity
Planner plug-ins. Double-click the line showing an Error status.

Figure A-45 Installation step listing

3. This takes you to another window, where you can see the command that has
failed, the parameters that were used, and an output tab that shows detailed
log information about the failure. Sometimes this information allows you to


change something and try the step again. If so, back on the window in
Figure A-45 on page 98, you can change the status of the step from Error to
Ready, using the drop-down menu below the list of steps.
4. When you have done this, you can click either Run Next or Run All on the
right to see whether you have fixed the problem. If not, you can try again. In
some cases, if you think you can fix the problem later after completing the
installation, you can put the step into a Held status, and continue with the rest
of the installation. Afterward, you can re-run the installation to do “held” steps.

Creating a Tivoli command prompt window shortcut
Now that you have installed the Tivoli Management Framework and Tivoli
Configuration Manager, it is handy to have a shortcut for a Windows command
window that is already sourced with the Tivoli environment variables. This
enables you to quickly run Tivoli command line interface commands.
1. Right-click anywhere on the background of your Windows desktop, and select
New → Shortcut.
2. The Create Shortcut window appears. Click Browse to navigate to
C:WINNTsystem32CMD.EXE and click OK.

Figure A-46 Create shortcut

3. Your window should now look like Figure A-47. Click the command line right
after CMD.EXE and add the following command option to the end of the line:
/k C:WINNTsystem32driversetcTivolisetup_env.cmd
Click Next.


Figure A-47 Create Shortcut window with entries

4. Enter a meaningful name such as Tivoli Command Prompt, then click Finish.
Your new Tivoli Command Prompt shortcut will appear on your desktop.

Figure A-48 Naming the Tivoli command prompt

Installing the Tivoli Endpoint Agent
We now have a TMR server and gateway on our demo machine, along with the
server and gateway functions of the Configuration Manager components. To be
able to perform a fully self-contained demo, we need to install the Tivoli Endpoint
Agent so we can perform inventory scans and software distributions to the same


machine. In our example, we are using a Windows 2000 Server system, so we
install that version of the Tivoli agent.
1. Browse to the CD image for Tivoli Management Framework 2 of 2. On that CD
image, browse to the LCFWINNT subdirectory, and run the setup.exe file
there.
2. The welcome window appears. Click Next to continue.

Figure A-49 Tivoli endpoint installation


3. Click Yes to accept the license agreement and continue.

Figure A-50 Endpoint license agreement

4. On the Accounts and File Permissions window, click Next to continue.

Figure A-51 Accounts and file permissions


5. In our example, we used the Browse button to select C:Tivolilcf as our
destination folder. Click Next to continue.

Figure A-52 Endpoint destination folder

6. The ID and password entered here will be used by the Tivoli endpoint agent to
gain access to any shared file systems that it might need to access. You
would not do this in a production environment. However, in our demo
environment, to ensure that we always have the access permissions we
require, we use the Administrator user ID shown here. Enter Administrator
as the user and smartway as the password. Click Next to continue.

Figure A-53 User and password for remote access from Tivoli endpoint


7. In this self-contained example, the endpoint agent on this machine will always
use the Tivoli gateway on the same machine. Also, we are using the default
Tivoli ports for access. In the Options field, fill in -g cm423server+9494, or
substitute the name of your machine. The other options that are configured
are -D address_notif_interval=300. (This is useful in DHCP environments:
The endpoint informs the gateway of its IP address every 300 seconds.) Click
Next to continue.

Figure A-54 Port settings for the Tivoli endpoint agent

Note: Another useful option to use for endpoints, like this one where there is
an endpoint on the same machine as a gateway, is -D start_delay. This
option makes sure that the gateway is up and running before the endpoint
starts by delaying the start of the endpoint. However, I've found in my testing
that it does not work to include this option in this panel, because the delay
causes the initial endpoint connection to time out, and therefore causes the
endpoint installation to fail. When the endpoint is installed and running
correctly, this option can be added to the last.cfg file, so it can be activated the
next time the endpoint starts up.

8. Review the information (Figure A-55 on page 105) and click Next to continue.
The Tivoli endpoint agent will be installed and configured, and the endpoint
will attempt to log in to the Tivoli gateway.


Figure A-55 Installation progress

9. If all is successful, you will see the window in Figure A-56. Click Next to
continue.

Figure A-56 Successful installation of Tivoli endpoint


10.Click Finish to complete the installation.

Figure A-57 Endpoint setup is complete

Installing the CM 4.2.3 Windows Desktop
The Windows Desktop console provides automatic login to the Java interfaces for
Inventory, MDIST2, Activity Planner, and Change Manager, and enables you to
install the endpoint Software Package Editor in an InstallShield mode.
1. Browse to the Configuration Manager 4.2.3 Desktop CD image and execute
the setup.exe in its root directory.
2. In the window that appears, accept English as the language and click OK to
continue.

Figure A-58 Language selection


3. Click Next to continue.

Figure A-59 Desktop component installation

4. The License Agreement window appears. Accept the agreement as shown
and click Next to continue.

Figure A-60 License agreement window


5. Click Yes to install the Software Package Editor, then click Next to continue.

Figure A-61 Verification o environment

6. A confirmation window appears (Figure A-62). Click Next to continue.

Figure A-62 Confirmation window


7. When the installation is finished, you should see the window in Figure A-63.
Click Finish.

Figure A-63 Tivoli Configuration Manager desktop installation complete


Related publications

The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this Redpaper.

IBM Redbooks
For information about ordering these publications, see “How to get IBM
Redbooks” on page 112. Note that some of the documents referenced here
might be available only in softcopy.
All About IBM Tivoli Configuration Manager Version 4.2, SG24-6612
Troubleshooting Tivoli Using the Latest Features, SG24-6614

Other publications
These publications are also relevant as further information sources:
IBM Tivoli Configuration Manager Planning and Installation Guide Version
4.2.3, GC23-4702
IBM Tivoli Configuration Manager Reference Manual for Software Distribution
Version 4.2.3, SC23-4712
IBM Tivoli Configuration Manager User's Guide for Software Distribution
Version 4.2.3, SC23-4711
Tivoli Enterprise Installation Guide Version 4.1.1, GC32-0804
Tivoli Framework Maintenance and Troubleshooting Guide Version 4.1.1,
GC32-0807
Tivoli Framework User’s Guide, GC31-8433
Tivoli Framework Planning for Deployment Guide Version 4.1.1, GC32-0803

Online resources
These Web sites and URLs are also relevant as further information sources:
Tivoli Software Information Center
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html


How to get IBM Redbooks
You can search for, view, or download Redbooks, Redpapers, Hints and Tips,
draft publications and Additional materials, as well as order hardcopy Redbooks
or CD-ROMs, at this Web site:
ibm.com/redbooks

Help from IBM
IBM Support and downloads
ibm.com/support

IBM Global Services
ibm.com/services


Index
DB2 UDB Enterprise Server Edition
Symbols installing 73
.sp file 35
DB2 Universal Database 73
.spb package 37
developers.lnk 12
creating 43

A E
e-mail notification 24, 27
Access Manager 7
endpoint agent 72
ActiveX 4
installing 100–104
Activity Plan Monitor 6–7
port settings 104
Activity Planner 6, 8, 72, 85, 106
Endpoint Software Package Editor 8, 72
activity plan 6
Enterprise deployment 15
Activity Plan Editor 6
Enterprise Directory
Activity Plan Monitor 7
Query Facility 8
and Change Manager 7
and software distributions 7
plug-ins 98 F
asset control 5 file server 35–36, 38
asset management 4
H
B HTTPS protocol 7
built format 34
I
C IBM Rational ClearQuest
Change Manager service 7 release area 12
ClearQuestsitedefs.dat 24, 26 IBM Rational License Server 19
cm_db database 85, 87 IBM Rational PurifyPlus
configuration file deployment method selection 15
ClearQuestsitedefs.dat 24 IDEs selection 18
creating 28 installation configuration description 19
duplicating 31 launchpad 16
modifying 25 license server setting 19
saving 30 release area 12
configuration settings Release Area path 20
editing 27 setup 14, 17, 21
Create Profile dialog 56 software license agreement 21
Create Release Area page 20 IBM Rational PurifyPlus for Windows 2
IBM Tivoli Configuration Manager
components and services 4
D Database 85
Data Moving component 8
environment installation 71
DB2 UDB 8.1 Fixpack 6
installation wizard 85
installing 82
installing 8, 91


installing Rational upgrades 68 R
Inventory component 5 Rational application 2
other features and services 6 Rational ClearCase 2
software package formats 34 Rational ClearCase LT 2
winstsp command 64 Rational ClearQuest 2
IBM Tivoli Configuration Manager 4.2.3 Rational product 11, 35, 64, 68, 72
installation path 88 installing 32
installing 91 overview 2
installation command syntax 32 Rational product release area
installation image 37 creating 12
Inventory component 5, 62 Rational ProjectConsole 2
Inventory Gateway 72 Rational Purify for Windows 2
Inventory scan 7–8 Rational PurifyPlus
Inventory Server and Gateway 8 creating software package 39
Inventory signature 48 Rational RequisitePro 2
ITCM Inventory Rational Robot 3–4
software signature capability 69 Rational Rose Enterprise Edition 3
Rational Rose Professional Ada Edition 3
Rational Rose Professional C++ Edition 3
J
Java 1.3 for Tivoli 72 Rational Rose Professional Data Modeler Edition 3
Java RDBMS Interface Module (JRIM) 72 Rational Rose Professional J Edition 3
JavaHelp 1.0 for Tivoli 72 Rational Rose Professional Modeler Edition 3
Rational Rose RealTime 3
Rational Rose Visual Basic Edition 3
M Rational SoDA for Word 3
MATCHED_SWARE table 48, 63 Rational Test Agent 2
configuration repository 48 Rational Test Enablers 4
maximum path length 13 Rational Test Manager 4
MDist2 4 Redbooks Web site 112
status 65–66 Contact us viii
Microsoft Visual Basic 3 release area 11, 35, 37–38, 40–41, 69
Microsoft Visual Studio 18 creating 12
model-driven development 3 network drive 40
multicast distribution 4, 35, 37 standard installation 12
Resource Manager 7
N round-trip engineering 3
not-built format 34–38, 60–63
PurifyPlusSetup software package 61 S
software package 34 Scalable Collection Service 72
Set Subscribers 56
P Setup wizard 12
policy region 52–53, 57 setup.exe 12–13, 32, 73, 91, 101, 106
Current Resources 57 shortcut
Pristine Manager 8 creating 99
profile manager 7, 52–58, 60, 62 signature 62
PurifyPlusSetup sitedefs.dat 12
importing in built format 62 siteprep.exe modify wizard 27
importing in not-built format 61 SoDA 3


software distribution 4, 6–8 enterprise directories 8
Software Distribution component 4, 7–8, 52, 62–63 importing a software package 59
integrating with Inventory 48 installing 73
log 67 Tivoli Framework Patch 4.1.1 72
message ID 66 Tivoli Java Client Framework 72
on source host 61 Tivoli Management Framework 7, 52, 73
profile 52 4.1.1 72
Software Distribution Reference Manual 34 Deployment Guide 73
Software Distribution Software Package Editor 72 installation 73
software package 38, 49, 57 service 73
and multicasting 5 User’s Guide 73, 111
block 34–35, 37–38, 44, 48, 62 Tivoli management region (TMR) 7, 72, 100
block (built) format 46 Tivoli tasks 6
creating 39–42 TMR Server Component 72
creating profile 56
definition file 34, 62
distributing 53
U
UDP broadcast 4
file 34–35, 42–43, 60
UML 3
format 34
formats 34
importing 52, 60 V
importing existing 60 visual modeling 3
importing into Tivoli environment 59–62
installing 63–65
W
not-built format 35 Web Gateway 7
profile 59 Web Interface 7
PurifyPlusSWD.pm 61 Web UI 7
removing 46 WebSphere technology 7
rolling back installation 65 wmdist command 65
variables in 45 wsetinvswd y command 48, 63
Software Package Editor 42, 72–73 wundosp command 65
creating software packages 34
default format 35
Selector window 43
source host 35, 37, 46, 60–62
current files 35
specified software package block path 62
sp file 34–35, 43
SWARE_SIG table 62

T
target environment 8
TCP connection 4
Tivoli Desktop For Windows 72
Tivoli endpoint 100
installation 101
Tivoli endpoint agent 100, 103–104
Tivoli environment

Index 115

Back cover ®

Deploying Rational
Applications with IBM Tivoli
Configuration Manager Redpaper

Learn how to use This IBM Redpaper provides an overview of the Rational
Tivoli Configuration product installation process, describes how to create IBM INTERNATIONAL
Manager to deploy Tivoli Configuration Manager software packages for the TECHNICAL
Rational products Rational products, and demonstrates how these packages SUPPORT
can be used to distribute Rational products to a large number ORGANIZATION
of systems. The paper can be used as a reference document
Follow step-by-step
to enable clients to perform unattended installations of
examples
Rational products.
BUILDING TECHNICAL
Simplify The installation process applies to a Microsoft INFORMATION BASED ON
management of Windows-based target environment. PRACTICAL EXPERIENCE
Rational Although some information about Tivoli Configuration
environments Manager is provided, this paper assumes that readers are IBM Redbooks are developed by
already familiar with the product. the IBM International Technical
Support Organization. Experts
from IBM, Customers and
Partners from around the world
create timely technical
information based on realistic
scenarios. Specific
recommendations are provided
to help you implement IT
solutions more effectively in
your environment.

For more information:
ibm.com/redbooks

Deploying rational applications with ibm tivoli configuration manager redp4171

More Related Content

What's hot (15)

Similar to Deploying rational applications with ibm tivoli configuration manager redp4171 (20)

More from Banking at Ho Chi Minh city (20)

Recently uploaded (20)

Deploying rational applications with ibm tivoli configuration manager redp4171