SAND CDBMS Administration Guide
The SAND Enterprise Service

 

Previous Topic:
The SAND Enterprise Agent (SEA)
Chapter Index
Next Topic:
Administering the SAND Enterprise Service (part 2)

 

Administering the SAND Enterprise Service


Starting the Service

UNIX

By default the SAND Enterprise Service (SES) is started as a Daemon process when the system starts. At installation time, entries are put into the /sbin/rc[0,2,3].d directories to make the Service start automatically at Run Level 3.

If the SES process was stopped or did not start, use the following command to start the SES Daemon manually (executable by ROOT only):

/sbin/init.d/nesd start

When the SAND Enterprise Service is started, it does the following:


Windows

By default, the SAND Enterprise Service (SES) is started as a Windows Service when the system starts. If the SES process was stopped or did not start, use the Windows Service Control window to start the service:

Errors and other messages returned during startup are written to the Windows event log.

When the SAND Enterprise Service is started, it does the following:


Stopping the Service

When the service is stopped, any running database instances are stopped by killing the nserv engines that are running them (note that in Real Mode, this may cause problems with the database). Errors and other messages are written to the NE Service event log, or to the event log under Windows.

On a UNIX platform, use the following command to stop the SES Daemon (executable by ROOT only):

/sbin/init.d/nesd stop


On a Windows server, use the Windows Service Control window to stop the SAND Enterprise Service:

 

Previous Topic:
The SAND Enterprise Agent (SEA)
Chapter Index
Next Topic:
Administering the SAND Enterprise Service (part 2)