Starting and Stopping FME Flow Manually

Although the FME Flow System Services start automatically, you can start and stop the services manually in the following ways:

  • From the Services window (the procedure for accessing the services may vary by Windows version):

    • Control Panel > Administrative Tools > Services

    Or

    Start > Run > services.msc

    In the Services window, select one or more of the services, and start or stop as required.

Note  On Windows 8, you must be running as Administrator to start or stop the FME Flow System Services.

Linux scripts for starting and stopping FME Flow are located in:

<FMEFlowDir>/Server/

Although you can configure FME Flow to start automatically, you can start it manually by running startServer.sh as the root user.

This script starts all the FME Flow System Services in the necessary order. Alternatively, to start each service individually, run the following scripts, located in the same directory:

  • startCore.sh: FME Server Core service
  • startEngines.sh: FME Engines
  • startDatabaseServer.sh: FME Server Database
  • startApplicationServer.sh: FMEServerAppServer
  • startWebSocketServer.sh: FME Flow WebSocket Server
  • startCleanup.sh: FME Flow Cleanup service
  • startRootServices.sh - Starts all the services that run as the root user. This script calls startWebSocketServer.sh, startCleanup.sh, and startApplicationServer.sh.

To stop FME Flow, run stopServer.sh as the root user.

Alternatively, stop the services individually with these scripts:

  • stopCore.sh
  • stopEngines.sh
  • stopDatabaseServer.sh
  • stopApplicationServer.sh
  • stopWebSocketServer.sh
  • stopCleanup.sh
  • stopRootServices.sh

What Happens to Jobs After a Manual Restart?

When FME Flow is restarted, the behavior of jobs that are in a Running or Queued state depends on how the jobs were submitted:

 

Run Workspace

Flow Apps

Schedules

Automations

Streams

Full Restart Running jobs are resubmitted to the queue. Queued jobs run before resubmitted jobs. Running jobs fail and are not resubmitted.* Queued jobs run once the FME Flow services are running. Running jobs are resubmitted to the queue. The job ID may change depending on availability of FME Engines.
FME Engines Restart
Core Restart
Database Restart
Web Application Server Restart Jobs continue to run as the FME Engines process the job queue.

* If Retry on Failure was checked on the workspace action of an automation, the job is resubmitted based on the Retry settings once the FME Flow services are running.

A resubmitted job has the same ID as its initial run, and assumes the job_<ID>.log filename. Logs for previous submissions of the same job can be accessed in the same folder. For more information, see FME Job Logs and About Log Files in FME Flow.