DIMigrationConsiderations.

book Page 1 Friday, April 27, 2007 1:20 AM

Data Integrator Migration Considerations

Data Integrator 11.7.2

for Windows and UNIX

DIMigrationConsiderations.book Page 2 Friday, April 27, 2007 1:20 AM

Patents Business Objects owns the following U.S. patents, which may cover products that are offered
and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and
6,289,352.

Trademarks Business Objects owns the following U.S. patents, which may cover products that are offered
and licensed by Business Objects: 5,555,403; 6,247.008 B1; 6,578,027 B2; 6,490,593; and
6,289,352. Business Objects and the Business Objects logo, BusinessObjects, Crystal
Reports, Crystal Xcelsius, Crystal Decisions, Intelligent Question, Desktop Intelligence,
Crystal Enterprise, Crystal Analysis, WebIntelligence, RapidMarts, and BusinessQuery are
trademarks or registered trademarks of Business Objects in the United States and/or other
countries. All other names mentioned herein may be trademarks of their respective owners.

Copyright © 2007 Business Objects. All rights reserved.

Third-party Business Objects products in this release may contain redistributions of software licensed
contributors 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

Date April 26, 2007

DIMigrationConsiderations.book Page 3 Friday, April 27, 2007 1:20 AM

Introduction

Introduction
This document contains, tracks, and briefly describes all behavior changes
associated with the Data Integrator product from version 6.5 through the
latest release. Each behavior change is listed under the version in which the
behavior originated, This document lists behavior changes by release,
starting with the current release and ending with Data Integrator version 6.5.
For the latest Data Integrator technical documentation, consult the Data
Integrator Technical Manuals included with your product.
This Migration Considerations document contains the following sections:
• Behavior changes in version 11.7.2
• Behavior changes in version 11.7.0
• Behavior changes in version 11.6.0
• Behavior changes in version 11.5.1
• Behavior changes in version 11.5.0.0
• Behavior changes in version 11.0.2.5
• Behavior changes in version 11.0.2
• Behavior changes in version 11.0.1.1
• Behavior changes in version 11.0.1
• Behavior changes in version 11.0.0
• Behavior changes in version 6.5.1
• Behavior changes in version 6.5.0.1
• Behavior changes in version 6.5.0.0
• Business Objects information resources
To review Data Integrator documentation for previous releases (including
Release Summaries and Release Notes), visit the Business Objects
Customer Support documentation page at http://
support.businessobjects.com/documentation/.

Behavior changes in version 11.7.2

The following sections describe changes in the behavior of Data Integrator
11.7.2 from previous releases. In most cases, the new version avoids
changes that would cause existing applications to modify their results.
However, under some circumstances a change has been deemed worthwhile
or unavoidable.

Data Integrator Migration Considerations 3

DIMigrationConsiderations.book Page 4 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.7.2

This section includes migration-specific information associated with the

following features:
• Embedded data flows
• Oracle Repository upgrade
• Solaris and AIX platforms

Embedded data flows

In this version of Data Integrator, you cannot create embedded data flows
which have both an input port and an output port. You can create a new
embedded data flow only at the beginning or at the end of a data flow with at
most one port, which can be either an input or an output port.
However, after upgrading to Data Integrator version 11.7.2, embedded data
flows created in previous versions will continue to run.

Oracle Repository upgrade

If you previously upgraded your repository to Data Integrator 11.7.0 and open
the “Object State Report” on the Central repository from the Web
Administrator, you may see the error “ORA04063 view ALVW_OBJ_CINOUT
has errors”. This occurs if you had a pre-11.7.0. Oracle central repository and
upgraded the central repository to 11.7.0.
Note: If you upgraded from a pre-11.7.0.0 version of Data Integrator to
version 11.7.0.0, and you are now upgrading to version 11.7.2.0 (this
release), this issue may occur, and you must follow the instructions below.
Alternatively, if you upgraded from a pre-11.7.0.0 version of Data Integrator to
11.7.2.0 without upgrading to version 11.7.0.0, this issue will not occur, as it is
fixed in 11.7.2.0.
To fix this error, manually drop and recreate the view ALVW_OBJ_CINOUT
using an Oracle SQL editor, such as SQLPlus.
Use the following SQL statements to perform the upgrade:
DROP VIEW ALVW_OBJ_CINOUT;
CREATE VIEW ALVW_OBJ_CINOUT (OBJECT_TYPE, NAME, TYPE,
NORMNAME, VERSION, DATASTORE, OWNER,STATE, CHECKOUT_DT,
CHECKOUT_REPO, CHECKIN_DT,
CHECKIN_REPO, LABEL,
LABEL_DT,COMMENTS,SEC_USER,SEC_USER_COUT) AS
(

4 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 5 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.7.2

select OBJECT_TYPE*1000+TYPE,NAME, N'AL_LANG' ,

NORMNAME,VERSION,DATASTORE, OWNER, STATE, CHECKOUT_DT,
CHECKOUT_REPO, CHECKIN_DT,
CHECKIN_REPO, LABEL, LABEL_DT,COMMENTS,SEC_USER
,SEC_USER_COUT
from AL_LANG L1 where NORMNAME NOT IN ( N'CD_DS_D0CAFAE2' ,
N'XML_TEMPLATE_FORMAT' , N'CD_JOB_D0CAFAE2' , N'CD_DF_D0CAFAE2' ,
N'DI_JOB_AL_MACH_INFO' , N'DI_DF_AL_MACH_INFO' ,
N'DI_FF_AL_MACH_INFO' )
union
select 20001, NAME,FUNC_TYPE ,NORMNAME, VERSION, DATASTORE,
OWNER, STATE, CHECKOUT_DT, CHECKOUT_REPO, CHECKIN_DT,
CHECKIN_REPO, LABEL, LABEL_DT,COMMENTS,SEC_USER
,SEC_USER_COUT
from AL_FUNCINFO F1 where FUNC_TYPE = N'User_Script_Function' OR OWNER
<> N'acta_owner'
union
select 30001, NAME, N'PROJECT' , NORMNAME, VERSION, N'' , N'' , STATE,
CHECKOUT_DT, CHECKOUT_REPO, CHECKIN_DT,
CHECKIN_REPO, LABEL, LABEL_DT,COMMENTS,SEC_USER
,SEC_USER_COUT
from AL_PROJECTS P1
union
select 40001, NAME,TABLE_TYPE, NORMNAME, VERSION, DATASTORE,
OWNER, STATE, CHECKOUT_DT, CHECKOUT_REPO, CHECKIN_DT,
CHECKIN_REPO, LABEL, LABEL_DT,COMMENTS,SEC_USER
,SEC_USER_COUT
from AL_SCHEMA DS1 where DATASTORE <> N'CD_DS_d0cafae2'
union
select 50001, NAME, N'DOMAIN' , NORMNAME, VERSION, DATASTORE, N'' ,
STATE, CHECKOUT_DT, CHECKOUT_REPO, CHECKIN_DT,
CHECKIN_REPO, N'' ,to_date( N'01/01/1970' , N'MM/DD/YYYY' ), N'' ,SEC_USER
,SEC_USER_COUT
from AL_DOMAIN_INFO D1
);

