IBM SC34-4499-03 manual Scope of this documentation

Scope of this documentation

This documentation is intended for users and administrators installing and using the bridge. It is assumed that you familiar with both the VisualAge Smalltalk and TeamConnection products.

The following subsections describe the mechanics of enabling the ENVY/Manager- TeamConnection Bridge for VisualAge Smalltalk Pro (Version 4.0 or later), the process of exporting ENVY components to TeamConnection, and the process of importing these components back into ENVY/Manager. See the VisualAge Generator documentation for tool-speci®c details. TeamConnection information related to change tracking and build processing are addressed in the TeamConnection documentation.

Many terms used by VisualAge Smalltalk and TeamConnection are problematic because the tools may de®ne these terms differently.Release and component are typical examples. To avoid any ambiguity, such terms may preceded by the name of the tool they are applied to, such as TeamConnection release.

Description of the ENVY/Manager-TeamConnection Bridge

Basic functionality

It makes sense to describe the functionality of the bridge from the perspective of a Smalltalk developer, because it is through the Smalltalk image that the user drives the bridge. The bridge is an import/export facility for three types of entities:

vSmalltalk con®guration maps

vSmalltalk applications

vFiles residing on local and networked ®le systems that are accessible through the image

The bridge allows a Smalltalk developer to store any of these entities in a TeamConnection database and retrieve them at a later time. As is the case when exporting to other ENVY/Manager libraries, con®guration maps and applications must be versioned before they can be exported. This enforces the notion that the Smalltalk developer uses the bridge and TeamConnection to maintain baselines rather than for managing work-in-progress.

Developers use ENVY/Manager's ®ne-grained support to facilitate the process of shared development in open editions of components on a daily basis. At appropriate junctures, components are versioned and promoted to TeamConnection, where together with other project elements, they form a baseline across an entire project. The resulting baseline may contain objects such as program elements, ®le, and metadata.

From the perspective of the TeamConnection user or administrator, the bridge allows the Smalltalk image to function as a TeamConnection client, storing and retrieving parts in a TeamConnection family database.

250User's Guide