Implementation Plan
|
Role |
Unit |
Name |
Date Signed Off |
|
Systems Analyst Designer (Owner) |
|
|
|
|
Technical Architect (Owner) |
|
|
|
|
Developer |
IS Apps |
Thalia Nikolaidou |
03/07/2017 |
|
Development Technology Administrator |
IS Apps |
Riky Harris |
03/07/2017 |
|
Production Management Coordinator |
IS Apps |
John Chan |
03/07/2017 |
|
Project Manager |
IS Apps |
Richard Bailey |
03/07/2017 |
1 Implementation Tasks
1.1 Infrastructure Components No changes to existing infrastructure
1.2 Application Components 1.2.1 Source code GitLab repository URL should be latest tagged release, under https://gitlab.is.ed.ac.uk/isapps-software/etime/tags .
In order to grab the latest code for deployment you should export the code to your machine. From this point on, that folder on your machine will be referred to as {local_etime}.
After you have completed the deployment you should remove your exported copy of the code.
1.2.2 Database The database scripts are located under the db/Patches/FIN116 directory, therefore, {local_etime}\db\Patches\FIN116. Log in to the targeted environment’s FIN database instance as Oracle user “etime”. Execute the scripts in the order provided.
1.3 Application Setup
Log in to the targeted environment’s application servers as the “etime” user.
Run the following commands to stop the etime tomcat container and deploy the etime.war application:
cd /u01/app/etime/tomcat/bin;
tomcat_etime stop;
Run the following commands to remove any existing etime.war file and etime folder:
cd /u01/app/etime/apache-tomcat/webapps/;
rm etime.war;
rm -R etime;
Copy the file
{local_etime}\target\etime.war
to
/u01/app/etime/apache-tomcat/webapps
Run the following commands to start the etime tomcat container and deploy the etime.war application:
cd /u01/app/etime/tomcat/bin;
tomcat_etime start;
1.4 Integration Components N/A
1.5 Data Population & Migration N/A
1.6 Implementation Validation Log in to the targeted environment’s application URL and ensure that the application is up and running. TEST: www-test.etime.finance.ed.ac.uk LIVE: www.etime.finance.ed.ac.uk
2.0 Rollback 2.1.1 Database The rollback database scripts are located under the db/Patches/FIN116/rollback directory, therefore, {local_etime}\db\Patches\FIN116\rollback. Log in to the targeted environment’s FIN database instance as Oracle user “etime”. Execute the scripts in the order provided.
2.1.2 Source code GitLab repository URL should be latest tagged application version, under https://gitlab.is.ed.ac.uk/isapps-software/etime/tags .
In order to grab the latest code for deployment you should export the code to your machine. This folder will serve as the {local_etime} from here on. The etime.war that will be used for application setup as described in 2.3, can be found under {local_etime}\target\etime.war .
After you have completed the deployment you should remove your exported copy of the code.
2.1.3 Rollback steps 1. Revert database changes, as described in 2.7.1 2. Get previous stable application version, as described in 2.7.2 3. Deploy previous stable application version, using 2.3 4. Verify implementation, as described in 2.6
3 Rollout Steps 1. Get the application code, as described in 1.2.1 2. Apply database changes, as described in 1.2.2 3. Deploy the application, as described in 1.3 4. Verify implementation, as described in 1.6