Migrating icCube : 2.0.3 to 2.0.4
icCube 2.0.4 is backward compatible with the previous version; notice several changes in the required Java CLASSPATH as well as in the configuration file (icCube.xml).
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.
If you've edited the configuration file $install/bin/icCube.xml in the previous version, then you'll have to copy this file into the 2.0.4 directory $install/bin and notice the removal of several TCP properties in the xmlaComponentConfiguration section. Notice as well the change of the class name in the icCubeAuthorizationService section. Filters are now defined in their own section and each component is referencing a chain of filters.
Unless you've edited the 2.0.3 $install/bin/icCube.bat (or .sh) file, there's no need to migrate this file. Otherwise, you'll have to copy this file into the 2.0.4 directory $install/bin and notice the new entries in the Java CLASSPATH section (GVI export-2-excel, GWT servlet, Windows SSO, ...).
Next chapter : 2.0.4 to 2.0.5.