Welcome back to TGIF everyone! We hope you all enjoyed last week’s post, and we look forward to bringing you more weekly content!
Today, Bailey is here to share a way to automate starting, stopping, and assigning engines to FME Flow Streams.
FME Flow Streams run a workspace continuously on an FME Engine, meaning that engine is unavailable to process other jobs on your FME Flow. Using the FME Flow REST API and Automations, you can start and stop your stream at certain times, or in response to an event, and free up the engine while the stream is running - all without manual intervention.
Check out a video demo here.
As with FME, there’s always many different ways to do the same thing. If your organization is on a subscription, you can also use dynamic, or CPU-usage, engines to similarly accomplish this. You may also want to implement some checks into this workflow, such as testing whether the stream started successfully before assigning an engine to it. You can do this with additional REST API calls and Testers in your workspace.
Happy FMEing everyone!