Working with Libraries in a Multi-user Context

1. Export Procedure

One classical pitfall is to export models (libraries and projects) that are linked by "reference" relationship one by one. Rather, export of linked models must be done at the same time because doing it one by one may lead to the export of still exported models. For the sake of illustration, having two projects P1 and P2 referencing library L1 may lead to one re-export of L1 if one tries to export P2 after having exported P1. The following section describes the correct procedure.

We assume in this section that a Team for Capella Client is opened and its workspace contains a set of models (projects and libraries) that are interconnected by the way of reference links.

In that context, the export procedure is as follows:

  1. Select all AIRD of interlinked models,

  2. Right-click on the selection, and click on export,

  3. Choose Export model in Team for Capella category,

  4. Test the connection, authenticates if required and click on finish.

  5. You can afterwards connect to the models you want as usual.

Figure below illustrates the four steps described above in the given context:

  • five models (two projects P1, P2 and three libraries L1, L2, L3),

  • P1 refers to L1 and L2,

  • P2 refers to L1,

  • L2 refers to L3.

07. Working with libraries in a multi user context html m4969ca1b

2. Project/Library Usage

Libraries can be accessed as classic remote projects with Team for Capella and have almost the same behavior as with Capella standalone:

  • When connected to a remote library, its semantic model is visible as well as all its diagrams,

  • When connected to a remote project referencing libraries, only semantic models of these libraries are visible from the project.

It is allowed to open, in the same client, a project and some libraries it references. Thus, it is possible to have two views (or more) of the same semantic elements:

07. Working with libraries in a multi user context html m33d35ac0

If a library is referenced with a "readAndWrite" access policy, it is allowed to change its semantic model from the project connection, from P1.team in this example:

07. Working with libraries in a multi user context html m4b9ebc9b

Even if the user is logged with the same login to L1 and to P1, if a change is done on one side, there will be a green lock on this side and a red lock on the other (so concurrent changes are forbidden on library’s elements).

3. Limitations and Known Issues

  • When working with a library, it is recommended to close referencing projects (this recommendation applies only when several remote libraries/projects are open).

    • Known issue: lock decorators are not correctly updated between a library and its view in referencing projects,