Skip to main content

Installation

Installation Notes

Distributed Installation

The entire application can be installed on a single computer (the Web server) or can be distributed over several machines.

The machine on which the application layer is running should not have any other software on it, since both the memory and processor are under a heavy load if there are many users.

Our recommendation is a distributed installation (multi-server).

Note:

If you wish login to be performed using the integrated security functions, there are a number of issues that need to be taken account of with respect to the way in which the individual components are distributed over various computers.

The authentification mechanism Kerberos can currently only be used successfully in a distributed application (Multi-Server Installation).

Running the Setup

This setup supports the following possibilities for installation:

If your Web server is to be used for a number of applications, the setup can be carried out in two stages. In this case, only a very small part of the software is installed on the Web server (Web layer). This part requires little memory and little CPU performance. The application layer can then be installed on one or more machines as master or slave. The application layer can be installed on another machine or on several other machines as master and slave(s). The distinction between master and slave(s) is made at installation time, but can also be controlled via the file webengine.cfg (Microsoft IIS).

Licensing

Nolicenses are required in order to install the application layer and the Web layer.

Single-Server Installation

A single-server installation includes both the Web layer and the application layer. Both are installed together on a single computer.

Note: When there is already a multi-server installation on the computer, you must deinstall it before performing a single-server installation.

Start the Setup program:

  1. After a couple of pages you will come to the page which allows you to select the installation type. Select IIS - Single Server.
  2. Then you will be asked to specify the target folder for the application files.
  3. On the following page you can determine where the virtual folder of Microsoft IIS is to be located. You can change this folder as required.
  4. Next define the temporary folder. All temporary files are stored in this folder. Please note: All users must have the access permission "Full control" for this folder.
  5. Start the installation by clicking the Install button on the last page.

After installation, the application will be available immediately under the following URL: http://<Name of the computer>/Cockpit10.

Multi-Server Installation

The Setup program must be run twice (or more) to complete a multi-server installation. Once on the machine on which the Web Server runs and once (or more times) on the machines on which the actual application will run (once for the application layer master, and once for each application layer slave). The order of installation is only important for the application layer since, in this case, the master must be installed first and then the slave. It makes no difference whether the Web Layer is installed before or after the application layer.

Note: When there is already a single-server installation on the computer on which you want to install the web layer or the application layer, you must deinstall it before performing a multi-server installation.

Installing the Web Layer

This section covers the setup on the machine on which the Microsoft IIS is installed. Start the Setup program:

  • After a couple of pages you will come to the page which allows you to select the installation type. Select IIS - Multi-Server - Web Layer.
  • On the next page you can determine where the virtual folder of IIS is to be located. You can change this folder as required.
  • In the next step, you will be asked to enter the Name of the computer on which the application layer is installed/will be installed. This entry is not case-sensitive. Make sure that the name is entered correctly, otherwise the Web layer will not be able to communicate with the application layer and the entire application will not run.
  • Start the installation by clicking the Install button on the last page.

Installing the Application Layer Master

This section covers the setup on the machine on which the runtime files are to be installed and which is to act as the master.

Start the Setup program:

  1. After a couple of pages you will come to the page which allows you to select the installation type. Select IIS - Multi-Server - Application Layer Master.
  2. Then you will be asked to specify the target folder for the application files.
  3. Next define the temporary folder. All temporary files are stored in this folder. Please note: All users must have the access permission "Full control" to this folder.
  4. Start the installation by clicking the Install button on the last page.

Installing the Application Layer Slave

This section covers the setup on the machine on which the runtime files are to be installed and which is to be defined as the slave. Please note: The application layer master must already be installed when you call the setup program for the slave.

Start the Setup program:

  1. After a couple of pages you will come to the page which allows you to select the installation type. Select Multi Server - Application Layer Slave.
  2. Then you will be asked to specify the target folder for the application files.
  3. Next define the temporary folder. All temporary files are stored in this folder. Please note: All users must have the access permission "Full control" to this folder.
  4. Then you will then be asked to specify the computer name of the machine on which the application layer master has been installed.
  5. Start the installation by clicking the Install button on the last page.

After both setup programs have run, the application will be available immediately under the following URL: http://<ComputerName>/Cockpit10.

Was this article helpful?

We're sorry to hear that.