Converting SAS/IntrNet Programs to SAS Stored Processes

Compatibility Features

The following features describe similarities between Application Dispatcher and stored processes:

The SAS Stored Process Web Application (a component of the SAS Web Infrastructure Platform) provides the middle-tier equivalent of the Application Broker. The SAS Stored Process Web Application requires a servlet container host such as JBoss, BEA WebLogic, or IBM WebSphere. For other requirements, see the SAS Web Infrastructure Platform installation instructions.
The SAS Stored Process Server (a component of SAS Integration Technologies) provides the equivalent of the SAS/IntrNet Application Server. The typical stored process server configuration (a load-balanced cluster) is very similar in functionality to a SAS/IntrNet pool service. New servers are started as demand increases to provide a highly scalable system.
Streaming output from a stored process is written to the _WEBOUT fileref. The underlying access method has changed, but the functionality is very similar to the functionality of SAS/IntrNet. ODS, HTML Formatting Tools, DATA step code, or SCL programs can continue to write output to _WEBOUT.
The Application Server functions (APPSRVSET, APPSSRVGETC, APPSRVGETN, APPSRV_HEADER, APPSRV_SESSION, and APPSRV_UNSAFE) are supported in stored processes except as noted in the "Conversion Considerations" section. In many cases, equivalent STPSRV functions are recommended for new programs.
The _REPLAY mechanism is supported by the stored process server. The value of the _REPLAY URL has changed, but this does not affect most programs.
The SAS/IntrNet sessions feature has been implemented by the stored process server. The same SAVE library, session macro variables, and session lifetime management functions are available in stored processes.

Top of Page