SAS 9.1.3 Intelligence Platform: System Administration Guide

8 Overview of SAS Application Server Components and Their Initial Configuration R Chapter 2
3 The metadata server has been configured to write daily logs to the directory
SAS-config-dir\Lev1\SASMain\MetadataServer\logs. By default, the following
information is written to the log:
3 SAS Metadata Server start and stop information, including the invoking user
ID, SAS long version number, SAS Metadata Model version, the directory
where the metadata server was started, and configuration file options
3 user connection and disconnection events
3 repository creation, deletion, open, close, pause, resume, and refresh events
3 errors, including task/thread exceptions, memory allocation errors, I/O errors,
application logic errors, authentication errors, and authorization failures
3 The metadata server has been configured to authenticate users with the host
operating system’s authentication mechanism.
3 The metadata server has been configured to use SAS proprietary encryption to
encrypt user credentials that are sent over the network.
For information about changing this configuration, see the following sections:
3 “Modifying Your Initial Configuration to Optimize Performance” on page 23
3 “Making Other Changes to Your Initial Configuration” on page 24
Overview of SAS Application Server Components and Their Initial
Configuration
During the installation process, the SAS Configuration Wizard created metadata
definitions and configuration files for a set of SAS servers that are referred to
collectively as a SAS Application Server. The name of the SAS Application Server is
assigned as follows:
3 The name SASMain is assigned on machines that have a SAS Metadata Server in
addition to the SAS Application Server.
3 The name SASApp is assigned on machines that do not have a SAS Metadata
Server installed.
An application server can contain several types of components. The most common
components are SAS Workspace Servers and SAS Stored Process Servers. An
application server can also contain SAS/CONNECT servers, SAS OLAP Servers, and
SAS batch servers. By default, these application server components are configured as
follows:
3 The initial workspace server has the following configuration:
3 The workspace server is configured as a standard workspace server (without
workspace pooling or load balancing). With this configuration, each client
must establish a connection to a single-user server process, use the server,
and then disconnect.
3 Workspace server logging is disabled.
3 The initial stored process server has the following configuration:
3 The stored process server is configured to be load balanced. By default, the
object spawner balances a workload across three stored process server
processes.
3 Logging for stored process servers is enabled by default.
3 By default, only minimal logging is enabled for the SAS/CONNECT spawner.