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


Enterprise Architect enables you to easily import complete sample models (Packages), including all necessary model information, code and build scripts. These sample patterns make it simple to explore and try out the Visual Execution Analyzer. You can generate an example model for:

  • Java
  • Microsoft.NET
  • Microsoft C++
  • PHP Apache

Access Project | New Model (Ctrl+Shift+M) > VEA Examples

In Project Browser, right-click on Package | Add a Model using Wizard > VEA Examples

Display Samples



See also


Select the appropriate technology.


Displays the samples available for the selected technology; select the required sample to import.

description field

Displays a description of the selected sample.

Destination folder

Browse for and select the directory in which to load the source code for the sample.

Use Local Path

Enable the selection of an existing local path to place the source code under; changes the 'Destination folder' field to a drop-down selection.

Compiler command

Displays the default compiler command path for the selected technology; you must either:

  • Confirm that the compiler can be found at this path, or
  • Edit the path to the compiler location

Local Paths Local Paths Dialog

Edit Local Paths

Many VEA examples specify their compiler using a local path.

The first time you use any sample you must click on this button to ensure the local path points to the correct location.

The 'Local Paths' dialog displays.


  • If required, you can define custom samples by adding files to the AppSamples directory where Enterprise Architect is installed; top-level directories are listed as Technologies and can contain an icon file to customize the icon displayed for the technology
  • Directories below this are defined as groups in the patterns list; the patterns are defined by the presence of four files with a matching name: a zip file (.zip), XMI file (.xml), config file (.cfg) and optional icon (.ico)
  • The config file supports these fields:
         -  [provider], [language], [platform], [url], [description], [version] - all displayed in the 'description' field
         -  [xmirootpaths] - the root path of the source code in the exported xmi; this is replaced with the selected destination folder when
            the user applies the application pattern

Learn more