Deploying or importing a MDG Technology

[Alfred Crombez]

I created a new MDG Technology that contains several model templates. From the documentation I could deduct that to make the MDG Technology available, you can either import it into a model or deploy it on EA program files, other directory, or network share.

When I import the technology, I can see it in the resources but the model templates are not available in the "add model wizard". However, if I deploy it on a directory, the model templates become available in the "add model wizard".

Since we are storing all our models in a single SQL Server model, I would prefer to add the technology in there for all users so that I don't need to foresee an additional network share for deploying the technology. Can this be done somehow?

Thanks,
Alfred

[Oliver F.]

You can put your MDG technology XML file onto either a shared network volume or a HTTP server.
Afterwards your users will have to point EA to this directory (settings->MDG Technologies, then Advanced... opens the file dialog in which you can add or remove paths).

I hope this helps.

[Alfred Crombez]

Thanks Oliver. The option you describe is the one I am currently using. I would prefer though to import the MDG technology into the shared model in our SQL Server model database so that we don't need to refer an additional share.

However, if I import the technology into the model, it is available in the "Resources" tab of the model, but the model templates are not available in the "add model wizard". I have the impression that the model template part of the MDG technology is not imported into the model. Maybe this is a limitation of the tool (or done by design as such).

[«Midnight»]

Alfred,

Importing MDG Technologies - versus having them load at startup time - is an obsolescent method. Many MDG features will not work correctly or even at all if you work this way.

For newer MDG Technologies, those developed since EA 7.0 came out, the only safe way to go is the load from location route.

By using a common URL (or several) to point to the technology files you should be able to get the effect of sharing with minimal overhead. You still need to set up each local EA installation to use the locations, but the result is stored in the registry and thus will apply to all EA sessions (and models) opened after that point.

Yes, that means new users 'joining' the model still need to go through a setup process (to set the MDG location), but that's life...

David

[Alfred Crombez]

Thanks David for confirming not to deploy MDG technologies by import. It is clear now for me that the network folder deployment is the best way to go, for now and for the long term.

-Alfred