Introducing the Cloud Server

The Sparx Systems Cloud Services solution provides seamless access to Enterprise Architect repositories (models) from anywhere in the world, providing high performance for remote access, secure encrypted links and optimization for high latency WAN connections.

Cloud-based repositories provide easy access to models, not only for people within your local team, but for remote team members, external customers and consultants anywhere around the world with Internet access. Collaborative and distributive modeling and design are dramatically enhanced by using a Cloud-based repository, and can provide the shared backbone for a wealth of development scenarios.

This section will:

  1. Familiarize you with the concepts of the Cloud Services
  2. Walk you through the process of setting up a server
  3. Walk you through the process of connecting for the first time
  4. Discuss considerations of when and where you should use a Cloud server
  5. Highlight some of the additional functionality available through the Cloud server
  6. Outline working with Active Directory using IIS


Connecting to models stored in a Cloud Server is as simple as entering a single URL. Enterprise Architect models are stored in databases. With standard connection to DBMS repositories, such as SQL Server and Oracle, Enterprise Architect requires users to install the appropriate drivers for the database and create ODBC or other connections.

When connecting to a Cloud Server that procedure is dramatically simplified, requiring only a URL to the provided Cloud repository. No special drivers or further configuration is required.

Connecting to a Cloud Server provides a number of key benefits:

  1. Improved performance for models used for distributed development. The Cloud server provides benefits to connections that involve high latency and reduced data transfer speeds.
  2. The process of setting up drivers and connections can now be performed once by an administrator during the server configuration. The only set-up required on a user machine is to install Enterprise Architect and connect to any model on the Cloud server using a simple URL.
  3. Database servers no longer have to be exposed through a firewall; the Cloud server can be run from inside a corporate firewall. All model connections are now created using HTTP, allowing firewalls to completely isolate your database server.
  4. A Cloud server can be configured to encrypt all communication. Using standard TLS/SSL protocols, you can be confident that your data is not intercepted during transmission on insecure networks.
  5. A Cloud server can be configured to provide HTTP-level authorization to any model taken directly from the model user list. Even when the model is exposed on a public network, you can be assured that only authorized users are able to access your model.
  6. A Cloud server can be configured to provide read-only access to any model; for example, for clients required to review a model.

Security Considerations

As with any web connected service, there are a number of security concerns that must be considered when setting up a new service. To help you minimize risks, consider these points:

  • If any data is considered private, always use an HTTPS connection and require user authentication. There is an option on each of the service's database configurations to prompt for this.
  • There is an implicit trust in sharing a model with anyone. Security is available in models, which prevents a wide range of possible interactions. However, due to Enterprise Architect's flexibility determined users can circumvent this. In particular Model Search SQL queries can be run in a number of places that allow data to be read that would not otherwise be accessible. Of note, this includes user IDs and hashes of their passwords. To prevent this type of access to a list of users, you could use Global Authentication instead of Model Authentication. This is discussed further in the Cloud Server Configuration topic.

Learn more