IBM SC34-4499-03 User Manual

IBM VisualAge TeamConnection Enterprise Server

User’s Guide

Ve r s i o n 3 .0

IBM

SC34-4499-03

IBM VisualAge TeamConnection Enterprise Server

User’s Guide

Ve r s i o n 3 .0

IBM

SC34-4499-03

Fourth Edition (March 1998)

Note

Before using this document, read the general information under “Notices” on page xiii.

This edition applies to Version 3.0 of the licensed program IBM TeamConnection and to all subsequent releases and
modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the
product.

Order publications by phone or fax. The IBM Software Manufacturing Company takes publication orders between 8:30
a.m. and 7:00 p.m. eastern standard time (EST). The phone number is [phone]. The fax number is (800)
284-4721.

You can also order publications through your IBM representative or the IBM branch office serving your locality.
Publications are not stocked at the address below.

A form for comments appears at the back of this publication. If the form has been removed, address your comments
to:

IBM Corporation
Attn: Information Development
Department T99B/Building 062
P.O. Box 12195

Research Triangle Park, NC, USA 27709-2195
You can fax comments to [phone].
If you have comments about the product, address them to:

IBM Corporation

Attn: Department TH0/Building 062

P.O. Box 12195

Research Triangle Park, NC, USA 27709-2195
You can fax comments to [phone].
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way

it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 1992, 1995, 1996, 1997, 1998. All rights reserved.

Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is
subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Figures.......................... xi

Notices..........................xiii

Trademarks ........................ xv

About this book.......................xvii

How this book is organized ...................xvii

Conventions ........................xvii

Tell us what you think .....................xviii

Part 1. Introducing TeamConnection .................. 1

Chapter 1. An introduction to TeamConnection............ 3

TeamConnection definitions ................... 4

TeamConnection’s client/server architecture ............. 4

TeamConnection database .................. 5

Interfaces ........................ 5

Families......................... 6

Users and host lists..................... 6

Parts.......................... 6

Components ....................... 7

Releases ........................ 8

Work areas ....................... 8

Drivers ......................... 9

Defects and features ....................10

Processes ........................10

Build..........................11

Packaging ........................12

Roles people play ......................12

Part 2. Developing a product using TeamConnection ...........15

Chapter 2. Getting familiar with the TeamConnection client interfaces ...17

Using the GUI........................17

Starting the GUI ......................18

Stopping the GUI .....................19

Performing tasks with the GUI .................19

Using the Settings notebook ..................20

Online help information....................21

Using the command line interface .................21

Using the TeamConnection web client................22

Chapter 3. The basics of using TeamConnection ...........25

Laying the groundwork.....................25

© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 iii

Authority to perform tasks...................26

Finding objects within TeamConnection ...............27

Finding parts .......................27

Using work areas ......................28

Naming your work areas ...................29

Creating parts........................29

Naming your parts .....................30

Preparing to build your parts ..................30

Working with parts ......................31

Working in serial or concurrent development mode ..........31

Working with common parts ..................32

Getting parts from TeamConnection ...............33

Checking parts in to TeamConnection...............34

Finding different versions of TeamConnection objects ..........35

Versioning releases .....................35

Versioning work areas ....................36

Versioning drivers .....................37

Versioning parts ......................38

Working with defects and features .................38

Testing and verifying part changes .................39

Chapter 4. The states of TeamConnection objects...........41

Defects and features .....................41

The states of work areas ....................45

The states of drivers .....................47

Verification and test records ...................49

iv User’s Guide

Chapter 5. Working with no component or release processes ......51

Working in serial development ..................51

Accepting a defect .....................52

Creating a work area ....................53

Checking out a part .....................54

Searching for a part.....................55

Checking in a part .....................58

Verifying and testing part updates ................60

Freezing the work area....................65

Refreshing the work area ...................66

Building the application ...................67

Integrating the work area ...................68

Closing a defect ......................69

Working in concurrent development ................70

Refreshing the work area from the driver..............71

Integrating the work area ...................72

Reconciling differences....................73

Chapter 6. Working with component and release processes .......77

