Export XMI limitations

[bholtzman]

Hi all,
Please forgive me for not reading all of the documentation. I was experimenting with using the Export XMI feature interchangeably with Project Transfer to generate an EAP file from a server-based EA model. I can export an XMI quickly over an http cloud connection but can only use Project Transfer with an ODBC connection and it takes longer.

I observed that the XMI export seems to be missing some of the tagged values from the model. Is this typical? It wasn't all of them, just some. Is there some basis for including some versus others? What other ways might an EAP file generated using an XMI export differ from an EAP generated by a Project Transfer?

Thanks for indulging me!

Bill

[Geert Bellekens]

Hi Bill,

Xmi export/import should transfer all content of the model, but none of the meta-content such as templates, tagged value types, users, ...

In order to transfer these things use Export/Import Reference Data

Geert

[Mauricio Moya (Arquesoft)]

Also you have to be careful if having different root nodes in you EAP file, and relationships between elements in different root nodes. If you only export one of the root node, you will miss the connectors (as expected). If you pretend to fully transfer a EAP file into a database, it is better to use model transfer. XML export ignores: scripts, profiles, templates, document templates, tag values, images, etc.

[crequena]

Hi,

We had some performance issues when performing a model transfer from remote repositories, specifically with MSSQL databases.
Hence, I have developed an open-source library to perform model imports and exports without using EA's API.

If you know how to use a Java library, you could give it a try: https://krequena.github.io/eamodeltransfer/.

[Mauricio Moya (Arquesoft)]

Hi,

We had some performance issues when performing a model transfer from remote repositories, specifically with MSSQL databases.
Hence, I have developed an open-source library to perform model imports and exports without using EA's API.

If you know how to use a Java library, you could give it a try: https://krequena.github.io/eamodeltransfer/.

Humm, it sounds dangerous... specially the part of "without using EA's API". Could you explain a little the strategy used to transfer the data? is it the same as "Project transfer"? If so, and you pretend to transfer from two MSSQL databases, why not use the native replication of the database in SQLServer Management studio?

[bholtzman]

Thanks Geert and all. I am just staying with Project Transfer to insure I get everything, although I see that I can also use Export Reference Data.

Bill

[jacksnb]

Is there any way to get around the export having different root nodes in the EAP file, and keeping relationships between elements in different root nodes?

[Paolo F Cantoni]

Is there any way to get around the export having different root nodes in the EAP file, and keeping relationships between elements in different root nodes?

Hi Jack?,

Can you be more explicit about what you are asking?  Perhaps with a diagram or two?  It is possible to transfer packages between repositories and have them in different branches.  However, there are strict limitations and so  you need to indicate what you are trying to do.

HTH,
Paolo