PUBLIC

SAP Information Steward

Document Version: 4.3 Support Package 2 (14.3.2.0) – 2023-11-21

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

THE BEST RUN

Content

1 About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Upgrade to SAP Information Steward 4.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1 Upgrade an existing environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Upgrading your existing environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Re-enable SSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Upgrading metadata collection from BusinessObjects Enterprise 3.x. . . . . . . . . . . . . . . . . . . . . . 8
Upgrade considerations for Match Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Upgrade considerations for Data Insight views that contain SAP tables. . . . . . . . . . . . . . . . . . . . .9
2.2 Verify upgrade success. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Checking the Information Steward version in the CMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Data Cleanse upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Content upgrade log file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Migrate to a new environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

3.1 Migrating Information Steward to a new environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Example: Migrating Information Steward 14.3.x Oracle database. . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2 Objects supported for migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3 Migrating CMS content using Promotion Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

4 Information Steward behavior changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.1 Changes in version 4.3 SP00 (14.3.00). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2 Changes in version 4.3 SP1 (14.3.01). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3 Changes in version 4.3 SP2 (14.3.02). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Upgrade Guide
2 PUBLIC Content
1 About this guide

Use this guide to help you with upgrading to a new SAP Information Steward version. Refer to the latest Release
Notes for version information. Also use this guide to review the changes in the latest version and past versions
of Information Steward.

This guide contains the following upgrade topics:

• Upgrade from previous versions of Information Steward

• Behavior changes associated with each version of Information Steward
• Upgrade metadata collection from SAP BusinessObjects Enterprise 3.x machine

Upgrade Guide
About this guide PUBLIC 3
2 Upgrade to SAP Information Steward 4.3

Based on your system setup, there are several ways to upgrade to the latest version of Information Steward.

For information about the compatibility between Data Services and Information Steward and BI or IPS,
see KBA 3197694 and the Product Availability Matrix located at https://userapps.support.sap.com/sap/
support/pam . To go directly to Information Steward, enter “Information Steward” in the search field.

 Note

You must obtain a new 4.3 product key the first time you install, upgrade, or update Data Services and
Information Steward 4.3. The 4.3 product keys are not backwards compatible and do not work with older
versions of the product.

The following list illustrates common supported installation sequences for upgrading Business Intelligence
platform (BI) SPx Patch y (where x and y can be a valid BI supported support pack and patch version), Data
Services, and Information Steward to the latest version. Information platform services (IPS) can be used in
place of BI in any of these sequences.

Upgrade method Description

Fresh install First time installation of Data Services (DS) and Information Steward (IS). No previously con-
figured objects. Use this method when you are new to the product or using the product in a
new environment.

Note [1] + BI/IPS 4.3 SPx Patch y [2] + Data Services 4.3 SPxx + Information Steward 4.3 SPxx

 Note
[1]: If your Data Services environment is on the early version of Windows prior to Windows
10 or Windows Server 2016 (for example, Windows 2008, Windows 2008 R2, Windows
2012, or Windows 2012 R2), you must apply a Windows Package update before upgrading.
Refer to SAP Note 2451830 for more information.

[2]: For information about obtaining a license key for running a full or fresh installation of
Information platform services (IPS), see KBA 3208592 .

Upgrade install with unin- Uninstall previous versions of Data Services and Information Steward before installing the
stall/reinstall
most current version. Reuse the configurations from the previous installation.

Use this option when upgrading from version 3.x to 4.3 SPxx.

Upgrade Guide
4 PUBLIC Upgrade to SAP Information Steward 4.3
Upgrade method Description

Upgrade install with up- Install the current version of Data Services and Information Steward without uninstalling previ-
date capability
ous versions. Automatically reuse configurations from the previous installation.

There are several options for the upgrade install based on your previous installation of
Information Steward.

• Scenario 1: Upgrade from an existing Data Services and Information Steward 4.0 SPx
installation
BI/IPS 4.0 SPx Patch y + Data Services 4.0 SPx Patch y + Note[2] + Information Steward
4.0 SPx Patch y + BI/IPS 4.3 SPx Patch y + Data Services 4.3 SPxx + Information Steward
4.3 SPxx[1]
• Scenario 2: Upgrade from an existing Data Services and Information Steward 4.1 SPx
installation
BI/IPS 4.1 SPx Patch y + Data Services 4.1 SPx Patch y + Information Steward 4.1 SPx
Patch y + BI/IPS 4.3 SPx Patch y + Data Services 4.3 SPxx + Information Steward 4.3
SPxx[1]
• Scenario 3: Upgrade from an existing Data Services and Information Steward 4.2 SPx
installation
BI/IPS 4.2 SPx Patch y + Data Services 4.2 SPx Patch y + Information Steward 4.2 SPx
Patch y + BI/IPS 4.3 SPx Patch y [3] + Data Services 4.3 SPxx + Information Steward 4.3
SPxx[1]

 Note
