Adding FME Engines on a Separate Machine

You can add processing capacity to your FME Server by installing additional FME Engines on a separate computer from the FME Server Core.

WARNING: We recommend installing all FME Engines on systems that are synchronized to the same time zone as other FME Engines and the FME Server Core. If time zones differ, unexpected issues may arise, including:
Difficulty accessing the FME Server Web User Interface.
Improper timing of Schedule Initiated triggers.
Inconsistent or misleading timestamps in log files (accessed from Resources).

In the instructions below, the computer that hosts the FME Server Core is the <coreHost>.

Note: To avoid confusion when configuring scheduled tasks and viewing logs, we recommend that <engineHost> be configured for the same time zone as <coreHost>. For more information, see About Times and Time Zones.

Note: In a fault-tolerance environment, we recommend assigning unique names to FME Engines. However, if multiple FME Engine hosts have the same FME Engine name, the job queue server configuration applies to all FME Engines with the same name in the same way regardless of which host it resides on. For more information, see Job Queues.

  1. Obtain the Installer. Be sure to obtain the FME Server Installer (not the Engine Installer).
  2. Start the installer on another computer (<engineHost>).

  3. On the Installation Extractor dialog, specify a Destination folder in which to extract installation files. Note that this folder only specifies where installation files are extracted—it does not specify where FME Server program files are installed. That location is specified later in the installer.

    Tip: Take note of the specified Destination folder location. Following installation, you may wish to:

    Review the installation .log file.

    Remove these files. Doing so saves almost 2 GB disk space.

    Click Install.

    When extraction is complete, the installer opens. Proceed through the installer to the Choose Setup Type dialog.

  4. On the Choose Setup Type dialog, select the Distributed Engine setup type.
  5. On the Destination Folder dialog, specify the directory to install the FME Engines.
  6. On the User Account page, specify the Windows user account that will run the <engineHost>. This account must have:
    • Read/Write access to the FME Server System Share that you specify in the next dialog. The System Share is the location where FME Server stores Repositories and Resources files.
    • Read/Write access to the FME Server installation directory that you specified in the previous dialog.
    • "Log on as a service" rights on the <engineHost>. For more information, see this Microsoft Docs article.
  7. On the Existing FME Server System Share dialog, provide the UNC path to the FME Server System Share directory.

    8. If the <coreHost> machine is an Express installation of FME Server, the System Share is written, by default, to %ALLUSERSPROFILE% \Safe Software\FME Server\, unless specified otherwise.

    Note: Unless modified, C:\ProgramData is the default value of the %ALLUSERSPROFILE% environment variable.

    In all cases, enter the UNC path to the System Share, including the final Safe Software\FME Server directories, which are created by default. For example, \\MyServer\Safe Software\FME Server.

  8. On the FME Server Hostname dialog, enter the hostname of the <coreHost> computer.
  9. On the Database Server Type dialog, specify the database type that you specified when installing the FME Server Core. If you specified a database other than the "FME Server Database," enter the connection parameters in the next dialog.
  10. On the Install Python 2.7 dialog, specify whether you want to install an optional Python 2.7 interpreter. (A Python 3.7 interpreter is installed by default.)

    11. WARNING: The Python 2.7 interpreter relies on the Visual Studio 2008 runtime, which has security vulnerabilities. If you will run existing FME Desktop workspaces from FME Server that reference Python 2.7, we strongly recommend upgrading them to reference Python 3.x in lieu of installing the Python 2.7 interpreter.

  11. Complete the remaining dialogs of the FME Server Installer.
  12. If this <engineHost> is connecting to a <coreHost> that also hosts the built-in FME Server database and the initial FME engines, as with an Express Installation, allow the necessary connection to this machine:
    1. On the <coreHost>, open file pg_hba.conf, located in %ALLUSERSPROFILE%\Safe Software\FME Server\pgsql\data.

      2. Note: Unless modified, C:\ProgramData is the default value of the %ALLUSERSPROFILE% environment variable.

    2. Change the following lines:

      3. host    all     all     127.0.0.1/32      md5

      host    all     all     ::1/128         md5

      to:

      host    all      all       0.0.0.0/0         md5

      host   all      all     ::/0             md5

    3. Restart the FME Server Database and FME Server Engines services.
  13. If the <coreHost> machine was an Express Installation of FME Server, complete the following steps on the <coreHost> to configure the FME Server Web Services:
    1. Open the corresponding propertiesFile.properties file for the Data Download, Data Streaming, Job Submitter, and Notification services, located at <FMEServerDir>\Utilities\tomcat\webapps\<service_name>\WEB-INF\conf\propertiesFile.properties.

      2. For example, the properties file for the Data Download Service is at <FMEServerDir>\Utilities\tomcat\webapps\fmedatadownload\WEB-INF\conf\propertiesFile.properties

    2. For each properties file, locate the parameter REQUEST_DATA_DIR and change the value from a local file system path (for example, C:/ProgramData/Safe Software/FME Server//resources/system/temp/requestdata) to a UNC path that references the <coreHost> (for example, //MyHost/FME Server/resources/system/temp/requestdata).

      3. Note: Use forward slashes only.

    3. After saving the changes in the properties file for each service, restart the FME Server Application Server service.
  14. On the <coreHost> machine, open configuration file fmeServerConfig.txt, located in <FMEServerDir>\Server\, and update the FME_SERVER_HOST_NAME parameter to a value that fully resolves to the IP address of the <coreHost> machine.
  15. Restart the FME Server Core service.
  1. If not already accomplished, mount the directory that holds the FME Server System Share. (The System Share holds FME Server Repositories and Resources):

    2. sudo mount -t nfs <coreHost>:/<FMEServerSystemShare> /<mntPath>

  2. Obtain the Installer. Be sure to obtain the FME Server Installer (not the Engine Installer).
  3. Start the FME Server Installer:

    4. sudo ./<installationFile>

  4. From the setup type list, choose Engine.

  5. The installer prompts you for a location to install the FME Server Engine components. This can be on the local machine.

  6. The installer prompts you for the name of the <coreHost>. In a fault-tolerant installation, the primary <coreHost> should always be specified. Do not specify the failover host.

  7. The installer prompts you for the FME Server System Share location. Enter the mounted directory created in step 1.

  8. Enter the database type you specified when installing the FME Server Core. If you specified a database other than the "FME Server Database", enter the connection parameters.
  9. Complete the remaining dialogs of the FME Server Installer.
  10. Manually start FME Server, and configure it to start automatically.
  11. If this <engineHost> is connecting to a <coreHost> that also hosts the built-in FME Server database and the initial FME engines, as with an Express Installation, allow the necessary connection to this machine:
    1. On the <coreHost>, open file pg_hba.conf, located in <FMEServerDir>\Utilities\pgsql\data\.
    2. Change the following lines:

      3. host    all     all     127.0.0.1/32      md5

      host    all     all     ::1/128         md5

      to:

      host    all      all       0.0.0.0/0         md5

      host   all      all     ::/0             md5

    3. Restart the FME Server Database and FME Server Engines services.
  12. Ensure that the user account that runs <engineHost> has the necessary permissions to access the FME Server System Share and the FME Server install directory. For more information, see Directory and Account Permissions.
  13. On the <coreHost> machine, open configuration file fmeServerConfig.txt, located in <FMEServerDir>\Server\, and update the FME_SERVER_HOST_NAME parameter to a value that fully resolves to the IP address of the <coreHost> machine.
  14. Restart the FME Server Core service.

The installation on <engineHost> starts two FME Engines by default. The FME Engines start and register with the FME Server Core running on <coreHost>. All licensed engines are listed on the Licensing & Engines page of the Web User Interface, under 'Licensed Engines'.

Note: You may have to disable any firewalls that are running on this computer.

You can also use the Engines & Licensing page to perform the following tasks:

For more information, see Verify the Installation (Windows) or Verify the Installation (Linux).