E3 Server coordinates all E3 modules. It always executes as a service, even in Demo mode, whether it was registered as a service or with the /regserver parameter, and it must also always be executing. It can also be started when a local E3 Studio is initialized, or using a shortcut to execute a Domain (for example, e3admin -start app.dom). It is responsible for:

•Checking and managing usage of licenses for different E3 modules

•Starting, stopping, or monitoring Domain's runtime process (E3Run)

•Opening, editing, or manipulating DOM files

•Controlling user access to Domain objects

•Monitoring other Domain servers and implementing Hot-Standby

E3 Server is capable of working with only one Domain file at a time, and this one is called the open Domain. Domain files can only be manipulated via E3 Server.