Jedox Web Services and Configurations


Jedox Setup installs the following four services for Jedox Web:

  1. JedoxSuiteHttpdService:
    This service is an extended Apache Webserver, containing the program code for the Graphical User Interface (GUI).
  2. JedoxSuiteCoreService:
    This service handles the data of workbooks, internal formula calculation, database access, load/save procedures, etc.
  3. JedoxSuiteTomcatService:
    This service provides the functionality of Jedox Integrator (ETL), Jedox Analyzer, and Scheduler.
  4. JedoxSuiteMolapService:
    This is the Jedox OLAP server, where the “real” databases and system databases are stored. The latter are necessary to maintain internal configuration data.

To end Jedox Web you have to stop all four services.
To restart Jedox Web, start the services in reverse order: 4 -3 -2 -1.

After installation, the services are started automatically.
You can then access Jedox Web in your web browser at this address:
http://localhost (from the same machine)
http://server-network-address (from a remote machine).

Jedox Web Configuration Files

The Apache Webserver component (JedoxSuiteHttpdService) is configured (apart from the standard Apache configuration via the files httpd.conf, php.ini, etc.) in the file config.php in the directory …Jedox Suite\httpd\app\etc. Here you can specify the connection to a Jedox server that the GUI uses for storage of internal configuration data.

The Jedox Web Core component (JedoxSuiteCoreService) is mainly configured via the file …Jedox Suite\core\config.xml (Windows) or …/core-Linux-i686/etc/config.xml (Linux).

The (main) Jedox connection is configured in the file …\Jedox Suite\core\palo_config.xml (Windows) or …/core-Linux-i686/etc/palo_config.xml (Linux).

Default Configuration

By default, Jedox Web is installed with the following settings. Note that any changes to default port settings must be noted in the related configuration files. See SSL Configuration for a Standalone Installation for more information.

  • The Apache Web server component listens only to the localhost interface ( Port 80 (or port 443, if using SSL). 
  • The Apache Web Server communicates with the Core Server on port 8193.
  • The Jedox OLAP Server listens only to the localhost interface (, Port 7777. This port is also used by the Apache Web Server and the Core Server to store the internal configuration data on the Jedox OLAP Server.
  • The Apache Web Server communicates with the Tomcat Server (Jedox Integrator, Jedox Analyzer and Scheduler) on Port 8010.
  • The admin account has the password “admin” for both Jedox Web as well as for the Jedox OLAP Server.
  • The Jedox Integrator Web Client communicates with the Jedox Integrator Server on port 7775.
  • Tomcat Service can use 1024 MB memory maximum by default.

Turn off Password Storage in the Login Browser

By default, password storage is offered in the login browser. If you don’t want this, you have to replace “false” with “true” in the file …\Jedox Suite\httpd\app\etc\config.php in the following entry:

// enable browser autocomplete for passwords in login screen

After changes, the service JedoxSuiteHttpdService must be restarted.

Changing maximum memory for Tomcat Service

The memory consumption of the Tomcat Service is limited by the maximum heap size: this is the maximum amount of heap memory the Java Virtual Machine (JVM) is allowed to allocate. Especially on a 64-bit system it is convenient to assign more memory than the default 1024 MB.

Changing on Windows:

  1. Change value for Max_Memory in file …\tomcat\bin\setenv.bat.
  2. Execute …\tomcat\bin\serviceRemove.bat.
    (This stops and removes the Service)
  3. Execute …\tomcat\bin\serviceInstall.bat.
    (This installs and starts the Service)

Changing on Linux:

  1. Stop the Tomcat service via ./ stop tomcat
  2. Change value for Max_Memory in file …/tomcat/bin/
  3. Restart the Tomcat Service via ./ start tomcat

Accessing the Jedox OLAP Server from different Client Machines

It may also be necessary for users to access the Jedox OLAP Server component of Jedox Web from Excel Clients on different machines. In this case, you must update the palo.ini and make other changes to configuration files.

  1. Changes in the file …\olap\data\palo.ini:
    Change the entry http “” 7777 to either http “” 7777 or http <SERVER-IP> 7777.
  2. If you enter a static IP other than, you also need to change other configuration files:
    In …\httpd\app\etc\config.php, the entry define(‘CFG_PALO_HOST’, ‘’) needs to be changed to the Server IP used in palo.ini.
    In …\core\palo_config.xml, the entry <host></host> needs to be changed to the Server IP used in palo.ini.
  3. Changing the Jedox OLAP Server port:
    Change the port entry http 7777 to the new port.
    This change must also be made  in …\httpd\app\etc\config.php for the entry define(‘CFG_PALO_PORT’, ‘7777’);
    and in …\core\palo_config.xml for the entry <port>7777</port>.
  4. The Jedox services need to be restarted after making these changes in order to apply these settings.

Additional Core Configuration

The most important configuration options for the Jedox Web Core Server are defined in the file …\core\config.xml (Windows) or …/core-Linux-i686/etc/config.xml (Linux).

These are:

  • <logging level=”info” ignore_repeated=”true”>
    Here you can define which log level is generally used.
    Available log levels are critical, error, warning, notice, info, and debug.
    Level defined in <logging> tag is default log level (fallback) so you can omit level definition in <logger> tag.
  • <logger level=”info” target=”…/log/core.log” />
    Here you can define which log level is used for the named individual logger and where the log message is written to (additional info).
  • <session><timeout seconds=”300″/>
    Here you can define the time (seconds) after which an orphaned user session will be closed (this is a session with no logout, where the browser window was simply closed).
  • <autosave> <interval seconds=”900″/>
    Here you can define the intervals at which the core creates a copy of the currently opened and modified Jedox spreadsheets (designer mode only).
  • <view_independent_calculation scope=”worksheet”>
    Possible options: worksheet, workbook, application.
    Normally formulas are only calculated for the visible area (plus dependent ones).
    Until Jedox 3.3, the formulas were only calculated for the current sheet. Starting with Version 4.0, an extension of the calculation range can be set. But an extension should be made only when necessary, because the performance will suffer.
    With the entry “worksheet” (default entry) the calculations are limited on the previous formulas in the current worksheet.
    With the entry “workbook” the calculations are limited on the previous formulas in the current file.
    With the entry “application” all previous formulas are calculated in all opened files of the current Jedox session.

Changing the passwords for admin and _internal_suite

The Jedox OLAP Server is used as an important backend for metadata storage by Jedox Web. Because of this, both the UI (Apache) and core need to have admin access to the Jedox OLAP Server. This access is configured in the configuration files …\httpd\app\etc\config.php and …\core\palo_config.xml. As of version 3.2 a special user “_internal_suite” with a randomly created password is used for this.

When changing the Jedox admin password (via Jedox Studio User Manager or Jedox Excel Add-in), no changes in configuration files are necessary.

If you change the password for user _internal_suite, then the following change is also needed:

in …\httpd\app\etc\config.php  the line

define(‘CFG_PALO_PASS’, ‘old_password’);

After that, the service “JedoxSuiteHttpdService”  must be restarted.