Review the SAS Middle-Tier Configuration
The automated migration tools do not preserve any of the SAS middle-tier configuration information. The deployment of the SAS 9.4 middle tier is always “out of the box.”
Many of the defaults have changed, and any customizations should be reviewed with respect to SAS 9.4 web administration guidelines before they are implemented. Do not assume that the defaults used in SAS 9.2 or SAS 9.3 middle-tier configuration are appropriate for SAS 9.4. For more information, see SAS Intelligence Platform: Middle-Tier Administration Guide.
Update a Whitelist-Related Property in SAS Management Console
After migration, you must update the sas.web.csrf.referers.knownHosts property using SAS Management Console. For more information about
sas.web.csrf.referers.knownHosts and how to change its value, see “Modify the Whitelist for URLs and HTTP Request Methods” in SAS Intelligence Platform: Middle-Tier Administration Guide.
Reconfigure Transport Layer Security (TLS)
Any configuration of TLS (also known as SSL) made to your SAS system is not migrated. After you migrate your SAS system, you have to reconfigure TLS.
For more information, see “Configure SAS Web Server Manually for HTTPS” in SAS Intelligence Platform: Middle-Tier Administration Guide or see “Configure SAS Web Application Server for HTTPS” in SAS Intelligence Platform: Middle-Tier
Administration Guide.
Review Role Changes to SAS Web Report Studio
SAS Web Report Studio 4.4 uses the user roles that are implemented in SAS 9.4. For information about SAS 9.4 roles, see “Availability of Application Features in a New Deployment” in SAS Intelligence Platform: Security Administration Guide.
You should review your migrated SAS Web Report Studio users and their re-mapped roles to determine whether you should make any changes. The capabilities for most of your SAS Web Report Studio migrated users should remain the same. However, any SAS Web Report Studio 3.1 advanced users lose the ability to manage distribution lists.
To review roles and to manually re-apply any lost capabilities, see the SAS Intelligence Platform: Web Application Administration Guide.
Redefine Themes and Branding
SAS 9.2 and later includes a new theme infrastructure that is used by web applications such as SAS Web Report Studio and the SAS Information Delivery Portal.
For information about migrating custom themes created with SAS Theme Designer for Flex, see the section Migrate and Update Custom Themes Automatically, available at http://support.sas.com/documentation/cdl/en/flexthemedesignug/65531/HTML/default/
viewer.htm#n01c94tuyvd288n1otqnjw82670h.htm.
The product-specific branding that was available in SAS Web Report Studio 4.2 is no longer supported. There are no provisions for migrating older branding changes to the new themes in version 4.4. This means that the branded areas must be redefined in the new themes infrastructure.
Location of Dashboards and Indicators
After you upgrade to SAS BI Dashboard 4.4, update the URLs for all SAS BI Dashboard static links, StM data (in indicator data), and custom graph indicators that use stored processes. You update these URLs in the SAS BI Dashboard Image Web address field.
See your SAS BI Dashboard online Help for more information.
After migration, dashboards and any objects in the dashboard (such as indicators, models, and ranges) are metadata objects and are saved in SAS folders. Any dashboards that you created before SAS BI Dashboard 4.3 are saved as metadata objects. The default location for these metadata objects is the Products\BIDashboard 4.4 directory. This directory contains the
DashboardConfigs,IndicatorDefinitions, ModelConfigs, and RangeDefinitions subdirectories.
CAUTION:
Do not move the contents of these folders into different folders. If the contents of these folders are moved to different folders, these objects cannot be used with their dashboards.
SAS BI Dashboard and JDBC DSX Files
If your SAS BI Dashboard relies on any data sources specified in JDBC data source XML (DSX) files, then you must manually migrate these data sources.
You have two options for migrating your data.
• Move the data under metadata control.
• Continue to use a SAS libref that points to the workspace server's file system.
If you use this libref method, then you must manually fix the librefs in JDBC DSX files.
For more information, see “Working with Data Source XML (.dsx) Files” in SAS Intelligence Platform: Web Application Administration Guide.
Middle-Tier Post-migration Tasks 109
Deprecated Middle-Tier Property
In SAS 9.3, a property was added to the SAS middle tier, Policy.DisableConcurrentUserLogins. The value of
Policy.DisableConcurrentUserLogins is either TRUE or FALSE.
In SAS 9.4, Policy.DisableConcurrentUserLogins has been replaced by
Policy.ConcurrentUserLogins. The value of Policy.ConcurrentUserLogins is either DENY or LOGOFF.
Reviewing Your WebDAV Configuration
Review WebDAV Report Repository Permissions
After migration, you should review your WebDAV security settings and make the changes appropriate for your site and its security needs. For more information, see
“Implement Authorization for the SAS Content Server ” in SAS Intelligence Platform:
Middle-Tier Administration Guide.
Note about Migrated WebDAV Content Datestamps
The SAS automated migration tools replace creation dates on content with the date on which the migration occurred. The migration tools preserve modification dates on content. For this reason, migrated WebDAV content can have a creation date that is later than its modification date.
Update SAS Enterprise Miner Workspace Server WebDAV Paths If you published SAS Enterprise Miner model packages to a WebDAV server, you might need to manually update the WebDAV path.
For more information, see the SAS Enterprise Miner: Administration and Configuration.
Update SAS Information Delivery Portal URLs
Some additional steps must be performed after the SAS Deployment Wizard executes to ensure that links within the SAS Information Delivery Portal have migrated
appropriately. To facilitate this process, SAS provides a script that you should run to perform these tasks. See the Instructions.html file for more information.
Instructions.html is under the SAS configuration directory in the Levn/Documents subdirectory (for example, C:\SAS\Config94\Lev1\Documents).