|
What is Cameo Team Server?
Cameo Team Server allows collaborative work with metamodels and models in the Cameo Suite. Being a single repository for all Cameo clients, it delivers identical functionality and work principles for all clients that use it. Cameo Team Server forms a base for integrating different models from different clients as all models reside in a single repository.
The figure above shows a basic schema how the Cameo Team Server clients (e.g., Cameo Requirements+) interact with the server. Clients connect to the Cameo Team Server to retrieve projects (schemas, repositories, or models) and update them. Cameo Team Server manages the server storage and acts as a lock database thus allowing for clients to acquire and release locks. Locks enable model editing. They allow model merging into the central repository without conflicts. To edit projects, clients lock parts of the projects they want to change, modify them, and commit changes to the server. Cameo Team Server also provides authentication services for the clients (clients can authenticate against the server using a username and a password).
Benefits of the Cameo Team Server?
- Allows developing Cameo Requirements+ schemas, requirements and storyboards collaboratively in a single repository. Cameo Team Server provides a single repository for all project artifacts. Schemas, repositories, and in future – models and simple files – are stored in a single repository. This forms a base for easier management of a project, easier structuring of various artifacts into packages, and easier management of the infrastructure because everything is stored in a single repository managed by a single server.
- Scalability - suitable for large projects. All the project data is stored in an RDBMS, thus the server is infinitely scalable. This allows you to quickly store and retrieve large amounts of data.
- Fast updates and commitments to the server. Only data that changes between the server and the client is transferred. This means that time needed for updating and committing does not increase when the project size grows and depends only on the volume of changes made in the current commitment or changes made to the central repository.
- All project data is stored in an RDBMS. Cameo Team Server uses an RDBMS to store all project data. Apache Derby comes as part of the installation package by default (bundled together with Cameo Team Server) and does not require any additional administration. It is optionally possible to use MySQL thus exploiting existing client infrastructure thus allowing faster work with the projects. In future Oracle, PostgreSQL and Microsoft SQL Server database management systems are going to be supported.
- Element-level versioning. Stores history of how each element changed during time. In future releases this will allow history reviews at element level and fine-grained reverts at element or package level.
- Automatic locking. Locks are acquired automatically when users try adding, removing or editing project elements. No user intervention in this process is required.
- Server administration. Server administration is done using a Web Client that connects to the server and allows for managing projects, users (adding/removing/editing/disconnecting), locks (reviewing/releasing), and licenses. The Web Client is part of the server that does not require any additional software to be installed to work.
Cameo Team Server Functions
The user working with the Cameo Team Server may perform several operations:
- Add a brand new Cameo Requirements+ project (repository or schema) into the server, convert a local project to a server project and vice versa.
- Get the newest Cameo Requirements+ project version from the server (update local project with new changes from the server).
- Lock for the edit part of the project on the server. When part of the project is locked every other user that is working with the server has read-only access to this part. Locks are acquired automatically on the project parts that are being modified. The user can manually acquire locks on project parts.
- Commit changes to the server. After locking and editing information, the user may commit the changes to the server thus making them visible to the whole team. The unlock operation may be performed after the committing in order to allow other users to edit new information.
- The user can review acquired locks in Lock View. This view provides a tree structure of the locked project elements. The user can browse from this tree to the normal repository tree. The user can selectively release acquired locks.
Connecting to the Cameo Team Server
All Cameo Requirements+ client versions starting from 4.0 can connect to the Cameo Team Server. Whenever you install Cameo Team Server you supply a license key, which bears information on how many simultaneous connections can be made to this server at a single time. There is no limitation on how many installed client versions of Cameo Requirements+ may access the Team Server potentially. The limitation of the connections specified in the server limits the number of the clients that can work with the server (perform update, commit, etc.) in parallel. The number of the projects you can create in the server repository is also not limited.
Evaluation version of the Cameo Team Server may be provided to you for a trial upon request. You will be able to run several client licenses and use Cameo Team Server with no restrictions on functionality for a limited period of time. Please send your request with the following information: company name, contact person name, phone, number of the client licenses and server connections you are looking to purchase, to sales@cameosuite.com.
Pricing of the Cameo Team Server?
Cameo Team Server does not require any licenses to be installed and run. However, in order to be able to store metamodels and models in the server storage, a license for the specific client type must be supplied through the Web client (administrator console).
|
594 Kb)