Data Integrator Migration Considerations 5

DIMigrationConsiderations.book Page 6 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.7.0

Solaris and AIX platforms

Data Integrator 11.7.2 on Solaris and AIX platforms is a 64-bit application and
requires 64-bit versions of the middleware client software (such as Oracle and
SAP) for effective connectivity. If you are upgrading to Data Integrator 11.7.2
from a previous version, you must also upgrade all associated middleware
client software to the 64-bit version of that client. You must also update all
library paths to ensure that Data Integrator uses the correct 64-bit library
paths.

Behavior changes in version 11.7.0

The following sections describe changes in the behavior of Data Integrator
11.7.0. from previous releases. In most cases, the new version avoids
changes that would cause existing applications to modify their results.
However, under some circumstances a change has been deemed worthwhile
or unavoidable.
This section includes migration-specific information associated with the
following features:
• Data quality
• Distributed data flows
• JMS Adapter interface
• XML Schema enhancement
• Password management
• Web applications
• Web services

Data quality
Data Integrator now integrates the BusinessObjects Data Quality XI
application for your data quality (formerly known as Data Cleansing) needs,
which replaces Firstlogic’s RAPID technology.
Note the following changes to data cleansing in Data Integrator:
• Depending on the Firstlogic products you owned, you previously had up
to three separate transforms that represented data quality functionality:
Address_Enhancement, Match_Merge, and Name_Parsing.

6 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 7 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.7.0

Now, the data quality process takes place through a Data Quality
Project. To upgrade existing data cleansing data flows in Data Integrator,
replace each of the cleansing transforms with an imported Data Quality
Project using the Designer.
You must identify all of the data flows that contain any data cleansing
transforms and replace them with a new Data Quality Project that
connects to a Data Quality blueprint or custom project.
• Data Quality includes many example blueprints - sample projects that are
ready to run or can serve as a starting point when creating your own
customized projects. If the existing blueprints do not completely suit your
needs, just save any blueprint as a project and edit it. You can also create
a project from scratch.
• You must use the Project Architect (Data Quality’s graphical user
interface) to edit projects or create new ones. Business Objects strongly
recommends that you do not attempt to manually edit the XML of a
project or blueprint.
• Each imported Data Quality project in Data Integrator represents a
reference to a project or blueprint on the data quality server. The Data
Integrator Data Quality projects allow field mapping.
To migrate your data flow to use the new Data Quality transforms
1. Install Data Quality XI, configure and start the server. For installation
instructions, see your Data Quality XI documentation.
Note: You must start the server before using Data Quality XI with Data
Integrator.
2. In the Data Integrator Designer, create a new Business Objects Data
Quality datastore and connect to your Data Quality server.
3. Import the Data Quality projects that represent the data quality
transformations you want to use. Each project appears as a Data Quality
project in your datastore. For the most common data quality
transformations, you can use existing blueprints (sample projects) in the
Data Quality repository
4. Replace each occurrence of the old data cleansing transforms in your
data flows with one of the imported Data Quality transforms. Reconnect
the input and output schemas with the sources and targets used in the
data flow.
Note: If you open a data flow containing old data cleansing transforms
(address_enhancement, name_parsing, match_merge), Data Integrator
displays the old transforms (even though they no longer appear in the object
library). You can even open the properties and see the details for each old
transform.

Data Integrator Migration Considerations 7

DIMigrationConsiderations.book Page 8 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.7.0

