is 422 release notes en

is 422 release notes en
SAP Information Steward
Document Version: 4.2 Support Package 2 (14.2.2.0) - 2014-05-29
Release Notes
Table of Contents
1
Compatibility update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
2
Restrictions update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
3
Installation and upgrade considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4
Known issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
5
Fixed issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1
Issues fixed in support packs and previous patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
5.2
Issues fixed in this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
6
SAP Information Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Release Notes
Table of Contents
1
Compatibility update
Before upgrading to Information Steward 4.2 SP2, ensure that the following prerequisite software has been
installed:
●
SAP BusinessObjects Business Intelligence (BI) platform 4.1 SP2 or SP3 or its higher compatible patches
or
SAP BusinessObjects Information platform services (IPS) 4.1 SP2 or SP3 or its higher compatible patches
●
SAP BusinessObjects Data Services 4.2 SP2 or higher compatible patches
For more information on the compatibility of Data Services with BI platform or IPS versions, see SAP Note
1740516
.
For the availability of any higher compatible patches, see the “Support Packages and Patches” area of the SAP
Service Marketplace.
For compatibility with SAP HANA, see SAP Note 1600140
.
For JDBC driver compatibility when connecting to Oracle, refer to SAP Note 1741042
.
For the latest updates in compatibility, see the Product Availability Matrix document located in the SAP Service
Marketplace: https://service.sap.com/PAM
Steward" in the search field.
Release Notes
Compatibility update
. To go directly to Information Steward, enter "Information
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
3
2
Restrictions update
The following restrictions apply to SAP Information Steward 4.2.
Common and new restrictions
●
Information Steward does not support the capability to deploy and run on an SAP BusinessObjects Business
Intelligence platform side-by-side environment (two versions of BusinessObjects Enterprise on the same
machine).
●
If Information Steward is running in an SSL environment, it can only connect to a BusinessObjects Enterprise
integrator source that is SSL. If Information Steward is not running in an SSL environment, it can only connect
to a BusinessObjects Enterprise integrator source that is also not SSL.
●
Installing Information Steward using Windows AD/LDAP/SAP authentication does not work. When installing
Information Steward, use Enterprise authentication. After installation is completed, you can switch to
Windows AD/LDAP/SAP authentication.
●
The Data Insight module of Information Steward cannot export more than 250 columns of data to a Microsoft
Excel file.
Currently, Data Insight supports exporting data to Microsoft Excel 2007 and older and does not support more
than 250 columns. As a workaround, you can selectively choose the columns to export, so that it will not
exceed 250 columns.
●
The Data Cleansing Advisor feature, which is available in the Data Insight module, currently generates data
cleansing solutions for party data only. Party data is data about individuals or organizations, such as name,
address, and phone data.
●
The Match Review feature does not support Sybase tables.
Data Services Integrator
●
●
The Metadata Management module of Information Steward does not support the following Data Integrator or
Data Services objects:
○
COBOL copybooks
○
DTDs
○
EXCEL workbooks
○
XML schemas
○
IDOCs
○
PeopleSoft domains
The Data Services Metadata Integrator does not collect metadata from memory datastores. It also doesn't
collect metadata if the Data Services repository is an Oracle RAC database.
Note
To configure a connection to an Oracle RAC database as the Data Services repository, you can specify a
single node for the service name in the repository connection input parameters.
4
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Release Notes
Restrictions update
BusinessObjects Enterprise Metadata Integrator
●
The BusinessObjects Enterprise Metadata Integrator does not collect metadata for the following objects:
○
Business Views
○
Crystal Reports that connect to XML files or Web Services
○
Desktop Intelligence documents based on 8-bit universe names
○
multi-dimensional .unx universes
●
The Metadata Management module of Information Steward still uses the term Universe classes for Universe
folders in .unx universes in SAP BusinessObjects Business Intelligence platform.
●
The BusinessObjects Enterprise Metadata Integrator will terminate any open Universe Designer and Desktop
Intelligence Designer sessions before it starts the collection. Ensure that no users are using the Designer
before you run the BusinessObjects Enterprise Metadata Integrator on the same computer.
Metadata Management
●
The Metadata Management module of Information Steward does not export objects collected by the MITI
Metadata Integrator.
●
The SQL parser in Metadata Management has limited parsing capabilities to collect column names and table
names to build the relationships. This limitation might occur in situations such as the following:
○
If you do not qualify column names in a derived table with the table name, the Metadata Integrator cannot
associate the column with the correct table and displays the following warning message:
Parsing failure for derived Table <table_name>.
Note
Qualify the column name with the table name: <table_name.column_name> or add the tables used
by the derived tables to the universe. The Metadata Integrator treats the universe tables as a system
catalog to find the table and column references.
○
If a Metadata Integrator fails to parse the SQL parser for a view, it cannot build the source-target
relationship between the view and the table or tables upon which the view is based and displays the
following warning message:
Unable to parse SQL: <error message>
Note
The Metadata Integrators collect the SQL statement and Metadata Management displays it. Analyze
the SQL statement in Metadata Management and establish a user-defined relationship for these tables
and columns.
●
Metadata Management does not export the SQL statement for a view to the CWM XML file.
●
The SAP Sybase PowerDesigner metadata integrator in Information Steward version 4.2 (14.2.0) works with
the SAP Sybase PowerDesigner application version 16.1 and newer. If you use SAP Sybase PowerDesigner
Release Notes
Restrictions update
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
5
version 16.0 and older, you need to continue to use the Meta Integration Metadata Bridge (MIMB) metadata
integrator for SAP Sybase PowerDesigner metadata collection.
6
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Release Notes
Restrictions update
3
Installation and upgrade considerations
SAP Information Steward 4.2 can be installed in either of the following ways:
●
As a new, full installation or uninstalling any previous Information Steward and Data Services versions.
●
As an upgrade on top of an existing Information Steward 4.0 or 4.1 version (without uninstalling the previous
version).
Full installation
The Information Steward 4.2 installer automatically detects whether a version of Information Steward is already
installed and then follows the appropriate workflow. If Information Steward is not already installed on the system,
the installer performs the full installation.
For more information about installing and configuring Information Steward, see the following resources:
●
For deployment and architecture information, see the Data Services and Information Steward Master Guide.
●
For full installation instructions, see the Installation Guide.
●
For additional installation and configuration troubleshooting tips, see SAP Note 1570523
.
Supported installation scenarios
The following list illustrates common supported installation sequences for upgrading Business Intelligence
platform (BI), Data Services, and Information Steward to Version 4.2. Information platform services (IPS) can be
used in place of BI in any of these sequences:
●
Scenario 1: New installation
BI 4.1 SP2/SP3 (full installation) + Data Services 4.2 SP2 + Information Steward 4.2 SP2
●
Scenario 2: Upgrade from existing DS/IS 4.0 installation
BI 4.0 SP2 + BI 4.0 patch 2.13 (or above) + Data Services 4.0.x + Information Steward 4.0.x + Data Services
4.2 SP2 + Information Steward 4.2 SP2
●
Scenario 3: Upgrade from existing DS/IS 4.1 installation
BI 4.0 SP4 (full installation) + Data Services 4.1 SP1 + Information Steward 4.1 SP1 + BI 4.1 SP2 (patch
installation) + Data Services 4.2 SP2 + Information Steward 4.2 SP2
●
Scenario 4: Upgrade from existing DS/IS 4.2 SP1 installation [1]
BI 4.1 SP2 (full installation) + Data Services 4.2 SP1 + Information Steward 4.2 SP1 + Data Services 4.2 SP2 +
Information Steward 4.2 SP2
Note [1]: Data Services repository upgrade is not mandatory. For more information, see the SAP Data
Services Upgrade Guide.
Release Notes
Installation and upgrade considerations
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
7
Upgrade installation
The Information Steward 4.2 installer automatically detects whether a version of Information Steward is already
installed and then follows the appropriate workflow:
●
If Information Steward is not already installed on the system, the installer goes through the full installation.
For full installation instructions, see the Install Guide. Also, see SAP Note 1570523
installation and configuration troubleshooting tips.
●
for additional
If an existing version of Information Steward is installed, the installer performs an upgrade installation.
For information about upgrading your Data Services and Information Steward landscape, see the Data
Services and Information Steward Master Guide. For more information about possible upgrade scenarios, see
SAP Note 1723435
.
You need to enter only the administrator-level password in the Central Management Server (CMS) connection
screen of the installer.
Upgrading after Information Steward 4.0 SP2 Patch 4 or Patch 5 was applied
If you applied Information Steward 4.0 SP2 Patch 4 or Patch 5, and upgrade to a higher patch level or service pack
level, you must run a repair install of Information Steward after installing it. On Windows, use the Repair Program
utility. On Linux, use the modifyOrRemoveProducts.sh utility. For more information, see SAP Note 1738878
.
Upgrading from Data Insight, Metadata Management, Data Services, or Data
Quality Management
When upgrading from BusinessObjects Data Insight 3.0, BusinessObjects Metadata Management 3.1, SAP
BusinessObjects Data Services 3.2, or SAP BusinessObjects Data Quality Management 3.2, license keys enable
access to comparable functionality in Information Steward modules. To enable full functionality of all Information
Steward modules and features, you must obtain and install a full Information Steward or Information Steward –
Multi-Source Metadata Integrators by MITI license key. For more information, contact your SAP account
executive.
The Information Steward modules enabled by each upgrade license and license name displayed in the CMC are
shown in the following table:
Upgrade from...
Information Steward module
Data In­
sight
BusinessObjects
Data Insight
8
Cleans­
ing
Package
Builder
Meta­
data
Man­
ÏÍ`…°ŸFò•
ment
√
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Name in CMC
Meta­
pedia
Meta Integration
Bridge Metadata
Integrator (MITI)
SAP BusinessObjects
Information Steward –
Platform for Data Insight
Release Notes
Installation and upgrade considerations
Upgrade from...
Information Steward module
Data In­
sight
Cleans­
ing
Package
Builder
Name in CMC
Meta­
data
Man­
agement
Meta­
pedia
BusinessObjects
Metadata
Management
√
√
BusinessObjects
Metadata
Management /
MITI
√
√
Meta Integration
Bridge Metadata
Integrator (MITI)
SAP BusinessObjects
Information Steward –
Platform for Metadata
Management
√
SAP BusinessObjects
Information Steward –
Platform for Metadata
Management with MultiSource Metadata Integrators
by MITI
SAP
BusinessObjects
Data Services
√
√
Data Services
SAP
BusinessObjects
DQM
√
√
Data Quality Management
Premium
After you install Information Steward, the license key information is available in the License Keys management
area of the CMC.
Data Insight and Metadata Management coexistence
Data Insight and Metadata Management products cannot be deployed to the same Central Management Server
(CMS). You must either obtain a full version of Information Steward or deploy the upgraded versions of Data
Insight and Metadata Management to separate CMS systems.
Release Notes
Installation and upgrade considerations
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
9
4
Known issues
This section lists known issues in descending order by internal issue identification tracking number. We also use
these numbers in the release notes that accompany our support packages and patches. You can reference the
issue ID when searching for the issue on our knowledge base or when speaking to SAP Business User Support.
When possible, workarounds are provided to help you resolve these issues.
Issue ID
Description
ADAPT01727174
DCA - RH6.5-SQL Anywhere ODBC is not configured during installation. When DCA
processes, an error is issued: “The ODBC Driver Manager library for data source is not
set. Set the <DQL_ANYWHERE_12_X_DRIVERMANAGER> environment variable by
running DSConnectionManager.sh.”
ADAPT01725639
The report functionality does not work properly in Internet Explorer 11.
Workaround: To make the Crystal reports viewer work, configure the Information
Steward website in compatible view in Internet Explorer.
ADAPT01713377
When you select Disk Cost in the Select features step of the installation, the installer
calculates cost using all drives, including mapped drives. This may result in additional
installation time if, for example, the network is slow.
Workaround: Unmap your network drives before you install the software.
ADAPT01709665
When planning to use Cleansing Package Builder on Websphere, the initial deployment
does not work.
Workaround:
1.
Navigate to the Websphere installation directory and find the
CPBWebservice.ear\CPBWebservice.war\WEB-INF\conf folder. For exam­
ple, the Websphere directory could be similar to this: C:\Program Files
(x86)\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps
\Win2k8R2Tomcat7Node01Cell\CPBWebservice.ear\CPBWebservice.war
\WEB-INF\conf.
2.
ADAPT01709514
Delete axis2.xml.
In Data Insight, when running a column profiling task with the Median & Distribution
and the Word Distributed option selected, the following warning message is shown.
The auto refresh of the task <task_name> in project
<project_name> has exceeded. Use the Refresh button to check
the status.
However, the task never completes.
Workaround: Have your Unix administrator change the value of ulimit-n to a value of
4096.
ADAPT01706509
10
Associating a custom content type with a column that contains Unicode data is not
supported in Data Insight. Therefore, if you have data in a column that, for example,
contains both English and Chinese, the results for content type profiling are based on
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Release Notes
Known issues
h
Issue ID
Description
the English data only for custom content types. The Chinese is not recognized nor in­
cluded in the results.
ADAPT01702019
In Excel workbooks, if a column contains more than one data type, or multiple text
alignments, one of the data types will be set to null.
Workaround: Refer to the following Microsoft support link for workarounds for this de­
sign limitation: http://support.microsoft.com/kb/194124
ADAPT01691524
When promoting a cleansing package via the Central Management Console (CMC), the
promoted cleansing package might appear in a Ready state in the promoted destina­
tion environment even though the cleansing package is still in the process of being pro­
moted. If you open the cleansing package before it has been fully promoted, the
cleansing package will be corrupt and the EIMAdaptiveProcessingServer will restart.
Workaround: Check the Promotion Management within the CMC to ensure the job has
completed successfully before opening the cleansing package in Cleansing Package
Builder.
ADAPT01665689
When a rule name or rule dimension name contains Unicode characters, saving failed
data to one of the following failed data databases stores the name as question marks
(???) in the IS_FD_RULES_INFO table: SAP HANA, Informix IDS, MySQL, Netezza,
Sybase ASE, Sybase IQ, and Teradata.
ADAPT01660813
Information Steward reports are only available in English, regardless of the set local­
ized language. If you are using Information Steward in a language other than English
and click View Reports in the top right corner, the Reports window shows trans­
lated links and descriptions. However, when you click a link to a report, the Parameters
window and the generated report are not translated.
ADAPT01652309
Starting JBoss Application Server 5.0.1 when Information Steward is deployed with the
SAP BusinessObjects Business Intelligence (BI) platform dswsbobje component
shows an error on startup. This error can be ignored as it has no effect on Information
Steward.
ADAPT01628665
You might encounter an invalid keycode error during installation. This is likely due to
some client tools installed on desktop deployments. For information, see SAP Note
1707707
.
ADAPT01623284
When testing a rule for which invalid input values require conversion to a number, the
results are inconsistent. For example, if "26 JUL 1997" or a blank value is entered as
input, the data passes the rule. However, if "25 JUL 1996" is entered as input, the data
fails the rule.
ADAPT01555974
In Cleansing Package Builder Design mode, or in the Create Custom Cleansing Package
wizard, while importing a list of standard forms or variations using a Microsoft Excel
file or a comma separated value (CSV) file, the following behaviors may occur:
Release Notes
Known issues
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
11
Issue ID
Description
●
In an Excel worksheet containing duplicate column names, all column names are
visible in the list of column names in the dialog box. However only the first instance
of the duplicate column name may be selected.
Workaround: Rename duplicate column names so that each column name in the
worksheet is unique.
●
While an Excel file is selected during an import operation within Cleansing Package
Builder, you cannot use Excel to modify and save the file.
●
In an Excel worksheet, if the columns do not contain an equal number of records,
data from a column other than the selected column may be imported in error.
Workaround: Ensure that each column in the worksheet contains an equal number
of rows so that there are no empty cells. To avoid duplicate data warning mes­
sages, ensure your data is unique.
●
When importing standard forms or variations in Design mode using a CSV file, an
empty field within a record column causes the import process to stop and a mes­
sage indicates that the value already exists in the cleansing package. Standard
forms or variations imported before the empty field are saved.
Workaround: Before beginning the import process, ensure that all fields within the
desired record column are populated. You may duplicate data to fill empty fields.
To avoid duplicate data warning messages, ensure your data is unique.
ADAPT01525554
In Information Steward, the type of connection established when SSL is enabled is not
supported by Metadata Management 3.x. As a result, during a test connection, all at­
tempts to log on to Metadata Management 3.x will fail with a communication error.
This does not prevent the integrator from running.
ADAPT01523082
In Cleansing Package Builder, a custom cleansing package is usually available in De­
sign and Advanced modes. If you manually create or modify a parsing rule in Advanced
mode and that rule is invalid, when you switch to Design mode an error message dis­
plays and Cleansing Package Builder closes the cleansing package.
Workaround: Reopen the cleansing package and edit the parsing rule so it is valid.
Close and then reopen the cleansing package to continue working.
ADAPT01520065
A profiling task fails when the same Data Services job server is associated with both
the Information Steward and Data Services repositories.
Workaround: Create separate Data Services job servers for Information Steward and
Data Services.
ADAPT01517520
Redundancy profiling tasks fail in the following cases:
●
Two SAP extractors, one SAP extractor, and one virtual view based on another
SAP extractor.
●
Two virtual views based on two SAP extractors.
ADAPT01512202
Information Steward installer fails when there are two File Repository Servers (FRS)
installed, but they point to different physical locations. This issue is due to a limitation
on the SAP BusinessObjects Business Intelligence platform.
ADAPT01393699
Schema Name for tables collected by SAP BusinessObjects Enterprise Metadata
Integrator is displayed as “Unknown schema name for <Universe Name>” for Uni­
12
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Release Notes
Known issues
Issue ID
Description
verses using MySQL connection. This issue is resolved in this release for the case
where the same MySQL ODBC DSN is available where the SAP BusinessObjects
Enterprise Metadata Integrator is run.
ADAPT01278734
The display of search results and lineage information is not limited to that information
for which the user has access permission.
ADAPT01275081
When installing this product on a CMS cluster, you must use the physical machine
name of the CMS server.
ADAPT01263270
If a Data Services job uses the Table_Comparison transform, Metadata Management
will not show the impact and lineage on the same table.
ADAPT00619242
Information Steward loses connection to the Information Steward repository when the
following situations occur:
●
Restarting the Information Steward repository database server.
●
Disconnecting from and reconnecting to the Information Steward web server to
the network.
To recover from this error, restart the web server on which the Information Steward
web application is running.
Release Notes
Known issues
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
13
5
Fixed issues
This section contains a list of issues that have been fixed in the SAP Information Steward 4.2 SP2 (14.2.2) release.
The list includes the fixes that are forwarded from the previous patches and additional fixes in this release.
5.1
Issues fixed in support packs and previous patches
The fixes in the following support packs (SPs) and patches are included in this release. These fixes are listed in the
Fixed issues section of the respective release’s Knowledge Base Article (KBA) Release Notes on the SAP Service
Marketplace.
Information Steward release version
4.2 Patch 1.3
1985605
4.2 Patch 1.2
1972322
4.2 SP1
1950281
4.1 Patch 3.1
1985647
4.1 SP3
1959016
4.1 SP2
1894524
4.1 Patch 1.1
5.2
KBA release notes
1843978
Issues fixed in this release
Issues fixed in this release are listed below in descending order by an internal issue identification tracking number.
You can reference the issue ID when searching for the issue on our knowledge base or when speaking to SAP
Customer Support.
Issue ID
Description
ADAPT01725946
The rule history JSON data retrieved from the server does not have project information for
certain rules. Information Steward does not check for the null values and an error causes
the page to hang. This issue has been fixed in this release.
ADAPT01725627
When viewing lineage from the BI launchpad in a different domain, a javascript error is
thrown. This issue has been fixed in this release.
ADAPT01720988
When you run Calculate Score on a rule and save failed data to a failed rule connection,
run Calculate Score again without selecting the failed rule connection, and then click View
14
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Release Notes
Fixed issues
Issue ID
Description
More Failed Data, the error message displayed is not correct. The issue has been fixed in
this release.
ADAPT01720788
When importing Metapedia terms, the ‘Last Modified by’ field does not appear as the
name of the user that loaded the term. Instead, it shows "Last Modified by system up­
grade". This issue has been fixed in this release.
ADAPT01712646
When importing Excel files with a custom format, if the Excel file is not in the standard for­
mat expected by Information Steward, then the automatic approve value is ignored. This
issue has been fixed in this release.
ADAPT01712144
Information Steward does not search BusinessObjects Enterprise 4.0 metadata after inte­
grator runs. This issue has been fixed in this release.
ADAPT01710962
The Failed Data export fails if the filter includes a "datetime" column type. This issue has
been fixed in this release.
ADAPT01709284
The EIMAdaptiveProcessingServer does not have "Everyone, View" security rights. This is­
sue has been fixed in this release.
ADAPT01699428
The recovery process for failed universes collects all universes except for the universe
causing the failure. The failed universe is identified in the log. This issue has been fixed in
this release.
ADAPT01689065
If you connect to a remote CMS during a primary installation of Information Steward, con­
figuring the Information Steward repository will fail. This issue has been fixed since
Information Steward 4.2 SP1.
ADAPT01668672
When you use the promotion management console to migrate existing Information
Steward objects during an upgrade installation, integrator source groups and integrator
run histories are not migrated properly. This issue has been fixed since Information
Steward 4.1 SP2.
ADAPT01657755
If you initially configured an Information Steward repository using one type of database in
a previous version of Information Steward installation, and then switched the repository to
use a different type database via the ISRepositoryUtility tool, when upgrading to
Information Steward 4.2 the initial database information is pre-populated on the reposi­
tory information screen. This issue has been fixed since Information Steward 4.2 SP1.
ADAPT01656567
Viewing Data Services Auto Documentation fails while analyzing the lineage of a Data
Services integrator source column after upgrading from Information Steward version 4.0.
This issue has been fixed in this release.
ADAPT01654235
The Log Level properties are not displayed correctly for Data Services Metadata Browsing
and View Data Services in the Central Management Console (CMC) after upgrading from
Information Steward 4.0 SP2 to Information Steward 4.1 or 4.1 SP1. This issue has been
fixed since Information Steward 4.2 SP1.
ADAPT01628174
When you configure a Metadata collection on a SAP BusinessObjects Business Intelli­
gence (BI) platform 4.0 FP3 system for a CMS that has an earlier SAP BusinessObjects
Business Intelligence (BI) platform 4.0 version installed, you may see the following error
message when you collect reports: "Unable to open report. The maximum connection limit
has been reached." This issue has been fixed since Information Steward 4.2 SP1.
Release Notes
Fixed issues
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
15
Issue ID
Description
ADAPT01623686
At the end of any mode of installation (including uninstallation), the UNIX installer incor­
rectly states: “Click Finish to exit this installation” (or “uninstallation”). It should state:
“Press [Enter] to exit this installation”. This issue has been fixed since Information
Steward 4.2 SP1.
ADAPT01563343
A profiling task fails when a column name contains an apostrophe ('). This issue has been
fixed since Information Steward 4.1 Patch2.1.
ADAPT01522843
On rare occasions, the ISJobServer or EIMAdaptiveProcessingServer are not added to the
CMS server list for that server node, even though the corresponding components were se­
lected and the installation finished with success. This issue has been fixed in this release.
ADAPT01521649
On Linux, if the Listener Port or JMXConnector Port is specified out of range (1000,
10000) during installation, you cannot change any settings for the Data Services View
Data Services and Data Services Metadata Browsing Service in EIMAdaptiveProcessing­
Server from the CMC. This has been fixed since Information Steward 4.1 Patch 1.2.
ADAPT01516162
When re-installing Information Steward on a machine where it was previously installed,
during the post process check-up, some problems are found due to missing services. Pos­
sible symptoms:
●
.ISJobServer is not installed.
●
.EIMAdaptiveProcessingServer is not installed or some important services (Metadata
Search Service, Metadata Relationship Service, and so on) are not part of the EIMA­
daptiveProcessingServer.
●
When adding the required services to either one of the servers (ISJobServer, EIMA­
daptiveProcessingServer) via CMC, it shows the error “The edge between objects
<#id> and <#id2> does not exist.”
●
Problems during runtime which lead to some missing components.
This issue has been fixed in this release.
16
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Release Notes
Fixed issues
6
SAP Information Resources
A global network of SAP technology experts provides customer support, education, and consulting to ensure
maximum information management benefit to your business.
Useful addresses at a glance:
Address
Content
Customer Support, Consulting, and Education serv­
ices
Information about SAP Business User Support pro­
grams, as well as links to technical articles, downloads,
and online discussions.
http://service.sap.com/
Product documentation
http://help.sap.com/bois/
Supported platforms (Product Availability Matrix)
https://service.sap.com/PAM
Product tutorials
http://scn.sap.com/docs/DOC-8751
Forums on SCN (SAP Community Network )
http://scn.sap.com/community/businessobjects-in­
User Guide, Administration Guide, and other documen­
tation for SAP Information Steward.
Information about supported platforms for SAP
Information Steward with a search function to quickly
find information related to your platform.
Tutorials that have been developed to help you find an­
swers to the most common questions about using SAP
Information Steward.
Discussions that include information and comments
from other SAP users and the means to share your
knowledge with the community.
formation-steward
EIM Wiki page on SCN
http://wiki.sdn.sap.com/wiki/display/EIM/EIM
The means with which to contribute content, post com­
ments, and organize information in a hierarchical man­
ner to so that information is easy to find.
+Home
Release Notes
SAP Information Resources
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
17
www.sap.com/contactsap
© 2014 SAP AG 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 AG.
The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only
warranties for SAP Group 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 AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising