 |
|
| Performing Post-migration Tasks |
Middle-Tier Post-migration Tasks
| 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.2 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.2 Web administration guidelines before they are implemented. Do not assume that the defaults used in SAS 9.1.3 middle-tier configuration are appropriate for SAS 9.2. For more information, see SAS 9.2 Intelligence Platform: Web Application 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.2. For information about SAS 9.2 roles, see Ensure Availability of Application Features in the 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 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. For more information, see Migrating Custom Themes in the SAS Intelligence Platform: Web Application Administration Guide.
The product-specific branding that was available in SAS Web Report Studio 3.1 is 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 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 no longer uses these explicit permissions, during migration to SAS 9.2, these explicit permissions are automatically removed, and all users' home folders are relocated to the SAS 9.2 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 the SAS Intelligence Platform: System Administration Guide.
| Location of Dashboards and Indicators |
After you upgrade to SAS BI Dashboard 4.3, 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.
![[cautionend]](../../../../common/63294/HTML/default/images/cautend.gif)
| 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 the SAS Intelligence Platform: Web Application Administration Guide.
| Resetting SAS Web Application URLs |
When migrating from SAS 9.1.3 to SAS 9.2, 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.2 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.
| WebDAV Attribute | Example Values | |
|---|---|---|
| Before Migration (SAS 9.1.3) | After Migration (SAS 9.2) | |
| WebDAV personal repository name | wsj.WIN | William Jones |
| WebDAV person identifier in an ACE | WIN\wsj | person/William Jones |
Note: SAS 9.2 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 the SAS Intelligence Platform: Web Application 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 © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.