If you attempt to validate a data flow that contains an old data cleansing
transform, Data Integrator throws an error. For example:
[Custom Transform:Address_Enhancement] BODI-1116074: First Logic support is
obsolete. Please use the new Data Quality feature.
If you attempt to execute a job that contains data flows using the old data
cleansing transforms Data Integrator throws the same type of error.
Contact Business Objects Customer Support at http://
support.businessobjects.com/ if you need help migrating your data cleansing
data flows to the new Data Quality transforms.

Distributed data flows

After upgrading to this version of Data Integrator, existing jobs have the
following default values and behaviors:
• Job distribution level: Job
All data flows within a job will be run on the same job server.
• The cache type for all data flows: In-memory type
Uses STL map and applies to all join caches, table comparison
caches and lookup caches, and so forth.
• Default for Collect statistics for optimization and Collect statistics
for monitoring: deselected.
• Default for Use collected statistics: selected.
Since no statistics are initially collected, Data Integrator will not initially
use statistics.
• Every data flow is run as a process (not as a sub data flow process).
New jobs and data flows you create using this version of Data Integrator have
the following default values and behaviors:
• Job distribution level: Job.
• The cache type for all data flows: Pageable.
• Collect statistics for optimization and Collect statistics for
monitoring: deselected.
• Use collected statistics: selected.
If you want Data Integrator to use statistics, you must collect statistics
for optimization first.
• Every data flow is run as a single process. To run a data flow as
multiple sub data flow processes, you must use the Data_Transfer
transform or select the Run as a separate process option in
transforms or functions.

8 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 9 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.7.0

• All temporary cache files are created under the

LINK_DIR\Log\PCache directory. You can change this option from the
Server Manager.

JMS Adapter interface

A new license key may be required to install the JMS Adapter interface. If you
have a license key issued prior to Data Integrator XI R2 version 11.5.1, send
a request to licensing@businessobjects.com with “Data Integrator License
Keys” as the subject line.

XML Schema enhancement

Data Integrator 11.7 adds the new Include schema location option for XML
target objects. This option is selected by default.
Data Integrator 11.5.2 provided the key
XML_Namespace_No_SchemaLocation for section AL_Engine in the
Designer option Tools > Options > Job Server > General, and the default
value, FALSE, indicates that the schema location is included. If you upgrade
from 11.5.2 and had set XML_Namespace_No_SchemaLocation to TRUE
(indicates that the schema location is NOT included), you must open the XML
target in all data flows and clear the Include schema location option to keep
the old behavior for your XML target objects.

Password management
Data Integrator now encrypts all password fields using two-fish algorithm.
To simplify updating new passwords for the repository database, Data
Integrator includes a password file feature. If you do not have a requirement
to change the password to the database that hosts the repository, you may
not need to use this optional feature.
However, if you must change the password (for example, security
requirements stipulate that you must change your password every 90 days),
then Business Objects recommends that you migrate your scheduled or
external job command files to use this feature.
Migration requires that every job command file be regenerated to use the
password file. After migration, when you update the repository password, you
need only regenerate the password file. If you do not migrate using the
password file feature, then you must regenerate every job command file
every time you change the associated password.

Data Integrator Migration Considerations 9

DIMigrationConsiderations.book Page 10 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.6.0

Web applications
• The Data Integrator Administrator (formerly called the Web Administrator)
and Metadata Reports interfaces have been combined into the new
Management Console in Data Integrator 11.7. Now, you can start any
Data Integrator Web application from the Management Console launch
pad (home page). If you have created a bookmark or favorite that points
to the previous Administrator URL, you must update the bookmark to
point to http://computername:port/diAdmin.
• If in a previous version of Data Integrator you generated WSDL for Web
service calls, you must regenerate the WSDL because the URL to the
Administrator has been changed in Data Integrator 11.7.

Web services
Data Integrator is now using Xerces2 library. When upgrading to 11.7 or
above and configuring the Web Services adapter to use the xsdPath
parameter in the Web Service configuration file, delete the old Web Services
adapter and create a new one. It is no longer necessary to configure the
xsdPath parameter.

Behavior changes in version 11.6.0

Data Integrator version 11.6.0.0 will only support automated upgrade from
ActaWorks and Data Integrator versions 5.2.0 and above to version 11.5. For
customers running versions prior to ActaWorks 5.2.0 the recommended
migration path is to first upgrade to Data Integrator version 6.5.1.
If you are upgrading to 11.6.0.0, to take advantage of the new Netezza bulk-
loading functionality, you must upgrade your repository.
If you are upgrading from Data Integrator versions 11.0.0 or older to Data
Integrator 11.6.0.0, you must upgrade your repository. If upgrading from
11.5.0 to 11.6.0.0, you must upgrade your repository to take advantage of the
new:
• Data Quality Dashboards feature
• Preserving database case feature
• Salesforce.com Adapter Interface (delivered with version 11.5 SP1
Adapter Interfaces)

10 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 11 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.6.0

The following sections describe changes in the behavior of Data Integrator

from previous releases. In most cases, the new version avoids changes that
would cause existing applications to modify their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.
This section includes:
• Netezza bulk loading
• Conversion between different data types

Netezza bulk loading

