Transfer from SQL tp Local EA File and Back

[OmarSoto]

Good Day:
 I have am using EA with the data residing in SQL Server.  I have a need to export a root node or an individual package to a local EAP file so I can take it on my laptop and once finished, reload it to the SQL model.  How can I do this, or where in the docs can I see how to do this.

thank you,

Omar

[«Midnight»]

Hi Omar,

First, you can send the model to an EAP file from the main menu via Tools | Data Management | Project Transfer. There are several options, which are self-explanatory. Remember that this is an all-or-nothing proposition; the target model will be erased. Be sure you've got your versions correct before restoring the model from home.

[HINT: You can use this same method to make a backup copy before you do the transfer. This will same you some real grief somewhere down the line.]

The resulting EAP file will often be fairly large. If you are sending it via mail you'll want to compress it somehow. In general EAP files compress very well.

Another way would be to export the model to XMI. This will provide you with a text stream, allowing you to compress and send it in a variety of ways.

You can do this by selecting the root node in the Project Browser tree:

• Make sure the root node is actually highlighted.
  
• Right-click the root node and select Export Model to XMI.
  
• Follow the directions to send the model to a file.
  
• Import the model at home.
  
• Reverse the process to bring the project back to work.

This can be a bit tricky the first time, so make a backup copy and experiment a bit. You'll probably want to ensure that you don't strip GUIDs when you reload. This will keep the identity of your element the same across transfers. [This last part is more important when models are shared between developers, but I wanted to guard you against 'drift' of your models when that time comes.]

HTH, David

[OmarSoto]

I got those parts OK.  The part I am wondering about is how to I bring the changes back into the SQL Server model for a specific package.

Omar

[«Midnight»]

OK, that's different... Or perhaps not.

If you've extracted the entire model by either means above - see the warning below - and you are absolutely positive the changes are entirely confined to a single package, you can do an extract the package in question and import it over the same package in the other model.

[WARNING: If you used the XMI method of transfer, and stripped the GUIDs when you imported at home, you may have a small problem. When EA strips the GUID values from elements (and everything else) it essentially created a set of entirely new objects, which 'just happened' to have identical properties to the old ones. This is most useful for cloning a model. However, the GUID value is what EA uses to identify elements. You run a serious risk of either importing a second set of objects into your work model, or breaking links between the elements in your package and other elements elsewhere in the model. This is way I mentioned this in my earlier post.]

Now, if you used the Data Transfer method, you can just extract the package in question to XMI and import it into your model at the correct point. You will use the same process as I mentioned earlier but instead of selecting the root node you'll select the package you want to export or import. The shortcuts are the same (ctrl-alt-I/E) but the context menu prompts change slightly to Import/Export | Import (or Export) package from (to) XMI file.

Remember the bit about not stripping GUIDs when you import. Make a copy of the entire model - to a 'throwaway' EAP file - and practice this several times with different targets. You cannot undo this operation, so you want to fully understand it before you go too far.

Once you get the mechanics worked out, look up "Contolled Packages" (no quotes, but note the spelling) in the EA docs. Perhaps this method will help you extrract the portions of the models you work on, once you have an entire copy in both locations.

HTH, David