Appboard/2.5/admin/installation: Difference between revisions

imported>Jason.nicholls
imported>Jason.nicholls
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.
# start up AppBoard and log in as the administrator. To ensure all widgets are upgraded it is necessary to _visit every single board_ at least once.


=== Running AppBoard ===
=== Running AppBoard ===

Revision as of 08:43, 3 October 2014

Planning

  1. Obtain the latest GA version
  2. Verify the target system meets the System Requirements
  3. Ensure you have a valid license file

Installation

Template-note.png
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 Loading Database Drivers page for more information.

Upgrading

When upgrading there are additional considerations:

  1. 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.
  2. ensure you have a full archive before starting (see Backup and Recovery)
  3. 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.
  4. start up AppBoard and log in as the administrator. To ensure all widgets are upgraded it is necessary to _visit every single board_ at least once.

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.

Related Topics