Moving through design, size, and review ...............78

Changing defect ownership ...................79

Accepting a defect ......................80

Approving the fix.......................81

Checking out a part ......................82

Checking in the changes ....................83

Freezing the work area....................85

Building the application ...................86

Accepting fix records .....................87

Integrating changed parts into a release ...............88

Adding a driver member ...................88

Reconciling the differences ..................89

Refreshing the driver ....................91

Building the driver .....................92

Restricting the driver ....................93

Integrating the parts.....................94

Completing the driver ....................95

Testing the built application ..................96

Using a configured process ...................97

Retrieving a past version of a part .................97

Part 3. Using TeamConnection Notes Integrated Databases ........101

Chapter 7. Introduction to TeamConnection Integrated Notes Databases 103

Getting started .......................103

Prerequisites and dependencies .................104

Using TeamConnection with Lotus Notes...............104

Sources of user information ..................104

Database types ......................105

Forms and subforms ....................106

Views.........................107

Reviews ........................109

Document archiving .....................109

Chapter 8. Creating and Maintaining Integrated Notes Databases .....111

Initializing the original template and creating a database..........112

Creating customized production databases ..............116

Performing reconciliation ....................118

Database maintenance: refreshing design from a template .........119

Chapter 9. Database Design Strategies and Advanced Customization ....121

Rules of thumb and general advice.................121

Using the Customization setup facility ................122

Notes Database Customization .................123

Modify TeamConnectionAccess.................124

Reconciliation of Notes and TeamConnection Data ..........124

Advanced customization ....................125

Part 4. Using TeamConnection to build applications............127

Chapter 10. Basic build concepts ................129

Contents v

The physical structure of the build function ..............129

The build object model.....................130

Parent-child relationships in a build tree ...............131

Working with a build tree ....................133

Putting the pieces together ...................135

Chapter 11. Installing, starting, and stopping build servers .......137

Installing the build function ...................137

Creating a build server on MVS .................137

Creating a build server on MVS/OE ...............139

Starting build servers using teamcbld ................140

Starting an MVS build server...................141

Starting the MVS/OE build server .................143

Creating build startup files (for non-MVS environments) ..........144

Stopping the build servers....................145

Stopping an MVS build server ..................145

Chapter 12. Working with build scripts and builders ..........147

Creating a builder ......................147

Writing a build script .....................150

Passing parameters to a build script ...............151

Writing a simple build script ..................153

Writing an executable file for a build script .............153

Testing a build script .....................154

Modifying the contents of a build script ...............155

Putting a builder to work ....................155

Removing a builder from a part ..................156

Working with VisualAge C++ and Templates.............157

vi User’s Guide

Chapter 13. Working with MVS build scripts and builders ........159

Creating a builder for MVS builds .................159

Writing an MVS build script ...................163

File name conversions for MVS .................164

Passing parameters to an MVS build script .............164

TeamConnection syntax for MVS build scripts ............165

Supported JCL syntax ....................166

Example of a build script for a C compile..............168

Example of a build script for a COBOL compile ...........170

Example of a build script for a link ................171

Chapter 14. Working with parsers ................175

Creating a parser ......................175

Writing a parser command file ..................177

Putting a parser to work ....................178

Removing a parser from a part ..................179

Chapter 15. Building an application: an example ...........181

Starting the build servers ....................183

Creating builders and parsers ..................184

Creating the build tree for the application...............184

Starting the build on the client ..................189

Putting the build scripts to work ..................191

Finishing the job and reporting the results to the user ..........192

Monitoring the progress of a build .................192

Running a build in spite of errors .................193

Building all parts, regardless of build times ..............193

Finding out which parts will be built ................194

Canceling a build ......................194

More sample build trees ....................195

Defining multiple outputs from a single build event ..........195

Synchronizing the build of unrelated parts.............196

Part 5. Using TeamConnection to package products............199

Chapter 16. Using TeamConnection to package a product ........201

Setting up your build tree for packaging ...............202

Setting up a build tree for the gather tool..............202

Chapter 17. Using the Gather tool ................205

