PUBLIC

SAP Data Services

Document Version: 4.3 (14.3.00.00) – 2024-03-25

Upgrade Guide
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 What's in this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 Naming conventions and variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Upgrade prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Upgrade considerations for SAP Data Services 4.3 Support Packages. . . . . . . . . . . . . . . . . . . .11

4 Choose BI or IPS platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

5 Update SAP transport files and SAP authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6 JDBC and ODBC drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

7 Upgrade scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

7.1 Upgrading from Data Services 4.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installing without uninstalling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing by first uninstalling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

8 Scenario: Migrate Data Services to a new environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8.1 Backing up existing configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.2 Installing IPS and Data Services on the new server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.3 Migrating CMS content using Promotion Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.4 Migrating Data Services repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
8.5 Migrate Data Services configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Migrating adapter configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Migrating the admin.xml configuration file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Migrating the Access Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8.6 Verifying the upgrade process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

9 Data Services behavior changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

9.1 Behavior changes in version 14.3.03.00. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Multi-subnet failover and column encryption for SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.2 Behavior changes in version 14.3.01.00. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Multi-subnet failover enabled by defult for SQL Server repository. . . . . . . . . . . . . . . . . . . . . . . . 34
9.3 Behavior changes in version 14.3.00.00. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
New product keys required for 4.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Update connection for Oracle repository with TCPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Update connection for Microsoft SQL Server repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Update connection for MySQL repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Upgrade Guide
2 PUBLIC Content
 New default value for the Validate certification option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Upgrade Guide
Content PUBLIC 3
1 What's in this guide

The information in the Upgrade Guide is important when you have SAP Data Services currently installed, and
you plan to upgrade the installation with a newer version of Data Services.

Find the following information in this guide:

• Upgrade scenarios including upgrading from previous versions of Data Services.

• Migrating to a new environment while you upgrade.
• Behavior changes associated with each version of Data Services and Data Integrator products.

Naming conventions and variables [page 4]

This documentation uses specific terminology, location variables, and environment variables that
describe various features, processes, and locations in SAP Data Services.

1.1 Naming conventions and variables

This documentation uses specific terminology, location variables, and environment variables that describe
various features, processes, and locations in SAP Data Services.

Terminology

SAP Data Services documentation uses the following terminology:

• The terms Data Services system and SAP Data Services mean the same thing.
• The term BI platform refers to SAP BusinessObjects Business Intelligence platform.
• The term IPS refers to SAP BusinessObjects Information platform services.

 Note

Data Services requires BI platform components. However, when you don't use other SAP applications,
IPS, a scaled back version of BI, also provides these components for Data Services.

• CMC refers to the Central Management Console provided by the BI or IPS platform.
• CMS refers to the Central Management Server provided by the BI or IPS platform.

Variables

The following table describes the location variables and environment variables that are necessary when you
install and configure Data Services and required components.

Upgrade Guide
4 PUBLIC What's in this guide
 Variables Description

INSTALL_DIR The installation directory for SAP applications such as Data

Services.

Default location:

• For Windows: C:\Program Files (x86)\SAP

BusinessObjects
• For UNIX: $HOME/sap businessobjects

 Note
INSTALL_DIR isn't an environment variable. The in-
stallation location of SAP software can be different than
what we list for INSTALL_DIR based on the location
that your administrator sets during installation.

BIP_INSTALL_DIR The directory for the BI or IPS platform.

Default location:

• For Windows: <INSTALL_DIR>\SAP

BusinessObjects Enterprise XI 4.0

 Example
C:\Program Files
(x86)\SAP BusinessObjects\SAP
BusinessObjects Enterprise XI 4.0

• For UNIX: <INSTALL_DIR>/enterprise_xi40

 Note
These paths are the same for both BI and IPS.

 Note
BIP_INSTALL_DIR isn't an environment variable.
The installation location of SAP software can be different
than what we list for BIP_INSTALL_DIR based on the
location that your administrator sets during installation.

Upgrade Guide
What's in this guide PUBLIC 5
Variables Description

<LINK_DIR> An environment variable for the root directory of the Data

Services system.

Default location:

• All platforms
<INSTALL_DIR>\Data Services

 Example
C:\Program Files (x86)\SAP
BusinessObjects\Data Services

Upgrade Guide
6 PUBLIC What's in this guide
 Variables Description

<DS_COMMON_DIR> An environment variable for the common configuration di-

rectory for the Data Services system.

Default location:

• If your system is on Windows (Vista and newer):

<AllUsersProfile>\SAP
BusinessObjects\Data Services

 Note
The default value of <AllUsersProfile> environ-
ment variable for Windows Vista and newer is
C:\ProgramData.

 Example
C:\ProgramData\SAP
BusinessObjects\Data Services

• If your system is on Windows (Older versions such as

XP)
<AllUsersProfile>\Application
Data\SAP BusinessObjects\Data
Services

 Note
The default value of <AllUsersProfile> en-
vironment variable for Windows older versions
is C:\Documents and Settings\All
Users.

 Example
C:\Documents and Settings\All
Users\Application Data\SAP
BusinessObjects\Data Services

• UNIX systems (for compatibility)

<LINK_DIR>

The installer automatically creates this system environment

variable during installation.

 Note
Starting with Data Services 4.2 SP6, users
can designate a different default location for

Upgrade Guide
What's in this guide PUBLIC 7
Variables Description

<DS_COMMON_DIR> during installation. If you can't find

the <DS_COMMON_DIR> in the listed default location, ask
your System Administrator to find out where your de-
fault location is for <DS_COMMON_DIR>.

<DS_USER_DIR> The environment variable for the user-specific configuration

directory for the Data Services system.

Default location:

• If you're on Windows (Vista and newer):

<UserProfile>\AppData\Local\SAP
BusinessObjects\Data Services

 Note
The default value of <UserProfile> environment
variable for Windows Vista and newer versions is
C:\Users\{username}.

• If you're on Windows (Older versions such as XP):

<UserProfile>\Local
Settings\Application Data\SAP
BusinessObjects\Data Services

 Note
The default value of <UserProfile> en-
vironment variable for Windows older ver-
sions is C:\Documents and Settings\
{username}.

 Note
The system uses <DS_USER_DIR> only for Data
Services client applications on Windows. UNIX plat-
forms don't use <DS_USER_DIR>.

The installer automatically creates this system environment

variable during installation.

Parent topic: What's in this guide [page 4]

Upgrade Guide
8 PUBLIC What's in this guide
2 Upgrade prerequisites

