It looks like with the changes done in the Integrity 12 and higher versions, to accommodate architectural changes from JBoss to Tomcat, there is more customization needed.
ex.
https://www.ptc.com/en/support/article?n=CS301619
If it's a war file from prior JBoss/Integrity usage, it would need to be made compatible with Tomcat.
ex. Modifying the existing deployment descriptor "web.xml" and also creating a web service deployment descriptor "sun-jaxws.xml" in the war file.
Seems like the general steps for a Tomcat .war file, as I understsand it, would be:
Copy the custom war file to following location in server install directory : server/mks/deploy/
2. Create a xml file in following location in server install directory : server/conf/Catalina/localhost/
The name of the xml file should be same as the context in the URL. Generally format of URL is like, http://<hostname>:<port>/<context>;
Example: If the URL is http://localhost:7001/demo/sample then name of xml file should be demo#sample.xml. Note that / in URL's context is to be replaced by # in name.
Then add below content to xml file:
<Context docBase="${catalina.base}/mks/deploy/<name of custom war file>.war" crossContext="true" cookies="false">
<Manager pathname=""/>
<JarScanner scanClassPath="false" scanAllFiles="false" scanAllDirectories="false">
<JarScanFilter tldSkip="*.*"/>
</JarScanner>
</Context>
In the above example content replace <name of custom war file>.war with the name of custom war file.
Consulting with PTC's services/solutions folks, seems like it might be a good avenue.
