Deployment
Deployment Strategy
The Live server is being configured with all the connectors/alarms at the moment by John Hercus and Trend. Once the communication testing is finished today the Live server will be ready to replace the old infrastructure server. Actually the old infrastructure server will stop working today as the License has been transferred to the new infrastructure Test server. Once this process is finished today the only main thing pending is the DR test for the Live server.
Dependencies
No dependencies with other projects or systems.
Communication
Estates and Buildings Energy Team to communicate to end users.
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 | DSOR (Release 1-n) | Y | John Chan 05/09/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 05/09/2014 |
|
System Design Specification (SDS) | Document complete and accurate.
Action: The Document must be copied to the Wiki Not required as no inhouse developers involved. | ASOR (Final Release / Handover) | N/A | John Chan 05/09/2014 |
|
System Description Document | Document complete and accurate.
Action: The Document must be copied to the Wiki Not required as no inhouse developers involved. | ASOR (Final Release / Handover) | N/A | John Chan 05/09/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. Low number of 6 concurrent users.
| ASOR (Final Release / Handover) | N/A | John Chan 05/09/2014 |
|
Performance | The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing. No performance issues encountered during testing by users or project team. | ASOR (Final Release / Handover) | Y | John Chan 05/09/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 Trend will be supporting the software application. | DSOR (Final Release / Handover) | N/A | John Chan 05/09/2014 |
|
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) TREND963 set up. | ASOR (Release 1-n) | Y | John Chan 05/09/2014 |
|
Change Control(s) | A change control entry has been created for the LIVE implementation request.
| ASOR / (Release 1-n) | N | John Chan 05/09/2014 | TO DO: Anne Mathison to set up. |
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. Project EST079 not set up in JIRA. | ASOR (Final Release / Handover) | Y | John Chan 05/09/2014 |
|
Production Management Handover | Handover to Production Management is completed and the team are in are in position to support the application post deployment. | ASOR (Final Release / Handover) | N | John Chan 05/09/2014 | TO DO: Handover meeting to be set up. |
Support Accounts | Read access accounts or update current read access accounts have been set up for support staff(requires business owner approval) Functional AD account trend963 created. | ASOR (Final Release / Handover) | Y | John Chan 05/09/2014 |
|
Password Manager (InfoKeep) | InfoKeep has been updated with all relevant account details including external supplier accounts
Functional AD account trend963 created. | ASOR (Release 1-n) | Y | John Chan 08/09/2014 |
|
Environment comparison | Database comparison between TEST and LIVE (might be required before and after go-live) Third Party system and will be supported by Trend. | ASOR (Final Release / Handover) | N/A | John Chan 05/09/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 changes | ASOR (Release 1-n) | N/A | John Chan 05/09/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 introduced. | ASOR (Release 1-n) | N | John CHan 05/09/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. External vendors require the use of VPN where. Non vendors can access the system within EDLAN only. | ASOR (Release 1-n) | Y | John Chan 05/09/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 | ASOR (Final Release / Handover) | Y | John Chan |
|
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 | ASOR (Release 1-n) | Y | Heather Larnach 08/09/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 | ASOR (Release 1-n) | Y | Heather Larnach 08/09/2014 |
|
Security | All security requirements, e.g. SSL encryption, IP based restrictions firewall requirements have been specified, tested and implemented in LIVE | ASOR (Release 1-n) |
|
|
|
|
|
|
|
|
|
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
Will be on windows patching schedule | ASOR (Final Release / Handover) | Y | John Chan 05/09/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 On virtual infrastructure | ASOR (Release 1-n) | Y | John Chan 05/09/2014 |
|
Start/Stop scripts | Are Server Start-up/Shutdown scripts in place? Including start-up procedure documented, enabled and tested. | ASOR (Release 1-n) |
|
|
|
Ports | Port allocation file been updated:
https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers | ASOR (Release 1-n) |
|
|
|
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) |
|
|
|
DR Copy | DR copy to Edzell configured and tested(unless existing database which is already setup). | ASOR/Release1 |
|
|
|
Logs | For all logs the following is in place:
| ASOR (Release 1-n) |
|
|
|
| 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 05/09/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 SLA in progress between Programme Manager and Production Management. This will be done outwith this project. | ASOR (Final Release / Handover) | N/A | John Chan 05/09/2014 |
|
Time Recording Code | A Time Recording code for the application, if required, has been confirmed and set up. ESTS01 code to be used. | ASOR (Final Release / Handover) | Y | John Chan 05/09/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 | ASOR (Release 1-n) | Y | John Chan 05/09/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 05/09/2014 |
|
Hardware and Software Licensing | All required licensing is in place including maintenance/support arrangements with external suppliers. | ASOR (Final Release / Handover) | Y | John Chan 05/09/2014 |
|
Browser Compatibility | Browser compatibility has been tested and compatibility information updated See for details | ASOR (Final Release / Handover) | Y | John Chan
|
|
Portal Compatibility | Portal compatibility, where required, has been confirmed the Portals Service Owner. No portals used. | ASOR (Final Release / Handover) | N/A | John Chan
|
|
Help Desk | The new application is recognised with the UniDesk (A business contact queue is defined where initial calls are raised with) Existing support arrangements. | ASOR (Final Release / Handover) | Y | John Chan 05/09/2014 |
|
User Guide Documentation | Appropriate documentation has been produced for users of the new application. No changes required. | ASOR (Final Release / Handover) | N/A | John Chan 05/09/2014
|
|
Training Material | Training material, if required, has been produced and is of an appropriate standard. | ASOR (Final Release / Handover) | N/A | John Chan
|
|
Demonstration or Walkthrough | Demonstration or walkthrough of the new application has taken place for other stakeholder. | ASOR (Final Release / Handover) | Y | John Chan 05/09/2014 |
|
Deployment Date(s) | Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review. See deployment strategy at top of this page. | ASOR (Final Release / Handover) | Y | John Chan 05/09/2014 |
|
Deployment Resources | IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured. Anne Mathison to organise. | ASOR (Final Release / Handover) | Y | John Chan 05/09/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 be responsibile for communications. | ASOR (Final Release / Handover) | Y | John Chan 05/09/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 current system not | ASOR (Release 1-n) | N/A | John Chan 05/09/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. IS APPS Wiki page updated. https://www.wiki.ed.ac.uk/pages/viewpage.action?pageId=181666738
| ASOR (Final Release / Handover) | Y | John Chan 05/09/2014 |
|