FME Server Core
This container should be considered a technical preview and should not be run in production.
FME Server works hand-in-hand with FME Desktop. Design the workflow you want to automate in FME Desktop's drag-and-drop interface and then publish it to FME Server at the push of a button.
Using FME Server you can schedule the workspace you created to automatically run at any time interval, turn it into a self-serve process for others to run whenever they want, or have your workspace always running in real-time.
Find out more at http://www.safe.com/fme/fme-server/
How to use this image
This repository is one of four images, one for each component of FME Server:
- safesoftware/fmeserver-db: The database server to house the FME Server settings and schema
- safesoftware/fmeserver-core: The main Core of FME Server
- safesoftware/fmeserver-web: The web front end of FME Server
- safesoftware/fmeserver-engine: The FME engines that run translations
Since FME Server is a multi-container deployment, the standard way of running these containers together is to use docker-compose with a docker-compose.yml file.
You can download this file from: http://downloads.safe.com.s3.amazonaws.com/fme/beta/docker-compose.yml
EXTERNALHOSTNAME in this docker-compose.yml file should be changed from localhost to the external IP address or hostname you will use to connect to this host. In the fmeserverweb container this is used for topic monitoring in the Web UI. In the fmeserverengine container this is for the Data Download service result download URL.
This will set up the database data and FME Server shared data in your home directory, and start the containers for the Core, Web, Database, and Engines. Further engines can be started using the docker-compose scale command.
In depth instructions for deploying FME Server using these containers can be found here.
We recommend running this on a machine that has at least 4 GB or RAM available. If you are using Docker for Mac or Docker for Windows you can change this in your Docker Settings.
There are several tags for different versions of FME Server available.
latest will always point to the most recent version of FME Server available. For each specific version of FME, there is also a
<version>-latest tag which will be the latest beta of that version available if it is still in development, or the latest release build of that version. The more static versions such as
2017.0, will always point to the release build of that version.
For example, if 2017.0 is the latest release version of FME Server and we have 2017.1 and 2018.0 in development, then the
2017.0 tag will point to the release build for 2017.0,
2017-latest will point to the latest beta for 2017.1, and
latest will point to the latest beta for 2018.0.