[1]: A Data Services repository upgrade is mandatory. For more information, see the
SAP Data Services Upgrade Guide.

[2]: If your Data Services environment is on the early version of Windows prior to
Windows 10 or Windows Server 2016 (for example, Windows 2008, Windows 2008
R2, Windows 2012, or Windows 2012 R2), you must apply a Windows Package update
before upgrading. Refer to SAP Note 2451830 for more information.

[3]: You must obtain new 4.3 product keys the first time you install, upgrade, or
update Information Steward 4.3. The 4.3 product keys are not backwards compatible
and do not work with older versions. In addition, after installing BI/IPS, you will need
to remove both the BI/IPS 4.2 and IS 4.2 license keys in the CMC and then add the
new BI/IPS 4.3 license key. All the servers in the CMS must also be re-enabled before
proceeding. For more detailed upgrade instructions, see Upgrading your existing envi-
ronment [page 7].

For additional information about installing the software, see the Master Guide and the Install Guide.

Related Information

Preparation [page 6]
Verify upgrade success [page 10]

Upgrade Guide
Upgrade to SAP Information Steward 4.3 PUBLIC 5
2.1 Upgrade an existing environment

Run the Information Steward setup file to begin the upgrade process.

The installer detects that a version of Information Steward is already installed and upgrades the features that
are already installed to the new version.

 Note

In a distributed deployment where the primary installation is on a Linux computer and an expanded
installation is on one or more Windows computers, you must upgrade the Linux computer before you
upgrade the Windows computers.

For additional upgrade scenarios, see the Master Guide.

For information about installing new or additional features, see the Installation Guide.

2.1.1 Preparation

Task you need to complete before you can upgrade Information Steward to a newer version or service pack.

To prepare for the upgrade, do the following:

• Obtain new 4.3 product keys as you will need them the first time you install, upgrade, or update
Information Steward 4.3.

 Note

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

• Back up your Information Steward repository using the backup utility provided by your database vendor.
Make sure that your database backup allows you to restore all of the repository tables and data.
• Export your user-created content such as projects or their contents (tables, rules, rule binding, scorecards,
and so on), custom attributes, Metapedia terms, and categories.
• Upgrade the SAP Business Intelligence (BI) platform or Information platform services (IPS).
• Upgrade the BI platform client to the same version as the BI server if a BI platform client is installed on the
machine where Information Steward is installed. Likewise, if you use an IPS client, upgrade it to the same
version as the IPS server if an IPS client is installed on the machine where Information Steward is installed.
• Upgrade SAP Data Services to a version that is compatible with the version of Information Steward.
• Update the Data Services-supplied SAP transport files and SAP authorizations on the SAP server. For more
information, see the SAP Data Services Supplement for SAP.
• Disable the Secure Socket Layer (SSL) protocol on the Central Management server (CMS) if applicable.
The Information Steward installer does not support the SSL protocol during the installation process.

Upgrade Guide
6 PUBLIC Upgrade to SAP Information Steward 4.3
2.1.2 Upgrading your existing environment

Steps to complete to upgrade to the latest version of Information Steward.

Before installing the latest version of Information Steward, you must also install BI/IPS and the latest version of
Data Services.

The following steps assume you are upgrading from 4.2.xx to the latest version of Information Steward.

1. Run an Upgrade install for SAP Business Intelligence (BI) platform or Information platform services (IPS).
2. After running the BI/IPS 4.3 Upgrade installation, remove the BI or IPS 4.2 license key and the Information
Steward 4.2 license key in the CMC. Then, add the BI/IPS 4.3 license key into the CMC.

 Note

All servers in the CMS must be re-enabled before proceeding to subsequent upgrades.

3. Run an Upgrade install for Data Services 4.3 SPxx. Enter the Data Services 4.3 license key during
installation. Check the SAP BusinessObjects Enterprise (BOE) server status after installation. All servers
should be running without errors.
4. Launch the setup program for the new version of Information Steward as follows:

