Appboard/2.5/admin/installation: Difference between revisions

imported>Jason.nicholls
imported>Jason.nicholls
Line 31: Line 31:
* [[appboard/2.5/admin/memory_configuration|Memory Configuration]]
* [[appboard/2.5/admin/memory_configuration|Memory Configuration]]
* [[appboard/2.5/admin/ssl_configuration|SSL Configuration]] (HTTPS secure access)
* [[appboard/2.5/admin/ssl_configuration|SSL Configuration]] (HTTPS secure access)
* [[appboard/2.5/admin/configuration_database|Configuration Database]]
* [[appboard/2.5/admin/clustering_and_failover|Clustering & Failover]]
* [[appboard/2.5/admin/clustering_and_failover|Clustering & Failover]]
* [[appboard/2.5/admin/db_drivers|Loading Database Drivers]]
* [[appboard/2.5/admin/db_drivers|Loading Database Drivers]]

Revision as of 06:24, 22 July 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
A clean AppBoard install will be missing many common JDBC database drivers due to licensing restrictions. Refer to the Related Topics below.

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 the archive. i.e. never uncompress a new version of the product over the top of an existing install unless directed by support.

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