Export all models (entire repository) as HTML

[Viking]

Hi, we have created several models (top level packages) within EA. Each model reflect a domain. The models are interrelated, meaning that they reference each other. We would like to export all models that also users without EA-access can see the content. This was not possible in the past (see also https://sparxsystems.com/forums/smf/index.php?topic=21624.0). My understanding was that EA is becoming more and more a tool that supports EAM. So it should be possible to export all models into one html-site because all together represent the view of the enterprise. Is there a possiblity to export all models at once in the meantime or to integrate the models later? Many thanks in advance, V.

[peterc]

Rather than having each model under their own Root Node, is there any reason that you could not have one Root Node and then each model in a separate Package below that Root Node? You would then be able to export to HTML from your one Root Node.

You should be able to do that retrospectively by creating a Package for each model and dragging everything in the Project Browser from each existing Root Node to the corresponding new Package (but I haven't tried it to prove that everything works as you want!).

If you really want to keep the Root Nodes to work on, could the above be a publication step that you do on a copy of the model? It might depend how often you wish to publish updated HTML pages.

[Geert Bellekens]

With virtual documents you can get them all to publish as one HTML export.

Geert

[Viking]

Many thanks, peterc and Geert. O.K., I will go with virtual documents. V.

[adepreter]

If I were you, I would rather simplify by changing my root packages into sub-packages.
Here is an example of a complex root package published to HTML: http://www.labnaf.one/guidance/index.html

It is easy to do. Here is something I did some time ago. You will need to tune it for your specific case.

1. Create a new single target package where you want your root packages to be moved to.

2. Using SQL Server Management Studio or equivalent, run some SQL to
a) change the package type for the root packages to be moved
Example:
UPDATE t_package set PackageFlags = NULL
WHERE t_package.Package_ID in (
   SELECT  Package_ID FROM t_package
   WHERE PackageFlags like 'isModel=1%'
   AND NOT (Name = 'XXXTRANSFER' or Name = 'XXXProjects')
   )

b) move the selected root packages into the new single target package.
Example:
UPDATE t_package set Parent_ID =  {ID OF MY SINGLE PACKAGE}
WHERE t_package.Package_ID in (
   SELECT Package_ID FROM t_package
   WHERE Parent_ID = 0
   AND NOT Name = 'XXXTRANSFER'
   )

Try first on a test database :-)