Performing Post-migration Tasks

Server Tier Post-migration Tasks

	z/OS Burst Set and Optimizer Library Considerations
	Update SAS Server Configuration Files
	Migrating Content Stored Outside the SAS Configuration Directory
	Update Stored Process Archive Package Paths
	Update Stored Process WebDAV Paths
	Rebuild OLAP Cubes
	Manually Convert Data Explorations to Reports
	Redeploy Jobs for Scheduling
	Verify Migrated Jobs with Data Quality Transformations
	Reschedule Flows
	Modify Migrated Information Maps to Enable SAS Web Report Studio Optimization

z/OS Burst Set and Optimizer Library Considerations

If the burst set library is pre-assigned in z/OS, attempting to distribute using an existing burst set in that library generates a message that the table could not be read (or a blank list) when you select Recipients and Distribution Rules. Attempting to create a new burst set while the library is pre-assigned generates exceptions, similar to the following:

An error occurred in processing the page request. createBurstSet() (com.sas.report.output.management.OutputManagementException: The physical data is not available [ java.sql.SQLException: Unable to execute for an undetermined reason. SQL passthru expression contained these errors: ERROR: Libname WRSDIST is not assigned.

[ java.sql.SQLException: SQL passthru expression contained these errors: ERROR: Libname WRSDIST is not assigned. ] ] ) SQL passthru expression contained these errors: ERROR: Libname WRSDIST is not assigned.

Root Cause: java.sql.SQLException: SQL passthru expression contained these errors: ERROR: Libname WRSDIST is not assigned.

In actuality, the library is pre-assigned, but the message states that it is not. Removing the pre-assigned flag returns functionality to normal.

Update SAS Server Configuration Files

As mentioned earlier, certain SAS application server configuration files such as autoexec files (appserver_autoexec.sas) and sasv9.cfg files are not migrated. At some point, you might need to tune these files with configuration settings (such as Java options) appropriate for your site. For more information, see Optional Setup Tasks.

Although the command to start SAS and any settings in config or autoexec files are not migrated, load balancing configuration and metadata information for SAS servers is migrated. (Load balancing here should not be confused with server clustering--the management of multiple Web application servers on the SAS middle tier.) The same server load-balancing algorithms that were present in SAS 9.1.3 are available and still used. The new load-balancing algorithms are for servers or configurations that did not exist in SAS 9.1.3. For more information about the load balancing algorithms available in SAS 9.2, see Understanding the Load-Balancing Algorithms in the SAS Intelligence Platform: Application Server Administration Guide.

Migrating Content Stored Outside the SAS Configuration Directory

About Migrating Content Stored Outside the SAS Configuration Directory

SAS 9.1.3 content stored outside the configuration directory remains in its SAS 9.1.3 location. Examples of SAS 9.1.3 content include the following:

Note: If you are migrating from Windows 32-bit operating systems to Windows 64-bit operating systems, there are some particular post-migration steps that you must perform, such as converting your custom formats catalog before rebuilding your cubes. For more information, see the white paper available at the Migration Focus Area: http://support.sas.com/migration/. [cautionend]

In the design phase of your migration, the migration analysis report identified any SAS content that would require manual steps to migrate. (These steps are listed in the "Product: Level Configuration" section of the analysis report.) When the migration utility encounters metadata that points to content residing outside of the SAS 9.1.3 configuration directory, it writes a warning message to the analysis report and copies only SAS source files (files with a .sas extension) to the migration package to tier-name/levconfig/datapackagesuffix.

The following migration analysis report identifies some SAS 9.1.3 stored processes that would not be migrated to SAS 9.2, because these stored processes reside outside of the SAS 9.1.3 configuration directory:

[Example of a migration analysis report]

The SAS migration tools do not support automatically migrating this content and updating the SAS 9.2 metadata. If you want to maintain two separate repositories for your SAS content outside of the configuration directory, then you must manually move this content and update your SAS 9.2 metadata.

CAUTION:: Regardless of whether you choose to migrate SAS 9.1.3 content that is stored outside of the configuration directory, we strongly recommend that you back up this content before proceeding.

