Important note: databases that have been loaded in Jedox version 2018.2 cannot be loaded in version 2018.1 or older!
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. If you have an existing Jedox software module and you want to update your version, please read Updating a Jedox Installation in Windows.
The setup will recognize an existing Jedox version 2018.1 or 7.1 or 7.0 (SRx) installation and perform an update.
Step 1 – Run the current Jedox Setup file for Windows by double-clicking and 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.
- Advanced setup
Here you will receive the selection of the components of step 5.
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.)
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 – Selection of the components:
- To install the Jedox SAP Connector, please refer to SAP Java Connector (JCo) Installation before you proceed.
- The R Integration can be installed later, as described in R Installation.
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:
Jedox requires the following software installations: VCRedist 2013, VCRedist 2017, Java Version 8, .Net.
If one of these installations was not found, you will get this dialog window showing the missing software.
With the “Next” button in this dialog window, the missing software except of Java Version 8 will be installed. If Java Version 8 is missing, Jedox Setup will ask you to install this software manually.
Please note that VCcredist installation might require system restart during setup process.
After all required software is installed, Jedox Setup will continue to install Jedox Suite.
Step 12 – Final options:
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”.
Please note that 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. The requirements you will find 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 sep.inc.php) will be adjusted accordingly. In sep.inc.php will be included ‘./sample_scripts/sep.inc.drill_through.php’ instead of ‘./sample_scripts/sep.inc.default.php’.
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 via
“Start – Programs – Jedox Suite – Jedox Web” or via
“Start – Programs – Jedox Suite – Jedox Excel Add-in”.
Administrator login in Jedox Web:
Note 1: to avoid display errors, delete your browser’s cache and cookies before you start Jedox Web.
Note 2: in Windows operating systems with user control, the Jedox In-Memory DB Server is only available for the user who has installed Jedox.
Note 3: : the setup will automatically change the script name in the sep.inc.php script during update to the sep.inc.default.php script ((resp. if Drilldown is enabled to the sep.inc.drill_through.php script), to ensure that a syntactically correct script is used. If you have used a custom script before, you need to re-include it in sep.inc.php after the update.