The following is the LaunchWorks Deployment guide for a new installation.  This guide should be used as a step by step checklist for proper Installation/Deployment of the LaunchWorks application.


This document should be filled in with customer specific information that pertains to the installation of all require LaunchWorks applications.


Pre-Deployment Information – Defining Environment Information

Note: This deployment automatically configures launch with server-specific settings. Client must provide the following information prior to installation for these settings to be accurate:


Step
Comments
Absolute File Path to my SQL install
Ex:  C:\Program Files\MySQL\MySQL Server 5.0
Absolute File Path to Apache Tomcat install
Ex:  C:\Program Files\Apache Software Foundation\Tomcat 7.0
MySQL User Name

MySQL Password

Launch Server
Server Name

Network Location (Internal / DMZ)

Audit Launch Database Server (optional)
Server Name

 Database DBMS

 Database Name

 Database User

 Database Password

Source Database (optional)
 Database Server

 Database DBMS

 Database Name

 Database User

 Database Password

BOE Server
 CMS Name

 CMS Admin User

 CMS Admin Password

 CMS User

 CMS Password

 CMS Port Number
6400 (default, change if necessary)
SMTP Server
SMTP Server Name

SMTP User Name (if required)

SMTP Password (if required)

SMTP "From" email address

SMTP "To" email address

 

Installation Checklist

All references to {tomcat root} refers to: C:\Program Files\Apache Software Foundation\Tomcat7

All references to {launch url} refers to: http://localhost:[port]/launch/


Step
Owner
Comments
Download required installation package from LaunchWorks
Prerequisite
This will contain a .war file for the codebase and a database update script
Run appropriate update script against the database to create LW backend database compatible with your launch install
Prerequisite
Script will be provided with deployment package:
launch_sql_<version>.sql
Confirm all prerequisite steps are complete in terms of internal and LaunchWorks related preparations
Prerequisite
 
Stop Tomcat web service 
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
 
Configure appconfiguration.properties file with CMS and database settings.
Deployment
 Reference Section 1.  
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
To reach Administration console got to http://\{localhost}:{port}/launch/administration/ 
Test application connection
Testing
Reference Section 2.
Backup serverBackupReference Section 3.


1. AppConfiguration.properties

Configure AppConfiguration.properties file (optional for update deployment)Using the configuration settings documented in Section 1.1, edit the AppConfiguration.properties filelocated in the WEB-INF sub-directory of the newly-extracted auditlaunch application folder. The following sections should be completed:






Also be sure to remove comment #'s for the "database" section that applies to the dbms. Audit Launch will be using for its main configuration files (typically MySQL). Remove the hash (#) in front of each line of that section. Be sure all other sections are commented with hashes. An example is shown below:


2. 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.


Login to the administration console:  (e.g. http://(localhost)/launch/administration)



Note:  Please contact your system administrator, or support@launchworks.com for Administration Console username and password


Select View Application:

Click “Test Application” for the appropriate App_Name:   


 


 


Confirm Successful Connections Tests:

 


 


 


   

3. 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.