Starting and Stopping Express Server Using the Command Line

You must restart Express Server any time you update a spatial index or generate an overview (see Updating a Spatial Index Using the Command Line and Updating an Overview Using the Command Line).

For information on restarting the JPIP server, see Starting and Stopping the JPIP Server Using the Computer Management Dialog or Command Line.

Windows Systems

On Windows, Express Server runs as a collection of services. To start or stop Express Server, you must start or stop the following services:

• The World Wide Web Publishing service (IIS)
• The LizardTech Express Server Admin Backend service
• The LizardTech Express Server Tomcat service

To stop the services from the command line, enter the following commands:

C:\> net stop w3svc

C:\> net stop esadminagent

C:\> net stop lttomcat8

To start the services from the command line, enter the following commands:

C:\> net start w3svc

C:\> net start esadminagent

C:\> net start lttomcat8

Linux Systems

On Linux, Express Server runs as a daemon process. At installation time, startup scripts are copied into the standard System V install script location, /etc/init.d, and are set to start and stop at run level 3.

The Apache Web Server communicates with the Express Server process over a local network connection. Thus starting and stopping Express Server is a two-step job, involving both Express Server and Apache.

To start Express Server from the command line, run the following commands:

$ /etc/init.d/ltcsd start

$ /etc/init.d/lttomd start

$ /etc/init.d/ltagentd start

$ <path-to-apache>/bin/apachectl start

To stop Express Server from the command line, run the following commands:

$ /etc/init.d/ltcsd stop

$ /etc/init.d/lttomd stop

$ /etc/init.d/ltagentd stop

$ <path-to-apache>/bin/apachectl stop