Appboard/2.4/admin/installation: Difference between revisions
imported>Jason.nicholls (Created page with '{{DISPLAYTITLE:Installation & Upgrading}} === Planning === # Obtain the latest GA version # Verify your system meets the [[appboard/2.4/system_requirements|System Requirements]…') |
imported>Jason.nicholls |
||
| (27 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Installation & Upgrading}} | {{DISPLAYTITLE:Installation & Upgrading}} | ||
[[Category:AppBoard 2.4]] | |||
=== Planning === | === Planning === | ||
# Obtain the latest GA version | # Obtain the latest GA version | ||
# Verify | # Verify the target system meets the [[appboard/2.4/system_requirements|System Requirements]] | ||
# Ensure you have a [[support/obtaining_a_license|valid license file]] | |||
=== Installation === | |||
* [[appboard/2.4/admin/windows_installation|Windows Installation Guide]] | |||
* [[appboard/2.4/admin/unix_installation|Linux / UNIX Installation Guide]] | |||
{{Note|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: | |||
# 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 [[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. | |||
# 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 [[appboard/2.4/admin/accessing_appboard|Accessing AppBoard]] page to access AppBoard once it's running. | |||
=== Related Topics === | |||
* [[appboard/2.4/admin/runtime_options|Runtime Options]] | |||
* [[appboard/2.4/admin/memory_configuration|Memory Configuration]] | |||
* [[appboard/2.4/admin/ssl_configuration|SSL Configuration]] (HTTPS secure access) | |||
* [[appboard/2.4/admin/clustering_and_failover|Clustering & Failover]] | |||
* [[appboard/2.4/admin/db_drivers|Loading Database Drivers]] | |||
* [[appboard/2.4/admin/enabling_cgi|Enabling CGI]] | |||
* [[appboard/2.4/admin/multiple_instances|Multiple Instances]] | |||
* [[appboard/2.4/admin/blazeds_installation_instructions|BlazeDS Installation Instructions]] | |||
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.
