Book a Demo

Author Topic: Recover from Version Control without Database  (Read 4864 times)

Ramiro Gonzalez

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
Recover from Version Control without Database
« on: June 01, 2010, 03:41:16 am »
Is it possible to reconstruct the full repository (EAP or DBMS) with just the XMI files from Version Control Server but without the original Database?

Trying just importing the root XMI files seems to load just the structure but not the diagrams. And loading file by file give us odd results, like for example loading some diagrams but losing others. Seems to me, it requires a special order of importing files… is this right? How can I figure out the right order to load the files?

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Recover from Version Control without Database
« Reply #1 on: June 01, 2010, 09:36:28 am »
Try loading ALL the packages twice - but sequentially:

Load: A, B, C then A, B, C

If that produces a better result then you might try it three time (although twice is usually enough).

HTH,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Ramiro Gonzalez

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
Re: Recover from Version Control without Database
« Reply #2 on: June 02, 2010, 07:57:36 am »
But... there is no an automatic way? or by script using command line?

I have more than 100 xmi files (one for each package on several views), and is kind of cumbersome to do it by hand.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Recover from Version Control without Database
« Reply #3 on: June 02, 2010, 09:49:06 am »
Quote
But... there is no an automatic way? or by script using command line?

I have more than 100 XMI files (one for each package on several views), and is kind of cumbersome to do it by hand.
See if Project|Import/Export|Batch Import... helps.

Certainly after the first import there should be a list of packages you can batch import.

HTH,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Recover from Version Control without Database
« Reply #4 on: June 02, 2010, 03:44:06 pm »
Another thing to look at is Model Branches. (Package Control/Export as Model Branch)
You can export a model branch (a package with all its subpackages recursively) and import that into another model.
I think that is a lot easier then importing each xmi file separately, or using batch import.

Geert

Van Lepthien

  • EA User
  • **
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Re: Recover from Version Control without Database
« Reply #5 on: June 30, 2010, 05:30:58 am »
Similarly, you can take baselines and export them and later import the exported baseline.

Frank Horn

  • EA User
  • **
  • Posts: 535
  • Karma: +1/-0
    • View Profile
Re: Recover from Version Control without Database
« Reply #6 on: June 30, 2010, 04:27:39 pm »
Ramiro,

here are the steps I would take:

1. Import the root packages via the "Version Control - Get Package" command. If you know how they depend on each other, first import those which do not depend on any other packages, then those which depend only on those previously imported and so on (recursively). If this is not possible, i.e. if your root packages have circular dependencies: Just import them in an arbitrary order.

2. Use the "Version Control - Get All Latest" command for each root package. If EA says they are up to date: don't believe it! Always choose the "Force reload from XMI" option.

3. Check whether your model is complete. If diagrams or dependencies are missing: Repeat step 2.