Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Export to XMI

You use the 'Export Package to Native/XMI File' dialog to export a Package from your model to a file in one of several XMI (XML-based) or Native formats. The dialog, by default, allows exporting to XMI 1.1, XMI 2.1, Enterprise Architect's Native XML or Native XEA format. The exported file contains all the information required for completely round-tripping the Package within Enterprise Architect; that is, performing Enterprise Architect-to-Enterprise Architect transfers.

Access

Select a Package in the Browser window, then:

Ribbon

Publish > Model Exchange > Export > Native Format

Publish > Model Exchange > Export > XMI Format

Keyboard Shortcuts

Ctrl+Alt+E

Export Package to Native/XMI file

Option

Action

See also

Package

Displays the name of the currently-selected Package.

If this is not the required Package, click on the Browse package button and select the correct Package.

Filename

Type in the file path of the XML/XEA file to be generated, or click on the Browse. button and browse for the location.

Options

  • 'Native XEA' - Select this option to export the selected Package to Enterprise Architect's Native XEA format
  • 'Native XML' - Select this option to export the selected Package to Enterprise Architect's Native XML format (default if you have selected the 'Native Format' menu option)
  • 'XMI 1.1' - Select this option to export the selected Package to XMI 1.1 (default if you have selected the 'XMI Format)' menu option)
  • 'XMI 2.1' - Select this option to export the selected Package to XMI 2.1
 Publish Model Package Native File Formats

Generate Merge file using Baseline Version

This option is enabled when:

  • 'XMI 1.1' is selected and
  • The selected Package has a baseline

Click on the Browse. button to open the 'Baselines' dialog and select the baseline.

Once export is complete, the Merge File will be generated by comparing the selected Package with the selected baseline. The Merge File will be generated in the same location as the XMI file, with the same name as the XMI file but with the suffix _Merge.xml.

This file is used to merge the contents of a Package with that of the XMI file, using the 'Merge Package with XMI' dialog.

 Manage Baselines in Model Merge with XMI Using Merge File

Format XML Output

Select this check box to format the output.

Note that Native XEA format doesn't support this option, so the option is grayed out for that format.

You can set a default selection for 'Format XML Output' by selecting 'Start > Preferences > Preferences > XML Specifications > Format XMI Output'.

View XML

Click on this button to view the exported XML file.

This button is disabled when 'Native > XEA' is selected.

Export

Click on this button to initiate the Package export.

Close

Click on this button to close this dialog.

Help

Click on this button to display this Help topic.

Progress

Monitor the progress of Package export.

Notes

  • In the Corporate, Unified and Ultimate Editions of Enterprise Architect, if security is enabled you must have 'Export XML' permission to export to XML
  • Alternative Images used in the Package being exported are not included in the exported Native/XMI file, unless the 'Export Alternate Images' option is selected in the 'XML Specifications' section of the 'Preferences' dialog
  • The Log file for the Package being exported is not generated unless the 'Write Log' option is selected in the 'XML Specifications' section of the 'Preferences' dialog
  • XMI 2.1 files exported by Enterprise Architect Version 7.0 or later might not be correctly imported by versions of Enterprise Architect earlier than Version 7.0
  • A Native XML file exported by Enterprise Architect Version 15.0 or later cannot be imported by versions of Enterprise Architect earlier than Version 15.0
  • A Native XEA file exported by Enterprise Architect Version 16.0 or later cannot be imported by versions of Enterprise Architect earlier than Version 16.0

Learn more

Prev Next