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.

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

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 mobileenabler.cfg (Microsoft IIS).

Also take note of the section Installation Procedure.

Licensing

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

Installation Procedure

This section outlines the procedure for installing CSP Mobile.

Single-server installation:

  1. Install the Web layer and the application layer on the Web server.
  2. Check the settings in the file web.config. Change the entry teamserver, entering the required CSP Server as the "value".
  3. If you are using databases that require an integrated login, you can either store the domain user account for authentication in IIS or you can adjust the settings in the Connect dialog box in Cockpit (see FAQs and problems).
  4. Configure the Windows Firewall and add the exceptions for World Wide Web Services (HTTP) and Secure Web Services (HTTPS).
  5. Use a Web browser to test whether it is possible to open the page http://<name of the computer>/CubewareBI.
  6. If necessary, set up the SSL connection.

Multi-server installation:

  1. Install the Web layer on the Web server and define the required application layer in the Setup Wizard.
  2. Check the settings in the file web.config. Change the entry teamserver, entering the required CSP Server as the "value".
  3. If you are using databases that require an integrated login, you can either store the domain user account for authentication in IIS or you can adjust the settings in the Connect dialog box in Cockpit (see FAQs and problems).
  4. Configure the Windows Firewall and add the exceptions for: World Wide Web Services (HTTP) and Secure Web Services (HTTPS).
  5. Use a Web browser to test whether it is possible to open the page http://<name of the computer>/CubewareBI.
  6. If necessary, set up the SSL connection.
  7. Install the application layer.
  8. Configure the Windows Firewall and add the following exceptions: Port range (4444+), and where necessary add <installation path>\Mobileworker.exe and MobileEnabler.exe.
  9. Ensure that the CSP Mobile service is running.

App installation:

  1. Install the app on the mobile device. You can download the app from the Apple AppStore (iOS) or Microsoft Store (Windows).
  2. If you wish to log into the CSP Server using your Windows user account, enable Windows Authentication in the settings for the app.
  3. Start the app and enter the user and password you wish to use to log into the CSP Server. Enter the Mobile server (the computer on which the Web layer has been installed) in the Server field.
  4. You can store a Mobile server in the settings for the app. This is then automatically preset when you call the login screen.
  5. The CSP Server is in principle specified in the file web.config. If you wish to use a different CSPCSP Server, you can also store this in the settings for the app.

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 that 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 via the mobile device.

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:

  1. 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.
  2. On the next page you can determine where the virtual folder of IIS is to be located. You can change this folder as required.
  3. 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.
  4. 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 that 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.

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 that 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 installation of both setup routines, the application will be available immediately via the mobile device.

Was this article helpful?

We're sorry to hear that.