I honestly would separate the services out. Clients will use system resources to GET hosted packages, so I would just setup an Apache instance hosting your packages over HTTPS or if you can swing it something in the cloud storage realm (AWS, Azure, GCP, Akamai, etc). What happens if you deploy a new version of MSFT O365 and your fleet is pulling a 1-2 GB package from your Tomcat? I bet that would degrade jamf performance. So, if you already have RHEL, standing up an Apache to host files is fairly easy as you can install all the required packages via yum
