Remote Engines

Select Engine Management > Remote Engines.

Technology Preview

Note: This feature is under active development. Expect changes to the current behavior, and avoid using it in production environments.

Remote engines allow you to use queues to run jobs on remote installations of FME Server that may be closer to your data, while bypassing Queue Control rules. You can connect to a remote FME Engine on an FME Server that is part of your network, or on a separate FME Server configured in the cloud, such as FME Cloud, Azure Functions, or Google Cloud Functions.

Capabilities and Limitations

When running jobs on remote engines, keep in mind the following:

• Engines can run remotely on any type of license, Standard or Dynamic.

• Remote engines that connect through a Proxy are supported.

• Remote engines can queue jobs when offline, and run them once engines are online.

• Remote engines can accept workspaces that are registered to run only the Job Submitter Service.

• Remote engines cannot run jobs submitted from a Run a Workspace or Run a Dynamic Workspace automations action. Workspaces submitted from Schedules or Workspace Apps are supported.

• Remote engines cannot run custom formats or linked transformers.

Getting Started with Remote Engines

To target remote engines to run jobs:

1. Create queues (if necessary).

2. Create a connection to a remote engine and associate it with one or more queues.

3. Run the job on one of the specified queues.

Create Queues (if necessary)

You may already have queues that you use to target jobs to FME Engines based on existing Queue Control rules. When specified explicitly in a Run Workspace directive, those same queues can run jobs on remote engines, effectively bypassing queue control rules. Alternatively, you can create new queues and use those instead. To create new queues, select the Queues tab, and click New.

Create a Remote Engine Connection and Associate it with Queues

1. On the Remote Engines tab of the Engine Management page, click Create and complete the following fields:

• Name: Specify a name of your choice for the remote engine connection.

• URL: The URL of the FME Server on which the remote FME Engines reside.

• Username: The username of the FME Server account.

• Password: The password to authenticate the account username.

• Queues: The queues to associate with the remote engine connection. When one of these queues is specified explicitly in a run workspace directive, the job is routed to this connection.

2. (Optional) If the remote engine is currently online, click Test to ensure the specified credentials are valid.
3. Click OK.

The remote engine connection appears on the Engine Management page. You may need to refresh the page until the STATUS icon shows a green check mark.

Run a Job with the Remote Engine Connection

On the Run Workspace page (under Advanced), specify the desired Job Queue associated with the remote engine connection that you want to run the job. The specified queue overrides the queue that would otherwise be assigned based on queue control rules, and instead routes the job to the remote engine connection.