Before you upgrade to the latest version of SAP Data Services 4.3, read about important prerequisites.

Data Services version 4.3 has significant changes. These changes affect you when you upgrade from Data
Services 4.x.

The following table contains general changes to be aware of before you install the upgrade.

 Note

For software behavior changes introduced in each support pack or patch, see the applicable “Behavior
changes” section.

General software changes

Change Information

System requirements System requirements change over time. For the latest infor-
mation about system requirements, see the Product Availa-
bility Matrix on the SAP Support Portal.

BI and IPS For information about the compatibility between Data Serv-
ices and BI or IPS, refer to the PAM and to KBA 3197694 .

Installation For any installation changes, see the Installation Guide.

Universal Data Cleanse If you use Universal Data Cleanse and have modified a per-
son and firm dictionary or created a custom dictionary, en-
sure that the Cleansing Package Builder in SAP Information
Steward is available before you upgrade. You need Cleansing
Package Builder to migrate your dictionary file to the new
cleansing package format.

Security Data Services requires that you enter a user name and pass-
word for your Data Services repository when you log into
Designer or when you open a Data Quality report. See the
Administrator Guide for more information.

Upgrade Guide
Upgrade prerequisites PUBLIC 9
Change Information

SAP system security Since version 4.2 SP2, Data Services includes several en-
hancements to functions, procedures, and authorizations
that provide secure integration with SAP systems. Adminis-
trators can assign authorizations at a more granular level,
such as authorizations that limit which users can execute
functions and which programs users can start.

The new secured functions are now delivered into the /

SAPDS namespace instead of the /BODS or customer Z
namespace.

Data Services looks for functions from the /SAPDS name-

space on SAP systems, if available. If Data Services does
not find the functions, it continues to work with existing /
BODS functions installed on SAP systems. For details, see
the Supplement for SAP.

 Note
You must update the transport files that are sup-
plied by SAP and update the SAP authorizations to
Data Services version 4.2 SP2 or later. SAP transport
files are shipped with namespace /SAPDS from SAP
NetWeaver, SAP BW, or SAP ERP patches. For details,
see the Data Services Supplement for SAP and SAP Note
1919255 .

Related Information

Data Services behavior changes [page 33]

Upgrade Guide
10 PUBLIC Upgrade prerequisites
3 Upgrade considerations for SAP Data
Services 4.3 Support Packages

Read about issues that can affect your pre- or post-upgrade to the new version of SAP Data Services.

The following issues and solutions include information that can contribute to a successful upgrade:

• You must obtain new 4.3 product keys, including keys for add-ons like NCOALink, the first time you install,
upgrade, or update Data Services 4.3.

 Note

The 4.3 product keys are not backwards compatible and do not work with older versions of Data
Services.

• If you use MySQL for your repository, you need to download and install a new JAR file after you upgrade
to 4.3.00.00 and later. The new JAR file is 8.0.26.jar. For download and installation instructions, see
Configuring JDBC drivers for Oracle and MySQL in the Installation Guide for Windows.
Before upgrading, always check the Product Availability Matrix (PAM) for the latest supported JAR file
version.
• The SAP Data Service Management Console cannot launch if the version of the Apache Tomcat Introscope
Wily server is earlier than 10.7. For more information, see SAP Note 3036039 .
• In an earlier release, we changed the user access control (UAC) so that standard users have access to
configuration files. The Data Services installer migrates the objects in your current DSConfig.txt file to
the new Data Services 4.3 SPxx locations, which may have different access rights. For more information
about these changes, see “User Access Control (UAC) support” in the Data Services 4.2 Upgrade Guide.
• During a Windows upgrade installation, optionally choose to change the default location of the Data
Services common directory (%DS_COMMON_DIR%). If you choose to change the default location, check
that the new directory adheres to the following requirements:
• The new directory is local and all applicable users have permission to access it.
• The new directory has sufficient disk space for the configuration and log files that reside in the
common directory.
• The %DS_COMMON_DIR% location can't point to the same folder as %LINK_DIR% on Windows. For more
information, see KBA 2258787 .
For more information about changing the location of the common directory, see the Installation Guide for
Windows.
• After you back up your repositories and upgrade to the latest version of Data Services, upgrade your
underlying repositories to the new version using the Repository Manager. For information about the
repository manager, see the Administrator Guide.

 Note

• Supported database versions for the repository can be found in the PAM.
• Thoroughly back up your repositories after you upgrade. Create a database backup of the schema
or database where the Data Services repository is located. Back up steps differ between database
vendors, so see your vendor documentation for more information.

Upgrade Guide
Upgrade considerations for SAP Data Services 4.3 Support Packages PUBLIC 11
• If you are upgrading to 4.3 from Data Services versions 4.0 or 4.1 (this does not apply when upgrading from
4.2), the upgrade installation to the latest version of Data Services does not upgrade the features that you
installed with Data Services version 4.0 or 4.1. To upgrade the features from version 4.0 or 4.1:
• Run the upgrade installation for 4.3 SPxx.
• Run a modify installation of version 4.3 SPxx to add the features from 4.0 or 4.1.
Features that you installed with versions other than 4.0 or 4.1 should upgrade with the upgrade
installation unless otherwise noted.
• Your Data Services 4.3 CMS configurations do not change when you upgrade to the new version.
• You can choose to reuse configurations in the DSConfig.txt file by pointing to the existing configuration
file location during installation.
• If you configured a MySQL or Oracle repository at any time after installing Data Services 4.0, manually
configure the JDBC drivers after upgrading to the latest version of Data Services. For more information,
read about configuring JDBC drivers for SAP HANA, Oracle, and MySQL in the Installation Guide.
• The following information applies to you when you upgrade from 4.x or earlier versions:
• Data Services Profiler configuration: When you upgrade to the latest version of Data Services, the
installer sets the Profiler configuration parameters to default values. If you had previously modified
any of the Profiler configuration parameters, make note of your customizations and upgrade to the
latest version of Data Services. After installation completes, log into the CMC and change the Profiler
configuration parameters to your custom settings.
• Oracle users: Before upgrading to the latest version of Data Services, be sure to grant the database
account the “create any sequence” privilege.

Related Information

Data Services behavior changes [page 33]

Upgrade Guide
12 PUBLIC Upgrade considerations for SAP Data Services 4.3 Support Packages
4 Choose BI or IPS platform

Before you upgrade to the latest version of SAP Data Services 4.3, know the platform that your current
installation uses.

When you initially installed Data Services, you chose one of the following platforms:

• SAP BusinessObjects Business Intelligence platform (BI)

• SAP BusinessObjects Information platform services (IPS)