• On Windows, double-click setup.exe. In the setup program, set the installation location to the same
location as your current installation of
• On Linux, type ./setup.sh.
5. Enter the Information Steward 4.3 license key.
6. In the setup program, set the installation location to the same location as your current installation of
Information Steward.
The installer detects that a version of Information Steward is already installed and updates existing
features. When applicable, choose to install new features and new optional objects.
7. Enter administrator-level connection information for your Central Management Server (CMS).
When you are upgrading Information Steward, the CMS connection automatically retrieves all connection
data except the password. When prompted, enter the repository password.
8. Re-enable all servers in the CMS before proceeding to subsequent upgrades.
9. If you are upgrading a repository of database type DB2 or connection automatically retrieves all connection
data except the password. When prompted, enter the repository password. SAP HANA the Data Source
Name or Database Connection Name parameter still appears. You cannot change to a server name
connection.
10. If you want to be able to use Information Steward's Data Cleansing Advisor feature, enable the Data
Cleansing Advisor service as follows:

a. In the Central Management Console, choose Servers Service Categories Core Services .
b. Stop the EIMAdaptiveProcessingServer.
c. Right-click EIMAdaptiveProcessingServer and choose Select Services.
d. Move Data Cleansing Advisor Service from the list of available services to the list of services for
EIMAdaptiveProcessingServer.
11. If you have a distributed environment, upgrade each machine that hosts Information Steward components
to the new version of Information Steward. The order in which you upgrade the machines does not matter.

Upgrade Guide
Upgrade to SAP Information Steward 4.3 PUBLIC 7
Related Information

Verify upgrade success [page 10]

Migrate to a new environment [page 13]

2.1.3 Re-enable SSL

SSL protocol needs to be enabled on the CMS or a web application server before upgrading.

If you use the SSL protocol on the CMS or a web application server and you disabled it prior to installing
Information Steward, you must re-enable it before you use the upgraded Information Steward application.

For more information, see the SAP BusinessObjects Information Platform Services Administrator Guide and
the SAP BusinessObjects Business Intelligence Platform Administrator Guide.

2.1.4 Upgrading metadata collection from BusinessObjects

Enterprise 3.x

Steps to upgrade the metadata collection on an SAP BusinessObjects Enterprise XI 3.x machine to the newest
version of Information Steward.

The SAP BusinessObjects Enterprise Metadata Integrator in the new version of Information Steward uses a
remote job server to collect metadata from an SAP BusinessObjects Enterprise XI 3.x machine.

Before you upgrade the remote job server in SAP BusinessObjects Enterprise XI 3.x:

• Upgrade your primary installation of Information Steward.

• Disable the SSL protocol (if applicable) in the CMS. The Information Steward installer does not support the
SSL protocol during the installation process.

To upgrade the remote job server installed on an SAP BusinessObjects Enterprise XI 3.x machine:

1. On the computer where SAP BusinessObjects Enterprise XI 3.x is installed, follow a standard installation
for Information Steward until you come to the BusinessObjects Enterprise Server Login window.
2. Specify the login information for the Central Management Server (CMS) that you will use to configure and
schedule integrator source runs and click Next.
The installation wizard detects that a previous version of the Information Steward Remote Job Server is
installed and automatically upgrades it.

If you disabled the SSL protocol on the CMS, re-enable it after you have upgraded Information Steward.

For more information about upgrading metadata from BusinessObjects Enterprise 3.x, see the SAP Information
Platform Services Administrator Guide and the SAP Business Intelligence Platform Administrator Guide

Upgrade Guide
8 PUBLIC Upgrade to SAP Information Steward 4.3
2.1.5 Upgrade considerations for Match Review

Tasks to perform before you can upgrade your match review configurations.

Before you run the installation wizard, perform the following tasks:

• Ensure existing match review configurations do not use the same database connection and input table
name. If match review tasks with status In Progress exist and different match review configurations
reference an input table with the same name, the match reviewer can only work on the input table that was
worked on first.
• Finish all match review tasks with status In Progress. If tasks with status In Progress exist when the
installation wizard upgrades the match review configurations, the reviewed data will also be migrated.

2.1.6 Upgrade considerations for Data Insight views that

contain SAP tables

Default data transfer methods for Data Insight views that contain SAP tables.

The data transfer method for reading SAP tables contained in Data Insight views is specified when your
Administrator defines the connection in the Central Management Console (CMC). The default data transfer
method is different for some Information Steward releases, as the following table shows:

Information Steward
release version Default Data Transfer Method Additional information

4.2 SP1 ABAP You can also specify RFC (Remote Function Call), Shared direc-
tory, or FTP.

4.2 SP2 RFC ABAP is disabled for all views.

4.2 SP3 RFC You can now enable ABAP for a Data Insight view with the new
Data Transfer Method option in the View Editor.

Upgrade Guide
Upgrade to SAP Information Steward 4.3 PUBLIC 9
2.2 Verify upgrade success

After upgrading your existing environment to a new version of SAP Information Steward, verify that the servers
are running and the version number has been updated.

Verify Steps

The EIMAdaptiveProcessing- 1. Log on to the CMC.