If you are upgrading to 11.6.0.0, to take advantage of the new Netezza bulk-
loading functionality, follow this procedure:
To enable Netezza bulk loading
1. Upgrade your repository to version 11.6.0.0.
2. In the Designer, for each ODBC datastore that uses a Netezza data
source:
a. Right-click the datastore and click Edit to open the datastore editor.
b. Click OK.
This procedure verifies the connection to the database. If you receive a
connection error:
a. Open the ODBC Administrator.
b. Select the data source name.
c. Click Configure.
d. Click Test Connection.
e. Correct any connection errors.
f. Right-click the datastore and click Edit to open the datastore editor.
g. Click OK.
3. In the Designer, for each Netezza job:
a. Open the job so it appears in the workspace.
b. Click the Save All button.
This procedure causes Data Integrator to set the default options in the
jobs.

Data Integrator Migration Considerations 11

DIMigrationConsiderations.book Page 12 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.5.1.5

If you only upgrade the repository and do not perform the other steps, then
the Bulk Loader Options tab for Netezza targets and the new options in the
datastore editor won’t be visible. However, Data Integrator still automatically
employs bulk loading unless one or more of the following options have values
set on the Netezza target table editor Options tab:
• Ignore columns with value
• Ignore columns with null
• Any Error handling options
• Any Transaction control options

Conversion between different data types

For this release, there is a change in behavior for data conversion between
different data types. Previously, if an error occurred during data conversion
(for example when converting a varchar string to an integer, the varchar string
contains non-digits), the result was random. Now, the return value will be
NULL for any unsuccessful conversion.
Previously Data Integrator returned random data for the result of a varchar to
datetime conversion when the varchar string contains an illegal date format.
Now, the return value will be NULL.

Behavior changes in version 11.5.1.5

Data Integrator version 11.5.1.5 supports only automated upgrade from
ActaWorks and Data Integrator versions 5.2.0 and above to version 11.5. For
customers running versions prior to ActaWorks 5.2.0 the recommended
migration path is to first upgrade to Data Integrator version 6.5.1.
If you are upgrading to 11.5.1.5, to take advantage of the new Netezza bulk-
loading functionality, you must upgrade your repository.
If you are upgrading from Data Integrator versions 11.0.0 or older to Data
Integrator 11.5.1.5, you must upgrade your repository. If upgrading from
11.5.0 to 11.5.1.5, you must upgrade your repository to take advantage of
these features:
• Data Quality Dashboards
• Preserving database case
• Salesforce.com Adapter Interface (delivered with version 11.5 SP1
Adapter Interfaces)

12 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 13 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.5.1

Behavior changes in version 11.5.1

No new behavior changes in this release.

Behavior changes in version 11.5.0.0

Data Integrator version 11.5 will only support automated upgrade from
ActaWorks and Data Integrator versions 5.2.0 and above to version 11.5. For
customers running versions prior to ActaWorks 5.2.0 the recommended
migration path is to first upgrade to Data Integrator version 6.5.1.
If you are upgrading from Data Integrator version 11.0.0 to Data Integrator
version 11.5.0.0, you must upgrade your repository.
The following sections describe changes in the behavior of Data Integrator
from previous releases. In most cases, the new version avoids changes that
would cause existing applications to modify their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.
This section includes:
• Web Services Adapter
• Varchar behavior
• Central Repository

Web Services Adapter

Newer versions of Data Integrator will overwrite the XSD that defines the
input and output message files. Data Integrator stores those XSDs in a
Tomcat directory and during Metadata import passes to the engine a URL to
the XSDs. The engine expects the XSDs to be available at run time.
To avoid this issue, prior to installing Data Integrator version 11.5, save a copy
of your LINKDIR\ext\webservice contents. After installing the new version of
Data Integrator, copy the directory contents back in place. If you do not follow
this procedure, the web service operations will require re-import from the web
service datastore after the installation completes.

Varchar behavior
Data Integrator 11.5.0 and above conforms to ANSI SQL-92 varchar
behavior. When you upgrade Data Integrator and save your previous
configurations, Data Integrator uses the previous varchar behavior as the

Data Integrator Migration Considerations 13

DIMigrationConsiderations.book Page 14 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.5.0.0

default. However, Business Objects recommends that you use the ANSI
varchar behavior because the previous varchar behavior will not be
supported in future Data Integrator versions.
To change from the previous varchar behavior to the ANSI varchar
behavior
1. In the Data Integrator Designer, click Tools > Options > Job Server >
General
2. Enter al_engine for Section, ANSI_VARCHAR_BEHAVIOR for Key, and
TRUE for Value.
3. Click OK.
4. If you want your jobs and work flows from a previous version of Data
Integrator to use the ANSI varchar behavior, you must make changes in
the following areas:
• NULLs and empty strings in scripts and script functions
• Trailing blanks in sources and functions
• NULLs, empty strings, and trailing blanks in transforms
For details about the changes in these areas and a comparison of the
prior behavior and the varchar ANSI behavior, please contact Business
Objects Technical Support at Business Objects Customer Support at
http://www.techsupport.businessobjects.com/ (requires registration).

Central Repository
Business Objects recommends the following guidelines to upgrade your
central repository when installing a new version of Data Integrator.
• Maintain a separate central repository for each Data Integrator version to
preserve object history.
An upgrade of the central repository might override the versions of any
object whose internal representation (ATL) has changed in the new
release.
To preserve the current ATL of objects and their history
1. Create a new central repository on the current Data Integrator
release and export the latest version of all objects and their
dependents from the existing central repository to the new central
repository.
2. Install the new Data Integrator release and upgrade the new central
repository to the new Data Integrator release.

