Overview of configuration management tool integration (CM tool integration)
Modeler can be integrated with leading configuration management tools (CM tools), so that you can store and manage Models in your CM tool environment.
 | Before using the CM tool integration, you should consider using the Modeler Modeler configuration management features, which may provide a better solution for your needs. Modeler configuration management supports branching (sandboxing) for serial development of items. You cannot use the CM tool integration and Modeler configuration management features with the same model, because they are mutually exclusive. For more information about whether to use CM tool integration or Modeler configuration management, see Modeler configuration management or CM tool integration? (Modeler CM). |
Storing a model in a CM tool is particularly useful when working with large models and distributed teams, because the CM tool integration provides more options for access and change control.
For information about different solutions for working across sites, see Working Across Sites.
The CM tool integration makes use of Packages (the Model itself behaves as a package) to transfer information between the CM tool and Modeler environments. The CM tool integration commands you typically use are available on a Package's or Model's context menu.
The CM tool integration uses check out and check in operations to manage the changing of items. If you want to change an item that is stored in a CM tool, you must check out the Package or Model that owns that item, change the item in Modeler, and then check in the owning Package or Model to the CM tool. While a Package is checked out to you, other users cannot check out and change that Package (although other user may be able to change the package in your model). A Package's or Model's icon indicates whether it is checked in or checked out.
| | • You cannot use your CM tool to check out multiple versions of a Package or Model file for parallel development, because Package and Model files cannot be merged. • When making changes, you should check out the required Packages as a set, make the required changes, and then check in those Packages as a set. Working with sets of Packages keeps the CM tool package files in a complete and consistent state. |
When a Model is stored in a CM tool, the Model and Packages files are versioned each time they are checked in, except in the case of Telelogic Synergy™/CM where files are versioned on check out. You can use additional features that your CM tool may support, such as labeling and baselines, to manage the Model and its Packages in your CM tool environment. If a Model is under configuration control, the versioning facilities in Model Explorer are disabled.
You can also use the Modeler automation interface to facilitate check in and check out operations through the Export and Import functions. For more information, see the Modeler Automation Interface Help.
Modeler has been tested with the following CM tools:
• Serena® Version Manager™ - DEPRECATED
• Serena® Dimensions™ - DEPRECATED
• Microsoft® Visual SourceSafe® - DEPRECATED
• Rational® ClearCase® - DEPRECATED
• Telelogic Synergy™/CM - DEPRECATED
For information about which versions of the preceding applications are supported, see “Release Notes”.
The topics that document the CM tool integration in this help are generic, using Microsoft Visual SourceSafe terminology. For notes about working with one of the preceding CM tools, see the following topics:
Modeler integrates with CM Tools through the Microsoft Common Source Code Control (CSCC) Interface standard. If you are using a CM tool not listed and that CM tool complies with the Microsoft CSCC interface standard, your CM tool may work with Modeler. If you cannot integrate with your CM tool through the CSCC interface, you may be able to integrate with your CM tool through the Modeler automation interface.
You can embed external configuration files as OLE objects into Modeler rich text fields, or alternatively you can add OLE links to external configuration files. For more information, see Embedding and linking external configuration files (CM tool integration).