Import from XMI

You can import a package from an XMI (XML based) file. This enables you to move Enterprise Architect Model elements between models, for distributed development, manual version control and other benefits.

Important:
  • 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.
  • If you are importing an XMI 1.1 file that was previously exported with a UML_EA.DTD file, the UML_EA.DTD file must be present in the directory into which the XMI file is being written. An error occurs if the UML_EA.DTD file is absent.

Note:

In the Corporate edition of Enterprise Architect, if security is enabled you must have Import XMI permission to import packages from XMI.

You can import the following formats:

  • UML 1.3 (XMI 1.0)
  • UML 1.3 (XMI 1.1)
  • UML 1.4 (XMI 1.2)
  • UML 2.0 (XMI 2.1)
  • UML 2.1 (XMI 2.1)
  • MOF 1.3 (XMI 1.1)
  • MOF 1.4 (XMI 1.2)

Enterprise Architect can also import the *.emx and *.uml2 files generated by tools such as Rational Software Architect (RSA) and Rational Software Modeler (RSM).

Import From XMI

To import a package from XMI, follow the steps below:

  1. In the Project Browser window, select the package into which to import the file.
  2. Either:
  • Right-click and select the Import/Export | Import Package from XMI menu option, or
  • Select the Project | Import/Export | Import Package from XMI menu option.

The Import Package from XMI dialog displays.
 
ImportXML

 

Note:

To import .emx or .uml2 files, click on the Import EMX / UML2 Files button. Go to Import EMX/UML2 Files.
  1. In the Filename field, type the directory path and filename from which to import the XMI file.
  2. Select the Import diagrams checkbox to import diagrams.
  3. Select the Strip GUIDs checkbox to remove Universal Identifier information from the file on import. This enables the import of a package twice into the same model; the second import requires new GUIDs to avoid element collisions.
  4. Select the Write log file checkbox to write a log of import activity (recommended); the log file is saved in the directory from which the file is being imported.
  5. Click on the Import button.