Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: John Gentilin on November 23, 2015, 02:46:44 pm
-
Can the Cloud Server use the EAP file thru an ODBC connection ?
I would like to write a script that shuts down the Server then commits/pushes the EAP file to our GIT repo on a daily basis so we can roll back if necessary.
-John Gentilin
-
Hello John,
I suppose, this is not possible. EAP is a MS Access database file and Access is not a C/S application. Theoretically to get it work you would need a MS-Access running on your server and something that makes your MS-Access answering to requests coming from outside, but I belief there is nothing like that on the cloud server.
-Peter
-
Can the Cloud Server use the EAP file thru an ODBC connection ?
No
-
Maybe I asked the question the wrong way, can the Cloud Services utilize a .EAP file ? I happened to be looking at the Feature Request thread, and this was posted
http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1444222568
Which seem to indicate to me, that even though it expected the .eap file to me in a fixed location it could utilize a EAP file. ODBC was just a thought I put in there.
-John Gentilin
-
No. The cloud service does not utilize eap files regardless of connection method. If your requirement is for a "file based" repository you have options.
The default if firebird. It's the easiest to set-up, all you need to do is enter model-name.fdb into the new model dialog and then allow connections to it.
Alternatively, you could also use the Access 2007 format.
-
Thank you
-
I thought that Sparx EA version control didn't support git, as Sparx EA required exclusive locks. I'll look for the Online Help or White Paper that says this, but this is the main reason why my organization is staying with SubVersion.
-
I thought that Sparx EA version control didn't support git, as Sparx EA required exclusive locks. I'll look for the Online Help or White Paper that says this, but this is the main reason why my organization is staying with SubVersion.
Correct. However, the OP is putting the entire EAP file into git, which is more disaster recovery planning than version control.