solution wanted: multi-user

[marcelloh]

We are working on an oracle set, and various users can simultaniously edit the same object, package or... stuff like that.
The object saved is the one of the slowest person that saves.

What is the best solution for this?

I know there is:
- Locking
- Audit facilities
- Baseline Difference

For the first one: what if someone locks, and dies behind the keyboard. is it overridable?

For the last 2, does it mean I have to check before and after each save, if my object is changed. (And do I have to do additional stuff for it?)

Some advice on this would be handy.

[beginner]

For the first: yes, the admin can take back all locks at his wish.

For the rest: there is no simple solution. If you want to be safe you have to take quite some effort (e.g. a team to evaluate changes and bring them in a master db after some QA).

You can go with the first solution as long as you can trust your modelers. Backup is mandatory, however.

b.

[Geert Bellekens]

Marcel,

The easiest solution is to turn on the built-in security feature (with "require user lock to edit").
This ensure exclusive write access to elements.
The locks are easily overridable (although the GUI dialog could use improvement).
This of course doesn't ensure versioning or tracking.

For versioning I would integrate EA with your favorite Version Control system. I've done that with a couple of VC's and it works quite well (though it is usually slower then security, and the finest granularity is the package, where security works on element level)

If you don't need versioning and only want to track the changes you could turn on auditing, but that could have an impact on EA's performance as well, depending on how you set it up. Test before deploy!

Geert