To check before upgrading...
Carefully read requirements, they may have changed since you last installed/upgraded your iTop instance :
Why upgrading? What features are brought by new versions:
|What's new||new in 2.3||new in 2.4||new in 2.5||new in 2.6||new in 2.7||new in 3.0|
|Change log||Cumulative change log (exaustive list of changes includind each sub releases)|
Before upgrading your iTop instance to a new version, read all migration notes on the upgrade path ! For example if you're upgrading from 2.6.3 to 3.0.0, you must read the following migration notes :
from 2.6 to 2.7
from 2.7 to 3.0
|Migration Notes||2.0.3 to 2.1||2.1 to 2.2||2.2 to 2.3||2.3 to 2.4||2.4 to 2.5||2.5 to 2.6||2.6 to 2.7||2.7 to 3.0|
Before upgrading, check all of your installed extensions are compatible with the new version !
List of installed extensions and their version can be found in the “about iTop…” dialog, located in the log-off menu.
Check compatibility by opening each extension documentation.
Process : dry-run on a test environment
You should first try the update on a test environment running the same environment (PHP and MySQL version and configuration) and same data !
log/setup-queries-*.sqlfile (this file is generated since 2.5.0) and sometimes they can be executed in advance on a not yet migrated iTop database
To be used for minor migrations only (x.y.a to x.y.b), see limitations
If your installed iTop instance is at least in the 2.7.0 version
you will be able to use the application upgrader to automate the
process ! It is located in the System / Application Upgrade
This is recommended especially for security upgrades, where very few changes are generally made !
The iTop application upgrader will check the system configuration and warn you if the requirements are not met.
Application updater can still be used with complete iTop packages, but as those files are big (20MB or so) this needs to allow big uploads in the web server configuration !
If you can't use iTop application updater for any reason (upload size, write permissions, …), use the below manual process.
Make a backup of your current iTop directory (you should exclude /data/backups)
Unzip the downloaded package in your iTop directory : this will create a /web subdirectory
If you used the /webservices/cron.params file, copy it to /web/webservices
Remove previous version core files :
rm -rf addons datamodels images lib manifest.xml portal application core dictionaries env-test index.php navigator setup webservices approot.inc.php css js pages synchro sources documentation
Your iTop directory should now contains
the following subdirectories : conf, data, env-production, log, extensions, web (and maybe toolkit or collectors if you have installed them)
no file at the iTop directory level
You may need to remove
templates/if present (since 2.7.0)
Copy new version core files by launching this command, still in your iTop directory :
cp -r ../web/* .
Check permissions (your webserver user must have access)
Change iTop configuration file to make it writable :
chmod 644 conf/production/config-itop.php
Launch a Setup (using in your browser :
On step 2, keep “upgrade” radio selected.
Check that the database backup is selected
Click next on all following steps