14 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 15 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.0.2.5

3. Keep the existing central repository to maintain the history of the

objects in the current release.
4. Use the new central repository for objects that you create in the new
release.
• Upgrade the central repository and local repositories at the same time, if
possible.
A central repository might not work with a local repository that is on a
different Data Integrator release. You might not be able to perform multi-
user operations between a central repository and a local repository that
are on different Data Integrator versions. Therefore, upgrade the central
repository and local repositories to the same Data Integrator version at
the same time.
• If it is not convenient to upgrade the central and local repositories at the
same time, check in all objects before you upgrade the central repository.
Check in all objects (or undo the check-outs if objects have not been
modified after check-out), especially those objects that were checked out
to the local repositories that will not be upgraded at the same time. After
you upgrade the central repository the new Data Integrator version, you
will not be able to check in any objects from the local repository of an
older Data Integrator version.

Behavior changes in version 11.0.2.5

The following sections describe changes in the behavior of Data Integrator
from previous releases. In most cases, the new version avoids changes that
would cause existing applications to change their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.

Teradata named pipe support

Beginning with Data Integrator version 11.0.2.5, you can use named pipes to
bulk load data into Teradata databases. When Data Integrator tries to connect
to the pipes, Teradata Warehouse Builder might not yet have created the
pipes. Data Integrator waits one second and retries to connect, up to 30
seconds. If you need to change the 30-second wait time, go to the Designer
select Tools > Options > Job Server > General window, enter al_engine for
Section, enter NamedPipeWaitTime for Key, and enter a different value.

Data Integrator Migration Considerations 15

DIMigrationConsiderations.book Page 16 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.0.2

If you use Warehouse Builder and Teradata Tools and Utilities version 7.0 or
7.1, go to the Data Integrator Designer Tools > Options > Job Server >
General window, enter al_engine for Section, enter PreTWB5_Syntax for Key,
and set the value to TRUE.

Behavior changes in version 11.0.2

No new behavior changes in this release.

Behavior changes in version 11.0.1.1

The following sections describe changes in the behavior of Data Integrator
from previous releases. In most cases, the new version avoids changes that
would cause existing applications to change their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.

Statistics repository tables

The repository tables AL_FLOW_STAT and AL_JOB_STAT are no longer
populated for job, work flow, or data flow statistics. These two tables no longer
exist in the newly created Data Integrator version 11.0.1 repositories. They
may still exist in the repositories that are upgraded to version 11.0.1.
Beginning with Data Integrator version 11.0.1, all job, work flow, and data flow
statistics are stored in the AL_HISTORY, AL_HISTORY_INFO, and
AL_STATISTICS tables. In particular, the job statistics, previously stored in
AL_JOB_STAT, are now stored in the AL_HISTORY and AL_HISTORY_INFO
tables. The work flow and data flow statistics, previously stored in
AL_FLOW_STAT are now stored in the AL_STATISTICS table. Use the
metadata reporting tool to retrieve all job, work flow and data flow statistics.

Behavior changes in version 11.0.1

Data Integrator version 11.0 will only support automated upgrade from
ActaWorks and Data Integrator versions 5.2.0 and above to version 11.0. For
customers running versions prior to ActaWorks 5.2.0 the recommended
migration path is to first upgrade to Data Integrator version 6.5.1.
If you are upgrading from Data Integrator version 11.0.0 to Data Integrator
version 11.0.1, you must upgrade your repository to use the following
features:

16 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 17 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.0.1

• Sybase IQ as a source or target

• New Data Integrator functions:
• replace_substr_ext
• long_to_varchar
• varchar_to_long
• load_to_xml
• extract_from_xml
• match_pattern
• match_regex
• literal
• Generate delete row types in table comparison transform
• COBOL data file reader
• Impact Analysis in Metadata Reports for BusinessObjects XI
• Auditing (some additional functionality was introduced in version 11.0.1)
The following sections describe changes in the behavior of Data Integrator
from previous releases. In most cases, the new version avoids changes that
would cause existing applications to change their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.

Crystal Enterprise adapters

After installing a new version of Business Objects, you might receive a class
not found error when trying to start Crystal Enterprise adapter. Update the
Crystal Enterprise adapter configuration by updating the
<BOProductName>BusinessObjects directory name in the classpath for both
the Crystal Enterprise adapter and the DMAC command file.
To update classpaths
1. Locate the new jar files. The default locations are:
Crystal Enterprise 10: C:\Program Files\Common Files\Crystal
Decisions\2.5\java\lib
BusinessObjects XI: C:\Program Files\Common Files\ Business
Objects\3.0\java\lib
2. For the Crystal Enterprise Adapter:
a. To ensure any new adapter instances have the correct classpath,
modify LINK_DIR\adapters\install\CrystalAdaper.xml with the new jar
file location. Modify the element <adapter3PartyJarFiles> by globally

Data Integrator Migration Considerations 17

DIMigrationConsiderations.book Page 18 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.0.0

