Overview

Overview

3.1 Background

The PURE system delivers a functional and usable research management information system, designed for researchers, administrators, and managers across the University. The PURE database infrastructure has reached an age where it is no longer satisfying the demands made of it.

IS Applications are currently undertaking a series of projects to migrate existing databases from our old database infrastructure to the new one established under project ITS100.

The reasons for the moves are well known, with the old environment approaching the end of its lifespan, and the various benefits of improved performance and greater reliability being offered by the new infrastructure, as well as the potential of better failover capabilities.

This project covers the migration of the PURE database (currently in BETA, TEST & LIVE) to the new infrastructure. The project will also be aligning the both PURE and the PURE interfaces (called PUREINT) to the DEV, TEST and LIVE environments on the new infrastructure.

3.2 Scope, Objectives and Deliverables

 The scope of this project includes the following:

1)     Establishing the parameters of what needs to be done for the migrations using the guidance available here

2)     Configuring environments in DEV, TEST and LIVE

3.)    Collapse PUREINT schema and the PURE schema inot the same instance

4)     Setting up a fresh installation of PURE in DEV on the new infrastructure (this will include Java 7 and Tomcat 7 and all associated scripts and configuration files)

5)    Respecting external file paths in all environments

6)     Check internal configuration

7)     PUREINTBROWSER users and passwords need to be confirmed as working for the sync jobs

8)     Check the database links are changed / updated to point to DEV HR, Finance, VRS apps

9)  Configure the Pure Web Services apache log-ons set up in BETA to DEV to allow web service testing

10)  Change the PUREBETA environment to be secured with DEV EASE from TEST EASE

11)  Setting up versions of the PURE database (currently called BETA) in DEV, TEST and LIVE that will replace those on the old infrastructure

12)  Updating the TAD and any other relevant documentation

Image 1.1 This is the proposed design for the database migration:

No changes that would affect the functionality of the database or related applications will be made. The decommissioning of older versions of migrated databases has not been included in the scope of migration projects so far but will be considered as far as possible, within the time & cost limits of the project.

 The objectives are as follows:

1. To migrate the PURE schemas from the TEST and LIVE environments on the old infrastructure to DEV, TEST and LIVE environments on the new infrastructure
2. To update supporting technical documentation for the migrated databases & related applications

The deliverables for the project are:

1. A migrated version of the PURE database in DEV, TEST and LIVE
2. Updated technical and support documentation

3.3 Benefits

This project will deliver the standard benefits expected of each of the database migrations:

                             1.     Increased reliability

2.     Reduced support time

3.     Reduced loss of service

4.     Improved customer service

• In addition the existing infrastructure is non-standard, in that there are DEV,  BETA, TEST and LIVE environments and DEV has become out of synch with the actual development. This project will restore the standard development architecture of DEV, TEST and LIVE and thus will make all future projects in relation to PURE more straightforward and remove the need for the BETA environment..

3.4 Success Criteria

The success of the project will be determined by the successful move of the PURE database to the new Infrastructure with no loss of performance and standard BETA, TEST and LIVE environments.