Using the teamcpak command for the Gather tool............205

Command line flags.....................206

Examples of the teamcpak gather command ............208

Writing a package file for the Gather tool...............208

Syntax rules for a Gather package file...............208

Chapter 18. Using the Tivoli Software Distribution packaging tool .....215

Using the teamcpak command with Tivoli Software Distribution .......215

Command line flags.....................216

Example of the teamcpak softdist command.............217

Writing a package file for Tivoli Software Distribution ...........217

Syntax rules for a Tivoli Software Distribution package file ........217

Keywords for a Tivoli Software Distribution package file .........218

Problem determination for the Tivoli Software Distribution tool ........220

Sample package file .....................221

Part 6. Appendixes ..........................225

Appendix A. Environment Variables................227

Setting environment variables ..................234

Appendix B. Importing makefile information into TeamConnection .....235

Creating a rules file ......................237

Appendix C. TeamConnection Merge ...............239

Appendix D. Enabling an OS/2 Workframe project for TeamConnection 241

Creating a TeamConnection-enabled Workframe project..........241

Contents vii

Setting up your project options ..................241

Using your TeamConnection Workframe project ............242

Project actions ......................242

Part actions.......................243

Using your project: a simple scenario ................244

Appendix E. Enabling a Workframe/NT project for TeamConnection ....245

Setting up your project options: ..................245

Using your TeamConnection WorkFrame project ............246

Project actions .......................246

Part actions........................247

Appendix F. Enabling and Using the ENVY/Manager-TeamConnection Bridge 249

Overview of the ENVY/Manager-TeamConnection Bridge .........249

Scope of this documentation ..................250

Description of the ENVY/Manager-TeamConnection Bridge........250

Preparing to use the ENVY/Manager-TeamConnection Bridge ........251

Setting up the bridge environment ................252

Installing and activating the ENVY/Manager-TeamConnection Bridge ....253

Using the ENVY/Manager-TeamConnection Bridge ...........255

Setting default properties ...................255

Exporting ENVY components to TeamConnection ...........258

Importing ENVY components from TeamConnection ..........260

Using the ENVY/Manager-TeamConnection Bridge: a simple scenario for

VisualAge Generator developers.................261

Scenario assumptions ....................261

Exporting ENVY components to TeamConnection ...........262

Object mapping in TeamConnection ...............263

Build generation ......................263

Making a change to a member .................265

viii User’s Guide

Appendix G. Source Code Control User’s Guide ...........267

Differences between other source code control providers and TeamConnection . . 267

Projects vs Families.....................267

Installing the TeamConnection source code control DLL .........268

Connecting TeamConnection to an IDE ...............269

Removing the TeamConnection Source Code Control DLL ........269

Using TeamConnection as your source code control provider ........269

Before you start ......................269

Opening a project .....................270

Integrated features .....................270

Full features of TeamConnection ................271

Appendix H. Supported expandable keywords ............275

Appendix I. Authority and notification for TeamConnection actions ....277

Appendix J. Sample REXX execs, build scripts, and parsers .......301

Sample REXX execs .....................301

Sample build scripts......................305

Sample parsers .......................306

Sample package files .....................306

Customer support ......................307

Bibliography ........................309

IBM VisualAge TeamConnection Enterprise Server library .........309

TeamConnection technical reports .................310

DB2...........................310

Related publications .....................311

Glossary .........................313

Index ..........................323

Readers’ Comments — We’d Like to Hear from You ..........333

Contents ix

x User’s Guide

Figures

1. A sample TeamConnection client/server network .......... 5

2. Sample of a component hierarchy ............... 7

3. Parts, releases, and components................ 8

4. Tasks window ......................18

5. Components window ....................26

6. Accept Defects window ...................53

7. Create Work Areas window .................54

8. Check Out Parts window ..................55

9. Part Filter window.....................56

10. Edit Task List window ...................57

11. Check In Parts window ...................59

12. Build Parts window ....................61

13. Extract Parts window....................62

14. Check Out Parts .....................63

15. Check In Parts window ...................64

16. Freeze Work Areas window .................65