changing the path to the new jar files for Crystal Enterprise 10 (see
the default location noted in the previous step) to that of the
BusinessObjects XI path.
b. Save the file. Any future adapter instances created will now have the
correct jar file path.
c. Change any configured adapter instances by deleting the configured
adapter instance and creating a new one using the same adapter
instance name, which keeps all adapter usage valid.
3. For the DMAC command file launched by the DMAC wizard:
a. Edit LINK_DIR\ext\dmac\wizard.com.
b. Change the entry set CE_JARS_DIR= to point to the new path. For
example, if you installed BusinessObjects XI, the line should read:
set CE_JARS_DIR=C:\Program Files\Common Files\Business
Objects\3.0\java\lib

Behavior changes in version 11.0.0

Data Integrator version 11.0 will only support automated upgrade from
ActaWorks and Data Integrator versions 5.2.0 and above to version 11.0. For
customers running versions prior to ActaWorks 5.2.0 the recommended
migration path is to first upgrade to Data Integrator version 6.5.1.
The following sections describe changes in the behavior of Data Integrator
from previous releases. In most cases, the new version avoids changes that
would cause existing applications to change their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.
This section includes:
• Changes to code page names
• Data Cleansing
• License files and remote access software
• Administrator Users

Changes to code page names

Starting with Version 11.0, Data Integrator displays some code pages with
different names. For example, code page MS1252 displays as CP1252.
Additionally, two code pages are no longer supported. These changes are

18 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 19 Friday, April 27, 2007 1:20 AM

Behavior changes in version 11.0.0

visible only in the list locales screens (in installer, datastore and file-formats).
The Data Integrator engine does not have any upgrade issues and
understands the old code page name.

Old codepage name New Name (Data Integrator version 11.0 and later)
iso885910 Not supported
MS949 CP949
MS950 CP950
MS1250 CP1250
MS1251 CP1251
MS1253 CP1253
MS1254 CP1254
MS1255 CP1255
MS1257 CP1257
MS874 CP874
MS1258 CP1258
MS1361 Not Supported
USASCII US-ASCII

Data Cleansing
The new Data Integrator installation will overwrite all template job files
shipped with Data Integrator with the upgraded job files compatible with
Firstlogic 7.50. If the user had manually modified the template job files with
Data Integrator version 6.5 and wants to preserve the changes, Business
Objects recommends that a copy is made of the job file, or that the job file is
renamed, prior to installing Data Integrator version 11.0.
After installing Data Integrator version 11.0 and the Firstlogic 7.5 suite, you
should do the following:
• From the Data Integrator CD, copy pwdiqjob.upd from the \Utilities
directory to the dtr_iq directory. Click Yes to overwrite existing file.
• For all your job templates, run Firstlogic's edjob utility to upgrade your
Firstlogic job files from the previous version to 7.50. Find the edjob utility
under the installation of Firstlogic. Run the utility to upgrade all jobs of the

Data Integrator Migration Considerations 19

DIMigrationConsiderations.book Page 20 Friday, April 27, 2007 1:20 AM

Behavior changes in version 6.5.1

same extension by specifying *.<extension> in the utility. Extension

names are “diq”, “iac”, and “mpg”. For instructions on how to use the
edjob utility, refer to Firstlogic documentation.
Note: If the jobs have already been updated to 7.50c (using the .upd file sent
with the master install with edjob), you will receive the following error when
trying to open a 7.50 job: Error: The “Report Defaults” block, occurrence 1,
has an incorrect number of lines and the job cannot be loaded.
These jobs will need to be manually edited to change the version string in the
General block from 7.50c to 7.10c. Then edjob can be rerun with the correct
.upd file.
For all job templates created under the address enhancement application,
manually edit the job templates using an editor such as Notepad, and
comment out the “Create Output File” block by adding the '*' character at the
beginning of the line. For example:
*BEGIN Create Output File

License files and remote access software

In release 6.0 and higher, Data Integrator includes a specific change to
license support when activating Data Integrator components across a
terminal server, such as PC Anywhere or Terminal Services Client. You must
request new license files to use release 6.x or above when using a terminal
server. Specifically, you require:
• New Designer licenses to use a terminal server to initiate a Designer
session across a terminal server connection (when using evaluation or
emergency licenses, or node-locked licenses)
• New Job Server and Access Server licenses to open the Service
Manager Utility across a terminal server connection (when using any type
of license)
If you do not make the license change, you may see the error “Terminal
Server remote client not allowed.” If you require terminal services contact
licensing@businessobjects.com.

Behavior changes in version 6.5.1

The following sections describe changes in the behavior of Data Integrator
from previous releases. In most cases, the new version avoids changes that
would cause existing applications to change their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.

20 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 21 Friday, April 27, 2007 1:20 AM

Behavior changes in version 6.5.0.1

Informix native client support

If you created an Informix repository and datastores with a previous Data
Integrator release using DataDirect Technologies Connect ODBC driver, they
are not compatible with Data Integrator 6.5.1. You must recreate your
repository, datastores, and jobs if you want to use the Informix native driver.

Behavior changes in version 6.5.0.1

The following sections describe changes in the behavior of Data Integrator
from previous releases. In most cases, the new version avoids changes that
would cause existing applications to change their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.
This section includes:
• Web services support
• Sybase bulk loader library on UNIX

Web services support

