There are three options when you install FME Server: Express, Custom/Distributed, or Engine.
The Express option allows you to package all the components, or layers, of the FME Server architecture into a single machine. It is the quickest and easiest of the installation options since all components are provided for you, and you only need to provide a single server to host the installation.
Use the Express installation for any of these scenarios:
- You want to get started quickly with a single installation of FME Server.
- You are not planning to implement a distributed or fault tolerance environment with this system.
Distributed/Fault Tolerant Installation
Another option is to install with the Distributed option. With Distributed, you can physically distribute the components into 3-tier or 2-tier configurations:
A Distributed Installation allows you to distribute the FME Server Application (FME Server Core, FME Server Queue, FME Server Web Application), FME Engines, FME Server Database, and the FME Server System Share across physically separate servers. As of FME Server 2018.0, it is recommended that the FME Server Web Application be installed on the same system with the FME Server Core.
If you choose this distributed architecture, you must provide and manage:
- A server for the FME Server Application (and optionally for any of the distributed FME Engines).
- You can run the FME Server Web Services on your own servlet (Apache Tomcat and Oracle WebLogic are supported), or use the Apache Tomcat servlet provided with the FME Server installation.
- A database server to host the FME Server Database (Oracle, PostgreSQL, and SQL Server are supported).
- A remote file system to host shared resources. This must be accessible using the UNC protocol and not through mapped network drives.
The diagram above shows the two distributed installations types recommended by Safe Software.
Benefits of a distributed architecture
Implementing a multi-tier architecture is good if you want to keep components separate so that each can be managed by the appropriate expert team. You also have finer control over applying security updates to the FME Server, FME Server Engines and Database servers when they are separate entities.
If you use the default FME architecture, you do not have the same amount of control for security.
Implementing a multi-tier architecture
You can implement a multi-tier architecture by:
- Choosing one of the Distributed Installation options at installation time, or
- Although you can never configure an Express installation to be fault tolerant or separate the web and engine components, after an Express installation you can choose to change the database provider for the FME Server Database to a database on a separate machine.
The third option for FME Server installation is an Engine-only installation. The Engine installation allows you to build onto a current FME Server distributed installation by adding FME Engines on a separate machine. By installing additional FME Engines on a separate computer from the FME Server Core, you add both processing capacity and fault tolerance to your FME Server.
There is also the option for Silent installation with either Linux or Windows.
When performing a Silent installation, you can override any default installation properties to customize the installation. Installation properties can be set in advance or run with their default values.
The following command is an example of a silent installation on Windows for an install with all default options (similar to an Express install), with logging enabled:
msiexec /i fme-server-2019.0.1.1-b18312-win-x64.msi /qb /norestart /l*v installFMEServerLog.txt