Engines
Select Engine Management > Engines.
Note: To license your FME Engines or view the remaining credits on your Dynamic Engines (CPU Usage), use the Licensing page.
Use the Engines tab of the Engine Management page to perform the following tasks:
- Configure the number of FME Engines to start (see below).
- View the properties defined on your engines. Properties are useful when configuring engine assignment rules for Queue Control and Streams.
- View the queues to which your engines are assigned.
- View the Streams to which your engines are assigned.
- View the Deployment Status of components in your FME Server.
Configuring the Number of FME Engines to Start
Under Hosts, move the cursor over the Standard Engines or Dynamic Engines (CPU Usage) field for the Engine host you want to configure. Use the up/down arrows to change the number of starting engines as desired. Click Change.
Note: Dynamic Engines are configurable only if they are enabled on the Licensing page.
When configuring the number of FME Engines to start, consider the following:
- Dynamic Engines are not configured to start by default. Once started, they are initially assigned to the Default job queue, and charged only for time during which they run jobs.
- Changes on the Engines page are requested through port 7500, by default. To process these requests, it may be necessary to configure a rule in the firewall settings of machines hosting FME Engines to allow open communication through port 7500. To change the port number through which these requests are processed, use the NODE_ENGINE_ADMIN_PORT directive in the processMonitorConfigEngines.txt and fmeServerConfig.txt configuration files.
WARNING: Once started, Dynamic Engines are initially assigned to the Default job queue. Configure Queue Control to ensure your Dynamic Engines run only the jobs you intend.
Tip: To send notifications when Dynamic Engine credits fall below a specified amount, configure the Low Credit system event.