Hello Community!
I'm looking for documentation that describes the upgrade process within a major product release (i.e. 9.n to 9.n+1). A client of mine is keen to implement ARIS and is happy to go with an initial installation of 9.6 with upgrade to 9.7 as it is released (scheduled Q4 2014, possibly October).
Before confirming this approach, I would first like to understand how ARIS is upgraded within a major product release. I'm aware that to upgrade from 7.x to 9.x is essentially a re-implementation with data migration (there is no in-situe upgrade path) but I would like some confirmation that a minor upgrade within a major product release (e.g. 9.6 to 9.7) would be achieved.
I'm assuming this delta would support an in place upgrade!
EDIT: I've just read section 6 of the ARIS Server Installation and Administration guide (for 9.6 - section 6, page 147) which states that the upgrade process is essentially to back everything up via a supplied bat / sh script (presumably this includes config settings as well as all databases), uninstall the current version of the system (9.x), install the new version of the system (9.6) and then re-import the data backed up in the first step.
It seems quite convoluted to have to uninstall and reinstall rather than applying a code base delta..
Does anyone have any experience of this process (good / bad / ugly) that you can share?
Many Thanks,
Ben
Matias Kokko on
Hi,
I may have a different version of the admin guide, but in mine the section 6 is about migrating from 7.2 to 9.x, which is essentially a complete reinstallation.
I've upgraded from 9.5 to 9.6 and that is an in place upgrade. Especially if you have used the setup program to install a standard environment (in contrast to manually creating tenants and provisioning components through ACC) the setup program of a newer version will identify which components you ave installed and automatically update them. Better go through the readme notes though because there may be some manual preparations/actions after update needed. Pretty straightforward anyway.
And as always it's recommended to backup databases and configuration before updating.