DBMS Repository and Subversion

[anupdarvatkar]

Hi,

I am new to EA. I intend to use DBMS as repository and Subversion for version control. I am not able to understand how the two will work together.
Question - how do I import the repository of the model (which is in DB) in subversion? Or is there an issue in what I am trying to do?

[Paolo F Cantoni]

Hi,

I am new to EA. I intend to use DBMS as repository and Subversion for version control. I am not able to understand how the two will work together.

Technically they don't directly work together.  

Unlike most other modelling tools, EA persists its in-memory model to a database rather than XMI/XML/Other textual representations.  When EA starts up, it incorporates (in the sense of "giving body to") the database into the in-memory model that you interact with via the infamous EAUI.   You can also persist the in-memory model to XMI files via a variety of mechanisms and source control these textual files via your favourite source control system (Subversion).  You can use internal support for version control or (like we do) use external source control.

Question - how do I import the repository of the model (which is in DB) in subversion? Or is there an issue in what I am trying to do?

Separately to the normal startup - which uses the database (whether MS Access - for .EAP files or an RDBMS server of various flavours) you can import the previously exported (whether from EA - or sometimes other products) XMI and add/overwrite parts of the in-memory model.  This is usually performed at the package level.

So, in summary, the database is the "Now" persistence of the current in-memory model.  Subversion is use to control textual snapshots of the in-memory model from various times in the past.

HTH,
Paolo

[Geert Bellekens]

I would recommend you read the version control chapter in the help file. There a quite a few options to decide on.
From you post I understand that you will probably want to go with the single shared model.
You will need to setup you version control provider first. (project/Version control/version control setting). That is where you define you local folder for the exported xmi files. Then you decide which parts of you model you want to control in subversion. You can select any package to be controlled. On a package you select the option Package control/configure and select the version control provider you defined earlier.
As indicated by Paulo EA will export an xmi file for each controlled package, and upload it into the subversion repository; all of this transparant to the user.
Once checked in EA will lock the package and only allow it to be modified by the user who has checked out this package.