Skip to main content
Released

Remote Engines on FME Server

Related products:FME Flow
  • May 1, 2020
  • 1 reply
  • 35 views
  • gerhardatsafe
  • siennaatsafe
    siennaatsafe
  • fmelizard
    fmelizard
  • jiriteach
    jiriteach
  • stewartatsafe
    stewartatsafe

fmelizard
Contributor

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.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

jiriteach
Forum|alt.badge.img

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.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings