Features
Obeo Designer Team provides a fine-grained concurrency management policy: only the minimum set of elements are locked and automatically released when you save the modifications.
| Implicit locking | Any object being edited is automatically locked. It is notified to other users by a specific icon visible on all the representations where the object is visible. The lock is automatically released once the modifications are saved. |
| Explicit locking | It is possible to explicitly lock objects to avoid their modifications by other users. The lock is released on demand. |
| Instant updating | As soon as a modification on a model element is saved, it is instantly reflected to other users who view the same object. . |
| CDO-based technology | The repository is managed with CDO, the Eclipse open-source solution to store EMF models into a database. |
| User Profiles | Specific permissions can be defined to give users an access to only some parts of the model. |
| Ready-to-deploy collaborative server | This server comes with a multi-platform backend for high-level performances. It uses an H2 multi-platform Java implemented database that delivers on both performance and stability. Obeo can assist users integrate this with other databases. |
| Collaborative server administration | This console allows you to enter commands to execute operations on the server: list all active repositories and sessions, export the database to an XML file, reset the database to a state described in XML file, list and delete durable locks, stop the server.
Note: this feature is available with Obeo Designer Team Server which has to be downloaded separately. |
| Local project export | Modeling projects which are installed on your environment can be exported to the remote repository and shared with other team members. |
| Remote project import | Projects installed on the remote repository can be imported into your environment. |