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


Deploying rational applications with ibm tivoli configuration manager redp4171

Deploying rational applications with ibm tivoli configuration manager redp4171

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (15)

Semelhante a Deploying rational applications with ibm tivoli configuration manager redp4171

Semelhante a Deploying rational applications with ibm tivoli configuration manager redp4171 (18)

Mais de Banking at Ho Chi Minh city

Mais de Banking at Ho Chi Minh city (20)

Último

Último (20)

Deploying rational applications with ibm tivoli configuration manager redp4171