Skip to main content

This is what I was going to post in FME Communities. Please change anything that doesn't make sense as I may have used terminology wrong:

We are currently deploying FME Flow 2024.1.1 and will need to run FME Server 2022.2 in parallel for the next few months while we migrate workspaces/solutions over to Flow. 

With that in mind, we were curious about changing the URL of FME Flow from https://DOMAIN/fmeserver to https://DOMAIN/fmeflow by changing the fmeserver.war file name to fmeflow.war and redeploying Tomcat. Note: We’re using our own version of Tomcat and have a distributed deployment setup. 
We were able to get the new ‘fmeflow’ URL to work with this new .war file and subsequent folders. Our question is: Are there hard-coded elements that we would need to look out for and change to ensure all functions/elements work in FME Flow? 

Hi @mmccart,  We don’t recommend changing the FME Flow URL by renaming the .war file from fmeserver to fmeflow. There are several reasons for this:

This modification isn’t supported by Safe Software. The URL is referenced in many different areas, and there’s no clear way to predict the full impact of making this change. It could cause disruptions to various services, especially in environments with distributed deployments like yours.
The URL is called frequently by internal services, WebSocket connections, and possibly other external integrations. Changing it without knowing all of the dependencies could result in services not functioning as expected, like 404 errors or services failing to start.
Safe Software is aware of the need for more flexible URL customization options, and it’s something that may be addressed in future releases. Until then, making these changes could lead to unsupported behavior, and we strongly advise against it.
Before attempting this, it’s worth asking why or if the URL change is necessary.In summary, it’s a risky and unsupported change, and we recommend avoiding it for now.

Safe Software is working on improvements for future versions that might offer a more reliable way to handle this.

 

Thanks, Toyosi


Thanks for the information. We will look for a different method to handle our issue.


Reply