Book a Demo

Author Topic: Use a repository (Oracle) for multiple projects?  (Read 2006 times)

David Swain

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Use a repository (Oracle) for multiple projects?
« on: June 20, 2008, 07:57:18 pm »
How do I use a repository (Oracle) for multiple projects?

I have just created a repository as per help, and tried transferring a couple of sample project EA files - and the second one overwrote the first ...

(I am a new EA user) I had thought I could put all projects / models in a single repository ... however there does not seem to be a facility to select different projects from a repository.  What blindingly obvious thing have I missed, please?
Thanks.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Use a repository (Oracle) for multiple project
« Reply #1 on: June 20, 2008, 09:04:12 pm »
No problem David,

Or at least it will be no further problem once you get used to how EA does this.

Similar to EAP files, DBMS repositories have a one-to-one correspondence to EA projects. That is, you need to create a separate repository for each EA project.

When you think about this a bit it make sense - though it could have been done in other ways. Given that EA works across many DBMS products, there would be severe limitations on how you could manage team access and such if all EA projects were part of the same schema instance. Even if you could get something working on one DBMS it is unlikely that it would work on the others.

Each time you do a project transfer - which is how you 'bootstrap' a brand new EA schema instance - you overwrite the entire contents of the target project (whether an EAP file or a DBMS repository). So in your case the second project trashed the first.

Just set up a process with your DBA (or whatever role is appropriate for your organization) to set these things up from time to time. Perhaps a script could call the Sparx script as part of a more comprehensive setup routine. This would also likely involve setting up user rights and such.

Another thing you might want to do is create one or more template projects. Perhaps you have a few startup configurations you use, or you want some corporate standard for look and feel; these would dictate the contents of otherwise 'empty' projects. Now you could transfer these to DBMS template schema instances. Your repository creation process could specify doing a transfer, or perhaps they could simply copy a template schema over.

HTH, David
No, you can't have it!