Welcome Guest! Log in


After reading this article, please feel free to ask questions on the forum or to the Support Team.

Overview of the upgrade process

  • Make a backup of your Analytics WebappHome directory
  • Make a backup of your Analytics installation (or make sure you can reinstall your current version)
  • Please read carefully the Release Notes
  • Download and install the new Analytics version (please ask your Application Server's administrator)
  • Specific operations when upgrading from version 2.0.x to 2.1.x or 2.2.x:
    • Open and Save your analytics repositories in order to migrate them
    • Important note: once opened and saved into Analytics 2.1.x or 2.2.x, a repository can no longer be opened from Analytics 2.0.x.

Comments  

# Virginie_Samson 2016-02-10 14:28
Hello
What do you mean by "open and save your analytics repositories" ?

Thanks
# Virginie_Samson 2016-02-16 13:36
Help ... :-*
# Thomas BLETON 2016-02-16 14:09
In Analytics, simply double click each of your Repositories (renamed "Deployment managers" in the latest versions). And then save them (Ctrl + S).
# Virginie_Samson 2016-02-25 10:52
Can we have 2 versions of Web Analytics on the same machine? Or do we MUST stop the old one service before starting the migration ?
# Thomas BLETON 2016-02-25 15:30
Short answer: yes it is possible.
Long answer: do not use an existing webapp home with an older version of Analytics! The idea is to have your new version running under a different Port, and set a STAMBIA_WEBAPP_HOME_ variable pointing to a new directory location.
We'll write an article on this subject soon.
# Virginie_Samson 2016-02-25 11:04
Does the file tomcat-users.xml change in this version ?
Do we need to copy it back?
# Thomas BLETON 2016-02-25 15:32
As far as I know, no need to alter this file in this version. I also use Tomcat and did not have to change it.
# Virginie_Samson 2016-02-25 17:01
I did the replace of the analytics.war, the reboot of Tomcat, but we are still on the old version
(Cf Mail Support)
An idea?
# Damien ESPRIET 2016-10-24 16:12
Pour info, sous JBoss, il est nécessaire de vider le cache en supprimant le dossier tmp/work pour redémarrer correctement.
# Nicolas Verscheure 2018-01-23 09:44
We have done the migration from version 2.07 to 2.2.4. When we open the repository, we have warning on each package. The support gives us the following solution : go in the configuration section, modify a description of a configuration, save, close the repository and the warnings disapears.

You have no rights to post comments

Articles

Suggest a new Article!