FME Flow: 2024.1

Adding FME Engines on a Separate Machine

Warning  This topic applies only to traditional FME Flow installations. If your FME Flow runs in a containerized environment, such as Docker Compose or a Kubernetes cluster, this architecture is not supported.
  • Skill Level: Intermediate
  • Estimated Time Required: 30-45 minutes
  • Prerequisites:

You can add processing capacity to your FME Flow by installing additional FME Engines on a separate computer from the FME Flow Core.

When adding FME Engines, keep in mind the following:

  • This approach requires the engine machines to be in the same network as your original FME Flow installation, and in the same data center or geographically close. To run jobs outside of your network, use Remote Engine Services instead.
  • Adding FME Engines that do not match the primary release version of the FME Flow Core is not supported. The primary release version refers to the first decimal value following the release year. For example, if the release version of the FME Flow Core is 2020.0, FME Engines from release versions 2020.0.1 or 2020.0.2 are supported. However, FME Engines from release versions 2020.1 or 2021 are not supported.
  • We recommend installing all FME Engines on systems that are synchronized to the same time zone as other FME Engines and the FME Flow Core. If time zones differ, unexpected issues may arise, including:
  • For more information, see About Times and Time Zones.

In the instructions below, the computer that hosts the FME Flow Core is the <coreHost>.

Note  In a fault-tolerance environment, we recommend assigning unique names to FME Engines. However, if multiple FME Engine hosts have the same FME Engine name, the queue server configuration applies to all FME Engines with the same name in the same way regardless of which host it resides on. For more information, see Queue Control.