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/clustering_and_failover|Clustering & Failover]] | ||
* [[appboard/2.5/admin/db_drivers|Loading Database Drivers]] | * [[appboard/2.5/admin/db_drivers|Loading Database Drivers]] | ||
* [[appboard/2.5/admin/enabling_cgi|Enabling CGI]] | * [[appboard/2.5/admin/enabling_cgi|Enabling CGI]] | ||
* [[appboard/2.5/admin/multiple_instances|Multiple Instances]] | * [[appboard/2.5/admin/multiple_instances|Multiple Instances]] | ||
* [[appboard/2.5/admin/blazeds_installation_instructions|BlazeDS Installation Instructions]] | * [[appboard/2.5/admin/blazeds_installation_instructions|BlazeDS Installation Instructions]] | ||
Revision as of 06:14, 22 July 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 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.