17. Refresh Work Areas window .................67

18. Build Parts window ....................68

19. Integrate Work Areas window .................69

20. Verify Defects window ...................70

21. Refresh Work Areas window .................71

22. Integrate Work Areas window .................73

23. Reconcile Collision Record window ...............75

24. Modify Defect Owner window .................79

25. Accept Defects window ...................80

26. Accept Approval Records window ...............82

27. Check Out Parts window ..................83

28. Check In Parts window ...................84

29. Freeze Work Areas window .................85

30. Build Parts window ....................86

31. Complete Fix Records window ................87

32. Add Driver Members window .................88

33. Fix Work Areas window ...................89

34. Activate Fix Records window .................90

35. Refresh Work Areas window .................91

36. Refresh Drivers window...................92

37. Build Parts window ....................93

38. Restrict Drivers window ...................94

39. Commit Drivers window ...................94

40. Complete Drivers window ..................95

41. Accept Test Records window .................96

42. Notes Integrated Database Creation and Staging ..........112

43. The physical structure of TeamConnection ............129

44. Sample build object model for msgcat.exe.............133

45. The build tree for the hello application ..............134

46. Two versions of a build tree .................135

© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 xi

47. TeamConnection components on separate machines .........137

48. Create Builder window ...................148

49. Modify Part Properties window ................156

50. Modify Part Properties window ................157

51. Create Builder window ...................160

52. A JCL fragment for an MVS compile ..............168

53. A JCL fragment converted to a build script ............170

54. Create Parser window ...................176

55. Modify Part Properties window ................178

56. Modify Part Properties window ................180

57. Sample build tree .....................182

58. Sample build object model for msgcat.exe.............183

59. Create Parts window....................185

60. Create Parts window....................186

61. Modify Part Properties window ................187

62. Connect Parts window ...................188

63. The build tree display ...................189

64. Build Parts window ....................190

65. The build tree for robot.dll ..................195

66. The build tree for robot.app .................196

67. Part of the build tree for robot.app ...............202

68. Adding the gather step to the build tree .............204

xii User’s Guide

Notices

References in this publication to IBM products, programs, or services do not imply that
IBM intends to make these available in all countries in which IBM operates. 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. Subject to IBM’s valid
intellectual property or other legally protectable rights, any functionally equivalent
product, program, or service may be used instead of the IBM product, program, or
service. The evaluation and verification of operation in conjunction with other products,
except those expressly designated by IBM, are the responsibility of the user.

IBM may have patents or pending patent applications covering subject matter 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 the IBM Director of Licensing, IBM
Corporation, 500 Columbus Avenue, Thornwood, NY, USA 10594.

Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs and
other programs (including this one) and (ii) the mutual use of the information which has
been exchanged, should contact the Site Counsel, IBM Corporation, P.O. Box 12195,
3039 Cornwallis Road, Research Triangle Park, NC 27709-2195, USA. Such
information may be available, subject to appropriate terms and conditions, including in
some cases, payment of a fee.

The licensed program described in this document and all licensed material available for
it are provided by IBM under terms of the IBM Customer Agreement.

This document is not intended for production use and is furnished as is without any
warranty of any kind, and all warranties are hereby disclaimed including the warranties
of merchantability and fitness for a particular purpose.

IBM may change this publication, the product described herein, or both. These changes
will be incorporated in new editions of the publication.

This publication 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 IBM Corp. 1992, 1995, 1996, 1997, 1998 xiii

xiv User’s Guide

Trademarks

The following terms are trademarks of International Business Machines Corporation in
the United States and/or other countries:

AIX® NetView®
C/370™ OpenEdition®
C Set ++® Operating System/2®
DB2® OS/2®
DB2 Universal Database® SOM®
IBM® SOMobjects@tm;
MVS™ TeamConnection™
MVS/ESA™ VisualAge®
MVS/XA™ XGA

ENVY is a registered trademark of Object Technology International, Inc.

Lotus and Lotus Notes are registered trademarks and Domino is a trademark of Lotus
Development Corporation.

