Appboard/2.4/admin/installation: Difference between revisions
imported>Jason.nicholls No edit summary |
imported>Jason.nicholls No edit summary |
||
| Line 14: | Line 14: | ||
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.1 to v2.2. Once any differences have been dealt with a new version archive can be produced and that 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 06:29, 5 July 2013
Planning
- Obtain the latest GA version
- Verify your 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.1 to v2.2. Once any differences have been dealt with a new version archive can be produced and that 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.