Data Services uses the central user management capabilities of BI or IPS for security. The software
authenticates users against BI or IPS, and registers repositories in BI or IPS.

When you install or upgrade Data Services, ensure that you install or upgrade with a compatible version of BI or
IPS. To find out which version is compatible with this version of Data Services, see the following resources:

• For information about the compatibility between Data Services and BI or IPS, see KBA 3197694 .
• For information about BI Platform user licenses, see KBA 2176896 .
• For information about installing the platform, see the applicable installation guide:
• SAP BusinessObjects Business Intelligence platform Installation Guide
• SAP BusinessObjects Information platform services Installation Guide

 Note

To download full and patch installations of BI or IPS, visit the Software Download page on the SAP Support
Portal .

 Remember

If you update your deployment from BI or IPS version 4.2 SP4 or higher using the update installation
program, and if you use the bundled IBM DB2 Workgroup Edition (UNIX) or Microsoft SQL Server 2008
Express (Windows) database server, the installation program preserves the database servers. You can
continue to use these bundled database servers for your Data Services repository.

Upgrade Guide
Choose BI or IPS platform PUBLIC 13
5 Update SAP transport files and SAP
authorizations

When you work with SAP applications in SAP Data Services, update the SAP transport file and SAP
authorizations.

To ensure full functionality with SAP applications, update the SAP-supplied transport file and the SAP
authorizations in addition to upgrading to the newest version of Data Services.

Additionally, if you have ABAP data flows that run in Execute Preloaded mode, regenerate and upload the ABAP
again after you upgrade Data Services.

When you update the transport file and authorizations, the upgrader installs new and updated authorization
classes to the /SAPDS namespace. The following table maps the new authorization class and objects to the
equivalent classes and objects in previous installations. For more information about authorization classes and
objects, see the Supplement for SAP.

Data Services or SAP (Net-

Transport File and Authori- SAP (NetWeaver/ERP/BW Weaver/ERP/BW Service
zation Installation Service Packs) Packs) Data Services

Namespace /SAPDS /BODS n/a

Authorization class SDS BODS ZSDS

Authorization object S_SDSAUTH S_DSAUTH ZDSAUTH

Authorization object S_SDSS S_SDS ZSDS

Authorization object S_SDSDEV S_DSDEV ZDSDEV

Authorization object S_SDSPGMCK S_DSPGMCHK ZPGMCHK

Upgrade Guide
14 PUBLIC Update SAP transport files and SAP authorizations
6 JDBC and ODBC drivers

SAP Data Services and its system and service components use drivers, such as the JDBC and ODBC drivers,
for communication.

Before installation or upgrade, check the Product Availability Matrix (PAM) to view driver requirements for
the database type and version that you use for your local repository. After installation, when you configure
datastores and other connections to databases, ensure that you meet the driver requirements for the
databases that you use as sources, targets, and other types of repositories.

Find additional driver information for the specific database that you use for datastores, adapters, or
repositories in the applicable guide:

• Datastores: Designer Guide or applicable supplement

• Adapters: Supplement for Adapters
• Repositories: Administrator Guide

Also consult the Installation Guide and the Upgrade Guide for other special driver instructions.

JDBC drivers

The Central Management Server uses the JDBC driver for installation of the default (local) repository. The
Central Management Console (CMC) also requires the driver when you register the repository.

Data Services Management Console uses JDBC drivers to communicate with the repository for processes with
data.

ODBC drivers

For most database types, the Repository Manager uses the ODBC driver for creating and upgrading the
repository.

 Note

Some database types require a different driver type. For example, Oracle uses Oracle client. Therefore, it is
important that you consult the PAM for the supported driver and version for the database that you select
for your repository.

Data Services Management Console uses the ODBC driver for communication with certain types of
repositories. Management Console also uses the ODBC driver for communication with certain types of
database datastores.

Upgrade Guide
JDBC and ODBC drivers PUBLIC 15
Repository driver source

The following table describes whether Data Services bundles the repository driver with your installation and
upgrade, or whether you download and install the driver.

Driver Database Access

JDBC • DB2 Bundled with Data Services installer.

• SAP ASE
For upgrade, the installer replaces the
• SAP HANA
old driver with the new driver as neces-
• SQL Server sary. There are no additional actions re-
• SAP SQL Anywhere quired by you.

JDBC • Oracle Download and install the driver that ex-

• MySQL actly matches the driver name and ver-
sion listed in the PAM. Data Services
doesn't recognize the driver if you enter
an inexact driver name and version.

If the supported JDBC driver version

has changed, and you upgrade to a new
version of Data Services, the repository
is listed as “inactive” in the Central
Management Console (CMC). If after
upgrade your repository is listed as in-
active, perform the following steps:

1. Download the driver that exactly

matches the driver name and ver-
sion listed in the PAM.
2. Place the new JDBC driver into the
applicable directory or directories,
such as %BIP_INSTALL_DIR%
\java\lib\im\MySQL.
3. Restart the EIM Adaptive Process-
ing Server in the CMC.

ODBC All Download and install the correct ver-

sion of the driver from your database
management system. Consult the PAM
for correct versions.

Upgrade Guide
16 PUBLIC JDBC and ODBC drivers
7 Upgrade scenarios

To guide you through the upgrade process, we present a scenario for upgrading to the newest version of Data
Services from Data Services version 4.x.

Follow the upgrade scenario to understand how the example applies to your upgrade situation.

If the scenario fits your situation, find additional upgrade scenarios in SAP Note 3375103 .

For compatibility information between Data Services and BI or IPS versions, refer to KBA 3197694 .

After you read this Upgrade Guide, make sure to read the Installation Guide that is specific for your operating
system (Windows or Unix) for specific operating system information and installation instructions.

Upgrading from Data Services 4.x [page 17]

This scenario presents two methods to upgrade from SAP Data Services version 4.x to the latest
version of Data Services 4.3.

7.1 Upgrading from Data Services 4.x

This scenario presents two methods to upgrade from SAP Data Services version 4.x to the latest version of
Data Services 4.3.

With either of the following methods, you can choose to reuse the previous 4.x SPxx configurations, if
applicable.

• Install the latest version of Data Services 4.3 on top of Data Services 4.x SPxx
• Uninstall Data Services 4.x SPxx and install the latest version of Data Services 4.3

 Remember

After you perform the upgrade using either method, use the Data Services Repository Manager to upgrade
your repository.

Installing without uninstalling [page 18]

Install the latest version of SAP Data Services 4.3 on top of Data Services 4.1 or 4.2.

Installing by first uninstalling [page 18]

