High-Level SAS Migration Requirements

Migrating, using the SAS automated migration tools, requires the following:
specific versions of SAS.
The SAS automated migration tools support migration for the following versions of SAS:
  • SAS 9.1.3 to SAS 9.3.
    For SAS 9.1.3, the baseline SAS maintenance level must be SP4 and Xythos must be at 4.0.48 or later.
    Note: For SAS 9.1.3 z/OS systems, before you migrate, make sure that you have applied the hot fix described in this SAS Note: http://tsdsrv05.unx.sas.com:7777/docs/sasnotes/fusion/30/981.html
  • SAS 9.2 to SAS 9.3.
  • SAS 9.3 to SAS 9.3.
    For more information about the use cases for SAS 9.3 to SAS 9.3 migration, see About Using the SAS Migration Utility to Copy an Existing Deployment in SAS Intelligence Platform: System Administration Guide.
  • SAS 9.1.3 to SAS 9.2.
    For more information, see the SAS Intelligence Platform: 9.1.3 to 9.2 Migration Guide.
For additional information about specific SAS offerings, refer to http://support.sas.com/migration/utilitynotes.
Later in this document, you will be instructed to create a migration analysis report for each tier of your SAS deployment. One purpose of this report is to help you identify those SAS components that must be upgraded before you can migrate to SAS 9.3. For more information, see Inventorying Your Current SAS Deployment.
full system migration all at the same time.
All your content and configuration from your earlier SAS version is migrated to SAS 9.3 at the same time.
the same topology.
Your SAS architecture must continue to be distributed across logical machines in the same fashion. Because a logical machine corresponds to a single SAS configuration directory, this directory can be relocated to a different physical machine during migration.
Redistributing logical machines on different physical machines increases the level of complexity for your migration. Common issues involve port conflicts and physical files residing outside of the configuration directory tree. Understand this complexity and plan for it when designing your migration.
Note: You can add new SAS 9.3 products during a migration. Make sure the new product components are contained in your SAS order and deployment plan file.
certain changes to the middle tier.
  • The SAS middle tier is supported only on 64-bit operating systems.
  • The SAS Deployment Wizard will change the Web application server vendor to the one selected in your SAS 9.3 deployment plan.
  • Apache Tomcat is replaced with JBoss Application Server.
  • Xythos and Apache HTTP WebDAV servers are replaced with SAS Content Server.
  • When you migrate to SAS 9.3, the SAS Migration Utility enables you to change database vendors. For more information, see Database type for SAS Web Infrastructure Platform.
the same operating system family.
Your SAS 9.3 components must run on the same operating system family as they did in your earlier SAS version.
You can migrate within the Windows family (for example, Windows 32-bit to Windows 64-bit) or migrate within the UNIX family (for example, Solaris to HP-UX).
The SAS Migration Utility uses the CPORT and CIMPORT procedures to change file formats when migrating within operating system families. For more information, see MIGRATE Procedure in Base SAS Procedures Guide, CPORT Procedure in Base SAS Procedures Guide, and CIMPORT Procedure in Base SAS Procedures Guide.
For more information about post-migration tasks when migrating from one version of an operating system to another, see Overview of Performing Post-migration Tasks.
Note: On UNIX, SAS 9.3 should be installed on a file system that supports large files (files that are greater than 2GB in size).