Even though the SAS automated migration tools migrate SAS tables that reside under the SAS 9.1.3 configuration directory and in a SASEnvironment or Data folder, the best practice is to store your SAS tables outside the SAS configuration directory. Migrating large amounts of data encountered under the configuration directory slows migration utility performance.

Where your tables reside--and how the libraries reference those tables--determine whether you must manually update paths in your libraries. Rules for how the automated migration tools update paths to data in SAS libraries are as follows:

Libraries that reference relative paths to data will remain unchanged.
Libraries that reference paths to data in the SAS 9.1.3 configuration directory SASEnvironment and Data folders will be updated to reference the new 9.2 folder location.
Libraries that reference paths to data outside the SAS 9.1.3 configuration directory will not be updated and will still reference the same path in SAS 9.2.
Libraries that reference paths to data inside the SAS 9.1.3 configuration directory (but not in a SASEnvironment or Data folder) will not be updated and will still reference the same path in SAS 9.2.

Migrate External SAS Data Integration Studio Content

The SAS Migration Utility is able to migrate all your SAS Data Integration Studio 3.4 jobs and job flows because these are objects that are stored in metadata. However, if any of your jobs or job flows point to files that reside outside of the SAS 9.1.3 configuration directory, (such as source code files), then you have to manually migrate these external files.

For more information, see Migrate Content Stored Outside the SAS Configuration Directory in Special Considerations for Customers Upgrading to SAS 9.2.

Migrate Libraries Stored Outside the SAS Configuration Directory

The SAS 9.2 migration tools do not support automatically migrating content that is stored outside the SAS configuration directory. (This is true, even when the target machine running SAS 9.2 is the same as the SAS 9.1.3 machine.) For more information, see the rules for how the automated migration tools update SAS library metadata.

If you want to maintain two separate repositories for your SAS libraries outside of the configuration directory, then you must manually move these libraries and update your SAS 9.2 metadata.

CAUTION:: If you do not update the file and library paths to a new SAS 9.2 location, future changes made with SAS 9.2 will be written to the old SAS 9.1.3 libraries.

To manually migrate SAS libraries that reside outside the SAS 9.2 configuration directory, follow these steps:

Using the method prescribed by your site, back up your SAS 9.1.3 libraries.

Note: As you would with any backup, run these backups through your site's validation procedures to be confident of their integrity before proceeding with your SAS migration.
If you have decided to create a new library repository, create the new location and copy your SAS 9.1.3 libraries to this new location. This new location must be accessible to the SAS Application Servers associated with these libraries.
Log on to SAS Management Console as an unrestricted user (such as sasadm).
In the left pane, in the Plug-ins tab, expand the Data Library Manager icon.
Expand the Libraries folder.
Right-click the library, and select Properties from the pop-up menu.
In the Properties dialog box, select the Options tab.
In the Available items list, select the SAS 9.1.3 library path, and then select Edit.
In the dialog box that appears, modify the path to the new SAS 9.2 library that you created earlier.
Click OK to save the path.
In the Properties dialog box, select the new path, and click OK to select this repository as the repository for the selected library.

In the Properties dialog box, click OK to save the change to the library.
Repeat this process for each library that you want to change.

Note: Because you have already defined the new path, you will skip steps 8-10.

Migrate Stored Processes Stored Outside the SAS Configuration Directory

The SAS migration tools do not support automatically migrating content that is stored outside the SAS configuration directory. (However, the migration utility does package any .sas files pointed to by metadata outside of the SAS 9.1.3 configuration directory.) If you want to maintain two separate repositories for your SAS stored processes outside of the configuration directory, then you must manually move these stored processes and update your SAS 9.2 metadata.

To manually migrate SAS stored processes that reside outside the SAS 9.2 configuration directory, follow these steps:

Using the method prescribed by your site, back up your SAS 9.1.3 stored processes.

Note: As you would with any backup, run these backups through your site's validation procedures to be confident of their integrity before proceeding with your SAS migration.
If you have decided to create a new stored process code repository, create the new location and copy your SAS 9.1.3 stored processes to this new location. This new location must be accessible to your SAS Metadata Server and Stored Process Server.

