Create an SCC Environment

Before Enterprise Architect can be used with an SCC version control product, the appropriate software must be installed and configured by an administrator.

The following topics describe some basic tasks that must be completed in order to create an SCC based version control environment that can be used by Enterprise Architect.




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.

Please consult the documentation for your particular version control product.


List of SCC compatible version control providers

Create a new SCC project

It is good practice to create folders in your PC's file system for organizing your files and documents.

Similarly, it is good practice to create a new version control project, or least a new folder within a project, for each new Enterprise Architect project.

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 version control project for each separate model.

Please consult the documentation for your particular version control product.



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

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



Create a local working copy folder

A working copy folder should be created on each users' machine, for Enterprise Architect to use when exporting and importing the version controlled package files.

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.

It is this folder that is specified as the Local Project Path, when defining your Version Control Configurations.

Please consult the documentation for your particular version control product.


Version Control Setup




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

Learn more