What is FME Server?
FME Server is the second piece of the FME platform that allows you to do more with data integration workflows created in FME Desktop. Use FME Server to run workspaces on a schedule, create Automations for real-time data processing, or build self-serve data portals. Stay updated by setting up notifications that alert you and your team when new information becomes available.
Automate, manage, and control how data flows in a convenient web interface.
FME Server Essentials
Ready to get started? Below are some of the essential operations you’ll need to know to start working with FME Server.
Run a Job
From the navigation menu select "Run Workspace". Choose a repository, workspace, and service type, plus set any additional parameters you may need. The most popular services are Data Download, Data Streaming, and Job Submitter.
Click “Run” to submit your job.
See which jobs have been completed, are in the queue, or are currently running, by using the Jobs drop-down in the navigation menu.
Build an Automation
With Automations, you run data integration jobs automatically when an event occurs. For example, a new file added to your directory can trigger your workflow to run and integrate the file with your database.
Once complete, the Automation can be set up to send you and your team a notification update with the status of the data.
Set a Schedule
Have data tasks that need to be completed on a specific date or at a regular interval? Set your own custom schedules for any of your workflows to ensure no data gets left behind.
Create Server Apps
FME Server Apps make it easy to share data and increase accessibility for internal and external customers. Create custom web pages for self-serve portals that allow users to upload data for a workspace, or to download data that results from a workspace.
Add Dynamic Engines
If you find yourself needing more processing power, add as many Dynamic Engines as needed for your task and simply remove them once complete. Dynamic Engines is an add-on feature with pricing based on CPU time rather than the number of engines added.