Business Objects products in this release may contain redistributions of software
licensed from third-party contributors. Some of these individual components may
also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required
notices, can be found at: http://www.businessobjects.com/thirdparty
2008-03-16
Contents
Data Quality to Data Services Migration Guide7Chapter 1
Data Services XI Release 3 provides data integration and data quality
processes in one runtime environment, delivering enterprise performance
and scalability.
The data integration processes of Data Services allow organizations to easily
explore, extract, transform, and deliver any type of data anywhere across
the enterprise.
The data quality processes of Data Services allow organizations to easily
standardize, cleanse, and consolidate data anywhere, ensuring that end-users
are always working with information that's readily available, accurate, and
trusted.
Documentation set for Data Services
You should become familiar with all the pieces of documentation that relate
to your Data Services product.
What this document providesDocument
Documentation Map
Release Summary
Release Notes
Getting Started Guide
8Data Services Migration Considerations
Information about available Data Services books,
languages, and locations
Highlights of key features in this Data Services release
Important information you need before installing and
deploying this version of Data Services
An introduction to Data Services
Data Quality to Data Services Migration Guide
Introduction
What this document providesDocument
1
Installation Guide
Advanced Development Guide
Designer Guide
Integrator's Guide
Management Console: Administrator
Guide
Management Console: Metadata Reports Guide
Migration Considerations
Migration Guide
Performance Optimization Guide
Information about and procedures for installing Data
Services
Guidelines and options for migrating applications including information on multi-user functionality and
the use of the central repository for version control
Information about how to use Data Services Designer
Information for third-party developers to access Data
Services functionality
Information about how to use Data Services Administrator
Information about how to use Data Services Metadata
Reports
Release-specific product behavior changes from
earlier versions of Data Services to the latest release
Information about how to migrate from Data Quality
to Data Services
Information about how to improve the performance
of Data Services
Reference Guide
Detailed reference material for Data Services Designer
Data Services Migration Considerations9
Data Quality to Data Services Migration Guide
1
Introduction
Technical Manuals
What this document providesDocument
A compiled “master” PDF of core Data Services books
containing a searchable master table of contents and
index:
•Installation Guide
•Getting Started Guide
•Designer Guide
•Reference Guide
•Management Console: Metadata Reports Guide
•Management Console: Administrator Guide
•Performance Optimization Guide
•Advanced Development Guide
•Supplement for J.D. Edwards
•Supplement for Oracle Applications
•Supplement for PeopleSoft
•Supplement for Siebel
•Supplement for SAP
Tutorial
A step-by-step introduction to using Data Services
In addition, you may need to refer to several Adapter Guides and
Supplemental Guides.
What this document providesDocument
JMS Adapter Interface
Salesforce.com Adapter
Interface
Supplement for J.D. Edwards
Supplement for Oracle Applications
10Data Services Migration Considerations
Information about how to install, configure, and use the Data
Services Adapter for JMS
Information about how to install, configure, and use the Data
Services Salesforce.com Adapter Interface
Information about license-controlled interfaces between Data
Services and J.D. Edwards World and J.D. Edwards OneWorld
Information about the license-controlled interface between Data
Services and Oracle Applications
Data Quality to Data Services Migration Guide
Introduction
What this document providesDocument
1
Supplement for PeopleSoft
Supplement for SAP
Supplement for Siebel
Information about license-controlled interfaces between Data
Services and PeopleSoft
Information about license-controlled interfaces between Data
Services, SAP ERP and R/3, and SAP BI/BW
Information about the license-controlled interface between Data
Services and Siebel
Accessing documentation
You can access the complete documentation set for Data Services in several
places.
Note: For the latest tips and tricks on Data Services, access our Knowledge
Base on the Customer Support site at http://technicalsupport.businessob
jects.com. We have posted valuable tips for getting the most out of your Data
Services product.
Accessing documentation on Windows
After you install Data Services, you can access the documentation from the
Start menu.
1. Choose Start > Programs > BusinessObjects XI 3.0 >
BusinessObjects Data Services > Data Services Documentation.
Note: Only a subset of the documentation is available from the Start
menu. The documentation set for this release is available in
LINK_DIR\Doc\Books\en.
2. Click the appropriate shortcut for the document that you want to view.
Accessing documentation on UNIX
After you install Data Services, you can access the online documentation by
going to the directory where the printable PDF files were installed.
1. Go to LINK_DIR/doc/book/en/.
Data Services Migration Considerations11
Data Quality to Data Services Migration Guide
1
Introduction
2. Using Adobe Reader, open the PDF file of the document that you want
to view.
Accessing documentation from the Web
You can access the complete documentation set for Data Services from the
Business Objects Customer Support site.
1.
Go to www.businessobjects.com
2. From the "Support" pull-down menu, choose Documentation.
3. On the "Documentation" screen, choose Product Guides and navigate
to the document that you want to view.
You can view the PDFs online or save them to your computer.
Business Objects information resources
Customer support, consulting, and training
A global network of Business technology experts provides customer support,
education, and consulting to ensure maximum business intelligence benefit
to your business.
Useful addresses at a glance
Product information
http://www.businessob
jects.com
Product documentation
http://www.businessob
jects.com/support
Documentation mailbox
documentation@businessobjects.com
12Data Services Migration Considerations
ContentAddress
Information about the full range of Business
Objects products.
Business Objects product documentation, including the Business Objects Documentation
Roadmap.
Send us feedback or questions about your
Business Objects documentation.
The Business Objects Customer Support web site contains information about
Customer Support programs and services. It also has links to a wide range
of technical information including Knowledge Base articles, downloads, and
support forums. http://www.businessobjects.com/support
Information on Customer Support programs,
as well as links to technical articles, downloads, and online forums.
An online resource for sharing and learning
about Data Services with your developer colleagues.
Information about how Business Objects can
help maximize your business intelligence investment.
Information on Business Objects training options and modules.
Looking for training options?
From traditional classroom learning to targeted e-learning seminars, Business
Objects can offer a training package to suit your learning needs and preferred
learning style. Find more information on the Business Objects Education
web site: http://www.businessobjects.com/services/training
Send us your feedback
Do you have a suggestion on how we can improve our documentation? Is
there something that you particularly like or have found useful? Drop us a
line, and we will do our best to ensure that your suggestion is considered for
the next release of our documentation: documentation@businessobjects.com.
Data Services Migration Considerations13
Data Quality to Data Services Migration Guide
1
Introduction
Note: If your issue concerns a Business Objects product and not the
documentation, please contact our Customer Support experts.
Overview of migration
About this guide
The Data Quality Migration Guide provides information about:
•migrating your Data Quality Projects into Data Services
•understanding some of the benefits of using Data Services
•seeing the differences between previous versions of Data Quality and
Data Services
•using best practices during migration
•learning how to troubleshoot during migration
Who should migrate?
Anyone who is using Data Quality XI and Data Services as standalone
applications should migrate to Data Services.
The migration utility works with these versions of software:
•Data Integrator 11.7.x
•Data Quality XI 11.7.x and 11.6.x
•Data Integrator XI R2
•Data Quality XI R2 11.5 and newer
•Firstlogic IQ8 8.05c and newer
Those who are using the Firstlogic Data Quality Suite (Job file, RAPID, Library
and/or eDataQuality) cannot use the migration utility to convert the existing
projects into Data Services. The only option is to create the projects again
in Data Services.
1
Some manual steps are required.
2
Some manual steps are required.
14Data Services Migration Considerations
1
2
Why migrate?
You may have seen some literature that includes a comprehensive list of
reasons to migrate. Here are a handful of the main reasons why you should
migrate.
Performance
The new platform utilizes the past Data Integrator features with the improved
Data Quality features in one user interface.
Data profiling of source and target
You can monitor, analyze, and report on the quality of information contained
in the data marts, data warehouses, and any other data stored in databases.
You can test business rules for validity and prioritize data quality issues so
that investments can be made in the high impact areas.
Improved multi-user support
Data Quality to Data Services Migration Guide
Introduction
1
With Data Services, you have access to both a central repository (if
purchased) for multi-user storage and a local repository for each user. Version
control for the repository objects keeps you in control by labeling and
comparing objects. This version includes top-notch security with
authentication to access the central repository, authorization for group-based
permissions to objects, and auditing for changes to each object.
Powerful debugging capabilities
You can set break points, view the data before and after each transform, set
filters when previewing data and save and print the preview data.
Repository management
You can easily manage your fully relational repository across systems and
have the ability to import repository objects from a file. You can also import
source and target metadata for faster UI response times. With datastore
configurations, you can define varying connection options for similar
datastores between environments, use different relational database
technology between environments without changing your jobs, and use
different database owners between systems without making changes during
Data Services Migration Considerations15
Data Quality to Data Services Migration Guide
1
Introduction
migration to each environment. With system configurations, you can associate
substitution configurations per system configuration by associating different
substitution parameter values by environment.
Import and export metadata
You can import and export metadata with Common Warehouse Model (CWM)
1.0/1.1 support and ERWIN (Computer Associates) 4.x XML. You can also
export on Meta Integration Model Bridge (MiMB), if you have it installed.
Auditing
You can audit your projects with statistics collection, rule definitions, email
notification, and audit reporting.
Reports and dashboards
With the reporting tool, you can view daily and historical execution results
and duration statistics. With the data validation dashboard, you can view the
results of validation rules, organize the validation rules across jobs into
functional areas and drill down statistics to a functional area's validation
rules. You can also define high-level business rules based on results of
validation rules.
With impact and lineage analysis, you can understand the cost and impact
of other areas when the datasource is modified. You can view, analyze and
print jobs, work flows, and data flow details, view table/file usage based on
the source and target, view a summary of job variables and parameters,
generate PDF/Word documents on a job-by-job basis, and view a transform
option and field mapping summary.
Introduction to the interface
The Data Services user interface is different from the Data Quality user
interface. It has similar elements, but in a different presentation.
16Data Services Migration Considerations
Data Quality to Data Services Migration Guide
Introduction
1
Note: The window shows a project named my_gsl_proj open on the left
portion of the screen. The right portion shows the GlobalSuggestions
transform input and output fields and the Option groups.
In the upper left corner of the Data Services UI, you can see the Project
Area. You can see your project folders and any jobs that you have. It's a
hierarchical view of the objects used in each project.
Below the Project Area is the is the Local Object Library where you have
access to all of the reusable objects in your jobs. It is a view into your
repository, so that you do not need to access the repository directly. There
are tabs at the bottom so that you can view projects, jobs, work flows, data
flows, transforms, data sources, file formats and functions.
The right side of the window is the workspace. The information presented
here will differ based on the objects you have selected. For example, when
you first open Data Services, you will see a Business Objects banner followed
by Getting Started options, Resources, and Recent Projects. In the example,
the workspace has the GlobalSuggestions transform open to the object editor.
Data Services Migration Considerations17
Data Quality to Data Services Migration Guide
1
Introduction
The editor displays the input and output schemas for the object and the panel
below lists the options for the object.
See the Data Services Designer Guide: Designer User Interface for
information.
Related Topics
•Introduction to the interface on page 16
Downloading blueprints and other content objects
We’ve identified a number of common scenarios that you are likely to perform
with Data Services. Instead of creating your own job from scratch, look
through the blueprints. If you find one that is closely related to your particular
business problem, you can simply use the blueprint and tweak the settings
in the transforms for your specific needs.
For each scenario, we’ve included a blueprint that is already set up to solve
the business problem in that scenario. Each blueprint contains the necessary
Data Services project, jobs, data flows, file formats, sample data, template
tables, and custom functions to run the data flows in your environment with
only a few modifications.
You can download all of the blueprints or only the blueprints and other content
that you think you will find useful from the Business Objects Diamond
Developer website. On the Diamond website, we periodically post new and
updated blueprints, custom functions, best practices, white papers, and other
Data Services content. You can refer to this site frequently for updated content
and use the forums to provide us with any questions or requests you may
have. We've also provided the ability for you to upload and share any content
you've developed with the rest of the Data Services development community.
Instructions for downloading and installing the content objects are also located
on the Diamond website.
1. To access the Business Objects Diamond Developer website, go to
http://diamond.businessobjects.com/dataservices/blueprints in your web
browser.
2. Log in to your Diamond account using your username and password, or
create a new account.
18Data Services Migration Considerations
3. Open the Content Objects User's Guide to view a list of all of the available
blueprints and content objects and their descriptions, and instructions for
downloading and setting up the blueprints.
4. Use the filters at the top of the Data Services Blueprints page to search
for the blueprint or content objects that you want to download.
5. Select the blueprint that you want to download. To download all blueprints,
select Data Quality Blueprints - All.
6. Follow the instructions in the user's guide to download the files to the
appropriate location and make the necessary modifications in Data
Services to run the blueprints.
Introduction to the migration utility
The Data Quality Migration Utility is a Windows-based utility command line
that migrates your Data Quality repository to the Data Services repository.
The utility is in the LINK_DIR\DQMigration folder. It uses an XML-based
configuration file.
You can set options on this Windows-based utility to migrate the entire
repository (recommended) or on a project-by-project or
transform-by-transform basis. You can also set the utility to Analyze Mode
where the utility identifies errors and warning during migration so that you
can either fix them in Data Quality before fully migrating.
Data Quality to Data Services Migration Guide
Introduction
1
After running the utility you can optionally view the Migration Report in a web
broswer for details of possible errors and warnings. We highly recommend
you fix these before trying to run the job in Data Services.
In addition, if your Data Quality jobs were published as Web services, after
running the utility you can publish the migrated jobs as Data Services Web
services. For information on publishing jobs as Web services, see the DataServices Integrator's Guide.
Related Topics
•Running the dqmigration utility on page 29
Data Services Migration Considerations19
Data Quality to Data Services Migration Guide
1
Introduction
•dqmigration utility syntax and options on page 31
Terminology in Data Quality and Data Services
Several terms are different between Data Quality and Data Services.
Data Quality
er/option editor
vices
projectfolder
jobproject
workspacecanvas
data flowdataflow
object editoroption explor-
real timetransactional
sourcereader
DescriptionData Ser-
Terms are different, but it holds the project or job
that runs.
In Data Quality, a project is able to run. In Data
Services, a project is a level higher. The project
contains the job, and the job is able to run.
In Data Quality, you dragged a transform onto a
canvas. In Data Services, you drag a transform
onto a workspace.
In Data Quality, a dataflow is a series of transforms hooked together, that may or may not run.
In Data Services, the data flow includes everything that will extract, transform and load data.
The terms are different, but you do the same
things: set your options.
The terms are different, but they mean the same
thing: processing one or many records at a time,
usually through a web service.
The terms are different, but they mean the same
thing: a place where the incoming data is held.
targetwriter
substitution
variables
substitution
parameters
In Data Quality, you had a few basic layers: a folder, a project, and a dataflow
that contains a series of transforms which may or may not run.
20Data Services Migration Considerations
The terms are different, but they mean the same
thing: a place where the output data is held.
The terms are different, but they mean the same
thing: a text string alias.
In Data Services, the top layer is called a project. The next layer is a job that
runs. The job may hold a work flow which is where you can set up conditional
processing. The work flow, if you use one, will contain the data flow that
contains a series of transforms.
See the Data Services Designer Guide: Designer User Interface for
information.
Naming conventions
Object names
Your objects, when migrated, will have the prefix DQM_. If the name of the
object is longer than 64 characters, then a numeric suffix will be added (for
example, _001) to preserve the unique names.
Data Quality input and output fields have a period in their names. However,
Data Services does not allow a period (.) in the column names. Therefore,
the dqmigration utility replaces the period with an underscore (_).
For example, suppose your Data Quality Reader transform has input field
names input.field1, input.field2, and input.field3. After migration,
these field names become input_field1, input_field2, and input.field3.
Deprecated objects
Differences between Data Quality and Data Services
While this list is not exhaustive, it lists the major differences that you will see
between Data Quality and Data Services.
There are also changes to transform options and option groups. See each
transform section in this document for details.
•Web Services
The .Net deployment is deprecated.
•Match transforms
The Aggregator, Sorter3, Candidate Selector, Match or Associate, Group
Statistics, Unique ID, and Best Record transforms are now included
together in one Match transform. You will also notice the performance
improvement in the Match and UDT transforms.
•GAC transform
Support for Australia, Canada, Global Address, EMEA, Japan and USA
engines. There is also a new Suggestion List option group.
•URAC transform
You can only output one Suggestion Lists output field within URAC.
•Search/Replace transform
The Search/Replace Transform is replaced by a Query transform using
a new search_replace() function call.
3
The Sorter transform only becomes part of the Match transform when it is migrated in a specific
transform order like Sorter, Aggreator and then Match.
22Data Services Migration Considerations
Data Quality to Data Services Migration Guide
Introduction
•Data Cleanse transform
New dictionary connection management window.
•Global Suggestion Lists transform
New Suggestion List Option group.
•Phonetic Key transform
The Phonetic Key transform is replaced by a query transform with either
a double_metaphone() or soundex() function call.
•Substitution variables and files
Substitution variables are now referred to as Substitution parameters.
•Python changes
Several Python methods have been deprecated.
Deprecated objects
The improved technology in Data Services requires the depreciation of certain
aspects of Data Quality.
•Compound Transforms
•Shared options
•Candidate Selector's Unique ID record stem support
•Some options and behaivours related to pre/post SQL operations in the
database Reader and Writer transforms
•UDT's per dataflow mode (use a workflow and scripts as a workaround)
•Disabled transforms
1
Note: Disabled transforms in Data Quality projects are enabled after
migration. If you don't want to the enable the transform, then removed
them prior to migration.
•Flat Files
•Binary file type support in fixed-width files in versions of Data Quality
earlier than 11.7
•Logical and packed field support in versions of Data Quality earlier
than 11.7.
•Data collections
•Thread and watermark settings on a per-transform basis
•Observer transform
Data Services Migration Considerations23
Data Quality to Data Services Migration Guide
1
Introduction
•Progress Service transform
•Integrated batch API
•Admin methods in real-time API
•Netscape and Firefox browsers
•JIS_Encoding for flat files
•Some less popular code page support (most used code pages are
supported)
•Several Python methods
•Web Services .Net deployment
•Several Web Services functions
•Sun Java application server for web tier
Related Topics
•Introduction to the interface on page 16
•Overview of migrated transforms on page 55
Premigration checklist
To ensure a smooth migration, make sure you have completed the following
tasks.
•Upgrade to Data Quality XI 11.7, if possible.
Being on the most current version ensures that the latest options and
functionality are properly installed and named. The options will more
easily map to the Data Services options. Upgrade the repository using
RepoMan.
•Verify that you have permissions to both the Data Quality and Data
Services repositories.
If you don't have a connection to the repositories or permissions to access
the repositories, then you will not be able to migrate to Data Services.
•Back up your Data Quality and Data Services repositories.
Your projects will look different in Data Services. You may want to keep
a backup copy of your repository so that you can compare the Data Quality
and/or Data Services setup with Data Services.
•Clean your repository.
24Data Services Migration Considerations
Data Quality to Data Services Migration Guide
Delete any unused projects or projects that have verification errors.
Projects that do not run on Data Quality XI will not migrate well and will
not run on Data Services without making some changes in Data Services.
Projects that have verification errors due to input or output fields will not
migrate. Remove any custom transforms, compound transforms and
projects that you do not use anymore from the file system repository.
•Verify that your support files are accessible.
If you have a flat file reader or writer, ensure that the corresponding FMT
or DMT file is in the same directory location as the flat file reader or writer.
•Install Data Services.
Follow the installation instructions in the BusinessObjects Data Services
XI 3.0 Installation Guide.
Using the migration tool
Overview of the migration utility
Using the migration tool
1
You invoke the Data Quality migration utility with the dqmigration command
and specify a migration configuration file name. The utility is only available
on Windows. If your repository is on UNIX, you must have a shared system
to the repository, or FTP the repository file to a Windows system prior to
running the utility.
The configuration file specifies the Data Quality repository to migrate from,
the Data Services repository to migrate to, and processing options for the
migration utility. Data Services provides a default migration configuration file
named dqmig.xml in the directory LINK_DIR\DQMigration. You can either
edit this file or copy it to customize it. For details, see Running the dqmigration
utility on page 29.
The value of the LINK_DIR system variable is the path name of the directory
in which you installed Data Services.
The dqmigration utility creates the following files:
•
Migration report in LINK_DIR \DQMigration\mylogpath
Data Services Migration Considerations25
Data Quality to Data Services Migration Guide
1
Using the migration tool
This migration report provides the status of each object that was migrated
and displays the informational, warning, and error messages from the
migration utility. After the dqmigration utility completes, it displays a
prompt that asks you if you want to view the migration report. Always
open the file in Internet Explorer.
•Work files
The dqmigration utility creates a directory LINK_DIR
\DQMigration\work_files that contains the following files. Use these files
if you need to troubleshoot any errors in the migration report.
•Directories configuration_rules_1 and configuration_rules_2 – These
directories contain a copy all of the intermediate XML created during
migration.
•.atl files – These files contain the internal language that Data Services
uses to define objects.
The last step of the dqmigration utility imports the .atl files and creates the
equivalent jobs, data flows, and connections in the Data Services repository.
Related Topics
•Running the dqmigration utility on page 29
•dqmigration utility syntax and options on page 31
•Migration report on page 35
Migration checklist
During migration, follow these steps.
•Complete the steps in the premigration checklist.
•Run the migration utility on your entire repository (recommended) or on
your project that has all verification errors fixed.
•Follow the utility prompts to complete the migration steps.
•Review the view the migration report by selecting to view the report at
the end of the migration.
•If you have errors or warnings that can be fixed in Data Quality 11.7, then
fix them and run the utility again. The files for the repository (or project,
as the case may be) will be overwritten in Data Services when the utility
is rerun.
26Data Services Migration Considerations
•Fix any other errors or warnings in Data Services.
•Follow the recommendations in each transform section to optimize
performance.
•Test the jobs in Data Services and compare the results with Data Quality
results.
•Make changes in Data Services, as appropriate.
After you have your jobs migrated to Data Services, you should set aside
some time to fully analyze and test your jobs in a pre-production environment.
Related Topics
•Premigration checklist on page 24
Connection information
The database connection options may be confusing, especially for
<DATABASE_SERVER_NAME> which may be the name of the server, or
the name of the database. To set your database connection information,
open the dqmig.xml file in the directory LINK_DIR \DQMigration.
Data Quality to Data Services Migration Guide
Using the migration tool
1
Locate the <DI_REPOSITORY_OPTIONS> section.
Based on your database type, you would enter information similar to the
following.
Example: DB2
<DATABASE_TYPE>DB2</DATABASE_TYPE> <!-- Note here that Server name
When you run the dqmigration utility, you can specify the options in one of
the following ways:
•Run the dqmigration utility and specify all options on the command line.
•Specify all options in a configuration file and run the dqmigration utility
and select only the option that references that file on the command line.
•Specify default values for the options in the configuration file and run the
dqmigration utility with some options specified on the command line.
The command line options override the values specified in the
configuration file.
To run the dqmigration utility:
1. Make sure the PATH system environment variable contains
%LINK_DIR%/bin. The utility will not run if it is not there.
2. Set up the configuration file that contains the options for the dqmigration
utility.
For example, create a customized configuration file named
dqmig_repo.xml and copy the contents of file dqmig.xml file to
dqmig_repo.xml.
Using the migration tool
1
3. Specify the information for the Data Quality repository that you want to
migrate.
a. In the DQ_REPOSITORY_OPTIONS section of the configuration file,
specify the following options.
•Absolute path name of your Data Quality repository configuration
file in the <CONFIGURATION_RULES_PATH> option.
•Path name, relative to the absolute path name, of your Data Quality
substitution file in the <SUBSTITUTION_FILE_NAME> option.
Note: Business Objects recommends that when you run the dqmigra
tion utility the first time, you migrate the entire Data Quality repository
instead of an individual project file to ensure that all dependent files
are also migrated. Therefore, do not specify a value in the
<FILE_OR_PATH> option the first time you run the utility. However,
it is possible that after you migrate the entire repository and you fix
errors in the resulting Data Services jobs, you might find an error that
is easier to fix in Data Quality. In this case, you can run the migration
utility on just the project after fixing it in Data Quality.
Data Services Migration Considerations29
Data Quality to Data Services Migration Guide
1
Using the migration tool
b. Specify the information for the Data Services repository to which you
want to migrate.
For example, change the options in the dqmig_repo.xml configuration file
to migrate the Data Quality repository at location D:\dqxi\11_7\repos
itory\configuration_rules to the Data Services repository repo.