Tivoli, Tivoli Management Environment, and TME 10 are trademarks of Tivoli Systems
Inc. in the United States and/or other countries.

The following terms are trademarks of other companies:

HP-UX 9.*, 10.0 and 10.01 for HP 9000 Series 700 and 800 computers are X/Open
Company UNIX 93 branded products. HP-UX 10.10 and 10.20 for HP 9000 Series 700
and 800 computers are X/Open Company UNIX 95 branded products.

UNIX is a registered trademark in the United States and other countries licensed
exclusively through X/Open Company Limited.

Intel and Pentium are registered trademarks of Intel Corporation.

Microsoft, Windows, Windows NT and the Windows logo are registered trademarks of
Microsoft Corporation.

Visual Basic and Visual C++ are trademarks of Microsoft Corporation.

PowerBuilder and Powersoft are registered trademarks of Sybase, Incorporated.

Java, HotJava, Network File System, NFS, Solaris and the Sun logo are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United States and other
countries.

Netscape Navigator is a U.S. trademark of Netscape Communications Corporation.

© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 xv

Adobe, the Adobe logo, Acrobat, the Acrobat logo, Acrobat Reader, and PostScript are
trademarks of Adobe Systems Incorporated.

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

xvi User’s Guide

About this book

This book is part of the documentation library supporting the IBM TeamConnection
licensed programs. It is a guide for client users.

For additional information when performing TeamConnection tasks, refer to the

Commands Reference

graphical user interface (GUI).

when entering commands or online help when using the

Getting Started with the TeamConnection Clients

client user.

This book is available in PDF format. Because production time for printed manuals is
longer than production time for PDF files, the PDF files may contain more up-to-date
information. The PDF files are located in directory path nls\doc\enu (Intel) or
softpubs/en_US (UNIX). To view these files, you need a PDF reader such as Acrobat.

How this book is organized

“Part 1. Introducing TeamConnection” on page 1, gives all users an overview of the
concepts of TeamConnection and introduces the terminology that is used throughout
this book.

“Part 2. Developing a product using TeamConnection” on page 15, describes the
different interfaces and basic TeamConnection tasks. It uses scenarios to explain
how to do many tasks.

This part is for everyone using TeamConnection to do daily work. The information is
meant for both the person who uses the command line interface and the person
who uses the GUI, as instructions for both are provided.

“Part 4. Using TeamConnection to build applications” on page 127, tells how to use
the TeamConnection build function. For information in installing and administering
the build function, refer to the

“Part 5. Using TeamConnection to package products” on page 199, tells how
TeamConnection helps you automate the packaging and distribution of your
application.

“Part 6. Appendixes” on page 225, contains various pieces of information that you
can refer to as you plan for and use TeamConnection.

Information on customer service, a bibliography, and a glossary are included at the
back of this book.

contains basic information for the

Administrator’s Guide

Conventions

This book uses the following highlighting conventions:

© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 xvii

v

Italics

are used to indicate the first occurrence of a word or phrase that is defined in

the glossary. They are also used for information that you must replace.

v Bold is used to indicate items on the GUI.
v Monospace font is used to indicate exactly how you type the information.
v File names follow Intel conventions: mydir\myfile.txt. AIX, HP-UX, and Solaris users

should render this file name mydir/myfile.txt.

Tips or platform specific information is marked in this book as follows:

Shortcut techniques and other tips

IBM VisualAge TeamConnection Enterprise Server for OS/2

IBM VisualAge TeamConnection Enterprise Server for Windows/NT

IBM VisualAge TeamConnection Enterprise Server for Windows 95

IBM VisualAge TeamConnection Enterprise Server for AIX

IBM VisualAge TeamConnection Enterprise Server for HP-UX

IBM VisualAge TeamConnection Enterprise Server for Solaris

Tell us what you think

In the back of this book is a comment form. Please take a few moments to tell us what
you think about this book. The only way for us to know if you are satisfied with our
books or if we can improve their quality is through feedback from customers like you.

xviii User’s Guide

Part 1. Introducing TeamConnection

Chapter 1. An introduction to TeamConnection............ 3

