You have two options for creating new models. You can use a local repository on your computer. This is a Microsoft Jet database that is compatible with MS-Access and has a .eap file extension. As a more robust alternative, you can use one of several database engines to hold your repository. The (EA)<sup>2</sup> reporting component is designed for SQL Server 2005 or 2008. Setting up a new model in either environment is described below.
Local .EAP Project Files
You can use the (EA)<sup>2</sup> Base Model to create new models that have a complete package structure for modeling enterprise archtiecture. To create a local Enterprise Project, i.e. a .eap file, based on the (EA)<sup>2</sup> Base Model, click on Copy a Base Project, provide a name for the new project and navigate to the My Documents/OAD Consulting/EA2 folder and select the EA2_BaseModel.EAP. You can also select a base model of your own making. For example, you could open use the (EA)<sup>2</sup> Base Model to create a new model, make changes to the structure of your new model, and then save it as your own base model.
Please note that you will not be able to use the (EA)<sup>2</sup> SQL reporting components with a local .eap file. They require a SQL Server database.
SQL Server Databases
There are a couple of steps required to create a new project using SQL Server. You must first create a SQL Server database and use the SQL script supplied by Sparx Systems to create the Enterprise Architect tables. Before using the Sparx script, you may want to change the COLLATION statements in the script to follow your standards.
If you don't, you may have trouble later trying to join the EA repository to another database, e.g. a configuration management database.
Next, you need to run the EA2_SQL_Installation_Script.SQL script in the My Documents/OAD Consulting/EA2 folder. This script will populate the SQL views, user-defined functions, and stored procedures supplied with (EA)<sup>2</sup>. It may be necessary to run the script several times as the intricate relationships among the views get resolved. After the errors are no longer being reported, you can run the EA2_TestViews.sql script to run all of the views to ensure everything has been installed properly.
You must place the name of the database you have created for your EA repository between the square brackets of the USE statement before running this script. For example change the line in the script that looks like:
USE [ ] to USE [MyDatabase].
Check the documentation at the beginning of the EA2_SQL_Installation_Script.SQL script for additional details.
Finally, you will need to transfer the EA2 Base Model.eap to the new database. This is done by selecting Tools | Data Management | Transfer Project from the Enteprise Architect main menu. Select .EAP to DBMS, set the source project to My Documents/OAD Consulting/EA2/EA2_BaseModel.eap and the source file to the new database you created.
