Previous Page | Next Page

Product-Specific Details

SAS Data Integration Studio

Overview

SAS Data Integration Studio users who are migrating to version 4.2 should take special note of the following changes:

For general information about SAS Data Integration Studio, see the online Help or the SAS Data Integration Studio: User's Guide.

Objects That Are Not Migrated

External file metadata that is older than SAS 9.1.3, and any jobs that include such metadata , will not be migrated. The external files must be re-registered in the 9.2 environment. Any jobs that include external file metadata that is older than SAS 9.1.3 must be recreated in the 9.2 environment.

Updates to Jobs and Transformations during Migration

After migration, you will see the following changes to jobs and transformations.

All migrated transformations, including pre-3.2 version generated transformations, will be converted to use the new prompting framework. For most users, the main impact of this change is on the Options tab for transformations. It is now easier to select options from this tab. After migration, jobs with updated transformations should produce the same output as before.

Any pre-3.4 versions of the Table Loader transformation and the SQL Join transformation will be replaced with the latest versions of these transformations. After migration, jobs with converted transformations should produce the same output as before.

Any job whose process flow included a separate Report transformation, such as Correlations Report and Frequency Report, will no longer have that transformation in the process flow. The need for separate Report transformations has been eliminated. After migration, jobs that used to require the Report transformations should produce the same output as before.

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 [arrow] Redeploy Jobs for Scheduling or Tools [arrow] Redeploy Jobs to Stored Processes.

Any job that was deployed as a Web Service in SAS Data Integration Studio 3.4 will appear in the Stored Process folder of the Inventory tree, not the Web service (generated) folder. This special kind of stored process can be used as before.

Migrate Content Stored Outside the SAS Configuration Directory

Some metadata objects specify paths to physical files. If these files are stored outside of the directories that are part of the standard migration process, then you will have to manually migrate the files. If a file on the target computer has a different physical path than it had on the source computer, then any migrated metadata that points to that file would have to be updated to point to the new location.

For example, the metadata for a transformation within a job can point to a file that contains source code. If the file is stored outside of the SAS configuration directory, it will not be moved during the standard migration process. If you execute the job after migration, an error will appear the SAS log, saying that the transformation could not access the source code file. To fix the problem, manually migrate the source code file to the target computer, taking care to preserve the directory structure, if possible. Then run the job again. If the transformation fails, review the physical path to the file and either change the path on the file system or update the metadata that points to the file.

Similarly, if the metadata for an external file points to a file that is stored outside of the SAS configuration directory, it will not be moved during the standard migration process. If you right-click the metadata for the external file and select Open, a "file does not exist" error displays. To fix the problem, manually migrate the file to the target computer and perform the steps described above for transformations.

The metadata for a deployed job, such as a job that has been deployed for scheduling, points to a file that contains the code for the job. If you migrate the metadata for a deployed job, and the metadata is pointing to a file that does not exist in the target environment, then the deployed job will fail. To fix the problem, manually migrate the file to the target computer and perform the steps described above for transformations.

However, if the path to the source code files in the target environment cannot be the same as it was in the old environment, you must update the directory definition in the target environment, and then reschedule all flows that include jobs that use the updated deployment directory definition.

To update directory definitions in the target environment, perform the following steps:

  1. In SAS Management Console, right-click the Schedule Manager and select Deployment Directories.

  2. Edit any outdated deployment directory definitions so that they point to the location where you moved the source code files.

To identify jobs that use an updated deployment directory definition, perform the following steps:

  1. In SAS Management Console, right-click the Schedule Manager and select Manage Deployed Jobs.

  2. In the Manage Deployed Jobs window, right-click the job and select Properties.

  3. In the properties window, click the Scheduling Details tab.

  4. In the Scheduling Details tab, see if an updated deployment directory definition is specified in the Directory field.

  5. Note the names of all jobs that specify an updated deployment directory definition.

To identify flows that include a job that uses an updated deployment directory definition, perform the following steps:

  1. In SAS Management Console, right-click the Schedule Manager and select Manage Deployed Jobs.

  2. In the Manage Deployed Jobs window, expand a job that uses an updated deployment directory definition. Note all flows that include that job.

  3. Repeat for all jobs that use an updated deployment directory definition.