Install the latest version of SAP Data Services 4.3 after you uninstall Data Services 4.x.

Parent topic: Upgrade scenarios [page 17]

Upgrade Guide
Upgrade scenarios PUBLIC 17
7.1.1 Installing without uninstalling
Install the latest version of SAP Data Services 4.3 on top of Data Services 4.1 or 4.2.

Before you begin, ensure that you have a version of BI or IPS that is compatible with the version of Data
Services that you are installing.

 Note

For the latest information regarding Data Services and BI platform/IPS compatibility, see KBA 3197694
and the Product Availability Matrix (PAM) .

1. Select the order in which to install or uninstall software to accomplish this upgrade. Note that in the
following upgrade statements, (+) means installing, and (-) means uninstalling.
a. For this scenario, your current installation consists of the following software and versions.

BI/IPS 4.2 SPx Patch y + DS 4.2 SP14 Patch yy [1]

b. Install the latest BI/IPS 4.3 version and the latest DS 4.3 version on top of the current installation in the
following order:

BI/IPS 4.3 SPx Patch y + DS 4.3 SPxx [2]

 Note

[1]: If your Data Services environment is on a version of Windows prior to Windows 10 or Windows
Server 2016, such as 2008, 2008 R2, 2012, or 2012 R2, apply a Windows Package update before
performing the Data Services upgrade. Refer to SAP Note 2451830 for more information.

[2]: A Data Services repository upgrade is mandatory.

2. Upgrade your repository using the Repository Manager.

Task overview: Upgrading from Data Services 4.x [page 17]

Related Information

Installing by first uninstalling [page 18]

7.1.2 Installing by first uninstalling

Install the latest version of SAP Data Services 4.3 after you uninstall Data Services 4.x.

Before you begin, ensure that you have a version of BI or IPS that is compatible with the version of SAP Data
Services that you are installing.

 Note

For the latest information regarding Data Services and BI platform/IPS compatibility, see KBA 3197694
and the Product Availability Matrix (PAM) .

Upgrade Guide
18 PUBLIC Upgrade scenarios
The following upgrade statement shows an example upgrade scenario. Note that (+) means installing, and (-)
means uninstalling:

BI/IPS 4.0 SP4 + DS 4.1 SP1 - DS 4.1 SP1 + BI/IPS 4.3 SPx Patch y + DS 4.3 SPxx

1. Uninstall the oldest version of Data Services.

You do not have to uninstall BI or IPS.

2. After uninstall completes, perform the following steps to restore the runtime configurations:
a. Move the admin.xml and admin.key files from <LINK_DIR>\conf to <DS_COMMON_DIR>\conf
b. Move the startup_script.xml and adapter.key files from <LINK_DIR>\adapters to
<DS_COMMON_DIR>\adapters
c. Move all *.xml files from <LINK_DIR>\adapters\config to
<DS_COMMON_DIR>\adapters\config
d. Restart the web server on which the SAP Data Services Management Console is deployed.

Data Services default web server is Apache Tomcat.

e. Restart the Data Services Service.
f. If you use Access Servers, log into the Data Services Management Console and add the Access Servers
in the Administrator application to restore the configuration.
3. Install the latest compatible version of BI/IPS 4.3.

If you didn't uninstall the previous version, you are installing the latest version on top of the previous
version.
4. Install Data Services 4.3 SPxx.
5. Optional. If you plan to reuse the repositories from Data Services versions 4.x, update the Data Services
repository InfoObjects. To update the InfoObjects, resave the repositories in the Central Management
Console (CMC), or perform the following steps:
a. In a command prompt, change directories to <LINK_DIR>\bin\.
b. Run the following command: DSXI40UpgradeMgr.bat -RU -CC<CMS System> -CU<CMS User>
-CP<CMS Password> -CA<CMS Auth>

 Sample Code

DSXI40UpgradeMgr.bat -RU -CClocalhost -CUAdministrator -CPP455w0rd

-CAsecEnterprise

6. Upgrade all of your repositories using the Repository Manager.

Task overview: Upgrading from Data Services 4.x [page 17]

Related Information

Installing without uninstalling [page 18]

Upgrade Guide
Upgrade scenarios PUBLIC 19
8 Scenario: Migrate Data Services to a new
environment

Migration is necessary to upgrade or expand your environment, or to switch from the SAP BusinessObjects
Business Intelligence(BI) platform to the SAP BusinessObjects Information platform services (IPS) landscape.

This scenario walks you through a migration from your existing SAP Data Services deployment in a BI 4.0
landscape to the latest compatible version of IPS 4.3 landscape on new hardware.

 Note

Because Data Services is required to be installed before you install SAP Information Steward, we don't
cover migrating Information Steward in the scenario. For Information Steward upgrade information, refer to
the Information Steward Upgrade Guide and KBA 1906581 .

Also in the scenario, we migrate to a new server, so we refer to the “old machine” and the “new machine”
where:

• The old machine is the environment you migrate from

• The new machine is the environment you migrate to

 Note

• During the migration, perform the upgrade of all the Data Services repositories in-place in the same
database server that holds the Data Services repositories. Do not move your databases from an
existing database server host to another host during this migration.

BI platform or IPS

When your Data Services and Information Steward applications share the Central Management Server (CMS)
with other SAP applications, you should keep using the BI platform in your system landscape. Choose to use
IPS when you have only Data Services and Information Steward sharing the CMS.

In your environment, ensure that the target BI platform version or IPS version is compatible with the version of
Data Services.

 Note

For compatibility information between Data Services and BI or IPS versions, see KBA 3197694 and the
Product Availability Matrix (PAM) .

Upgrade Guide
20 PUBLIC Scenario: Migrate Data Services to a new environment
Migration scenario

In this scenario, we perform the following tasks:

• Upgrade Data Services that is deployed on BI 4.0 SP5 to another deployment with the latest compatible
IPS 4.3 version on another system.
• Upgrade the existing Data Services version from Data Services 4.1 to 4.3 SPxx.

Before migration

Before we migrate to a new environment, our environment on the old machine consists of the following
deployment:

• Installed on machine 1:
• BI 4.0 SP5
• Data Services 4.1

After migration

• On machine 2, the new machine:

• IPS 4.3 SPx Patch y
• Data Services 4.3 SPxx
• On machine 1, the old machine:
• Upgrade to BI 4.3 SPx Patch y

Order of tasks

1. Backing up existing configuration [page 22]

