Ports and Executables and Firewall Exceptions for FME Server

This list is intended to give a starting point when creating inbound / outbound firewall rules to allow communication between all FME Server components. The FME Server Reference Manual has an up-to-date list of ports that FME Server uses, but the tables below highlight the individual executables.

If your FME Server architecture has distributed FME Engines, then please see the section "Distributed FME Server Engines" below.

*Note: this list may not be exhaustive. If you have experienced any different, please leave a comment below.

Port Executable (Inbound)

25 FMEPublisher.exe
465 FMEPublisher.exe
6379 FMEServer.exe
7069 FMEConnection.exe
7070 FMEServer.exe
7071 FMEServer.exe
7072 FMENotifier.exe
7073 FMEScheduler.exe
7074 FMENotifier.exe
7075 FMERelayer.exe
7076 FMERelayer.exe
7077 FMEConfiguration.exe
7078 FMEWebSocket.exe
7079 FMEMountPoint.exe
7081 FMECleanup.exe
7082 postgres.exe
7500 FMEProcessMonitorEngines.exe
7501 FMEProcessMonitorCore.exe

Port Executable (Outbound)

25 none
465 none
7069 FMEServer_ApplicationServer.exe, FMEConfiguration.exe, FMEConnection.exe, FMEEngine.exe
6379 FMEServer.exe
7070 FMEEngine.exe
7071 All executables
7072 All executables
7073 FMEServer_ApplicationServer.exe, FMEConfiguration.exe, FMEScheduler.exe
7074 FMESubscriber.exe
7075 FMEServer_ApplicationServer.exe, FMEConfiguration.exe, FMERelayer.exe
7076 FMEPublisher.exe
7077 FMEServer_ApplicationServer.exe, FMEConfiguration.exe
7078 none
7079 FMEServer_ApplicationServer.exe, FMEConfiguration.exe, FMEMountPoint.exe
7081 FMEServer_ApplicationServer.exe, FMEConfiguration.exe, FMECleanup.exe
7082 FMEConnection.exe, FMEProcessMonitorCore.exe FMEProcessMonitorEngines.exe, FMEServer.exe
7500 FMEServer_ApplicationServer.exe, FMEServer.exe
7501 FMEServer_ApplicationServer.exe, FMENotifier.exe, FMERelayer.exe

Distributed FME Server Engines

Distributed FME Server Engines may require additional configuration to the fmeServerConfig.txt file, found where the FME Server Core has been installed ("<FMEServer_InstallDir>\Server\").

FME Server Engines establish communication with the FME Server Core over Port 7070. Once this connection is established, another random port is opened for dedicated communication - this occurs so that Port 7070 becomes available again for any other service trying to connect.

We have observed that environments with strict firewalls rules ("allow none, except xxxx") that a dedicated port pool must be defined for FME Server.

In fmeServerConfig.txt, there is a parameter called FME_SERVER_PORT_POOL. The default value is 0 - which means that the assigned dedicated port is random. Try setting this parameter to a valid range of available ports - for example - 7100-7150.

After this change is made - and the file is saved - the FME Server Core must be restarted, as well as any distributed FME Engines.

The FME_SERVER_PORT_POOL parameter has been added to the Tomcat/ Web App Server as well. To update this parameter Find where Tomcat is installed, navigate to there in the file system.

Go to the properties file for each web app:
...\webapps\fmerest\WEB-INF\conf\propertiesFile.properties
...\webapps\fmedatadownload\WEB-INF\conf\propertiesFile.properties
...\webapps\fmedatastreaming\WEB-INF\conf\propertiesFile.properties
...\webapps\fmejobsubmitter\WEB-INF\conf\propertiesFile.properties
...\webapps\fmenotification\WEB-INF\conf\propertiesFile.properties

Find the FME_SERVER_PORT_POOL parameter in propertiesFile.properties, change the parameter and restart Tomcat.

!! Make sure to also create the associated firewall exceptions for this FME_SERVER_PORT_POOL range. !!

*Note: You may experience a "stall", "freezing", or "timeouts" of the FME Server Web Interface if the distributed FME Engines are unable to establish communication to the FME Server Core over the randomly assigned port - or if you have configured an invalid range.

keyword: fme server port fme server ports