The migration utility packages any .sas files pointed to by metadata outside of the SAS 9.1.3 configuration directory. Alternatively, you can copy .sas files from the migration package in tier-name/levconfig/datapackagesuffix.
Log on to SAS Management Console as an unrestricted user (such as sasadm).
In the left pane, select the Folders tab.
Navigate to a folder that contains one of your SAS 9.1.3 stored processes.
In the right pane, right-click the stored process, and select Properties from the pop-up menu.
In the Properties dialog box, select the Execution tab, and then Manage.
In the Manage Source Code Repositories dialog box, choose a path that needs to be updated and select Edit.
Review the Associated Stored Processes dialog box and select OK.
In the dialog box that appears, modify the path to point to the new SAS 9.2 stored process code repository that you created earlier.
Click OK to save the modified code repository path.
In the Properties dialog box, click OK to save the stored process.

Update Stored Process Archive Package Paths

The SAS automated migration tools update stored process archive package paths that point to locations inside the SAS configuration directory.

The SAS Migration Utility cannot update any paths that reside outside of the configuration directory. The migration utility flags such problematic paths in its migration analysis report. In SAS 9.2, stored process archive package paths are no longer modeled by metadata but are stored in prompt metadata. Therefore, after the SAS Deployment Wizard finishes executing, you will need to manually update the _ARCHIVE_PATH prompt for all affected stored processes using SAS Management Console. For more information, see Developing Stored Processes with Package Results in the SAS Stored Processes: Developer's Guide and the prompt Help in SAS Management Console online Help.

Update Stored Process WebDAV Paths

The SAS 9.1.3, if you published stored process result packages to a Xythos WebDAV server, then the SAS automated migration tools are able to automatically migrate these paths to the new SAS 9.2 WebDAV server, known as the SAS Content Server. In SAS 9.1.3, if you used a WebDAV server other than Xythos, (such as Apache HTTP), then you must manually update these WebDAV paths.

In its migration analysis report. the SAS Migration Utility flags all stored process WebDAV publish paths that are not for Xythos. In SAS 9.2, stored process WebDAV paths are no longer modeled by metadata but are stored in prompt metadata. Therefore, using SAS Management Console, you will need to update the _COLLECTION_URL prompt for all affected stored processes. For more information, see Developing Stored Processes with Package Results in the SAS Stored Processes: Developer's Guide and the prompt Help in SAS Management Console online Help.

Rebuild OLAP Cubes

In the design phase of your migration, the migration analysis report identified that SAS 9.1.3 cubes would need to be rebuilt in order to run in SAS 9.2:

[Migration analysis report showing that cubes must be rebuilt]

In SAS 9.2, PROC OLAP does not overwrite a cube repository if it finds files already present. Instead, OLAP creates a new folder with a unique name for the new cube. As part of the SAS Deployment Wizard migration of OLAP content to SAS 9.2, SAS code files are created that you can run to recreate your SAS 9.1.3 cubes to run in the new environment. The deployment wizard writes these files to the SAS-configuration-directory\Levn\SASMain\OLAPServer\OLAP directory. You can run these SAS files to recreate your cubes without having to specify a new SAS 9.2 path for your cube repository.

Note: During the cube rebuild procedure, if a database that SAS accesses requires login credentials, you must supply these in order to rebuild the cube. For more information, consult with your site's database administrator. [cautionend]

To rebuild SAS 9.1.3 cubes with SAS 9.2, follow these steps:

Using the method prescribed by your site, back up your SAS 9.1.3 cubes.

Note: As you would with any backup, run these backups through your site's validation procedures to be confident of their integrity before proceeding with your SAS migration.
Before proceeding, make sure that you have first updated your metadata to point to the SAS 9.2 library repository. For more information, see Migrate Libraries Stored Outside the SAS Configuration Directory.
If you have decided to create a new cube repository, create the new location. This new location must be accessible to your SAS Metadata Server, SAS OLAP Cube Studio, and the workspace server with which you rebuild the cubes.
Log on to SAS OLAP Cube Studio 4.2.
In the left pane, select the Inventory tab, and expand the Cube node.
Right-click a cube you want to rebuild and from the pop-up menu, choose Edit Cube Structure.