Server and ISJobServer in
the Central Management
Console (CMC) should be
running and enabled. If they
are not enabled, restart and
enable them.
2. Select Servers from the Organize drop list on the CMC Home page.
3. Expand Service Categories in the file tree at left.
4. Click Enterprise Information Management Services listed under the Service Categories
folder.
5. Scan the servers listed at right to make sure the State column contains “Running” and
the Enabled column contains “Enabled.”

If the Enterprise Information Management Server is not running or enabled:

1. Select the server name from the list and click Actions.
2. Select Start Server or Enable Server as applicable.

The SAP Information Choose one of the following methods:

Steward software installed on
your system should reflect
the newest version number.
• View a list of installed programs from your operating system, and verify SAP Informa-
tion Steward is the version that you just installed.
• In Windows, open the Control Panel and view the list of installed programs.
• In Linux, change to the directory where Information Steward is installed, and run
the command ./modifyOrRemoveProducts.sh.

• Check the version in Information Steward by choosing Help About .

 Note
If the version in the About box is not the latest version, your web deployment may have
failed. Use WDeploy to redeploy the Information Steward web application.

If the installation process completed with a warning message that the Information Steward repository upgrade
failed, you must manually upgrade the repository with the ISRepositoryUtility command-line utility. For
details, see the Administrator Guide.

Related Information

Installation Guide: Verifying Information Steward servers are running

Installation Guide: Deploy web applications

Upgrade Guide
10 PUBLIC Upgrade to SAP Information Steward 4.3
2.2.1 Checking the Information Steward version in the CMC

After upgrading, verify that the version number has been updated in the CMC.

To check the installed version of Information Steward in the Central Management Console (CMC):

1. Log on to the CMC.

2. Select Servers from the CMC Home page drop list.
3. Click Servers List.
4. Right-click an Information Steward server, for example, ISJobServer, and select Metrics.
The version is displayed in the list of Common Server Metrics in the Version row.
5. Click OK to close the window.

2.3 Data Cleanse upgrade

Upgrade options for new versions of Information Steward when there are changes to the Cleansing Package
Builder mode.

There are two possible upgrade options:

• Schema upgrade: applies to published and private cleansing packages.

• Content upgrade: applies changes to the Person_Firm cleansing package. Custom cleansing packages
cannot be used in the content upgrade process.

Schema upgrade

A schema upgrade applies to published cleansing packages. The schema upgrade affects classifications and
the underlying structure of the cleansing package necessary for use with the Data Cleanse transform.

Upgrading the schema does not automatically upgrade the content. Additionally, if you want to upgrade the
Person_Firm cleansing packages, see the Content Upgrade section.

To upgrade the published cleansing package schema, open, modify, and then republish the cleansing package.
Private cleansing package schemas are automatically updated when they are edited and during merge or
content upgrade process.

Content upgrade

A content upgrade applies only to Person_Firm cleansing packages. The term content refers to the data of the
cleansing package: standard forms, variations, reference data, and rules. Content upgrade does not apply to
custom cleansing packages.

For more information, see the Information Steward User Guide.

Upgrade Guide
Upgrade to SAP Information Steward 4.3 PUBLIC 11
2.3.1 Content upgrade log file

The software writes all errors and warnings for a content upgrade to a log file.

Administrators can find the log file in the platform's logging folder.

The log file name includes the name of the service where Cleansing Package Builder's Publishing Service is
installed. By default, the location is in the EIM Adaptive Processing Server. Use the date and time listed in the
file explorer to help determine the correct log file.

Example

In Windows, find the log file in <%BOE_Install%>\SAP BusinessObjects Enterprise XI

<current_version>\logging

Example

Log file name: aps_<system_name>.EIMAdaptiveProcessingServer_trace.<number>.glf

Upgrade Guide
12 PUBLIC Upgrade to SAP Information Steward 4.3
3 Migrate to a new environment

You may want to migrate Information Steward to expand to a distributed environment or to install Information
Steward on a separate Information platform services (IPS).

 Note

We recommend installing Information Steward on a separate IPS. You should upgrade to the most recent
Information Steward version before you migrate to a new environment.

3.1 Migrating Information Steward to a new environment

Steps to migrate your existing Data Services and Information Steward deployment in a Business Intelligence
(BI) platform 4.x landscape to a private Information platform services (IPS) landscape on new hardware.

Before migrating to a new environment, install the latest supported version of SAP BI Platform or SAP
Information platform services (IPS). For compatibility information, see KBA 3197694 and the Product
Availability Matrix (PAM) . We recommend that you install IPS and then install the latest versions of Data
Services and Information Steward.

