RDBMS and VC?

[robert.staflin]

We're using multiple .eap files at the moment, but I get complaints about the version control capabilities (that I haven't yet deployed)...

I've managed to set this up using Subversion, but I'd like to also go the RDBMS route for added stability and ease of management - but I don't grasp how. The documentation on how to set either of VC (SCC) and RDBMS is clearly documented, but the combination?

Could anyone point me in the right direction? Any docs on setting the combination up? Thanks!

/Robert

[Geert Bellekens]

Robert,

There is in fact no difference between setting up VC with RDBMS or with EAP files.

Geert

[ChrisBD]

All you need to do is build your blank database using the script available on this site.

Then within EA use the "Tools\Data Management\Project Transfer" utility to transfer the EAP project to RDBMS.

The configuration for the VC is, as Geert said, the same for each project type.

I would suspect that you may need to have one DB for each EAP project, but I'm willing to be corrected on that.

[Geert Bellekens]

In fact you can store multiple models in the same db. They show up as multiple root elements in the project browser.
The advantage of using an integration with VC is that you can use the security of the VC to control who has write access to which (part of) project.

Geert

[ChrisBD]

Thank you Geert.
I've never transferred more than one EAP into a DB, and so wasn't sure if it would overwrite any previous project.

[Geert Bellekens]

Whoooo-STOP
You cannot transfer more then one eap file to a database, but you can have multiple models in eap files as well.

If you want to merge different eap files into one database you'll have to transfer one (the biggest one) and import the others from xmi.

Geert

[robert.staflin]

Great, thanks! I'm just stuck in the concept that it's the "file" that is being VCed. I'll try to set everything up and get back with more detailed questions.

[Geert Bellekens]

Robert,

It's not the eap file that is VC'd, but the xmi export file.

Geert

[robert.staflin]

Thanks again. Sadly, I can't get EA to transfer a project to the database though. The Project Transfer dialog is setup with .EAP to DBMS, the ODBC connection tests fine, but when I click "Transfer" I get a warning dialog stating "Enterprise Architect has experienced a network error and will close down".

So, close, but no cigar... :-(

I can't find this error more than in one place in the net (for EA version 6.1, and no answers).

I'm using PostgreSQL 8.4.1, psqlodbc_08_03-0400 and EA 7.5.849

[robert.staflin]

I get this on both my test and production systems.  

[Geert Bellekens]

Robert,

In order to transfer a project you first need to create the empty database.
There is a script available on the website.
Furthermore EA is pretty picky on the database driver you use. Checkout the help/website to find out wich specific driver you need to connect EA to PostgreSQL

Geert

[robert.staflin]

Thank you - the database is set up with an empty database, and the script run on it with no errors.

I'll check if it's a driver problem (I've only found two ODBC drivers for PostgreSQL - ODBCng and psqlodbc. The former won't show up in either of the odbcad.exe programs, but the latter does (I'm running everything on Windows Server 2008 r2 x64).

[Geert Bellekens]

You might want to actually read the page about the PostgreSQL.
It explicity states version 8.4.1 has issues transferring the project.

Geert

[robert.staflin]

Nope, now I've upgraded postgreSQL to 8.4.3, and there's still the same on both systems. Must be something else (unless Sparx means 8.4.1 and up - but on both pages (the one I looked at, and the one you pointed out) they point to the 8.4.1 driver, not the database iteself).  

[Geert Bellekens]

In that case I'd ask Sparx for help.
Send in a bug report using the link on the bottom of the page.

Geert