To reschedule flows that include a job that uses an updated deployment directory definition, perform the following steps:

  1. In SAS Management Console, select the Schedule Manager.

  2. in the table view on the right, select ALL in the Filter control, click Filter Now. All flows will be displayed.

  3. In the table view, hold down the CTRL key and click to select all flows that use an updated deployment directory definition.

  4. Right-click a selected flow, and then select Schedule Flow.

User Action Required for 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. To verify the DQSETUPLOC value, selectTools [arrow] Options from the menu bar, click the Data Quality tab, and then verify that the appropriate value is specified in the DQ Setup Location field.

Jobs that include the Apply Lookup Standardization transformation will not run successfully after migration until you take one of the following actions:

Note:   The export SAS Package method is possible only if you are using SAS 9.1.3 Service Pack 4, with SAS Data Integration Studio 3.4, and the 34DATABLDR09 hot fix installed.   [cautionend]

The following additional steps are required in order for the export SAS Package method to work:

  1. (Optional) In SAS Data Integration Studio 4.2, if you will not be using the migrated jobs that include the Apply Lookup Standardization transformation, delete them. Otherwise, you will have to manage multiple copies of the same metadata objects when you import the same jobs as a SAS Package.

  2. In SAS Data Integration Studio 3.4, create a package of jobs that use the same scheme repository type in the Apply Lookup Standardization. Create one package for the BFD scheme type and a separate package for the NOBFD scheme type.

  3. In SAS Data Integration Studio 4.2, verify that the default DQ Setup Location is correct, and that the default Scheme Repository Type matches the type (BFD or NOBFD) for the package of jobs that you are importing.

To verify these values before importing the SAS Package, selectTools [arrow] Options from the menu bar, click the Data Quality tab, and then verify that the appropriate value is specified in the DQ Setup Location field, and then specify the appropriate values in the DQ Setup Location field and the Scheme Repository Type field. The DQ Setup Location field should specify appropriate Quality Knowledge Base (QKB) location value (DQSETUPLOC value). The Scheme Repository Type field should match the type (BFD or NOBFD) for the package of jobs that you are importing.

When the package is imported, the job and its transformations are updated as they are during migration. The Apply Lookup Standardization transformation will use the default scheme repository values, and if the values are correct the transformation will run successfully.

Updates to Jobs and Transformations During Partial Promotion

You might have jobs stored in locations that are not part of the migration process. If these jobs can be exported to SAS 9.1.3 Package format, you can use the Import from SAS Package wizard in SAS Data Integration Studio 4.2 to convert and register these jobs on your metadata server.

If you have jobs that were exported in XML format prior to SAS Data Integration Studio 3.4., you must either include these jobs in a system migration, or import them in SAS Data Integration Studio 3.4, export them as a SAS Package, then import the SAS Package in SAS Data Integration Studio 4.2.

Note:   When a job in SAS 9.1.3 Package format is imported with the SAS 9.2 Import from SAS Package wizard, the job and its transformations are updated as they are during migration.   [cautionend]

Changes to the Tree View

After migration, you will see a number of changes to the tree view on the left side of the desktop. For more information, see "About the Initial Folder Structure for Migrated Systems" in the "Working with SAS Folders" chapter of the SAS Intelligence Platform: System Administration Guide.

SAS Workspace Server Requirements for New Jobs

From this release forward, new jobs with code that is generated by SAS Data Integration Studio must be executed on a SAS 9.2 Workspace Server or newer.

Impacts on Change Management

Administrators who are responsible for setting up change-management in SAS Data Integration Studio will have some additional work to do after migration. For more information, see the SAS Data Integration Studio chapter in the SAS Intelligence Platform Desktop Application Administration Guide.

Impacts on SAS Solutions

Some SAS 9.2 solutions might not be available until after the release of SAS Data Integration Studio 4.2. Accordingly, if your site is using a SAS solution, it is recommended that you not import individual solution objects until that solution is ready for SAS 9.2 and is installed.

Alternatively, you can migrate or import jobs with missing solution transformations and simply not open them until after the SAS 9.2 solution is installed. After the SAS 9.2 solution is installed, you could select a job in a tree view and use the Upgrade pop-up menu option to upgrade the job.

Previous Page | Next Page | Top of Page

Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.