Filter
Top Products
mismatches. If you make a change to an application, it is important to update all the
exported configuration maps that contain the application and to export all of the
configuration maps again.
Note: The Export all required maps too checkbox located on the Export page of the
Default Properties notebook defaults to this behavior.
The following describes two simple cases in which a mismatch might occur:
1. Export a configuration map that contains several applications.
2. Make a change to one of the contained applications.
3. Export the changed application only.
4. Attempt to import the configuration map.
or
1. Export two configuration maps that contain the same application.
2. Make a change to the common application and export only one of the configuration
maps that contains the application.
3. Attempt to import the second configuration map.
As the number of programmers authorized to version components and the complexity of
your applications increase, so does the possibility for these types of problem to occur.
Therefore, it is important to coordinate update authority in such a way that all affected
parties are notified about configuration changes, and that someone in the development
group has authority over all levels of components. It may also be advisable to limit
export actions to higher levels of authority than you have previously.
Exporting components is a substantial operation that typically takes at least ten to
twenty seconds (possibly minutes for a large collection of components). Such an
operation begins with the bridge exporting the components to temporary
ENVY/Manager libraries and then generating detailed descriptions of the library
contents for the benefit of TeamConnection. To guarantee atomicity and minimize the
number of times that the bridge must communicate with TeamConnection (thus avoiding
unnecessary overheads), all components are transferred in one primitive operation.
Even a single configuration map usually counts as more than one component, because
it typically contains at least one release application. Once the primitive operation is
invoked, control of the process is in the TeamConnection client code, which is
effectively blocked against the TeamConnection server. Because the Smalltalk image is
blocked waiting for the primitive to return, the user interface will not update, and the
user cannot halt the operation.
Exporting configuration maps and applications
The process for exporting ENVY-based configuration maps and applications to a
TeamConnection family database includes the following steps:
1. Select Configuration Maps or Applications from the Export cascade menu. You
will be prompted to select an appropriate version of the configuration map or
application that you want to export.
Appendix F. Enabling and Using the ENVY/Manager-TeamConnection Bridge 259