Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: bockfu on April 22, 2016, 05:24:18 am

Title: Practice for using MDG on project with DBMS backend
Post by: bockfu on April 22, 2016, 05:24:18 am
Can someone share the recommend practice for deploying a MDG when the model is accessed via DBMS.

From the user guide (http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/mdgtechnologies.html), there are two methods:

We have users who access the model two ways:
Method 1: Run from EA installed on local system
Method 2: Run remote desktop with EA UI launched on local system.

So I ruled out 'Import MDG Technologies to Model' as that involves a local path....and I did not want to change the EA installation used via remote desktop.

This leaves 'Access Remote Technologies'.  My observation is every user will have to apply the steps.  I just wanted to verify this was the common practice.

Updated: corrected terminology by changing MTS to MDG.



Title: Re: Practice for using MTS on project with DBMS backend
Post by: qwerty on April 22, 2016, 06:18:24 am
MTS is not MDG. The MTS is just a file that stores (not all) parameters to generate a MDG. So you need to be precise in your question.

q.
Title: Re: Practice for using MTS on project with DBMS backend
Post by: KP on April 22, 2016, 08:48:04 am
(Assuming "MDG" instead of "MTS")

Quote from: bockfu on April 22, 2016, 05:24:18 am
From the user guide (http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/mdgtechnologies.html), there are two methods:
  • Import MDG Technologies to Model
  • Access Remote Technologies

Use 1 if you have one model with many users. Use 2 if you have one user with many models. If you have many users with many models, it's a judgment call.

Quote
So I ruled out 'Import MDG Technologies to Model' as that involves a local path...

er...? It imports the technology directly into the DBMS (model) and then when you open the model, the technology is extracted and processed exactly the same as if it were a remote technology. No local paths involved.
Title: Re: Practice for using MDG on project with DBMS backend
Post by: bockfu on April 23, 2016, 01:16:32 am
Totally missed the second option for 'Import MDG Technologoes to Model':

Quote
To be available to all users of the model, through the Resources window for the model

Followed the steps and working like a charm.

thank you.