Guide to Software Updates
Guide to Software Updates
4 Guide to
®
Software Updates
SAS® Documentation
The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2013. SAS® 9.4 Guide to Software
Updates. Cary, NC: SAS Institute Inc.
SAS® 9.4 Guide to Software Updates
Copyright © 2013, SAS Institute Inc., Cary, NC, USA
Audience
This document is for existing SAS customers who are upgrading an existing SAS 9.4
deployment. The initial release of SAS 9.4 TS1M0, Rev. 940_13w26 was in July 2013.
The purpose of this document is to notify customers about changes that they might see
in SAS 9.4 and how those changes might affect their site. Specific information about
migrating your metadata and SAS content is available in the SAS Intelligence Platform:
Migration Guide.
This document is organized into the following parts:
n “Planning for a Software Update” helps you assess whether your site is ready for a
software upgrade.
Here is some of the information that you want to review as you plan to update the
software at your site:
o what products you currently have installed at your site
o how future software updates might impact your site
o what functionality has been deprecated or will be deprecated in the future
o new requirements for operating systems and third-party software
n “Installing SAS 9.4” provides links to the resources that you can use to install SAS
9.4.
n “Product Details and Requirements” can include the following types of information
for each product that runs on SAS 9.4:
o any steps that you might need to perform before you upgrade to a new release
xx Using This Book
o any software changes that might result in different behavior from a previous
release
xxi
Whatʼs New
What’s New in SAS 9.4 Guide to
Software Updates
Overview
SAS 9.4 Guide to Software Updates is cumulative and is updated whenever there is an
update of a SAS product. The following topics will help you determine what changes
were made after the initial release of SAS 9.4, which shipped in July 2013.
n SAS Model Risk Management 7.1. For more information, see Chapter 72, “SAS
Model Risk Management,” on page 345.
n SAS Risk Management for Banking 3.4. For more information, see Chapter 79, “SAS
Risk Management for Banking,” on page 367.
The third maintenance release for SAS Social Network Analysis Server is now
available. For more information, see Chapter 81, “SAS Social Network Analysis Server,”
on page 375.
n SAS Forecast Analyst Workbench 5.3. For more information, see Chapter 47, “SAS
Forecast Analyst Workbench,” on page 233.
n SAS Fraud Management 4.3. For more information, see Chapter 49, “SAS Fraud
Management,” on page 241.
n SAS Inventory Optimization Workbench 5.3. For more information, see Chapter 61,
“SAS Inventory Optimization Workbench,” on page 307.
n the first maintenance release for SAS Customer Due Diligence 6.3. For more
information, see Chapter 25, “SAS Customer Due Diligence,” on page 149.
n the second maintenance release for SAS Social Network Analysis Server 6.2. For
more information, see Chapter 81, “SAS Social Network Analysis Server,” on page
375.
n SAS Environment Manager 2.5. For more information, see Chapter 41, “SAS
Environment Manager,” on page 211.
n SAS/ETS 14.1. For more information, see Chapter 43, “SAS/ETS,” on page 221.
n SAS Forecast Server 14.1. For more information, see Chapter 48, “SAS Forecast
Server,” on page 237.
n SAS Fraud Management 4.2. For more information, see Chapter 49, “SAS Fraud
Management,” on page 241.
n SAS/IML 14.1. For more information, see Chapter 54, “SAS/IML,” on page 259.
n SAS Model Manager 14.1. For more information, see Chapter 71, “SAS Model
Manager,” on page 339.
n SAS/OR 14.1. For more information, see Chapter 75, “SAS/OR,” on page 353.
n SAS/QC 14.1. For more information, see Chapter 76, “SAS/QC,” on page 357.
n SAS/STAT 14.1. For more information, see Chapter 82, “SAS/STAT,” on page 377.
n SAS Studio 3.4. For more information, see Chapter 83, “SAS Studio,” on page 381.
n SAS Text Miner 14.1. For more information, see Chapter 85, “SAS Text Miner,” on
page 389.
These products were updated as part of the third maintenance release for SAS 9.4:
n Base SAS. For more information, see Chapter 13, “Base SAS,” on page 91.
n SAS/ACCESS software. For more information, see Chapter 14, “SAS/ACCESS,” on
page 107.
n SAS/CONNECT. For more information, see Chapter 22, “SAS/CONNECT,” on page
139.
n SAS Data Quality Server. For more information, see Chapter 31, “SAS Data Quality
Server,” on page 177.
n SAS In-Database Technologies. For more information, see Chapter 56, “SAS In-
Database Technologies,” on page 269.
xxviii What’s New in SAS 9.4 Guide to Software Updates
n SAS/GRAPH. For more information, see Chapter 50, “SAS/GRAPH,” on page 243.
n SAS Grid Manager. For more information, see Chapter 51, “SAS Grid Manager,” on
page 247.
n SAS Integration Technologies. For more information, see Chapter 58, “SAS
Integration Technologies,” on page 281.
n SAS Intelligence Platform. For more information, see Chapter 59, “SAS Intelligence
Platform,” on page 287.
n SAS/IntrNet. For more information, see Chapter 60, “SAS/IntrNet,” on page 303.
n SAS Management Console. For more information, see Chapter 64, “SAS
Management Console,” on page 317.
n SAS OLAP Server. For more information, see Chapter 73, “SAS OLAP Server,” on
page 347.
n SAS/SECURE. For more information, see Chapter 80, “SAS/SECURE,” on page
369.
n SAS Marketing Operations Management 6.4. For more information, see Chapter 66,
“SAS Marketing Operations Management,” on page 325.
n SAS Risk Dimensions 6.4. For more information, see Chapter 78, “SAS Risk
Dimensions,” on page 365.
n SAS Risk Management for Banking 3.3.For more information, see Chapter 79, “SAS
Risk Management for Banking,” on page 367.
n SAS Visual Analytics 7.2. For more information, see “SAS Visual Analytics 7.2” on
page 407.
n SAS Digital Marketing 6.4. For more information, see Chapter 35, “SAS Digital
Marketing,” on page 187.
n SAS Marketing Automation 6.4. For more information, see Chapter 65, “SAS
Marketing Automation,” on page 321.
n SAS Marketing Optimization 6.4. For more information, see Chapter 67, “SAS
Marketing Optimization,” on page 327.
n SAS MDM 4.2. For more information, see Chapter 68, “SAS MDM (Master Data
Management),” on page 331.
n SAS Real-Time Decision Manager 6.4. For more information, see Chapter 77, “SAS
Real-Time Decision Manager,” on page 361.
n SAS Task Manager 2.2. For more information, see Chapter 84, “SAS Task Manager,”
on page 387.
n SAS Visual Process Orchestration 2.2. For more information, see Chapter 87, “SAS
Visual Process Orchestration,” on page 411.
Several SAS solutions or products are now shipped with SAS Visual Analytics
components. For some of these solutions, you can delay the deployment of the SAS
Visual Analytics components. To address this issue, the documentation now includes an
“Adding SAS Visual Analytics to Your Deployment” on page 88 topic.
SAS Social Network Analysis Server 6.2 shipped its first maintenance release. For more
information, see Chapter 81, “SAS Social Network Analysis Server,” on page 375.
xxxii What’s New in SAS 9.4 Guide to Software Updates
SAS Web Parts 6.1 for Microsoft SharePoint shipped a second maintenance release
(6.12). For more information, see Chapter 89, “SAS Web Parts for Microsoft
SharePoint,” on page 415.
n Base SAS 9.4_M2. For more information, see Chapter 13, “Base SAS,” on page
91.
n SAS/ACCESS 9.4_M2 Interface to Hadoop, SAS/ACCESS 9.4_M2 Interface to
Oracle, SAS/ACCESS 9.4_M2 Interface to PC Files. For more information, see
Chapter 14, “SAS/ACCESS,” on page 107.
n SAS/CONNECT 9.4_M2. For more information, see Chapter 22, “SAS/CONNECT,”
on page 139.
n SAS 9.4_M2 In-Database Technologies. For more information, see Chapter 56,
“SAS In-Database Technologies,” on page 269.
n SAS 9.4_M2 Integration Technologies. For more information, see Chapter 58, “SAS
Integration Technologies,” on page 281.
n SAS 9.4_M2 Intelligence Platform. For more information, see Chapter 59, “SAS
Intelligence Platform,” on page 287.
n SAS/IntrNet 9.4_M2. For more information, see Chapter 60, “SAS/IntrNet,” on page
303.
n SAS Management Console 9.4_M2. For more information, see Chapter 64, “SAS
Management Console,” on page 317.
n SAS OLAP Server 9.4_M2. For more information, see Chapter 73, “SAS OLAP
Server,” on page 347.
n SAS/SECURE 9.4_M2. For more information, see Chapter 80, “SAS/SECURE,” on
page 369.
n SAS Web Report Studio 4.4_M2. For more information, see Chapter 90, “SAS Web
Report Studio,” on page 419.
The first maintenance release for SAS High-Performance Risk 3.1 is available. For
more information, see Chapter 53, “SAS High-Performance Risk,” on page 255.
n SAS Federation Server 4.1. For more information, see Chapter 28, “SAS and
DataFlux,” on page 157.
n SAS Merchandise Intelligence 5.2, which includes these products:
o SAS Revenue Optimization 5.2, which includes SAS Markdown Optimization,
SAS Regular Price Optimization, and SAS Promotion Optimization
o SAS Size Optimization 3.2, which includes SAS Size Profiling and SAS Pack
Optimization
o SAS Retail Forecasting 5.2
For more information, see Chapter 69, “SAS Merchandise Intelligence,” on page
333.
The first maintenance release of SAS Studio 3.1 is now available. For more information,
see Chapter 83, “SAS Studio,” on page 381.
The documentation is enhanced to include this information:
n Several SAS Data Surveyor products are no longer supported. For more information,
see “Deprecated Functionality in SAS 9.4” on page 30.
n The Deployment and Backup Recovery tool enables you to specify a central,
network-accessible vault location. For more information, see “Deployment Backup”
on page 293.
SAS Visual Analytics 6.4 is a new product release.For more information, see Chapter
86, “SAS Visual Analytics,” on page 395.
n SAS Text Miner 13.1. For more information, see Chapter 84, “SAS Task Manager,”
on page 387.
n SAS Visual Analytics 6.3. For more information, see Chapter 86, “SAS Visual
Analytics,” on page 395.
n SAS Web Parts 6.11 for Microsoft SharePoint. For more information, see Chapter
89, “SAS Web Parts for Microsoft SharePoint,” on page 415.
These products are updated as part of the first maintenance release for SAS 9.4.
n Chapter 14, “SAS/ACCESS,” on page 107
n Chapter 22, “SAS/CONNECT,” on page 139
n Chapter 50, “SAS/GRAPH,” on page 243
n Chapter 56, “SAS In-Database Technologies,” on page 269
n Chapter 58, “SAS Integration Technologies,” on page 281
n Chapter 59, “SAS Intelligence Platform,” on page 287
n Chapter 73, “SAS OLAP Server,” on page 347
The DataFlux chapter has been updated to reflect that SAS has now fully integrated the
DataFlux suite of data quality, data integration, data governance, and master data
management solutions. For more information, see Chapter 28, “SAS and DataFlux,” on
page 157.
Part 1
Introduction to Updating SAS Software at Your
Site
Chapter 1
Understanding the Process for Software Updates . . . . . . . . . . . . . 3
2
3
1
Understanding the Process for
Software Updates
Software update is a general term for any modification that is provided by the vendor for
existing software.
n Upgrades, also known as “new releases,” introduce new functionality and have a
new release number.
n Maintenance releases are applied to the installed software at your site. A
maintenance release is a collection of updates to SAS products or components that
corrects customer-reported issues and adapts a product to a changed environment.
A maintenance release can also include new software functionality.
4 Chapter 1 / Understanding the Process for Software Updates
Maintenance releases are cumulative. For example, the third maintenance release
contains all of the new features and enhancements for the first, second, and third
maintenance releases. If you choose not to install a maintenance release, you
automatically receive all of the content in that maintenance release when you next
upgrade your version of SAS or SAS product. For example, if you decide not to
install the second maintenance release, when you install the third maintenance
release or a SAS product that runs on the third maintenance release, you get the
software updates from the second and third maintenance releases.
There are two types of maintenance releases:
o SAS maintenance release is a maintenance release for SAS Foundation. This
type of maintenance release includes software changes for multiple SAS
products, such as Base SAS and SAS/GRAPH.
o product-specific maintenance release is a maintenance release for a specific
product, such as the first maintenance release for SAS Forecast Server. This
type of maintenance release includes software changes for a single SAS product.
n Hot fixes are as-needed updates that are generally included in each maintenance
release, but hot fixes can also be made available after the maintenance release has
shipped. To verify that you have the latest hot fixes for the products at your site, see
Technical Support Hot Fixes.
n Because of the dependencies between SAS products, you cannot perform these
tasks:
o You cannot partially install a maintenance release or update a single product.
The SAS deployment tools determine which SAS products to update. You must
upgrade all of the SAS software in a specific deployment whether that
deployment is on one machine or multiple machines.
o You cannot uninstall a maintenance release.
n Maintenance releases are cumulative. For example, the third maintenance release
contains all of the new features and enhancements from the first, second, and third
maintenance releases.
n Maintenance releases update the SAS software that is currently deployed at your
site.
n Before installing a maintenance release, back up your current SAS deployment.
Note: In general, SAS maintenance releases do not include any updates to JMP
products. For more information, see JMP Software Updates. Beginning with SAS 9.3,
the JMP Clinical, JMP Genomics, and SAS Visual Data Discovery (for the desktop)
products are installed and maintained with SAS installers. These products no longer use
a separate JMP installer.
1 Learn about the availability of new product releases or maintenance releases from
your SAS account representative, from the SAS website, or from this document.
6 Chapter 1 / Understanding the Process for Software Updates
2 Run a deployment registry report to determine what products you currently have
installed at your site. For more information, see “How to Run the Deployment
Registry Report” on page 14.
After running the deployment registry report, you know the release numbers for the
products at your site. Compare these release numbers to the release numbers of the
products in this document. A difference in release numbers helps you identify what
products at your site have updates.
By reviewing the product-specific information in this document, you can determine
how upgrading your software could affect your site. For example, you learn about
any new features that are available and how those features might affect your
existing SAS content. You also learn any post-configuration steps that you need to
complete before you start using the product.
5 Review your software order. After you request a maintenance release, a product
upgrade, or a new SAS product, you receive a Software Order E-mail (SOE), which
lists the product bundle that you ordered and the software revision number (for
example, SAS 9.4, Rev. 940_13w26).
6 Prepare your site for the software updates. These preparations include downloading
the order to a SAS 9.4 Software Depot, creating backups, determining how long the
upgrade takes, and notifying users about the scheduled update. You also perform
any pre-installation steps for the products at your site. You determined these pre-
installation steps when you assessed the impact of the software update at your site.
7 Install and configure any software updates. When you run the SAS Deployment
Wizard, SAS automatically detects any files on your system that are older than the
files in your order. If there are software updates to be installed for products already
in your deployment, the SAS Deployment Wizard goes into Update mode. If no
The General Process for Software Updates 7
software updates need to be installed, the SAS Deployment Wizard does not go into
Update mode, and you can exit the SAS Deployment Wizard.
Depending on your order, you might have new products to add to your deployment.
Adding these products might require that you run the SAS Deployment Wizard a
second time. For more information, see “Adding a New Product” on page 75.
8 Complete any post-configuration steps for the products at your site. You determine
these post-configuration steps when you assess the impact of the software update at
your site. To determine the post-configuration steps, see the “Product Details and
Requirements” section.
8 Chapter 1 / Understanding the Process for Software Updates
9
Part 2
Planning for a Software Update
Chapter 2
Determining the Product Release Numbers
for Products at Your Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 3
Reviewing Current and Future Software Updates . . . . . . . . . . . . . 17
Chapter 4
Updating Operating Environments and Third-
Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
10
11
2
Determining the Product Release
Numbers for Products at Your Site
To determine the Technical Support level for the SAS release that you are running at
your site:
1 Start SAS.
12 Chapter 2 / Determining the Product Release Numbers for Products at Your Site
2 In Windows and UNIX environments, review the information at the top of the log
when SAS starts.
To view this information in the SAS Display Manager, select Help About SAS 9.
Note: If you are working in a z/OS environment, look for the 9.4 (TS1Mx) string in
the output.
The following table shows examples of some product release numbers for products that
shipped in SAS 9.4:
SAS/GRAPH 9.4_M1
As this table shows, all products currently have a maintenance release number of M1.
Suppose Base SAS shipped a second maintenance release. Then the maintenance
release number for Base SAS would be M2. Then, the maintenance release numbers
are different because there have been two maintenance releases for Base SAS.
14 Chapter 2 / Determining the Product Release Numbers for Products at Your Site
If the other products in the table are not updated in the second maintenance release for
SAS 9.4, their maintenance release number stays M1.
For more information about product numbers, see SAS Provides New Product-Specific
Release Numbers.
Note: The deployment registry report lists all of the installed products. However, these
products might not be configured at your site.
For example, if your deployment includes an installation of SAS Visual Analytics
Designer, the deployment registry report could include the following entry:
Host: lax
Understanding the Contents of the Deployment Registry Report 15
The Display Version field shows that SAS Visual Analytics Designer 7.2 is installed at
your site.
16 Chapter 2 / Determining the Product Release Numbers for Products at Your Site
17
3
Reviewing Current and Future
Software Updates
For help with determining when to place a software order, contact your SAS account
representative.
n how plans to deprecate functionality could affect your site. For more information, see
“Deprecated Functionality in SAS 9.4” on page 30.
You can also use the Software Order E-mail or Software Order Information to determine
the revision number for the software in your order. For more information, see Chapter 8,
“Reviewing Your Software Order,” on page 53.
Note: The table is not a comprehensive list of all the products that shipped at a specific
time. For more information about a specific product, contact your SAS account
representative.
Current Product Releases 19
July 2013 (SAS 9.4, Rev. 940_13w30) SAS Decision Manager 2.1
SAS 9.4 In-Database Products
September 2013 (SAS 9.4, Rev. 940_13w36) SAS Data Quality Accelerator for Teradata
2.4
Current Product Releases 21
October 2013 (SAS 9.4, Rev. 940_13w40) DataFlux Authentication Server 3.2
DataFlux Data Management Server 2.5
DataFlux Data Management Studio 2.5
DataFlux Secure 2.5
SAS Contextual Analysis 12.3
SAS Data Management Console
SAS Data Quality Accelerator for Teradata
2.4
SAS Data Remediation 2.1
SAS Job Monitor 2.1
SAS MDM 4.1
SAS Visual Process Orchestration 2.1
November 2013 (SAS 9.4, Rev. 940_13w45) SAS Anti-Money Laundering 6.1
SAS Customer Due Diligence 6.1
SAS Peer Group Analysis 6.1
SAS Quality Knowledge Base for Contact
Information 22
22 Chapter 3 / Reviewing Current and Future Software Updates
March 2014 (SAS 9.4, Rev. 940_14w11) SAS Strategy Management 5.6
SAS Studio 3.1
SAS Visual Analytics 6.4
Current Product Releases 23
April 2014 (SAS 9.4, Rev. 940_14w14) SAS Anti-Money Laundering 6.2
SAS Data Quality Accelerator 2.5 for
Teradata
SAS Data Remediation 2.1_M1
SAS MDM 4.1_M1
SAS Task Manager 2.1_M1
May 2014 (SAS 9.4, Rev. 940_14w19) SAS Decision Services 6.3
June 2014 (SAS 9.4, Rev. 940_14w23) SAS Fraud Management 4.1
SAS High-Performance Risk
SAS Quality Knowledge Base for Contact
Information 23
24 Chapter 3 / Reviewing Current and Future Software Updates
September 2014 (SAS 9.4, Rev. 940_14w36) SAS IT Resource Management 3.5
Current Product Releases 25
October 2014 (SAS 9.4, Rev. 940_14w41) SAS Add-In 7.1 for Microsoft Office
SAS Enterprise GRC 6.1
SAS Enterprise Guide 7.1
SAS Environment Manager 2.4
SAS Visual Analytics 7.1
SAS Web Parts 6.12 for Microsoft SharePoint
November 2014 (SAS 9.4, Rev. 940_14w47) DataFlux Data Management Studio 2.6
DataFlux Web Studio 2.5
SAS Business Data Network 3.1
SAS High-Performance Risk 3.3
SAS Lineage 3.1
January 2015 (SAS 9.4, Rev. 940_15w04) SAS Anti-Money Laundering 6.3
SAS Customer Due Diligence 6.3
SAS Enterprise Case Management 6.3
SAS Financial Management 5.5
SAS Social Network Analysis Server 6.1
SAS Visual Scenario Designer 6.3
February 2015 (SAS, Rev. 940_15w08) SAS Asset Performance Analytics 6.1
SAS Customer Link Analytics 5.6
SAS Episode Analytics 2.2
SAS Studio 3.3
March 2015 (SAS 9.4, Rev. 940_15w12) SAS Data Remediation 2.2
SAS Digital Marketing 6.4
SAS Marketing Automation 6.4
SAS Marketing Optimization 6.4
SAS MDM 4.2
SAS Real-Time Decision Manager 6.4
SAS Task Manager 2.2
SAS Visual Process Orchestration 2.2
26 Chapter 3 / Reviewing Current and Future Software Updates
May 2015 (SAS 9.4, Rev. 940_15w20) SAS Add-In 7.11 for Microsoft Office
SAS Credit Scoring for Banking 5.4
SAS Enterprise Guide 7.11
SAS Event Stream Processing 3.1
SAS Forecast Analyst Workbench 5.2_M2
SAS Fraud Management 4.2
SAS High-Performance Risk 3.4
SAS Inventory Optimization 5.2_M2
SAS IT Resource Management 3.6
SAS Marketing Operations Management 6.4
SAS OpRisk VaR 6.1
SAS Risk Dimensions 6.4
Current Product Releases 27
August 2015 (SAS 9.4, Rev. 940_15w33) SAS Merchandise Intelligence 5.4
SAS Visual Analytics 7.3
28 Chapter 3 / Reviewing Current and Future Software Updates
October 2015 (SAS 9.4, Rev. 940_15w42) SAS Anti-Money Laundering 6.3_M1
SAS Customer Due Diligence 6.3_M1
SAS Enterprise Case Management 6.3_M1
SAS High-Performance Risk 3.5
SAS Risk Dimensions 6.5
SAS Social Network Analysis Server 6.2_M2
November 2015 (SAS 9.4, Rev. 940_15w47) SAS Contextual Analysis 14.1_M1
SAS Event Stream Processing 3.2
SAS Fraud Management 4.2_M1
January 2016 (SAS 9.4, Rev. 940_16w04) DataFlux Authentication Server 4.1
DataFlux Data Management Server 2.7
DataFlux Secure 2.7
SAS Anti-Money Laundering 6.3
SAS Customer Due Diligence 6.3
February 2016 (SAS 9.4, Rev. 940_16w08) SAS Add-In 7.12 for Microsoft Office
SAS Enterprise Guide 7.12
SAS Episode Analytics 3.1
SAS IT Resource Management 3.7
SAS Studio 3.5
March 2016 (SAS 9.4, Rev. 940_16w13) SAS Micro Analytic Services 1.3
April 2016 (SAS 9.4, Rev. 940_16w17) SAS Firmwide Risk for Solvency II 3.2
SAS High-Performance Risk 3.6
SAS Risk Dimensions 6.6
May 2016 (SAS 9.4, Rev. 940_16w22) SAS Forecast Analyst Workbench 5.3
SAS Fraud Management 4.3
SAS Inventory Optimization Workbench 5.3
Current Product Releases 29
June 2016 (SAS 9.4, Rev. 940_16w26) SAS Customer Intelligence 6.5
SAS Customer Link Analytics 6.5
SAS Decision Services 6.5
SAS Digital Marketing 6.5
SAS Marketing Automation 6.5
SAS Marketing Optimization 6.5
SAS Real-Time Decision Manager 6.5
SAS Social Network Analysis Server 6.2_M3
July 2016 (SAS 9.4, Rev. 940_16w30) SAS Anti-Money Laundering 7.1
SAS Model Risk Management 7.1
SAS Risk Management for Banking 3.4
August 2016 (SAS 9.4, Rev. 940_16w33) SAS Event Stream Processing 4.1
4
Updating Operating Environments and
Third-Party Software
versions of third-party software. SAS 9.4 delivers some software components that are
based on commercially available third-party software. For example, SAS Web
Application Server is based on VMware tc Server, and SAS Web Server is based on
VMware vFabric Web Server. When you apply upgrades and patches, do not upgrade
or patch any software components that are delivered with SAS. SAS maintains this
third-party software, so you are always running the correct version.
For more information, see Chapter 59, “SAS Intelligence Platform,” on page 287.
SAS also delivers the Java 7 JRE software as part of a SAS 9.4 deployment. This
software is the baseline for SAS products that run on SAS 9.4. SAS also delivers
updates for the JRE. These updates can be applied without updating other SAS
software. For more information, see SAS Third-Party Software Requirements - Java 7
Updates and Security Bulletins from SAS.
33
Part 3
Preparing Your Site for a Software Update
Chapter 5
Assessing the Effect on Products at Your Site . . . . . . . . . . . . . . . . 35
Chapter 6
Using Backups and Restoring Customizations . . . . . . . . . . . . . . . 39
Chapter 7
Undeploying SAS Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
34
35
5
Assessing the Effect on Products at
Your Site
Note: If no product updates are required for a machine, then you will not see a list of
product updates, and your installation of the product upgrade or maintenance release is
complete on that machine.
1 Run the SAS Deployment Wizard from the software depot that contains your SAS
9.4 installation.
Note: In a Windows environment, you must be an administrator to run the SAS
Deployment Wizard, but you do not have to use the same user ID that you used to
36 Chapter 5 / Assessing the Effect on Products at Your Site
install SAS 9.4. In UNIX environments, you must use the same user ID that you
used to install SAS 9.4. For both operating environments, the SDW_yyyy-mm-dd-
hh.mm.ss.log file lists the ID for the current user.
From the highest-level directory in your SAS Software Depot, start the SAS
Deployment Wizard by using the command for your operating environment.
Table 5.1 How to Start the SAS Deployment Wizard
TIP Starting in the second maintenance release for SAS 9.4, a recorded
response file is created automatically, so you do not need to specify the -record
option.
2 In the Review Required Updates step, click Print to print the list of required updates
for the current machine. (Alternatively, you can copy and paste this content into
another document, such as an e-mail.) Review the list of products in the Update
Summary section.
Note: If no product updates are required, then the list of required updates does not
appear, and you can exit the SAS Deployment Wizard.
Review the List of Products at Your Site 37
3 Because you are not installing any software at this time, click Cancel to exit the SAS
Deployment Wizard.
After reviewing the contents of the list of required updates and assessing the effect
on products at your site, you can install these product updates by restarting the SAS
Deployment Wizard.
Note: When you exit the SAS Deployment Wizard, the list of product updates is not
saved. When you install the software, a Deployment Summary for the installation
(which contains this list of product updates) is saved to the SAS-installation-
directory/InstallMisc/InstallLogs directory.
38 Chapter 5 / Assessing the Effect on Products at Your Site
Reviewing these product topics now will enable you to perform the following tasks:
n prepare for any feature changes that will affect your site
n identify any pre-installation or post-configuration steps that need to be performed for
the products that you have installed at your site
n plan for additional time to complete any product-specific steps for each updated
product
If no topic is listed for a product, then no product-specific steps are required for that
product.
39
6
Using Backups and Restoring
Customizations
Effect on Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Customizations to EAR and WAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Customizations to _usermods Configuration Files . . . . . . . . . . . . . . . . . 45
Record the Value of the Scheduling Services
Cache Locator Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Record Any Additional Customizations at Your Site . . . . . . . . . . . . . . . 46
Note: For more information, see “Undeploying the SAS Web Applications” on page
49.
The specific size increase depends on how SAS is deployed at your site.
Some of this increase in disk space is temporary because you can remove some files
after applying a maintenance release. For more information, see “General Information
about Creating and Removing Backup Files” on page 40.
CAUTION! When restoring backups that were created with operating system
commands or third-party tools, you must preserve the original datetime stamps
on the files.
You should also create a backup of your SAS content. Use the Deployment Backup and
Recovery tool to back up these components:
n the metadata server, including all registered metadata repositories, the repository
manager, and the server’s configuration directory
n the SAS Content Server repository
Understanding the Deployment Backup and Recovery Tool 41
n the databases that are managed by the SAS Web Infrastructure Platform Data
Server
n additional directories under SAS-configuration-directory/Levn as specified
by the administrator
The Deployment Backup and Recovery tool should be configured on the main machine
for the middle tier. For more information about this tool, see SAS Intelligence Platform:
System Administration Guide.
CAUTION! You cannot combine orders from different SAS releases (for example,
SAS 9.3 and SAS 9.4) in the same software depot. When you initially install SAS 9.4,
you are required to create a new software depot.
If you need more disk space, after the maintenance release has been installed, use the
SAS Update File Cleanup Utility to remove the backups that SAS created in the
SASHome directory. This utility must be run under the user ID that was used to install
SAS. For more information about this utility, see SAS Deployment Wizard and SAS
Deployment Manager 9.4: User’s Guide.
Additional backup folders are created for the web application server. For example, a
backup folder might be in the SAS-configuration-directory/Levn/Web/
WebAppServer directory. This backup folder can be quite large. The entire contents of
the SAS-configuration-directory/Levn/Web/WebAppServer directory are
moved to this backup directory before the software upgrade. A timestamp is appended
to the backup directory (for example, SASServer1_1.2015-06-16-15.57.35). Consult this
folder if you need to reapply any customizations after updating your software. After the
customizations have been reapplied and validated, you can delete these backup
directories.
42 Chapter 6 / Using Backups and Restoring Customizations
1 Unconfigure the Deployment Backup and Recovery tool on the main machine for the
middle tier.
3 Configure the Deployment Backup and Recovery tool only on the main machine for
the middle tier.
4 Follow the instructions for upgrading your software. For more information, see
“Install and Configure a Software Update” on page 69.
On the other machines where the Deployment Backup and Recovery tool is deployed,
complete these steps:
a Follow the instructions for upgrading your software. For more information, see
“Install and Configure a Software Update” on page 69. Complete the install
directory update.
b In the SASHome-directory/SASDeploymentManager/9.4/
product_data/svrbakupevm__94110_cd388__prt__ xx__sp0__1/
configure/svrbakupevm_default.properties files, change all of the
configuration script targets to false. (Setting these targets to false ensures
that none of these targets are run on this machine.)
n the WAR files in the configuration directory for the SAS server. For example,
delete SAS-configuration-directory/Levn/Web/WebAppServer/
SASServer_n/sas_webapps/sas.svcs.admin.backup.war.
n SAS-configuration-directory/Levn/Web/WebAppServer/
SASServer_n/conf/Catalina/localhost/
SASDeploymentBackup.xml.
n SAS-configuration-directory/Levn/Web/WebAppServer/
SASServer_n/sas_webapps/sas.svcs.admin.backup.war.
2 After you update your software on all hosts, open the sas.conf file. Verify that the
URL in the ProxyPass entry for SASDeploymentBackup contains the host name
of the main machine for the middle tier.
1 Verify that the URL in the ProxyPass entry for SASDeploymentBackup contains
the host name of the main machine for the middle tier.
Effect on Customizations
Therefore, customizations that you made to the applications after initial deployment can
be lost if you do not make a copy of the changed files. Here are some common
customizations:
n configuring web authentication
n configuring a custom HTTP time-out value
n creating custom content such as a portlet for the SAS Information Delivery Portal
n creating custom themes
Effect on Customizations 45
Before updating your software, record the current port value. In UNIX and Windows
environments, this port value is in the SAS-configuration-directory/Levn/Web/
gemfire/instances directory. For example, if the port number is 41448, you should
see this directory: SAS-configuration-directory/Levn/Web/gemfire/
instances/Ins_41448.
7
Undeploying SAS Web Applications
For more installation and configuration information, see SAS 9.4 Support for Web
Application Servers and HTTP Servers.
48 Chapter 7 / Undeploying SAS Web Applications
When you update the software at your site, SAS automatically performs these tasks:
n rebuilds all SAS web applications
n redeploys all SAS web applications
n restarts your web application servers
Before updating your software, you might want to undeploy the SAS web applications if
the update includes a new or renamed web application and the existing web application
is no longer supported. If you undeploy the SAS web applications, you need to do so
only on the tier where the software is being updated. If the SAS Deployment Wizard
does not go into Update mode, then no software updates are required, and you do not
need to undeploy your SAS web applications on that tier.
For more information, see these topics in the SAS Intelligence Platform: Middle-Tier
Administration Guide
n “Reverting Manual HTTPS Changes to SAS Web Server” in SAS Intelligence
Platform: Middle-Tier Administration Guide
n “Reverting Manual HTTPS Changes to SAS Web Server” in SAS Intelligence
Platform: Middle-Tier Administration Guide
When you undeploy your SAS web applications, a backup directory is created for each
instance of the SAS Web Application Server. Your existing WAR files are saved in this
backup directory.
When you upgrade your software and the SAS web applications are redeployed, a new
set of WAR files is delivered. Before updating the middle tier, verify that you have
enough disk space for the backups and the new WAR files. A good estimate is
approximately double the current disk space for your existing SAS web applications.
50 Chapter 7 / Undeploying SAS Web Applications
After your users successfully log on to the web applications and verify that everything is
working properly, you can delete these backup files.
Part 4
Installing Your Software Order
Chapter 8
Reviewing Your Software Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 9
Understanding the SAS Software Depot . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 10
Understanding the SAS Installation Files . . . . . . . . . . . . . . . . . . . . . . . 61
Chapter 11
Installing SAS 9.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
52
53
8
Reviewing Your Software Order
What Is in My Order? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
What Is in My Order?
When determining what products will be updated at your site, it is often useful to review
the list of products in your software order. SAS provides two resources that you can use
to determine what is in your order and when your order was placed.
n Software Order Email (SOE)
n SAS Order Information (SOI)
Here is an example of the information that you might see in the SAS Order Information
file.
9
Understanding the SAS Software
Depot
Note: When you install SAS 9.4, you are required to create a new software depot. You
cannot combine SAS 9.3 and SAS 9.4 orders in the same software depot. However, all
maintenance releases and software upgrades in the SAS 9.4 lifecycle can be added to
an existing SAS 9.4 Software Depot.
For more information about the SAS Software Depot, see these resources:
n “Creating SAS Software Depots” in SAS Intelligence Platform: Installation and
Configuration Guide
58 Chapter 9 / Understanding the SAS Software Depot
n SAS Installation Note 39379: Documentation and Frequently Asked Questions for
the SAS Software Depot
n SAS Note 38236: Validating SAS Software Depots on Windows Using the SAS
Software Depot Checker
To see what products will be installed and configured, review the plan.xml file before
you start the SAS Deployment Wizard. To view a diagram of your customized
deployment plan, see details_diagram.html (optimized for Firefox) or
details_diagram_for_ie7.mht (optimized for Internet Explorer) files that came with your
custom plan file.
In the SAS Deployment Wizard, compare the contents of your plan file with the items in
your SAS Software Depot. In the Specify Deployment Plan step, you can see the
structure of the selected plan file. Items that are in bold, black font are either not in your
order or are not supported on this platform. If software is missing from your order,
contact your SAS account representative.
Comparing Your Plan File to the Contents of Your Depot 59
TIP Standard deployment plans are available in your SAS Software Depot and 9.4
Standard Deployment Plans. If you need to create a custom deployment plan, copy
your plan.xml file to the plan_files directory in your SAS Software Depot. By
default, the plan files in this directory are displayed in the Specify the full path to a
customized deployment plan field.
After you complete your installation, a copy of the plan file that you used is saved in the
SAS-configuration-directory/Levn/Utilities directory. An example of this
directory path on Windows is C:\SAS\Config\Lev1\Utilities
\plan.date_time.xml.
60 Chapter 9 / Understanding the SAS Software Depot
61
10
Understanding the SAS Installation
Files
Instructions.html and
UpdateInstructions.html Files
After you install SAS for the first time, configure a new product, or reconfigure an
existing product, you must complete the manual steps in the Instructions.html file to
complete your deployment. The latest version of the Instructions.html file is available
from a link in the last step of the SAS Deployment Wizard and in the SAS-
configuration-directory/Levn/Documents/ directory. When you open the
Instructions.html file, you see a document titled “Configuration Guidelines and Details
for your-machine-name.” This document contains the validation steps for the last
deployment that you performed. Previous versions of the Instructions.html file are
available from the SAS-configuration-directory/Levn/Documents/Backup
directory. You might need to refer to a previous Instructions.html file to re-validate your
deployment.
After you install a maintenance release or upgrade to a new product release, you could
see an UpdateInstructions.html file, which contains the configuration steps that you
must manually complete. The UpdateInstructions.html file could contain a subset of
steps from the original Instructions.html file, or it could contain new steps that you must
complete because you are applying a maintenance release or upgrading to a new
product. The latest version of the UpdateInstructions.html file is available from the SAS-
configuration-directory/Levn/Documents directory. Previous versions of the
UpdateInstructions.html file are available from the SAS-configuration-
directory/InstallMisc/InstallLogs directory.
Note: If you need to re-validate your deployment after a software update, use the
Instructions.html file from your initial deployment.
The Deployment Summary for the Installation 63
Note: A Deployment Summary for each previous installation is saved in the home
directory of the user ID that was used to install SAS. The Deployment Summary for the
latest installation of the maintenance release is always available from SAS-
installation-directory/InstallMisc/InstallLogs.
For each product in the Update Summary, there are two columns of release numbers:
n The Installed column lists the product release number that was on your machine
before you applied the maintenance release or product upgrade.
n The Updated column lists the product release number that is on your machine after
you applied the maintenance release or product upgrade.
For each product in the Deployment Summary, review the information in “Product
Details and Requirements” to determine the post-configuration steps that are necessary
for your site. If you do not complete these post-configuration steps, you might
experience unexpected behavior or errors that will affect the use of your SAS software.
Installation Section
The Installation section lists whether each product update installed successfully. In the
following example, all products installed successfully, so you can complete any post-
configuration steps for these products.
However, if a product installation failed or completed with errors (such as the SAS Add-
In for Microsoft Office in the following example), review the audit files for that product.
The Deployment Summary for the Installation 65
Note: The installation of the SAS Add-In for Microsoft Office might fail if Microsoft Office
is not on the machine or if a Microsoft Office product is open.
66 Chapter 10 / Understanding the SAS Installation Files
67
11
Installing SAS 9.4
If you are installing SAS 9.4 for the first time, see these resources to determine the
steps for installing and configuring SAS 9.4 at your site:
n QuickStart Guides at http://support.sas.com/documentation/installcenter/94
n SAS Intelligence Platform: Installation and Configuration Guide
b Use the pg_dumpall command to create a backup of the WIP Data Server.
Here is an example of the pg_dumpall command:
pg_dumpall -c -h localhost -U dbmsowner -p 9432 -f location/db.out
C:\SAS-installation-directory\SASWebInfrastructurePlatformDataServer\
9.4\bin\pg_dumpall —c —h localhost -U dbmsowner -p 9432
-f location\db.out
For more information about backups, see SAS Intelligence Platform: System
Administration Guide.
1 Stop all LASR Analytic Servers by using the SAS Visual Analytics Administrator. For
more information, see SAS Visual Analytics: Administration Guide
2 Terminate all active SAS sessions, daemons, spawners, and servers, except for the
SAS Deployment Agent running on each of your servers. It is important to stop the
SAS servers in the inverse order that they were started. For more information, see
“Overview of Server Operation” in SAS Intelligence Platform: System Administration
Guide.
Note: In AIX operating environments, after you stop all the servers and processes,
you must clear the AIX file cache to avoid any locked files when you apply the
maintenance release. To clear this cache, run the /usr/sbin/slibclean
command by using the root user ID.
3 Verify that all machines where you are installing the software update are installed
with SAS 9.4 software.
70 Chapter 11 / Installing SAS 9.4
4 For each machine in your deployment, start the SAS Deployment Wizard from the
highest-level directory in your SAS Software Depot. You can start the SAS
Deployment Wizard in the following ways:
Table 11.1 How to Start the SAS Deployment Wizard
Operating
System How to Start the SAS Deployment Wizard
UNIX Execute setup.sh from the highest-level directory in your SAS Software
Depot.
z/OS For basic deployments, type setup.rexx to run the SAS Deployment
Wizard.
For planned deployments:
n The first invocation of the SAS Deployment Wizard is to install the
metadata server as a 64-bit application: setup.rexx –z64
n The second invocation of the SAS Deployment Wizard is to install the
remainder of your SAS 9.4 order as a 31-bit application: setup.rexx
To use a temporary directory other than /tmp, specify –templocation
new-temp-dir.
Note: If you install SAS using the -nojobsubmit option, the process
for applying a software update differs from the process that is described in
this document. For more information, see Documentation for a SAS 9.4
installation in z/OS operating environment at support.sas.com.
Install and Configure a Software Update 71
5 Select your order and the location of the SASHome directory. The SAS Deployment
Wizard goes into Update mode and installs any product updates on that machine.
Note: If a machine does not require any product updates, the SAS Deployment
Wizard does not go into Update mode and the installation of the maintenance
release on that machine is complete. Click Cancel to exit the SAS Deployment
Wizard.
6 After the deployment is complete, click Next in the SAS Deployment Wizard.
Note: If you have a basic deployment, your software update is complete, and you
can ignore the remaining steps. If you have a planned deployment, continue with
step 6.
7 Add or verify your CA or site-signed certificates. The process for adding certificates
depends on the maintenance release of SAS 9.4. SAS recommends upgrading to
the latest release of SAS 9.4 as soon as possible.
n Starting in the third maintenance release for SAS 9.4, a default CA certificate
bundle is shipped with SAS. You add additional certificates by using the SAS
Deployment Manager. For more information, see “Working with CA Certificates
for TLS and HTTPS Security” on page 101.
72 Chapter 11 / Installing SAS 9.4
n If you are upgrading to the first or second maintenance release for SAS 9.4, you
must re-import your site certificate into the SAS private JRE default truststore
(the cacerts file).
Importing a certificate into a keystore is accomplished with the Java keytool —
importcert command. The location of the cacerts file in the SAS private JRE
is SAS-installation-directory/SASHome/
SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/security.
For example, on Windows, the command that you run is similar to this:
cd C:\Program Files\SASHome\SASPrivateJavaRuntimeEnvironment\9.4\jre\
lib\security ..\..\bin\keytool -importcert -keystore cacerts -file mycert.crt
Note: If you click Cancel, you have installed but not configured the software
updates. You must configure the updated SAS products before you can run them. To
complete these configuration steps at a later time, see “Configure SAS Products” in
SAS Intelligence Platform: Installation and Configuration Guide.
9 If necessary, restart the SAS Metadata Server. In Windows and UNIX environments,
the SAS Metadata Server restarts automatically.
n In Windows environments, the following message appears in the SAS
Deployment Manager if the SAS Metadata Server is not running: A SAS
Metadata Server is not currently running on the Port.
To continue the configuration steps, restart the SAS Metadata Server manually.
For more information, see “Using SAS Management Console to Operate SAS
Servers” in SAS Intelligence Platform: System Administration Guide.
n To restart the SAS Metadata Server manually in UNIX environments:
1 At a UNIX prompt, navigate to the directory where the SAS Metadata Server
is configured.
10 In the Specify Connection Information panel of the SAS Deployment Manager, enter
the user ID and password of an unrestricted administrative user (for example,
sasadm@saspw).
11 Use the SAS Deployment Manager to update the configuration of your environment.
The panels that appear depend on your deployment. You must complete each panel.
When prompted for passwords for database IDs, you must use the same passwords
that you used to install SAS 9.4.
Note: In the SAS Web Infrastructure Database JDBC Properties panel, the SAS
Deployment Manager prompts you for the password for the JDBC connection for the
Web Infrastructure Platform. You must specify the password for the JDBC
connection. For more information about how alternative databases are configured,
see “Configuring an Alternative Database for SAS Web Infrastructure Platform
Services” at http://support.sas.com/resources/thirdpartysupport/v94/appservers/
SharedServicesAlternativeDatabase.pdf.
74 Chapter 11 / Installing SAS 9.4
When you update your configuration, SAS automatically starts your SAS servers,
configures your web application servers, and rebuilds and redeploys your SAS web
applications.
When the configuration is complete, the Deployment Summary opens. You need this
information later to determine whether there are additional post-configuration steps
for any of your products.
Note: The Deployment Summary for the installation is automatically saved. If the
Deployment Summary does not open automatically or if you need it later, you can
open it from your SAS installation directory. For more information, see “The
Deployment Summary for the Installation” on page 63.
12 Complete any necessary configuration steps for your web application server.
In the Validate SAS Web Server and SAS Web Application Server Configuration
step, click Next to determine whether the SSL encryption was configured manually.
If you have manually configuration changes, an error message appears.
Any manual changes to the TLS configuration must be reverted to the original non-
TLS values before applying a maintenance release or upgrading any software.
These manual changes to the TLS configuration can be reapplied to the upgraded
system.
For more information, see these topics in the SAS Intelligence Platform: Middle-Tier
Administration Guide
n “Reverting Manual HTTPS Changes to SAS Web Server” in SAS Intelligence
Platform: Middle-Tier Administration Guide
n “Reverting Manual HTTPS Changes to SAS Web Application Server” in SAS
Intelligence Platform: Middle-Tier Administration Guide
13 Review the list of products in the Update Summary section of the Deployment
Summary. For each product that was updated, determine whether there are
additional configuration steps to complete.
15 To validate the changes to your web application servers and SAS web applications,
review the validation sections in your Instructions.html file.
To update your SAS license, complete the steps for your operating environment:
n Software License Renewal Instructions—SAS 9.4 for Microsoft Windows for x64
Planned Deployment
n Software License Renewal Instructions—SAS 9.4 for UNIX Environments Planned
Deployment
need to configure each tier. For more information, see “Adding SAS Products” in SAS
Intelligence Platform: Installation and Configuration Guide.
If you are adding a SAS solution to an existing SAS 9.4 deployment (or if you need to
renew your software license for a SAS solution), use the SAS Deployment Manager to
update the SID file in the metadata. Verify that the SID file you select is for the order
that contains the new products. You might need to click Browse to select the correct
SID file. For more information, see the “Software License Renewal Instructions” for your
operating environment.
n Software License Renewal Instructions—SAS 9.4 for Microsoft Windows for x64
Planned Deployment
n Software License Renewal Instructions—SAS 9.4 for UNIX Environments Planned
Deployment
The SAS Download Manager automatically downloads the necessary SAS hot fixes
required by the SAS products in your order. However, these hot fixes are not
automatically applied by the SAS Deployment Wizard during the update of your existing
SAS environment.
Note: You can force the SAS Download Manager to skip downloading hot fixes when
downloading and creating your SAS Software Depot.
77
Part 5
Product Details and Requirements
Chapter 12
Introduction to Product Details and Requirements . . . . . . . . . . . 85
Chapter 13
Base SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 14
SAS/ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Chapter 15
SAS Add-In for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Chapter 16
SAS Anti-Money Laundering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
78
Chapter 17
SAS Asset Performance Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Chapter 18
SAS BI Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Chapter 19
SAS BI Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Chapter 20
SAS Business Data Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Chapter 21
SAS Business Rules Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Chapter 22
SAS/CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Chapter 23
SAS Contextual Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Chapter 24
SAS Credit Scoring for Banking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Chapter 25
SAS Customer Due Diligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Chapter 26
SAS Customer Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Chapter 27
SAS Customer Link Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Chapter 28
SAS and DataFlux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Chapter 29
SAS Data Integration Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
79
Chapter 30
SAS Data Quality Accelerator for Teradata . . . . . . . . . . . . . . . . . . . 173
Chapter 31
SAS Data Quality Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Chapter 32
SAS Data Remediation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Chapter 33
SAS Decision Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Chapter 34
SAS Decision Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Chapter 35
SAS Digital Marketing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Chapter 36
SAS Document Conversion Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Chapter 37
SAS Enterprise Case Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Chapter 38
SAS Enterprise GRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Chapter 39
SAS Enterprise Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Chapter 40
SAS Enterprise Miner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Chapter 41
SAS Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Chapter 42
SAS Episode Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
80
Chapter 43
SAS/ETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Chapter 44
SAS Event Stream Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Chapter 45
SAS Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Chapter 46
SAS Firmwide Risk for Solvency II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Chapter 47
SAS Forecast Analyst Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Chapter 48
SAS Forecast Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Chapter 49
SAS Fraud Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Chapter 50
SAS/GRAPH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Chapter 51
SAS Grid Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Chapter 52
SAS High-Performance Analytics Infrastructure . . . . . . . . . . . . 251
Chapter 53
SAS High-Performance Risk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Chapter 54
SAS/IML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Chapter 55
SAS Information Delivery Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
81
Chapter 56
SAS In-Database Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Chapter 57
SAS Information Map Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Chapter 58
SAS Integration Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Chapter 59
SAS Intelligence Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Chapter 60
SAS/IntrNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Chapter 61
SAS Inventory Optimization Workbench . . . . . . . . . . . . . . . . . . . . . . 307
Chapter 62
SAS IT Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Chapter 63
SAS Lineage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Chapter 64
SAS Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Chapter 65
SAS Marketing Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Chapter 66
SAS Marketing Operations Management . . . . . . . . . . . . . . . . . . . . . . 325
Chapter 67
SAS Marketing Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Chapter 68
SAS MDM (Master Data Management) . . . . . . . . . . . . . . . . . . . . . . . . . 331
82
Chapter 69
SAS Merchandise Intelligence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Chapter 70
SAS Micro Analytic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Chapter 71
SAS Model Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Chapter 72
SAS Model Risk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Chapter 73
SAS OLAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Chapter 74
SAS OpRisk VaR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Chapter 75
SAS/OR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Chapter 76
SAS/QC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Chapter 77
SAS Real-Time Decision Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Chapter 78
SAS Risk Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Chapter 79
SAS Risk Management for Banking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Chapter 80
SAS/SECURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Chapter 81
SAS Social Network Analysis Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
83
Chapter 82
SAS/STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Chapter 83
SAS Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Chapter 84
SAS Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Chapter 85
SAS Text Miner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Chapter 86
SAS Visual Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Chapter 87
SAS Visual Process Orchestration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Chapter 88
SAS Visual Scenario Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Chapter 89
SAS Web Parts for Microsoft SharePoint . . . . . . . . . . . . . . . . . . . . . 415
Chapter 90
SAS Web Report Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
84
85
12
Introduction to Product Details and
Requirements
However, some products require that you perform steps before upgrading to a new
release or perform post-configuration steps after installing the product. The “Product
Details and Requirements” section of this document contains information about product
changes and any pre-installation and post-configuration steps that you need to perform
for a specific SAS product. Each chapter begins with an upgrade path table. In the
table, find the row for your current release and the release that you are upgrading to.
The last column in that row contains the high-level steps that you must perform to install
and configure a SAS product. It is important that you review the documentation for all
86 Chapter 12 / Introduction to Product Details and Requirements
products at your site before updating the software at your site, so you can create a
complete installation and configuration checklist for your site.
Note: To determine the product release numbers for each machine in your SAS
deployment, generate a deployment registry report. For more information, see “How to
Run the Deployment Registry Report” on page 14.
Before you start the SAS Deployment Wizard, check the “Product Details and
Requirements” section of this document to determine whether any product pre-
installation or post-configuration steps are required.
If you are adding a SAS solution to an existing SAS 9.4 deployment (or if you need to
renew your software license for a SAS solution), use the SAS Deployment Manager to
update the SID file in the metadata. Verify that the SID file you select is for the order
that contains the new products. You might need to click Browse to select the correct
SID file. For more information, see the “Software License Renewal Instructions” for your
operating environment.
n Software License Renewal Instructions—SAS 9.4 for Microsoft Windows for x64
Planned Deployment
n Software License Renewal Instructions—SAS 9.4 for UNIX Environments Planned
Deployment
If your site meets the minimum system requirements and you want to add SAS Visual
Analytics components to your deployment now, complete these steps:
1 Work with your SAS account representative to add the SAS Visual Analytics
components to your plan.xml file.
2 After you have updated and saved the revised plan.xml file, follow the process for
applying software updates. For more information, see “Install and Configure a
Software Update” on page 69.
3 To add new products to your deployment, run the SAS Deployment Wizard a second
time. For more information, see “Adding a New Product” on page 87.
Adding SAS Visual Analytics to Your Deployment 89
If your site does not meet the minimum system requirements, you might decide to delay
the deployment of the SAS Visual Analytics components. However, you can still use the
SAS Deployment Wizard to apply any other software updates. For more information,
see “Install and Configure a Software Update” on page 69. You can also add any new
products. For more information, see “Adding a New Product” on page 87.
Note: If you delay the deployment of the SAS Visual Analytics components, you will not
be able to use SAS Mobile BI.
When you are ready to add the SAS Visual Analytics components to your deployment,
simply complete the previous steps. For more specific information, see the
administrator’s documentation for your SAS product or solution.
90 Chapter 12 / Introduction to Product Details and Requirements
91
13
Base SAS
9.4 9.4_M1, 9.4_M2, 1 Before you upgrade, see “Base SAS 9.4_M2”
9.4_M3 on page 100 and “Base SAS 9.4_M3” on
page 101 (if appropriate).
2 To upgrade to the latest release for SAS 9.4,
see “Install and Configure a Software Update”
on page 69.
9.4_M1 9.4_M2, 9.4_M3 1 Before you upgrade, see “Base SAS 9.4_M2”
on page 100 and “Base SAS 9.4_M3” on
page 101 (if appropriate).
2 To upgrade to the latest release for SAS 9.4,
see “Install and Configure a Software Update”
on page 69.
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “Base SAS 9.4” on
9.3_M2 9.4_M2, 9.4_M3 page 93, “Base SAS 9.4_M2” on page 100 ,
and “Base SAS 9.4_M3” on page 101 (if
appropriate).
2 Install and configure SAS 9.4.
n In UNIX environments, the default value of SORTSIZE has changed from 256M to
1G. The default value of MEMSIZE has changed from 512M to 2G.
You might need to verify that the systems at your site can handle this amount of
memory.
SAS Procedures
CONTENTS, COPY, MIGRATE, and SORT procedures
The International Components for Unicode (ICU) libraries, used by SAS for linguistic
collation, have been upgraded from version 4.2 to version 4.8.1. The new ICU
version uses locale data from version 2.0 of the Unicode Common Locale Data
Repository (CLDR), improves language support, and provides software fixes. For
more information, see http://site.icu-project.org/download/48 and http://
cldr.unicode.org/index/downloads/cldr-2-0.
A change in the ICU version that is used by SAS can affect the interpretation of
some data sets sorted by previous versions of SAS. For more information, see the
documentation for the SORT procedure, COPY procedure, and MIGRATE procedure
in Base SAS Procedures Guide.
The output from the CONTENTS procedure or the CONTENTS statement now
shows the ICU version number of a data set that is linguistically sorted.
FORMAT procedure
The range to specify a default length of an informat, picture, or format is 1–32767.
PRINT procedure
The PROC PRINT statement STYLE= option style attributes for the HEADER
location no longer affect the Obs column heading. You specify style attributes for the
Obs column heading by using the OBSHEADER location.
PRINTTO procedure
The PROC PRINTTO PRINT= statement opens the LISTING destination. You no
longer need to specify the ODS LISTING statement before you use the PRINTTO
procedure.
QDEVICE procedure
Here are some important updates for SAS 9.4:
Base SAS 9.4 95
n The PROC QDEVICE DEVLOC= option enables you to specify a device library
other than the SAS/GRAPH Gdevicen libraries and the Sashelp library. You can
report on the first occurrence of a device, or you can report on all occurrences of
a device in the Gdevicen and Sashelp libraries.
n The PROC QDEVICE CATALOG= option enables you to specify a catalog, other
than the DEVICES catalog, to search.
n The DEVICE statement and the PRINTER statement allow the wildcards * and ?
in device names and printer names.
n The value for a Windows printer device type, as reported by the TYPE variable,
is Printer Interface Device. Printer Interface Device replaces the value System
Printer.
n For all reports, the NAMETYPE variable has been renamed to TYPE.
n For all reports except the General report, information about prototypes has been
removed. The PROTOTYPE variable information is now reported in only the
General report.
n Character variable lengths in report output data sets now have a fixed length of
128 characters. The LENGTH statement is no longer required when reports are
merged or concatenated.
System Options
The EXTENDOBSCOUNTER (EOC) system option is new for SAS 9.4. In SAS 9.3, this
option was available only as a data set option and a LIBNAME option.
n If you are creating data sets with SAS 9.4 and those data sets need to be backward
compatible with a SAS release earlier than SAS 9.3, set the
EXTENDOBSCOUNTER system option to NO.
n If your SAS 9.4 data sets are not going to be read by a SAS release earlier than
SAS 9.3, set the EXTENDOBSCOUNTER system option to YES.
96 Chapter 13 / Base SAS
DMSOUTSIZE= 2,147,483,647
LRECL= 32,767
PDFCOMMENT PDFCOMMENT
YEARCUTOFF= 1926
ODS Changes
n In SAS 9.4, the default HTML style for z/OS environments has changed from Default
to Htmlblue.
n The ODS.TAGSETS RTF statement now supports the BACKGROUNDIMAGE= style
attribute.
n The following enhancements have been made to the ODS GRAPHICS statement:
o The default for the ANTIALIASMAX= option has changed from 600 to 4000.
o The default device driver for the RTF and TAGSETS.RTF destination has
changed to EMF.
n The default style for all Printer family destinations (PS, PDF, PCL) has changed from
Styles.Printer to Styles.Pearl.
If you are upgrading from a previous release of SAS, note that several new defaults
were implemented in SAS 9.3 for the SAS windowing environment in UNIX and
Windows operating environments.
Base SAS 9.4 97
New Default
Area of Change Previous Default Beginning with SAS 9.3
Where graphs are saved Current SAS directory SAS Work Library
The previous defaults are still used when you run SAS in batch mode.
Because of the changes in the default values, you will see the following changes:
n Results are displayed in the HTMLBlue style, which is a modern style well suited for
displaying graphs and tables together. Prior to SAS 9.3, tables were displayed in
monospace, and graphs were displayed using the LISTING style.
n Analytical procedures that support ODS Graphics automatically create graphs. Prior
to SAS 9.3, you had to explicitly enable ODS Graphics.
n Tables and graphs are displayed together in the HTML results viewer window. Prior
to SAS 9.3, tables and graphs were displayed separately in the Output and Graph
windows.
n Graphs are no longer saved in the current SAS directory by default. Instead, they
are saved in the directory that corresponds to your SAS Work library. Hence, by
default, graphs are automatically deleted at the end of your SAS session. You can
specify a different directory in your SAS preferences.
For more information, see the SAS Output Delivery System: User’s Guide.
98 Chapter 13 / Base SAS
BARCHART Statement
In SAS 9.4, the BARCHART statement STAT=PCT option displays percentages
between 0 and 100 in order to be consistent with other GTL statements. In prior
releases, STAT=PCT displayed proportional values between 0 and 1. To restore the
proportional value in SAS 9.4, change STAT=PCT to STAT=PROPORTION.
Font Changes
Here are the font changes in SAS 9.4:
n The new Unicode fonts, Arial Unicode MS and Times New Roman Uni, replace the
Monotype Sans WT and Thorndale Duospace WT Unicode fonts.
CSongGB19030-LightHWL NSimSun
REGRESSIONPLOT Statement
In the second maintenance release for SAS 9.4, the DEGREE= regression option range
is changed from 0-174 to 1-10. If the DEGREE= option value is outside of this range, an
error results and the graph is not generated. If your existing SAS programs specify in a
REGRESSIONPLOT statement a value for DEGREE= that is outside of the 1-10 range,
you must change the value to a value that is within the 1-10 range.
Base SAS 9.4_M3 101
MARKERSIZERESPONSE= SIZERESPONSE=
option
You can continue to use the deprecated options. However, SAS recommends that you
switch to the new options or alternate statement as soon as possible.
9.4, the SAS Deployment Wizard automates the process of updating the TLS
certificates in UNIX and z/OS environments and for Java applications on Windows and
UNIX. SAS provides a default CA certificate bundle. The installation also includes the
files that are used as the trusted list of certificates.
For SAS 9.4 deployments that were created before the third maintenance release of
SAS 9.4, you had to manually set the SSLCALISTLOC option in the configuration file to
point to your CA certificates. When you updated your software after the initial
deployment, any configuration files were overwritten, and you had to manually add the
SSLCALISTLOC option again.
When you update your software, the SAS Deployment Wizard looks through all
configuration files for any manual additions of the SSLCALISTLOC option. To prevent
any interference with the new trusted CA bundle, all manual additions of the
SSLCALISTLOC option are commented out in the configuration file. After you finish the
software update, your SAS software uses the new trusted CA bundle that shipped with
the software update.
If you need to use any additional self-signed or site-signed CA certificates, you must
add these certificates to the new trusted CA bundle. You can add certificates to the
trusted CA bundle by using the Add Certificate task in the SAS Deployment Manager.
Adding CA certificates should be repeated for each machine in the deployment.
Note: You need to add your certificates only the first time that you upgrade to the third
maintenance for SAS 9.4. In subsequent upgrades, you do not need to use the SAS
Deployment Manager to add these certificates unless you have new or updated
certificates. Any new or updated certificates need to be added to the trusted CA bundle.
For more information, see SAS Deployment Wizard 9.4 and SAS Deployment Manager
9.4: User’s Guide and “Setting Up CA Certificates for SAS Deployment” in SAS
Intelligence Platform: Installation and Configuration Guide.
Note: Starting in the third maintenance release for SAS 9.4, manually adding any self-
signed or site-signed CA certificates to the cacerts file is no longer supported.
Base SAS 9.4_M3 103
Hadoop Support
n The requirements for connecting to a Hadoop cluster using either the HADOOP
procedure or the FILENAME, Hadoop access method have changed. There is an
alternate method for specifying the location of the Hadoop configuration files so that
you no longer have to merge properties from multiple Hadoop configuration files and
then use the CFG= option to specify the location. You can now use the
SAS_HADOOP_CONFIG_PATH environment variable to specify the location of the
configuration files. For more information, see the documentation for the HADOOP
procedure in Base SAS Procedures Guide.
n The CONCAT and DIR Hadoop options in the FILENAME, Hadoop access method
are now mutually exclusive because the SAS_HADOOP_CONFIG_PATH
environment variable is available.
Procedures
n The new HEADERS statement in PROC HTTP replaces the HEADERIN and CT
procedure options. You now can use the new HEADERS statement to specify
header requests without providing a fully formatted input file via a fileref. For more
information, see “HEADERS Statement” in Base SAS Procedures Guide.
n The default method for PROC HTTP when the METHOD or IN options are not
specified has changed from POST to GET. For more information, see the PROC
HTTP METHOD option in Base SAS Procedures Guide
n For web servers that support caching, the HTTP procedure now uses connection
caching and cookie caching by default. For more information, see “HTTP Procedure”
in Base SAS Procedures Guide.
n The default value of BUFSIZE has changed in PROC MIGRATE. The new default is
the buffer page size of the current session. To continue using the previous behavior
(which is to clone the page size of the members from the source library), specify
BUFSIZE=KEEPSIZE. For more information, see “MIGRATE Procedure” in Base
SAS Procedures Guide.
DENSITYPLOT Statement
In SAS 9.4, the WEIGHT= option of the KERNEL( ) distribution option in the
DENSITYPLOT statement is changed to WEIGHTFUNCTION=. This change enables
the addition of the WEIGHT= option in the DENSITYPLOT statement. Starting with SAS
9.4, the WEIGHT= option is not valid in the KERNEL() distribution option and results in
a syntax error. If your existing SAS programs specify the WEIGHT= option in the
KERNEL( ) distribution option, then you must change WEIGHT= to
WEIGHTFUNCTION=.
HEATMAPPARM Statement
In the third maintenance release for SAS 9.4, the DISCRETEX= and DISCRETEY=
options are added to the HEATMAPPARM statement. These options specify whether
the X or Y axis is discrete. The default is FALSE. For existing SAS programs that use
the HEATMAPPARM statement, if the X axis is discrete, the DISCRETEX=TRUE option
must be specified in the HEATMAPPARM statement. Likewise, if the Y axis is discrete,
the DISCRETEY=TRUE option must be specified in the HEATMAPPARM statement.
Otherwise, the heat map might not be drawn.
WATERFALLCHART Statement
In the third maintenance release for SAS 9.4, the COLORSTAT= option is added to the
WATERFALLCHART statement. The COLORSTAT= option is enabled by the
COLORRESPONSE= option. The COLORSTAT= option specifies the statistic to be
calculated for the data range of the color gradient. The default is SUM. For existing SAS
programs that use the WATERFALLCHART statement, if STAT= is used with
COLORRESPONSE= in the WATERFALLCHART statement and STAT= specifies a
statistic other than SUM, then the chart colors and color statistic might change from
106 Chapter 13 / Base SAS
those of previous releases. In that case, to restore the original colors and color statistic,
set COLORSTAT= in the WATERFALLCHART statement to the same statistic that is
specified in STAT=.
107
14
SAS/ACCESS
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “SAS/ACCESS 9.4”
9.3_M2 9.4_M2, 9.4_M3 on page 109, “SAS/ACCESS 9.4_M1” on
9.2, 9.2_M2, page 110, “SAS/ACCESS 9.4_M2” on page
9.2_M3 111, and “SAS/ACCESS 9.4_M3” on page
111 (if appropriate).
2 Install and configure SAS 9.4.
SAS/ACCESS 9.4
Beginning with SAS 9.4, the SAS/ACCESS engines no longer support HP-UX or Linux
x86 operating environments.
SAS/ACCESS 9.4 to PC Files imports data from JMP files saved in JMP 7 or later
formats, and it exports data to files in JMP 7 or later formats. File formats in JMP 3
through JMP 6 are no longer supported. Support for these newer file formats enables
you to access JMP files from mobile apps such as the JMP Graph Builder iPad app. For
more information, see “JMP Files” in SAS/ACCESS Interface to PC Files: Reference.
110 Chapter 14 / SAS/ACCESS
n The META statement is used only for importing and exporting JMP files. META is no
longer supported and is ignored. Instead, extended attributes are automatically
used. If a file has extended attributes, they are automatically transferred to the new
file when that file is imported or exported. For example, when importing a JMP file
with extended attributes, the attributes are automatically attached to the new SAS
data set.
n The META data type for JMP files has been replaced by support for extended
attributes. META is ignored in programs, and a NOTE is generated about it in the
SAS log.
n The ROWSTATE data type is generated by JMP and is used to store several row-
level characteristics. If the JMP file contains row state information, PROC IMPORT
stores this information as a new variable with the name _rowstate_. If the EXPORT
procedures finds a column named _rowstate_, the procedure converts this column
into the row state information in the output JMP file. For more information, see “JMP
Data Types” in SAS/ACCESS Interface to PC Files: Reference.
n JMP variable names can be up to 255 characters in length.
n Because you can use the Base SAS IMPORT and EXPORT procedures on JMP
files without a SAS/ACCESS license, the preceding information applies to SAS 9.4
as well.
SAS/ACCESS 9.4_M1
The first maintenance release for the SAS/ACCESS 9.4 software shipped in December
2013. The SAS/ACCESS Interface to Relational Databases and the SAS/ACCESS
Interface to PC Files include some new and enhanced options.
Also, in the SAS/ACCESS Interface to PC Files when you open a Microsoft Excel
workbook (XLSX format), all other worksheets in the workbook have their formulas
automatically recalculated. This includes any formulas that reference a sheet that has
been added or replaced by PROC EXPORT DBMS=XLSX.
SAS/ACCESS 9.4_M3 111
SAS/ACCESS 9.4_M2
The second maintenance release for the SAS/ACCESS 9.4 software shipped in August
2014.
In SAS/ACCESS 9.4 Interface to PC Files, these SAS LIBNAME options are no longer
supported: FILELOCK=, CONNECTION=, and CONNECTION_GROUP=.
For the SAS/ACCESS Interface to Oracle, starting with Oracle 12c, the default data type
for SAS character variables in SAS output has changed to either VARCHAR2 or CLOB,
depending on the length of the variable.
SAS/ACCESS 9.4_M3
The third maintenance release for the SAS/ACCESS 9.4 software shipped in July 2015.
In the third maintenance release for SAS 9.4, these SAS/ACCESS features are
different:
n The format for specifying octal codes using the BL_ESCAPE= data set option has
changed. Specifying these codes with a preceding ‘E’ is no longer supported. For
example, instead of E'\24', specify this code as the three-digit octal code, \024.
n The default value of the SQLGENERATION= system option is now (NONE
DBMS='TERADATA DB2 ORACLE NETEZZA ASTER GREENPLM HADOOP
SAPHANA IMPALA HAWQ').
n For Hadoop, the NUMTASKS= LIBNAME option is no longer supported.
n For Impala, you can use ‘IMPALA’ in the LIBNAME statement to specify this engine.
112 Chapter 14 / SAS/ACCESS
n For MySQL, these functions now require SQL_FUNCTIONS=ALL before they can be
passed to MySQL: BYTE, COMPRESS, DATE, DATEPART, DATETIME, LENGTH,
REPEAT, ROUND, SOUNDEX, SUBSTR, TIME, TIMEPART, TODAY.
n For OLE DB, the COMPRESS function can be passed via the SQL pass-through
facility only when SQL_FUNCTIONS=ALL.
n For PostgreSQL, the COMPRESS and COT functions can be passed automatically
via the SQL pass-through facility. These functions do not require
SQL_FUNCTIONS=ALL.
n For Teradata, the SUM4 function was removed from the list of functions that can be
passed via the SQL pass-through facility. The TRIM function can be passed
automatically and does not require SQL_FUNCTIONS=ALL. The LENGTH function
does require SQL_FUNCTIONS=ALL.
113
15
SAS Add-In for Microsoft Office
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
6.1 (SAS 9.4) 6.1_M1 (SAS 1 Before you upgrade, see “SAS Add-In 6.1_M1 for
9.4_M1); 7.1, Microsoft Office” on page 117 and “SAS Add-In
7.11 (SAS 7.1 for Microsoft Office” on page 117 (if
9.4_M2); 7.12 appropriate).
(SAS 9.4_M3)
2 To upgrade to the latest release of SAS Add-In
for Microsoft Office, see “Install and Configure a
Software Update” on page 69.
6.1_M1 (SAS 7.1, 7.11 (SAS 1 Before you upgrade, see “SAS Add-In 7.1 for
9.4_M1); 7.1, 7.11 9.4_M2); 7.12 Microsoft Office” on page 117.
(SAS 9.4_M2) (SAS 9.4_M3)
2 To upgrade to the latest release of SAS Add-In
for Microsoft Office, see “Install and Configure a
Software Update” on page 69.
Add-In for Microsoft Office on SAS 9.4. You can migrate to SAS 9.4, or you can create a
new SAS 9.4 deployment.
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
5.1, 4.3 (SAS 9.3) 6.1 (SAS 9.4); 1 Before you migrate, see “SAS Add-In 6.1 for
6.1_M1 (SAS Microsoft Office” on page 116, “SAS Add-In
9.4_M1); 7.1, 6.1_M1 for Microsoft Office” on page 117, and
7.11 (SAS “SAS Add-In 7.1 for Microsoft Office” on page
9.4_M2); 7.12 117 (if appropriate).
(SAS 9.4_M3)
2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To create
a new deployment, see SAS 9.4 Intelligence
Platform: Installation and Configuration Guide.
3 To complete any post-configuration steps, see
SAS 9.4 Intelligence Platform: Desktop
Administration Guide.
6.1 (SAS 9.4); 7.12 (SAS To migrate within the same SAS release, see SAS
6.1_M1 (SAS 9.4_M3) 9.4 Intelligence Platform: Migration Guide.
9.4_M1);7.1, 7.11
(SAS 9.4_M2)
7.12 (SAS 9.4_M3) 7.12 (SAS To migrate within the same release, see SAS 9.4
9.4_M3) Intelligence Platform: Migration Guide.
n You can use SAS Add-In 5.1 for Microsoft Office to access SAS 9.3 and SAS 9.2
content.
You can use only one release of the SAS add-in at a time. The functionality that is
available in the SAS add-in depends on the roles and capabilities that are assigned in
SAS Management Console. These settings are release specific. If you are running SAS
Add-In 6.1 for Microsoft Office, you can use only those capabilities that are defined for
the 6.1 release. If you are running SAS Add-In 5.1 for Microsoft Office, you can use only
those capabilities that are defined for the 5.1 release. For more information about roles
and capabilities for SAS Add-In for Microsoft Office, see SAS Intelligence Platform:
Desktop Application Administration Guide.
If you have administrative privileges, use the SAS Add-In for Microsoft Office Utility to
select which release of the SAS add-in to enable for selected Microsoft Office
applications. (Always use the SAS Add-In for Microsoft Office Utility that is included with
the latest release of the SAS add-in.) For more information about this utility, see the
Help for SAS Add-In for Microsoft Office.
Note: Third-party ActiveX controls are not supported in 64-bit versions of Microsoft
Office. If you are running in a 64-bit Windows environment, use the ActiveX image
format for your SAS content.
Here are some of the new features in SAS Add-In 6.1 for Microsoft Office:
n support for Microsoft Office 2013, 2010, and 2007
SAS Add-In 7.1 for Microsoft Office 117
n enhancements to the automation interfaces, including new objects that enable you to
work with reports from SAS Visual Analytics
n support for the Excel XP tagset
n new tasks, such as High-Performance Logistic Regression, High-Performance
Linear Regression, SAS Rapid Predictive Modeler, and SAS Recency, Frequency,
and Monetary, that provide more integration with other SAS products
A new stand-alone installer is available for SAS Add-In for Microsoft Office. For more
information, see SAS Deployment Wizard and SAS Deployment Manager 9.4: User's
Guide, available at http://support.sas.com/deploywizug94.html.
The tasks are no longer available as options from the Task drop-down menu on the
SAS tab. To turn on the Task drop-down menu, select the new Show menu for built-in
tasks on the Ribbon option in the Options dialog box.
Also, the Show Prompts option on the SAS tab has been replaced by the Report
Controls option. This new option shows the entire report and the prompts. With the
report controls, you can filter, drill, expand, collapse, and brush the data.
SAS Add-In 7.11 for Microsoft Office includes a new feature that enables you to check
for updates when you first open Microsoft Excel, Microsoft Word, Microsoft PowerPoint,
or Microsoft Outlook or while you are working in these applications. If an update is
available, a message appears. In the message dialog box, click support.sas.com to
learn more about the contents of the software update. To apply a software update, you
must close all Microsoft Excel, Word, PowerPoint, and Outlook applications. You can
use this updates feature to upgrade from the 7.11 release to the 7.12 release.
If you want to switch to the SAS Visual Analytics Add-In for Office, you first must
uninstall the SAS Add-In for Microsoft Office. Then you can install the SAS Visual
Analytics Add-In for Office. Now, your add-in functionality is limited to opening,
interacting and refreshing SAS Visual Analytics reports in Microsoft Excel and Microsoft
PowerPoint.
For more information, see the software product page for SAS Add-In for Microsoft
Office.
119
16
SAS Anti-Money Laundering
6.1, 6.1_M1, 6.2, 6.2_M1 6.3, 6.3_M1 (SAS 9.4) For more information about
how to request this new
release and the features that
are available, contact your
SAS account representative.
120 Chapter 16 / SAS Anti-Money Laundering
5.1, 5.1_M1 (SAS 9.3) 7.1 (SAS 9.4) If your site is running SAS
Anti-Money Laundering 5.1 or
earlier, you should upgrade to
SAS Anti-Money Laundering
7.1. For more information
about how to request this
new release and the features
that are available, contact
your SAS account
representative.
5.2_M1 (SAS 9.3) 6.3, 6.3_M1 (SAS 9.4) For more information about
6.1, 6.1_M1, 6.2, 6.2_M1, how to request this new
6.3, 6.3_M1 (SAS 9.4) release and the features that
are available, contact your
SAS account representative.
n SAS Anti-Money Laundering 7.1 in July 2016. If your site is running SAS Anti-Money
Laundering 5.1 or earlier, you should upgrade to SAS Anti-Money Laundering 7.1.
For more information about this release, contact your SAS account representative and
see the product documentation page for SAS Anti-Money Laundering.
17
SAS Asset Performance Analytics
6.1 (SAS 9.4) 6.1_M1, 6.1_M2 (SAS 9.4) For information about how to
upgrade to the latest release
of SAS Asset Performance
Analytics, see SAS Asset
Performance Analytics 6.1:
Administrator’s Guide.
124 Chapter 17 / SAS Asset Performance Analytics
6.1, 6.1_M1, 6.1_M2 (SAS 6.1, 6.1_M1, 6.1_M2 (SAS To migrate within the same
9.4) 9.4) release, see SAS Asset
Performance Analytics 6.1:
Administrator’s Guide.
For the product documentation, see the product documentation page for SAS Asset
Performance Analytics.
Note: The documentation for SAS Asset Performance Analytics is available only to
customers who license this product.
125
18
SAS BI Dashboard
4.4 (SAS 9.4) 4.4_M1 (SAS 1 To upgrade to the latest release of SAS BI
4.4_M1 (SAS 9.4_M1) Dashboard 4.4, see “Install and Configure a
9.4_M1) 4.4_M2 (SAS Software Update” on page 69.
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
4.31, 4.31_M1, 4.4, 4.4_M1, 1 Before you migrate, see “SAS BI Dashboard 4.4”
4.31_M2 (SAS 9.3) 4.4_M2, 4.4_M3 on page 127.
4.3 (SAS 9.2_M3) (SAS 9.4)
2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To create
a new deployment, see SAS 9.4 Intelligence
Platform: Installation and Configuration Guide.
3 Complete the post-configuration steps in
“Updating Favorites in Your Web Browser” on
page 128 and SAS 9.4 Intelligence Platform:
Web Application Administration Guide.
4.4, 4.4_M1, 4.4, 4.4_M1, To migrate within the same SAS release, follow the
4.4_M2 (SAS 9.4) 4.4_M2, 4.4_M3 steps in SAS 9.4 Intelligence Platform: Migration
(SAS 9.4) Guide.
4.4_M3 (SAS 9.4) 4.4_M3 (SAS To migrate within the same release, follow the steps
9.4) in SAS 9.4 Intelligence Platform: Migration Guide.
for the new release. You can also access SAS BI Dashboard 4.4 by using this
unresolved link: http://server:port/SASBIDashboard.
130 Chapter 18 / SAS BI Dashboard
131
19
SAS BI Portal
4.4 (SAS 9.4) 4.4_M1 (SAS To upgrade to the latest release of SAS BI Portal
9.4_M1), 4.4_M2 4.4, see “Install and Configure a Software
(SAS 9.4_M2), Update” on page 69.
4.4_M3 (SAS
9.4_M3)
4.31, 4.31_M1, 4.4, 4.4_M1, To migrate to a new release, see SAS 9.4
4.31_M2 (SAS 9.3) 4.4_M2, 4.4_M3 Intelligence Platform: Migration Guide. To create
4.3 (SAS 9.2_M3) (SAS 9.4) a new deployment, see SAS 9.4 Intelligence
Platform: Installation and Configuration Guide.
4.4, 4.4_M1, 4.4, 4.4_M1, To migrate within the same SAS release, follow
4.4_M2 (SAS 9.4) 4.4_M2 , 4.4_M3 the steps in SAS 9.4 Intelligence Platform:
(SAS 9.4) Migration Guide.
4.4_M3 (SAS 9.4) 4.4_M3 (SAS 9.4) To migrate within the same release, follow the
steps in SAS 9.4 Intelligence Platform: Migration
Guide.
20
SAS Business Data Network
By linking terms to business rules and data monitoring processes, SAS Business Data
Network provides a single entry point for all data consumers to better understand their
data. Data stewards, IT staff, and enterprise architects can use the terms to promote a
common vocabulary across projects and business units. Permissions can be set to
allow only specific users to access and control the data in SAS Business Data Network.
134 Chapter 20 / SAS Business Data Network
SAS Business Data Network also provides workflow support that enables you to divide
the responsibilities for creating, reviewing, and approving terms among the members of
your team. In this way, each role can be fulfilled by the most qualified member of the
team.
For more information, see the software product page for SAS Business Data Network.
If SAS Business Data Network is in your order, you must run the SAS Deployment
Wizard a second time to add SAS Business Data Network to your deployment. For
more information, see “Adding a New Product” on page 87.
135
21
SAS Business Rules Manager
2.1 (SAS 9.4) 2.2 (SAS 9.4_M2), 1 Before you upgrade, see “SAS Business Rules
3.1 (SAS 9.4_M3) Manager 2.2” on page 137 and “SAS
Business Rules Manager 3.1” on page 138.
2 To upgrade to the latest release of SAS
Business Rules Manager, see “Install and
Configure a Software Update” on page 69.
3 Complete the post-installation configuration
steps in SAS Business Rules Manager:
Administrator’s Guide.
2.2 (SAS 9.4_M2) 3.1 (SAS 9.4_M3) 1 Before you upgrade, see “SAS Business Rules
Manager 3.1” on page 138.
2 To upgrade to the latest release of SAS
Business Rules Manager, see “Install and
Configure a Software Update” on page 69.
3 Complete the post-installation configuration
steps in SAS Business Rules Manager:
Administrator’s Guide.
1.2 (SAS 9.3_M2) 2.1 (SAS 9.4), 2.2 1 Before you upgrade, see “SAS Business Rules
(SAS 9.4_M2), Manager 2.2” on page 137 and “SAS
3.1_(SAS 9.4_M3) Business Rules Manager 3.1” on page 138.
2 To migrate to the new release, see SAS
Business Rules Manager: Administrator’s
Guide. To create a new deployment, see SAS
9.4 Intelligence Platform: Installation and
Configuration Guide.
2.1 (SAS 9.4), 2.2 2.2 (SAS 9.4_M2), To migrate to the latest release of SAS Business
(SAS 9.4_M2) 3.1 (SAS 9.4_M3) Rules Manager, see SAS Business Rules
Manager: Administrator’s Guide.
3.1 (SAS 9.4_M3) 3.1 (SAS 9.4_M3) To migrate within the same release, see SAS
Business Rules Manager: Administrator’s Guide.
In addition, SAS Business Rules Manager 2.2 provides new features and
enhancements that enable you to perform these tasks:
n create libraries and register tables in the SAS Metadata Repository
n send rule flows through approval workflows and track workflow tasks
n manage versions of rule sets and rule flows
n create rule flows as stored processes
n run a wizard to generate and import vocabularies, rule sets, and rule flows from an
input data source by using the Decision Tree, Scorecard, Market Basket Analysis, or
Recency Frequency Monetary discovery techniques
n execute rule flows inside the databases by using the SAS In-Database Code
Accelerator for Teradata and Greenplum
n selectively include rule sets in a rule flow
n display the terms and lookup tables that are used in a rule set
n import terms from an input data table
n search for rule sets by term
Beginning with SAS Business Rules Manager 3.1, the rule set editor does not
automatically add the term name in an expression that begins with a minus sign (–). For
example, if you enter -10 for term, SAS Business Rules Manager interprets this as
term = -10. (The behavior for positive values has not changed. The value +10 is still
interpreted as term = term +10.)
For more information, see the software product page for SAS Business Rules Manager.
139
22
SAS/CONNECT
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “SAS/CONNECT 9.4”
9.3_M2 9.4_M2, 9.4_M3 on page 141, “SAS/CONNECT 9.4_M1” on
page 142, “SAS/CONNECT 9.4_M2” on page
142, and “SAS/CONNECT 9.4_M3” on page
142 (if appropriate).
2 Install and configure SAS 9.4.
SAS/CONNECT 9.4
The following SAS/CONNECT spawner options are no longer supported:
n –TIMESTAMP
n –LOGEVENTS
n –SECURITY | –NOSECURITY
n –DELETE
142 Chapter 22 / SAS/CONNECT
SAS/CONNECT 9.4_M1
In December 2013, SAS shipped the first maintenance release for SAS 9.4, which
includes the new LOCKDOWN statement and LOCKDOWN system option. With
LOCKDOWN, SAS server administrators can create a restricted environment in which
the SAS client has access to a limited set of directories and files. All other directories
and files are inaccessible. In addition to there being access restrictions on directories
and files, there are restrictions on how SAS/CONNECT users can sign on when running
SAS in a locked-down state. For more information about the LOCKDOWN feature in
SAS/CONNECT, see “Locked-Down SAS Sessions” in SAS/CONNECT User’s Guide.
SAS/CONNECT 9.4_M2
In August 2014, SAS shipped the second maintenance release for SAS 9.4.
SAS/CONNECT 9.4_M3
In July 2015, SAS shipped the third maintenance release for SAS 9.4.
143
23
SAS Contextual Analysis
12.3 (SAS 9.4), 13.2 (SAS 1 Before you upgrade, see “About SAS
13.2 (SAS 9.4_M2) 9.4_M2); 14.1 and Contextual Analysis” on page 144.
14.1_M1 (SAS
9.4_M3) 2 To upgrade to the latest release of SAS
Contextual Analysis, see “Install and Configure
a Software Update” on page 69.
144 Chapter 23 / SAS Contextual Analysis
13.2 (SAS 9.4_M2) 13.2 (SAS For more information, contact your SAS account
9.4_M2); 14.1 and representative.
14.1_M1 (SAS
9.4_M3)
SAS Contextual Analysis enables you to identify key textual topics in your document
collections, automatically generate Boolean linguistic rules, and refine the model and
use it to categorize documents. You can also take advantage of concept extraction
capabilities by writing your own rules. (A concept is a property such as a book title, last
name, city, gender, and so on.)
SAS has shipped these releases:
n SAS Contextual Analysis 12.3 in October 2013
About SAS Contextual Analysis 145
24
SAS Credit Scoring for Banking
5.3 (SAS 9.4) 5.4 (SAS 9.4) For more information about how to upgrade to the
latest release, see SAS Credit Scoring for
Banking: Upgrade and Migration Guide.
148 Chapter 24 / SAS Credit Scoring for Banking
5.1, 5.2 (SAS 9.3) 5.3, 5.4 (SAS 9.4) For more information, see SAS Credit Scoring for
Banking: Upgrade and Migration Guide.
5.3 (SAS 9.4) 5.4 (SAS 9.4)
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Credit Scoring for Banking.
Note: The documentation for SAS Credit Scoring for Banking is available only to
customers who license this product.
149
25
SAS Customer Due Diligence
6.1, 6.2, 6.3 (SAS 9.4) 6.3_M1 (SAS 9.4) For more information about
how to request this new
release and the features that
are available, contact your
SAS account representative.
150 Chapter 25 / SAS Customer Due Diligence
6.1, 6.2, 6.3 (SAS 9.4) 6.3_M1 (SAS 9.4) For more information about
how to migrate to the latest
release, contact your SAS
account representative.
For more information about this release, contact your SAS account representative and
see the product documentation page for SAS Customer Due Diligence.
Note: The documentation for SAS Customer Due Diligence is available only to
customers who license this product.
151
26
SAS Customer Intelligence
SAS Customer Intelligence 6.3, 6.4, and 6.5 run on SAS 9.4.
6.3, 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 For more information about this release, contact
(SAS 9.4_M3) your SAS account representative.
6.1, 5.41 (SAS 9.3) 6.3, 6.4 (SAS 9.4); For more information about how to request this
6.5 (SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
6.3, 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 To migrate to SAS Customer Intelligence 6.4 or
(SAS 9.4_M3) 6.5, contact your SAS account representative.
6.5 (SAS 9.4_M3) 6.5 (SAS 9.4_M3) To migrate within the same release, see the
documentation for SAS Customer Intelligence.
For more information about this release, contact your SAS account representative and
see the product documentation page for SAS Customer Intelligence.
Note: The documentation for SAS Customer Intelligence is available only to customers
who license this product.
154 Chapter 26 / SAS Customer Intelligence
155
27
SAS Customer Link Analytics
5.5, 5.6 (SAS 9.4) 5.6 (SAS 9.4), 6.5 (SAS For more information about
9.4_M3) how to request this new
release and the features that
are available, contact your
SAS account representative.
156 Chapter 27 / SAS Customer Link Analytics
5.5 , 5.6 (SAS 9.4) 5.6 (SAS 9.4); 6.5 (SAS For more information about
9.4_M3) how to migrate to the latest
release, contact your SAS
6.5 (SAS 9.4_M3) 6.5 (SAS 9.4_M3) account representative.
For the product documentation, see the product documentation page for SAS Customer
Link Analytics.
Note: The documentation for SAS Customer Link Analytics is available only to
customers who license this product.
157
28
SAS and DataFlux
Some DataFlux products are being enhanced and changing their names to SAS, and
others will in the future. For example, in the SAS 9.4 release, DataFlux Federation
Server has been enhanced and become SAS Federation Server. In this release, SAS
has also created new web-based products that include new features and some
functionality from earlier DataFlux products, such as SAS MDM for master data
management. Certain SAS data management offerings include these newer versions of
the SAS products.
Instead of being licensed separately, DataFlux products are now part of SAS software
offerings that include other SAS products as well. For example, the SAS Data
Management offering includes Base SAS and the SAS Metadata Server as well as
DataFlux Data Management Studio and Data Management Server.
In certain SAS data management offerings, the following SAS products replace older
DataFlux products:
n SAS Event Stream Processing Engine
n SAS Federation Server, which includes SAS Federation Server Manager and SAS
Drivers for Federation Server
n SAS MDM, which includes new products such as SAS Data Remediation and SAS
Task Manager
The following DataFlux products are still supported but are used only in earlier software
releases:
n DataFlux dfPower Studio and DataFlux Integration Server
n DataFlux Event Stream Processing Engine
n DataFlux Federation Server, which includes DataFlux Federation Server Manager
and DataFlux Drivers for ODBC and JDBC.
n DataFlux qMDM Solution
For more information, see product names that being with “DataFlux” on the SAS
Product Documentation page.
For more information, see the product-specific software pages in the SAS Product
Listing: Index A-Z.
SAS Enterprise Data Integration Server included SAS/SHARE, but the SAS Data
Management Standard offering does not. As a result, your source environment might
include SAS/SHARE, but your migrated SAS 9.4 environment will not.
Note: In SAS Management Console, if you see a SAS/SHARE server in the metadata,
this server reference is a remnant from the source environment. No SAS/SHARE server
is listed in the SAS configuration directory.
If you want to continue using SAS/SHARE, contact your SAS account representative. If
your site is licensed for SAS/SHARE, work with your SAS account representative to
include SAS/SHARE in your software order.
The installation process for the UNIX and Linux operating environments now configures
host authentication. Formerly, this configuration process took place after installation.
Now, after installation, you can reconfigure authentication as needed, as described in
DataFlux Authentication Server 4.1 Administrator’s Guide.
You use the SAS Deployment Wizard to configure the metadata for DataFlux
Authentication Server 4.1 and SAS Federation Server 4.1. However, because no
metadata existed for these products before the 4.1 release, you must run the SAS
Deployment Wizard twice to upgrade from the 3.2 release to the 4.1 release.
During the first run, the SAS Deployment Wizard applies any maintenance releases and
installs any product updates. Run the SAS Deployment Wizard a second time to
complete the configuration steps for DataFlux Authentication 4.1 and SAS Federation
Server 4.1.
Starting with the first maintenance release, the DataFlux Authentication Server is
required only by DataFlux Web Studio and DataFlux Web Studio Server.
In the first maintenance release for DataFlux Authentication Server 4.1, you can use the
ASExport procedure to export users and groups from the DataFlux Authentication
162 Chapter 28 / SAS and DataFlux
Server to the SAS Metadata Server. However, to use the ASExport procedure, you must
also be running the third maintenance release for SAS 9.4.
For more information about the first maintenance release for DataFlux Authentication
Server 4.1 and the ASExport procedure, see DataFlux Authentication Server 4.1
Administrator’s Guide, Second Edition.
Metadata for individual instances of DataFlux Data Management Server 2.7 is now
created automatically on the SAS Metadata Server during installation. The server
instances can be updated to revise parts of the server configuration. Server instances
are no longer manually registered in DataFlux Data Management Studio. The primary
administrative interface for DataFlux Data Management Server remains in DataFlux
Data Management Studio.
Software upgrades can now be installed by updating the existing installed location of the
previous release (no manual migration). You can also choose to perform a SAS
Migration Utility migration and then manually migrate any files that are not automatically
migrated by the SAS Migration Utility.
DataFlux Data Management Studio 163
If you are moving from a DataFlux Authentication Server to a SAS Metadata Server, a
new utility is available to move the content for the DataFlux Data Management Server.
The dftool utility updates the local security files to replace DataFlux Authentication
Server IDs with SAS Metadata Server IDs.
DataFlux Secure
DataFlux Secure is installed in a disabled state. If you have not used DataFlux Secure
before, and if you do not want to use it now, then do not change your previous
configuration files as you move them forward into 2.41.
If you have used DataFlux Secure before, then you need to configure all of your
products to enable the provided security features. To enable and configure DataFlux
Secure, see DataFlux Secure: Administrator’s Guide.
If you want to configure DataFlux Secure for the first time, you need to enable and
configure DataFlux Secure on all instances of the products listed earlier. Global
enablement ensures that the same level of protection is provided for all of your servers,
clients, and network connections.
DataFlux Secure 165
DataFlux Secure 2.5 is installed in a disabled state. To enable and configure DataFlux
Secure, see DataFlux Secure: Administrator’s Guide.
DataFlux Secure now offers FIPS compliance for SOAP client connections in DataFlux
Data Management Server and DataFlux Data Management Studio.
This step must be performed for both new installations and for existing installations.
After the Web Studio Server is in SAS Management Console, this server appears in
the Data Management Servers riser in DataFlux Data Management Studio.
168 Chapter 28 / SAS and DataFlux
169
29
SAS Data Integration Studio
4.7 (SAS 9.4) 4.8 (SAS 9.4_M1), 1 Before you upgrade, see “SAS Data Integration
4.9 (SAS 9.4_M2), Studio 4.7_M1 and 4.8” on page 172 and “SAS
4.901 (SAS Data Integration Studio 4.7_M2 and 4.9” on
9.4_M3) page 172 (if appropriate).
2 To upgrade to SAS Data Integration Studio 4.8
or 4.9, see “Install and Configure a Software
Update” on page 69.
4.8 (SAS 9.4_M1) 4.9 (SAS 9.4_M2), 1 Before you upgrade, see “SAS Data Integration
4.901 (SAS Studio 4.7_M2 and 4.9” on page 172.
9.4_M3)
2 To upgrade to SAS Data Integration Studio 4.9,
see “Install and Configure a Software Update”
on page 69.
4.6 (SAS 9.3) 4.7 (SAS 9.4), 4.8 1 Before you upgrade, see “SAS Data Integration
(SAS 9.4_M1), 4.9 Studio 4.7” on page 171, “SAS Data
(SAS 9.4_M2), Integration Studio 4.7_M1 and 4.8” on page
4.901 (SAS 172 , and “SAS Data Integration Studio 4.7_M2
9.4_M3) and 4.9” on page 172 (if appropriate).
2 To migrate to SAS 9.4, see SAS 9.4 Intelligence
Platform: Migration Guide. To create a new
deployment, see SAS 9.4 Intelligence Platform:
Installation and Configuration Guide.
SAS Data Integration Studio 4.5 (and later) provides two ways to register an error table
in metadata:
n Use the Error & Exception tab in the properties window for the transformation.
n Right-click on the transformation and select Add Error Table.
After you have registered an error table in the metadata, complete these steps:
1 Double-click the port for the error table (the second port in the hierarchy of ports on
the Data Validation transformation).
3 Specify the name of an error table and point to the library in which it is registered.
This name could be the name of the error table for the job that you migrated.
172 Chapter 29 / SAS Data Integration Studio
You cannot use the Analyze in Web Viewer option in SAS Data Integration Studio
unless the SAS Lineage web client is installed. If the SAS Lineage web client is
available on your network, you can use it to display lineage for tables and external files
that are used in SAS Data Integration Studio. For more information, see Chapter 63,
“SAS Lineage,” on page 315.
173
30
SAS Data Quality Accelerator for
Teradata
2.4 (SAS 9.4) 2.5, 2.6 (SAS 9.4) 1 Before you upgrade, see “SAS Data Quality
Accelerator 2.5 for Teradata” on page 175 and
“SAS Data Quality Accelerator 2.6 for
Teradata” on page 175 (if appropriate).
2 To upgrade to the latest release of SAS Data
Quality Accelerator for Teradata, see “Install
and Configure a Software Update” on page 69.
2.5 (SAS 9.4) 2.6 (SAS 9.4) 1 Before you upgrade, see “SAS Data Quality
Accelerator 2.6 for Teradata” on page 175.
2 To upgrade to SAS Data Quality Accelerator
2.6 for Teradata, see “Install and Configure a
Software Update” on page 69.
2.4, 2.5 (SAS 9.4) 2.5, 2.6 (SAS 9.4) To migrate within the same SAS release, see SAS
In-Database Products: Administrator’s Guide.
SAS Data Quality Accelerator 2.6 for Teradata 175
2.6 (SAS 9.4) 2.6 (SAS 9.4) To migrate within the same release, see SAS In-
Database Products: Administrator’s Guide.
To remove the session-based variants and use the new syntax, you need to rewrite your
existing client programs.
31
SAS Data Quality Server
Determining Your Update Path for SAS Data Quality Server . . . 177
Upgrading an Existing SAS 9.4 Deployment . . . . . . . . . . . . . . . . . . . . . . 177
Migrating to SAS 9.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
9.4, 9.4_M1, 9.4_M3 1 Before you upgrade, see “SAS 9.4 Data
9.4_M2 Quality Server” on page 178.
2 To upgrade to the latest release for SAS 9.4,
see “Install and Configure a Software Update”
on page 69.
178 Chapter 31 / SAS Data Quality Server
9.3, 9.3_M1, 9.4 1 Before you migrate, see “SAS 9.4 Data Quality
9.3_M2 Server” on page 178.
2 Install and configure SAS 9.4.
32
SAS Data Remediation
2.1, 2.1_M1 (SAS 2.2 (SAS 9.4) For more information about this release, contact
9.4) your SAS account representative.
2.1, 2.1_M1 (SAS 2..2 (SAS 9.4) To migrate to SAS Data Remediation 2.2, see
9.4) SAS MDM: Administrator’s Guide.
2.2 (SAS 9.4) 2.2 (SAS 9.4) To migrate within the same release, see SAS
MDM: Administrator’s Guide.
33
SAS Decision Manager
2.1 (SAS 9.4) 2.2 (SAS 9.4_M2) 1 Before you upgrade, see “SAS Decision
Manager 2.2” on page 183.
2 To upgrade to the latest release of SAS
Decision Manager, see “Install and Configure a
Software Update” on page 69.
3 Complete the post-upgrade steps in SAS
Decision Manager: Administrator’s Guide .
2.2 (SAS 9.4_M2) 3.1 (SAS 9.4_M3) 1 Before you upgrade, see “SAS Decision
Manager 3.1” on page 183.
2 To upgrade to the latest release of SAS
Decision Manager, see “Install and Configure a
Software Update” on page 69.
3 Complete the post-upgrade steps in SAS
Decision Manager: Administrator’s Guide.
2.1 (SAS 9.4), 2.2 2.2 (SAS 9.4_M2), To migrate to the latest release of SAS Decision
(SAS 9.4_M2) 3.1 (SAS 9.4_M3) Manager, see SAS Decision Manager:
Administrator’s Guide.
3.1 (SAS 9.4_M3) 3.1 (SAS 9.4_M3) To migrate within the same release, see SAS
Decision Manager: Administrator’s Guide.
SAS Decision Manager 3.1 183
Beginning with SAS Decision Manager 3.1, the rule set editor does not automatically
add the term name in an expression that begins with a minus sign (–). For example, if
you enter -10 for term, SAS Decision Manager interprets this as term = -10. (The
behavior for positive values has not changed. The value +10 is still interpreted as term
= term +10.)
For more information, see the software product page for SAS Decision Manager.
184 Chapter 33 / SAS Decision Manager
Starting in March 2016, SAS Micro Analytic Services (which is shipped with SAS
Decision Manager) is available. When you upgrade SAS Decision Manager, you might
see new prompts for licensing and databases. These new prompts are related to Micro
Analytic Services. For more information about these prompts, see SAS Micro Analytic
Services: Programming and Administration Guide. For more information, see Chapter
70, “SAS Micro Analytic Services,” on page 337.
185
34
SAS Decision Services
6.2 6..3 (SAS 9.4) 6.3 (SAS 9.4); 6.5 For more information about how to request this
(SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
186 Chapter 34 / SAS Decision Services
5.6, 5.5, 5.5_M1 6.3, 6.2 (SAS 9.4); For more information about how to request this
(SAS 9.3) 6.5 (SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
6.2, 6.3 (SAS 9.4) 6.3 (SAS 9.4); 6.5 For more information about how to request this
(SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
6.5 (SAS 9.4_M3) 6.5 (SAS 9.4_M3) To migrate within the same release, see the
documentation for SAS Decision Services 6.5.
For more information about this release, contact your SAS account representative and
see the product documentation page for SAS Decision Services.
Note: The documentation for SAS Decision Services is available only to customers
who license this product.
187
35
SAS Digital Marketing
6.3, 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 For more information about this release, contact
(SAS 9.4_M3) your SAS account representative.
188 Chapter 35 / SAS Digital Marketing
6.1, 5.41 (SAS 9.3) 6.3, 6.4 (SAS 9.4); For more information about how to request this
6.5 (SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
6.3, 6.4 (SAS 9.4) 6.5 (SAS 9.4_M3) To migrate to SAS Digital Marketing 6.5, contact
your SAS account representative.
6.5 (SAS 9.4_M3) 6.5 (SAS 9.4_M3) To migrate within the same release, contact your
SAS account representative.
Note: The documentation for SAS Digital Marketing is available only to customers who
license this product.
189
36
SAS Document Conversion Server
For more information about SAS Text Miner, see Chapter 85, “SAS Text Miner,” on page
389.
190 Chapter 36 / SAS Document Conversion Server
Release That
Current Release You Are
at Your Site Upgrading To High-Level Steps and Resources
SAS Text Miner SAS Text Miner For more information about how to request this new
12.3 (SAS 13.1 (SAS release and the features that are available, contact
Document Document your SAS account representative.
Conversion Server Conversion To upgrade to SAS Document Conversion Server
12.3) Server 13.1) 13.1, see “SAS Document Conversion Server 13.1”
on page 192.
SAS Document Conversion Server 12.3 191
Release That
Current Release You Are
at Your Site Migrating To High-Level Steps and Resources
SAS Text Miner SAS Text Miner For more information about how to request this new
12.1 or 12.1_M1 12.3 or 13.1 release and the features that are available, contact
(SAS Document (SAS Document your SAS account representative.
Conversion Server Conversion To upgrade to SAS Document Conversion Server
12.1 or 12._M1) Server 12.3 or 12.3 or 13.1, see “SAS Document Conversion Server
SAS Text Miner 13.1) 12.3” on page 191 or “SAS Document Conversion
5.1_M1 (SAS Server 13.1” on page 192.
Document
Conversion Server
5.1_M1)
1 In the Windows Control panel, use the Add or Remove Programs functionality to
uninstall the SAS Document Conversion Server.
2 Run the SAS Deployment Wizard to update all relevant components, including the
first maintenance release for SAS Text Miner 5.1.
192 Chapter 36 / SAS Document Conversion Server
3 After this installation is complete, run the SAS Deployment Wizard again and install
only the SAS Document Conversion Server.
1 In the Windows Control panel, use the Add or Remove Programs functionality to
uninstall the SAS Document Conversion Server.
2 Run the SAS Deployment Wizard to update all relevant components, including the
first maintenance release for SAS Text Miner 5.1.
3 After this installation is complete, run the SAS Deployment Wizard again and install
only the SAS Document Conversion Server.
37
SAS Enterprise Case Management
6.1, 6.1_M1, 6.2, 6.2_M2, 6.3 6.3_M1 (SAS 9.4) For more information about
(SAS 9.4) how to request this new
release and the features that
are available, contact your
SAS account representative.
194 Chapter 37 / SAS Enterprise Case Management
6.1, 6.1_M1, 6.2, 6.2_M2, 6.3 6.3_M1 (SAS 9.4) For more information about
(SAS 9.4) how to migrate to the latest
3.2_M1 (SAS 9.3) release of SAS Enterprise
Case Management, see SAS
Enterprise Case
Management: Administrator’s
Guide.
For more information about the new features and enhancements in each release,
contact your SAS account representative.
For the product documentation, see the product documentation page for SAS Enterprise
Case Management.
Note: The documentation for SAS Enterprise Case Management is available only to
customers who license this product.
195
38
SAS Enterprise GRC
39
SAS Enterprise Guide
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
6.1 (SAS 9.4) 6.1_M1 (SAS 1 Before you upgrade, see “SAS Enterprise Guide
9.4_M1); 7.1, 6.1_M1” on page 202 and “SAS Enterprise
7.11 (SAS Guide 7.1” on page 202 (if appropriate).
9.4_M2); 7.12
(SAS 9.4_M3) 2 To upgrade to the latest release of SAS
Enterprise Guide, see “Install and Configure a
Software Update” on page 69.
6.1_M1 (SAS 7.1, 7.11 (SAS 1 Before you upgrade, see “SAS Enterprise Guide
9.4_M1) 9.4_M2); 7.12 7.1” on page 202.
(SAS 9.4_M3)
2 To upgrade to the latest release of SAS
Enterprise Guide, see “Install and Configure a
Software Update” on page 69.
7.1, 7.11 (SAS 7.12 (SAS 1 Before you upgrade, see “SAS Enterprise Guide
9.4_M2) 9.4_M3) 7.1” on page 202.
2 To upgrade to the latest release of SAS
Enterprise Guide, see “Install and Configure a
Software Update” on page 69.
Determining Your Update Path for SAS Enterprise Guide 199
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
5.1, 4.3 (SAS 9.3) 6.1 (SAS 9.4); 1 Before you migrate, see “SAS Enterprise Guide
6.1_M1 (SAS 6.1” on page 200, “SAS Enterprise Guide
9.4_M1); 7.1, 6.1_M1” on page 202, and “SAS Enterprise
7.11 (SAS Guide 7.1” on page 202 (if appropriate).
9.4_M2); 7.12
(SAS 9.4_M3) 2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To create
a new deployment, see SAS 9.4 Intelligence
Platform: Installation and Configuration Guide.
3 To complete any post-configuration steps, see
SAS 9.4 Intelligence Platform: Desktop
Application Administration Guide.
6.1 (SAS 9.4), 7.1, 7.11 (SAS To migrate within the same SAS release, see SAS
6.1_M1 (SAS 9.4_M2); 7.12 9.4 Intelligence Platform: Migration Guide.
9.4_M1); 7.1, 7.11 (SAS 9.4_M3)
(SAS 9.4_M2)
7.12 (SAS 9.4_M3) 7.12 (SAS To migrate within the same release, see SAS 9.4
9.4_M3) Intelligence Platform: Migration Guide.
200 Chapter 39 / SAS Enterprise Guide
n Solutions.css
n Theme.css
n Tom.css
n Watercolor.css
The removal of these styles could affect the SAS Enterprise Guide user in either of
these ways:
n If your default style in SAS Enterprise Guide is set to one of the styles that were
removed, you will not see any styles when you open your results. The HTML
appears white, and the default for any SAS Report content defaults to sasweb. If you
rerun the SAS Enterprise Guide project, the style is reset to HtmlBlue.
n The code or SAS task that generates the results refers to a style that has been
removed. In this case, you must edit the code to refer to an existing style, or contact
SAS Technical Support to obtain a ZIP file that contains the removed styles.
n Beginning with SAS Enterprise Guide 4.3, external file references are stored as
relative paths. Use pathnames that are relative to the current location of the project
file instead of using a full path.
To use SAS Visual Analytics 6.4 with the first maintenance release for SAS Enterprise
Guide 6.1, you must apply a hot fix. For more information, see SAS Note 52813.
SAS Enterprise Guide 7.11 shipped in May 2015. This release included a new feature
that enables you to check for updates when you first open SAS Enterprise Guide or
while you are working in SAS Enterprise Guide. If an update is available, a message
appears. In the message dialog box, a link to support.sas.com is available where you
can learn more about the contents of the software update. To apply a software update,
you must close SAS Enterprise Guide. You can use this updates feature to upgrade
from the 7.11 release to the 7.12 release.
SAS Enterprise Guide 7.12 shipped in February 2016. Beginning with SAS Enterprise
Guide 7.12, the save functionality has been updated to include a new Save All option
(Ctrl + Shift + S). The default behavior of the save option (Ctrl + S) now saves the active
item in the project.
SAS Enterprise Guide 7.1 203
For more information about these releases, see the software product page for SAS
Enterprise Guide.
204 Chapter 39 / SAS Enterprise Guide
205
40
SAS Enterprise Miner
12.3 (SAS 9.4) 13.1 (SAS 9.4_M1), 1 Before you upgrade, see “SAS Enterprise
13.2 (SAS 9.4_M2), Miner 13.1” on page 208, “SAS Enterprise
14.1 (SAS 9.4_M3) Miner 13.2” on page 208, and “SAS
Enterprise Miner 14.1” on page 209 (if
appropriate).
2 To upgrade to the latest release of SAS
Enterprise Miner, see “Install and Configure a
Software Update” on page 69.
13.1 (SAS 9.4_M1) 13.2 (SAS 9.4_M2), 1 Before you upgrade, see on page 208 and
14.1 (SAS 9.4_M3) “SAS Enterprise Miner 14.1” on page 209 (if
appropriate).
2 To upgrade to the latest release of SAS
Enterprise Miner, see “Install and Configure a
Software Update” on page 69.
13.2 (SAS 9.4_M2) 14.1 (SAS 9.4_M3) 1 Before you upgrade, see “SAS Enterprise
Miner 14.1” on page 209.
2 To upgrade to the latest release of SAS
Enterprise Miner, see “Install and Configure a
Software Update” on page 69.
SAS Enterprise Miner 12.3 207
12.1, 12.1_M1 12.3 (SAS 9.4), 1 Before you migrate, see “SAS Enterprise
(SAS 9.3) 13.1 (SAS 9.4_M1), Miner 12.3” on page 207, “SAS Enterprise
13.2 (SAS 9.4_M2), Miner 13.1” on page 208 , and “SAS
14.1 (SAS 9.4_M3) Enterprise Miner 14.1” on page 209 (if
appropriate).
2 Follow the steps in SAS Enterprise Miner:
Administration and Configuration Guide (for
your release) to migrate from a previous
release or to create a new deployment.
12.3 (SAS 9.4), 12.3 (SAS 9.4), To migrate within the same SAS release, follow
13.1 (SAS 13.1 (SAS 9.4_M1), the steps in SAS Enterprise Miner Administration
9.4_M1), 13.2 13.2 (SAS 9.4_M2), and Configuration Guide (for your release).
(SAS 9.4_M2) 14.1 (SAS 9.4_M3)
14.1 (SAS 9.4_M3) 14.1 (SAS 9.4_M3) To migrate within the same release, follow the
steps in SAS Enterprise Miner 14.1:
Administration and Configuration Guide.
available, SAS Enterprise Miner is not available (even if other SAS applications are
available on other nodes in the cluster).
If you are upgrading from an earlier release of SAS Enterprise Miner, note these
changes:
n Beginning with SAS Enterprise Miner 12.1, SAS consolidated the version numbers
for the main analytical products. Before the consolidation, the most recent version
number for SAS Enterprise Miner was 7.1.
n Beginning with SAS Enterprise Miner 12.1, the SAS Analytics Platform server was
deprecated. The SAS Analytics Platform service is not used for any SAS 9.3 (or
later) products or solutions.
SAS Enterprise Miner 14.1 shipped in July 2015. This release supports PMML 4.2 and
includes a new High-Performance Bayesian Network node. For more information
about SAS Enterprise Miner 14.1, see the software product page for SAS Enterprise
Miner.
210 Chapter 40 / SAS Enterprise Miner
211
41
SAS Environment Manager
Environment Manager 2.3 and 2.4 run on the second maintenance release for SAS 9.4.
SAS Environment Manager 2.5 runs on the third maintenance release for SAS 9.4.
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
2.1 (SAS 9.4) 2.1 (SAS 1 Before you upgrade, see “SAS Environment
9.4_M1); 2.3 and Manager 2.1 (SAS 9.4_M1)” on page 214, “SAS
2.4 (SAS Environment Manager 2.3 and SAS Environment
9.4_M2); 2.5 Manager 2.4” on page 216, and “SAS
(SAS 9.4_M3) Environment Manager 2.5” on page 217 (if
appropriate).
2 To upgrade to the latest release, see “Install and
Configure a Software Update” on page 69.
2.1 (SAS 9.4_M1) 2.3 and 2.4 (SAS 1 Before you upgrade, see “SAS Environment
9.4_M2); 2.5 Manager 2.3 and SAS Environment Manager
(SAS 9.4_M3) 2.4” on page 216 and “SAS Environment
Manager 2.5” on page 217 (if appropriate).
2 To upgrade to the latest release, see “Install and
Configure a Software Update” on page 69.
2.3 or 2.4 (SAS 2.4 (SAS 1 Before you upgrade, see “SAS Environment
9.4_M2) 9.4_M2); 2.5 Manager 2.3 and SAS Environment Manager
(SAS 9.4_M3) 2.4” on page 216 and “SAS Environment
Manager 2.5” on page 217 (if appropriate).
2 To upgrade to the latest release, see “Install and
Configure a Software Update” on page 69.
About SAS Environment Manager 213
2.1 (SAS 9.4) 2.1 (SAS To migrate within the same SAS release, see SAS
9.4_M1); 2.3 9.4 Intelligence Platform: Migration Guide.
(SAS 9.4_M2);
2.4 (SAS
9.4_M2); 2.5
(SAS 9.4_M3)
resources, gather health and availability information, perform control actions, collect
usage information, and monitor logs.
For more information, see the SAS Environment Manager: User’s Guide.
Users in SAS Environment Manager are mapped to users that are created in SAS
metadata. During installation, three user groups are created in SAS metadata to contain
SAS Environment Manager users. Users that are members of these groups are mapped
to user definitions in SAS Environment Manager with corresponding roles. Here are the
user groups and their corresponding roles:
For example, users that are added to the group SAS_EV_Guest are added as users in
SAS Environment Manager under the Guest role when the users are synchronized.
When you install SAS Environment Manager 2.1, all existing SAS Environment
Manager user definitions are automatically added to the SAS_EV_Guest group in
metadata. After the existing users have been added to the SAS_EV_Guest group, use
SAS Management Console to modify the user definitions or assign the users to other
SAS_EV groups in metadata.
After you have defined new users in SAS metadata, sign on to SAS Environment
Manager. Select Manage Synchronize Users. User definitions are created for all
users that are defined in the three SAS_EV groups in metadata. Any SAS Environment
Manager users that are not associated with user definitions in metadata are deleted.
When you perform an upgrade in place and the release number for SAS Environment
Manager does not change, these backup folders are created in the SAS-
configuration-directory/sas/Levn/Web/SASEnvironmentManager
directory:
n agent-backup_date-time
n server-backup_date-time
When you perform an upgrade in place and the release number for SAS Environment
Manager changes, two folders are created on the server because the version number
for Hyperic is included in the name of the directory. For example, if you are upgrading
from SAS Environment Manager 2.1 to 2.3, the version of Hyperic changed between
these releases. As a result, you see these two folders in the SAS-configuration-
directory/Levn/Web/SASEnvironmentManager directory after the software
upgrade:
n server-5.0.0–EE
n server-5.8.0–EE
Any new plug-ins for SAS Environment Manager might be deployed to the original
directory (server-5.8.0–EE) rather than to the new location (server-5.8.0–EE).
For example, these JAR files might appear in the SAS-configuration-
directory/Levn/Web/SASEnvironmentManager/server-5.0.0–EE/hq-
server/webapp/ROOT/WEB-INF/hq-plugins/ directory:
n emi-framework-plugin.jar
SAS Environment Manager 2.5 217
n emi-reportcenter-plugin.jar
n emi-snapshot-plugin.jar
You might also have these new JAR files in the SAS-configuration-
directory/Levn/Web/SASEnvironmentManager/server-5.0.0–EE/hq-
server/webapp/ROOT/WEB-INF/hq-plugins/emi_framework/lib directory.
n sas.sasev.framework.common.jar
n sas.sasev.framework.plugins.common.jar
n sas.sasev.framework.plugins.impl.jar
In order for the new plug-ins to work in the latest release of SAS Environment Manager,
you must copy these files and directories to the new location (server-5.8.0–EE).
Then you should delete the old location (server-5.8.0–EE). You might need to
restart SAS Environment Manager to see the new plug-ins.
If you modified certain default locations or settings in the SAS Environment Manager
Service Architecture, you must manually change these settings in SAS Environment
Manager 2.5. Then you must run the ugipinit script. Here are some changes that you
must manually update:
n Content that you stored in metadata folders must be manually imported. The update
process backed up this information, so you must import the data from the backup
location.
n Changes that you made to the service architecture configuration were not saved.
You must apply these changes manually.
n LIBNAME statements that you changed in the service architecture autoexec files
must be manually entered. The old files were backed up, so you can use the files as
218 Chapter 41 / SAS Environment Manager
a reference for making the changes. However, you cannot use the old autoexec files
with the new version of the application.
If you used the SAS Grid Manager plug-in for SAS Environment Manager, the functions
of this plug-in have been replaced by a SAS Grid Manager module. For more
information, see Chapter 51, “SAS Grid Manager,” on page 247.
If you are upgrading from SAS Environment Manager 2.4 and you did not enable the
SAS Environment Manager Service Architecture, you can ignore the message about the
update failing.
For more information about this release, see the software product page for SAS
Environment Manager.
219
42
SAS Episode Analytics
2.1, 2.2 (SAS 9.4) 2.2, 3.1 (SAS 9.4) For information about the
new features and
enhancements in this
release, contact your SAS
account representative.
220 Chapter 42 / SAS Episode Analytics
2.1, 2.2, 3.1 (SAS 9.4) 2.2, 3.1 (SAS 9.4) To migrate within the same
release, see the
documentation for SAS
Episode Analytics.
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Episode Analytics.
Note: The documentation for SAS Episode Analytics is available only to customers who
license this product.
221
43
SAS/ETS
12.3 (SAS 9.4) 13.1 (SAS 1 Before you upgrade, see “About SAS/ETS” on
9.4_M1), 13.2 page 223.
(SAS 9.4_M2),
14.1 (SAS 2 To upgrade to the latest release of SAS/ETS,
9.4_M3) see “Install and Configure a Software Update”
on page 69.
13.1 (SAS 9.4_M1) 13.2 (SAS
9.4_M2), 14.1
(SAS 9.4_M3)
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.1 (SAS 9.3) 12.3 (SAS 9.4), 1 Before you upgrade, see “About SAS/ETS” on
9.3_M1, 9.3 13.1 (SAS page 223.
9.4_M1), 13.2
(SAS 9.4_M2), 2 Install and configure SAS 9.4.
14.1 (SAS
9.4_M3) To determine the steps for installing and configuring
SAS 9.4 at your site, see the following resources:
n QuickStart Guides in the SAS Install Center
n SAS Intelligence Platform: Installation and
Configuration Guide
For migration information, see the following
resources:
n SAS Intelligence Platform: Migration Guide
n the product documentation page for SAS/ETS
About SAS/ETS
SAS has shipped these releases of SAS/ETS:
n SAS/ETS 12.3 shipped in July 2013. This is essentially a maintenance release, with
the exception that high-performance procedures for use in single-machine mode
have been added.
n SAS/ETS 13.1 shipped in December 2013. For more information about the new
features and enhancements in SAS/ETS 13.1, see What’s New in SAS/ETS 13.1.
224 Chapter 43 / SAS/ETS
n SAS/ETS 13.2 shipped in August 2014. For more information about the new features
and enhancements in SAS/ETS 13.2, see What’s New in SAS/ETS 13.2.
n SAS/ETS 14.1 shipped in July 2015. For more information about the new features
and enhancements in SAS/ETS 14.1, see What’s New in SAS/ETS 14.1.
225
44
SAS Event Stream Processing
2.1, 2.2, 2.3 (SAS 4.1 (SAS For more information about how to upgrade to the
9.4) 9.4_M3) latest release, contact your SAS account
3.1 (SAS 9.4_M2), representative.
3.2 (SAS 9.4_M3)
226 Chapter 44 / SAS Event Stream Processing
2.1, 2.2, 2.3 (SAS 4.1 (SAS For more information about how to migrate to this
9.4) 9.4_M3) release, contact your SAS account representative.
3.1 (SAS 9.4_M2),
3.2 (SAS 9.4_M3)
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Event Stream Processing.
Note: The documentation for SAS Event Stream Processing is available only to
customers who license this product.
227
45
SAS Financial Management
5.4 (SAS 9.4) 5.5 (SAS 9.4) For more information about
how to upgrade to this
release, contact your SAS
account representative.
228 Chapter 45 / SAS Financial Management
5.4 (SAS 9.4) 5.5 (SAS 9.4) To migrate or create a new deployment, see SAS
5.3, 5.3_M1 (SAS Financial Management 5.5: Installation and
9.3) Configuration Guide
For more information about this release, contact your SAS account representative and
see the product documentation page for SAS Financial Management.
For more information about the new features and enhancements in this release, contact
your SAS account representative and see the product documentation page for SAS
Financial Management.
46
SAS Firmwide Risk for Solvency II
3.1 (SAS 9.4) 3.2 (SAS 9.4) For more information about
how to upgrade to this
release, contact your SAS
account representative.
232 Chapter 46 / SAS Firmwide Risk for Solvency II
3.1 (SAS 9.4) 3.2 (SAS 9.4) To migrate to the new release or to create a new
deployment, see SAS Infrastructure for Risk
Management: Administrator’s Guide.
For more information about the new features and enhancements in this release, contact
your SAS account representative and see the product documentation page for SAS
Firmwide Risk for Solvency II.
Note: The documentation for SAS Firmwide Risk for Solvency II is available only to
customers who license this product.
233
47
SAS Forecast Analyst Workbench
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
5.2, 5.2_M2 (SAS 5.2_M2, 5.3 For more information about how to upgrade to the
9.4) (SAS 9.4) latest release, see SAS Forecast Analyst
Workbench: Upgrade and Migration Guide.
234 Chapter 47 / SAS Forecast Analyst Workbench
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
5.1 (SAS 9.3) 5.2, 5.2_M2, 5.3 For more information about how to migrate to this
(SAS 9.4) release, see SAS Forecast Analyst Workbench:
Upgrade and Migration Guide.
5.2, 5.2_M2 (SAS 5.2_M2, 5.3
9.4) (SAS 9.4)
Depending on the license that your organization has, you can use the Collaboration
Planning Workbench module of the SAS Forecast Analyst Workbench.
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Forecast Analyst Workbench.
Note: The documentation for SAS Forecast Analyst Workbench is available only to
customers who license this product.
236 Chapter 47 / SAS Forecast Analyst Workbench
237
48
SAS Forecast Server
12.3 (SAS 9.4) 13.1 (SAS 1 Before you upgrade, see “About SAS Forecast
9.4_M1), 13.2 Server” on page 239.
(SAS 9.4_M2),
14.1 (SAS 9.4_M3) 2 To upgrade to the latest release of SAS
Forecast Server, see “Install and Configure a
Software Update” on page 69.
13.1 (SAS 9.4_M1) 13.2 (SAS
9.4_M2), 14.1
(SAS 9.4_M3)
12.1, 4.1 (SAS 9.3) 12.3 (SAS 9.4), 1 Before you migrate, see “About SAS Forecast
13.1 (SAS Server” on page 239.
9.4_M1), 13.2
(SAS 9.4_M2), 2 To migrate to the new release, see SAS
14.1 (SAS 9.4_M3) Forecast Server: Migration Guide (for your
release). To create a new deployment, see
SAS Forecast Server: Administrator’s Guide
(for the release at your site).
12.3 (SAS 9.4), 12.3 (SAS 9.4), To migrate within the same SAS release, see SAS
13.1 (SAS 13.1 (SAS Forecast Server: Migration Guide (for the release
9.4_M1), 13.2 9.4_M1), 13.2 at your site).
(SAS 9.4_M2) (SAS 9.4_M2),
14.1 (SAS 9.4_M3)
14.1 (SAS 9.4_M3) 14.1 (SAS 9.4_M3) To migrate within the same release, see SAS
Forecast Server 14.1: Migration Guide.
SAS Forecast Server 12.3 does not support clustering of the middle-tier servers.
Because middle-tier clustering is not supported, SAS Forecast Server runs on the
master node in the cluster. If the master node is not available, SAS Forecast Server is
not available (even if other SAS applications are available on other nodes in the
cluster).
If you are upgrading from an earlier release of SAS Forecast Server, note these
changes:
n Beginning with SAS Forecast Server 12.1, SAS consolidated the version numbers
for the main analytical products. Before the consolidation, the most recent version
number for SAS Forecast Server was 4.1.
n Beginning with SAS Forecast Server 4.1, the SAS Analytics Platform server was
deprecated. The SAS Analytics Platform service is not used for any SAS 9.3 (or
later) products or solutions.
SAS also shipped these releases:
n SAS Forecast Server 13.1 in December 2013. Support for middle-tier clustering was
added in this release.
n SAS Forecast Server 13.2 in August 2014.
n SAS Forecast Server 14.1 in July 2015. This release includes SAS Forecast Server
Client, a new web-based interface that you can use to segment and forecast your
data.
For more information about these releases, contact your SAS account representative
and see the software product page for SAS Forecast Server.
241
49
SAS Fraud Management
Release That
Current Release You Are
at Your Site Upgrading To High-Level Steps and Resources
4.1, 4.2, 4.2_M1 4.2, 4.2_M1, 4.3 For more information about how to upgrade to the
latest release, contact your SAS account
representative.
242 Chapter 49 / SAS Fraud Management
3.3, 3.3_M1 (SAS 4.1, 4.2, 4.2_M1, For more information, contact your SAS account
9.3) 4.3 (SAS 9.4) representative.
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Fraud Management.
Note: The documentation for SAS Fraud Management is available only to customers
who license this product.
243
50
SAS/GRAPH
9.3, 9.3_M2, 9.4, 9.4_M1, 9.4_M2, 1 Before you migrate, see “SAS/GRAPH 9.4”
9.3_M3 9.4_M3 on page 245, “SAS/GRAPH 9.4_M1” on
page 245, and “SAS/GRAPH 9.4_M2” on
page 246 (if appropriate).
2 Install and configure SAS 9.4.
SAS/GRAPH 9.4
For more information about SAS/GRAPH 9.4, see the software product page for
SAS/GRAPH.
SAS/GRAPH 9.4_M1
Starting in the first maintenance release for SAS 9.4, if you are using a hyphen in your
NAME= option, be aware that the hyphen ‘-’ is converted to an underscore. For catalog-
246 Chapter 50 / SAS/GRAPH
based output, the NAME= option enables you to specify a name for the GRSEG entry
and the graphics output filename, if generated.
Note: For more information about significant changes that occurred in SAS 9.4, see
“Base SAS 9.4” on page 93.
SAS/GRAPH 9.4_M2
Prior to the second maintenance release for SAS 9.4, if the NAME= option specifies a
value that is greater than eight characters and begins with a number, SAS prepends an
underscore to the graphics output filename. The GRSEG entry name continues to
prepend an underscore to the NAME= value that begins with a number.
Starting in the second maintenance release for SAS 9.4, when the NAME= value is
greater than eight characters and begins with a number, the graphics output filename is
the NAME= value specified and an underscore is no longer prepended. When the
NAME= value is eight characters or less, the graphics output filename continues to be
equivalent to the GRSEG entry name.
SAS/GRAPH 9.4_M3
SAS shipped the third maintenance release for SAS/GRAPH in July 2015. For more
information about SAS/GRAPH 9.4, see the software product page for SAS/GRAPH.
247
51
SAS Grid Manager
9.4, 9.4_M1, 9.4_M3 1 Before you upgrade, see “SAS Grid Manager
9.4_M2 9.4_M3” on page 248.
2 To upgrade to the latest release for SAS 9.4,
see “Install and Configure a Software Update”
on page 69.
248 Chapter 51 / SAS Grid Manager
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “SAS Grid Manager
9.3_M2 9.4_M2, 9.4_M3 9.4_M3” on page 248.
2 Install and configure SAS 9.4.
To remove the old plug-in, delete the GridManagerPlugin folder from the hqu
directory. A typical location is /Web/SASEnvironmentManager/server-5.8.0-
EE/hq-engine/hq-server/webapps/ROOT/hqu.
250 Chapter 51 / SAS Grid Manager
251
52
SAS High-Performance Analytics
Infrastructure
Upgrading to the latest version of the infrastructure requires upgrading SAS High-
Performance Analytics Environment. If you overwrite the software on the cluster (or
move the existing software and install in the same path), then the upgraded or migrated
SAS software runs without modification.
Depending on your current version, upgrading the SAS High-Performance Analytics
Environment can provide this functionality:
n Create a high-speed parallel connection that delivers data from your remote data
source to the SAS High-Performance Analytics Environment on the analytic cluster.
n Perform text analysis in SAS LASR Analytic Server with SAS Visual Analytics and to
run PROC HPTMINE and HPTMSCORE with SAS Text Miner.
If you choose to install the software in a different directory on the cluster, specify the
new path as follows:
n For SAS LASR Analytic Servers, see “Add a LASR Analytic Server” in SAS
Intelligence Platform: Data Administration Guide.
n For SAS High-Performance Risk, see “Change the SAS High-Performance Risk
Property Values” in SAS High-Performance Risk: Administrator’s Guide.
Note: The infrastructure documentation and the documents in the preceding list are
available only to customers who license these products.
SAS High-Performance Analytics Infrastructure 2.8 253
53
SAS High-Performance Risk
Release That
Current Release You Are
at Your Site Upgrading To High-Level Steps and Resources
3.1, 3.2, 3.2_M1, 3.6 For more information about how to upgrade to the
3.3, 3.4, 3.5 latest release, contact your SAS account
representative.
256 Chapter 53 / SAS High-Performance Risk
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
3.1, 3.2, 3.3, 3.4, 3.6 (SAS 9.4) For more information about how to migrate to this
3.5 (SAS 9.4) release, contact your SAS account representative.
54
SAS/IML
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.3 (SAS 9.4) 13.1 (SAS 1 Before you upgrade, see “About SAS/IML” on
9.4_M1), 13.2 page 261.
(SAS 9.4_M2),
14.1 (SAS 2 To upgrade to the latest release of SAS/IML, see
9.4_M3) “Install and Configure a Software Update” on
page 69.
13.1 (SAS 9.4_M1) 13.2 (SAS
9.4_M2), 14.1
(SAS 9.4_M3)
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.1 (SAS 9.3) 12.3 (SAS 9.4), 1 Before you migrate, see “About SAS/IML” on
9.3_M1, 9.3 13.1 (SAS page 261.
9.4_M1), 13.2
(SAS 9.4_M2), 2 Install and configure SAS 9.4.
14.1 (SAS
9.4_M3) To determine the steps for installing and configuring
SAS 9.4 at your site, see the following resources:
n QuickStart Guides in the SAS Install Center
n SAS Intelligence Platform: Installation and
Configuration Guide
For migration information, see the following
resources:
n SAS Intelligence Platform: Migration Guide
n the product documentation page for SAS/IML
About SAS/IML
SAS has shipped these releases of SAS/IML:
n SAS/IML 12.3 shipped in July 2013. This release is a maintenance release with no
new features.
n SAS/IML 13.1 shipped in December 2013. For more information about the new
features and enhancements in SAS/IML 13.1, see What’s New in SAS/IML 13.1.
262 Chapter 54 / SAS/IML
n SAS/IML 13.2 shipped in August 2014. For more information about the new features
and enhancements in SAS/IML 13.2, see What’s New in SAS/IML 13.2.
n SAS/IML 14.1 shipped in July 2015. For more information about the new features
and enhancements in SAS/IML 14.1, see What’s New in SAS/IML 14.1.
263
55
SAS Information Delivery Portal
4.4 (SAS 9.4) 4.4_M1 (SAS 1 To upgrade to the latest release of SAS
9.4_M1), 4.4_M2 Information Portal 4.4, see “Install and
(SAS 9.4_M2) Configure a Software Update” on page 69.
2 Complete any post-configuration steps. For
more information, see “Updating Favorites in
Your Web Browser” on page 267.
Determining Your Update Path for the SAS Information Delivery Portal 265
4.31, 4.31_M1, 4.4, 4.4_M1, 1 Before you migrate, see “SAS Information
4.31_M2 (SAS 9.3) 4.4_M2 (SAS 9.4) Delivery Portal 4.4” on page 266.
4.3 (SAS 9.2_M3) 2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To
create a new deployment, see SAS 9.4
Intelligence Platform: Installation and
Configuration Guide.
3 Complete any post-configuration steps in
“Updating Favorites in Your Web Browser” on
page 267 and SAS 9.4 Intelligence Platform:
Web Application Administration Guide.
4.2 (SAS 9.2) 4.4_M2 (SAS 9.4) 1 Before you upgrade, see “SAS Information
Delivery Portal 4.3” on page 266 and “SAS
Information Delivery Portal 4.4” on page 266.
2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To
create a new deployment, see SAS 9.4
Intelligence Platform: Installation and
Configuration Guide.
3 Complete any post-configuration steps in
“Updating Favorites in Your Web Browser” on
page 267 and SAS 9.4 Intelligence Platform:
Web Application Administration Guide.
4.4 (SAS 9.4) 4.4, 4.4_M1 (SAS To migrate within the same SAS release, follow
9.4) the steps in SAS 9.4 Intelligence Platform:
Migration Guide.
266 Chapter 55 / SAS Information Delivery Portal
4.4_M1 (SAS 9.4) 4.4_M1 (SAS 9.4) To migrate within the same release, follow the
steps in SAS 9.4 Intelligence Platform: Migration
Guide.
Note: Starting in SAS Information Delivery Portal 4.4 (which runs on SAS 9.4), data
explorations are no longer converted to reports during migration or promotion.
maintenance release for SAS Information Delivery Portal 4.4, which runs on the second
maintenance release for SAS 9.4.
If you are running SAS Information Delivery Portal 4.2, you must upgrade to SAS
Information Delivery Portal 4.3 before you upgrade to SAS Information Delivery Portal
4.4. If you upgrade from 4.2 to 4.4, your data explorations in SAS Web Report Studio
4.2 might not convert properly. For more information, see Chapter 90, “SAS Web Report
Studio,” on page 419.
When you upgrade to SAS Information Delivery Portal 4.3, you have these options:
n You can upgrade to the latest release of SAS 9.2. SAS Information Delivery Portal
4.3 runs on SAS 9.2.
To upgrade to the latest release of SAS 9.2, see Planning for Maintenance Releases
and Product Upgrades for SAS 9.2.
n You can upgrade to the latest release of SAS 9.3. SAS Information Delivery Portal
4.31 runs on SAS 9.3.
When you upgrade to SAS 9.3, you can migrate, or you can create a new
deployment. For specific steps, see SAS 9.3 Intelligence Platform: Migration Guide
(if you are migrating to the new release) or SAS 9.3 Intelligence Platform: Installation
and Configuration Guide (if you are creating a new deployment). For post-
configuration steps, see SAS 9.3 Intelligence Platform: Web Application
Administration Guide.
for the new release. You can also access the SAS Information Delivery Portal by using
this unresolved link: http://server:port/SASPortal.
269
56
SAS In-Database Technologies
9.4 9.4_M1, 9.4_M2, 1 Before you upgrade, see “SAS 9.4_M1 In-
9.4_M3 Database Technologies” on page 272, “SAS
9.4_M2 In-Database Technologies” on page 272,
and “SAS 9.4_M3 In-Database Technologies” on
page 272 (if appropriate).
2 To upgrade to the latest release of SAS 9.4 In-
Database Technologies, see “Install and
Configure a Software Update” on page 69.
9.4_M1 9.4_M2, 9.4_M3 1 Before you upgrade, see “SAS 9.4_M2 In-
Database Technologies” on page 272 and “SAS
9.4_M3 In-Database Technologies” on page 272
(if appropriate).
2 To upgrade to the latest release of SAS 9.4 In-
Database Technologies, see “Install and
Configure a Software Update” on page 69.
Release That
Current Release You Are
at Your Site Upgrading To High-Level Steps and Resources
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “SAS 9.4 In-Database
9.3_M2 9.4_M2, 9.4_M3 Technologies” on page 271, “SAS 9.4_M1 In-
Database Technologies” on page 272, “SAS
9.4_M2 In-Database Technologies” on page 272,
and “SAS 9.4_M3 In-Database Technologies” on
page 272 (if appropriate).
2 Install and configure SAS 9.4.
In-database scoring for Netezza has been enhanced by the addition of the SAS
Embedded Process. The SAS Embedded Process is a SAS server process that runs
within Netezza to read and write data.
272 Chapter 56 / SAS In-Database Technologies
Guide. The installation and configuration of the SAS Embedded Process for Teradata
has been improved and simplified. The in-database deployment package is delivered to
the client from the SAS Install Depot. The new process has a smaller client footprint and
a faster installation.
For more information about this release, see the product documentation page for SAS
In-Database Technology.
274 Chapter 56 / SAS In-Database Technologies
275
57
SAS Information Map Studio
4.4 (SAS 9.4) 4.4_M1 (SAS To upgrade to the latest release of SAS
9.4_M1), 4.4_M2 Information Map Studio, see “Install and
(SAS 9.4_M2) Configure a Software Update” on page 69.
4.31, 4.31_M1, 4.4, 4.4_M1, 4.4_M2 1 Before you migrate, see “SAS Information
4.31_M2 (SAS 9.3) (SAS 9.4) Map Studio 4.4” on page 278.
2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To
create a new deployment, see SAS 9.4
Intelligence Platform: Installation and
Configuration Guide.
3 Complete the post-configuration steps in
SAS 9.4 Intelligence Platform: Desktop
Applications Guide
4.2 (SAS 9.2, SAS 4.4_M2 (SAS 9.4) 1 Before you upgrade, see “SAS Information
9.2_M1, SAS Map Studio 4.31” on page 279 and “SAS
9.2_M2), 4.2_M2 Information Map Studio 4.4” on page 278.
(SAS 9.2_M3)
2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To
create a new deployment, see SAS 9.4
Intelligence Platform: Installation and
Configuration Guide.
3 Complete the post-configuration steps in
SAS 9.4 Intelligence Platform: Desktop
Applications Guide
4.4, 4.4_M1 (SAS 4.4, 4,4_M1, 4.4_M2 To migrate within the same SAS release, see
9.4) (SAS 9.4) SAS 9.4 Intelligence Platform: Migration Guide.
4.4_M2 (SAS 4.4_M2 (SAS To migrate within the same release, see SAS
9.4_M1) 9.4_M2) 9.4 Intelligence Platform: Migration Guide.
278 Chapter 57 / SAS Information Map Studio
n If you cannot find a stored process in SAS Information Map Studio, the Hide from
user option might have been specified for the stored process. This option is
available in SAS 9.3 and later.
If you are running SAS Information Map Studio 4.2, you must upgrade to SAS
Information Map Studio 4.2_M2 before you upgrade to SAS Information Map Studio 4.4.
If you upgrade from 4.2 to 4.4, your data explorations in SAS Web Report Studio 4.2
might not convert properly. For more information, see Chapter 90, “SAS Web Report
Studio,” on page 419.
When you upgrade to SAS Information Map Studio 4.31, you have these options:
n You can upgrade to the latest release of SAS 9.2. SAS Information Map Studio
4.2_M2 runs on the third maintenance release for SAS 9.2.
To upgrade to the latest release of SAS 9.2, see Planning for Maintenance Releases
and Product Upgrades for SAS 9.2.
n You can upgrade to the latest release of SAS 9.3. SAS Information Map Studio 4.31
runs on SAS 9.3.
When you upgrade to SAS 9.3, you can migrate, or you can create a new
deployment. For specific steps, see SAS 9.3 Intelligence Platform: Migration Guide
(if you are migrating to the new release) or SAS 9.3 Intelligence Platform: Installation
and Configuration Guide (if you are creating a new deployment). For post-
configuration steps, see SAS 9.3 Intelligence Platform: Web Application
Administration Guide.
280 Chapter 57 / SAS Information Map Studio
281
58
SAS Integration Technologies
9.4, 9.4_M1, 9.4_M1, 9.4_M2, 1 Before you upgrade, see “SAS 9.4_M1
9.4_M2 9.4_M3 Integration Technologies” on page 285 , “SAS
9.4_M2 Integration Technologies” on page
285, and “SAS 9.4_M3 Integration
Technologies” on page 285 (if appropriate).
2 To upgrade to the latest release of SAS 9.4
Integration Technologies, see “Install and
Configure a Software Update” on page 69.
Determining Your Update Path for SAS Integration Technologies 283
9.3, 9.3_M1, 9.4. 9.4_M1, 1 Before you migrate, see “SAS 9.4 Integration
9.3_M2 9.4_M2, 9.4_M3 Technologies” on page 284, “SAS 9.4_M1
Integration Technologies” on page 285, “SAS
9.4_M2 Integration Technologies” on page
285, and “SAS 9.4_M3 Integration
Technologies” on page 285 (if appropriate).
2 Install and configure SAS 9.4.
In SAS 9.3, new features were made available for stored processes. If your client does
not support the new stored process features, then you might need to make your stored
process compatible with 9.2. For more information about how to make stored processes
compatible with SAS 9.2, see the Help in SAS Management Console.
/parameters/ /outputParameters/
/streams/ /dataTargets/
/packages/ /packageEntries/
If you are upgrading from an earlier release, note that in SAS/IntrNet 9.3, SAS BI Web
Services for .NET was discontinued. SAS BI Web Services for Java supports .NET
versions of generated web services that are migrated from SAS 9.2 in a way that is
transparent for clients.
SAS 9.4_M3 Integration Technologies 285
For more information about this release, see the software product page for SAS
Integration Technologies.
287
59
SAS Intelligence Platform
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “SAS Intelligence
9.3_M2 9.4_M2, 9.4_M3 Platform 9.4_M1” on page 298, “SAS
Intelligence Platform 9.4_M2” on page 299,
and “SAS Intelligence Platform 9.4_M3” on
page 300 (if appropriate).
2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To
create a new deployment, see SAS 9.4
Intelligence Platform: Installation and
Configuration Guide.
9.4, 9.4_M1, 9.4, 9.4_M1, To migrate within the same SAS release, see
9.4_M2 9.4_M2, 9.4_M3 SAS Intelligence Platform: Installation and
Configuration Guide.
SAS 9.4 includes SAS Web Application Server. It is based on VMware vFabric tc
Server. The middle tier includes SAS Web Server, an HTTP server that is based on
VMware vFabric Web Server. The SAS deployment tools can install and configure these
servers automatically with the following features:
n horizontal and vertical clustering of SAS Web Application Server
290 Chapter 59 / SAS Intelligence Platform
The new SAS Environment Manager offers monitoring and management features for
these servers. For more information, see Chapter 41, “SAS Environment Manager,” on
page 211.
The SAS 9.4 middle tier includes JMS Broker for Java Message Services. A Cache
Locator is installed and configured on the middle-tier machine. The Cache Locator is
used by SAS Web Application Server to locate other SAS applications that use a
distributed data cache for sharing information.
The SAS Remote Services application is deprecated, and SAS Enterprise Business
Intelligence deployments do not use the server. The SAS Remote Services application
is included with the software for backward compatibility with custom applications that
rely on it.
The following table lists the products that do not support this clustering feature.
For more information, see SAS Intelligence Platform: Middle-Tier Administration Guide.
In the SAS 9.2 release, SAS Table Server was offered. In the SAS 9.3 release, SAS
Framework Data Server was offered. In SAS 9.2 and SAS 9.3, respectively, the SAS
SAS 9.4 Intelligence Platform System Administration 293
Table Server and SAS Framework Data Server could be replaced with a third-party
vendor database. Using a customer-selected database was popular for deployments
that included a SAS solution that required a database such as Oracle. The transactional
needs for the solution and the middle tier could be consolidated in one database and
avoided the need for additional administration of a data server offered by SAS.
SAS 9.4 includes SAS Web Infrastructure Platform Data Server. The data server is
based on PostgreSQL 9.1.9. Besides fulfilling the role of data store for middle-tier data,
it also stores transactional information for SAS Environment Manager. The EVManager
database instance that is used by SAS Environment Manager depends on the SAS
Web Infrastructure Platform Data Server to log performance data. This dependency
cannot be met by a third-party vendor database.
If you used a third-party vendor database for SAS 9.2 or SAS 9.3, the SharedServices
database instance can continue to use the third-party vendor database when updating
to SAS 9.4. However, you must use the SAS Web Infrastructure Platform Data Server
for the SAS Environment Manager database (the EVManager database instance).
Deployment Backup
The Deployment Backup and Recovery tool, which is new with SAS 9.4, provides an
integrated method for backing up and recovering your SAS content across multiple tiers
and machines. If this tool is configured, it automatically backs up the following
components on the SAS server tier, middle tier, and data tier:
n the metadata server repositories, the repository manager, and all of the files in the
metadata server’s configuration directory.
n the contents of the Data, SASEnvironment, and server configuration directories for
each server on the SAS server tier. (If symbolic links in these directories point to
other locations, the referenced locations are not backed up.)
n all databases that are managed by the SAS Web Infrastructure Platform Data
Server.
By default, the tool backs up these items automatically every Sunday at 1:00 a.m. All
components (except the metadata server) are backed up to the following path on their
respective host machines: SAS-configuration-directory/Levn/Backup/
Vault. By default, backups are retained there for 30 days.
294 Chapter 59 / SAS Intelligence Platform
For metadata server backups, the tool uses the metadata server backup utility and its
configured backup location and retention policy.
The Deployment Backup and Recovery tool also enables you to specify a central,
network-accessible vault location. A central vault is highly recommended for multiple-
machine deployments. For deployments that are not current with the second
maintenance release for SAS 9.4, a central vault is required if your middle-tier
environment includes a clustered SAS Content Server. If a central vault is specified, the
backups from each host machine are copied to the central vault following each backup
operation. By default, files are retained in the central vault for 30 days.
The Deployment Backup and Recovery tool includes batch scripts that you can use to
perform these tasks:
n execute an ad hoc (unscheduled) backup
n specify a different backup schedule, a different vault location, or additional
directories under SAS-configuration-directory/Levn that you want to back
up
n display information such as the current schedule, the current configuration, and
detailed backup history
n complete a full or partial recovery from one of the backups
If your deployment has a heterogeneous operating system environment, you can use
the Deployment Backup and Recovery Tool only if your deployment is current with the
first maintenance release for SAS 9.4. A heterogeneous environment is one in which
the host machines that are included in the backup are in different operating system
families (for example, both UNIX and Windows). The first maintenance release also
includes support for manually configuring a central vault location in heterogeneous
deployments.
For more information, see “Using the Deployment Backup and Recovery Tool” in SAS
Intelligence Platform: System Administration Guide.
SAS 9.4 Intelligence Platform System Administration 295
Environment Manager, you can view reports for metrics, such as health, availability, and
quorum status.
If your SAS 9.4 deployment includes a clustered metadata server, be aware of the
following special considerations:
n To start a clustered metadata server, use your preferred method (for example, the
server script, SAS Environment Manager, or Windows Service Manager) to start
each of the nodes in the cluster. The nodes can be started in any order.
n Make sure that all of the nodes are running before you start components that
depend on the metadata server.
n The Active Server Properties dialog box, which is available in the Metadata
Manager node of SAS Management Console, includes a new Cluster tab that
displays the overall status of the cluster. Individual nodes can be monitored in SAS
Environment Manager and in SAS Management Console Server Manager.
n The following administrative functions cannot be performed on a server that is
running with the cluster option:
o completing a metadata server recovery
o backing up the metadata server with the REORG option
o running the optimizeIMDB command option of the metadata server script
o running the Metadata Analyze and Repair tools
To perform one of these functions, use the startNoCluster option of the metadata
server script to start a single node without the clustering option. After performing the
function, restart (or stop and start) the node to place it in cluster mode as the master
node. Then start the other nodes in the cluster. The master node updates the other
nodes with the new data from the recovery, REORG, optimizeIMDB, or analyze and
repair operation.
n The logging facility creates a separate log for each node in the cluster. The logs are
stored on their respective host machines and are available for viewing in SAS
Management Console.
n Effective with the second maintenance release for SAS 9.4, metadata server
clustering is supported on z/OS. In previous SAS 9.4 releases, metadata server
SAS 9.4 Intelligence Platform System Administration 297
clustering is supported only on UNIX and Windows. All of the nodes in the cluster
must have the same operating system.
2 Upgrade the first node (that is, the initially configured metadata server). The node is
restarted automatically after the upgrade.
For more information, see “Using Metadata Server Clustering” in SAS Intelligence
Platform: System Administration Guide.
Deployment Backup
Effective with the first maintenance release for SAS 9.4, the Deployment Backup and
Recovery tool includes the following changes:
n The syntax has changed for the sas-backup and sas-list-backups commands.
n The input file specifications have changed for the following commands: sas-
backup, sas-set-backup-schedule, and sas-remove-backup-schedule.
n The sas-status-backup command can be used only to display the status of a
backup operation. It no longer reports the status of recoveries.
n An alert email is generated if a backup or recovery is unsuccessful. By default, the
email is sent to the system administrator email address that was specified in the
SAS Deployment Wizard.
n A new offline recovery command (sas-recover-offline) can restore files from
the deployment backup when some resources are unavailable or have been taken
offline.
n On UNIX machines, it is no longer necessary to list the backup user (typically, the
SAS Installer user) in the etc/sudoers file.
Deployment Backup
Effective with the second maintenance release for SAS 9.4, the Deployment Backup
and Recovery tool includes the following changes:
n If you have specified a central vault location, the local backups are deleted from
each host machine after they are successfully copied to the central vault. However,
metadata server backups are not deleted from the location that is used by the
metadata server backup utility.
n A central vault location is no longer required if your middle-tier environment includes
a clustered SAS Content Server.
n When you use sas-update-backup-config to specify a central vault location,
the location is automatically added to the BackupServer.ini file.
n The syntax has changed for sas-remove-backup-schedule and sas-remove-
backup-customdir. JSON files are no longer used with these commands.
n The input data specifications for sas-add-backup-customdir have changed.
300 Chapter 59 / SAS Intelligence Platform
The new SAS Backup Manager can be accessed from the Administration tab of SAS
Environment Manager. The SAS Backup Manager is an easy-to-use interface for
scheduling, configuring, monitoring, and performing integrated backups. The interface
SAS Intelligence Platform 9.4_M3 301
incorporates most of the functions of the Deployment Backup and Recovery tool’s batch
commands.
Deployment Backup
In the third maintenance release for SAS 9.4, the Deployment Backup and Recovery
tool includes these changes:
n The command sas-update-backup-config has a new syntax and new filtering
capabilities.
n The following commands have been deprecated: sas-display-backup-source-
config, sas-add-backup-customdir, sas-display-backup-customdir,
and sas-remove-backup-customdir. For equivalent functionality, use sas-
display-backup-config and sas-update-backup-config.
n Some of the labels in the input file for sas-recover-offline and sas-recover
have been changed.
Deprecated Features
SAS has deprecated support of the SAS Audit, Performance, and Management
package. The functionality provided by the package was integrated into SAS
Environment Manager 2.4.
302 Chapter 59 / SAS Intelligence Platform
303
60
SAS/IntrNet
Release That
Current Release You Are
at Your Site Migrating To High-Level Steps and Resources
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “SAS/IntrNet 9.4” on
9.3_M2 9.4_M2, 9.4_M3 page 305, “SAS/IntrNet 9.4_M1” on page 305,
“SAS/IntrNet 9.4_M2” on page 306, and
“SAS/IntrNet 9.4_M3” on page 306 (if
appropriate).
2 Install and configure SAS 9.4.
SAS/IntrNet 9.4
Beginning with SAS/IntrNet 9.3, the SAS/IntrNet Configuration Utility was 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.
SAS/IntrNet 9.4_M1
The first maintenance release for SAS/IntrNet 9.4 shipped in December 2013. For more
information about this release, see the product documentation page for SAS/IntrNet
Software.
306 Chapter 60 / SAS/IntrNet
SAS/IntrNet 9.4_M2
The second maintenance release for SAS/IntrNet 9.4 shipped in August 2014. In this
release, the default value for DebugMask has changed from 32767 to 0, which indicates
that all debug values are disabled. For more information about this release, see the
product documentation page for SAS/IntrNet Software.
SAS/IntrNet 9.4_M3
The third maintenance release for SAS/IntrNet 9.4 shipped in July 2015. For more
information about this release, see the product documentation page for SAS/IntrNet
Software.
307
61
SAS Inventory Optimization
Workbench
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
5.2, 5.2_M2 (SAS 5.2_M2, 5.3 For more information about how to upgrade to the
9.4) (SAS 9.4) latest release, see SAS Inventory Optimization
Workbench: Upgrade and Migration Guide.
308 Chapter 61 / SAS Inventory Optimization Workbench
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
5.1 (SAS 9.3) 5.2, 5.2_M2, 5.3 For more information about how to migrate to this
(SAS 9.4) release, see SAS Inventory Optimization
Workbench: Upgrade and Migration Guide.
5.2, 5.2_M2 (SAS 5.3 (SAS 9.4)
9.4)
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Inventory Optimization Workbench.
Note: The documentation for SAS Inventory Optimization Workbench is available only
to customers who license this product.
310 Chapter 61 / SAS Inventory Optimization Workbench
311
62
SAS IT Resource Management
3.4 (SAS 9.4_M1); 3.7 (SAS 9.4_M3) 1 Before you upgrade, see “About SAS IT
3.5 or 3.6 (SAS Resource Management” on page 312.
9.4_M2)
2 To upgrade to the latest release of SAS IT
Resource Management, see “Install and
Configure a Software Update” on page 69.
312 Chapter 62 / SAS IT Resource Management
You can migrate to the latest release of SAS 9.4, or you can create a new deployment.
3.3, 3.21 (SAS 9.3) 3.4 (SAS 9.4_M1); 1 Before you migrate, see What’s New in SAS
3.5 or 3.6 (SAS IT Resource Management.
9.4_M2); 3.7 (SAS
9.4_M3) 2 To migrate to the new release, see SAS IT
Resource Management : Migration Guide.
3.4 (SAS 9.4_M1); 3.7 (SAS 9.4_M3) To migrate to SAS IT Resource Management
3.5 or 3.6 (SAS 3.7, see SAS IT Resource Management 3.7:
9.4_M2) Migration Guide.
3.7 (SAS 9.4_M3) 3.7 (SAS 9.4_M3) To migrate within the same release, see SAS IT
Resource Management 3.7: Migration Guide.
To view the documentation for this product, see the product documentation page for
SAS IT Resource Management.
314 Chapter 62 / SAS IT Resource Management
315
63
SAS Lineage
64
SAS Management Console
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “SAS Management
9.3_M2 9.4_M2, 9.4_M3 Console 9.4” on page 319.
2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To
create a new deployment, see SAS 9.4
Intelligence Platform: Installation and
Configuration Guide.
9.4, 9.4_M1, 9.4, 9.4_M1, To migrate within the same SAS release, see
9.4_M2, 9.4_M3 9.4_M2, 9.4_M3 SAS Intelligence Platform: Installation and
Configuration Guide.
In SAS 9.3, new features were made available for stored processes. If your client does
not support the new stored process features, then you might need to make your stored
process compatible with 9.2. For more information about how to make stored processes
compatible with SAS 9.2, see the Help in SAS Management Console.
In SAS Management Console 9.3, the Backup Wizard and the Replication Wizard were
removed from the Metadata Manager plug-in. These wizards have been replaced by the
Server Backup and Restore facility, which is in the Metadata Utilities folder of the
Metadata Manager plug-in. If you have created or scheduled any backup or restore
jobs, these jobs will not run in SAS Management Console 9.4. You must use the Server
Backup and Restore facility to re-create those jobs.
SAS has shipped these releases of SAS Management Console:
n first maintenance release for SAS Management Console 9.4 in December 2013
n second maintenance release for SAS Management Console 9.4 in August 2014
n third maintenance release for SAS Management Console in July 2015
For more information about these releases, see the product documentation page for
SAS Management Console.
320 Chapter 64 / SAS Management Console
321
65
SAS Marketing Automation
6.3, 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 For more information about this release, contact
(SAS 9.4_M3) your SAS account representative.
322 Chapter 65 / SAS Marketing Automation
6.1, 5.41 (SAS 9.3) 6.3, 6.4 (SAS 9.4); For more information about how to request this
6.5 (SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
6.3, 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 To migrate to SAS Marketing Automation 6.4 or
(SAS 9.4_M3) 6.5, see SAS Marketing Automation: Migration
Guide.
6.5 (SAS 9.4_M3) 6.5 (SAS 9.4_M3) To migrate within the same release, see SAS
Marketing Automation: Migration Guide.
For more information, see the product documentation page for SAS Customer
Intelligence.
Note: The documentation for SAS Marketing Automation is available only to customers
who license this product.
324 Chapter 65 / SAS Marketing Automation
325
66
SAS Marketing Operations
Management
6.3 (SAS 9.4) 6.4 (SAS 9.4) For more information about how to upgrade to the
latest release, contact your SAS account
representative.
326 Chapter 66 / SAS Marketing Operations Management
6.0 (SAS 9.3) 6.3, 6.4 (SAS 9.4) For more information, contact your SAS account
representative.
6.3 (SAS 9.4) 6.4 (SAS 9.4)
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Marketing Operations Management.
Note: The documentation for SAS Marketing Operations Management is available only
to customers who license this product.
327
67
SAS Marketing Optimization
6.3, 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 For more information about this release, contact
(SAS 9.4_M3) your SAS account representative.
328 Chapter 67 / SAS Marketing Optimization
6.1, 5.41 (SAS 9.3) 6.3, 6.4 (SAS 9.4); For more information about how to request this
6.5 (SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
6.3, 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 To migrate to SAS Marketing Optimization 6.4 or
(SAS 9.4_M3) 6.5, see SAS Marketing Optimization: Migration
Guide.
6.5 (SAS 9.4_M3) 6.5 (SAS 9.4_M3) To migrate within the same SAS release, see SAS
Marketing Optimization: Migration Guide.
For more information, see the product documentation page for SAS Customer
Intelligence.
68
SAS MDM (Master Data Management)
4.1, 4.1_M1 (SAS 4.2 (SAS 9.4) For more information about this release, contact
9.4) your SAS account representative.
4.1, 4.1_M1 (SAS 4.2 (SAS 9.4) To migrate to SAS MDM 4.2, see SAS MDM:
9.4) Administrator’s Guide.
4.2 (SAS 9.4) 4.2 (SAS 9.4) To migrate within the same release, see SAS
MDM: Administrator’s Guide.
69
SAS Merchandise Intelligence
5.2 (SAS 9.4) 5.4 (SAS 9.4_M3) For more information about how to request this
new release and the features that are available,
contact your SAS account representative.
4.2 (SAS 9.3) 5.2 (SAS 9.4); 5.4 For more information about how to request this
(SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
5.2 (SAS 9.4) 5.4 (SAS 9.4_M3)
Additional Information
For more information about SAS Merchandise Intelligence, contact your SAS account
representative and see the product documentation page for SAS Merchandise
Intelligence.
70
SAS Micro Analytic Services
1.2 (SAS 9.4) 1.3 (SAS 9.4) For information about how to
upgrade to this release,
contact your SAS account
representative and see SAS
Micro Analytic Services:
Programming and
Administration Guide.
338 Chapter 70 / SAS Micro Analytic Services
1.2, 1.3 (SAS 9.4) 1.3 (SAS 9.4) To migrate within the same
release, see SAS Micro
Analytic Services:
Programming and
Administration Guide.
Note: Currently, SAS Micro Analytic Services is available with SAS Decision Manager.
For more information, see Chapter 33, “SAS Decision Manager,” on page 181.
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Micro Analytic Services.
339
71
SAS Model Manager
12.3 (SAS 9.4), 13.1 (SAS 1 Before you upgrade, see “SAS Model Manager
13.1 (SAS 9.4_M2) 9.4_M2), 14.1 13.1” on page 342 and “SAS Model Manager
(9.4_M3) 14.1” on page 343 (if appropriate).
2 To upgrade to the latest release of SAS Model
Manager, see “Install and Configure a Software
Update” on page 69.
3 Complete the post-upgrade steps in SAS
Model Manager: Administrator’s Guide.
12.1, 3.1, 3.1_M1 12.3 (SAS 9.4), 1 Before you migrate, see “SAS Model Manager
(SAS 9.3) 13.1 (SAS 12.3” on page 341, “SAS Model Manager
9.4_M2), 14.1 13.1” on page 342, and “SAS Model Manager
(SAS 9.4_M3) 14.1” on page 343 (if appropriate).
2 To migrate to the new release, see SAS Model
Manager: Migration Guide. To create a new
deployment, see SAS 9.4 Intelligence Platform:
Installation and Configuration Guide.
3 Complete the post-installation, configuration,
and verification steps in SAS Model Manager:
Administrator’s Guide.
12.3 (SAS 9.4), 13.1 (SAS To migrate to the latest release of SAS Model
13.1 (SAS 9.4_M2) 9.4_M2), Manager, see SAS Model Manager: Migration
14.1_SAS 9.4_M3) Guide.
SAS Model Manager 12.3 341
14.1 (SAS 9.4_M3) 14.1 (SAS 9.4_M3) To migrate within the same release, see SAS
Model Manager: Migration Guide.
In addition, SAS Model Manager 12.3 provides support for these areas:
n SAS Enterprise Miner Random Forest (HPFOREST) models, as well as the
SAS/ETS COUNTREG and SEVERITY models
n multiple SAS application servers when scoring or retraining a model, and monitoring
performance of champion and challenger models
342 Chapter 71 / SAS Model Manager
SAS Model Manager 12.3 does not support middle-tier clustering. As a result, SAS
Model Manager runs on the master node in the cluster. If the master node is not
available, SAS Model Manager is not available (even if other SAS applications are
available on other nodes in the cluster).
If you are upgrading from a previous release of SAS Model Manager, note these
changes:
n In the 12.1 release, additional pre-installation configuration tasks were added to
create and configure the new SAS Model Manager database, before the Software
Deployment Wizard is run. In SAS Model Manager 12.3, the default database type is
the Web Infrastructure Platform Data Server. SAS Model Manager also supports
third-party databases, including DB2, MySQL, Oracle, PostgreSQL, and SQL Server.
n SAS Model Manager 12.3 on SAS 9.4 no longer uses the multicast address and port
configuration.
n Beginning with the 12.1 release of SAS Model Manager, SAS consolidated the
version numbers for the main analytical products. Before the consolidation, the most
recent version number for SAS Model Manager was 3.1.
n Beginning with SAS Model Manager 3.1, the SAS Analytics Platform server was
deprecated.
If you are upgrading from a previous release of SAS Model Manager, note these
changes:
n When you upgrade from SAS Model Manager 12.3 to 13.1, you must complete
additional post-upgrade steps. For more information, see SAS Model Manager:
Administrator’s Guide.
n The web application URL has been changed to be consistent across the SAS
Enterprise Decision Management product offerings. The SAS Model Manager Java
Client application is no longer available from a user’s desktop or via the Java Web
Start URL.
For more information about the new features and enhancements in this release, see the
product documentation page for SAS Model Manager.
If you are upgrading from SAS Model Manager 12.3 or 13.1 to 14.1, you must complete
additional post-upgrade steps. For more information, see SAS Model Manager:
Administrator’s Guide.
345
72
SAS Model Risk Management
6.1 (SAS 9.4) 7.1 (SAS 9.4_M3) For more information about this release, contact
your SAS account representative.
346 Chapter 72 / SAS Model Risk Management
6.1 (SAS 9.4) 7.1 (SAS 9.4_M3) For more information about this release, contact
your SAS account representative.
7.1 (SAS 9.4_M3) 7.1 (SAS 9.4_M3) To migrate within the same release, see SAS
MDM: Administrator’s Guide.
73
SAS OLAP Server
9.4 9.4_M1, 9.4_M2, 1 Before you upgrade, see “SAS 9.4 OLAP
9.4_M3 Server” on page 349.
2 To upgrade to the latest release of SAS 9.4
OLAP Server, see “Install and Configure a
Software Update” on page 69.
348 Chapter 73 / SAS OLAP Server
9.4_M1 9.4_M2, 9.4_M3 1 Before you upgrade, see “SAS 9.4 OLAP
Server” on page 349.
2 To upgrade to the latest release of SAS 9.4
OLAP Server, see “Install and Configure a
Software Update” on page 69.
9.3, 9.3_M1, 9.4, 9.4_M1, 9.4_M2, 1 Before you migrate, see “SAS 9.4 OLAP
9.3_M2 9.4_M3 Server” on page 349.
2 Install and configure SAS 9.4.
9.4 9.4, 9.4_M1, 9.4_M2, To migrate within the same SAS release, see
9.4_M3 SAS Intelligence Platform: Migration Guide.
For information about the new features and enhancements in these releases, see the
product documentation for SAS OLAP Cube Studio and SAS OLAP Server.
350 Chapter 73 / SAS OLAP Server
351
74
SAS OpRisk VaR
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
6.1, 6.1_M1 (SAS 6.1_M2 (SAS For more information about how to upgrade to the
9.4) 9.4) latest release, contact your SAS account
representative.
352 Chapter 74 / SAS OpRisk VaR
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
5.1, 4.21 (SAS 9.3) 6.1, 6.1_M1, For more information about how to migrate to this
6.2_M2 (SAS release, contact your SAS account representative.
9.4)
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS OpRisk VaR.
Note: The documentation for SAS OpRisk VaR is available only to customers who
license this product.
353
75
SAS/OR
Release That
Current Release You Are
at Your Site Upgrading To High-Level Steps and Resources
12.3 (SAS 9.4) 13.1 (SAS 1 Before you upgrade, see “About SAS/OR” on
9.4_M1), 13.2 page 356.
(SAS 9.4_M2),
14.1 (SAS 2 To upgrade to the latest release of SAS/OR, see
9.4_M3) “Install and Configure a Software Update” on
page 69.
13.1 (SAS 9.4_M1) 13.2 (SAS
9.4_M2), 14.1
(SAS 9.4_M3)
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.1 (SAS 9.3) 12.3 (SAS 9.4), 1 Before you migrate, see “About SAS/OR” on
9.3, 9.3_M1 13.1 (SAS page 356.
9.4_M1), 13.2
(SAS 9.4_M2), 2 Install and configure SAS 9.4.
14.1 (SAS
9.4_M3) To determine the steps for installing and configuring
SAS 9.4 at your site, see the following resources:
n QuickStart Guides in the SAS Install Center
n SAS Intelligence Platform: Installation and
Configuration Guide
For migration information, see the following
resources:
n SAS Intelligence Platform: Migration Guide
n the product documentation page for SAS/OR
12.3 (SAS 9.4), 12.3 (SAS 9.4), To migrate within the same SAS release, see SAS
13.1 (SAS 13.1 (SAS Intelligence Platform: Migration Guide.
9.4_M1), 13.2 9.4_M1), 13.2
(SAS 9.4_M2) (SAS 9.4_M2),
14.1 (SAS
9.4_M3)
14.1 (SAS 9.4_M3) 14.1 (SAS To migrate within the same release, see SAS
9.4_M3) Intelligence Platform: Migration Guide.
356 Chapter 75 / SAS/OR
About SAS/OR
SAS has shipped these releases:
n SAS/OR 12.3 shipped in July 2013. This release is essentially a maintenance
release, with the exception that high-performance features for use in single-machine
mode have been added.
n SAS/OR 13.1 shipped in December 2013. For more information about the new
features and enhancements, see What’s New in SAS/OR 13.1.
n SAS/OR 13.2 shipped in August 2014. For more information about the new features
and enhancements, see What’s New in SAS/OR 13.2.
n SAS/OR 14.1 shipped in July 2015. For more information about the new features
and enhancements, see What’s New in SAS/OR 14.1.
357
76
SAS/QC
Release That
Current Release You Are
at Your Site Upgrading To High-Level Steps and Resources
12.3 (SAS 9.4) 13.1 (SAS 1 Before you upgrade, see “About SAS/QC” on
9.4_M1), 13.2 page 360.
(SAS 9.4_M2),
14.1 (SAS 2 To upgrade to the latest release of SAS/QC, see
9.4_M3) “Install and Configure a Software Update” on
page 69.
13.1 (SAS 9.4_M1) 13.2 (SAS
9.4_M2), 14.1
(SAS 9.4_M3)
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.1 (SAS 9.3) 12.3 (SAS 9.4), 1 Before you migrate, see “About SAS/QC” on
9.3, 9.3_M1 13.1 (SAS page 360.
9.4_M1), 13.2
(SAS 9.4_M2), 2 Install and configure SAS 9.4.
14.1 (SAS
9.4_M3) To determine the steps for installing and configuring
SAS 9.4 at your site, see the following resources:
n QuickStart Guides in the SAS Install Center
n SAS Intelligence Platform: Installation and
Configuration Guide
For migration information, see the following
resources:
n SAS Intelligence Platform: Migration Guide
n the product documentation page for SAS/QC
12.3 (SAS 9.4), 12.3 (SAS 9.4), To migrate within the same SAS release, see SAS
13.1 (SAS 13.1 (SAS Intelligence Platform: Migration Guide.
9.4_M1), 13.2 9.4_M1), 13.2
(SAS 9.4_M2) (SAS 9.4_M2),
14.1 (SAS
9.4_M3)
14.1 (SAS 9.4_M3) 14.1 (SAS To migrate within the same release, see SAS
9.4_M3) Intelligence Platform: Migration Guide.
360 Chapter 76 / SAS/QC
About SAS/QC
SAS has shipped these releases:
n SAS/QC 12.3 shipped in July 2013. This release runs on SAS 9.4 and is a
maintenance release with no new features.
n SAS/QC 13.1 shipped in December 2013. For more information about the new
features and enhancements, see What’s New in SAS/QC 13.1
n SAS/QC 13.2 shipped in August 2014. For more information about the new features
and enhancements, see What’s New in SAS/QC 13.2.
n SAS/QC 14.1 shipped in July 2015. For more information about the new features
and enhancements, see What’s New in SAS/QC 14.1.
361
77
SAS Real-Time Decision Manager
6.3. 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 For more information about this release, contact
(SAS 9.4_M3) your SAS account representative.
362 Chapter 77 / SAS Real-Time Decision Manager
6.1, 5.41 (SAS 9.3) 6.3, 6.4 (SAS 9.4); For more information about how to request this
6.5 (SAS 9.4_M3) new release and the features that are available,
contact your SAS account representative.
6.3, 6.4 (SAS 9.4) 6.4 (SAS 9.4); 6.5 To migrate to SAS Real-Time Decision Manager
(SAS 9.4_M3) 6.4 or 6.5, contact your SAS account
representative.
6.5 (SAS 9.4_M3) 6.5 (SAS 9.4_M3) To migrate within the same release, contact your
SAS account representative.
Note: SAS Real-Time Decision Manager Run-Time Server 6.4 and 6.5 run on SAS
9.4. If you are currently running SAS Real-Time Decision Manager Run-Time Server
6.4, contact your SAS account representative to upgrade to SAS Real-Time Decision
Manager Run-Time Server 6.5. Upgrading and migrating to from the 6.4 release to
the 6.5 release is not supported.
For more information, see the product documentation page for SAS Customer
Intelligence.
Note: The documentation for SAS Real-Time Decision Manager is available only to
customers who license this product.
364 Chapter 77 / SAS Real-Time Decision Manager
365
78
SAS Risk Dimensions
6.1, 6.2, 6.3, 6.4, 6.6 (SAS For more information about how to upgrade to the
6.5 (SAS 9.4) 9.4_M3) latest release, contact your SAS account
representative.
366 Chapter 78 / SAS Risk Dimensions
5.4, 5.5 (SAS 9.3); 6.6 (SAS For more information about how to migrate to this
6.1, 6.2, 6.3, 6.4, 9.4_M3) release, contact your SAS account representative.
6.5 (SAS 9.4)
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Risk Dimensions.
Note: The documentation for SAS Risk Dimensions is available only to customers who
license this product.
367
79
SAS Risk Management for Banking
3.2, 3.3 (SAS 9.4) 3.4 (SAS 9.4) For more information about how to upgrade to the
latest release, contact your SAS account
representative.
368 Chapter 79 / SAS Risk Management for Banking
3.2, 3.3 (SAS 9.4) 3.4 (SAS 9.4) For more information about how to migrate to this
release, contact your SAS account representative.
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Risk Management for Banking.
Note: The documentation for SAS Risk Management for Banking is available only to
customers who license this product.
369
80
SAS/SECURE
9.3, 9.3_M1, 9.4, 9.4_M1, 1 Before you migrate, see “SAS/SECURE 9.4”
9.3_M2 9.4_M2, 9.4_M3 on page 371, “SAS/SECURE 9.4_M1” on
page 372, “SAS/SECURE 9.4_M2” on page
372, and “SAS/SECURE 9.4_M3” on page
373 (if appropriate).
2 Install and configure SAS 9.4.
SAS/SECURE 9.4
For software delivery purposes, SAS/SECURE is a product within the SAS System. In
SAS 9.4, SAS/SECURE is included with the Base SAS software. In earlier releases,
SAS/SECURE was an add-on product that was licensed separately. This change makes
strong encryption available in all deployments (except where prohibited by import
372 Chapter 80 / SAS/SECURE
restrictions). For more information about import and export restrictions, see Encryption
in SAS.
SAS/SECURE is installed with the Base SAS software. However, the default encryption
is now SASProprietary. To use the higher form of encryption that is provided by
SAS/SECURE, specify the NETENCRYPT system option or set the NETENCRALG=
system option to a value of RC2, RC4, DES, TRIPLEDES, or AES.
SAS/SECURE 9.4_M1
When working with encryption in SAS, note these changes in the first maintenance
release for SAS 9.4.
n For TLS encryption, SAS sets the default location of the Certificate Authority (CA)
trust list to SAS-configuration-directory/levn/certs/cacert.pem for
UNIX and z/OS foundation servers. This default location is specified by the
SSLCALISTLOC= option in the configuration files.
n For TLS encryption on UNIX and z/OS foundation servers, the SSL_CERT_DIR and
SSLCACERTDIR environment variables can now be used to point to the location of
the site- and CA-signed certificates. Certificates can also be found at the location
pointed to by the SSLCALISTLOC= option.
SAS/SECURE 9.4_M2
The second maintenance release for SAS/SECURE 9.4 shipped in August 2014.
SAS provides the libraries needed to run TLS on UNIX. To find the OpenSSL code base
version that is used to build the TLS libraries provided by SAS for each release, see
“Mapping Between SAS Version and OpenSSL Version” on the product documentation
page for SAS/SECURE.
SAS/SECURE 9.4_M3 373
SAS/SECURE 9.4_M3
In the third maintenance release for SAS 9.4, the SAS Deployment Wizard automates
the process of updating the TLS certificates in UNIX and z/OS environments and for
Java applications on Windows and UNIX. In UNIX and z/OS environments, the
installation process lays down a Mozilla bundle of trusted CA certificates. The
installation also includes the files that are used as the trusted list of certificates. In UNIX
environments, trusted certificates are now located in the trusted CA bundle in SAS-
installation-directory/SASSecurityCertificateFramework/1.1/
cacerts/trustedcerts.pem. During installation, the SAS Deployment Wizard sets
the SSLCALISTLOC system option in the SAS-installation-directory/
sasv9.cfg file to point to the trustedcerts.pem file.
SAS provides the libraries needed to run TLS on UNIX. To find the OpenSSL code base
version that is used to build the TLS libraries provided by SAS for each release, see
“Mapping Between SAS Version and OpenSSL Version” on the product documentation
page for SAS/SECURE.
374 Chapter 80 / SAS/SECURE
375
81
SAS Social Network Analysis Server
6.2, 6.2_M1, 6.2_M2 (SAS 6.2_M3 (SAS 9.4) For more information about
9.4) how to request this new
release and the features that
are available, contact your
SAS account representative.
376 Chapter 81 / SAS Social Network Analysis Server
6.2, 6.2_M1, 6.2_M2 (SAS 6.2_M3 (SAS 9.4) For more information about
9.4) how to migrate to the latest
3.1_M1 (SAS 9.3) release of SAS Social
Network Analysis Server, see
SAS Social Network Analysis
Server: Administration Guide.
For more information about these releases, contact your SAS account representative
and see the product documentation page for SAS Social Network Analysis Server.
Note: The documentation for SAS Social Network Analysis Server is available only to
customers who license this product.
377
82
SAS/STAT
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.3 (SAS 9.4) 13.1 (SAS 1 Before you upgrade, see “About SAS/STAT” on
9.4_M1), 13.2 page 380.
(SAS 9.4_M2),
14.1 (SAS 2 To upgrade to the latest release of SAS/STAT,
9.4_M3) see “Install and Configure a Software Update”
on page 69.
13.1 (SAS 9.4_M1) 13.2 (SAS
9.4_M2), 14.1
(SAS 9.4_M3)
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.1 (SAS 9.3) 12.3 (SAS 9.4) 1 Before you migrate, see “About SAS/STAT” on
9.3, 9.3_M1 13.1 (SAS page 380.
9.4_M1), 13.2
(SAS 9.4_M2), 2 Install and configure SAS 9.4.
14.1 (SAS
9.4_M3) To determine the steps for installing and configuring
SAS 9.4 at your site, see the following resources:
n QuickStart Guides in the SAS Install Center
n SAS Intelligence Platform: Installation and
Configuration Guide
For migration information, see the following
resources:
n SAS Intelligence Platform: Migration Guide
n the product documentation page for SAS/STAT
12.3 (SAS 9.4), 12.3 (SAS 9.4), To migrate within the same SAS release, see SAS
13.1 (SAS 13.1 (SAS Intelligence Platform: Migration Guide.
9.4_M1), 13.2 9.4_M1), 13.2
(SAS 9.4_M2) (SAS 9.4_M2),
14.1 (SAS
9.4_M3)
14.1 (SAS 9.4_M3) 14.1 (SAS To migrate within the same release, see SAS
9.4_M3) Intelligence Platform: Migration Guide.
380 Chapter 82 / SAS/STAT
About SAS/STAT
SAS has shipped these releases:
n SAS/STAT 12.3 shipped in July 2013. This release is essentially a maintenance
release, with the exception that high-performance procedures for use in single-
machine mode have been added.
n SAS/STAT 13.1 shipped in December 2013. For more information about the new
features and enhancements, see What’s New in SAS/STAT 13.1.
n SAS/STAT 13.2 shipped in August 2014. For more information about the new
features and enhancements, see What’s New in SAS/STAT 13.2.
n SAS/STAT 14.1 shipped in July 2015. For more information about the new features
and enhancements, see What’s New in SAS/STAT 14.1.
381
83
SAS Studio
connects to a SAS server to process the SAS code. The SAS server can be a hosted
server in a cloud environment, a server in your local environment, or a copy of SAS on
your local machine. After the code is processed, the results are returned to SAS Studio
in your browser.
SAS Studio supports multiple web browsers, such as Microsoft Internet Explorer, Apple
Safari, Mozilla Firefox, and Google Chrome.
In addition to writing and running your own SAS programs, you can use the predefined
tasks that are included with SAS Studio to analyze your data. The tasks are based on
SAS System procedures and provide access to some of the most commonly used graph
and analytical procedures. You can also use the default task template to write your own
tasks.
To add SAS Studio – Single User or SAS Studio Basic, see the installation and
configuration steps in SAS Studio: Administrator’s Guide on the SAS Studio product
documentation page.
Determining Your Update Path for SAS Studio 383
3.1 (SAS 9.4) 3.1_M1, 3.2, 3.3, 1 Before you upgrade, see “SAS Studio 3.1_M1”
3.4, 3.5 (SAS 9.4) on page 384, “SAS Studio 3.2” on page 384,
“SAS Studio 3.3” on page 385 , and “SAS
Studio 3.4” on page 385 (if appropriate).
2 To upgrade to the latest release of SAS
Studio, see “Install and Configure a Software
Update” on page 69.
3.2 (SAS 9.4) 3.3, 3.4, 3.5 (SAS 1 Before you upgrade, see “SAS Studio 3.3” on
9.4) page 385 and “SAS Studio 3.4” on page 385
(if appropriate).
2 To upgrade to the latest release of SAS
Studio, see “Install and Configure a Software
Update” on page 69.
3.1, 3.2, 3.3, 3.4, 3.5 (SAS 3.1, 3.2, 3.3, 3.4, 3.5 (SAS To migrate within the same
9.4) 9.4) SAS release, see SAS
Intelligence Platform:
Migration Guide.
Note: If you specified a sudo password in your initial deployment of SAS Studio, this
password is not saved. After the software update, you might need to rerun the
setup.sh file to reconfigure SAS Studio and to provide the sudo password.
In SAS Studio 3.1, the tasks used Apache Velocity 1.5. In SAS Studio 3.2, the tasks use
Apache Velocity 1.7. This change affects these three graph tasks: Bar Chart, Scatter
Plot, and Series Plot. If you save one of these tasks as a CTK file or in your My Tasks
folder in SAS Studio 3.1 and then try to run the task in SAS Studio 3.2, the generated
SAS Studio 3.4 385
SAS code is incorrect. To work around this issue, remove any CTK files or tasks in your
My Tasks folder that use the Bar Chart, Scatter Plot, and Series Plot tasks. Then re-
create these CTK files or tasks in your My Tasks folder in SAS Studio 3.2.
For more information about this release, see the product documentation page for SAS
Studio.
Starting in SAS Studio 3.3, these files are saved in a common directory
called .sasstudio. When you install SAS Studio 3.3, any customized files from SAS
Studio 3.1 or 3.2 are copied to the .sasstudio directory. If you make additional
changes in SAS Studio 3.1 or 3.2, these changes are not saved in the SAS Studio 3.3
files. When you are finished working with SAS Studio 3.1 or 3.2, delete
any .mysnippets, .mypreferences, and so on, directories.
Starting in SAS Studio 3.3, each connection of SAS Studio creates two SAS processes.
Each process has its own Work directory. One process is for the execution of code, and
the other process is dedicated to file I/O. These processes are not delayed or blocked
by the execution of other processes.
If you are migrating from SAS Studio 3.3 in a Windows operating environment, any data
that is not saved in your My Documents folder is not available in SAS Studio 3.4. You
must manually move this data from SAS Studio 3.3 to SAS Studio 3.4.
For more information about this release, see the product documentation page for SAS
Studio.
387
84
SAS Task Manager
2.1, 2.1_M1 (SAS 2.2 (SAS 9.4) For more information about this release, contact
9.4) your SAS account representative.
2.1, 2.1_M1 (SAS 2.2 (SAS 9.4) To migrate to SAS Task Manager 2.2, see SAS
9.4) MDM: Administrator’s Guide.
2.2 (SAS 9.4) 2.2 (SAS 9.4) To migrate within the same release, see SAS
MDM: Administrator’s Guide.
85
SAS Text Miner
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.3 (SAS 9.4) 13.1 (SAS 1 Before you upgrade, see “SAS Text Miner 13.1”
9.4_M1), 13.2 on page 392, “SAS Text Miner 13.2” on page
(SAS 9.4_M2), 392, and “SAS Text Miner 14.1” on page 393 (if
14.1 (SAS appropriate).
9.4_M3)
2 When you install and configure SAS Enterprise
Miner, you can also install and configure SAS
Text Miner. For more information, see SAS
Enterprise Miner: Administration and
Configuration Guide.
13.1 (SAS 9.4_M1) 13.2 (SAS 1 Before you upgrade, see “SAS Text Miner 13.2”
9.4_M2), 14.1 on page 392 and “SAS Text Miner 14.1” on
(SAS 9.4_M3) page 393 (if appropriate).
2 When you install and configure SAS Enterprise
Miner, you can also install and configure SAS
Text Miner. For more information, see SAS
Enterprise Miner: Administration and
Configuration Guide.
13.2 (SAS 9.4_M2) 14.1 (SAS 1 Before you upgrade, see “SAS Text Miner 14.1”
9.4_M3) on page 393.
2 When you install and configure SAS Enterprise
Miner, you can also install and configure SAS
Text Miner. For more information, see SAS
Enterprise Miner: Administration and
Configuration Guide.
Determining Your Update Path for SAS Text Miner 391
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
12.1, 12.1_M1 12.3 (SAS 9.4) 1 Before you migrate, see “SAS Text Miner 12.3”
(SAS 9.3) 13.1 (SAS on page 392, “SAS Text Miner 13.1” on page
5.1_M1 (SAS 9.3) 9.4_M1), 13.2 392, “SAS Text Miner 13.2” on page 392, and
(SAS 9.4_M2), “SAS Text Miner 14.1” on page 393 (if
14.1 (SAS appropriate).
9.4_M3)
2 When you install and configure SAS Enterprise
Miner, you can also install and configure SAS
Text Miner. For more information, see SAS
Enterprise Miner: Administration and
Configuration Guide.
12.3 (SAS 9.4), 12.3 (SAS 9.4) 1 Before you migrate, see “SAS Text Miner 13.1”
13.1 (SAS 13.1 (SAS on page 392, “SAS Text Miner 13.2” on page
9.4_M1), 13.2 9.4_M1), 13.2 392 , and “SAS Text Miner 14.1” on page 393 (if
(SAS 9.4_M2) (SAS 9.4_M2), appropriate).
14.1 (SAS
9.4_M3) 2 To migrate within the same SAS release, see
SAS Enterprise Miner: Administration and
Configuration Guide.
14.1 (SAS 9.4_M3) 14.1 (SAS To migrate within the same release, see SAS
9.4_M3) Enterprise Miner 14.1: Administration and
Configuration Guide.
392 Chapter 85 / SAS Text Miner
If you are upgrading from a previous release of SAS Text Miner, note these changes:
n SAS Document Conversion Server is automatically installed when you upgrade SAS
Text Miner.
n Beginning with SAS Text Miner 12.1, SAS consolidated the version numbers for the
main analytical products. Before the consolidation, the most recent version number
for SAS Text Miner was 5.1.
n Beginning with SAS Text Miner 5.1, the Text Miner node that was available in
previous releases of SAS Text Miner was replaced by the functionality in other SAS
Text Miner nodes. Also, the DOCPARSE procedure was replaced by the TGPARSE
procedure. If you currently use the DOCPARSE procedure, modify your code to use
the TGPARSE procedure.
If you are upgrading from a previous release of SAS Text Miner, note these changes:
n A new HPBOOLRULE procedure replaces macros in the Text Rule Builder node.
For more information about the benefits of running the Text Rule Builder node with
the HPBOOLRULE procedure and how you can specify to run the Text Rule Builder
node as it functioned prior to SAS Text Miner 14.1, see the documentation for SAS
Text Miner.
n The TGPARSE procedure has been replaced with the HPTMINE procedure in the
Text Parsing node when the parsing language is Chinese, Dutch, English, Finnish,
French, German, Italian, Japanese, Korean, Portuguese, Russian, Spanish, or
Turkish. For these languages, parsing is now multithreaded. The TGPARSE
procedure continues to be called when the parsing language is Arabic, Czech,
Danish, Greek, Hebrew, Hungarian, Indonesian, Norwegian, Polish, Romanian,
Slovak, Swedish, Thai, or Vietnamese.
For more information about the new features and enhancements in SAS Text Miner
14.1, see the software product page for SAS Text Miner.
394 Chapter 85 / SAS Text Miner
395
86
SAS Visual Analytics
6.2 (SAS 9.4) 6.3 (SAS 9.4_M1); 1 Before you upgrade, see “SAS Visual
6.4 (SAS 9.4_M1 Analytics 6.3” on page 401, “SAS Visual
and SAS 9.4_M2),; Analytics 6.4” on page 403, “SAS Visual
7.1, 7.2 (SAS Analytics 7.1” on page 404, “SAS Visual
9.4_M2); 7.3 (SAS Analytics 7.2” on page 407, and “SAS Visual
9.4_M3) Analytics 7.3” on page 410 (if appropriate).
2 To upgrade to the latest release of SAS Visual
Analytics, see SAS Visual Analytics:
Installation and Configuration Guide.
Determining Your Update Path for SAS Visual Analytics 397
6.3 (SAS 9.4_M1) 6.4 (SAS 9.4_M1 1 Before you upgrade, see “SAS Visual
and SAS 9.4_M2); Analytics 6.4” on page 403, “SAS Visual
7.1, 7.2 (SAS Analytics 7.1” on page 404, “SAS Visual
9.4_M2); 7.3 (SAS Analytics 7.2” on page 407, and “SAS Visual
9.4_M3) Analytics 7.3” on page 410 (if appropriate).
2 To upgrade to the latest release of SAS Visual
Analytics, see SAS Visual Analytics:
Installation and Configuration Guide.
6.4 (SAS 9.4_M2) 7.1, 7.2 (SAS 1 Before you upgrade, see “SAS Visual
9.4_M2); 7.3 (SAS Analytics 7.1” on page 404, “SAS Visual
9.4_M3) Analytics 7.2” on page 407, and “SAS Visual
Analytics 7.3” on page 410 (if appropriate).
2 To upgrade to the latest release of SAS Visual
Analytics, see SAS Visual Analytics:
Installation and Configuration Guide.
7.1 (SAS 9.4_M2) 7.2 (SAS 9.4_M2); 1 Before you upgrade, see “SAS Visual
7.3 (SAS 9.4_M3) Analytics 7.2” on page 407 and “SAS Visual
Analytics 7.3” on page 410 (if appropriate).
2 To upgrade to the latest release of SAS Visual
Analytics, see SAS Visual Analytics:
Installation and Configuration Guide.
7.2 (SAS 9.4_M2) 7.3 (SAS 9.4_M3) 1 Before you upgrade, see “SAS Visual
Analytics 7.3” on page 410.
2 To upgrade to the latest release of SAS Visual
Analytics, see SAS Visual Analytics:
Installation and Configuration Guide.
398 Chapter 86 / SAS Visual Analytics
6.1 (SAS 9.3) 6.2 (SAS 9.4); 6.3 1 Before you migrate, see “SAS Visual Analytics
(SAS 9.4_M1); 6.4 6.2” on page 399, “SAS Visual Analytics 6.3”
(SAS 9.4_M1 and on page 401, “SAS Visual Analytics 6.4” on
SAS 9.4_M2); 7.1, page 403, “SAS Visual Analytics 7.1” on page
7.2 (SAS 9.4_M2); 404, “SAS Visual Analytics 7.2” on page 407,
7.3 (SAS 9.4_M3_ and “SAS Visual Analytics 7.3” on page 410
(if appropriate).
2 To migrate or create a new deployment, see
SAS Visual Analytics: Installation and
Configuration Guide.
6.2 (SAS 9.4) 6.2 (SAS 9.4); 6.3 1 Before you migrate, see “SAS Visual Analytics
(SAS 9.4_M1); 6.4 6.3” on page 401, “SAS Visual Analytics 6.4”
(SAS 9.4_M1 and on page 403, “SAS Visual Analytics 7.1” on
SAS 9.4_M2); 7.1, page 404, “SAS Visual Analytics 7.2” on page
7.2 (SAS 9.4_M2); 407, and “SAS Visual Analytics 7.3” on page
7.3 (SAS 9.4_M3) 410 (if appropriate).
2 To migrate or create a new deployment , see
SAS Visual Analytics: Installation and
Configuration Guide.
6.3 (SAS 9.4_M1 6.3 (SAS 9.4_M1); 1 Before you migrate, see “SAS Visual Analytics
and SAS 9.4_M2) 6.4 (SAS 9.4_M1 6.4” on page 403, “SAS Visual Analytics 7.1”
and SAS 9.4_M2); on page 404, “SAS Visual Analytics 7.2” on
7.1, 7.2 (SAS page 407, and “SAS Visual Analytics 7.3” on
9.4_M2); 7.3 (SAS page 410 (if appropriate).
9.4_M3)
2 To migrate or create a new deployment, see
SAS Visual Analytics: Installation and
Configuration Guide.
SAS Visual Analytics 6.2 399
6.4 (SAS 9.4_M1) 6.4 (SAS 9.4_M2); 1 Before you migrate, see “SAS Visual Analytics
7.1, 7.2 (SAS 6.4” on page 403, “SAS Visual Analytics 7.1”
9.4_M2); 7.3 (SAS on page 404, “SAS Visual Analytics 7.2” on
9.4_M3) page 407, and “SAS Visual Analytics 7.3” on
page 410 (if appropriate).
2 To migrate or create a new deployment, see
SAS Visual Analytics: Installation and
Configuration Guide.
7.1, 7.2 (SAS 7.3 (SAS 9.4_M3) 1 Before you migrate, see “SAS Visual Analytics
9.4_M2) 7.3” on page 410.
2 To migrate or create a new deployment, see
SAS Visual Analytics: Installation and
Configuration Guide.
7.3 (SAS 9.4_M3) 7.3 (SAS 9.4_M3) To migrate within the same release, see SAS
Visual Analytics: Installation and Configuration
Guide.
reports that were created in SAS Visual Analytics 6.1 retain the dark report theme.
The new report themes have some differences from the previous releases. For
example, table and graph titles are no longer bold, and the thickness of some lines
has increased.
n Beginning with SAS Visual Analytics 6.2, lists of data items in SAS Visual Analytics
Designer are sorted based on the data set locale. For example, if you view Chinese
data in a browser with an English locale, then the data items are sorted based on the
data set’s Chinese locale.
n Beginning with SAS Visual Analytics 6.2, two map report objects are available in
SAS Visual Analytics Designer. The report object known as a geo map in previous
releases is now called a geo bubble map. The name was changed to distinguish it
from the new geo region map.
To complete your upgrade, perform these steps on any tier where a SAS Application
Server (with a SAS Workspace Server) is installed:
4 From the list of products, select the SAS Foundation check box.
5 Select the Advanced Programming for SAS LASR Analytic Server check box.
Note: If you need to click Retry when using the SAS Deployment Manager, you
might see this error message: Failed to update service database:
VDBService. You can ignore this error. It is generated because the SAS
Deployment Manager attempts to modify a configuration table a second time.
In the metadata, requirements for the Delete permission are replaced by requirements
for the Write permission.
Starting in SAS Visual Analytics 7.1, the range for recent items is a minimum of zero
and a maximum of 25 items. The default is 10 items.
Changes in Administration
n On the LASR Tables and LASR Servers tabs:
406 Chapter 86 / SAS Visual Analytics
o Most of the tab toolbar icons affect only those objects that have a selected
(checked) check box.
o Clicking on the cell next to a check box changes the check box’s state.
o The icon for the Get Status action is .
n The Administer permission affects the ability to set a server’s tables limit in the
administrator. (The ReadMetadata and WriteMetadata permissions are also
required.)
n The VA.EP.Capable.* extended attributes no longer have any effect. (In the 6.4
release, these extended attributes were used by administrators to explicitly specify
whether to attempt parallel loads. In the current release, explicit specification is
replaced by automatic detection.)
n SAS Mobile BI 7.1 has a new user interface. The new interface does not include a
banner. For this reason, support for the configuration properties that customize the
banner in the native mobile viewers is discontinued.
n From SAS Office Analytics 7.1, authentication to SAS Visual Analytics no longer
uses SAS Visual Analytics Transport Service. For this reason, actions and
information on the Mobile Devices tab in the administrator have no impact on SAS
Enterprise Guide, SAS Add-in for Microsoft Office, and SAS Web Parts for
SharePoint.
n The log4j configuration files for the explorer, designer, and web viewer are modified
as follows:
o Each record in the generated logs includes the application name and identifies
the connected user.
o An APM (SAS Audit, Performance, and Measurement package) log4j
configuration file is provided for future use with SAS Environment Manager. Do
not modify the log4j configuration files that have an _apm suffix.
o For the SAS_LASR_COMMANDS_FILE appender, generated log files include
LASRActions in their filenames, and loggers are based on a daily rolling file
appender.
SAS Visual Analytics 7.2 407
n The following predefined directory name no longer includes a version number: SAS-
configuration-directory/Applications/VisualAnalytics.
Note: The Modern appearance does not support right-to-left (RTL) languages. To
force the use of the appearance that supports RTL languages, specify a value of
classic for the configuration property home.ui.mode. The property is on the Visual
Analytics Hub node in the Configuration Manager in SAS Management Console.
For more information, see the SAS Intelligence Platform: Web Application
Administration Guide.
n In SAS Visual Analytics 7.1 and earlier, there was an Other Content area that
displayed lists of explorations, reports, stored processes, stored process reports,
queries, or tables that someone with theVisual Analytics: Administration role had
added for users. Starting in SAS Visual Analytics 7.2, there is no longer an Other
Content area. If your site had an Other Content area, that area upgrades to a
published collection. The published collection is displayed as a collection tile on the
home page with the Modern appearance, and as a folder under the My Content
heading on the home page with the Classic appearance.
Note: In order to support encryption of SASHDAT, you must apply the SAS
Intelligence Platform 9.4m2f and the SAS Visual Analytics 7.2 hot fixes. After the hot
fixes are applied, you must re-add the Hadoop Server and the SAS Data in HDFS
Library resource templates in SAS Management Console. For more information, see
SAS Visual Analytics: Installation and Configuration Guide (Distributed SAS LASR).
n On the LASR Tables and LASR Servers tabs, some columns are initially hidden. To
show or hide a column, right-click on any column heading, and then select the
column.
n The LASR Tables tab does not include a Compression column. In the Status
column, indicates a compressed table. To view the original size of a compressed
table, place your pointer over the table’s Size cell.
n Initially, the Folders pane is collapsed. To access the Folders pane, select View
Folders from the main menu.
n In a new deployment that offers guest access, the property App.AllowGuest is set on
individual software components, rather than at the suite level.
n The Build Analytical Model capability in SAS Visual Statistics is in the Visual
Analytics Explorer category.
n The SAS Visual Statistics high-cardinality properties have names that begin with
vae.modeling.
n The home page is independent from the SAS Visual Analytics suite.
o The property vah.client.ui.mode is replaced by a new home page property,
home.ui.mode.
o The property va.supportSharedThumbnails must be managed on two separate
nodes: Visual Analytics Hub and Visual Analytics.
o Capabilities for using the home page are in the Visual Analytics Hub category,
which is parallel to the Visual Analytics category.
o The Visual Analytics Data Administrators group is a member of the new
Home:Administration role.
SAS Visual Analytics 7.2 409
o The home page’s software component (Visual Analytics Hub) is a direct child of
SAS Application Infrastructure.
o A new property, home.exclude.capability.users, blocks home page modification
by anonymous users.
o A new property, home.allow.anonymous.user.personalization, temporarily
unblocks home page modification by anonymous users.
o Home page administration is documented in SAS Intelligence Platform: Web
Application Administration Guide.
87
SAS Visual Process Orchestration
2.1 (SAS 9.4) 2.2 (SAS 9.4) For more information about this release, contact
your SAS account representative.
412 Chapter 87 / SAS Visual Process Orchestration
2.1 (SAS 9.4) 2.2 (SAS 9.4) To migrate to SAS Visual Process Orchestration
2.2, see SAS MDM: Administrator’s Guide.
2.2 (SAS 9.4) 2.2 (SAS 9.4) To migrate within the same release, see SAS
MDM: Administrator’s Guide.
88
SAS Visual Scenario Designer
6.2, 6.2_M2 (SAS 9.4) 6.3 (SAS 9.4) For more information about
how to request this new
release and the features that
are available, contact your
SAS account representative.
414 Chapter 88 / SAS Visual Scenario Designer
89
SAS Web Parts for Microsoft
SharePoint
Release That
Current Release You Are
at Your Site Upgrading To
(SAS Release) (SAS Release) High-Level Steps and Resources
6.1 6.11, 6.12, 6.13 1 Before you upgrade, see “About SAS Web Parts
for Microsoft SharePoint” on page 417.
2 To upgrade to the latest release of SAS Web
Parts for Microsoft SharePoint by using the SAS
Deployment Wizard, see “Install and Configure a
Software Update” on page 69.
6.11, 6.12 6.12, 6.13 1 Before you upgrade, see “About SAS Web Parts
for Microsoft SharePoint” on page 417.
2 To upgrade to the latest release of SAS Web
Parts for Microsoft SharePoint by using the SAS
Deployment Wizard, see “Install and Configure a
Software Update” on page 69.
About SAS Web Parts for Microsoft SharePoint 417
Release That
Current Release You Are
at Your Site Migrating To
(SAS Release) (SAS Release) High-Level Steps and Resources
6.1 (SAS 9.4) 6.1 (SAS 9.4); To migrate within the same release, see SAS
6.11 (SAS Intelligence Platform: Installation and Configuration
9.4_M1); 6.12 Guide
and 6.13 (SAS
9.4_M2)
For more information about these functions, see SAS Web Parts for Microsoft
SharePoint: Administrator’s Guide.
SAS also shipped these releases of SAS Web Parts for Microsoft SharePoint:
418 Chapter 89 / SAS Web Parts for Microsoft SharePoint
90
SAS Web Report Studio
Determining Your Update Path for SAS Web Report Studio . . . 420
Upgrading an Existing SAS 9.4 Deployment . . . . . . . . . . . . . . . . . . . . . . 420
Migrating to SAS 9.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
4.4 (SAS 9.4) 4.4_M1 (SAS 1 Before you upgrade, see “SAS Web Report
9.4_M1), 4.4_M2 Studio 4.4” on page 422.
(SAS 9.4_M2),
4.4_M3 (SAS 2 To upgrade to the latest release of SAS Web
9.4_M3) Report Studio 4.4, see “Install and Configure
a Software Update” on page 69.
3 To complete any post-configuration steps, see
“Updating Favorites in Your Web Browser” on
page 423.
4.4_M1 (SAS 4.4_M2 (SAS 1 Before you upgrade, see “SAS Web Report
9.4_M1), 4.4_M2 9.4_M2), 4.4_M3 Studio 4.4” on page 422.
(SAS 9.4_M2) (SAS_9.4M3)
2 To upgrade to the latest release of SAS Web
Report Studio 4.4, see “Install and Configure
a Software Update” on page 69.
3 To complete any post-configuration steps, see
“Updating Favorites in Your Web Browser” on
page 423.
SAS Web Report Studio 4.3 421
4.31, 4.31_M1, 4.4, 4.4_M1, 1 Before you upgrade, see “SAS Web Report
4.31_M2 (SAS 9.3) 4.4_M2, 4.4_M3 Studio 4.3” on page 421 and “SAS Web
(SAS 9.4) Report Studio 4.4” on page 422.
2 To migrate to the new release, see SAS 9.4
Intelligence Platform: Migration Guide. To
create a new deployment, see SAS 9.4
Intelligence Platform: Installation and
Configuration Guide.
3 To complete any post-configuration steps, see
“Updating Favorites in Your Web Browser” on
page 267 and SAS 9.4 Intelligence Platform:
Web Application Administration Guide.
4.4, 4.4_M1, 4.4, 4.4_M1, To migrate within the same SAS release, follow
4.4_M2 (SAS 9.4) 4.4_M2, 4.4_M3 the steps in SAS 9.4 Intelligence Platform:
(SAS 9.4) Migration Guide.
4.4_M3 (SAS 9.4) 4.4_M3 (SAS 9.4) To migrate within the same release, follow the
steps in SAS 9.4 Intelligence Platform: Migration
Guide.
These steps are not required if you are upgrading to the second maintenance release
for SAS Web Report Studio 4.4, which runs on the second maintenance release for
SAS 9.4.
In SAS Web Report Studio 4.3, data explorations were converted to reports. If any of
the converted objects are based on cubes, then during migration this conversion does
not succeed until the cube files are rebuilt. If the LoadContent step displays a warning
during migration, follow the instructions in the Instructions.html file to build the cube files
and modify and rerun the LoadContent scripts.
If you are running SAS Web Report Studio 4.2, you must upgrade to SAS Web Report
Studio 4.3 before upgrading to SAS Web Report Studio 4.4. If you upgrade from 4.2 to
4.4, your data explorations might not convert properly.
When upgrading to SAS Web Report Studio 4.3, you have these options:
n You can upgrade to the latest release of SAS 9.2. SAS Web Report Studio 4.3 runs
on SAS 9.2.
To upgrade to the latest release of SAS 9.2, see Planning for Maintenance Releases
and Product Upgrades for SAS 9.2.
n You can upgrade to the latest release of SAS 9.3. SAS Web Report Studio 4.31_M2
runs on SAS 9.3.
When you upgrade to SAS 9.3, you can migrate, or you can create a new
deployment. For specific steps, see SAS 9.3 Intelligence Platform: Migration Guide
(if you are migrating to the new release) or SAS 9.3 Intelligence Platform: Installation
and Configuration Guide (if you are creating a new deployment). For post-
configuration steps, see SAS 9.3 Intelligence Platform: Web Application
Administration Guide.
For information about the new features and enhancements in SAS Web Report Studio
4.4, see “What’s New in SAS Web Report Studio 4.4” on the product documentation
page for SAS Web Report Studio.
If you saved the URL for a previous release as a Favorite link in a web browser, then
this link is broken when you upgrade to the new release. You must re-create this favorite
for the new release. You can also access SAS Web Report Studio 4.4 by using this
unresolved link: http://server:port/SASWebReportStudio.
424 Chapter 90 / SAS Web Report Studio
425
Recommended Reading
Glossary
planned deployment
a method of installing and configuring a SAS business intelligence system. This
method requires a deployment plan that contains information about the different
hosts that are included in the system and the software and SAS servers that are to
be deployed on each host. The deployment plan then serves as input to an
installation and configuration tool called the SAS Deployment Wizard.
Index
Special Characters planned 53
deprecated functionality 30
_usermods files 45 disk space
requirements 39
B
E
backup files 40
basic deployment 54, 55 EAR files
customization 44
EXTENDOBSCOUNTER= data
C set option 99
EXTENDOBSCOUNTER=
CA certificates 101 LIBNAME statement option
Configuration Guidelines and 99
Details 62 EXTENDOBSCOUNTER=
customizations 46 system option 99
customized deployment plan
58
F
D favorites
updating 423
deployment registry report files
contents of 14 _usermods 45
running 14 customizations 46
deployment summary for the EAR 44
installation 63 FORMAT procedure 94
deployment types 54, 55
deployments
430 Index
H S
third-party software 31