Remote Engine Services

SelectEngine Management>Remote Engine Services.

Technology Preview

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

Remote Engine Services allow you to use queues to run jobs on separate, specialized installations ofFME Flowthat may be closer to your data, while bypassingQueue Controlrules. You can install Remote Engine Services and connect to them on servers that are part of your network, available outside your network on accessible endpoints, or in the Cloud, such as Azure Functions or Google Cloud Functions. UnlikeAdding FME Engines on a Separate Machine、远程引擎服务可能特别有用if you want to run jobs on servers outside your network, while maintaining your primaryFME Flowinstallation behind a firewall.

Capabilities and Limitations

When running jobs on Remote Engine Services, keep in mind the following:

  • FME Enginesof Remote Engine Services can run on any type oflicense, Standard or Dynamic. Multiple engines of both types are supported, depending on licensing terms.
  • Connecting to Remote Engine Services through a proxy is supported.
  • FME Flowqueues jobs when Remote Engine Services are offline, and submits them for processing once they are online.
  • Remote Engine Services can acceptworkspaces that are registered to run only theJob Submitter Service. OtherFME Flow Web Servicesare not supported.
  • Remote Engine Services cannot run jobs submitted directly from aRun a WorkspaceorRun a Dynamic Workspaceautomations action.Workspaces submitted fromSchedulesorWorkspace Appsare supported.
    • Tip  "> Tip Workspaces that contain FMEFlowJobSubmitter transformers can submit jobs to Remote queues, even if thoseworkspaces are invoked from Run aWorkspaceor Run a DynamicWorkspaceactions.
  • Remote Engine Services cannot runcustom formatsorlinked transformers.

Getting Started with Remote Engine Services

To target remote engine services to run jobs:

  1. Install remote engine services on your remote server.
  2. Create queues (if necessary).
  3. Create a connection to a Remote Engine Service and associate it with one or more queues.
  4. Run the job on one of the specified queues.

Install Remote Engine Services

Follow the instructionshereto install remote engine services on your remote server. To obtain a remote engine service installer, visit theFME downloads page. Remote engine service installers are named beginning withfme-flow-remote-engine-*.

Create Queues (if necessary)

You may already have queues that you use to target jobs to FME Engines based on existingQueue Controlrules. When specified explicitly in aRun Workspacedirective, those same queues can run jobs on remote engine services, effectively bypassing queue control rules. Alternatively, you can create new queues and use those instead. To create new queues, select theQueuestab, and clickNew.

Create a Remote Engine Services Connection and Associate it with Queues

  1. On the Remote Engine Services tab of the Engine Management page, clickCreateand complete the following fields:
    • Name: Specify a name of your choice for the Remote Engine Service connection.
    • URL: The URL of the remote server on which theFME FlowRemote Engine Service was installed.
    • Username: The username of theFME FlowRemote Engine Service account.
    • Password: The password to authenticate the accountUsername.
    • Queues: The queues to associate with the Remote Engine Services connection. When one of these queues is specified explicitly in a runworkspacedirective, the job is routed to this connection.
    • Standard Engines: Specify the number of StandardFME Enginesyou want to start on the Remote Engine Service for running jobs.
      Note  "> NoteThis number is limited to yourLicensingterms.
    • CPU Usage Engines: Specify the number of Dynamic (CPU Usage)FME Enginesyou want to start on the Remote Engine Service for running jobs.
      Note  "> NoteThis number is limited to yourLicensingterms.
    • Proxy Enabled: To connect to the Remote Engine Service through a proxy, check this box and complete the following:
      • Host: The proxy server hostname.
      • Port: The port through which communication with the proxy server takes place.
      • No Proxy For: (optional) A list of hostnames and IP addresses that will be accessed through a direct connection, bypassing the proxy. To avoid entering multiple hosts in the same domain, hosts can be prefixed and appended with the wildcard character*.

        • To delimit the list, use commas, semicolons, or press the tab or enter keys. Do not copy-paste a list of entries. To delineate properly in the display, each entry must be added separately.

        Example:

        Note  "> NoteSpecifyinglocalhostdoes not include, by default,127.0.0.1or::1. To bypass the proxy when the local host is referenced, you must explicitly specify any other expected forms for referencing local traffic.
      • Authentication Required: Click if authentication is required to access the proxy server, and complete the following:
        • Username:运行专业帐户的用户名xy server.
        • Password: The password for the proxy server account.
        • Authentication Method: The authentication method used by the proxy server, eitherBasic,Digest, orNTLM.
  2. (Optional) If the Remote Engine Service is currently online, clickTestto ensure the specified credentials are valid.
  3. ClickOK.

The Remote Engine Services 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 Services Connection

On theRunWorkspaceorSchedulespage (under Advanced), specify the desiredJob Queueassociated with the Remote Engine Services 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 Services connection.

Administering Remote Engine Services

Administrators of Remote Engine Services installations can access theJobs,Analytics, andEnginespages of theFME FlowRemote Engine Service Web User Interface.

Resetting the Cache

When jobs are submitted to remote engines,FME Flowautomatically uploads contents to the remote engine service that are necessary to run the job, including theworkspaceand its dependencies, such as resources, packages, web connections, web services, and database connections. To clear this cache, select the Remote Engine Service for the cache you want to clear, clickActions, and selectReset Cache.

Removing Remote Engine Services

Select the Remote Engine Service you want to remove, clickActions, and selectRemove.