Skip to main content
  • EN

Currently, FME Engines must be located in the same network as the FME Server install. Remote Engines would enable you to deploy the FME Engine in a different network to the FME Server core. The Remote Engines would communicate securely with the FME Server Core over the internet. This would enable the following workflows:

  • Hybrid Deployments - Spread your FME Engines across multiple clouds, on-premises and the cloud, or within a cloud in different networks (e.g. public, private clouds)
  • Regional Offices - Deploy the FME Server in one office region, and then deploy Remote FME Engines into other office regions next to their data.
  • IoT Workflows - Deploy the Remote FME Engines on the edge directly next to the sensor.

In short, it will enable you to move FME closer to the data without having to manage multiple FME Servers.

Great idea - or even the concept of a remote probe which could allow connections to an on-premises dB for example while the engine and workbench runs in the cloud.

Community Stats

30,351
Posts
115,341
Replies
38,080
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.