Wow...EA is full of surprises! I didn't know that.
But, according to the EA help, it only works for DBMS, unfortunately.
So still, my question remains, why does EA has to access the DB for checked out packages? Isn't it a local-only thing?
Hi Jan,
The problem is that the EAP file is on the
wrong side of the VPN. EAP files (accessed with native Jet drivers) are designed by Sparx to be
local to your system. You can use them in shared configurations as you are, but you have to be aware of the limitations.
The
correct way to think of EA repositories is to think of them operating in two modes:
Native Jet and
Server (as in Client-Server). Not Jet and DBMS (Geert and Sparx - they're
all DBMSs - all that's changing is the drivers).
Only EAP files can operate in Native Jet mode. Consequently, if you are using native Jet access, the traffic between the applicaiton and the disk will be the same regardless of where the EAP fiel sis located.
To access an EA repository in server mode, you need Corporate edition or better. We've done extensive testing on various configurations of repositories and editions and now believe we have a good understanding of what's going on.
So, if you create a
separate access path to the
same, Samba based, EAP file, but using an ODBC connection, you should be able to access the EAP file in
server mode. Consequently, you should be able to use the WAN Optimizer as Geert suggests. I haven't used it myself, but from the reports by forum members I see no reason why it shouldn't work via the ODBC connector.
Also, from the way in which you expressed the original problem, you
may have a misunderstanding of the way package check-in/check-out works for EAP files. Just as with server-based access, Check-in involves the export of the package from the EAP file as an XMI. followed by the check-in of the exported XMI to the VCS. Check-out involves the reverse process: Check-out the package XMI from the VCS, import the checked-out XMI into the EAP file.
Consequently, in your original scenario, check-out involves the transmission of the XMI to your local machine over the VPN, immediately followed by the storage of the imported package information back across the VPN to the EAP file on the Samba drive.
HTH,
Paolo