Administration Panel

The Administration panel (shown below) and authorized access areas are visible to users with at least R rights for one of the following objects:

  • ste_users
  • ste_conns
  • ste_logs
  • ste_licenses
  • ste_sessions
  • ste_settings
  • ste_perf
  • audit

Users, Groups, Roles

Here you can edit users, groups, and roles for each Jedox connection (i.e., the connection to an OLAP server running behind Jedox Web) for which you have access rights. You can create or delete users, groups, and roles or change their details if you have at least D rights on the objects involved in user management (user, group, password, and rights). Otherwise, you will get an error message when you select a connection from the drop-down list in the user management settings.

When assigning rights within roles, we distinguish between Splash (S), Full Control/Delete (D), Write (W), Read (R), and No Access (N). For a legal object, only those rights that can actually be granted appear in the list.


Here you can create connections of any type that can be used as a reference in Jedox Integrator. The connections that are defined here can be used by multiple Integrator projects. Connection type JedoxOlap is used in all Jedox components, while type ODBC is used only in Jedox Web. All other connection types are used only in Jedox Integrator. Permissions can also be defined here.

Connections to Jedox OLAP and ODBC connections to relational servers can be created, edited, and deleted. Connections created here can be used in Jedox Spreadsheets by referring to their name. In the case of In-Memory DB server connections, they can also be used in Integrator projects as Jedox Global connections.

Jedox connections require specification of the network interface and port where the In-Memory DB server is accessible. By default, the localhost connection already exists and points to the In-Memory DB server included in the installation. You can create additional connections to other In-Memory DB server instances in your environment.

Jedox connections also require a username and a password. However, it is possible (and usually recommended) to omit these fields in the following two scenarios:

  1. The connection points to the In-Memory DB server that is included with the standard installation, and is configured to be used by Jedox Web for the storage of metadata and authentication of Jedox Web users. This is the case for the default localhost connection in standard installations.
  2. The connection points to a separate In-Memory DB server that uses the same System database (and thus the same set of users) as the internal one.

The username and password fields can be omitted by setting the checkbox to Use Login Credentials in the Connection Settings dialog, as shown below:

Setting this option ensures that every time this connection is used, it will happen in the context of the Jedox user who is currently logged in, and that user’s access rights are applied. In the first scenario above (connection pointing to the internal server), no additional session will be created for such a connection, and thus no additional license seat will be used. Note:  the interface entered for the connection must be exactly the same as the interface specified in the config.php file for the CFG_PALO_HOST key. By “interface”, we mean not only the same physical server, but the same “address” you are using, such as internal IP or internal/external DNS.

By contrast, you can choose to specify a username and password and not set the Use Login Credentials option. In this case, any instance of this connection will run in the specified user’s context, with that user’s access rights, and an additional session will be created in the In-Memory DB server. The default connection localhost_static is configured in this way. Such a connection can be useful for Integrator projects that require a specific user or set of access rights.

Internal connection

This connection is defined in the configuration files of Jedox Web to the In-Memory DB server with the metadata and the System database for the authentication of the users. This connection does not exist as an object in the Connection Manager, and it cannot be changed.

You have access to the internal connection only if you have a role with full rights on all of the following objects:

  • user
  • group
  • password
  • rights

Note: If you have no “visible” access to a particular connection, you cannot use that connection in workbook formulas. Previously, such connections could be used for back-end purposes, such as changing a password via a static connection with admin credentials. On all levels, you are only able to work with connections they have access to.


Here you can find log messages for the installed Jedox modules. They can be sorted in a variety of ways:

  • by Log Type (Apache, Spreadsheet Server, OLAP Server)
  • by Log Level (Warning, Error)

Selection changes are only displayed after clicking the Refresh button. The log messages can be exported as a CSV file. The old ones, renamed Tomcat messages (e.g. file.log.1) are not displayed.

The log messages of the supervision server (SVS) are also displayed.


Here you can activate and manage your licenses. Click on the links below for more detailed descriptions about these topics:


Here you can find the running sessions. Your own session is marked with an asterisk. Double-click on a user session to get the current OLAP jobs and the license used.

To stop a job, select the corresponding user session and then the desired job in the “Active jobs” tab. Click on the “Stop Job” button (indicated below) to cancel this job.


Here you can find various settings, such as the default storage path and data for sending emails. They can be changed with a double-click.

For more details, see Overview of Jedox Web Settings.


Jedox Performance Monitor can log and display information for several key performance measures, including system hardware resources, number of logged-in users, etc.

You can find a more detailed description in the article Performance Monitor.


OLAP lets you store audit information for specific cubes. The audit information keeps track of all individual cell changes, such as the cell path, time of change, user, new value, operation (Splashing, Copy), etc.

You can find more details in the article Audit Information.