Add/import .eap to version controlled dbms model?

[ssands]

apologies in advance if this is covered somewhere and I haven't seen it. I have a SVN version controlled, SQL -Server based model. There is another .eap model that I would like to merge with it, so that both are now in SQL Server and version controlled.

Can someone suggest a way to do this or point me to docs on this?

Thanks in advance,
Stu

[Helmut Ortmann]

To merge something you have to know what you are merging.

Some questions that may help you:
- Is the *.eap file you want to merge into your DBMS is something complete different?
- Are there common things?
- Are they mostly the same?
- What do you mean by merge?

From the technical point of view it's easy:
- Make sure you've saved the SQL Repository
- Export the packages to *.xml (one or more, what is better, it depends)
- Import the *.xmi files at the right location in the DBMS-Package structure


A little background information:
Two elements are the same element if they have the same unique GUID. If not they are different elements.

When you import an XML file over an existing package, ALL information in the current package is deleted first; before you import the XML file, please make sure you do not have important changes that you do not want to lose.

I you want new elements click on strip GUIDs.

Be careful and test import until you got the understanding.

If you import different things (GUID is different) it's easy. If not the import overwrites existing things, in extreme a whole package and it's content.


Helmut

[qwerty]

If you understand merge as "add" then ex-/import the relevant packages via XMI. If you understand merge as "decide which of both similar elements is the one I want" then use your brain.

q.

[ssands]

Thanks for the replies.

At this point we are assuming that all imported elements are unique and will have to rationalize them once they are all in the same model. (Bringing together a couple of teams who previously worked separately).

I ended up doing the xmi export of the model to import and then imported that into it's own package on the "main" model (SQL Server, SVN). That seems to work.

Now we have the hard problem of rationalizing components that are unique but represent the same thing, and having to pick the aspects of each element that we keep and adjusting diagrams accordingly.

I think that is just a manual effort, but achievable.

Thanks for the prompt replies.

[qwerty]

Now we have the hard problem of rationalizing components that are unique but represent the same thing, and having to pick the aspects of each element that we keep and adjusting diagrams accordingly..

That's the part where I referred to the brain work  

q.