Starting or stopping FileMaker Server components
 
Starting or stopping FileMaker Server components
Note  The following information is for server administrators.
Admin Console allows you to start and stop the Database Server, the FileMaker Data API Engine, a FileMaker WebDirect worker machine, and the XDBC Listener individually without restarting the master machine. You can stop or start these components using controls on the Status pane.
To start or stop the Database Server:
In the Status pane across from the FileMaker Server 16 text, start or stop the Database Server using the following:
To start or stop access via the FileMaker Data API:
In the Status pane across from the FileMaker Data API text, stop or start the FileMaker Data API Engine using the following:
To start or stop the Web Publishing Engine for Custom Web Publishing with PHP and XML:
In the Status pane across from the Web Publishing Engine text, stop or start the first worker machine (Worker Machine: 1), which is the Web Publishing Engine that is running on the master machine.
To start or stop a FileMaker WebDirect worker machine:
In the Status pane across from the Web Publishing Engine text, stop or start a FileMaker WebDirect worker machine using the following:
To start or stop the XDBC Listener:
In the Status pane across from the ODBC/JDBC text, stop or start the XDBC Listener using the following:
Important  When you start or stop a component, it may take some time before the state actually changes. The component may display a disabled state until the process completes.
Notes
If FileMaker Pro is already running while the Database Server is starting up on the same machine, the Database Server will fail to start. Stop FileMaker Pro, then start the Database Server. If this problem persists, restart your computer, then start the Database Server before starting FileMaker Pro.
If the Database Server fails to start, check the Event Viewer (Windows) or Console application (macOS) for error messages.
If you have large files or files with many connected clients, the process of stopping the Database Server may take several minutes. If you encounter problems, disconnect clients. See Disconnecting clients. Also try closing hosted files. See Closing hosted files.
When you stop the Database Server, Admin Console functionality is limited to the Status pane and the Log Viewer pane. To use other functionality, you must start the Database Server again.
When you stop the Web Publishing Engine, you must start it again before you can configure web publishing settings.
You can also stop and start these components from the command line interface. See Using the command line interface for the fmsadmin start and fmsadmin stop commands.
If you need to start or stop the FileMaker Server service or background processes manually, see Starting or stopping the FileMaker Server service (Windows) or Starting or stopping FileMaker Server background processes (macOS).
Related topics 
Startup settings