Before you migrate to the new version of SAP Data Services on a new server, back up the Data Services
4.0, 4.1, and 4.2 repositories, configuration files, and Data Quality cleansing packages.
2. Installing IPS and Data Services on the new server [page 23]
Install Information platform services (IPS) and the new version of SAP Data Services on the new
computer.
3. Migrating CMS content using Promotion Management [page 24]
Use the Promotion Management tool in the Central Management Console (CMC) to move objects from
an existing Data Services or Information Steward 4.x environment to the latest version environment.
4. Migrating Data Services repositories [page 27]
Move existing repositories from the old server to the new server.
5. Migrate Data Services configurations [page 29]

Upgrade Guide
Scenario: Migrate Data Services to a new environment PUBLIC 21
 Your migrated SAP Data Services application requires that you also migrate the required configuration
files.
6. Verifying the upgrade process [page 31]
After you complete the migration steps, verify that you have correctly set up IPS and SAP Data
Services.

8.1 Backing up existing configuration

Before you migrate to the new version of SAP Data Services on a new server, back up the Data Services 4.0, 4.1,
and 4.2 repositories, configuration files, and Data Quality cleansing packages.

In the following steps, we use variables to refer to file locations. For variable definitions, see Naming
conventions and variables [page 4].

1. Back up your local, central and profiler repositories.

2. Create a database backup of the schema or database where the Data Services 4.0, 4.1, and 4.2 repositories
are located.

 Note

The exact backup steps differ between database vendors.

 Caution

Make sure that your database backup allows you to restore all of the repository tables and data.

3. If your existing Data Services version is 4.1 or higher, back up the following configuration files:

• Back up the files in the <DS_COMMON_DIR> directory

• If your Access Server configuration is located outside of <DS_COMMON_DIR>, then make a backup of all
Access Server directories.

 Note

To find locations for your Access Servers, open the SAP Data Services Server Manager and open
the Access Server tab. Each Access Server is listed with the location.

4. If your existing Data Services version is 4.0, back up the following configuration files:

• admin.xml and admin.key under <LINK_DIR>/conf

• DSConfig.txt and DSConfig.key under <LINK_DIR>/conf
• Back up all Access Server configuration directories.
• Back up adapter configuration files under <LINK_DIR>/adapters
5. Back up customized Data Quality cleansing packages. If you customized your PERSON_FIRM cleansing
package, or if you created other customized cleansing packages, back them up into BIAR files.

For instructions, see the applicable version of the BI Administrator Guide or the IPS Administrator Guide.
Based on whether your old system uses BI or IPS, you use either Lifecycle Management Console or the
promotion management tool to back up cleansing packages into BIAR files.

Upgrade Guide
22 PUBLIC Scenario: Migrate Data Services to a new environment
On Unix, whether the Data Services version is 4.0 or 4.1, follow the steps in #3 above to back up the
configuration files.

Task overview: Scenario: Migrate Data Services to a new environment [page 20]

Next task: Installing IPS and Data Services on the new server [page 23]

8.2 Installing IPS and Data Services on the new server

Install Information platform services (IPS) and the new version of SAP Data Services on the new computer.

In the following steps, we use variables to refer to file locations. For variable definitions, see Naming
conventions and variables [page 4].

Perform the following steps to install IPS and Data Services onto a new computer:

1. Install IPS on the new machine, ensuring that the version is compatible with the new Data Services version
you plan to install. For information about the compatibility between Data Services and IPS, see KBA
3197694 .

The new server cannot have the BI platform installed on it. For IPS installation instructions, see the
Information platform services Installation Guide on the help portal for the applicable version.

IPS creates a new Central Management Server (CMS) for the Data Services installation.
2. Copy the DSConfig.txt and DSConfig.key files from the old machine in <LINK_DIR>\conf, and paste
them into the new server.

At this point, <LINK_DIR> doesn't exist, so choose a general location for the files.
3. Install the latest version of Data Services on the new machine. During install, choose Reuse existing
configuration and point to the location of the pasted DSConfig files when prompted.

Task overview: Scenario: Migrate Data Services to a new environment [page 20]

Previous task: Backing up existing configuration [page 22]

Next task: Migrating CMS content using Promotion Management [page 24]

Upgrade Guide
Scenario: Migrate Data Services to a new environment PUBLIC 23
8.3 Migrating CMS content using Promotion Management

Use the Promotion Management tool in the Central Management Console (CMC) to move objects from an
existing Data Services or Information Steward 4.x environment to the latest version environment.

 Note

You cannot use Promotion Management to move Data Insight objects from one environment to another,
such as from a test environment to a production environment. Instead, use the import—export process. For
information about using the import—export process, see the SAP Information Steward User Guide.

 Example

After you perform setup and testing on a development system, export projects and objects from the
development system and import them into the production system.

Promotion Management retains all the information associated with the migrated objects, including user
security. For complete information about Promotion Management, see the SAP BusinessObjects Business
Intelligence platform Administrator Guide or Information platform services Administrator Guide.

1. Log into the CMC on the target server, the new machine on which you installed IPS.
2. Under the CMC Home dropdown list, select Promotion Management.
3. The Promotion Jobs tab opens.
4. Connect to the source system:

a. Choose Settings Manage Systems .

The Manage Systems dialog box opens.

b. Click Add and add the connection details for the source server in the Add System dialog box.

The source system is the system where you have the previous versions of BI, Data Services, and
Information Steward installed.
c. Click Mark as Origin to select it and click OK.

 Note

Keep the Manage Systems dialog box open for the next step.

5. Connect to the destination system:

a. Click Add and add the connection details for the source server in the Add System dialog box.

The source server is the new machine on which you installed IPS and the new version of Data Services
and Information Steward.
b. Click OK, and then click Close.

 Note

Keep logged into the CMC for the next step.

6. Create a job:
a. Choose New Job, and then enter a name for the migration job in the New Job tab.

Upgrade Guide
24 PUBLIC Scenario: Migrate Data Services to a new environment
 b. Select the location from the Save Job in* dropdown list.
c. Select Login to a New CMS from the Source* dropdown list.
d. Select the source system, enter the user name and password, and then click Login.
e. Optional. Select an option from the Destination system dropdown list:

• Login to a New CMS: Places the objects on the target system when you promote the job.
• Output to LCMBAIR File: Exports the objects to a BAIR file and then imports the file on the
destination system.
f. Click Create.

The Add Objects from the system dialog box opens.

7. Expand the nodes in the column at left to display objects at right. Select one or more objects listed in the
table, and then click Add.
In the following table, view the information in the Path in Promotion Management column to find the
listed object. For example, for Data Services Repositories , expand the Data Services node and select
Repositories to see the Repositories objects.

Product Object Path in Promotion Management

