What's New in Application Server Administration for the SAS 9.2 Intelligence Platform

The SAS Intelligence Platform: Application Server Administration Guide explains how to administer a SAS Application Server.

This document contains new material about the following enhancements and changes to the SAS Intelligence Platform:

• server-based pooling mechanism

• change to OBJECTSERVERPARMS system option

• new configuration tools

• security enhancements

• load-balancing changes

• grid algorithm for load balancing

• new SAS logging facility

• automated SAS server tier configuration

• port changes

The SAS Pooled Workspace Server is a new SAS server type that exploits server-based pooling.

You no longer need to specify the OBJECTSERVERPARMS option, METAAUTOINIT, because it is on by default in SAS 9.2. (You can turn this option off by using the NOMETAUTOINIT option.)

These are the new SAS configuration tools:

• SAS Deployment Wizard that is used to add new software and configurations

• SAS Deployment Manager that is used to remove configurations

SAS contains these security changes:

• server access security in which the SAS Metadata Server verifies that a user has permission to use a server before the server grants the user access, enabling SAS to know the actual identity of the client user

• Integrated Windows Authentication (IWA) for single sign-on functionality for Windows desktop users

• fewer operating system accounts are required to run SAS 9.2

• internal accounts that SAS uses by default for some of the required user accounts (such as sastrust and sasadm)

SAS contains these changes to server load balancing:

• The stored process server and new pooled workspace server have load balancing enabled by default.

• The object spawner uses its operator connection for load balancing out-of-the-box. Administrators no longer have to create a separate load-balancing connection.

SAS has a new load-balancing algorithm that supports Workspace servers running in a grid.

SAS has a new logging facility controlled by the LOGCONFIGLOC system option. The traditional SAS log option LOGPARM= is ignored. The traditional SAS log option LOG= is recognized only when the %S{App.Log} conversion character is specified in the logging configuration file. For more information, see The SAS Logging Facility in SAS Logging: Configuration and Programming Reference.

SAS has eliminated most post-install manual configuration scripts for the SAS server tier initial configuration through its new deployment tool, the SAS Deployment Wizard.

The following SAS default ports have changed:

• The object spawner's managed ports can now share the same port.

• The new SAS Pooled Workspace Server uses port 8701.

• The new SAS Object Spawner port banks use ports 8801, 8811, and 8821.

• The object spawner load balancing port, 8571, is no longer used.

The SAS Intelligence Platform: Application Server Administration Guide has been reorganized to reflect the new SAS features.

Copyright © 2008 by SAS Institute Inc., Cary, NC, USA. All rights reserved.