If you have administrative permissions, you can shut down the XL Deploy server using the command-line interface (CLI) command:


You can also stop the XL Deploy server using a REST API call. This is an example of a command to generate such a call (replace admin:admin with your own credentials):

curl -X POST --basic -u admin:admin http://admin:admin@localhost:4516/deployit/server/shutdown

This requires the external curl command, available for both Unix and Microsoft Windows.

Note: If you modify any file in the XL_DEPLOY_SERVER_HOME/conf directory, or modify the XL_DEPLOY_SERVER_HOME/ext/synthetic.xml or XL_DEPLOY_SERVER_HOME/ext/xl-rules.xml file, then you must restart the XL Deploy server for the changes to take effect. For xl-rules.xml, you can change the default behavior as described in Define a rule.

Unclean shutdown

If the server is not shut down cleanly, the next start-up may be slow because XL Deploy will need to rebuild indexes.

Lock files left by unclean shutdown

If the server is not shut down cleanly, the following lock files may be left on the server:

  • XL_DEPLOY_SERVER_HOME/repository/.lock (ensure that XL Deploy is not running before removing this file)
  • XL_DEPLOY_SERVER_HOME/repository/index/write.lock
  • XL_DEPLOY_SERVER_HOME/repository/workspaces/default/write.lock
  • XL_DEPLOY_SERVER_HOME/repository/workspaces/security/write.lock (server start-up will be slower after this file is removed because the indexes must be rebuilt)
  • XL_DEPLOY_SERVER_HOME/repository/version/db/db.lck
  • XL_DEPLOY_SERVER_HOME/repository/version/db/dbex.lck
  • XL_DEPLOY_SERVER_HOME/repository/workspaces/default/db/db.lck
  • XL_DEPLOY_SERVER_HOME/repository/workspaces/default/db/dbex.lck
  • XL_DEPLOY_SERVER_HOME/repository/workspaces/security/db/db.lck
  • XL_DEPLOY_SERVER_HOME/repository/workspaces/security/db/dbex.lck