Previous Page | Next Page

Before You Begin

Introduction to This Guide

This guide covers the administration of the SAS Application Server, which is a logical entity that represents the SAS server tier in the SAS Intelligence Platform. This application server contains a set of actual servers. For example, a SAS Application Server usually contains the following servers:

Workspace Server

enables client applications to submit SAS code to a SAS session by using an application programming interface (API). For example, when you use SAS Data Integration Studio to submit an extract, transform, and load (ETL) job for processing, the application generates the SAS code necessary to perform the processing and submits it to a workspace server. You can run as many instances of workspace servers as are needed to support your workload.

Pooled Workspace Server

enables client applications to submit SAS code to a SAS session by using an application programming interface (API). Pooled workspace servers are workspace servers in every respect except that these servers automatically use pooling and load balancing.

Stored Process Server

interacts with SAS by submitting stored processes, which are SAS programs that are stored and can be executed by client applications. You can use stored processes to perform complex tasks such as analyzing data and creating reports, and then return the results to the client or publish the results to a channel or repository.

OLAP server

delivers pre-summarized, multidimensional data (cubes) to business intelligence applications. The data is queried using the multidimensional expressions language (MDX).

In addition, a SAS Application Server might contain one of more of the following servers:

SAS/CONNECT Server

enables clients to execute code on a remote host, or to move data between client and server machines.

SAS batch server

stores information in metadata about how to execute a SAS command in batch mode. A batch server is a required if you are using the SAS scheduling system. There are three batch servers:

  • DATA Step Batch Server

  • Java Batch Server

  • Generic Batch Server

SAS Grid Server

enables Platform LSF to start SAS/CONNECT servers on a SAS compute grid in order to execute grid-enabled SAS programs or grid-enabled jobs that are created in SAS Data Integration Studio and SAS Enterprise Miner.

This guide explains how to administer all of these server components and the SAS Application Server as a whole.

The guide consolidates information that was previously located in the SAS Intelligence Platform: Administration Guide, the SAS Integration Technologies: Server Administrator's Guide, and the SAS OLAP Server: Administrator's Guide. It also contains information describing SAS 9.2 functionality.

This guide assumes that you are familiar with the concepts and terminology that are introduced in the SAS Intelligence Platform: Overview document. For a list of all of the documents that SAS publishes to support administration of the SAS Intelligence Platform, see http://support.sas.com/92administration.

Previous Page | Next Page | Top of Page