Deployment
Deployment Strategy
Deployment date: Wednesday 29th May.
Deployment can be done with no impact to the existing HR service therefore low risk.
Apps Management will log onto Apex live and retrieve some user data to confirm Apex set up correctly post deployment.
Dependencies
No dependencies known that will impact on deployment.
Communication
Communication between IS Apps and two members of HR (Susan McLaren) will be done by email/telephone.
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 Test HESA and APEX implementations completed. UAT ongoing by Susan McLaren in HR. No concerns raised by HR. | DSOR (Release 1-n) | Y | John Chan 07/05/2013 |
|
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 |
|
System Design Specification (SDS) | Document complete and accurate.
Action: The Document must be copied to the Wiki Document reviewed and available on the projects website. Copied to Oracle HR R12 wikispace. | ASOR (Final Release / Handover) | Y | John Chan 27/05/2013 |
|
System Description Document | Document complete and accurate.
Action: The Document must be copied to the Wiki HESA SDD updated and reviewed. Copied APEX SDD to Oracle HR R12 wiki space and reviewed. | ASOR (Final Release / Handover) | Y | John Chan 27/05/2013 |
|
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.
| ASOR (Final Release / Handover) | N/A | John Chan 13/05/2013 | Note: Agreed in meeting of 11th Jan that this is not required - see meeting note. Only a few users will have access to the APEX application. |
Performance | The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing. No performance issues reported during UAT. | ASOR (Final Release / Handover) | Y | John Chan 13/05/2013 |
|
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 Tag 1.0.0r5912 and Branch prod_1.0.x created now in SVN | SOR (Final Release / Handover) | Y | John Chan 13/05/2013 |
|
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) No changes to the existing infrastructure. | ASOR (Release 1-n) | N/A | John Chan 21/05/2013 |
|
Change Control(s) | A change control entry has been created for the LIVE implementation request. #76186 - Creation of Apex user ids. Pre-requisite to 76187 - Signed Off #76187 - Deployment. - Signed Off | ASOR / (Release 1-n) | Y | John Chan 21/05/2013 |
|
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. Jira's to be reviewed at Handover. | ASOR (Final Release / Handover) | Y | John Chan 13/05/2013 |
|
Production Management Handover | Handover to Production Management is completed and the team are in are in position to support the application post deployment. APEX handover done. | ASOR (Final Release / Handover) | Y | John Chan 07/05/2013 |
|
Support Accounts | Read access accounts or update current read access accounts have been set up for support staff(requires business owner approval) | ASOR (Final Release / Handover) | Y | John Chan 21/05/2013 |
|
Password Manager (InfoKeep) | InfoKeep has been updated with all relevant account details including external supplier accounts | ASOR (Release 1-n) | Y | John Chan 17/05/2013 |
|
Environment comparison | Database comparison between TEST and LIVE (might be required before and after go-live) Discrepancy with Public Synonyms but this has been resolved now in HRS071-101. | ASOR (Final Release / Handover) | Y | John Chan 21/05/2013 |
|
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 for Apex. | ASOR (Release 1-n) | Y | John Chan 07/05/2013 |
|
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 Oracle Apex Forms being used. Training with external company already done. | ASOR (Release 1) | Y | John Chan 07/05/2013
| Handover APEX session to Apps Management to be done after go-live. |
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. | ASOR (Release 1-n) | N/A | 07/05/2013 | Note: not a web-based application
Apex on existing infrastructure. |
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. | ASOR (Final Release / Handover) | N/A | 07/05/2013 | No certificates being used or require to be renewed. |
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 TAD copied to wiki APEX TAD copied to wiki | ASOR (Release 1-n) | Y | Heather Larnach / David Foggo 13/05/2013 | |
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 Operations Document exists on the projects website. Operations document copied to wiki. | ASOR (Release 1-n) | Y | Heather Larnach / David Foggo 13/05/2013 |
|
Security | All security requirements, e.g. SSL encryption, IP based restrictions firewall requirements have been specified, tested and implemented in LIVE | ASOR (Release 1) | Y | Heather Larnach / David Foggo 13/05/2013
|
|
|
|
|
|
|
|
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 new patching requirements as built on existing infrastructure | ASOR (Final Release / Handover) | Y | John Chan 13/05/2013 |
|
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 On existing infrastructure | ASOR (Release 1-n) | Y | John Chan 13/05/2013 |
|
Start/Stop scripts | Are Server Start-up/Shutdown scripts in place? Including start-up procedure documented, enabled and tested. | ASOR (Release 1-n) | N/A | John Chan
|
|
Ports | Port allocation file been updated: https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers Using existing firewall configurations. | ASOR (Release 1-n) | N/A | John Chan 13/05/2013 |
|
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. | ASOR (Release 1-n) | N/A | John Chan 17/05/2013 | Not required to be done as advised by Jill Nicoll. |
DR Copy | DR copy to Edzell configured and tested(unless existing database which is already setup). | ASOR/Release1 | N/A |
| Note: existing database, already set up. |
Logs | For all logs the following is in place:
| ASOR (Release 1-n) | Y | David Foggo 13/05/2013 |
|
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) | N/A |
| Note: Existing system.. No change to existing support arrangements. |
Time Recording Code | A Time Recording code for the application, if required, has been confirmed and set up. HRSS01 | ASOR (Final Release / Handover) | Y | John Chan 17/05/2013 |
|
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 | ASOR (Release 1-n) | N/A | John Chan 17/05/2013 | Note: Agreed in meeting of 11th Jan that this is not required - see meeting note. DR level 3. |
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 17/05/2013 |
|
Hardware and Software Licensing | All required licensing is in place including maintenance/support arrangements with external suppliers. | ASOR (Final Release / Handover) | N/A | John Chan 13/05/2013 | APEX aplication is free. |
Browser Compatibility | Browser compatibility has been tested and compatibility information updated See for details | ASOR (Final Release / Handover) | N/A | John Chan 13/05/2013 | No change to existing APEX and Oracle HR application versions. |
Portal Compatibility | Portal compatibility, where required, has been confirmed the Portals Service Owner.
| ASOR (Final Release / Handover) | N/A | John Chan 13/05/2013 | No portals being delivered. |
Help Desk | The new application is recognised with the UniDesk (A business contact queue is defined where initial calls are raised with) | ASOR (Final Release / Handover) | N/A | John Chan 13/05/2013 | Note: existing system |
User Guide Documentation | Appropriate documentation has been produced for users of the new application. | ASOR (Final Release / Handover) | N/A | John Chan 13/05/2013 | Note: existing system, used by a single department. Training and user doc is responsibility of the business owners. |
Training Material | Training material, if required, has been produced and is of an appropriate standard. | ASOR (Final Release / Handover) | N/A | John Chan 13/05/2013 | Note: as above |
Demonstration or Walkthrough | Demonstration or walkthrough of the new application has taken place for other stakeholder. | ASOR (Final Release / Handover) | N/A | John Chan 13/05/2013 | Note: as above |
Deployment Date(s) | Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review. Go-Live date is Wednesday 29th May | ASOR (Final Release / Handover) | Y | John Chan 13/05/2013 |
|
Deployment Resources | IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured. Apps Mgmt, Config Team and Dev Tech resources booked in ASTA. | ASOR (Final Release / Handover) | Y | John Chan 13/05/2013 |
|
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. Jill Nicoll will be the deployment owner. | ASOR (Final Release / Handover) | Y | John Chan 13/05/2013 |
|
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. No service alert as the existing HR system will not be impacted. A service alert will have been raised the day after GO-Live for HRS072 | ASOR (Release 1-n) | N/A | John Chan 21/05/2013 |
|
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. | ASOR (Final Release / Handover) | N/A | John Chan | Nothing could be found to be reviewed. |