Because this scenario involves hardware migration, you need a new server machine on which to install IPS,
Data Services, and Information Steward. For information about upgrading Data Services, see the SAP Data
Services Upgrade Guide.

The following steps apply when moving the same version of Information Steward from one computer to
another or to a higher version.

 Note

See the SAP Data Services and SAP Information Steward Master Guide to read about migrating to a
distributed environment.

1. Back up your existing Information Steward 4.x repository.

2. Export the following Information Steward objects to a Lifecycle Management Business Intelligence Archive
(LCMBIAR) file from existing Information Steward 4.x:
a. User-created Data Insight projects, excluding Enterprise Project, unless you have tasks in this project.
Include all dependent tasks.
b. Data Insight connections, excluding the system default Views connection, which is created during
instrallation.
c. Integrator source configurations (if using Metadata Management).
d. Integrator source group configurations (if using Metadata Management).
e. Match Review configurations (if using Match Review).
3. Create a new database of the same type as the existing Information Steward 4.x repository database. This
will be used to create a temporary Information Steward 4.x repository during installation.

Upgrade Guide
Migrate to a new environment PUBLIC 13
4. In the new environment, install the latest compatible version of SAP BI Platform or SAP Information
platform services (IPS) so that a new Central Management Server (CMS) repository is created.
5. In the new environment, install the latest version of SAP Data Services 4.x.
6. In the new environment, install the latest version of Information Steward 4.x. During installation, make the
following selections:
a. Select the primary installation type.
b. Enter the connection information for the CMS on the new IPS.
c. Use database connection information of the database created in step 3 for the Information Steward
repository. This will create a default Information Steward repository.

Ensure that all Information Steward services are up and running successfully in the new environment
before continuing with the next steps.
7. Restore the backup of the existing Information Steward 4.x repository. This repository will be linked to the
new Information Steward Installation.
8. Find the CUID of the new Information Steward repository, in the new environment. This is a blank
repository with only system data. The repository CUID will be used to link the old repository to the CMS
of this new environment. To get the MM_REPO_CUID, connect to the new Information Steward repository
from any SQL tool and run the following, noting the value of the parameter_value column:

SELECT parameter_value FROM MMD_Parameter WHERE technical_name = 'MM_REPO_CUID'

9. Update the CUID of the Information Steward repository restored from backup in step 7.

UPDATE MMD_Parameter SET parameter_value = 'enter the MM_REPO_CUID value returned

from the select SQL Query in step 8' WHERE technical_name = 'MM_REPO_CUID'
10. Import the Information Steward CMS objects using Promotion Management from the LCMBIAR created in
step 2.
11. Stop the following Information Steward services on all nodes, and keep them stopped until all the steps are
done:
a. EIMAdaptiveProcessingServer
b. ISJobServer
12. Edit the <installRoot>/InformationSteward/MM/config/InstallUtility.properties file,
updating the repository connection information to the repository database restored in step 7.
13. Run the ISRepositoryUtility from the command line.
a. cd <InstallRoot>/InformationSteward/MM/bin
b. ISRepositoryUtility.bat(on Windows) or./ISRepositoryUtility.sh(on Linux) upgrade
boeUse Administator boePassword CMS_ADMINISTRATOR_PASSWORD password
IS_REPOSITORY_PASSWORD

 Note

Run the utility in upgrade mode even when the Information Repository is from the same
Information Steward version. The upgrade mode will update the data only if it’s not up to date.

14. Clean up the existing environment-related runtime information from the repository restored in the step 7.
Run the following SQL commands from SQL tool:
a. DELETE FROM MMT_Ep_Ds_Obj
b. DELETE FROM MMT_Ep_Ds_Obj_Details

Upgrade Guide
14 PUBLIC Migrate to a new environment
 c. Recreate all Data Insight tables that are used for profiling and rule task by recreating the Data Services
repository tables used by Data Insight using RepomanBatch on Windows and repoman on Linux from
command line from %LINK_DIR%\bin on Windows and $LINK_DIR/bin on Linux:

For SAP HANA Database

RepomanBatch(Windows) or ./repoman(Linux) -NHAVA -SHANADBServer -UISREPOUser

-PISREPOPassword -pHANADBport -tinformation_steward -s -c -o

For Sybase ASE Database

RepomanBatch(Windows) or ./repoman(Linux) -NSybase -SSybaseDBServer

-UISREPOUser -PISREPOPassword -QSybaseDBName -tinformation_steward -c -o

For SQL Anywhere Database

RepomanBatch(Windows) or ./repoman(Linux) -NSQLAnywhere -SSybaseDBServer