When using Data Integrator with Web services, the following limitations exist:
SAP R/3 IDoc message sources in real-time jobs are not supported
The Data Integrator Web services server uses the first Job Server in the
list of those available for a batch job. The first Job Server might be a
server group.
If you are using Web services and upgrading to version 6.5.0.1, Web
services server (call-in) functionality that you created with previous
versions of Data Integrator is not supported. Perform the following
changes to manually upgrade the Web services server:
• Regenerate a WSDL file
Prior to release 6.5.0.1, every batch job and real-time service
configured in Data Integrator was published in the WSDL file. In
release 6.5.0.1, Data Integrator only publishes batch jobs and real-
time services that you select. Clients that call Data Integrator using
Web services will fail until you authorize the jobs and services being
invoked. Consult Data Integrator technical manuals for instructions
about how to select jobs, enable security, and generate a WSDL file
for a Web services server.

Data Integrator Migration Considerations 21

DIMigrationConsiderations.book Page 22 Friday, April 27, 2007 1:20 AM

Behavior changes in version 6.5.0.0

• Change SOAP calls to match those in the 6.5.0.1 version.

A session ID is not included in SOAP messages unless you enable
security for the Web services server. Prior to release 6.5.0.1, the
sessionID message part was published in every SOAP message.
To fix this problem, change SOAP calls to match those in the 6.5.0.1
version of the WSDL file.
• If security is off, remove the sessionID line from the SOAP input
message.
• If security is on, copy the sessionID from the SOAP body to the
SOAP header as a session ID now appears in the SOAP header
instead of the body.
Note: When you install 6.5.0.1, the installer automatically upgrades
the Web Services Adapter and your existing Web services clients will
function properly.

Sybase bulk loader library on UNIX

The installed Sybase client on UNIX platforms does not include the Sybase
bulk loader dynamic shared library that Data Integrator requires. Please refer
to the README in either the CDROM Location/unix/PLATFORM/AWSybase
directory or the $LINK_DIR/AWSybase directory for instructions about how to:
• Confirm that the library is available in the Sybase client installation
• Build the library

Behavior changes in version 6.5.0.0

The following sections describe changes in the behavior of Data Integrator
from previous releases. In most cases, the new version avoids changes that
would cause existing applications to change their results. However, under
some circumstances a change has been deemed worthwhile or unavoidable.
This section includes:
• Browsers must support applets and have Java enabled
• Execution of to_date and to_char functions
• Changes to Designer licensing
• License files and remote access software
• Administrator Repository Login
• Administrator Users

22 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 23 Friday, April 27, 2007 1:20 AM

Behavior changes in version 6.5.0.0

Browsers must support applets and have Java enabled

The Administrator and the Metadata Reporting tool require support for Java
applets, which is provided by the Java Plug-in. If your computer does not
have the Java Plug-in, you must download it and make sure that your security
settings enable Java to run in your browser. Business Objects recommends
you use Java Plug-in 1.3.1.
To find a plug-in go to: http://java.sun.com/products/plugin/downloads/
index.html.

Execution of to_date and to_char functions

Prior to release 6.0, Data Integrator did not always push the functions
to_date and to_char to the source database for execution when it was
possible based on the data flow logic. The fix for this improved optimization
requires that the data format specified in the function match the format of the
extracted data exactly. The result can be significant performance
improvement in flows that use these functions.
It may be that your existing function calls do not require a change because
the format already matches the data being extracted. If the formats do not
match, this change is required. If your function calls do not correspond to this
new format requirement, you will see an error at runtime.
Compare the examples below with your to_date or to_char function calls
to determine if a change is needed.
For example, the WHERE clause of the query transform in the
DF_DeltaSalesOrderStage of the Customer Order Rapid Mart (was
eCache) includes the following function calls:
WHERE (to_date(to_char(SALES_ORDER_XACT.LOAD_DATE, 'YYYY.MM.DD
HH24:MI:SS'), YYYY.MM.DD')
= to_date(to_char($LOAD_DATE, 'YYYY.MM.DD HH24:MI:SS'),
'YYYY.MM.DD'))
To support this chance, change the WHERE clause to the following:
WHERE (to_date(to_char(SALES_ORDER_XACT.LOAD_DATE,
'YYYY.MM.DD'), 'YYYY.MM.DD')
= to_date(to_char($LOAD_DATE, 'YYYY.MM.DD'), 'YYYY.MM.DD'))
Also, in the Sales Rapid Mart in the DF_SALESOrderHistory data flow, in
the mapping column, VALID_FROM is set as:
to_date(to_char($G_LOAD_DATE, 'YYYY.MM.DD HH24:MI:SS'),
'YYYY.MM.DD')
To support this change, the mapping needs to be changed to:
to_date(to_char($G_LOAD_DATE, 'YYYY.MM.DD'), 'YYYY.MM.DD')

Data Integrator Migration Considerations 23

DIMigrationConsiderations.book Page 24 Friday, April 27, 2007 1:20 AM

Behavior changes in version 6.5.0.0

Similarly, the SELECT list of the ConvertTimes query transform in the

DF_Capacity_WorkCenter data flow of the Profitability Rapid Mart,
contains the following function call(s):
to_date(to_char($G_LOAD_DATE, 'YYYY.MM.DD') || '00:00:00'),
'YYYY.MM.DD HH.MI.SS')
Change the function calls to:
to_date((to_char($G_LOAD_DATE, 'YYYY.MM.DD') || '<space>00:00:00'),
'YYYY.MM.DD H24:MI:SS')

Changes to Designer licensing

