Introduction to Objecteering CM Synergy
Overview
The Objecteering CM Synergy MDAC, available in the Enterprise Edition of Objecteering, can be used to:
· configure elements of an Objecteering model
· carry out check-out operations for a particular task
· realize check-in tasks and the most frequently used CM Synergy operations
· simplify your work in the domain of configuration management
The functions of this MDAC are accessible from the Objecteering interface.
Functions
Using the Objecteering CM Synergy MDAC, it is possible to:
·
Create and/or
select a default task
·
Check-in and/or
check-out a model element
·
Delete the old version of a checked-out element, and replace it with
its latest version
·
Update the Objecteering model in accordance with the CM Synergy
project
MDAC architecture
The architecture of the Objecteering CM Synergy MDAC is based on the following concepts:
· The Objecteering CM Synergy MDAC supports Objecteering 6.1, and CM Synergy 6.3 and 6.4.
· Objecteering drives configuration management functions handled by CM Synergy. We strongly advise developers using CM Synergy not to carry out configuration operations. The main commands are available from Objecteering. For other commands which are not available from Objecteering, the build manager uses CM Synergy.
· The CM Synergy session is started in a command prompt or in GUI mode with Objecteering.
· Administration operations are handled by CM Synergy (creation of databases, projects, etc.).
· CM Synergy projects in "shared" mode are managed and automatically recognized.
· Each developer has his own Objecteering work database.
The Objecteering CM Synergy MDAC substitutes the Objecteering Multi-user MDAC. Objecteering Multi-User must not be used to carry out usual group-work operations (otherwise, CM Synergy would not be aware of modifications).
The Objecteering CM Synergy MDAC cannot be deployed in a project if another group work or change management MDAC has already been deployed.
Functional limits
The Objecteering CM Synergy MDAC does not handle the following configuration management functions:
· Administration of CM Synergy databases
· Preparation and management of the WorkFlow (Folder, CM Synergy work area, etc).
· Preparation of the Objecteering modeling project data reception structures (creation of CM Synergy projects, etc .)
· Parallel development and merge of Objecteering objects
· Manual selection of earlier versions of the configuration's objects
These functions are handled through the standard CM Synergy interface.
Bugs and known restrictions
The Objecteering CM Synergy MDAC uses Objecteering Multi-user MDAC functions. This means that Objecteering Multi-User restrictions also apply to the Objecteering CM Synergy MDAC. Please note the following restrictions:
· No consistency checks are carried out on the repository. It is consequently possible to obtain an inconsistent model in the repository by externalizing elements independently from other elements, although each user may have a consistent model in his local database. In order to reduce the risk of obtaining an inconsistent model, we strongly recommend that the "Import from repository" command is regularly carried out on the project, so as to detect possible inconsistencies.
· When the CM Synergy session is started in GUI mode, the CM Synergy windows are hidden by the Objecteering window. The CM Synergy "Properties" and "History" windows activated by the Objecteering CM Synergy MDAC may also appear behind the Objecteering window.
· The Objecteering CM Synergy MDAC will not allow you to check out a new version if a parallel version exists whatever its state ("working", "integrate", …) . Parallel version detection relies on warning messages sent by CM Synergy on check-out. These warnings can be partially disabled by the "parallel_exclude_rules" CM Synergy attribute. If you make any changes to this attribute, it is likely to cause problems such as allowing many users to check-out the same element without mean to merge them.
· The CM Synergy MDAC does not function with CM Synergy projects in "shared" mode whose work area is a local copy on each station, the 'shared' project work area has to be located on a shared network drive that all users must use.
· Personal/insulated CM Synergy projects are not supported anymore.
Connecting to a project in "shared" mode with a work area stored on an NTFS partition
When you connect to a project in "shared" mode with a work area stored on an NTFS partition, CM Synergy modifies the NTFS access rights and the owner of the extracted files, according to the Windows account and not CM Synergy. We strongly recommend, therefore, that you use the same CM Synergy login name as the login name used for the Windows account. If this is not the case, problems caused by CM Synergy can, for example, make it impossible for the real owner to modify an extracted file (a checked-out file). These problems do not arise for work areas stored on FAT-type partitions.
Migrating from an earlier version of CMSynergyModule
In the case of migration from a version of CMSynergyModule earlier than the 5.0.35 version, the teamwork repository must be recreated from an up-to-date project.
The following steps should be carried out:
1. For
each project connected to the repository, run a check-in
on all elements which have been checked-out,
so as to guarantee that the repository contains the latest modifications.
This operation can be launched by running the "Project
check-in" command for each Objecteering model.
2. From one of the projects, run the "Import from repository" command on the root package, in order to have a complete Objecteering model, and then unselect the CMSynergyModule MDAC. Only this Objecteering model will be used to recreate the repository. You must no longer use the other Objecteering models.
3. On the Objecteering model used during phase 2, select the new CMSynergyModule MDAC, and export the project to CM Synergy.
4. A new database should then be created for each user and connected to the CMSynergy shared work area.