In contrast to the Stand-Alone installation, in which all parts of EEC are installed on a single computer, a Client-Server installation distributes the EEC parts across at least two computers – a workstation and a server.
If a FastObjects database is used for data storage, the server acts as both a file and database server. With this variant of data storage, the application, resources and database do not have to be on one server, but can be installed on three different servers:
If an EOX file is used for data storage, the application and resources do not have to be on one server, but can be installed on two different servers:
A file server provides the application with plug-ins and resources as Windows shares. Depending on whether the application or the resources are on the share, users will have either read-only or also write access to the respective share.
The database server contains a DBMS (FastObjects) that stores the data on the local hard disk of the server. The DBMS is started as an operating system process (see Installation of the FastObjects server).
Another file server provides the resources that are accessed during the runtime.
The client-server installation involves two steps:
- First, the servers are installed by starting the installation on the server that provides the share with the application. During the installation, the target location of the resources must be specified.
- Then, data storage is set up (FastObjects or EOX file). Once all server-based steps are complete, the client installation is realized on each workstation. This is done via another setup wizard that is installed in the subfolder ec_client_setup of the application. To set up a client with administrator rights on a FastObjects database, a parameter is added at the start of the installation file: ec_client_setup_<buildID>.exe /admin.
The installation of the client generates on each workstation a separate ec.ini file, as well as links to the application on the application share.
The above figure shows the folders and the process data traffic of the client-server installation. The read and write rights required for the individual areas are shown.
If EEC is started on the workstation, it reads the folders and files of the application, such as plugins, dropins, features or configuration. Locally, EEC generates caches, and stores the settings in a separate configuration folder. EEC has read and write access to the resources, as well as to the contents via the DBMS. For data storage with EOX files, it is possible to specify read-only or also write access. Client-computer-specific parts of the configuration folder and the workspace folder are always stored locally on the workstations in order to prevent noncompliance with Windows security policies, for example, regarding trusted assemblies (cf. Microsoft: Code Access Security Policy Tool).
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.
Advantages of the Client-Server installation:
Lowest possible administration effort: All key data are stored centrally, and can be stored and updated there.
Disadvantages of the Client-Server installation:
When starting, application data (plug-ins) must be loaded from the server. This can lead to longer starting times. Each client computer requires a valid license.
Note:
Frequently, the FastObjects-DBMS is installed on a workstation at first for practical reasons. This often leads to problems, for example, as such a computer is shut down.