Deployment
Deployment Strategy
Deployment date: 23/07/2014
As detailed in the implementation plan:
1. Database components created/updated
2. Package run to extract data from Oracle HR into UOE_HESA_* tables.
3. Update to LIVE HESA universe to display new field: REFUOA2014
4. APEX Hesa application used by HR Systems team to correct data.
5. Generate HESA extract using EPP4235 report in Oracle HR via a request.
Dependencies
Oracle HR database to be available on the day.
Communication
Only HR Systems Team will be using APEX to correct the data and performing the HESA extract for submission so minimal communication required. The main Oracle HR application will not be affected by the changes.
Deployment Checklists
Application checklist
Component | Success Criteria | Project Stage Required (Agile) | Ok (Y/N) | Reviewed By (Date) | Outstanding Actions (Who) |
|---|---|---|---|---|---|
Implementation Plan | Feedback from previous test implementations completed and successful full implementation undertaken for UAT 3 implementation plans uploaded 1. Oracle 2. Apex 3. Business Intelligence Suite | DSOR (Release 1-n) | Y | John Chan 15/07/2014
| |
Implementation Risk Assessment | A risk assessment has been undertaken for the Implementation Plan and selected deployment dates. (e.g. roll back) | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
System Design Specification (SDS) | Document complete and accurate.
Action: The Document must be copied to the Wiki No existing SDS exists. | ASOR (Final Release / Handover) | N/A | John Chan 15/07/2014 |
|
System Description Document | Document complete and accurate.
Action: The Document must be copied to the Wiki No existing SDD exists and no change to APEX SDD required. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Scalability/Load Testing | Adequate load testing has taken place. The results have been recorded and analysed to ensure that the application will cope with the anticipated load. Only HR System teams will be correcting the data in APEX and performing the HESA extract so minimal users. | ASOR (Final Release / Handover) | N/A | John Chan 11/07/2014 |
|
Performance | The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing. No performance issue encoutered during UAT by HR Systems team | ASOR (Final Release / Handover) | Y | John Chan 11/07/2014
|
|
Source Code
Source control must be checked out till go-live and checked-in after go live | Source code has been secured with VSS or other source control tool. Where code is provided by a third party (e.g. supplier) it has been established who is responsible to maintain source code | DSOR (Final Release / Handover) | N | John Chan 15/07/2014 | Post deployment tasks Pam and Greg to upload to |
Configuration Management Database | The relevant details regarding new or changed infrastructure components have been added to the configuration management database (This is currently maintained in the Change Control System) Added APEX HR HESA into the Human Resources business area. | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Change Control(s) | A change control entry has been created for the LIVE implementation request. CC#94153 | ASOR / (Release 1-n) | Y | John Chan 14/07/2014 |
|
Test Log Review | A review of the test log (JIRA) has taken place to ensure all required actions have been completed. If this is not the case, then confirmation on criticality of outstanding issues and action plan for resolution is required. Review of Jiras to be done prior to deploymeny sign off. | ASOR (Final Release / Handover) | Y | John Chan 11/07/2014 |
|
Production Management Handover | Handover to Production Management is completed and the team are in are in position to support the application post deployment. One off annual project. Any issues will be done by the projects team. Minimal support (if any) required by Production Management. Adequate handovers done in previous years i.e Apex handover | ASOR (Final Release / Handover) | N/A | John Chan 14/07/2014 |
|
Support Accounts | Read access accounts or update current read access accounts have been set up for support staff(requires business owner approval) No changes introduced by this project. | ASOR (Final Release / Handover) | N/A | John Chan 14/07/2014 |
|
Password Manager (InfoKeep) | InfoKeep has been updated with all relevant account details including external supplier accounts No changes introduced by this project. | ASOR (Release 1-n) | N/A | John Chan 14/07/2014 |
|
Environment comparison | Database comparison between TEST and LIVE (might be required before and after go-live) Any issues arising would be quickly noticed and will be dealt with by the projects team. | ASOR (Final Release / Handover) | N/A | John Chan 14/07/2014 |
|
Client requirements
| Does the application have specific client requirements, such as JVM/JRE versions, JInitiator? If so have these requirements been raised with Desktop services Wiki pages to be updated: [1] https://www.wiki.ed.ac.uk/display/insite/Corporate+applications+with+client+based+requirements [2] https://www.wiki.ed.ac.uk/display/insite/Client+side+requirements+for+corporate+applications No new client requirements introduced by this project. | ASOR (Release 1-n) | N/A | John Chan 14/07/2014 |
|
Technologies | Is there any new software or technologies involved? (Y/N) If yes state any additional actions taken to ensure adequate handover to the production support team No new technologies. | ASOR (Release 1-n) | N | John Chan 14/07/2014 |
|
Access outside University | By default all web based applications are accessible outside University without use of VPN etc Wiki list If not accessible from outside University this needs to be approved by Production Management. No changes introduced
| ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Certificates | All changes to certificates or new certificates for this service have to be added to the certificate master list. The certificate master list is being managed by Applications Management This includes TEST and LIVE certificates and records type of certificate and expiry dates. No changes introduced | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Infrastructure checklist
Component | Success Criteria | Project Stage Required (Agile) | Ok (Y/N) | Reviewed By (Date) | Outstanding Actions (Who) |
|---|---|---|---|---|---|
Technical Architecture Document(TAD) | Documentation complete and accurately reflects the environment subjected to UAT.
Action: TAD needs to be copied to Wiki No changes introduced | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Operational Document | Describes fully operational tasks and ongoing maintenance.This document should be fully populated and any missing sections or issues should be highlighted.
Action: TAD needs to be copied to Wiki No changes introduced | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Security | All security requirements, e.g. SSL encryption, IP based restrictions firewall requirements have been specified, tested and implemented in LIVE No changes introduced | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
|
|
|
|
|
|
Patching | Ensure that all applications have an agreed patching schedule and this schedule is agreed with service owners. Different technologies have different patching strategies: Oracle, Windows, Linux No changes introduced and on current patching schedule. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Infrastructure diagrams | All infrastructure diagrams are updated with newest server and infrastructure detail:
https://www.wiki.ed.ac.uk/display/insite/Server+Layout+%28Unix%29
and
https://www.wiki.ed.ac.uk/display/insite/Server+Layout+%28Windows%29 No changes introduced | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Start/Stop scripts | Are Server Start-up/Shutdown scripts in place? Including start-up procedure documented, enabled and tested. No changes | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Ports | Port allocation file been updated:
https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers No changes introduced | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Backup and Recovery | All backups as noted in the TAD need to be confirmed operational.
A test recovery of user data needs to be done to validate the integrity of the recovery mechanism and process. No changes and will not be tested as part of this project. | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
DR Copy | DR copy to Edzell configured and tested(unless existing database which is already setup). No changes and will not be tested as part of this project. | ASOR/Release1 | Y | John Chan 15/07/2014 |
|
Logs | For all logs the following is in place:
No changes | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
| High level Architecture Document (HLA) | If an HLA document exists this document has to be reviewed and moved/stored on the Tech Collab wiki section No HLA document exists. | ASOR (Final Release / Handover) | N/A | John Chan 15/07/2014 |
Support checklist
Component | Success Criteria | Project Stage Required (Agile) | Ok (Y/N) | Reviewed By (Date) | Outstanding Actions (Who) |
|---|---|---|---|---|---|
Support Agreement (including any charging arrangements)
| A support agreement (SLA or OLA) is in place for any new applications – including any hosting or support charges.
Action: SLA moved to wiki:
https://www.wiki.ed.ac.uk/display/insite/SLA+repository+-+Applications+Management | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Time Recording Code | A Time Recording code for the application, if required, has been confirmed and set up. Existing HRSS01 code to be used. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Disaster Recovery and Business Continuity | Appropriate DR/BC provision is in place and has been fully tested. Application DR/BC details have been transferred to the DR Portfolio and DR level (1, 2 or 3) has been agreed No changes to existing DR/BC provision. | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Test Environment | An adequate TEST environment has been established for the application which may be used by support to test future changes prior to releasing these in the LIVE environment. | ASOR (Release 1-n) | Y | John Chan 15/07/2014 |
|
Hardware and Software Licensing | All required licensing is in place including maintenance/support arrangements with external suppliers. No changes. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Browser Compatibility | Browser compatibility has been tested and compatibility information updated See for details No changes. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Portal Compatibility | Portal compatibility, where required, has been confirmed the Portals Service Owner. No portals in MyEd.
| ASOR (Final Release / Handover) | N/A | John Chan 15/07/2014 |
|
Help Desk | The new application is recognised with the UniDesk (A business contact queue is defined where initial calls are raised with) Only HR Systems team will be using APEX and generating the HESA Extract. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
User Guide Documentation | Appropriate documentation has been produced for users of the new application. Any user guide documentation will be updated by HR Systems team for their own use. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Training Material | Training material, if required, has been produced and is of an appropriate standard. Any training documentation will be updated by HR Systems team for their own use. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Demonstration or Walkthrough | Demonstration or walkthrough of the new application has taken place for other stakeholder. Only HR Systems team will be using APEX and generating the HESA Extract. | ASOR (Final Release / Handover) | N/A | John Chan 15/07/2014 |
|
Deployment Date(s) | Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review. See deployment strategy at the top of this page for deployment dates. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Deployment Resources | IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured. Ann Mathison will book relevant resources in ASTA. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Deployment Ownership | Responsibilities for managing the go-live, including: comms with service owner and end users, ensuring go live timescales are met, managing issues arising and managing comms between all teams involved in go live. Anne Mathison will manage the go-live. | ASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
Service Announcement(s) | A Service announcement has been raised with the agreed deployment date on the alert system:
http://reports.is.ed.ac.uk/alerts/
Service announcements should be raised by Project Manager 10 days before go live, but no later than 4 days. Not required as no downtime required when deploying changes. Main Oracle HR application will be available during this time. | ASOR (Release 1-n) | N/A | John Chan 15/07/2014 |
|
Web Sites and Other Document Sources | External and internal web sites have been reviewed to ensure that all application references are present, correct and up to date. No changes required as no internal web sites found. | foundASOR (Final Release / Handover) | Y | John Chan 15/07/2014 |
|
