Windows Installation


This article describes installation of a full Jedox instance, including the In-Memory DB. For installation of the Jedox Excel Add-in alone, see Excel Add-in Installation (Client Only).

In Windows, you must have administrator rights to install Jedox software. To install and run Jedox, please read first the hardware requirements and the software requirements.

Important: if you have an existing Jedox instance, see the article Updating a Jedox Installation in Windows before starting Setup.


Step 1Download and run the current Jedox Setup file for Windows. Select the language for installation:

Step 2 – Jedox Setup Wizard:

Step 3 – License Agreement:

Step 4 – Setup type
If setup has not detected a Jedox installation on the computer:

Choose the type of setup you prefer:

  • Default setup
    This includes the installation of the Jedox In-Memory DB Server, Excel Add-in and Jedox Web with default settings. This article describes the default setup.
  • Advanced setup
    Here you can select the components to install, such as Jedox Excel Add-in. See also Excel Add-in Installation (Client Only).

If setup has detected a Jedox installation on the computer:

Choose the type of setup you prefer:

  • Repair / Update
    (Displays the previously installed components and allows a new selection of components.)
  • Delete
    Uninstalls the existing Jedox installation and then quits the setup.

The following is the description of an advanced setup. The setup dialog for the default setup is shorter in some cases.


Step 5 – In the default setup, the following components are preselected:


Step 6 – Select the destination directory for the installation.


Step 7 – Definition of the user access:

  • Anyone who uses this computer (all users)
  • Only for the current user


Step 8 – Option to disable the Import Wizard and the Modeler for Jedox Excel Add-in.


Step 9 – Setting other paths:


Step 10 – Setting interfaces and ports:

It is also possible to leave the interface fields for Apache server and for Jedox In-Memory DB Server empty (but not the port fields!). Then, the Apache server and the Jedox In-Memory DB Server will be accessible via all network interfaces. This possibility exists also for the Tomcat server interface. But we do not recommend to leave it empty as the Tomcat server does not require separate user authentication. Moreover, normally the Tomcat server is only used locally.

Note regarding occupied port 80: if you are using anti-virus programs (such as Eset with specific settings), then setup may indicate that that port 80 is in use, although it is not.
Furthermore, Skype uses sometimes Port 80. In this case please uncheck the corresponding checkmark in Skype –Tools –Options –Advanced – Connection.

If the problem persists, you will have to restart the installation and choose Advanced Mode to change the used port to a free one.

Note regarding manually changed ports: if the last setup of Jedox included manual changes to ports and config files, these do not get entered into the registry and the Setup. In these cases, you must stop the Jedox services to unblock these ports before proceeding with the actual installation.

Step 11 – Missing software installations:

In case of missing software installations, a dialog showing the missing software is displayed. You are prompted to install the following software: VCRedist 2013, VCRedist 2017, Java Version 11 and .Net.

Click Next on this dialog to install all the missing software.

Please note that VCcredist installation might require system restart during the setup process.

After all required software is installed, Jedox Setup will continue to install Jedox Suite.


Step 12Final options:

  • Updates
    Subscription of update information.
  • Install / Overwrite Demo Data
    (in „Default setup“ this option is not shown and will be always set as „checked“)

    Install Demo Data: Option if demo data installation does not exist.

    Overwrite Demo Data: Option if demo data installation does already exist.

    If this option is set, the following demo data will be reinstalled: the database “Demo”, the database “Biker”, the folder group “Demo spreadsheets” and the report group “Demo Reports”.
    Note: the folder group and the report group are matched to an internal identifier, so they will be overwritten even if they had been renamed previously. Any changes made to these contents will be lost during the update, so you should only use this option if you have not re-used the mentioned structures for custom contents
  • Enable GPU Accelerator (in „Default setup“ this option is not shown and will be always set as „unchecked“).
    If a suitable graphics card is available, you can activate the GPU acceleration for the Jedox In-Memory DB Server. You can find the requirements in the corresponding Knowledge Base article.
  • Enable Drilldown in Supervision Server (this option you receive only in a new Windows installation).
    When you enable Drilldown functionality, the corresponding files (palo.ini and will be adjusted accordingly. In will be included ‘./sample_scripts/’ instead of ‘./sample_scripts/’.

Step 13 – Existing components are removed and then the new installation process begins.


Step 14 – Completing the Jedox installation:

After this message, you can start the installed software through the Start menu.

Jedox comes with a predefined administrator user account, and both user name and password are initially set to “admin”. These credentials should be changed immediately after installation. See Hardening Jedox for information on making your Jedox installation as secure as possible.

When installation is finished, the following services will run:

  • JedoxSuiteHttpdService
  • JedoxSuiteCoreService
  • JedoxSuiteTomcatService
  • JedoxSuiteMolapService

Notes on installation

  • To avoid display errors, delete your browser’s cache and cookies before you start Jedox Web.
  • In Windows operating systems with user control, the Jedox In-Memory DB is only available for the user who has installed Jedox.
  • Setup will automatically change the script name in the script during the update to the script (or, if Drilldown is enabled, to the script), to ensure that a syntactically correct script is used. If you have used a custom script before, you need to replace it in after the update.