Appboard/2.4/admin/installation: Difference between revisions
imported>Mike.berman No edit summary |
imported>Jason.nicholls |
||
| (One intermediate revision by the same user not shown) | |||
| Line 21: | Line 21: | ||
# 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. | ||
# it is necessary to log into the Builder at least once to ensure all widgets are upgraded. | |||
=== Running AppBoard === | === Running AppBoard === | ||
Latest revision as of 09:08, 3 October 2014
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.
- it is necessary to log into the Builder at least once to ensure all widgets are upgraded.
Running AppBoard
Refer to the OS specific installation guides above for starting/stopping AppBoard. Also see the Accessing AppBoard page to access AppBoard once it's running.
