Changing the context root of the JTS server bundled with RDM

We've just setup a new RDM instance to go along side our CLM setup. In our CLM configuration we have a reverse proxy sitting in front of our application servers that directs requests from users to the relevant application server.

For RDM we want to use the same domain we are using for CLM, meaning that we need to add a new rule to our proxy to forward requests to RDM. Because the proxy is already forwarding /jts to our CLM JTS server, we need to change the context root of the JTS server bundled with RDM so that we can have a distinct URL.

A while ago I asked this question and learned that in order to change the context root of a CLM application all you need to do is rename the war file and the relevant configuration directory in the /server/conf folder.

I've tried doing this for our RDM JTS application (renamed to jts01), however in the logs I can see that on startup it's still looking for files in the /server/conf/jts folder and we get a 404 error when hitting https://localhost:9443/jts01

Is changing the context root of the RDM JTS server supported, and if so, what do I need to do to get it working?

Thanks