Advantages and disadvantages (CM tool integration)
If you are using a CM tool to perform back ups of a Model, there is little affect on the way you use Modeler; however, if you want to use a CM tool to manage your Modeler Models, there are issues that you should consider.
 | Important: Before using the CM tool integration, you should consider using the database-based 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 provides features to support version and access control. If you choose to use your CM tool to store Models, you may not be able to make use of these features. The following tables identifies the advantages and disadvantages of using a CM tool to manage your Model.
Issue | Without CM tool | When stored in CM tool | ||
|---|---|---|---|---|
Version control | Complete Models can be versioned through Model Explorer. | Models and Packages are versioned each time they are checked in to the CM tool.
| ||
Access control | You control access through: • Server setup • Database and Model access permissions set up in Model Explorer. • Package access permissions set up in Modeler. | The primary control of access is through access rights granted in the CM tool. Modeler access permissions are used to allow only single user access or multi-user access, as required.
| ||
Multi-user access | Controlled at item level through transaction locks, and diagram level through diagram locks. | Controlled in the CM tool at Package level through check in and check out operations of Packages. If single user use of Modeler is being used, only one user can change the contents of a Package in Modeler at any given time. If team use of Modeler is being used, access is controlled at item level through transaction locks, and diagram level through diagram locks. | ||
Visibility of Changes | Changes are seen immediately by other users. | Changes are available only after the changed Packages are checked in. Changes are seen by other users only after those users update the changed Packages in their Modeler environment. | ||
Package Reuse | Can reuse a Package by copying it to another Model, but the copied Package is not linked to the original Package and it is not updated when the original Package is changed. | Packages from many CM tool Models can be referenced. If a referenced Package is updated, the updated information is picked up next time a user performs a get latest version or check out operation on the Package in their Modeler environment.
Packages Referencing Packages in Different CM Tool Projects |