Skip to main content

We would like to automate all the steps in deploying and configuring FME FLOW. Most of the steps in the application itself can be done via the API, however there is no option to do this for the proxy settings.

 

We have tried many things already:

-Setting the environment variables in windows

-Running mcd-scripts to set the proxy for windows and FME itself (https://docs.safe.com/fme/2019.0/html/FME_Server_Documentation/AdminGuide/Using_FME_Server_wit)

-Looking all over the v3 & v4 API documentation

-Looking in all the FME flow config files

-adding the proxy settings in the server.yml file in the tomcat folder

All above didn't work

 

So do you still have a suggestion? We assumed it might have to do with security that it is not so easy.

 

Thanks in advance,

 

Matthijs

Back in the day, setting the FME Flow (Server) proxy settings could only be done on the command line. It's mentioned in an old part of the documentation, but there's a decent chance it still works with FME Flow:

https://docs.safe.com/fme/2018.1/html/FME_Server_Documentation/Content/AdminGuide/Using_FME_Server_with_Proxy_Server.htm


Back in the day, setting the FME Flow (Server) proxy settings could only be done on the command line. It's mentioned in an old part of the documentation, but there's a decent chance it still works with FME Flow:

https://docs.safe.com/fme/2018.1/html/FME_Server_Documentation/Content/AdminGuide/Using_FME_Server_with_Proxy_Server.htm

Thank you for your reply David. Found that also, that still seemed to work for fme server 2019, however the documentation only seems to mention machines hosting the engines services.

 

We would like to set the proxy on the server-wide level on our core machine, so the setting normally configured under "System configuration" -> "Network and email" -> "Proxy". That is neither in the v3 nor the v4 API.


In v4 of the fme flow API it is not possible to configure the application-wide proxy, as is done in the web-application. Are you still working on it, or if not, will this be implemented later? If both no, we would like to see it in the definitive version 4 as a nice-to-have. It would help us in the complete automated deployment of the FME platform.

 

Thanks in advance.


Reply