TeamConnection definitions ................... 4

TeamConnection’s client/server architecture ............. 4

TeamConnection database .................. 5

Interfaces ........................ 5

Families......................... 6

Users and host lists..................... 6

Parts.......................... 6

Components ....................... 7

Releases ........................ 8

Work areas ....................... 8

Drivers ......................... 9

Defects and features ....................10

Processes ........................10

Build..........................11

Packaging ........................12

Roles people play ......................12

This section presents an overview of the TeamConnection product. The information in
this section should be read and understood by everyone who is going to work with
TeamConnection.

Additional conceptual information is provided in Parts 3, 4, 5, and 6.

© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 1

2 User’s Guide

Chapter 1. An introduction to TeamConnection

TeamConnection provides an environment and tools to make software development run
smoothly, whether your development team is small or large. Using TeamConnection,
you can communicate with and share data among team members to keep up with the
many tasks in the development life cycle, from planning through maintenance.

What does TeamConnection do for you? It takes care of the following:

v

Configuration management

controlling software modules as they change over time. This includes controlling
access to your software modules and providing notification to team members as
software modules change.

v

Release management

application. The release provides a logical view of objects that must be built, tested,
and distributed together. Releases are versioned, built, and packaged.

v

Version control

that make up an application. Version control enables you to build your product using
stable levels of code, even if the code is constantly changing. It provides control over
which changes are available to everyone and, optionally, allows more than one
developer at a time to update a part.

v

Change control

TeamConnection. TeamConnection keeps track of any part changes you make and
the reasons you make them. Your development team can build releases with
accuracy and efficiency, even as the parts evolve. The product ensures that the
change process is followed and that the changes are authorized. After changes are
made, it allows you to integrate the changes and build the application.
TeamConnection tracks all changes to the parts across multiple products and
environments.

The

change control process

change control should be, from loose to very tight. You can also adjust the level of
control as you move through a development cycle.

v

Build support

and then to create it within TeamConnection from your input parts. Independent steps
in a build can run in parallel on different servers, thus reducing your build time. You
can build applications for platforms in addition to the one TeamConnection runs
on—currently, you can use TeamConnection to build applications on AIX, HP-UX,
OS/2, Windows NT, Windows 95, Solaris, MVS, and MVS OpenEdition.

v

Packaging support

other users.

This chapter defines the basic terms and concepts you need to make the most of
TeamConnection. Read this chapter first; then decide which information you need next:

: the tracking of relationships among the versions of the various parts

: the controlling of changes to parts that are stored in

: the function that enables you to define the structure of your application

: the preparation of your application for electronic distribution to

: the process of identifying, organizing, managing, and

: the logical organization of objects that are related to an

is configurable. Your team can decide how strict the

© Copyright IBM Corp. 1992, 1995, 1996, 1997, 1998 3

Topic and description Page

Developing products using TeamConnection:

v Getting familiar with the interfaces
v The basics of using TeamConnection
v More about
v Following TeamConnection processes

defects

and

features

16

Using TeamConnection to build applications:

v Build concepts
v Installing build agents and processors
v Working with build scripts and builders
v Working with
v Building an application

Packaging applications:

v Using the packaging function
v Using the Gather utility
v Using the NVBridge utility

parsers

TeamConnection definitions

The following definitions are in logical order rather than alphabetical. provides additional
information about these terms.

TeamConnection’s client/server architecture

128

“Chapter 16. Using
TeamConnection to
package a product” on
page 201

4 User’s Guide

Figure 1 on page 5 is an example of a network of TeamConnection clients and servers.

Figure 1. A sample TeamConnection client/server network

TeamConnection
Data stored in a family server’s database includes:

v Text objects, such as source code and product documentation
v Binary objects, such as compiled code
v Modeled objects that are stored in the information model by tools such as VisualAge

Generator

v Other TeamConnection objects that are metadata about the other objects
A TeamConnection

and parts stored on the database server.

TeamConnection database

TeamConnection is built on IBM’s DB2 Universal Database. Please refer to the DB2
documentation referenced in this document’s “Bibliography” on page 309 for detailed
information on DB2 database configuration, administration, and utilities.