Data Services Repositories Data Services Repositories

Data Services RFC Configurations Data Services RFC

Configurations

Data Services Published cleansing packages Data Quality Cleansing Packages

Published

Data Services Data Services security (users and Users or User Groups. For more infor-
user groups) mation see the SAP BusinessObjects
Business Intelligence platform Admin-
istrator Guide

Information Steward Profiling connections Information Steward

Connections

Information Steward Data Insight projects Information Steward Enterprise

Profiling Projects

Information Steward Data Review Information Steward Data

Review

Information Steward Profiling tasks and rule tasks 1. Select a project object
from Information Steward
Enterprise Profiling Projects
2. Click Manage Dependencies.
3. Select the profiling tasks and rule
tasks to upgrade.
4. Click Apply & Close.

Information Steward Metadata Management Integrator Information Steward Metadata

Sources Management Integrator Sources

Upgrade Guide
Scenario: Migrate Data Services to a new environment PUBLIC 25
 Product Object Path in Promotion Management

Information Steward Metadata Management Source Information Steward Metadata

Groups Management Source Groups

Information Steward User-created utilities and scheduling Information Steward Metadata

information for Information Steward Management Utilities
utilities

Information Steward Metapedia user security settings Metadata Management

Metapedia folder

Information Steward Published cleansing packages Data Quality Cleansing Packages

Published
 Note
Skip cleansing packages if you
migrated them as a part of the
Data Services migration.

Information Steward Information Steward security (users Users or User Groups. For more infor-
and user groups) mation see the SAP BusinessObjects
Business Intelligence platform Admin-
istrator Guide

 Note

When selecting the repositories to migrate, review the list of existing repositories and carry forward
only the valid ones. If there are any obsolete or invalid repositories, deselect those from the promotion
job.

 Note

Promotion jobs can take a long time to complete when there is a large cleansing package. For this
reason, you might want to create a separate migration job for cleansing packages. If you have multiple
cleansing packages, create several separate migration jobs.

8. After all objects are added, click Close.

 Note

You can add objects later using the Add Objects icon.

9. Optional. Click the Manage Dependencies icon and select any dependent objects to migrate from the
Manage Dependencies dialog box.
10. Click Apply & Close.
11. Click the Promote icon.

The Promote dialog box opens.

12. Optional. Promote security settings by following these substeps:
a. Choose Security Settings at left.
b. Select Promote Security, Promote Object Security, and Promote User Security.
c. Click Save.

Upgrade Guide
26 PUBLIC Scenario: Migrate Data Services to a new environment
 d. Choose Test Promote.
e. Click the Test Promote button.

 Note

If there are many objects to be promoted, this may take some time to complete.

f. Verify that the test promotion is successful.

13. If you created several migration jobs, select them and then click the Promote icon to complete the
migration of the CMS content.

 Note

Depending on the size of the projects and the contents, it might take several minutes to complete the
promotion job. If the content is too big, consider breaking the contents into multiple migration jobs.

14. Click History to verify the job status. Click the Refresh icon as necessary until the job is completed.
15. Log into the CMC on the destination system to verify that Promotion Management migrated all objects
(repositories, users and user groups, if any).

 Note

With regard to EIM Adaptive Processing Service (APS) configuration, the IPS Data Services System
Landscape Directory (SLD) configuration parameters are set to default values. If you previously modified
any of the Service configuration parameters, log into the CMC to change the parameters to your custom
settings.

 Note

With regard to Data Services Application settings, the IPS SLD settings are set to default values. If you
previously modified any of these settings, log into the CMC and change the options to your custom settings
( CMC Home Applications Data Services Application ).

For additional information, see Master Guide: “Separate Information platform services and BI platform”.

Task overview: Scenario: Migrate Data Services to a new environment [page 20]

Previous task: Installing IPS and Data Services on the new server [page 23]

Next task: Migrating Data Services repositories [page 27]

8.4 Migrating Data Services repositories

Move existing repositories from the old server to the new server.

1. On the old (source) machine, open the SAP Data Services Server Manager.
2. Find all repositories that you migrated to the new server, and remove the association with the Job Server
on the old machine.

Upgrade Guide
Scenario: Migrate Data Services to a new environment PUBLIC 27
3. On the new (destination) machine, log into the Central Management Console (CMC) and select Data
Services.
4. Click Repositories.
5. Find the repositories that contain the old version of Data Services in the Version column.
6. Open the Data Services Repository Manager. Use the Get Version and Upgrade buttons to upgrade the
repositories that contain the old version of Data Services. Perform the upgrade for all types of repositories
(local, central and profiler).
In most cases, your repository versions between the CMC and the Repository Manager need to match. The
Designer does not support mixed versions. If the versions do not match, you cannot perform the following
tasks:
• Export to different repositories
• Connect to different profiler and central repositories
• Promote objects
7. On the destination (new) machine, launch SAP Data Services Server Manager and make sure that all the
migrated repositories are associated with the correct Job Servers.
8. For each migrated repository, perform a Re-sync operation. Then choose Close and Restart to restart the
Data Services service.
9. On the destination (new) machine, restart the Server Intelligence Agent (SIA) service and restart the web
server (for example, Tomcat).
10. On the destination (new) machine, log in to the CMC and select Data Services and then click Repositories.

11. Select a repository on the right and click Actions Properties .

12. Enter the password and click Test Connection.
13. When the test is successful, click Save.
14. Verify that all objects have been migrated:
a. On the destination (new) machine, log into the Data Services Management Console and open the
Administrator application.
b. Expand Management CMS Connection .
c. Click Test and Apply.

Error or success messages appear at the top of the CMS Connection tab.
d. Expand Batch and verify that all the repositories migrated.
e. Click each job for the selected repository and verify that the schedules, if any, are migrated in the
Repository Schedules tab.
f. Expand SAP Connections and select RFC Server Interface Configuration. Verify that RFC configurations,
if any, are migrated.

Task overview: Scenario: Migrate Data Services to a new environment [page 20]

Previous task: Migrating CMS content using Promotion Management [page 24]

Next: Migrate Data Services configurations [page 29]

Upgrade Guide
28 PUBLIC Scenario: Migrate Data Services to a new environment
8.5 Migrate Data Services configurations

Your migrated SAP Data Services application requires that you also migrate the required configuration files.

Configuration files contain the information that Data Services needs to operate. The following list contains the
configuration files that you must migrate:

• Real-time services
• JDBC drivers
• Profiler configurations
• admin.xml
• Adapters
• Access Servers

Real-time services

