Upgrading to a Newer Version

The Exalead CloudView migration option launched during the installation process, for example, ./install.<bat/sh> -migrate, automatically includes all the components of the Exalead CloudView solution as well as configuration updates.

The migration option cannot migrate the custom code that you may have developed and deployed in <DATADIR>/webapps/360-mashup-ui.

During the installation process:

1. The system detects that you have an existing Mashup UI application and moves it to webapps/360-mashup-ui.old.

2. A new instance of the application is then deployed to the webapps/360-mashup-ui directory.

To migrate your custom code on the new application you have to copy back:

  • Resources (stylesheets, images, javascript)

  • Custom widgets

  • Custom jar files

  • Custom JSP files and tags

To ease the migration process, a good practice is to always make your custom code “visible”. For example, instead of:

  • modifying the style.css file, create a new file that just contains your rules.

  • modifying a deployed widget, copy it first to create your very own widget.

These good practices can significantly speed up the migration process.