Changes to Note Before You Upgrade to SAS Data Integration Studio 4.3
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, are 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 job whose process flow included a separate Report transformation, such as Correlations Report and Frequency Report, no longer has 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.
-
The DataFlux IS Job transformation is now called the DataFlux Batch Job Transformation. The DataFlux IS Service transformation is now called the DataFlux Data Service transformation. For other changes related to these transformations, see Working with Data Quality Transformations in SAS Data Integration Studio: User's Guide.
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 must manually migrate the files. If a file on the target
computer has a different physical path than the file had on the source
computer, then any migrated metadata that points to that file has
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, the file will not be moved during the standard migration
process. If you execute the job after migration, an error will appear
in the SAS log, saying that the transformation could not access the
source code file. To fix the problem, use the operating system tools
to copy the source code file to the target computer, preserving 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, the file 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 complete the
steps described earlier 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 complete the steps described earlier for transformations.
However, if the path
to the source code files in the target environment cannot be the same
as the path 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:
To identify jobs that
use an updated deployment directory definition:
To identify flows that
include a job that uses an updated deployment directory definition:
To reschedule flows
that include a job that uses an updated deployment directory definition:
To reschedule flows
that include a job that uses an updated deployment directory definition:
User Action Required for Migrated Jobs with Data Quality Transformations
User Action Required for Migrated Jobs with Data Service Transformations
User Action Required for Migrated Jobs with the Create Match Code Transformation
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,
select Tools
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.
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.
User Action Required for Migrated Jobs with the Apply Lookup Standardization Transformation
Migration to 9.3 when the QKB is different on the target system
If you are migrating
from SAS 9.1.3 or SAS 9.2 to SAS 9.3, and the target system has a
different QKB than you had on the source system, then user action
is required in order for a job with the Apply Lookup Standardization
transformation to work. You must open each affected job and replace
the migrated Apply Lookup Standardization transformation with a new
(4.3) Apply Lookup Standardization transformation. You must restore
the mappings in each job.
Migration to 9.3 when the QKB is the same on the target system
If you are migrating
from SAS 9.2 to SAS 9.3, and the target system has the same QKB that
you had on the source system, then no user action is required in order
for a job with the Apply Lookup Standardization transformation to
work.
If you are migrating
from SAS 9.1.3 to SAS 9.3, and the target system has the same QKB
that you had on the source system, then user action is required in
order for a job with the Apply Lookup Standardization transformation
to work.
You can take one of
the following actions:
-
Open each affected job and replace the migrated Apply Lookup Standardization transformation with a new (4.3) Apply Lookup Standardization transformation. You must restore the mappings in each job. After replacing the transformation, the Control Flow of the transformation in the job is out of order. Use the Details panel to restore Control Flow.
-
Alternatively, you could return to your old SAS Data Integration Studio environment, export the original Apply Lookup Standardization jobs to the SAS 9.1.3 package format, and then use the Import SAS Package wizard in SAS Data Integration Studio 4.3 to convert and register these jobs on your metadata server.
The following additional
steps are required in order for the export SAS Package method to work:
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 the SAS Package format, you can use
the Import from SAS Package wizard in SAS
Data Integration Studio 4.3 to convert and register these jobs on
your metadata server.
Changes to the Tree View
If you are migrating
from SAS 9.1.3 to SAS 9.3, 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 Systems That Are Migrated from SAS 9.1.3 in SAS Intelligence Platform: System Administration Guide.
Impacts on Change Management
Administrators who are
responsible for setting up change-management in SAS Data Integration
Studio have additional work to do after migration. For more information
about administering SAS Data Integration Studio, see SAS Intelligence Platform: Desktop Application Administration Guide.
Impacts on SAS Solutions
Copyright © SAS Institute Inc. All rights reserved.