Book a Demo

Author Topic: EA Audit and shared projects  (Read 3663 times)

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
EA Audit and shared projects
« on: October 12, 2011, 10:50:25 pm »
Hi

I enabled EA user security to enable the Auditing.
All models are shared as XMIs via SVN + the EAP file is sometimes committed to SVN when images are added to the project (otherwise we run a Get All Latest to retrieve the latest definition from XMIs)

I wonder how audit logs can be managed in such approach : if each user has its audit log stored in its own EAP, they're lost as far as SVN is concerned. Do we have to force each user to commit an XMI export of its audit log? Or else?
Anyone came across this and can explain a workable solution?

cheers
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: EA Audit and shared projects
« Reply #1 on: October 13, 2011, 02:17:58 am »
The audit (from my point of view) just makes sense with a central repository where an admin can manipulate it. For your de-central model you can be sure that a lot of users will not check in their audit logs manually. So it's rather pointless.

q.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: EA Audit and shared projects
« Reply #2 on: October 13, 2011, 08:22:37 am »
I would recommend using the baseline comparison instead in this situation. Each change is made by a single user and you can actually see how the changes are interrelated.

Without explicitly baselining anything it's possible to compare against any prior version.

What you don't get is a long term history of any element in a single view. But my experience is that I've needed to clear old audit history frequently enough that I didn't really get that anyway.
« Last Edit: October 13, 2011, 08:24:22 am by simonm »

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: EA Audit and shared projects
« Reply #3 on: October 13, 2011, 08:34:03 am »
FWIW: we use the audit on a central repository. Each night the audit is exported. If the export has more than 3 lines a snapshot of the db is made and checked into VC together with the audit export. Afterwards the audit is clean washed with a Execute ('delete from t_snapshot where 1'). So we have single snapshots with an audit that tells the differences to the prior snapshot. I'm pretty sure nobody will ever really make use of these audits but you feel saver if you know that any possible bad thing has been logged (just like CCTV; if someone had been killed you will eventually find the killer but you can't resurrect the victim).

q.

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Re: EA Audit and shared projects
« Reply #4 on: October 13, 2011, 06:28:10 pm »
Hi qwerty

What do you mean by central repository ? Is it an EAP that's shared by many users - if so how can you share it?
Do you work in a shared environnement with SVN, XMIs or do you use a central dB instead?
the baseline seems a good alternative
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: EA Audit and shared projects
« Reply #5 on: October 14, 2011, 02:40:51 am »
Actually it's not a big difference between using an EAP and a MySQL Server - except that likely your net-admin will kill you in the first case. EAP files are simply MS Access and you can share them over a network drive, but... (ask your admin about the network traffic).

We are using a MySQL Server accessed via ODBC. An old workstation is running a batch that opens all schemes, checks for updates (via the audit log), exports the whole tree and checks it in (we're using ClearCase but svn or any other VC software will do too) along with the audit. That's it.

The repositories are configured with security so users can only fiddle around were they are authorised. Further we set Require Lock to Edit which prevents concurrent access to the same objects (and forces modellers to talk to each other).

Before that we tried VC packages but had a lot of problems with that (VC and EA both did not play smoothly together as we wished, but that's a different story).

q.