-UISREPOUser -PISREPOPassword -QSQLAnywhereDBName -pSQLAnywhereDBport
-tinformation_steward -s -c -o

For Microsoft SQL Server Database

RepomanBatch(Windows) or ./repoman(Linux) -NMicrosoft_SQL_Server

-SMSSQLDBServer -UISREPOUser -PISREPOPassword -QMSSQLDBName
-tinformation_steward -c -o

For Oracle Database

RepomanBatch(Windows) or ./repoman(Linux) -NOracle -SORADBServer

-UISREPOUser -PISREPOPassword -V"Oracle 11g" -QOracleSID -pOracleDBport
-tinformation_steward -s -c -o
15. Create a new job server using the Data Services server manager and associate it with the Information
Steward repository.
16. You can promote cleansing packages to the upgraded environment using the Promotion Management tool
in the CMC.

1. The user security for Data Insight Project, Connection and other objects in CMS may not get promoted. Set
up the user security again in new system.
2. The rule author, approver and observer may have been reset to blank. Edit the rule to fix the author,
approver, and observer.
3. Create a new failed data database or use a copy of old failed data database else the failed data of existing
environment would be corrupted. Use SAP Note 1863547 for Windows and use SAP Note 2592327 for
Linux to update the failed data connection in the new environment.
4. The rule task may fail with error “com.sap.icc.dataservices.api.DSAPIException:
com.sap.icc.sdk.connection.NoSuchConnectionException: Object of type ICC.Connection named xxxx
does not exist. (COR-10552)”. Edit all the rule tasks that are using the failed data connection and set
the failed data connection again.
5. If tasks were scheduled in CMS in the existing environment, the task schedules will not be migrated.
Recreate all the task schedules.
6. If the tasks are scheduled using an external tool and using the project and task id, then
regenerate the execution command for the task or use the project name (using parameter
-configurationProjectObjectName) and task name (using parameter -configurationTaskObjectName) in
the task execution command instead of using -configurationProjectObject and -configurationTaskObject.

You can find more information about many of these steps in the following guides:

Upgrade Guide
Migrate to a new environment PUBLIC 15
How to Resource

• Install Information Steward to a distributive environ- SAP Data Services and SAP IS Master Guide
ment
• Install Data Services components for Data Insight

Install Information Steward SAP Information Steward Installation Guide for Windows

SAP Information Steward Installation Guide for UNIX

• Create a new repository SAP Information Steward Administrator Guide

• Create new job server

Install IPS SAP Information platform services documentation

Install BI platform SAP BusinessObjects Business Intelligence Platform docu-

mentation

Promote a cleansing package using the Promotion Manage- CMC Help file ( Help Help ) or SAP Business Intelli-
ment tool gence platform Administrator Guide

Related Information

Objects supported for migration [page 19]

3.1.1 Example: Migrating Information Steward 14.3.x Oracle

database

Follow steps to migrate your SAP Information Steward repository to a new server with the same Information
Steward version. These steps can be followed if you are upgrading or migrating to a new environment.

This example walks you through migrating from an SAP Information Steward 14.3.x environment, using an
Oracle database, to a new server with the same SAP Information Steward 14.3.x version. Adjust steps as
needed if you are using a different database.

Some Information Steward objects are created from the Central Management Console (CMC), and some
objects are created from Information Steward Explorer. All the objects created from CMC are stored in the
Central Management Server (CMS) database, and a copy of these objects is saved in the Information Steward
repository. The unique object identifier from the repository is updated in the CMS object. To move an existing
Information Steward installation to new servers without losing the content, you must move this Information
Steward content from both the CMS and the repository.

Information Steward repository information is also stored in the CMS during installation. A unique CUID is
created during installation and saved in the repository and in the repository object in the CMS. This CUID is
used as a link between the CMS and the repository.

The following Information Steward objects are saved in the CMS:

• Data Insight projects

Upgrade Guide
16 PUBLIC Migrate to a new environment
• Profiling and rule tasks of projects
• Data Insight connections
• Integrator sources
• Integrator source groups

The following Information Steward objects are saved in the Information Steward repository:

• Projects, connections, tasks, and integrator sources

• Rules
• Rule binding
• Tables
• Virtual views
• Scorecard setup
• Metadata collected using integrators and so on

In the current (old) environment

Do the following in the existing SAP Information Steward environment.

1. Using Promotion Management, export the following Information Steward objects to a Lifecycle
Management Business Intelligence Archive (LCMBIAR) file:
• User-created Data Insight projects, excluding Enterprise Project, unless you have tasks in this project.
Include all dependent tasks.
• Data Insight connections, excluding the system default Views connection, which is created during
installation.
• Integrator source configuration (if using Metadata Management).
• Integrator source group configuration (if using Metadata Management).

 Note

