This functionality is only available for certain module packages.

You are here: Administration > Installation variants > Stand-Alone

Stand-Alone

A Stand-Alone installation is set up on a workstation.

After installing and licensing the application, you can start working immediately (see chapter Starting).

Note:

The installation, or parts of it, must not be moved, copied or renamed at the file system level.
Such changes limit the operability of the application, or prevent the application from being executed.

Stand-Alone installation with FastObjects for data storage (standard installation):

All parts of EEC are installed within a folder structure. FastObjects is used as DBMS (see Databases). The DBMS is embedded in the EEC process. The following image shows the installed folder:

Functional configuration image/svg+xml EEC. Workstation artifacts.xml configuration workspace Data access Refers to ec.exeec.inip2plug-insdropinsEEC.resourcesinstallFastObjects DBMSdbserverdb

Stand-Alone installation with EOX file for data storage:

All parts of EEC are installed within a folder structure. An EOX file is used for data storage purposes. Access to an EOX file instead of a FastObjects database can be configured subsequently in ec.ini. The following image shows the installed folder:

The folders plugins and dropins must always be directly below the installation folder (ec).

After installation EEC has to be licensed, before it can start (see Licensing and Starting).

Advantages of the Stand-Alone installation:

There is virtually no installation effort. Without administrative efforts, several EEC versions can be installed easily in parallel on a computer in different folders.

Data storage via EOX file can be realized also as read-only, so that a specific status of the model is maintained.

Disadvantages of the stand-alone installation:

When extending the application area to a team, it becomes more complex to synchronize database contents, for example.