Interfaces

TeamConnection provides the following interfaces that you can use to access data:

v A graphical user interface based on industry standards.
v A command line interface that lets you type TeamConnection commands from a

prompt or from within TeamConnection

v A web client that you access through your web browser.

family servers

client

gives team members access to the development information

control all data within the TeamConnection environment.

Chapter 1. An introduction to TeamConnection 5

Families

You can use any interface to do your TeamConnection work, or you can switch among
them. This book usually gives instructions for using both interfaces.

For more information, see “Chapter 2. Getting familiar with the TeamConnection client
interfaces” on page 17.

A

family

represents a complete and self-contained collection of TeamConnection users
and development data. Data within a family is completely isolated from data in all other
families. One family cannot share data with another.

Refer to the

Users and host lists

Users are given access to the TeamConnection development data in a specific family
through their
access to the family. The superuser gives other users the
of

actions

might in turn be able to grant some equal or lesser level of authority to other users.
However, the ability to grant authority for some actions is reserved to the superuser.
There are no actions which the superuser cannot perform.

For host-based authentication, each user ID is associated with a
of client machine addresses from which the user can access TeamConnection when
using that ID.

A single user can access TeamConnection from multiple systems or logins. Likewise, a
single system login can act on behalf of multiple users. The set of authorized logins for
a TeamConnection user ID makes up the user’s host list.

It is also possible to authenticate users through the use of passwords, either in place of
host lists, or as an alternative form of authentication.

Refer to the

Parts

Administrator’s Guide

user IDs

on particular data. Depending on the authority granted to a user, that user

. Each family has at least one

Administrator’s Guide

for more information about families.

superuser

, who has privileged

authority

to perform some set

host list

for more information.

, which is a list

6 User’s Guide

TeamConnection
include text objects, binary objects, and modeled objects. These parts can be stored by
the user or the tool, or they can be generated from other parts, such as when a linker
generates an executable file. Parts can also be groupings of other TeamConnection
objects for building and distribution, or simply for convenient reference. Common part
actions include the following:

Create To store a part from your workstation on the server; from that time on,

TeamConnection keeps track of all changes made to the part. Or, to create a
part to use as a place holder to store the output of a build.

parts

are objects that users and tools store in TeamConnection. They

Components

Check out

To get a copy of a part so that you can make changes to it.

Check in

To put the changed part back into TeamConnection.

Extract To get a copy of the part

TeamConnection.

Edit To change a part from within TeamConnection using a specified editor.
Build To construct an output part from parts that you have defined to

TeamConnection as input to the output part.

These are simplified definitions of part actions; there is more about the actions you can
perform against parts in “Chapter 3. The basics of using TeamConnection” on page 25.

The current version of each part is stored in the TeamConnection database, along with
previous versions of each part. You can return to previous versions if you need to.

without

making changes to the

current version

in

Within each family, development data is organized into groups called
component hierarchy of each family includes a single top component, called

descendants

child can have multiple parents.

The following figure depicts a component hierarchy.

Figure 2. Sample of a component hierarchy

TeamConnection uses components to organize development data, control access to the
data, and notify users when certain actions occur. Descendant components inherit
access and notification information from ancestor components. Information about the
components is stored in the database, including:

v The component’s position in its family hierarchy.
v The user who owns the component. The component

managing data related to it, including defects or features.

of that root. Each

child component

has at least one parent component; a

owner

components

root

is responsible for

. The

, and

Chapter 1. An introduction to TeamConnection 7

Releases

v The users who have access to the component and the level of access each user

has. This information makes up the component’s

v The users who are to be notified about changes to the component. This set of users

is called the

process

v The

An application is likely to contain parts from more than one component. Because you
probably want to use some of the same parts in more than one application, or in more
than one version of an application, TeamConnection also groups parts into
release is a logical organization of all parts that are related to an application; that is, all
parts that must be built, tested, and distributed together. Each time a release is
changed, a new version of the release is created. Each version of the release points to
the correct version of each part in the release.