This LCMBIAR file can be used to import the Information Steward CMS objects in the new
environment. Or you can use Promotion Management to promote the objects from the existing source
CMS to the new destination CMS.

2. Export or back up the Information Steward repository database.

In the new environment

Do the following in the new SAP Information Steward environment

It’s important that you complete the Information Steward installation using a new repository database of same
database type that you are using in existing environment. Do not point to the existing repository; this would
cause loss of the project and connection details.

Ensure that all Information Steward services are up and running successfully in new environment before
continuing with the next steps.

Upgrade Guide
Migrate to a new environment PUBLIC 17
1. 1. Find the CUID of the new Information Steward repository, in the new environment. This is a blank
repository with only system data. The repository CUID will be used to link the old repository to the CMS of
this new environment. Follow these steps to find the CUID:
1. If you have a BI installation, open BO Query Builder (http://BITomcat:port/AdminTools).
2. Log on to the CMS where Information Steward is installed.
3. Execute the following query:
SELECT * FROM CI_APPOBJECTS, CI_SYSTEMOBJECTS, CI_INFOOBJECTS WHERE SI_KIND =
'MM.Repository'
4. In the result that appears, note the value of the SI_MM_REPO_CUID property.
2. Connect to the new Information Steward repository from any SQL tool and run the following, noting the
value of the parameter_value column.
SELECT parameter_value FROM MMD_Parameter WHERE technical_name = 'MM_REPO_CUID'
3. Stop the following Information Steward services on all nodes, and keep them stopped until all the steps are
done:
• EIMAdaptiveProcessingServer
• ISJobServer
4. When all services are stopped, connect to the Information Steward repository from any SQL tool and drop
all the Information Steward views and tables created in the new repository. (Alternatively, you can drop
the database or schema (with the cascade option) and create it again with same default settings (same
password, tablespace, and so on).
5. Restore the existing Information Steward repository to the new database or schema (if you’re using
Oracle).
6. If you see an error about the following three tables related to datetime format, open a customer support
incident with component EIM-IS-SVR.
• MMT_Extended_Text
• MMT_User_Preference
• MMT_Equivalency_Rule
7. When the schema is restored, and if there is no error about the three tables listed above, make sure all the
views are valid. If anything is invalid, fix those issues.
8. Replace <IS_REPO_SCHEMA> with the value of the new schema from your environment.
9. Import only the three tables listed above and use TABLE_EXISTS_ACTION=TRUNCATE.
10. Update the Information Steward repository CUID in the new repository with the value that you saved in
Step 1. Use the following SQL to update the value:
UPDATE MMD_Parameter SET parameter_value = 'cuid value' WHERE technical_name =
'MM_REPO_CUID'
11. Update the existing environment-related runtime information from the new repository. (If you do not do
this, the Data Insight task would run on the existing job server and try to use the existing repository
connection.) Run the following SQL commands:
• DELETE FROM AL_MACHINE_INFO WHERE SEQNUM = enter the seqnum value of the job server entry.
Delete only job server information.
• DELETE FROM IMMT_Ep_Ds_Obj.
• DELETE FROM MMT_Ep_Ds_Obj_Details.
• Recreate all Data Insight tables that are used for profiling and rule task by recreating the Data Services
repository tables used by Data Insight using RepomanBatch on Windows and repoman on Linux.
./repoman -NOracle -SORADBServer -UISREPOUser -PISREPOPassword -V"Oracle 11g"
-QOracleSID -pOracleDBport -tinformation_steward -s -c -o
or

Upgrade Guide
18 PUBLIC Migrate to a new environment
 RepomanBatch -NOracle -SORADBServer -UISREPOUser -PISREPOPassword -V"Oracle
11g" -QOracleSID -pOracleDBport -tinformation_steward -s -c -o
12. Import the Information Steward CMS content from the existing CMS to the new CMS using Promotion
Management, either by importing the content from the LCMBIAR backup or by moving the content directly
from the existing CMS to the new CMS.
13. Start the EIMAdaptiveProcessingServer and ISJobServer. When the services are up, check the content in
CMC to ensure everything appears correct.
14. Check the content in Information Steward Explorer. Don't run any tasks or create any new objects yet.
Make sure that the contents show up correctly, including the scorecards.
15. Add the repository to a new Job Server using svrcfg (on Linux) or Server manage (on Windows)
16. Restart the EIM Adaptive Processing Server and the Information Steward Job Server services and start
using the new Information Steward environment.

3.2 Objects supported for migration

Use the Promotion Management tool in the Central Management Console (CMC) to move Information Steward
objects from an existing Information Steward environment to the new Information Steward environment.

For instructions see Migrating CMS content using Promotion Management [page 20].

All the information associated with each object, including user security, is retained. Access more information
about the Promotion Management tool in the CMC Help file ( Help Help ).

To access the Promotion Management tool:

1. From the CMC Home page, select Promotion Management from the Manage list. The Promotion Jobs tab
opens.
2. Select New Job and complete the options as applicable.
3. Click Create. The new job is created, and the Add Objects from the system dialog box opens.

You can move the following objects from the Add Objects from the system dialog box. For each object, select
the objects and click Add, or Add & Close.

Object Path in Promotion Management

Profiling connections Select Information Steward Connections from the file

tree at left.

Data Insight projects Select Information Steward Enterprise Profiling

Projects from the file tree at left.

Profiling tasks and rule tasks

1. Select Information Steward Enterprise Profiling
Projects from the file tree at left.
2. Click Manage Dependencies.

Metadata Management Integrator Sources Select Information Steward Metadata Management

Integrator Sources from the file tree at left.

Upgrade Guide
Migrate to a new environment PUBLIC 19
Object Path in Promotion Management

Metadata Management Source Groups Select Information Steward Metadata Management

Source Groups from the file tree at left.

User-created utilities and scheduling information for Infor- Select Information Steward Metadata Management
mation Steward utilities
Utilities from the file tree at left.

Metapedia user security settings Select Information Steward Metadata Management

Metapedia from the file tree at left.

Published cleansing packages Select Data Quality Cleansing Packages Published

from the file tree at left.

Private cleansing packages Select Data Quality Cleansing Packages Private

from the file tree at left.

Information Steward security (users and user groups) 1. Select the applicable user type (such as User or User
Groups) from the file tree at left.
2. Choose the applicable user groups.

3.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.

Upgrade Guide
20 PUBLIC Migrate to a new environment
 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.
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

Upgrade Guide
Migrate to a new environment PUBLIC 21
 Product Object Path in Promotion Management

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

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

Upgrade Guide
22 PUBLIC Migrate to a new environment
  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.
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

Upgrade Guide
Migrate to a new environment PUBLIC 23
 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”.

Upgrade Guide
24 PUBLIC Migrate to a new environment
4 Information Steward behavior changes

Behavior changes associated with the Information Steward product since version 14.3.00.

Each behavior change is listed under the version number in which the behavior originated.

For information about behavior changes in the 4.2 releases, see the Information Steward 4.2 Upgrade Guide on
the help portal.

4.1 Changes in version 4.3 SP00 (14.3.00)

Behavior changes that occurred in the Information Steward 4.3 Service Pack 00 release.

New process for publishing data cleansing solutions

SAP Information Steward 4.3 SP0 has a new method for publishing your data cleansing solutions that
bypasses SAP Data Services Workbench. The new method publishes the solution directly to the SAP Data
Services repository, so that the solution is immediately available as a data flow in Data Services.

Before you upgrade to Information Steward version 4.3 SP00, perform the following steps:

1. Check Workbench for any data cleansing solutions that you haven't exported to Data Services.
2. Export the existing data cleansing solutions in Workbench to an ATL file.
3. Import the ATL files to Data Services.
4. Perform the upgrade.

If you upgrade before you perform the previous steps, open Information Steward version 4.3 SP00 and perform
the following steps:

1. Open the Data Cleansing Advisor tab in Data Insight.

2. Check the list of existing data cleansing solutions for any solutions that you didn't export to Data Services
from Workbench before the upgrade.

 Note

Data Cleansing solutions are included when you export a project as part of the upgrade process. For
more information about upgrading, see Upgrade an existing environment [page 6].

3. Make sure the solution is in the “Ready” state.

 Note

If Data Insight purged the staged data as part of normal cleanup processes, the solution has a status of
“Archived”. For instructions to restore archived cleansing solutions, see the User Guide.

Upgrade Guide
Information Steward behavior changes PUBLIC 25
4. Publish the data cleansing solution using the new option, Export to Data Services.

If the solutions aren't listed in the Data Cleansing Advisor tab after you upgrade, and you still want to publish
them to Data Services, recreate the solutions using the Data Cleansing Advisor wizard.

4.2 Changes in version 4.3 SP1 (14.3.01)

No behavior changes occurred in the Information Steward 4.3 Service Pack 1 release.

4.3 Changes in version 4.3 SP2 (14.3.02)

No behavior changes occurred in the Information Steward 4.3 Service Pack 2 release.

Upgrade Guide
26 PUBLIC Information Steward behavior changes
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
Important Disclaimers and Legal Information PUBLIC 27
www.sap.com/contactsap

© 2023 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