Appboard/2.4/admin/installation: Difference between revisions
imported>Jason.nicholls No edit summary |
imported>Jason.nicholls No edit summary |
||
| Line 10: | Line 10: | ||
* [[appboard/2.4/admin/windows_installation|Windows Installation Guide]] | * [[appboard/2.4/admin/windows_installation|Windows Installation Guide]] | ||
* [[appboard/2.4/admin/unix_installation|Linux / UNIX Installation Guide]] | * [[appboard/2.4/admin/unix_installation|Linux / UNIX Installation Guide]] | ||
=== Upgrading === | === Upgrading === | ||
| Line 16: | Line 15: | ||
When upgrading there are additional considerations: | When upgrading there are additional considerations: | ||
# major version upgrades should be performed in a lab before deploying to production, for example moving from AppBoard v2. | # major version upgrades should be performed in a lab before deploying to production, for example moving from AppBoard v2.3 to v2.4. Once any differences have been dealt with, a new version archive can be produced and this used when upgrading production. | ||
# ensure you have a full archive before starting (see [[appboard/2.4/admin/backup_and_recovery|Backup and Recovery]]) | # ensure you have a full archive before starting (see [[appboard/2.4/admin/backup_and_recovery|Backup and Recovery]]) | ||
# perform a ''clean'' installation, ''then'' restore the archive. i.e. never uncompress a new version of the product over the top of an existing install unless directed by support. | # perform a ''clean'' installation, ''then'' restore the archive. i.e. never uncompress a new version of the product over the top of an existing install unless directed by support. | ||
Revision as of 03:58, 28 August 2013
Planning
- Obtain the latest GA version
- Verify the target system meets the System Requirements
- Ensure you have a valid license file
Installation
Upgrading
When upgrading there are additional considerations:
- major version upgrades should be performed in a lab before deploying to production, for example moving from AppBoard v2.3 to v2.4. Once any differences have been dealt with, a new version archive can be produced and this used when upgrading production.
- ensure you have a full archive before starting (see Backup and Recovery)
- perform a clean installation, then restore the archive. i.e. never uncompress a new version of the product over the top of an existing install unless directed by support.
