This will contain a .war file for the codebase and a database update script

If provided, run appropriate update script against the database to create LW backend database compatible with your upgrade

Prerequisite

Script will be provided with deployment package:launch_sql_<version>.sql

Backup/Archive the current /launch installation to ensure a rollback policy for codebase

Prerequisite

Archive to current server (or predetermined archive location) that is accessible in the event of a needed rollback

Retain a copy of the appconfig.properties file for post installation configuration

Prerequisite

This can be found in the current code location. E.g. C:\Program Files\Apache Software Foundation\Tomcat7\launch\WEBINF\

Stop Tomcat web service

Deployment

Remove/Archive the current /launch installation folder (and all sub folders) from the Tomcat directory

Deployment

Move the delivered LaunchWorks .war file install package to the server and place in the Tomcat/webapps folder

Deployment

E.g. C:\Program Files\Apache Software Foundation\Tomcat 7.0\Note: if the .war file is not named “launch.war” please rename during this step. When the .war is extracted, the .war name will be the name of the codebase. This should be “launch” in most scenarios

Start Tomcat web service.

Deployment

Confirm /launch has been extracted to the /webapps folder as expected

Deployment

Stop Tomcat web service

Deployment

Replace the appconfiguration.properties file with the original from step 4 above

Deployment

Remove/Archive the launch.war file from the current /webapps folder to avoid redeploy during standard Tomcat web service maintenance

Deployment

This can simply be done by adding an "Archive" folder to the server desktop and placing the .war inside.

Start Tomcat web service.

Deployment

Login to the Administration Console and Confirm database connection

Testing

See below for link

Test application connection

Testing

See below for link

Test Application Connection

Once the code has been deployed (or migrated) and the application configurations have been made, run the following test to assure all connections have been made.

Backups

Database, virtual server, and file system backups will be performed by the IT resources and standard automated processes. These backups are standard practice and LaunchWorks is under the assumption that backups of these types are scheduled/processed are regular intervals in the event of needing any database, virtual server, or file system backup for disaster recovery. It these processes are not in place, or you need assistance in defining any aspect of the LaunchWorks installation to be backed up, please contact your LaunchWorks representative.