Migrating icCube : 2.0.1 to 2.0.2
2.0.2 is a maintenance release that is backward compatible with 2.0.1 except for minor changes into the configuration file.
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.
Unless you've edited the 2.0.1 $install/bin/icCube.xml file, there's no need to migrate this file. Otherwise, you'll have to copy this file into the 2.0.2 directory $install/bin and notice the new properties ( activeMdxRequestCount, singleMdxEvalThreadCount, singleMdxEvalQueueSize ) into the section olapEngineComponentConfiguration as well as the new scheduler application directory (schedulerDirectory) in the section directories.
HTTP hostname configuration - this new optional ( hostName ) property in the section ( httpComponentConfiguration ) allows for configuring icCube to listen on a specific network interface for multi-homed machine.
Note that reloading a schema does not delete first the loaded schema anymore; this allows for not deleting the loaded schema in case the reload command is generating some errors. To keep the previous behavior (e.g., for memory usage) you'll have to manually unload first the loaded schema.
Next chapter : 2.0.2 to 2.0.3.