Adding FME Engines on a Separate Machine

Warning "> WarningThis topic applies only to traditionalFME Flowinstallations. If yourFME Flowruns in a containerized environment, such as Docker Compose or a Kubernetes cluster, this architecture is not supported.

Skill Level: Intermediate
Estimated Time Required: 30-45 minutes
Prerequisites:
- ExistingExpress, Distributed, or Fault-TolerantFME Flowinstallation.
- Access to system, network, andFME Flowadministrators.

You can add processing capacity to yourFME Flowby installing additional FME Engines on a separate computer from theFME FlowCore.

When adding FME Engines, keep in mind the following:

Adding FME Engines that do not match the primary release version of theFME Flow Coreis not supported. The primary release version refers to the first decimal value following the release year. For example, if the release version of theFME FlowCore is 2020.0, FME Engines from release versions 2020.0.1 or 2020.0.2 are supported. However, FME Engines from release versions 2020.1 or 2021 are not supported.
We recommend installing all FME Engines on systems that are synchronized to the same time zone as other FME Engines and theFME FlowCore. If time zones differ, unexpected issues may arise, including:
- Difficulty accessing theFME Flow Web User Interface.
- Improper timing ofFME Flow Scheduletriggers.
- Inconsistent or misleading timestamps in log files (accessed fromResources).

For more information, seeAbout Times and Time Zones.

In the instructions below, the computer that hosts theFME FlowCore is the<coreHost>.

Note "> NoteIn 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 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, seeQueue Control.

Windows

Obtain the Installer. Be sure to obtain theFME FlowInstaller (not the Engine Installer).
Start the installer on another computer (<engineHost>).
On the Installation Extractor dialog, specify aDestination folderin which to extract installation files. Note that this folderonlyspecifies where installation files are extracted—it doesnotspecify whereFME Flowprogram files are installed. That location is specified later in the installer.
Tip "> TipTake note of the specifiedDestination folderlocation. Following installation, you may wish to:
- Review the installation .log file.
- Remove these files to save disk space.
ClickInstall.
When extraction is complete, the installer opens. Proceed through the installer to the Choose Setup Type dialog.
On the Choose Setup Type dialog, select the Distributed Engine setup type.
On the Destination Folder dialog, specify the directory to install the FME Engines.
On the User Account page, specify the Windows user account that will run the
. This account must have:
- Read/Write access to theFME FlowSystem Share that you specify in the next dialog. The System Share is the location whereFME FlowstoresRepositoriesandResourcesfiles.
- Read/Write access to theFME Flowinstallation directory that you specified in the previous dialog.
- "Log on as a service" rights on the<engineHost>. For more information, seethis Microsoft Docs article.
On the ExistingFME FlowSystem Share dialog, provide the UNC path to theFME FlowSystem Share directory.

If the <coreHost> machine is an ExpressinstallationofFME Flow, the System Share is written, by default, to %ALLUSERSPROFILE% \Safe Software\FME Flow\, unless specified otherwise.

Note "> NoteUnless 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 finalSafe Software\FME Flowdirectories, which are created by default. For example,\\MyServer\Safe Software\FME Flow.

On theFME FlowHostname dialog, enter the hostname of thecomputer.
On the Database Server Type dialog, specify the database type that you specified when installing theFME FlowCore. If you specified a database other than the "FME Flow Database," enter the connection parameters in the next dialog.
On the Database User dialog, specify the user name and password for theFME FlowDatabase that you specified when installingFME Flow.
Complete the remaining dialogs of theFME FlowInstaller.
If this<engineHost>is connecting to a<coreHost>that also hosts the built-inFME Flowdatabase and the initial FME engines, as with anExpress Installation, allow the necessary connection to this machine:

On the<coreHost>, open file pg_hba.conf, located in %ALLUSERSPROFILE%\Safe Software\FME Flow\pgsql\data.

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

Change the following lines:

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

RestarttheFME FlowDatabase andFME FlowEngines services.

If the<coreHost>machine was anExpress InstallationofFME Flow,完成以下步骤<coreHost>to configure theFME FlowWeb Services:
1. Open the corresponding propertiesFile.properties file for the Data Download, Data Streaming, Job Submitter, and Notification services, located at <FMEFlowDir>\Utilities\tomcat\webapps\<service_name>\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 Flow//resources/system/temp/requestdata) to a UNC path that references the (for example,//MyHost/FME Flow/resources/system/temp/requestdata).
3. After saving the changes in the properties file for each service,restarttheFME FlowApplication Server service.
On the<coreHost>machine, open configuration file fmeServerConfig.txt, located in \Server\, and update the FME_SERVER_HOST_NAME parameter to a value that fully resolves to the IP address of the machine.
RestarttheFME FlowCore service.

Linux

If not already accomplished, mount the directory that holds theFME FlowSystem Share. (The System Share holdsFME FlowRepositoriesandResources):

sudo mount -t nfs <coreHost>:/<FMEFlowSystemShare> /<mntPath>

Obtain the Installer. Be sure to obtain theFME FlowInstaller (not the Engine Installer).
Start theFME FlowInstaller:

sudo ./<installationFile>

From the setup type list, chooseEngine.
The installer prompts you for a location to install theFME Flow引擎组件。这可以在本地食蟹猴e.
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.
The installer prompts you for theFME FlowSystem Share location. Enter the mounted directory created in step 1.
Enter the database type you specified when installing theFME FlowCore. If you specified a database other than the "FME Flow Database", enter the connection parameters.
Enter the user name and password for theFME FlowDatabase that you specified when installingFME Flow.
Complete the remaining dialogs of theFME FlowInstaller.
ManuallystartFME Flow, and configure it to start automatically.
If this<engineHost>is connecting to a<coreHost>that also hosts the built-inFME Flowdatabase and the initial FME engines, as with anExpress Installation, allow the necessary connection to this machine:
1. On the<coreHost>, open file pg_hba.conf, located in <FMEFlowDir>\Utilities\pgsql\data\.
2. Change the following lines:
3. RestarttheFME FlowDatabase andFME FlowEngines services.
Ensure that the user account that runs<engineHost>has the necessary permissions to access theFME FlowSystem Share and theFME Flowinstall directory. For more information, seeDirectory and Account Permissions.
On the<coreHost>machine, open configuration file fmeServerConfig.txt, located in <FMEFlowDir>\Server\, and update the FME_SERVER_HOST_NAME parameter to a value that fully resolves to the IP address of the<coreHost>machine.
RestarttheFME FlowCore service.