Data Integrator Designer version 6.5 does not support floating licenses. If you
are currently using floating Designer licenses, obtain a new license key
before upgrading. Send your request to licensing@businessobjects.com with
Data Integration License Keys as the subject line. The new key will be added
to your existing License Authorization Code.
For more information, see the Online Customer Support site at http://
www.techsupport.businessobjects.com. Search for the Article titled “Business
Objects Data Integrator 6.5: Changes to Designer License Keys Q&A.”

License files and remote access software

In release 6.0 and higher, Data Integrator includes a specific change to
license support when activating Data Integrator components across a
terminal server, such as PC Anywhere or Terminal Services Client. You must
request new license files to use release 6.x when using a terminal server.
Specifically, you require:
• New Designer licenses to use a terminal server to initiate a Designer
session across a terminal server connection (when using evaluation or
emergency licenses, or node-locked licenses)
• New Job Server and Access Server licenses to open the Service
Manager Utility across a terminal server connection (when using any type
of license)
If you do not make the license change, you may see the error “Terminal
Server remote client not allowed.” If you require terminal services contact
licensing@businessobjects.com.

24 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 25 Friday, April 27, 2007 1:20 AM

Behavior changes in version 6.5.0.0

Administrator Repository Login

In release 6.0 and higher, in the Data Integrator Administrator, all the
repository connectivity occurs using JDBC and hence the previous
connectivity information is either invalid or incomplete. When you use the
Administrator, you will need to re-register all of your repositories.
Use the following connection information guidelines:

Database Connection Description

Type Field
All types Repository Any logical name.
name
Machine name Machine name on which the database server is running
Port Port on which the database server is listening. The
Administrator provides default values; if you do not know
the port number, use the default.
Oracle Service name/ The database instance name to connect to. Depending on
SID whether you are using an 8.0.2 or 8i database, it is either
the SID or the Service name.
DB2 Datasource Datasource name as configured in DB2 client configuration
utility. This is the same as in previous Administrator or
Designer connections.
Sybase Database Database instance name.
name
Microsoft Database Database instance name.
SQL name
Server
Informix Server name The name of the machine on which the server is running.
Database The name of the database instance running on the Server.
name

Administrator Users
Administrator user configuration information in ActaWorks version 5.x was
saved in a primary repository. When you upgrade to Data Integrator version
6.x, this information is lost. You must reconfigure your Administrator users
manually.

Data Integrator Migration Considerations 25

DIMigrationConsiderations.book Page 26 Friday, April 27, 2007 1:20 AM

Business Objects information resources

Business Objects information resources

Business Objects offers a full documentation set covering its products and
their deployment. Additional support and services are also available to help
maximize the return on your business intelligence investment. The following
sections detail where to get Business Objects documentation and how to use
the resources at Business Objects to meet your needs for technical support,
education, and consulting.

Documentation
You can access electronic documentation at any time from the product
interface, the web, or from your product CD.

Documentation on the web

The full electronic documentation set is available to customers on the web
from the Customer Support web site at: http://support.businessobjects.com/
documentation/.

Documentation on the product CD

Look in the Doc directory of your product CD or installation directory for
guides in Adobe Acrobat PDF format.

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is
there something you particularly like or have found useful? Drop us a line,
and we will do our best to ensure that your suggestion is included in the next
release of our documentation: documentation@businessobjects.com.
Note: If your issue concerns a Business Objects product and not the, please
contact our Customer Support experts at http://support.businessobjects.com.

Customer support, consulting, and training

A global network of Business Objects technology experts provides customer
support, education, and consulting to ensure maximum business intelligence
benefit to your business.

26 Data Integrator Migration Considerations

DIMigrationConsiderations.book Page 27 Friday, April 27, 2007 1:20 AM

Business Objects information resources

Data Integrator Community

The Business Objects developer community is an interactive Web site where
you will find technical resources to help you better use your Business Objects
software. Here you can interact with others and provide feedback on
Business Objects software, technical content, and the Web site.
http://diamond.businessobjects.com/EIM/DataIntegrator

Customer support centers

Business Objects offers customer support plans to best suit the size and
requirements of your deployment. We operate customer support centers in
the following countries:
• USA
• Australia
• Canada
• United Kingdom
• Japan

Online Customer Support

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://support.businessobjects.com/

Consultation
Business Objects consultants can accompany you from the initial analysis
stage to the delivery of your deployment project. Expertise is available in
relational and multidimensional databases, connectivities, database design
tools, customized embedding technology, and more.
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/

Training
From traditional classroom learning to targeted e-learning seminars, we 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

Data Integrator Migration Considerations 27

DIMigrationConsiderations.book Page 28 Friday, April 27, 2007 1:20 AM

Business Objects information resources

Useful addresses at a glance

Address Content
Business Objects product Information about the full range of
information Business Objects products.
http://www.businessobjects.com
Product documentation Business Objects product
http://support.businessobjects.com/ documentation, including the
documentation Business Objects Product
Document Map and the most
current information on platfrom
support.
Business Objects Documentation Send us feedback or questions
mailbox about documentation.
documentation@businessobjects.com
Online Customer Support Information on Customer Support
http://support.businessobjects.com programs, as well as links to
technical articles, downloads, and
online forums.
Business Objects Consulting Information on how Business
Services Objects can help maximize your
http://www.businessobjects.com/ business intelligence investment.
services/consulting/
Business Objects Education Information on Business Objects
Services training options and modules.
http://www.businessobjects.com/
services/training

28 Data Integrator Migration Considerations