Scope

1. Identification

1.1. Description of the product

Team for Capella is a collaborative solution to have several contributors working on the same model, with the granularity as fine as a model element and diagrams.

It decouples the versioning issue which is ensured by a Source Control Management (SCM) tool from the concurrent accesses issue.

It introduces a shared repository which is populated from the SCM tool and which enables several users to work on the same model.

Users can simultaneously edit the same Capella model without conflicts. Only modified elements are locked, not the whole model, and other users can see in live modifications made by connected teammates. It is no longer necessary to split the model into fragments or to merge concurrent modifications.

It is recommended to version exported models with a SCM tool, for instance Git. Please refer to the Capella embedded documentation at the section Capella Guide > User Manual > Version Control with GIT for more details.

Here is an overview of the Team for Capella architecture:

Team for Capella is composed of three parts:

A server, to manage the model repositories, and associated features (such as locks, etc.);
An administration module, to schedule automatic backups (models, changes and database) and trigger diagnostic and maintenance tasks;
An add-on, packaged as an update site, to bring the multi-user functionalities on top of the standard Capella rich client.

Please refer to the Team for Capella documentation at the section Introduction to Team for Capella > Rationale and Concepts for more information.

Team for Capella is available in 64 bits version for Windows and for Linux.

The Team For Capella server is composed of the CDO repositories server and an HTTP Jetty server.
By default, the Jetty admin server is automatically started with the CDO server on the port 8080.

The REST admin server is used:

to manage repositories with the REST Admin API
by applications (importer, maintenance application, console application) to execute code on server

Please refer to the Team for Capella documentation at the section System Administrator Guide > Server Configuration for more information.

1.2. Deployment modes

Team for Capella can be deployed on different modes:

Cloud: With the Cloud deployment mode, Team for Capella server is installed and administrated by Obeo, and Team for Capella clients are accessible through a remote desktop technology.
On-Premise: With the On-Premise deployment mode, Team for Capella is installed and administrated on the client’s infrastructure. The multiple ways to install/deploy Team for Capella are described in section Installation Architecture.

1.3. Applicability

This guideline is applicable to following versions of Capella and Team for Capella:

Value name

Value

AppChk

[INSTALLDIR]\capella\capella.exe;

Product Name

Capella x64 / Team for Capella x64

Product Version

7.0.0

This can be followed and adapted to the Linux version of Capella / Team for Capella. Path are equivalents, the Linux bundle provides .sh scripts which are equivalent to the Windows .bat scripts described in this guide.

2. Document overview

This document is intended for persons in charge of installing Team for Capella.

It describes the nominal installation, configuration and uninstallation of Team for Capella.

Please refer to the Team for Capella documentation for more details and advanced configuration.

The Team for Capella Guide is available from the documentation embedded in the client, but also online, see Referenced Documentation.

To read the embedded documentation, launch a Team for Capella client (after installation), click on the Help menu in the top menu bar. Then click on the Help Contents button. A web page will appear with all documentation and especially the Capella Guide and Team for Capella Guide sections.