Migrating icCube : 2.5.6 to 2.6

icCube 2.6 is backward compatible with the previous version but see below for new SSL/HTTPS configuration and MDX request result cache (beta) properties as well as for the classpath update.

Installation Reminder

Different versions of icCube can be installed side-by-side on the same machine and no file will be removed during the installation of a new version.

The main two directories mentioned in this page are:

  • the installation directory (referred to $install hereafter) : this is where the icCube binaries are installed,
  • the application directory (referred to $app hereafter) : this is the place where a running instance of icCube server is storing its data (e.g., users, roles, cubes, etc...). On startup of icCube this directory (if not existing) is created and initialized with the content of the $install directory.

Configuration (icCube.xml)

Within the configuration file $install/bin/icCube.xml, the following properties have been either added, modified or deleted.


A bunch of new properties to configure the SSL/ HTTPS connector: for more information please refer to this page.

  • sslPortNumber: (added) the port number of the HTTPS connector (-1 if not activated).
  • sslKeystore / sslKeystorePassword / sslKeystoreType : (added) configures the JAVA key store to use to with the SSL / HTTPS connector..
  • sslTruststore / sslTruststorePassword / sslTruststoreType : (added) configures the JAVA trust store to use to with the SSL / HTTPS connector..


  • icCube.resultCacheMode : (added) controls the activation and mode of the MDX result request cache.
  • icCube.resultCacheSize : (added) defines the size in MB of the MDX result request cache.

Launcher (icCube.bat / icCube.sh)

The classpath has been updated to use the latest (v 4.2.1) HTTP core / client libraries.