• support.sas.com

• Knowledge Base

• Support

• Training & Bookstore

• Community

Hot Topics

• Migration for Metadata-Based Deployments
  The SAS Migration Utility is featured in SAS 9.3 Intelligence Platform: Migration Guide
  
  
• Calculators
  • Compatibility Calculator
  • PROC MIGRATE Calculator
• Papers
  • Peaceful Coexistence: Multiple SAS Releases
  • Migration Planning Worksheet
• SAS Notes
  • Data Migration and Compatibility
  • Migration for Metadata-Based Deployments

Related Links

• Install Center
• Section 508 Accessibility
• Expanded Table of Contents
• Contact Us

Software

Migration

SAS/IntrNet Software

In SAS 9.3, the SAS/IntrNet Configuration Utility has been replaced by the SAS/IntrNet Service Tasks in the SAS Deployment Manager. The Create a New IntrNet Service utility on Windows and the inetcfg.pl script on UNIX are no longer available.

The SAS/IntrNet documentation provides requirements and setup for upgrading to the latest release. See the What's New topics for changes and enhancements in SAS®9.

See also information about compatibility in SAS software, in Base SAS syntax, and in SAS files.

See also Converting SAS/IntrNet Programs to Stored Processes.

Peaceful Coexistence of Multiple Versions of SAS/IntrNet

You can run multiple versions of SAS/IntrNet on the same computer. Take care with the following issues.

• Application Servers and other components must be configured so that TCP/IP ports do not overlap.
  
  
• Each service is tied to a specific release. Name your services based on the application or applications they support and not the version of SAS. For example, naming your services "default8" and "default9" will make it difficult or confusing when you want to move an application to the next release. All references to the service name will need to be changed or the service name will be misleading.
  
  
• It is generally recommended that the latest available release of SAS®9 Application Broker and Load Manager be used to control both SAS 8.2 and SAS®9 servers. This allows the standard URLs to be used to access and manage both sets of servers. A single broker.cfg file can contain both SAS 8.2 and SAS®9 server definitions. It is possible to install both SAS 8.2 and SAS®9 versions of the CGI Tools, but they must be installed to different locations on the Web server.
  
  
• The SAS/GRAPH components installed in the /sasweb/graph are not compatible across SAS releases. If you use the JAVA driver in your SAS/IntrNet applications and need to support multiple releases, you must install the needed releases of SAS/GRAPH components on your Web server. Use the ServiceSet directive in your broker.cfg to define _GRAFLOC as appropriate for each service. Verify that your applications use &GRAFLOC (and not the fixed value /sasweb/graph) as the codebase for JAVA graphics.
  
  
• SAS/IntrNet 9 Application Dispatcher samples may not be fully compatible with a SAS 8.2 Application Server. If you want to use the samples, verify that the "default" service is a SAS/IntrNet 9 service; otherwise, you must modify all of the sample HTML files to use a SAS/IntrNet 9 service.