The Cube Designer Wizard displays.

Note: The identity used to edit and rebuild the cube must have ReadMetadata and WriteMetadata permissions granted for the cube and all of its dimensions, levels, hierarchies, and measures. If the identity is not granted these permissions, the Edit Cube Structure action is dimmed. The security reporting macros available with SAS 9.2 can help in determining whether an identity has the correct permissions to build a cube. For more information, see Authorization Model in the SAS Intelligence Platform: Security Administration Guide. Also, to run reports based on cubes and to refresh cubes, make sure that users have Read access to tables and cubes, and Read metadata access to the underlying libraries.
Click Browse for the Physical cube path field, and enter the new path where you want to store your rebuilt cubes.

If you have updated your metadata to point to the SAS 9.2 library repository, then accept the wizard defaults. For more information, see Migrate Libraries Stored Outside the SAS Configuration Directory.
On the final dialog box of the wizard, make sure that Save the metadata and create the cube is selected, and then select Finish.

The SAS 9.2 workspace server rebuilds the cube and saves it to the new location.
Repeat this process for each cube that you want to rebuild.

Manually Convert Data Explorations to Reports

In the November 2010 release of SAS 9.2, (which contains the release of SAS Web Report Studio 4.3), data explorations are now maintained as reports. When you upgrade or migrate, the SAS deployment tools automatically convert each bookmark in the data exploration into a report that you can view and edit using SAS Web Report Studio 4.3.

Note: If the conversion for any data exploration fails, you will receive a warning in the Instructions.html file. Because data explorations can have dependencies on OLAP cubes, make sure the cubes have been built after you migrate and before you run the scripts described later in this topic. For more information, see Rebuild OLAP Cubes. [cautionend]

To convert the data explorations manually, complete the following steps:

Read Before You Convert in Special Considerations for Customers Upgrading to SAS 9.2.
Do one of the following:
- After performing a migration or promotion, run the manualLoadContent-OrderNumber.bat/.sh script.
- After performing an upgrade, run the manualUpdateContent-OrderNumber.bat/.sh.
Note: Before execution, you will need to edit the script to replace the SPECIFY_ADMIN_PASSWORD_HERE and SPECIFY_TRUSTED_PASSWORD_HERE values with the correct passwords before executing it. It is strongly recommended that you specify a value encoded by SAS for the password.
For more information, such as where the script is located and where its log file is written, see Update Content Manually for the SAS Content Server in the SAS Intelligence Platform: Web Application Administration Guide.
Manually run the script (manualAdjustUrls-OrderNumber.bat/.sh) to adjust URLs and references to metadata that has moved either during migration or an upgrade.

For more information, such as where the script is located and where its log file is written, see Adjust Directive URLs Manually in the SAS Intelligence Platform: Web Application Administration Guide.
Validate that the conversion script was successful by running SAS Web Report Studio and loading one of the newly created reports.

For more information, see the SAS Web Report Studio 4.3 User's Guide.

SAS Web Report Studio upgrades the generated reports when you save them. However, if you want to upgrade all the generated reports at once, rerun the appropriate script specified in step 1.

After the conversion to bookmarks, the newly created reports follow this naming convention: data-exploration-name_bookmark-name-report.srx

If the bookmark name contains spaces, the resulting report name contains no spaces. For example, assume you have a data exploration named Sales Forecast that contains two bookmarks: Region A and Region B. The resulting report filenames after the upgrade or migration are: Sales Forecast_RegionA-report.srx and Sales Forecast_RegionB-report.srx, respectively.

Note: If the resulting report name is longer than 60 characters, then the portion of the name that precedes -report.srx is truncated. [cautionend]

If the data exploration contains conditional highlighting that includes an image, the image is removed from the conditional highlight. If a collection portlet in the SAS Information Delivery Portal pages contains links to the data explorations, these links are removed and replaced with links to the newly created reports. The converted links become visible to users when they refresh the collection or reopen the portal. For more information, see Differences between Data Explorations and Reports in Special Considerations for Customers Upgrading to SAS 9.2.

