Sparx Systems

Team Modeling Resources for Enterprise Architect

This page provides resources for users who intend to deploy Enterprise Architect in a shared, team environment.

Team based modeling can involve usage of a DBMS server for shared model repositories, role-based security to help govern editor permissions and performance optimization for remote repository connections (for example when editing a model via VPN).

Resources for each of these needs are listed below:

DBMS Repositories: Other Team Modeling Resources:

Please note: Either the Trial Edition or the Registered Edition of Enterprise Architect is required to use the resources listed below.

Setting Up DBMS Repositories

The Corporate and Suite Editions of Enterprise Architect support a variety of DBMS's to host the model repository. To use a DBMS repository you need to create a database and the Enterprise Architect schema (consisting of a collection of tables). General speaking the creation and modification of database definitions is performed by a user (typically a DBA) with an elevated level of security, therefore these types of tasks are handled outside of Enterprise Architect the application. Below are the scripts for each of the supported DBMS's to create the required definitions.

Please Note: Throughout Enterprise Architect's history Sparx Systems have endeavored to avoid changing the underlining database structure due the problems that this would cause with older versions. However since 2010 there have been two major schema releases:

  • Schema 1220 released in Jun-2016 with Enterprise Architect v13 (build 1302)
  • Schema 851 released on 10-Feb-2010 with Enterprise Architect v8 (build 851)

In both of the above releases the schema changes have not required any code changes to the Enterprise Architect logic, thereby allowing earlier version of Enterprise Architect to stay compatible with newer schema definitions (and vice versa). In the most recent release, 'schema 1220' consists mainly of index updates which improve Enterprise Architect's overall performance in larger models.

EASchema 1220 files:

MySql (instructions)
 EASchema_1220_MySQL.sql (56 KB, 20-Jun-2016)
Note: all long text fields are now MEDIUMTEXT (instead of TEXT) which allows for more than 65K characters.

Microsoft SQL Server from 2005, all editions including Express and Azure (instructions)
 EASchema_1220_SQLServer.sql (63 KB, 20-Jun-2016)

Oracle from 9i (all editions) (instructions)
 EASchema_1220_Oracle.sql (63 KB, 20-Jun-2016)

PostgreSQL (instructions)
 EASchema_1220_PostgreSQL.sql (50 KB, 20-Jun-2016)

Adaptive Server Anywhere 8 and 9, SQL Anywhere 10 and 11 (instructions)
 EASchema_1220_SybaseASA.sql (54 KB, 20-Jun-2016)

EASchema 851 files:

MySql
 EASchema_851_MySQL_InnoDB.sql (51 KB, 10-Feb-2010)
 EASchema_851_MySQL_MyISAM.sql (51 KB, 10-Feb-2010) Note: MyISAM Databases do not support transactions or unicode.

Microsoft SQL Server from 2005, all editions including Express and Azure
 EASchema_851_SQLServer.sql (88 KB, 10-Feb-2010)
 EASchema_851_SQLAzure.sql (88 KB, 27-Nov-2013)

Oracle from 9i (all editions)
 EASchema_851_Oracle.sql (105 KB, 10-Feb-2010)

PostgreSQL
 EASchema_851_PostgreSQL.sql (52 KB, 10-Feb-2010)

Adaptive Server Anywhere 8 and 9, SQL Anywhere 10 and 11
 EASchema_851_SybaseASA.sql (57 KB, 10-Feb-2010)

Initial data into a DBMS repositories

Once a DBMS database is created and the Enterprise Architect schema defined, the model now needs the 'base' data loaded. Traditionally this step has been achieved by loading the contents of the 'EABase.eap' sample model into a newly created database, using the Project Transfer action within Enterprise Architect.

As an alternative it is now possible to load this same data using standard SQL statements. However please note the scripts below, only contain statements to insert new data, therefore don't attempt to run these on models that already contain data.


MySQL
 EABase_1220_MySQL.sql (227 KB, 30-Jun-2016)

Microsoft SQL Server from 2005, all editions including Express and Azure
 EABase_1220_SQLServer.sql (277 KB, 30-Jun-2016)

Oracle from 9i (all editions)
 EABase_1220_Oracle.sql (276 KB, 30-Jun-2016)

