Technical Changes for Cloud Users


This article describes the key user-related objects of a Jedox model that may be affected by the Cloud upgrade. Please check back here regularly as additional items may be added over time.

1. System Logs location has changed

All logs under Administration have now been moved to the Cloud Console. You can review, sort, and filter the logs there. Integrator Monitor execution logs have not changed location and are still available in Jedox Suite.

The specific logs that are now in the Cloud Console include:

  • Jedox In-Memory DB (OLAP) logs
  • Apache logs
  • Spreadsheet Server logs
  • Scheduler Server logs
  • Integrator internal logs
  • Supervision Server (merged with Jedox In-Memory DB logs)
2. Specific commands in macros have changed

Any macro that explicitly refers to “” will not work in this new environment. Generally, it is inadvisable to hard-code IP or server addresses in macros.

Change all In-Memory DB (OLAP) connections to use system variables. For more information, see Macro Engine API Documentation and refer to the section on the $_JEDOX variable.

Examples of session variables:

When establishing connections to Jedox Integrator in a macro where you are specifying an explicit address, use jedox-etl (instead of e.g. as the address. A port does not have to be specified.

3. Separate address required for Excel connections

When connecting to a Jedox server that is on the new infrastructure, you can set up a connection from Jedox Excel Add-in by copying the Excel Add-in certificate. You can download the certificate from the Connection area of the Jedox Cloud Console, using the button indicated below:

When manually creating or editing a connection in Jedox Excel Add-in, you need to specify the field “Separate OLAP Address” as well as the general address. The ports for both addresses are 80.

Address: https://<CUSTOMER DOMAIN>
Separate OLAP address: http://olap.<CUSTOMER DOMAIN>
OLAP port: 80
Web Port: 80

Note: the connection to Jedox OLAP only uses HTTP for the initialization of the connection. All requests that transfer data use TLS/HTTPS.

4. In-Memory DB connections in Jedox Web Connection Manager

When creating a new connection to your Jedox In-Memory DB (OLAP) server in Jedox Web Connection Manager, the interface to use is jedox-olap, and the port to use is port 80.

5. Changes to SFTP connections to Cloud environment

Hostname for SFTP connection has changed to ssh.<CUSTOMER DOMAIN>

Sometimes integration processes use a file storage location in Tomcat to store files on the Jedox Cloud file system. The old path for storage was /user_data/live/tomcat-etl/webapps/etlserver/data/files. This path no longer exists.

The new path is /tomcat-etl/webapps/etlserver/data/files

6. Settings in Jedox Models

Jedox Models include settings that can be changed in the Administration area of Jedox Web. One of these settings defines the address for Jedox Integrator, specifically the setting system.integrator_server.url. In the new infrastructure, the value of this setting must be changed to http://jedox-etl.

7. Connections to Jedox components in Supervision Server scripts

If your Supervision Server scripts establish direct connections to either Jedox In-Memory DB (OLAP) or Jedox Integrator, the address used when establishing the connection needs to be changed in the script.

Instead of using the network interface (or some other custom interface), use the address jedox-olap and jedox-etl.

The port for OLAP is 80. For Integrator, a port does not have to be specified.

Connections from SVS scripts using the reserved OLAP connections string, such as palo_data("SupervisionServer/$database",...) must not be changed.