Deployment

Implementation Plan

Feedback from previous test implementations completed and successful full implementation undertaken for UAT K:\ISAPPS\dsg\Projects\LMP004\ImplementationPlan_LMP004.doc

DSOR (Release 1-n)

Y

HB

Implementation Risk Assessment

A risk assessment has been undertaken for the Implementation Plan and selected deployment dates. (e.g. roll back) N/A - New system

ASOR (Release 1-n)

N/A

HB

System Design Specification (SDS)

Document complete and accurate.

Action: The Document must be copied to the Wiki https://www.wiki.ed.ac.uk/display/insite/Library+IDM+Integration

ASOR (Final Release  / Handover)

Y

HB

System Description Document

Document complete and accurate.

See SDS

Action: The Document must be copied to the Wiki

ASOR (Final Release  / Handover)

Y

HB

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.

Basic load testing performed using 400 accounts

[appalmal@lac-almasftp full]$ pwd

/home/appalmal/patrons/idm/full

[appalmal@lac-almasftp full]$ ls -l

total 48 -rw-rw-r--. 1 appalmal appalmal   204 Jun  4 18:25 2015-06-04T18-25-48-total-1-batch-1.zip -rw-rw-r--. 1 appalmal appalmal   204 Jun  4 18:33 2015-06-04T18-32-00-total-1-batch-1.zip -rw-rw-r--. 1 appalmal appalmal   201 Jun  5 11:30 2015-06-05T11-30-40-total-1-batch-1.zip -rw-rw-r--. 1 appalmal appalmal   692 Jun  5 11:37 2015-06-05T11-36-57-total-1-batch-1.zip-rw-rw-r--. 1 appalmal appalmal 31531 Jun  5 11:46 2015-06-05T11-41-59-total-1-batch-1.zip

[appalmal@lac-almasftp full]$ The single batch is 2015-06-05T11-36-57-total-1-batch-1.zip and the 400 batch is 2015-06-05T11-41-59-total-1-batch-1.zip

As Library Alma Live system was a new service, full exports from IDM Live were used to perform real load testing averaging 2.5 hours for full load.

ASOR (Final Release  / Handover)

Y

HB

Performance

The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing. Performance reviewed and approved by Alex Forrest of Library & Collections.

https://www.projects.ed.ac.uk/project/lmp004/uat_plan-0

ASOR (Final Release  / Handover)

Y

HB

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)

SVN Link?

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)

Application added as LIBFEED

ASOR (Release 1-n)

Y

HB

Change Control(s)

A change control entry has been created for the LIVE implementation request.

Change Control - 95546

ASOR / (Release 1-n)

Y

HB

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.

All JIRAs addressed

ASOR (Final Release  / Handover)

Y

HB

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)

Handover pending

Support Accounts

Read access accounts or update current read access accounts have been set up for support staff(requires business owner approval) IDM LIBFEED_SERVICEUSER account created on IDMLIVE.

ASOR (Final Release  / Handover)

Y

HB

Password Manager (InfoKeep)

InfoKeep has been updated with all relevant account details including external supplier  accounts

ASOR (Release 1-n)

GEN entries present. IDM libfeed_serviceuser not present

Environment comparison

Database comparison between TEST and LIVE (might be required before and after go-live)

N/A - New system testeddirectou on live.

ASOR (Final Release  / Handover)

Y

HB

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

Interface only - N/A

ASOR (Release 1-n)

Y

HB

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

Standard Java application.

ASOR (Release 1-n)

Y

HB

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.

N/A - Interace Application

ASOR (Release 1-n)

Y

HB

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.

N/A - Interface service only

ASOR (Final Release  / Handover)

Y

HB

Technical Architecture Document(TAD)

Documentation complete and accurately reflects the environment subjected to UAT.

Action: TAD needs to be copied to Wiki

TAD at https://www.wiki.ed.ac.uk/display/insite/Library+IDM+Integration

ASOR (Release 1-n)

Y

HB

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

TAD at https://www.wiki.ed.ac.uk/display/insite/Library+IDM+Integration

ASOR (Release 1-n)

Y

HB

Security

All security requirements, e.g. SSL encryption, IP based restrictions firewall requirements have been specified, tested and implemented in LIVE

Firewall settings detailed in TAD

ASOR (Release 1-n)

Y

HB

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

Deployed on existing servers

ASOR (Final Release  / Handover)

Y

HB

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

Deployed on existing servers

ASOR (Release 1-n)

Y

HB

Start/Stop scripts

Are Server Start-up/Shutdown scripts in place?

Including start-up procedure documented, enabled and tested.

ASOR (Release 1-n)

Y

HB

Ports

Port allocation file been updated:

https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers

GEN entries confirmed

ASOR (Release 1-n)

Y

HB

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)

Tech Mgmt to confirm

DR Copy

DR copy to Edzell configured and tested(unless existing database which is already setup).

Backups via Data Guard

ASOR/Release1

Y

HB

Logs

For all logs the following is in place:

• Logs are rotated and old logs are archived or deleted to ensure server space is not reached
• In production only minimal levels of logging is switched on (debug may be adequate on DEV, but not on Production)

Logging confirmed

ASOR (Release 1-n)

Y

HB

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)

S Kaemof to confirm

Time Recording Code

A Time Recording code for the application, if required, has been confirmed and set up.

ASOR (Final Release  / Handover)

Requested by A Heyn

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

DR as detailed in TAD.

ASOR (Release 1-n)

Y

HB

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)

UAT was performe on Live platform. Confirm Test platform active?

Hardware and Software Licensing

All required licensing is in place including maintenance/support arrangements with external suppliers.

N/A - IS Apps-Developed

ASOR (Final Release  / Handover)

Y

HB

Browser Compatibility

Browser compatibility has been tested and compatibility information updated

See

http://www.ed.ac.uk/schools-departments/information-services/services/computing/application-development/application-support/supported-web-browsers/browser-application

 for details

N/A - Interface application

ASOR (Final Release  / Handover)

N/A

HB

Portal Compatibility

Portal compatibility, where required, has been confirmed the Portals Service Owner.

N/A

ASOR (Final Release  / Handover)

N/A

HB

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)

TBC with A Heyn

User Guide Documentation

Appropriate documentation has been produced for users of the new application.

N/A - Interface application

ASOR (Final Release  / Handover)

N/A

HB

Training Material

Training material, if required, has been produced and is of an appropriate standard.

N/A - Interface application

ASOR (Final Release  / Handover)

N/A

HB

Demonstration or Walkthrough

Demonstration or walkthrough of the new application has taken place for other stakeholder.

Interface application, but tested and approved by customer.

ASOR (Final Release  / Handover)

Y

HB

Deployment Date(s)

Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review.

Implementation date enforced by business requirements

ASOR (Final Release  / Handover)

Y

HB

Deployment Resources

IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured.

N/S - Live Code deployed for testing

ASOR (Final Release  / Handover)

Y

HB

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.

All comms completed by Project Manager.

ASOR (Final Release  / Handover)

Y

HB

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.

N/A - New service

ASOR (Release 1-n)

Y

HB

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.

N/A - Interface application

ASOR (Final Release  / Handover)

Y

HB