The final piece of the puzzle - DBMS, VC, Security

[PhilK]

Hi all,

After some RTFM'ing and playing around from the replies I got for my post about restricting access to a large model I've now got DB export/import, version control using SVN and user security implemented.  Both my colleagues and I are pretty blown-away by what we've been able to do in such a short time with EA, but I think we are missing the final piece of the jigsaw puzzle.  

Reading the Version Control whitepaper and looking at the Shared Model example near the back this looks like the best fit for our usage, but looking at it I think we are just not getting the interaction between the DB and VC functions.

Does this usage look right?

1.) DBMS -> Local EAP (under SVN)
2.) SVN checkout
3.) Change model
4.) SVN check-in
5.) Local EAP -> DBMS

What's the benefit with this solution over that of the Workgroup Model?  Does using the DB store and VC mean a degree of duplication of the model?  How are the DB and VC repositories kept in sync?  Can we have different branches of the model under VC and still be in the DB?

[Geert Bellekens]

Does this usage look right?

1.) DBMS -> Local EAP (under SVN)
2.) SVN checkout
3.) Change model
4.) SVN check-in
5.) Local EAP -> DBMS

No, it doesn't, for the following reasons:

1. You normally either use a dbms or a local EAP file, not both. (Unless you want to edit the model offline, or in a remote location from time to time)

2. You never control the EAP files themselves into VC, only the package (in the form of the xmi exports). There is really no point. The eap file is in a binary format, and unless you can read that (which i doubt) you can't do anything useful comparing the different versions. If you really only need a backup of your eap file then... use a backup solution, no version control.

3. There is no need for the EAP file at all, just work on the dbms and control the packages in the VC. (I really don't see why you would do all that transferring between eap files and dbms, looks very time consuming to me)

Geert

[PhilK]

Thanks Geert,

Your answer prompted me to look a little closer and I've now worked out what the "Connect to Server" checkbox is on the Open Project window, boy is this so much easier than the ham-fisted way I've been importing and exporting DBMS files to a local EAP model - now it's a direct connection to the DB.  Perhaps renaming it to "Connect to DB" would make things clearer  

So, to update things:

Open DBMS Model
Package Control->Check-out
Update things
Package Control->Check-in
Save DBMS Model

Is that about it?  

What's the connection with VC and the DB regarding svn locks and conflicts, can one user one user just save the model to the DB without resolving any svn issues?  If they can how do you recover from this?

Best regards

Phil

[Geert Bellekens]

Phil,

You're almost there. Actually it's

Open DBMS Model
Package Control->Check-out
Update things in the checked-out package and save immediately
Package Control->Check-in
Save DBMS Model

Since EA forces an exclusive lock on the checked-out package you don't have to worry about conflicts.

Geert

[PhilK]

Aha!!

Got it, thanks Geert.  All I need to do now is work out how to work with svn branches in the model and everything will be complete.

Cheers

Phil

[Geert Bellekens]

Good luck with that.
There are some people here on the forum who have experience with branching who explained their way of doing things.
Use the search button on the top left to find them.

From what I remember, there is no easy solution, and you better avoid branching as much as possible.

Geert