Configuration

[Mega]

Hi All

I am planning to introduce EA into our organisation so investigating an ideal deployment option. After some initial research I have found that the following deployment may be ideal for us:

1. Version Control using Subversion.
2. One Repository - Multiple Projects (creating a single EA Project and creating multiple root nodes under Version Control).
3. Shared Model - A number of modellers (User A, User B, User C) will work on a shared model stored in Local Server.

According to EA documentation:
1) I have created one Repository dedicated for EA models on SVN Server.
2) Created one Local Working Copy of this Repository on Local Server.
3) Create one .EAP project stored on Local Server as shared project.
4) Create for .EAP project many nodes. Nodes has been configured as Version Controlled Packages with 'This model is private' unchecked.

This is a diagram of my configuration:


After some preliminary testing it seems that if any user checks out a package from version control the package is checked out (and modifiable) for anyone else using the shared model. But, how it could be different if all users use the same one Local Working Copy with the same version control user? :-?

Is there any possibility to solve this porblem?
Is there any possibility to assign for each user different Local Working Copy or different version control user if they work on the same shared .EAP file with nodes controled by Subversion??

Best Regards,

[Mega]

Has someone solved this problem and it pretended him to establish the real concurrent model for the shared model of EAP project?

[Eve]

I don't know about the rest of your configuration, but one problem is going to be having everyone use the same SVN user.  You need to use different users for EA to be able to distinguish between them.

Have you read the Deployment and Version Control white papers?  http://www.sparxsystems.com.au/resources/whitepapers/

[HowardB]

Hello Mega,

The behaviour that you describe belongs to EA versions that pre-date 7.5

If you check-out Subversion working copies onto each of the users' PCs, that is, each of the laptops and the desktop PC, and direct EA to use the (personal) working copy instead of trying to share a common working copy folder between all three users, that should solve the problem for you.

When you lock a file in Subversion, a lock token for the file is created in the repository and also copied to the working copy folder.

If your working copy folder does not contain the lock token that the repository says it should, then the file isn't locked in that working copy, and EA won't see the corresponding package as "checked-out".

As of EA version 7.5, this behaviour still applies, however, in addition, EA now records the Windows user name of the person that has checked-out a package.

regards,
Howard Britten.

[Geert Bellekens]

I've had this problem in the past using a different VC. (Serena Dimensions using SCC).
We solved this by using the EA security on top of the VC.
EA security allows you to lock certain elements for editing. Those then become editable only by the user who locked them.
So a checkout from version control made the package writable to all users, and the EA security made it writable only for the person who locked the package/elements.
This was a bit of overhead, but luckily EA automatically proposed to lock the package when performing a checkout (and unlock when doing a check-in), so all the user had to do was click OK.

On another note, have you considered using a (real) database iso the EAP files? The EAP files are basically Access datatabases, which might be a drawback when accessing those with a lot of users.

Geert

[aap]

Hello Mega,

The behaviour that you describe belongs to EA versions that pre-date 7.5

If you check-out Subversion working copies onto each of the users' PCs, that is, each of the laptops and the desktop PC, and direct EA to use the (personal) working copy instead of trying to share a common working copy folder between all three users, that should solve the problem for you.

When you lock a file in Subversion, a lock token for the file is created in the repository and also copied to the working copy folder.

If your working copy folder does not contain the lock token that the repository says it should, then the file isn't locked in that working copy, and EA won't see the corresponding package as "checked-out".

As of EA version 7.5, this behaviour still applies, however, in addition, EA now records the Windows user name of the person that has checked-out a package.

regards,
Howard Britten.

Does the new EA 7.5 behaviour prevent use of the Work Group Model schema described in the "Setting up Version Control" white paper? I'm having trouble getting this to work with EA 7.5 (847) clients.

I have set up a shared EAP file and shared Subversion working copy on a network drive. My co-worker and I are both using the same SVN userid, but distinct Windows userids. I want to be able to check out a package so that we can both work on it, but the package appears unchecked-out on my co-worker's PC and can't be checked out because EA correctly reports that I have checked it out!

Help please!

Thanks
Andy Pryor