Overview

Background

There is a need to migrate the eTime and JAMS applications to the new virtualised environment as their current location is being decommissioned

JAMS - the Journal Auto-upload Management System is a web-based application used by System Accounting Section (SAS)

eTime  - the timesheet for guaranteed hours and research staff.

Scope

• Migrate JAMS to the new virtualised environment
• Migrate eTime to the new virtualised environment
• Scope is to only include what is already there and to migrate it to a supported IS Apps environment

Objectives

• To migrate JAMS application to a secure and managed IS virtual environment
• To migrate eTime application to a secure and managed IS virtual environment

Deliverables

• Migrate JAMS to a new virtualised environment (JAMS is the Journal Auto-upload Management System which is a web-based application used by SAS).
• Build DEV, TEST and LIVE environments for JAMS
• Stop old JAMS application
• Migrate eTime to a new virtualised environment
• Build DEV, TEST and LIVE environments for eTime
• Stop old eTime application
• Upgrade to later versions of JAVA and Tomcat (optional)

Out Of Scope

• Any enhancements to the either systems (Scope is to only include what is already there and to migrate it to a supported IS Apps environment)
  • The 3 other JAMS processes are Ant-driven runnable jar files scheduled by cron jobs which run in the background
  • Any existing of new eTime JIRAs that are present in other projects
  • disaster recovery testing
• Bamboo is not to be included at this time for JAVA applications
• Upgrade to JAVA v8 is out of scope
• Upgrade to JAVA v7 is out of scope (optional)
• Upgrade to Tomcat v7 is out of scope (optional)

Benefits

• This project will move the application from out of life infrastructure for JAMS

• This project will move the application from out of life infrastructure for eTime

Success Criteria

• That JAMS application continues to function as at present
• That eTime application continues to function as at present