FME Server Ports

The following ports are used by FME Server:

Port Description Process
Windows Linux
80* Web application server (for running the FME Server Web Services) and automatic Licensing requests. FMEServer_ApplicationServer.exe java
445 FME Server System Share (for storing Repositories and Resources). System Not applicable
6379 FME Server Queue, for managing Queue Control. redis-server.exe, FMEServer.exe redis-server, FMEServer
7069 Database Connections and Web Connections requests. FMEConnection.exe FMEConnection
7070 FME Engines register on this port initially, after which they are assigned a dedicated port for communication. FMEEngine.exe, FMEServer.exe fme, FMEServer
7071 Run Workspace, Projects, Workspaces, Licensing, User Management and Automations Log requests. FMEServer.exe FMEServer
7072 Automations external actions and Notification Service subscriber requests. FMENotifier.exe FMENotifier
7073 Schedules requests. FMEScheduler.exe FMEScheduler
7074 Automations external actions and Notification Service subscribers register on this port initially, after which they are assigned a dedicated port for communication. FMENotifier.exe FMENotifier
7075 Automations triggers and Notification Service publisher requests. FMERelayer.exe FMERelayer
7076 Automations triggers and Notification Service publishers register on this port initially, after which they are assigned a dedicated port for communication. FMERelayer.exe FMERelayer
7077 FME Server configuration and Backup & Restore requests. FMEConfiguration.exe FMEConfiguration
7078 WebSocket Server requests. FMEWebSocket.exe FMEWebSocket
7079 Resources requests. FMEMountPoint.exe FMEMountPoint
7081 System Cleanup requests. FMECleanup.exe FMECleanup
7082** The PostgreSQL database server that hosts the FME Server Database provided with the installer. postgres.exe postgres
7500 Manage FME Engines processes, cancel FME Engines, and add/remove FME Engines. FMEProcessMonitorEngines.exe FMEProcessMonitorEngines
7501 Manage FME Server Core processes. FMEProcessMonitorCore.exe FMEProcessMonitorCore

* If you specified another port for the Web Application Server during installation (for example, 8080) or configured your FME Server for HTTPS (for example, on port 443), reference that port instead.

** If you are using your own database server rather than the PostgreSQL database server provided with the installer, reference the applicable port instead. The following table lists the default ports for each database server provider. For more information, check with your database administrator.

Database Provider Port
PostgreSQL 5432
Microsoft SQL Server 1433
Oracle 1521

See Also

Diagram of FME Server Ports

Mouse-over for diagram:

Defining an Ephemeral Port Range

FME Server makes use of ephemeral ports. For certain processes, ports are used to establish an initial connection, after which another random port is opened for dedicated communication, freeing up the original port to connect with other services. If your FME Server installation distributes components across a network in a locked-down environment with strict firewall rules, you must define a dedicated pool of ports that FME Server can use for the random port assignment.

  1. Open fmeServerConfig.txt.
  2. Locate parameter FME_SERVER_PORT_POOL, under FME SERVER SETTINGS START > Port and Host Assignments.
  3. The default value is 0, meaning the dedicated port assignment is random. Change the parameter to a valid range of available ports. For example, 7100-7150.
  4. Repeat steps 2-3 with the propertiesFile.properties files that correspond to the following FME Server Web Services:
    • fmerest
    • fmedatadownload
    • fmedatastreaming
    • fmejobsubmitter
    • fmenotification
  5. Restart the FME Server Application Server, FME Server Core, and FME Server Engines services to apply these changes.
  6. Create the associated firewall exceptions for this range.

Other Ports

Depending on functionality, FME Server will also occupy additional ports, including but not limited to:

Functionality Port
Automations FTP/SFTP
SMTP Email Trigger
IMAP Email Trigger
SMTP Email Action
21/22
25 (Windows), 7125 (Linux) or 465 (secured)
993 (Gmail, Outlook, Office365, Yahoo)
465 (Gmail, Yahoo) or 587 (Outlook, Office365)
System Email 465 (Gmail, Yahoo) or 587 (Outlook, Office365)
Active Directory 389 or 636 (secured)
Proxy 8080
File Share Protocols 445
Apache Tomcat Shutdown Request 8005
On servers running Remote Engines, for communication with requesting FME Server. 443