The explanation of the issue was long, but the resolution is fairly simple. All we need to do is restore the setenv.sh to the tomcat home location, so we can just run installService.sh again. Once doing that, the instance can be started up and runs with the proper resources and variables. As a note for future upgrades, any time you upgrade the linux archive install you should run installService.sh as well before starting up.