To restore the real-time services configuration, log into the Data Services Management Console and open the
Administrator application. Add the Access Servers in the Management Console.

Configuring JDBC drivers

If you configured a MySQL or Oracle repository at any time after installing Data Services 4.0 or higher, you
must manually configure the JDBC drivers after the migration. For more information, see “Post-installation,
Configuring JDBC drivers for SAP HANA, Oracle, and MySQL” in the Data Services Installation Guide.

Data Services Profiler configuration

When you migrate Data Services, the Profiler configuration parameters are set to default values. If you had
modified any of the Profiler configuration parameters after installing 4.0 or higher, you need to log on to the
Management Console and change the Profiler configuration parameters to your custom settings.

Parent topic: Scenario: Migrate Data Services to a new environment [page 20]

Previous task: Migrating Data Services repositories [page 27]

Next task: Verifying the upgrade process [page 31]

Upgrade Guide
Scenario: Migrate Data Services to a new environment PUBLIC 29
8.5.1 Migrating adapter configuration files

As part of the migration from BI to IPS environment, migrate all adapter configuration files from the old
machine to the new machine.

For the directory locations of the variables that we use in the following steps, see Naming conventions and
variables [page 4].

Here are the locations of the adapter files on the old machine:

• For Data Services 4.1 and later: <DS_COMMON_DIR>\adapters

• For Data Services 4.0 and earlier: <LINK_DIR>\adapters

1. Copy startup_script.xml and adapter.key files from ...\adapters on the old machine.
2. Paste the files on the new server in <DS_COMMON_DIR>\adapters folder.
3. Copy all XML files from the old machine in the ...\adapters\config folder, and paste them to
<DS_COMMON_DIR>\adapters\config on the new machine.
4. Copy all XML files from the old machine in the ...\adapters\install folder, and paste them to the
<DS_COMMON_DIR>\adapters\install on the new machine.
5. Open the new machine, and run a command to update the applicable adapter type with the -classpath
Java parameter values.
a. Make sure that you have the %LINK_DIR% and the %DS_COMMON_DIR% environment variables set
on the new system.
b. Open a command prompt and enter the following command:

cd %LINK_DIR%

c. Run the following command line for each adapter type, replacing the <"Adapter type"> element at
the end of the command with the adapter name. Enter the adapter name exactly as it appears in the
Management Console.

"ext/Jre/bin/java.exe" -classpath
"lib/acta_adapter_sdk.jar;lib/acta_tool.jar;lib/log4j-1.2.8.jar;ext/lib/
jaxp.jar;ext/lib/xercesImpl.jar;ext/lib/xml-apis.jar;ext/lib/xalan.jar"
com.acta.adapter.sdkutil.UpdateAdapterVersion "%LINK_DIR%"
"%DS_COMMON_DIR%" "<Adapter type>"

6. After you have run -classpath for each existing adapter, restart the web server in which the Data
Services Management Console is deployed and restart the Data Services service.

Stop and start services automatically by restarting the computer.

8.5.2 Migrating the admin.xml configuration file

As part of the migration from BI to IPS, migrate the admin.xml configuration file.

Location on old machine:

• For Data Services 4.1 and later: <DS_COMMON_DIR>\conf

• For Data Services 4.0 and earlier: <LINK_DIR>\conf

For locations of the variables, see Naming conventions and variables [page 4].

Upgrade Guide
30 PUBLIC Scenario: Migrate Data Services to a new environment
1. Copy admin.xml and admin.key files from the old machine.
2. Paste the files on the new server in <DS_COMMON_DIR>\conf.

8.5.3 Migrating the Access Servers

As part of the BI to IPS migration, migrate any Access Server configuration files, and then restore any real-time
services.

1. Copy all access server configuration directories from the old machine to the new machine.

To view the location for each access server, on the old machine, open the SAP Data Services
Server Manager and open the Access Server tab. The access server configuration files are usually in
<DS_COMMON_DIR> or <LINK_DIR> in the Access Server folder.

a. On the source (old) machine, copy the access server configuration directory files.
b. Open the new (destination) machine and paste the access server configuration directories in the new
location.
2. On the new machine, restart the computer to restart the SAP Data Services service.
3. Restore the real-time services configuration by adding each access server configuration from the old
machine to the new machine:
a. Log into the SAP Data Services Management Console.
b. Open the Administrator application.
c. Expand the Management node and click Access Servers.

The Access Servers tab opens.

d. Click Add and enter Machine Name, Communication port, and select whether to use SSL protocol.
e. Click Ping to see if the Access Server is available and exists on the computer and port you specified.
f. Click Apply.

8.6 Verifying the upgrade process

After you complete the migration steps, verify that you have correctly set up IPS and SAP Data Services.

Perform the following steps on the new computer:

1. Log into the Central Management Console (CMC) and open the Data Services page.
2. Select Repositories.

Ensure that the repository list includes all migrated repositories.

3. Continue checking each applicable node to ensure that all migrated objects are present.

Check for the following:

• Repositories
• Jobs
• Job schedules

Upgrade Guide
Scenario: Migrate Data Services to a new environment PUBLIC 31
 • Adapters
• Real-time services
• Web services
• SAP connections (RFC server configurations)
4. Expand the Management node and check that the following objects are migrated as applicable:

• Datastores
• File locations
• Substitution parameters
• Report server configurations
• Access Servers
• Profiler configurations
• CMS connections
5. Log into the Data Services Designer using a migrated user name and password.
6. Select a migrated repository.
7. Open a migrated project and execute a migrated job.

Task overview: Scenario: Migrate Data Services to a new environment [page 20]

Previous: Migrate Data Services configurations [page 29]

Upgrade Guide
32 PUBLIC Scenario: Migrate Data Services to a new environment
9 Data Services behavior changes

Find information about behavior changes in SAP Data Services 4.3 releases.

Knowing the behavior changes in Data Services from one release to another is important when you plan your
upgrade and migration projects.

For information about behavior changes in previous Data Services 4.2 releases, see the 4.2 Upgrade Guide on
the help portal.

Behavior changes in version 14.3.03.00 [page 33]

Changes in the behavior of SAP Data Services 4.3 Support Package 03 (14.3.03) and its patches from
previous releases of Data Services.

Behavior changes in version 14.3.01.00 [page 34]

Changes in the behavior of SAP Data Services 4.3 Support Package 1 (14.3.01) and its patches from
previous releases of Data Services.

Behavior changes in version 14.3.00.00 [page 34]

Changes in the behavior of SAP Data Services 4.3 Support Package 00 (14.3.00) and its patches from
previous releases of Data Services.

