Create an SCC Environment

You can use a Microsoft Common Source Code Control (SCC) compatible product as a version control provider for Enterprise Architect. The first step in doing this is for an administrator to install and configure the server and client applications. A number of basic tasks are performed in creating an operational SCC-based environment.

Tasks in Creating an SCC Environment

Task

Detail

See also

Install and configure your chosen version control product

A version control server component is typically installed on a dedicated server machine.  All Enterprise Architect users who require access to version control must be able to connect to the server machine.

After installing the version control software, the administrator should also create version control user IDs for all users who require access to version control.

For further information, consult the product documentation for your particular version control product.

 

System Requirements (list of SCC compatible version control providers)

Create a new SCC project

It is good practice to create a new SCC version control project, or least a new folder within a project, for each Enterprise Architect project being added to version control with SCC.

If you have a single Enterprise Architect project that contains many different models (for example, a DBMS hosted project with multiple model root nodes), you might choose to create a new SCC version control project for each separate model.

For further information, consult the product documentation for your particular version control product.

 

 

Configure your SCC project to support exclusive check-outs for .XML files

The XMI-format files used for the version control of Enterprise Architect packages can not be merged like ordinary text files can. Therefore, Enterprise Architect must enforce serialized editing of its version controlled packages.  As a consequence, it is important that your version control application is configured to use 'exclusive checkouts' for XML files.

 

Version Control Basics

Create a local working copy folder

A working copy folder must exist on each users' machine, for Enterprise Architect to use when exporting and importing the version controlled package files. It is this folder that is specified as the Local Project Path, when defining your Version Control Configurations.

The working copy folder is the 'sandbox' where you modify the controlled files.  The working copy folder is usually associated with a folder that exists within the version control repository.  Your version control product provides some means by which you associate a working copy folder with a repository folder.

For further information, consult the documentation for your particular version control product.

 

Version Control Setup

Notes

When installing the client component software on users' PCs, check that the SCC client is also installed, as it might not be a part of the default installation

Learn more