This functionality is only available for certain module packages.

You are here: Administration > Installation > Client-Server-Installation

Client-Server Installation

Familiarize yourself first with the special characteristics of the client-server installation. For this, you will find an overview and background information in Installation variants.

The installation is carried out as follows:

  1. Choose the distribution of the EEC parts adapted to your requirements and IT structure to one or several servers.
  2. Create the folder for resources and the FastObjects server.
  3. Share the created folders for remote access.

Note:

Mapped drives or UNC paths cannot be specified during the server installation. For the server installation the Setup file is to be copied to the server and there installed locally.

  1. Copy the installation file to the server on which the application is to be located later on.
  2. Execute the setup file to start the setup.
  3. Follow the instructions of the setup wizard.
  4. Select the installation variant Client-Server-Installation.
  5. Install the database server.

Note:

Instructions on how to install the database server can be found in Installation of the FastObjects server.

  1. On the server connect the network share of the resource folder as a network drive (map) and enter the path into the initialization file (for example ec.ini) (see com.mind8.global.resourcePath).
  2. For all clients, enter the valid defaults for resource path and DB URL in the file ec_client_setup\ec_client_setup.cfg.

The DB URL consists of the protocol, host name and database name, for example: fastobjects://hostname/<Name of database>.

You obtain the database name from the database server configuration (also see Adding a database to the DB server configuration).

Note:

Please note that localhost always points to the computer on which the process is currently executed.

Since client computers are generally installed without administrator rights on the database, but with one client at least being assigned such rights, a parameter must be transferred at the start of the installation with the client that has administrator rights.

Take the following steps on each client computer without database administrator rights on which EEC is to be used:

  1. Map the installation folder of the server and the resource folder to a drive.
  2. Copy the subfolder ec_client_setup from the server to the client.
  3. Start the file ec_client_setup_<buildID>.exe and use it to carry out the local installation on the client.

If the UNC paths are not available, these can be edited subsequently in the initialization file (for example ec.ini).

Take the following steps on each client computer with database administrator rights on which EEC is to be used:

  1. Map the installation folder of the server and the resource folder to the client on a drive.
  2. Copy the subfolder ec_client_setup from the server to the client.
  3. Start the file ec_client_setup_<buildID>.exe with the parameter /admin and use it to carry out the local installation on the client.
  4. If the UNC paths are not available, these can be edited subsequently in the initialization file (for example ec.ini).

Afterwards EEC has to be licensed, bevore it can start (see Licensing and Starting).

Note:

Never start a Client-Server installation without the correct setting of the folders Workspace and Configuration in the files ec.ini and ec_admin.ini.

Each client has its own ec.ini and ec_admin.ini.

If this has already happened, follow the instructions in the chapter Repairing a Client-Server installation.

Optimizations:

Property Comment
RAM See initialization parameter -xmx

More: