Overview
Background
The project will upgrade the core Polopoly CMS application software from 9.16.1 to a newer version that can work with version 11g of the Oracle database and is expected new enhancements to the upgraded version will allow opportunities to be explored.
In addition the Oracle database supporting the Polopoly CMS application is currently Oracle 10g. Support for this version of Oracle runs out in July 2013 and we cannot upgrade to Oracle 11g unless we upgrade the Polopoly CMS application.
The project will also address the requirement to upgrade the front end servers and determine whether they can be hosted on a VM environment.
Scope
The project will deliver an upgrade to the current Polopoly CMS version from 9.16 to 10.0 FP 5. DEV, TEST and LIVE environments will be upgraded. The database version will not be upgraded. This will be upgraded as part of UWP008.
Objectives
The main objective of the project is to Upgrade to Polopoly CMS version and return the system to LIVE service. To achieve this will require investigation into the appropriate version to upgrade to provide the compatibility required for upgrading the database to Oracle 11g. The new version should provide the stability of operation required by UWP and the user community and potentially , additional features which can be exploited by the user community. As the Front end servers are nearing the end of ther operational life, this project will replace them with new VMs, two for TEST and two for LIVE. The servers to be replaced are :-
LIVE servers: MINT + OLIVE
TEST servers: SPYNIE + STALKER
Deliverables
The project will provide
1. An assessment and recommendation of which version of Polopoly to use for the upgrade. The essential criteria will be its compatibility with the Oracle 11g.
2. Full Test Plan and Testing Report from the UWP Team.
3. An upgraded Dev, Test and LIVE environment.
4. An assessment of the fitness of the TEST environment for the purpose of testing out the upgraded CMS prior to going LIVE.The TEST environment should reflect the LIVE environment to allow testing and training to be carried out with confidence that what happens in TEST reflects what will happen in LIVE."?
5. To provide an implementation plan.
6. To provide a roll back strategy in the event of issues. The criteria for rollback will be agreed beforehand.
7. Upgraded front end servers for the TEST and LIVE environments (two servers for TEST and two for LIVE) .
8. Implementation plan for the new servers.
9 .Load test on the new servers.
10. DR test on the new servers .
Benefits
The upgrade will allow the underlying POLO database version to be upgraded to version 11g . It is currently version 10 which ran out of support in July 2013.
Success Criteria
To successfully upgrade the Polopoly Content Management System to version 10.0 and introduce the new TEST and LIVE front end servers with acceptable performance.
DR Test completed.
Documentation for services updated and accepted.