Overview of Server Operation :: SAS(R) 9.3 Intelligence Platform: System Administration Guide, Second Edition

About Required Servers

In order for clients to access the SAS Intelligence Platform, the following components must be running on network-accessible machines:

a SAS Metadata Server
the SAS object spawner, which acts as a listener for SAS Workspace Servers, SAS Pooled Workspace Servers, and SAS Stored Process Servers

Depending on which SAS products you have installed, one or more instances of the following additional components might also be required to be running on network-accessible machines: SAS OLAP Server, SAS Framework Data Server, SAS Services Application (also referred to as Remote Services), SAS/CONNECT spawner, SAS/SHARE server, SAS Content Server, and a Web application server.

If you want to use the SAS Deployment Tester utility, then the SAS Deployment Tester server must also be running.

Starting Servers in the Correct Order

Because of dependencies, it is important to start the servers in the correct order. Server dependencies are shown in the following table:

Server Dependencies

Server	Server Dependencies
SAS Metadata Server	None
SAS OLAP Server	SAS Metadata Server
SAS object spawner	SAS Metadata Server
SAS Framework Data Server	None
SAS Services Application (Remote Services)	SAS Metadata Server
Web application server	SAS Services Application (Remote Services)
SAS/CONNECT spawner	SAS Metadata server
SAS/SHARE server	SAS Metadata server
SAS Deployment Tester server	None

The following is an example of a start-up order that meets the dependency requirements:

Start the SAS Metadata Server.
Start the SAS OLAP Server.
Start the SAS object spawner.
Start the SAS/SHARE server
Start the SAS/CONNECT spawner.
Start the SAS Framework Data Server.
Start the SAS Services Application (Remote Services).
Start the SAS Deployment Tester server (optional).
Start the Web application server. (The SAS Content Server starts automatically when the application server is started.)

Servers should be stopped in the inverse order, with the metadata server stopped last.

About Server Start-up Parameters

The start-up parameters for SAS servers are stored in configuration files. For a list of these configuration files and their locations, see Reference: Configuration Files for SAS Servers.

For detailed information about start-up parameters for each server, see the documentation references in the table in Summary of Procedures for Server Operation.

Summary of Procedures for Server Operation

To operate servers in SAS Management Console, you must have the appropriate user credentials. To determine what credentials are required for each task, see Who Can Do What: Credential Requirements for SAS Management Console Tasks.

The following table summarizes the server operation methods for each server. For detailed information about start-up parameters for each server, see the documentation references that are provided in the last column.

Summary of Server Operation Procedures

Server Type	Available Methods for Server Operation	Documentation Location for Start-up Parameters
SAS Metadata Server, SAS OLAP Server, and SAS object spawner	Windows service1 z/OS started task2 sas.servers script 3 (UNIX or z/OS) Individual server script (or Windows shortcut) SAS Management Console (except start-up)	Options for the Metadata Server Invocation Command Overview of System Options for SAS Application Server Components in SAS Intelligence Platform: Application Server Administration Guide Spawner Invocation Options in SAS Intelligence Platform: Application Server Administration Guide
SAS Workspace Server, SAS Pooled Workspace Server, and SAS Stored Process Server	Started by the object spawner SAS Management Console (except start-up)	Overview of System Options for SAS Application Server Components in SAS Intelligence Platform: Application Server Administration Guide
SAS Framework Data Server	Windows service 1 z/OS started task 2 sas.servers script3 (UNIX or z/OS) Individual server script (or Windows shortcut) SAS Management Console (except start-up)
SAS Services Application (Remote Services)	Windows service 1 z/OS started task 2 sas.servers script3 (UNIX orz/OS) Remote Services script (or Windows shortcut)	SAS Intelligence Platform: Middle-Tier Administration Guide
Web application server	Server console or script Windows service (JBoss and Oracle WebLogic only)1	SAS Intelligence Platform: Middle-Tier Administration Guide
SAS Content Server	Starts automatically when the Web application server is started	SAS Intelligence Platform: Middle-Tier Administration Guide
SAS/CONNECT spawner, SAS/SHARE server, and SAS Deployment Tester server	Windows service 1 z/OS started task 2 sas.servers script 3 (UNIX orz/OS) Individual server script (or Windows shortcut)	Communications Access Methods for SAS/CONNECT and SAS/SHARE SAS/SHARE User's Guide
1 On Windows systems, this is the recommended method.
2 On z/OS systems, this is the recommended method.
3 On UNIX systems, this is the recommended method.

Refer to the following topics for information about operating servers and services: