Middle-Tier Post-migration Tasks

Overview of Middle-Tier Post-migration Tasks

The following topics are contained in this section:

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.3 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.3 Web administration guidelines before they are implemented. Do not assume that the defaults used in SAS 9.1.3 or SAS 9.2 middle-tier configuration are appropriate for SAS 9.3. For more information, see SAS Intelligence Platform: Middle-Tier Administration Guide.

Review Role Changes to SAS Web Report Studio

SAS Web Report Studio 4.3 uses the user roles that are implemented in SAS 9.3. For information about SAS 9.3 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, refer to 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. If you created custom themes for your SAS Web applications in SAS 9.1.3, then you can migrate certain components of your themes to the new theme infrastructure.
In previous releases, SAS Logon Manager used the same graphics and configuration files as other SAS Web applications. In the second maintenance release for SAS 9.3, SAS Logon Manager uses graphics from a separate directory and is also configured with a separate template file. For more information, see Migrating Custom Themes in SAS Intelligence Platform: Middle-Tier Administration Guide.
For information about migrating custom themes created with SAS Theme Designer for Flex, see “Migrate and Update Custom Themes Automatically” in SAS Theme Designer for Flex: User's Guide, available at http://support.sas.com/documentation/cdl/en/flexthemedesignug/65088/HTML/default/viewer.htm#n01c94tuyvd288n1otqnjw82670h.htm.
The product-specific branding that was available in SAS Web Report Studio 3.1 and SAS Web Report Studio 4.2 are no longer supported, and there are no provisions for migrating older branding changes to the new themes in version 4.3. This means that the branded areas must be redefined in the new themes infrastructure.

Notes about Migrated SAS Web Report Studio User Folders

SAS 9.2 and later secures a user’s folders by using a custom Access Control Template (the Private User Folder ACT). This ACT is designed to allow administrators, System Services, and the user access to a particular user’s folder and to prevent other users’ access.
In SAS 9.1.3, SAS Web Report Studio manages user folders at the application layer. As part of this management, explicit permissions are added to the user’s 9.1.3 SAS Web Report Studio home folder to achieve privacy.
Because SAS 9.2 and later no longer uses these explicit permissions, during migration to SAS 9.3, these explicit permissions are automatically removed, and all users’ home folders are relocated to the SAS 9.3 home folder location.
After migration, reports and folders are relocated and properly secured, and require no additional post-migration action.
For more information, see About the SAS Folder Structure in SAS Intelligence Platform: System Administration Guide.

BI Dashboard Post-Migration Tasks

About SAS BI Dashboard 4.3

With version 4.3, SAS BI Dashboard has been completely rewritten. There are some major usage differences between version 4.3 and version 4.2.
SAS BI Dashboard 4.3 is displayed in the Adobe Flash Player. This change makes the dashboard environment much more user-friendly, interactive, and feature-rich. The way you display your dashboard content is also different in the new version. For example, in version 4.2, it was very common to have multiple dashboard portlets on a single portal page. With version 4.3, each dashboard portlet renders an Adobe Flash Player, which means that using multiple portlets causes performance problems and can possibly cause your browser to crash.
For this reason, you should use only one dashboard portlet on a portal page at a time. Although the dashboard portlet displays a single dashboard at a time, version 4.3 is designed to allow much greater flexibility for displaying multiple indicators in a single dashboard. With version 4.2, you had very little control over the position of the different indicators in a dashboard. In version 4.3, you can position indicators with exact pixel placement.
When you upgrade to version 4.3 from version 4.2, your 4.2 content is converted. Everything is moved, including ranges, data models (called indicator data objects in version 4.3), indicators, and dashboards. However, you should plan to take advantage of the new interactive features in version 4.3 by creating new dashboard objects. (You can use your existing indicators, data, and ranges.)
Also, you should modify portal pages that contain multiple dashboardsso that they display a single dashboard in version 4.3. Start by creating a dashboard that would occupy the whole portal page, and then position the indicators as you would like.

Location of Dashboards and Indicators

After you upgrade to SAS BI Dashboard 4.3, 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, so any dashboards that you created prior to SAS BI Dashboard 4.3 are saved as metadata objects. The default location for these metadata objects is the Products\BIDashboard 4.3 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.

Resetting SAS Web Application URLs

When migrating from SAS 9.1.3 to SAS 9.3, attributes required to access your SAS Web applications can change. For example, SAS middle-tier machine names and the ports on which a Web application listens for client requests can change.
After migrating, be sure to review the URLs for your migrated SAS Web applications to make sure that they are still valid. For a list of these applications, see the Portal-WebApplications.html file that resides in the Documents subdirectory under your SAS 9.3 configuration path.

Reviewing Your WebDAV Configuration

About Reviewing Your WebDAV Configuration

The SAS automated migration tools migrate SAS 9.1.3 WebDAV repository access control lists (ACLs) except for those ACLs under the /sasfolders directory. Migrating WebDAV ACLs under the /sasfolders directory has these effects:
  • causes performance degradation during migration and increases repository disk space unnecessarily
  • compromises WebDAV security by allowing access to user IDs other than the SAS Administrator and the SAS Trusted User
(In SAS 9.1.3, the ACLs are located by default in the SAS configuration path under sasdav/wrs.)
The automated SAS migration tools update certain references to identities, so that these references are based on the identity's name, instead of on the identity's user ID. This change affects only WebDAV access control entries (ACEs) and WebDAV personal repository names. The following table provides an example for the user William Jones who has a login with a user ID of WIN\wsj.
Example of a Migrated WebDAV Personal Repository Name and ACE Entry
WebDAV Attribute
Example Values
Before Migration (SAS 9.1.3)
After Migration (SAS 9.3)
WebDAV personal repository name
wsj.WIN
William Jones
WebDAV person identifier in an ACE
WIN\wsj
person/William Jones
Note: SAS 9.2 and later uses the name value from the user’s metadata definition (not the display name value), because the name value should be stable over time.

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 Implementing 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 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 supplies a script that you should run to perform these tasks. Refer to Instructions.html for more information.
Instructions.html resides under the SAS configuration directory in the Levn/Documents subdirectory (for example, C:\SAS\Config92\Lev1\Documents).
Copyright © SAS Institute Inc. All rights reserved.