SAS servers

Overview of SAS Servers

Note: In the SAS Intelligence Platform, the term “server” refers to a program or

programs that wait for and fulfill requests from client programs for data or services.

The term server does not necessarily refer to a specific computer, since a single

computer can host one or more servers of various types.

• the SAS Metadata Server, which writes metadata objects to, and reads metadata

objects from, SAS Metadata Repositories. These metadata objects contain

information about all of the components of your system, such as users, groups, data

libraries, servers, and user-created products such as reports, cubes, and information

maps.

• SAS Workspace Servers, which provide access to SAS software features such as the

SAS language, SAS libraries, the server file system, results content, and formatting

services.

• A program called the SAS object spawner runs on a workspace server's host

machine. The spawner listens for incoming client requests and launches server

instances as needed.

• SAS Pooled Workspace Servers, which are configured to use server-side pooling. In

this configuration, the SAS object spawner maintains a collection of workspace

server processes that are available for clients. This server configuration is intended

for use by query and reporting tools such as SAS Information Map Studio, SAS Web

Report Studio, and the SAS Information Delivery Portal.

• SAS Stored Process Servers, which fulfill client requests to execute SAS Stored

Processes. Stored processes are SAS programs that are stored on a server and can be

executed as required by requesting applications. By default, three load balanced SAS

Stored Process Servers are configured.

The SAS object spawner runs on a stored process server's host machine, listens for

incoming client requests, and launches server instances as needed.

• SAS OLAP Servers, which provide access to cubes. Cubes are logical sets of data

that are organized and structured in a hierarchical multidimensional arrangement.

Cubes are queried by using the multidimensional expression (MDX) language.

• the SAS Framework Data Server, which is the default location for middle-tier data

such as alerts, comments, and workflows, as well as data for the SAS Content Server

and SAS Service Parts Optimization. The server is provided as an alternative to

using a third-party DBMS. (The server cannot be used as a general-purpose data

store.)

• SAS/CONNECT servers, which provide computing resources on remote machines

where SAS Integration Technologies is not installed.

• batch servers, which enable you to execute code in batch mode. There are three types

of batch servers: DATA step batch servers, Java batch servers, and generic batch

servers. The DATA step server enables you to run SAS DATA steps and procedures

in batch mode. The Java server enables you to schedule the execution of Java code,

such as the code that creates a SAS Marketing Automation marketing campaign. The

generic server supports the execution of any other type of code.

• the SAS Content Server, which is part of the middle tier architecture. This server

stores digital content (such as documents, reports, and images) that is created and

used by SAS Web applications.