Each part in TeamConnection is managed by at least one component and contained in
at least one release. One release can contain parts from many components; a
component can span several releases. Figure 3 shows the relationships between parts,
the releases that contain them, and the components that manage them.

notification list

by which the component handles defects and features.

.

access list

.

releases

.A

Work areas

8 User’s Guide

Figure 3. Parts, releases, and components

Each time a new development cycle begins, you can define a separate release. Each
subsequent release of an application can share many of the same parts as its
predecessor. Thus maintenance of an older release can progress at the same time as
development of a newer one. Each release follows a process by which defects and
features are handled.

A release contains the latest ″official″ version of each of its parts. As users check parts
out of the releases, update them, and then check them back in, TeamConnection keeps

track of all of these changes, even when more than one user updates the same part at
the same time. To make this possible, TeamConnection uses something called a

area

.

A work area is a logical temporary work space that enables you to isolate your work on
the parts in a release from the official versions of the parts. You can check parts out to
a work area, update them, and build them without affecting the official version of the
parts in the release. After you are certain that your changes work, you
work area with the release (or
you are using the driver subprocess). The integration makes the parts from your work
area the new official parts in the release.

You can do the following with work areas:

v Check out parts from a release
v Update any or all of the checked-out parts
v Get the latest copies of the parts in the release, including any changes integrated by

other users

v Get the latest copies of the parts in another work area
v

Freeze

instant in case you need to return to it later

v Build the parts in the work area
v Move all parts back into the release by integrating the work area

For more information, see “Using work areas” on page 28.

the work area, making a snapshot of the parts as they exist at a particular

commit

the driver that the work area is a member of, if

integrate

work

the

Drivers

A driver is a collector for work areas. You create drivers associated with specific
releases so that you can exercise greater control over which work areas are integrated
into the release and commit the changes from multiple work areas simultaneously.

When a work area is added to a driver, it is called a
can be a member of more than one driver. By making a work area part of a driver, you
associate the parts changed in relation to that work area with the specified driver.
These parts must be members of the release associated with the driver.

Drivers enable you to place the following controls over work area integrations:
v Define and monitor prerequisite and corequisite work areas to ensure that mutually

dependent changes are integrated in proper order.

v Monitor and resolve conflicting changes to the same part (if you use concurrent

development).

v Restrict access to driver members so that they can be changed only by users with

proper authority.

Chapter 1. An introduction to TeamConnection 9

driver member.

A single work area

Defects and features

A defect is a record of a problem to be fixed. A feature is a record of a request for a
functional addition or enhancement. Both may be associated with a work area, and both
follow the processes defined for the component and release that are associated with
the work area. TeamConnection tracks both objects through their life cycles as
developers change and commit parts.

You can use defects and features to record problems and design changes for things
other than the products you are developing under TeamConnection control. For
example, you can use defects to record information about personnel problems,
hardware problems, or process problems. You can use features to record proposals for
process improvements and hardware design changes.

For more information, see “Working with defects and features” on page 38.

Processes

An application changes over time as developers add features or correct defects.
TeamConnection controls these changes according to the
your application’s components and releases. A process enforces a specific level of
control to part changes and ensures that actions occur in a specified order.

Two separate types of processes are defined: component processes, which can be
different for each component within a family, and release processes, which apply to all
activities associated with a given release. Component or release processes are built
from a number of lower-level processes, or
TeamConnection product.

subprocesses

processes

, that are included with the

you choose for

10 User’s Guide

A defect or feature written against a component moves through successive
during its life cycle. The TeamConnection actions that you can perform against it
depend on its current state. The component processes define these actions. You can
require users to do some, all, or none of the following for tracking defects and features:

dsrFeature

Design, size, and review changes to be made for features

verifyFeature

Verify that the features have been implemented correctly

dsrDefect

Design, size, and review fixes to be made for defects

verifyDefect

Verify that the fixes work

At the release level you can require some, all, or none of the following subprocesses:
track This subprocess is TeamConnection’s way of relating all part changes to a

specific defect or feature and a specific release. Each work area gathers all

states