PostgreSQL
 EABase_1220_PostgreSQL.sql (277 KB, 30-Jun-2016)

Below are copies of the Jet 3.5, 4 and Microsoft Access 2007 EABase projects, including the latest schema definitions (1220).
 EABase.zip (137 Kb, 30-Jun-2016)

Enterprise Architect Base Project (EAP) Microsoft Jet 4.0
 EABase_JET4.zip (302 Kb, 30-Jun-2016)

Enterprise Architect Base Project - Microsoft Access from 2007
 EABase1220.zip (278 Kb, 30-Jun-2016)

Update DBMS Repositories

As mentioned in the previous section Enterprise Architect's official schema definition doesn't change very frequently however if your model was created inbetween 10-Feb-2010 and Jun-2016 then it will not have the most up-to-date indexes defined.

The SQL scripts below are provided to update a 'schema 851' model to 'schema 1220'. The process to run these scripts should be:

  1. Take a backup of the current DBMS repository.
  2. Connect to the RDBMS database to be updated (using the SQL management console of choice).
  3. Load the relevant EASchema_Alter851to1220_xxx.sql file.
  4. Run the script.
MySql
 EASchema_Alter851to1220_MySQL.sql (18 KB, 20-Jun-2016)
Note: all long text fields are now MEDIUMTEXT (instead of TEXT) which allows for more than 65K characters.

SQL Server 2000/2005/2008/2012/Express and Azure
 EASchema_Alter851to1220_SQLServer.sql (97 KB, 20-Jun-2016)

Oracle 9i, 10g, 11g and 12c
 EASchema_Alter851to1220_Oracle.sql (29 KB, 20-Jun-2016)

PostgreSQL
 EASchema_Alter851to1220_PostgreSQL.sql (23 KB, 20-Jun-2016)

Sybase Adaptive Server Anywhere 8 and 9, SQL Anywhere 10 and 11
 EASchema_Alter851to1220_SybaseASA.sql (11 KB, 20-Jun-2016)

Firebird
 EASchema_Alter851to1220_Firebird.sql (12 KB, 23-Jun-2016)

Updating Pre Feb-10-2010 DBMS Repositories

If you model was created before 10-Feb-2010 then the following steps should be undertaken before attempting to upgrade from 'schema 851' to 'schema 1220'.

Note: To apply the update patches, open the existing repository model and use the Run Patch menu item. See the Enterprise Architect User Guide for more information on running an SQL Patch.


MySql
 MySQLScriptUpdatePatch.xml (7 KB)

Microsoft SQL Server from 2005, all editions including Express
 MSSQLScriptUpdatePatch_2005-8.xml (11 KB) Update
(Please Note: This update script is not applicable for SQL Server 2000)

Oracle from 9i (all editions)
 OracleScriptUpdatePatch.xml (6 KB) Update

PostgreSQL
 PostgresScriptUpdatePatch.xml (7 KB) Update

Adaptive Server Anywhere 8 and 9, SQL Anywhere 10 and 11
 ASAScriptUpdatePatch.xml (8 KB) Update

Cloud Services

The Sparx Systems Cloud Services application provides a convenient mechanism for hosting models. It provides easy access to people within your team, and optionally to external customers and consultants anywhere around the world.

For more information please refer to the following resources:

Setting up the Cloud Server
Cloud Trial
Cloud Server Guide
Download the Cloud Server Application - Registered User access required

User (Role-Based) Security

User security is included in the Corporate, Business and Software Engineering, Systems Engineering and Ultimate editions. Trial users can enable user security on a project, by entering the following key: {C27378C8-6CD8-4efa-92F8-4E0E4F1A8B65}

A separate key is available for Registered users from the registered site.

WAN Optimizer

With the release of Enterprise Architect version 11, the functionality provided by the WAN Optimizer has been replaced by Cloud Services, as a result no further development will be made to the WAN Optimizer. This section remains here for legacy purposes.

The Sparx Systems' Wide Area Network (WAN) Optimizer is a server side process for enhancing performance when connecting to remote model repositories. This process reduces the amount of data transmitted and, in turn, the level of network traffic between the Enterprise Architect client and the remote repository.

Download the WAN Optimizer service and client application:

 wanoptimizer.exe (1.1 MB)