Implementation Tasks

Implementation co-ordinator

The Developers will co-ordinate the implementation process. After the completion of each step, the responsible persons should report to the developers that it is complete, so that the next step can be progressed.

Pre-implementation checklist

• Both CESAR live ColdFusion instances must have the following datasource definitions:
  • cesarMigrationImport
  • cesar
• The oracle user "cesar" on OLLLIVE has the following (non-standard) permissions granted, either directly or via roles:
  • CREATE JOB (or CREATE ANY JOB)
• CESAR has a new release number (1.0.x) defined in release.properties.
• OLLBOOK has a new release number (2.0.x) defined in release.properties.

Implementation process overview

Implementation - stage 1

These first steps of the implementation can be done prior to OLLiE/OLLBOOK being made unavailable.

Identify CESAR production release build

Developers will identify which build number will be used to deploy to production.

The final build is build #707.

Identify OLLBOOK production release build

Developers will identify which build number will be used to deploy to production.

The final build is build #35.

Identify WPMSERV production release build

Developers will identify which SVN tag will be used to deploy to production.

The final tag is tag 2.3.1.r19513.

Promote CESAR to live environment

Applications Management will use bamboo to promote CESAR into production.

Developers will increment the release number in CESAR trunk to 1.1.x in anticipation of future deployments.

Create CESAR web service definition on OLLBOOK and WPMSERV ColdFusion instances

Dev Tech will create a web service definition for CESAR for use by OLLBOOK and WPMSERV applications. If the web service definition already exists, it should be refreshed.

Web Service Name: cesar WSDL URL:         https://www.cesar.lifelong.ed.ac.uk/services/api.cfc?wsdl

It should be created on the following four ColdFusion instances:

student (ollbook) https://niddry.mis.ed.ac.uk:9106/cfide/administrator/ student (ollbook) https://morton.mis.ed.ac.uk:9106/cfide/administrator/

cpg (wpmserv)     https://niddry.mis.ed.ac.uk:9112/cfide/administrator/ cpg (wpmserv)     https://morton.mis.ed.ac.uk:9112/cfide/administrator/

Implementation - stage 2

During this stage of the implementation OLLiE and OLLBOOK applications will be made unavailable to users.

Disable use of OLLBOOK

Dev Tech will disable access to OLLBOOK application. The developers will provide an Application.cfc file which will display a maintenance message (provided by OLL). This file should be copied into the webroot. No other changes are required because the Application.cfc will override the existing Application.cfm.

ollbook@morton.mis.ed.ac.uk:/homes/mis/ollbook ollbook@niddry.mis.ed.ac.uk:/homes/mis/ollbook

Disable use of OLLiE

OLL team will notify their wider staff that use of OLLiE should cease at a predetermined point. OLL admin will revoke user access to OLLiE to enforce this.

Promote WPMSERV to live environment

Dev Tech will deploy WPMSERV application to live environment. This application is not configured to use bamboo so the deployment must be done manually.

The deployment consists of copying the files in the tag into the webroot. A patch of only the changed files would be sufficient. No other action needs to be taken.

wpmserv@morton.mis.ed.ac.uk:/u01/software/wpmserv/htdocs wpmserv@niddry.mis.ed.ac.uk:/u01/software/wpmserv/htdocs

Promote OLLBOOK to live environment

Apps Man will use bamboo to promote OLLBOOK into production.

Dev Tech will immediately put the deployed application into maintenance mode by backing up the existing Application.cfc and replacing it with one provided by developers.

Developers will increment the release number in OLLBOOK trunk to 2.1.x in anticipation of future deployments.

Data migration and data population

During this stage OLLBOOK will remain unavailable to users.

Run OllieExport stored procedures to generate export data into staging tables

Developers will run the stored procedures in MSSQL OllieExport database to populate the export staging tables from the OLL_1_LIVE database:

1. generate_course_export
2. generate_course_instance_export
3. generate_student_export
4. generate_student_meeting_export
5. generate_studentStudyPlan_export
6. generate_enrolments_export

Copy data from OllieExport staging tables into CESAR import tables

Dev Tech will copy the data from the OllieExport tables on mis-ford, into the CESAR import tables on OLLLIVE.

Firstly, the CESAR import tables must be verified to be empty:

delete from OLLIE_IMPORT_COURSE_INSTANCES; delete from OLLIE_IMPORT_STUDENTS; delete from OLLIE_IMPORT_STUDENT_MEETINGS; delete from OLLIE_IMPORT_STU_STUDY_PLANS; delete from OLLIE_IMPORT_ENROLMENTS;

Then, the data should be copied:

export_course_Instances -> OLLIE_IMPORT_COURSE_INSTANCES export_students -> OLLIE_IMPORT_STUDENTS export_student_meetings -> OLLIE_IMPORT_STUDENT_MEETINGS export_students_study_plans -> OLLIE_IMPORT_STU_STUDY_PLANS export_enrolments -> OLLIE_IMPORT_ENROLMENTS

Run CESAR import process

Developers will run the import process on the CESAR application to copy the data from the CESAR import tables into the application’s main database.

Manual data preparation – adding class instances, etc

OLL team will organise data entry and data maintenance.

Implementation Validation

OLL team will organise testing of the deployed application. Confirmation that the following customer facing components are operational is essential:

• OLLBOOK – full process of creating a booking.
• OLLBOOK – adding a course instance to shopping basket, then allowing it to expire after 30 mins. Verifying on CESAR that the space is no longer taken.

Launch

Enable access to CESAR.

OLL team will notify staff that CESAR can be used.

Enable public access to OLLBOOK.

Dev Tech will remove the block on OLLBOOK and allow public access.

Roll-back

In the event of a roll-back being required, the following steps must be taken:

Restore previous OLLBOOK version from production branch: prod_1.0.0.

Restore previous WPMSERV version from tag 2.3.0.r13954. Note for unknown reasons there is no WPMSERV production branch. It is assumed that this tag represents the status of live prior to CESAR launch.

OLL admin will restore user access to OLLiE.

Closure tasks and clean-up

Once the application has been in place for a sufficient period of time, OLL will sign off acceptance, and closure can take place.

Creation of Bamboo production support plans

Developers will create production support plans for CESAR and OLLBOOK.

Removal of import facility

Developers will create a build of CESAR which has the ColdFusion import utility removed and Oracle import tables dropped. Developers will push it to Dev, Beta, Test and Train environments. Apps Man will push it to live.

Dev Tech will remove the /ollieImport directory and cesar-ollbook basic auth user from all 10 CESAR ColdFusion instances.

Dev Tech will remove the cesar-ollbook basic auth entry from InfoKeep.

Dev Tech will drop the OllieImport database and OllieImport user from mis-ford.

Dev Tech will remove the CesarMigrationImport datasource from all 10 CESAR ColdFusion instances.

Removal of obsolete datasources

Dev Tech will remove the old OLLiE datasource from all 6 OLLBOOK instances (datasource name: ollbook_dev, ollbook_test, ollbook_live).

Dev Tech will remove the old OLLiE datasource from all 6 WPMSERV instances (datasource name: wpm_ollbook).

OLLiE decommissioning

Production Management will co-ordinate decommissioning of OLLiE databases and application.