28.12.2012 Views

SAS 9.3 Web Applications: Clustering - Index of - SAS

SAS 9.3 Web Applications: Clustering - Index of - SAS

SAS 9.3 Web Applications: Clustering - Index of - SAS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

What’s New in <strong>SAS</strong> <strong>Web</strong> <strong>Applications</strong><br />

<strong>Clustering</strong><br />

Overview<br />

Whatʼs New<br />

This document applies to the first maintenance release for <strong>SAS</strong> <strong>9.3</strong>.<br />

<strong>SAS</strong> Middle Tier Supported on 64-Bit<br />

Systems Only<br />

The <strong>SAS</strong> <strong>9.3</strong> middle-tier s<strong>of</strong>tware is supported on 64-bit operating systems only.<br />

<strong>SAS</strong> Workflow Modifications<br />

<strong>SAS</strong> Workflow requires manual reconfiguration in order to be deployed in a cluster. If<br />

your site does not require high-availability and scalability for <strong>SAS</strong> Workflow, you can<br />

choose to deploy it to a stand-alone server instance to avoid the reconfiguration task.<br />

Cookie Management for IBM <strong>Web</strong>Sphere<br />

Application Server<br />

In previous releases <strong>of</strong> this document, one <strong>of</strong> the configuration tasks for IBM<br />

<strong>Web</strong>Sphere Application Server was to override the default cookie name for the<br />

servers in the cluster. In this release, the strategy is reversed. The cookie name for<br />

the stand-alone server instance is changed, and the default cookie name is used for<br />

the servers in the cluster. This change is in response to sites that lost session affinity<br />

with <strong>SAS</strong> Information Delivery Portal, <strong>SAS</strong> BI Portlets, and <strong>SAS</strong> JSR 168 Remote<br />

Portlets <strong>Web</strong> applications.<br />

v

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!