GUI screens from an external source

[jami]

Hi,
I have a lot of GUI mockups in JPG format, which I have to put in the model as objects to which I can create relations with use cases, additionally they should be generated through MasterDocument. I am currently placing them in a LinkedDocument. This takes up a lot of space in the repository and slows it down a lot.

Is it possible for EA to download these images from an external source (eg SharePoint) and generate them in the documentation? (The hyperlink could be placed in tags or properties of an object)

[jami]

Hi, maybe someone knows the solution to the above case?

[Eve]

If you are wanting them generated with the built-in generators I expect you'll need to have them in the model.

What's the concern with the space and what is it slowing down?

[jami]

Thx Eve.

I manage multiple repositories. Each of them has approximately 2,500 records in the t_document table. Each LinkedDocument contains a GUI image and a table describing the fields. Such a repository weighs approximately 500mb. After removing the documents, the repository weighs about 130mb. Now I have to migrate these repositories into one and I am afraid that such a number of screens will kill the main repository after migration.

In total I will have:
t_document: 20,000 records (GUI + description)
t_object: 200,000 records
t_objectproperties: 1,100,000 records
t_package: 30,000 records

Not too much?

[qwerty]

Since you were talking of MasterDocument (you are really using MSAccess replication?) you should strongly consider to switch to a real database instead. EAP is nice for stand alone working (or maybe 2-3 persons). But once it gets serious you need a real database. And throw that replication away as far as you can!

q.

[Geert Bellekens]

Since you were talking of MasterDocument (you are really using MSAccess replication?) you should strongly consider to switch to a real database instead. EAP is nice for stand alone working (or maybe 2-3 persons). But once it gets serious you need a real database. And throw that replication away as far as you can!

q.

Master Document = Virtual document package. Not related to the Access replication.

Having a lot of records in t_document should not slow down things too much if you are in fact on a "real" DBMS. (20K is peanuts for a real database)
And remember "Premature Optimalization is the root of all Evil"

Geert

[jami]

Each repository is a separate database (SQL). I am currently trying to migrate to one common database and work on multiple RootNodes.
I download the repositories to a local disk (ProjectTransfer) and then I can easily test them and export them to XMI faster.

The problem when it arises is also importing such large XMI to the target database repository.
OutOfMemory is displayed...

[Eve]

Have you tried the native xml? That has handling for larger packages.

[jami]

Hi, thank you for your answer.

The documentation says: "The contents of the current project will be deleted prior to importing the Native XML files"

My requirement is to keep the current data in the repository. The repositories should be imported as separate Models (Root Node).

Maybe I will have to import individual packages separately.

If the database exceeds 1GB, will I lose the ability to transfer the project to a local disk?

[jami]

Eve, thank you again for the hint.
Native XMI helped.
I exported the entire model to the native XMI.
Using the default XMI import mechanism, I have already imported some large models from other repositories.
Currently, my target repository is about 1.5GB.