Step 1. Migrate legacy JSP system from Windows to AWS Linux — Migrate Front End Application

I have a client with a legacy Java/JSP system built in the mid 2000's that has remained virtually unchanged. Up to now, they have been self-hosted on a Windows 2003 platform. They are looking to update the system to operate on AWS Linux, and migrate it. Currently, the system is not working in production, and the client needs to use it, so we would like to execute this project as soon as feasible. This system is built on JAVA/JSP with Tomcat application server, Apache web server, and MySQL. There are several small, supporting applications that run as services, as well as a number of hard-coded references to the file system, and a few other dependencies on the Windows OS. The system has two main aspects: the front end, public (and staff) facing web site to interact with the system, and a processing system that creates information products. It was built as a distributed system with the front end on one instance, and one or more processing node instances to create products. The client now only services a handful of customers with (usually) only a single individual using the system, so they would like to maintain a single instance with the option of adding processing nodes if necessary. The front end instance includes the code for processing products, and processing nodes have the JSP pages and servlets removed. Step 1. Migrate Front End Application In the first step, the objective is to migrate the front end, and get it working on modern browsers. Most of the breaking dependencies on Windows are in the product creation part of the system, so I would like to leave that to a second step. The rest of the work will be dependent on getting the front end working, so I'd like to do that as soon as possible. I would like to configure one or more development instances so we can do the next steps in parallel, and maintain one pristine production instance. There are issues with the JavaScript responsible for creating product requests, so fixing that will be part of the scope of this step. As a secondary goal, I if time and budget allows, I am happy to make improvements to the configuration of the code, and to deploying future changes. I would also like to document some of the work done to make future changes easier.