Working with Serena Dimensions (CM tool integration)
CM tool integration support for Serena Dimensions is being deprecated.
The topics that document the CM tool integration in this help are generic using Microsoft Visual SourceSafe terminology. The following notes apply when working with Serena Dimensions.
Serena Dimension clients must have the optional SCC Integration component installed.
To work with Serena Dimensions, you require a Modeler license and a CM Integration license.
Through Dimensions Administration Console you must set up the Dimensions server to work with Modeler. For more information, click here
Before checking in a Model the first time, you must set up the Dimensions server to work with Modeler, and then create a Dimensions Project, Workspace and Part in which to store the Model.
If the check in or check out commands are not available in Modeler, it may be because the lifecycle status of the associated items in Dimensions is preventing them from being checked in or checked out.
If you perform an undo check out operation, the Output pane may record messages similar to the following messages. These messages can be ignored:
Warning: unable to delete "\\SIMONM2\ModelerATF\Models_2\d4b96e5f-7e97-4f98-9359-16aaa1985b70\0\Package1.pkf" file locked by Modeler file will be made read-only
When working with Dimensions, Warning dialogs which include the following text may be displayed:
Warning: The Directory you opened the IDE project <id> does not end with the Dimensions project directory <directory>.
These warnings can be ignored. If you want to prevent Dimensions from showing these warnings:
1. Using a text editor, open the dm.cfg file that resides in the Dimensions CM folder. If you have installed Dimensions 10.1 to the default location, the path of the CM folder is as follows:
◦ For 64-bit versions of Windows—C:\Program Files (x86)\Serena\Dimensions 10.1\CM
◦ For 32-bit versions of Windows—C:\Program Files\Serena\Dimensions 10.1\CM
2. Add a new line and type the following text:
DM_SCC_CONFIRMWARNINGS N
3. Save the changes you have made to the dm.cfg file.