Any Information Map Viewer portlets are converted to report portlets, and the associate data exploration is converted to a report and associated to the converted report portlet.

Redeploy Jobs for Scheduling

All jobs that were deployed for scheduling or were deployed as stored processes should be redeployed in the SAS 9.2 environment. From the SAS Data Integration Studio desktop, you can select Tools Redeploy Jobs for Scheduling or Tools Redeploy Jobs to Stored Processes.

For more information about migrated jobs, see Updates to Jobs and Transformations During Migration in Special Considerations for Customers Upgrading to SAS 9.2.

Verify Migrated Jobs with Data Quality Transformations

If jobs that include the Create Match Code transformation do not run successfully after migration, verify that the appropriate Quality Knowledge Base (QKB) location value (DQSETUPLOC value), is specified on the global options window for SAS Data Integration Studio.

For more information, see User Action Required for Migrated Jobs with Data Quality Transformations in Special Considerations for Customers Upgrading to SAS 9.2.

Reschedule Flows

After migrating to SAS 9.2, owners of scheduled flows will need to submit them to the scheduling server used by the SAS 9.2 system. To reschedule flows, follow these steps:

Determine the user IDs associated with each SAS 9.1.3 flow. (Locate the checklist you completed earlier in Determine the User ID Associated with Scheduled Flows.)
If you have migrated any SAS Web applications, such as SAS Web Report Studio, verify that scheduling is enabled (Configuration Manager Web Report Studio 4.3 Properties Settings Application Scheduling).

Note: For more information, see Using Configuration Manager in SAS Intelligence Platform: Web Application Administration Guide.
Reschedule the flow for your SAS product. For example:
- For SAS Data Integration Studio, reschedule job flows.
  
  In SAS Management Console, use the reschedule function in Schedule Manager.
  
  For more information, see SAS Management Console online Help.
- For SAS Web Report Studio, reschedule report flows.
  
  In SAS Web Report Studio, on the Scheduled and Distributed Reports window (File Manage Files View scheduled and distributed reports), use the Actions button.
  
  For more information, see SAS Web Report Studio online Help.

Modify Migrated Information Maps to Enable SAS Web Report Studio Optimization

When a measure data item that meets the following criteria is migrated from SAS 9.1.3 to SAS 9.2, it is not automatically optimized for SAS Web Report Studio in the same way that an identical, new SAS 9.2 data item is optimized.

The measure data items are in an information map that was migrated from SAS 9.1.3 to SAS 9.2 by using the SAS automated migration tools.
The migrated information map has large data sources.
The migrated measure data items are used in the expressions of other measure data items.
The default aggregate function for a migrated measure data item is specified as a property of the data item instead of being defined in the data item expression.

To optimize these migrated data items for SAS Web Report Studio, you must recreate them in a SAS 9.2 environment. Consider the following example, which uses SAS Information Map Studio 4.2 to recreate some migrated data items:

When you recreate one of these data items, specify its aggregate function as a property of the data item (that is, follow the same basic steps that you followed when you created the data item in SAS 9.1.3). Do not define the aggregate function in the expression of the data item.

For example, data item DataItem1 was created in SAS Information Map Studio 3.1 and its aggregate function, SUM(argument), was specified on the Classifications/Formats tab. In SAS Information Map Studio 4.2, re-create this data item and select SUM(argument) on the Classifications, Aggregations, Formats tab.

Note: Copying and pasting the information map or data items, or just updating the existing data items will not cause optimization to occur. You must create brand new data items.
Delete the old measure data item or name the new one with a unique name.
Go through your reports and modify any references to point to the new data items that you created.

Note: Neither new nor migrated measure data items are optimized for SAS Web Report Studio if the aggregate functions of the data items are defined in the data item expressions. If one of these data items is also referenced by the expression of another data item, then you can optimize it if you can change to specifying its aggregate function as a property of the data item. [cautionend]

For more information, see SAS Information Map Studio 4.2 online Help and the Base SAS 9.2 Guide to SAS Information Maps.

Top of Page