Running Servers as Windows Services

On Windows systems, depending on the options that were selected during the installation process, the following might be installed as services: the SAS/CONNECT spawner, the SAS Metadata Server, the SAS object spawner, the SAS OLAP Server, the SAS Services Application (Remote Services), the SAS Framework Data Server, and the SAS/SHARE server. This installation option is highly recommended. If these servers have been installed as services, then they start automatically when you restart the machines. To ensure that services are always started in the correct order, the required dependencies are built into the services.

The JBoss Application Server and the SAS Deployment Tester server might also be installed as a services. These services are set up to be started manually.

SAS provides scripts for installing the Oracle WebLogic Managed Server and WebLogic Administration Server as Windows services. You can install these services by following instructions that are provided in the Instructions.html file, which is located in SAS-configuration-directory/Levn/Documents. After you install the services, they will start up automatically when you restart the machine.

For each service, the following table shows the built-in dependencies and the actions that you can take from within Windows Services Manager:

Service Dependencies and Actions

Server	Dependencies	Available Net Commands
SAS Metadata Server	None	Start, stop, pause, and continue
SAS OLAP Server	Metadata server	Start, stop, pause, and continue
SAS object spawner	Metadata server	Start, stop, pause, and continue
SAS Services Application (Remote Services)	Metadata server	Start and stop
SAS Framework Data Server	None	Start, stop, pause, and continue
SAS/CONNECT spawner	Metadata server	Start and stop
SAS/SHARE server	Metadata server	Start and stop
SAS Deployment Tester server	None	Start and stop
JBoss Application Server	SAS Services Application (Remote Services)	Start and stop
Oracle WebLogic Administration Server	None	Start and stop
Oracle WebLogic Managed Server	Oracle WebLogic Administration Server	Start and stop

The service names have the following format:

SAS [deployment-name-and-level] <server-context -> server-name

For example, your services might be displayed in Windows Services Manager as follows:

SAS [Config-Lev1] Object Spawner
SAS [Config-Lev1] Remote Services
SAS [Config-Lev1] SASApp - OLAP Server
SAS [Config-Lev1] SASMeta - Metadata Server
SAS [Config-Lev1] FrameworkServer - SAS Framework Data Server

If you installed the JBoss Application Server as a service, the service is displayed as JBoss - SASServer1. If you installed the WebLogic Administration Server and WebLogic Managed Server as services, the service names consist of the domain name, the server name, and the configuration directory path, as in the following examples:

SASDomain
                  AdminServer (sas.Config.Lev1)

and

SASDomain
                  SASServer1 (sas.Config.Lev1)

SAS provides batch scripts that you can use to manage these services from the command line. You can also use the Windows Net command, which has the following syntax:

net start|stop|pause|continue
                  "

service-name"

For example, if the service name for the object spawner is

SAS [Config-Lev1]
                  Object Spawner

You would use the following command to stop the service:

net stop "SAS [Config-Lev1] Object Spawner"
You would use the following command to start the service:

net start "SAS [Config-Lev1] Object Spawner"