9.1 Behavior changes in version 14.3.03.00

Changes in the behavior of SAP Data Services 4.3 Support Package 03 (14.3.03) and its patches from previous
releases of Data Services.

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.

To obtain the latest version of documentation, visit the SAP Help Portal at https://help.sap.com/viewer/p/
SAP_DATA_SERVICES.

9.1.1 Multi-subnet failover and column encryption for SQL

Server

User interface options for SQL Server repository allows you to add additional connection parameters to be
able to setup multi-subnet failover and column encryption. Previously, the MultiSubnetFailover attribute
was hard coded to Yes, however, this cannot be used to connect to a mirror server. The user interface for
Repository Manager, Job Server Manager, and CMC have been updated to include an Additional connection
parameters field where you can add MultiSubnetFailover=Yes;ColumnEncryption=Enabled;.

Upgrade Guide
Data Services behavior changes PUBLIC 33
9.2 Behavior changes in version 14.3.01.00

Changes in the behavior of SAP Data Services 4.3 Support Package 1 (14.3.01) and its patches from previous
releases of Data Services.

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.

To obtain the latest version of documentation, visit the SAP Help Portal at https://help.sap.com/viewer/p/
SAP_DATA_SERVICES.

9.2.1 Multi-subnet failover enabled by defult for SQL Server

repository

SAP Data Services, by default, sets the MultiSubnetFailover attribute to Yes in the SQL Server connection
string to support the Microsoft SQL Server Always On for availability groups feature for the SQL Server
repository.

For more information about Always On for availability groups and Multi-subnet failovers, see the Microsoft
documentation.

9.3 Behavior changes in version 14.3.00.00

Changes in the behavior of SAP Data Services 4.3 Support Package 00 (14.3.00) and its patches from previous
releases of Data Services.

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.

To obtain the latest version of documentation, visit the SAP Help Portal at https://help.sap.com/viewer/p/
SAP_DATA_SERVICES.

9.3.1 New product keys required for 4.3

You must obtain a new 4.3 product key the first time you install, upgrade, or update Data Services 4.3. You will
not be asked to enter the new product key for future 4.3 upgrades or updates.

 Note

The 4.3 product keys are not backwards compatible and do not work with older versions of Data Services.

Upgrade Guide
34 PUBLIC Data Services behavior changes
9.3.2 Update connection for Oracle repository with TCPS

SAP Data Services 4.3.00.00 introduces new TCPS options for Oracle repositories. Previously, you entered
TCPS settings in a connection string. Therefore, if your current Oracle repository has TCPS enabled, you must
reactivate the Oracle repository after you upgrade to SAP Data Services 4.3.00.00.

Check the status of your Oracle repository after upgrade in the Central Management Console (CMC). If the
status is Inactive, you must perform additional steps to reactivate it.

To reactivate the repository, log into the CMC and perform the following steps:

1. Open the Data Services page from the CMC home screen.
2. Select the applicable Oracle repository from the Repositories node.
3. Select Actions Properties.
4. Complete the following options:
• Database Server Name (host name)
• Port
• SID or Service Name
• Distinguished Name
• SSL TrustStore Password, if applicable
• SSL KeyStore Password, if applicable
5. Test the connection.
6. When the connection test is successful, select Save.

For option descriptions, see the Administrator Guide.

9.3.3 Update connection for Microsoft SQL Server repository

SAP Data Services 4.3.00.00 introduces new options for Microsoft SQL Server repositories to enable SSL/TLS
protocol. If you have a SQL Server repository and then upgrade to 4.3.00.00, the repository in the Central
Management Console (CMC) shows your repository as inactive. Therefore, after you upgrade, you must
reactivate the SQL Server repository in the CMC.

Check the status of your SQL Server repository in the CMC after you upgrade. If the status is Inactive, perform
the following additional steps to reactivate it:

1. Open the Data Services page from the CMC home screen.
2. Select the applicable SQL Server repository from the Repositories node.
3. Select Actions Properties.
4. Complete the following options:
For repositories that use either the ODBC or the JDBC driver:
• Enable SSL
• Verify Server Certificate
For repositories that use the JDBC driver:
• Host Name in Certificate

Upgrade Guide
Data Services behavior changes PUBLIC 35
 • SSL KeyStore
• SSL KeyStore Type
• SSL KeyStore Password
• SSL TrustStore
• SSL TrustStore Type, if applicable
• SSL TrustStore Password, if applicable
5. Test the connection.
6. When the connection test is successful, select Save.

For option descriptions, see the Administrator Guide.

9.3.4 Update connection for MySQL repository

SAP Data Services 4.3.0.00 introduces new options for MySQL repositories to enable SSL/TLS protocol.
Because of the new options, if you have a MySQL repository and then upgrade to 4.3.00.00, the repository in
the Central Management Console (CMC) shows your repository as Inactive.

Therefore, after you upgrade, you must reactivate the MySQL repository in the CMC. When you reactivate the
repository, you can optionally enable the SSL/TLS protocol.

Check the status of your MySQL repository in the CMC after you upgrade. If the status is Inactive, perform the
following additional steps to reactivate it:

1. Open The Data Services page from the CMC home screen.
2. Select the applicable MySQL repository from the Repositories node.
3. Select Actions Repositories.
4. Complete the following options:
• Host Name
• Port Number
• Enable SSL (if applicable)
• Encryption Parameters (if applicable):
• RSA Public Key
• SSL CA File
• SSL Certificate
• SSL Cipher
• SSL Key
• SSL KeyStore
• SSL KeyStore Password
• SSL KeyStore Type
• SSL Mode
• SSL TrustStore
• SSL TrustStore Password
• SSL TrustStore Type

Upgrade Guide
36 PUBLIC Data Services behavior changes
  Note

For option descriptions, see the topic “Registering MySQL repository with SSL/TLS in the CMC” in the
Administrator Guide.

5. Test the connection.

6. When the connection test is successful, select Save.

9.3.5 New default value for the Validate certification option

In new jobs, the Validate certification option is now disabled by default when using the SSL protocol for the
Microsoft SQL datastore.

In versions prior to Data Services 4.3 SP00, the Validate Certificate option was enabled by default.

When Validate certification is disabled, you can use the SSL protocol without having to validate the server
certificate.

For more information, see “Microsoft SQL Server database datastore options” in the Designer Guide.

Upgrade Guide
Data Services behavior changes PUBLIC 37
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Upgrade Guide
38 PUBLIC Important Disclaimers and Legal Information
Upgrade Guide
Important Disclaimers and Legal Information PUBLIC 39
www.sap.com/contactsap

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN