Question about Server Based Repositories

[mark.tootell]

Hi
I recently created a server based model for one of my development teams which is working extremely well for us. Another team is wanting to use the same approach for a new development and has asked me to configure it for them however I have run into an issue.
The first one was set up using the instructions and a newly created database, but there is a reluctance to create another new database for the new development. Is it possible to have multiple models on one database? If so, how do you set each on up (the instructions in the manual start from a new clean database)?
Thanks

[Uffe]

Hello Mark,


No. One database equals one repository equals one project.

You can run multiple databases on the same server instance, of course, but not multiple EA projects in a single database.

That said, you can allow teams to work on separate modelling activities side-by-side in the same project. I usually set up different root nodes for the different teams in this situation.
For this approach to work properly, all team members need to be disciplined and refrain from reusing model elements across the team boundaries or you'll quickly end up in EA's version of dependency hell.

It should also be noted that certain policies are set at the repository/project level (eg access, version control, and various other stuff), so if the teams need these policies to be set in different ways this approach won't work.


/Uffe

[Geert Bellekens]

Mark,

It is entirely possible to host multiple model in a single repository, regardless of whether the repository is a local .eap file or a "real" database on a server.

Just make different root packages for each different model.

What you cannot do is use project transfer to transfer different .eap repositories into a single DBMS repository.

So you take the largest of your .eap files and transfer that using model transfer, and then move the rest of the .eap file another way.

This "other way" can either be xmi export/import, or (since v11)  copy/paste of packages between the model in .eap and the model on the DBMS.

The latter is definitely the fastest and easiest option.

Geert