Appboard/2.5/admin/installation: Difference between revisions
imported>Jason.nicholls |
imported>Jason.nicholls |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
# Obtain the latest GA version | # Obtain the latest GA version | ||
# Verify the target system meets the [[appboard/2.5/system_requirements|System Requirements]] | # Verify the target system meets the [[appboard/2.5/system_requirements|System Requirements]] | ||
# Ensure you have a [[ | # Ensure you have a [[support/obtaining_a_license|valid license file]] | ||
=== Installation === | === Installation === | ||
| Line 12: | Line 12: | ||
* [[appboard/2.5/admin/unix_installation|Linux / UNIX Installation Guide]] | * [[appboard/2.5/admin/unix_installation|Linux / UNIX Installation Guide]] | ||
{{Note| | {{Note|AppBoard ships with a limited set of JDBC drivers due to licensing restrictions. The appropriate drivers may need to be installed to interface with your chosen configuration database or data sources. Refer to the [[appboard/2.5/admin/db_drivers|Loading Database Drivers]] page for more information.}} | ||
=== Upgrading === | === Upgrading === | ||
| Line 20: | Line 20: | ||
# major version upgrades should be performed in a lab before deploying to production, for example moving from AppBoard v2.4 to v2.5. Once any differences have been dealt with, a new version archive can be produced and this used when upgrading production. | # major version upgrades should be performed in a lab before deploying to production, for example moving from AppBoard v2.4 to v2.5. 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.5/admin/backup_and_recovery|Backup and Recovery]]) | # ensure you have a full archive before starting (see [[appboard/2.5/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/apply 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:07, 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.4 to v2.5. 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/apply 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.
