Business objects DATA FEDERATOR XI 3.0 User Manual

Data Federator Release Notes

BusinessObjects Data Federator XI 3.0 Service Pack 2

© 2009 SAP® BusinessObjects™. All rights reserved. SAP BusinessObjects and its logos, BusinessObjects, Crystal Reports®, SAP BusinessObjects Rapid Mart™, SAP BusinessObjects Data Insight™, SAP BusinessObjects Desktop Intelligence™, SAP BusinessObjects Rapid Marts®, SAP BusinessObjects Watchlist Security™, SAP BusinessObjects Web Intelligence®, and Xcelsius® are trademarks or registered trademarks of Business Objects, an SAP company and/or affiliated companies in the United States and/or other countries. SAP® is a registered trademark of SAP AG in Germany and/or other countries. All other names mentioned herein may be trademarks of their respective owners.

2009-07-27

Introduction 5Chapter 1

What's new in this release 7Chapter 2

Migrating data from previous versions 11Chapter 3

Restoring data from Data Federator XI 3.0 or XI 3.0 Service Pack 1........12

Restoring data from Data Federator XI Release 2 Accelerated or XI Release

2 Accelerated SP1.....................................................................................17

Known issues and limitations 27Chapter 4

Known issues.............................................................................................28

Known limitations.......................................................................................35

Known issues and workarounds when using Data Federator with other

software.....................................................................................................36

Fixed issues 39Chapter 5

BusinessObjects Data Federator XI 3.0....................................................40

Bugs fixed in Service Pack 1 FixPack 2....................................................40

Bugs fixed in Service Pack 1 FixPack 1....................................................42

More Information 47Appendix A

Index 51

Data Federator Release Notes 3

Contents

4 Data Federator Release Notes

Introduction

This document provides information about BusinessObjects Data Federator XI 3.0 Service Pack 2.

This document lists known issues, fixed issues, as well as new features in this release.

You should read this entire document before installing Data Federator.

6 Data Federator Release Notes

What's new in this release

This Service Pack for BusinessObjects Data Federator adds the following changes.

• easier deployments

• install multiple instances of Data Federator Query Server on a single

machine

• automated Data Federator statistics management

• SAP NetWeaver BI connector improvements

• easier Infoprovider selection

• faster data exchange between Data Federator and SAP NetWeaver

BI using binary XML

• easier configuration with automatic callback registration

• improved Data Federator Designer interface

8 Data Federator Release Notes

What's new in this release

• improved creation of target tables from existing datasources or from

sets of other tables

• improved syntax of case analysis formulas

• environment extensions

• connector to SQL Server 2008 through ODBC or OLEDB

• support for SUSE Linux Enterprise 10

Data Federator Release Notes 9

What's new in this release

10 Data Federator Release Notes

Migrating data from previous versions

Restoring data from Data Federator XI 3.0 or XI 3.0 Service Pack 1

If you want to save and re-use your data from version XI 3.0 or XI 3.0 Service Pack 1, you must back up the data before you install Data Federator XI 3.0 Service Pack 2.

The backup must be made on the same machine and operating system where you want to install Data Federator XI 3.0 Service Pack 2.

1. In the previous release of Data Federator (XI 3.0 or XI 3.0 Service Pack

1), use the Data Federator Backup and Restore Tool to make a backup.

Note:

For details on the Data Federator Backup and Restore Tool, see the documentation for backing up and restoring data in the Data Federator User Guide or Data Federator Installation Guide.

2. Uninstall the previous release of Data Federator.

3. Install Data Federator XI 3.0 Service Pack 2.

4. Use the Data Federator Backup and Restore Tool to restore your

backed-up data.

5. Check that the data you restored did not overwrite changes that this

release makes to the connector resources.

The following tables show the list of connector resources and the changes between this release and XI 3.0 and between this release and XI 3.0 Service Pack 1.

Use Data Federator Administrator to edit your resources and make sure that they are not missing the following changes.

12 Data Federator Release Notes

Migrating data from previous versions

Restoring data from Data Federator XI 3.0 or XI 3.0 Service Pack 1

Table 3-1: List of changes to connector resources introduced in this release

Name of resource

jdbc.access

jdbc.db2.iSeries

Changes introduced between release XI 3.0 and this release

the property:

capabilities=isjdbc\=true;or derByStrings\=false;can cel\=false

became:

capabilities=isjdbc\=true;or derByStrings\=false;can cel\=false;outer Join\=false;leftOuter Join\=true;rightOuter Join\=true;sumAggregateDis tinct\=false;countAggregate Distinct\=false;minAggregate Distinct\=false;maxAggregate Distinct\=false

the property:

capabilities=isjdbc\=true;or derBy\=false

became:

capabilities=isjdbc\=true;or derBy\=false;outerJoin\=false

Data Federator Release Notes 13

Migrating data from previous versions

Restoring data from Data Federator XI 3.0 or XI 3.0 Service Pack 1

Name of resource

jdbc.mysql

Changes introduced between release XI 3.0 and this release

the property:

driverProperties=useUni code\=true;characterEncod ing\=utf8

became:

driverProperties=useUni code\=true;characterEncod ing\=UTF-8

the property:

sqlStringType=oracle9

became:

sqlStringType=oracle8

the property:

jdbc.oracle.oracle8

14 Data Federator Release Notes

capabilities=isJDBC\=true;out erJoin\=false;leftOuter Join\=true;rightOuter Join\=true;order ByStrings\=false;emptyS tringEvaluation\=false

became:

capabilities=isJDBC\=true;out erJoin\=false;leftOuter Join\=false;rightOuter Join\=false;order ByStrings\=false;emptyS tringEvaluation\=false

Migrating data from previous versions

Restoring data from Data Federator XI 3.0 or XI 3.0 Service Pack 1

Name of resource

jco.sap.netweaverBI

odbc.teradata.teradataV2R5

odbc.teradata.teradataV2R6

Changes introduced between release XI 3.0 and this release

the property:

callbackServerPro gramID=DF_JCO_PLEASE_CHANGE

was deleted

the property:

sqlStringType=sql92

became:

sqlStringType=teradata

the property:

sqlStringType=sql92

became:

openclient.sybase.sybaseASE12

sqlStringType=teradata

the property:

capabilities=isJDBC\=true;mi nAggregateDistinct\=true;max AggregateDistinct\=true

became:

capabilities=isJDBC\=true;mi nAggregate\=false;maxAggre gate\=false

Data Federator Release Notes 15

Migrating data from previous versions

Restoring data from Data Federator XI 3.0 or XI 3.0 Service Pack 1

Name of resource

ws.generic

Name of resource

jdbc.access

Changes introduced between release XI 3.0 and this release

the property:

addNamespaceInParameter=true

was deleted

Changes introduced between release XI 3.0 Service Pack 1 and this release

the property:

capabilities=isjdbc\=true;or derByStrings\=false;can cel\=false

became:

jco.sap.netweaverBI

16 Data Federator Release Notes

the property:

callbackServerPro gramID=DF_JCO_PLEASE_CHANGE

was deleted

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

If you want to save and re-use your data from version XI Release 2 Accelerated or XI Release 2 Accelerated SP1, you must back up the data before you install Data Federator XI 3.0 Service Pack 2.

The backup must be made on the same machine and operating system where you want to install Data Federator XI 3.0 Service Pack 2.

1. In the previous release of Data Federator (XI Release 2 Accelerated or

XI Release 2 Accelerated SP1), use the Data Federator Backup and Restore Tool to make a backup.

Note:

For details on the Data Federator Backup and Restore Tool, see the documentation for backing up and restoring data in the Data Federator User Guide or Data Federator Installation Guide.

2. Uninstall the previous release of Data Federator.

3. Install Data Federator XI 3.0 Service Pack 2.

4. Use the Data Federator Backup and Restore Tool to restore your

backed-up data.

5. Check that the data you restored did not overwrite changes that this

release makes to the connector resources.

The following is a list of connector resources and the changes that this release introduced to them.

Use Data Federator Administrator to edit your resources and make sure that they are not missing the following changes.

Data Federator Release Notes 17

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Table 3-2: List of changes to connector resources in this release

Changes introduced between re-

Name of resource

lease XI Release 2 Accelerated and this release

the property:

CAPABILITIES=isjdbc\=true;or derByStrings\=false

became:

capabilities=isjdbc\=true;or derByStrings\=false;can cel\=false;outer Join\=false;leftOuter Join\=true;rightOuter Join\=true;sumAggregateDis tinct\=false;countAggregate

jdbc.access

Distinct\=false;minAggregate Distinct\=false;maxAggregate Distinct\=false

18 Data Federator Release Notes

the property:

supportsSchema=NO

was added

the property:

supportsCatalog=NO

was added

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Changes introduced between re-

Name of resource

lease XI Release 2 Accelerated and this release

the property:

CAPABILITIES=isjdbc\=true;or derByStrings\=false

became:

jdbc.db2

jdbc.designer

jdbc.hsqldb

capabilities=isjdbc\=true;or derBy\=false

the property:

supportsCatalog=no

was added

the property:

supportsSchema=NO

was added

the property:

supportsCatalog=NO

was added

the property:

supportsSchema=NO

was added

the property:

supportsCatalog=NO

was added

Data Federator Release Notes 19

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Changes introduced between re-

Name of resource

lease XI Release 2 Accelerated and this release

the property:

DRIVERPROPERTIES=useUni code\=true;characterEncod ing\=utf8

became:

driverProperties=useUni code\=true;characterEncod ing\=UTF-8

the property:

jdbc.mysql

CAPABILITIES=isJDBC\=true;out erJoin\=false;leftOuter Join\=true;rightOuter Join\=true;order ByStrings\=false;aggregateDis tinct\=false

became:

capabilities=isJDBC\=true;out erJoin\=false;leftOuter Join\=true;rightOuter Join\=true;order ByStrings\=false;aggregateDis tinct\=false;cancel\=false

20 Data Federator Release Notes

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Changes introduced between re-

Name of resource

lease XI Release 2 Accelerated and this release

the property:

CASTCOLUMN TYPE=FLOAT\=FLOAT;BLOB\=BLOB

was deleted

the property:

URLTEMPLATE=jdbc:ora cle:thin:@<host name>[:<port>]:<databasename>

became:

urlTemplate=jdbc:ora cle:thin:@<host name>:<port>:<databasename>

jdbc.oracle.oracle10

the property:

supportsCatalog=NO

was added

the property:

connectionFailureSQL States=61000

was added

the property:

maxLoadPerConnection=1

was added

Data Federator Release Notes 21

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Changes introduced between re-

Name of resource

jdbc.oracle.oracle8

lease XI Release 2 Accelerated and this release

22 Data Federator Release Notes

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Changes introduced between re-

Name of resource

lease XI Release 2 Accelerated and this release

the property:

SQLSTRINGTYPE=oracle9

became:

sqlStringType=oracle8

the property:

CASTCOLUMN TYPE=FLOAT\=FLOAT;BLOB\=BLOB

was deleted

the property:

CAPABILITIES=isJDBC\=true;out erJoin\=false;leftOuter Join\=true;rightOuter Join\=true;order ByStrings\=false;emptyS tringEvaluation\=false

became:

capabilities=isJDBC\=true;out erJoin\=false;leftOuter Join\=false;rightOuter Join\=false;order ByStrings\=false;emptyS tringEvaluation\=false

the property:

URLTEMPLATE=jdbc:ora cle:thin:@<host name>[:<port>]:<databasename>

became:

urlTemplate=jdbc:ora

Data Federator Release Notes 23

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Changes introduced between re-

Name of resource

lease XI Release 2 Accelerated and this release

cle:thin:@<host name>:<port>:<databasename>

the property:

supportsCatalog=NO

was added

the property:

connectionFailureSQL States=61000

was added

the property:

24 Data Federator Release Notes

maxLoadPerConnection=1

was added

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Changes introduced between re-

Name of resource

lease XI Release 2 Accelerated and this release

the property:

CASTCOLUMN TYPE=FLOAT\=FLOAT;BLOB\=BLOB

was deleted

the property:

URLTEMPLATE=jdbc:ora cle:thin:@<host name>[:<port>]:<databasename>

became:

urlTemplate=jdbc:ora cle:thin:@<host name>:<port>:<databasename>

jdbc.oracle.oracle9

the property:

supportsCatalog=NO

was added

the property:

connectionFailureSQL States=61000

was added

the property:

maxLoadPerConnection=1

was added

Data Federator Release Notes 25

Migrating data from previous versions

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Changes introduced between re-

Name of resource

lease XI Release 2 Accelerated and this release

the property:

jdbc.sqlserver

jco.sap.netweaverBI

CASTCOLUMNTYPE=numeric\=DECI MAL

was deleted

the property:

callbackServerPro gramID=DF_JCO_PLEASE_CHANGE

was deleted

26 Data Federator Release Notes

Known issues and limitations

Known issues

This section lists known issues in BusinessObjects Data Federator XI 3.0 Service Pack 2.

Table 4-1: Known issues

Bug number

267

1193

Issue

In Data Federator Designer, if the decimal separator is "." (period), and you enter 99,01, that is, using a "," (comma) in a mapping formula, the error message does not indicate the specific problem.

Data Federator does not push expressions to the database management system when the expression is an argument of a function that is not pushed.

This could lead to different computed values when the same expression is both pushed and not pushed in the same query.

Query examples:

select (D0-3.15), abs(D0-3.15) from /wrappers/jd bc/mysql_push_test/TEST_TYPES

select ((D0-3.15) = abs(D0-3.15)) from /wrappers/jd bc/mysql_push_test/TEST_TYPES

In both examples, the function abs() is calculated by Data Federator. Therefore, the first expression (D0-3.15) is calculated by the database management system, while the second expression abs(D0-3.15) is calculated by Data Federator. If the database management system uses a different algorithm than Data Federator, then two expressions could have a different result.

28 Data Federator Release Notes

Known issues and limitations

Known issues

Bug number

1526

1760

Issue

Problem:

There is no error shown when a date is semantically incorrect (for example, 2003-13-02).

If the date is correct syntactically but not semantically (YYYYMM-DD), it is parsed and new date is created (for example, 2004-01-02).

Workaround:

Do not enter semantically-incorrect dates.

Problem:

When using the TIME format code 'hh', which represents a 12hour clock, in TIMESTAMPS with hour values from 13 to 23, the hour is not converted to 12-hour time.

Workaround:

Use a mapping formula to convert 24-hour time to 12-hour time.

1784

When using a comma-separated value (CSV) file as a datasource, if the file has a column that contains the character "\n", but lines in your file are separated by "\n\r", Data Federator will split the line in the wrong place.

Data Federator Release Notes 29

Known issues and limitations

Known issues

Bug number

1896

Issue

Problem:

When accessing an MS Access database, where the MS Access database and Data Federator Query Server are on different machines, while trying to connect from Data Federator to the Access database, the following connection error appears.

"Connection to 'jdbc:odbc:MSAccess_DSN' failed: '(unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides."

Workaround:

Stop the DataFederator.QueryServer service (in Control Panel > Administrative Tools > Services. Then, start the DataFederator.QueryServer service using the following command in a DOS window:

cd C:\Program Files\DataFedera-

tor\LeSelect\

bin\startup.bat

The connection to the MS Access database proceeds.

Problem:

When using the Data Federator thindriver, if a currently created or submitted Statement or Query object is canceled, the java

2131

30 Data Federator Release Notes

Statement object (either prepared or not) cannot be used any longer for further executions.

Workaround:

Create a new Statement object.

Known issues and limitations

Known issues

Bug number

2192

2360

Issue

Problem:

When including an archive file that contains filters on constraint violations, where those filters reference a datasource column in the filter formula, the datasource column is not updated to the ID that it gets when it is imported.

Workaround:

Check the filters in the constraint violations and update any datasource columns that you used in the formulas to their new IDs.

Problem:

The resource parameters username, password and schema should not be placed in a resource file. They are currently accepted when creating or modifying a resource, but ignored when registering a datasource with Data Federator Designer.

Workaround:

Modify these resource parameters from the Data Federator Administrator interface.

Data Federator Release Notes 31

Known issues and limitations

Known issues

Bug number

2544

3157

Issue

Problem:

Some system parameters require server restart after you change them.

When you change the value of one of these parameters using the Data Federator Administrator, and you click OK, you cannot revert to its original value.

Workaround:

If you want to revert the value of this type of system parameter, do the following.

Restart the server.

Type the original value.

Restart the server again.

Problem:

When using the Data Federator installer to install the OpenAccess ODBC to JDBC Bridge on Windows, the installer issues a warning. At the end of the installation, a message indicates that warnings were found during installation. When you open the file data-federator-install-dir/install.log , you see a warning concerning an entry in the Windows Registry.

This message is normal and it should not be reported as a warning.

Workaround:

Ignore the warning, and treat it as information.

32 Data Federator Release Notes

Known issues and limitations

Known issues

Bug number

3159

3620

Issue

Problem:

When installing Data Federator in silent mode, and the process is aborted, because there is one already installed, for example, it is only possible to determine that the installation failed if the install log is displayed on your desktop (or your 'home' if you are using Unix).

Workaround:

Check your desktop (home directory in Unix) for the presence of the install log.

Problem:

Data Federator does not support the Sybase data type TIMESTAMP.

Workaround:

When defining resources to connect to Sybase databases, use the data types DATETIME or SMALLDATETIME instead.

4345

Problem:

The column metadata of target tables shows default values of precision and scale for string and decimal data until the execution of first query on the corresponding tables. Afterwards, the column metadata displayed is correct.

Workaround:

As a workaround, to have the right metadata displayed for a target table at the very beginning, execute a query on the corresponding table ( select * from table).

Data Federator Release Notes 33

Known issues and limitations

Known issues

Bug number

6329

7850

8516

Issue

NullPointerException when date of file accessed by FTP is February 29 (leap year bug) for text, and xml datasources.

See Commons Net issue:

http://issues.apache.org/jira/browse/NET-193

This bug only appears for files created on a leap year day.

Problem:

On some operating systems, Data Federator does not support access to some combinations of data sources at the same time. This problem is caused, for example, on Solaris when using Informix and Red Brick in the same Data Federator project.

Problem:

If the expected result of the count aggregation exceeds the maximal size of an integer (2^32), then Data Federator may return an incorrect result, because the result type of count is integer and not decimal.

Problem:

8522

8538

34 Data Federator Release Notes

There is an issue on Teradata through ODBC when the column datatype is 18 digits and the data value you are trying to retrieve also contains 18 digits.

Problem:

On Informix IDS 9.4 on Linux, if a table has a space character (' ') in one of its rows, the space is trimmed.

Known issues and limitations

Known limitations

Bug number

10761

10769

Issue

Problem:

If you enter incorrect gateway parameters, you cannot query SAP NetWeaver BI tables, and no error message is shown in the Data Federator Administrator interface. The application hangs.

Workaround:

By default, when you add a SAP NetWeaver BI datasource, you do not have to enter gateway parameters. Make sure that if you do enter gateway parameters, that they are correct before you deploy your project.

Problem:

On Teradata v2R5, getting metadata of a table that contains a double quotes throws an exception.

Problem:

In Data Federator Designer, there are layout problems in mapping formulas when columns names are long.

10777

Workaround:

Do not exceed 30 characters for the column names of your target tables.

Known limitations

This section lists known limitations in BusinessObjects Data Federator XI

3.0 Service Pack 2.

Data Federator Release Notes 35

Known issues and limitations

Known issues and workarounds when using Data Federator with other software

Table 4-2: Known limitations

Bug number

1507

5274

5275

Limitation

The functions CONVERT and CAST are available in the Data Federator Administrator but not in Data Federator Designer. In Data Federator Designer, the "convert" functions such as toTimestamp() or toInteger() can be used instead.

Problem:

It is not possible to retrieve primary key or foreign key values from MS Access databases using an ODBC driver.

Workaround:

Use the JDBC driver to connect to MS Access.

When connecting to Netezza sources, columns of type

boolean will appear as type char. This is a bug in Netezza

ODBC and JDBC drivers.

Known issues and workarounds when using Data Federator with other software

This section lists known issues in third-party components when used with BusinessObjects Data Federator XI 3.0 Service Pack 2.

36 Data Federator Release Notes

Known issues and limitations

Known issues and workarounds when using Data Federator with other software

Table 4-3: Known issues and workarounds when using Data Federator with other software

Bug number

2511

5275

5455

5508

Issue

Problem:

The driver used to connect to DB2, jt400.jar, has some limitations, and if it used with Data Federator, you may get a No

columns error.

Netezza returns char as the data type for boolean columns.

Problem:

Some queries to SAS sources cause a general critical error.

There is no specific workaround. Please report an issue to SAS support, and provide the query that was pushed to the SAS source.

Problem:

Table names with a dot raise an SQL generation problem from BusinessObjects Web Intelligence and Crystal Reports.

Workaround:

If you need to use BusinessObjects Web Intelligence or Crystal Reports, do not create target tables with dots in their names in Data Federator.

Data Federator Release Notes 37

Known issues and limitations

Known issues and workarounds when using Data Federator with other software

Bug number

8785

8522

Issue

Problem:

On Netezza 3.0, due to an ODBC driver bug, a new connection is created each time Data Federator executes a query. If too many queries are executed, an exception is raised when we reach the maximum allowed connections.

Workaround:

Add <Parameter Name="Connection Status Avail

able">False</Parameter> in the Netezza section of the file data-federator-install-dir/LeSelect/CS/DataAc cess/ConnectionServer/odbc/odbc.sbo , as below:

<DataBase Active="Yes" Name="Netezza Server"> ... <Parameter Name="Connection Status Avail able">False</Parameter> </DataBase>

Problem:

An exception is raised from Teradata when retrieving a value with 18 digits when the data type of the column is also 18 digits.

For more information, see http://www.teradataforum.com/tera

data/20010904_194009.htm.

Problem:

9317

38 Data Federator Release Notes

On Windows, the Informix ODBC driver returns double as the type of data for decimal columns, and it returns the wrong precision value for decimal columns.

Fixed issues

BusinessObjects Data Federator XI 3.0

This section lists fixed issues in BusinessObjects Data Federator XI 3.0 Service Pack 2.

Accumulation of bug fixes in Service Packs

Service Packs include all of the fixes delivered in preceding Service Packs and FixPacks.

Bugs fixed in Data Federator connectors

• Description

8819: XML connector: problem with jis and utf16 encoding xml file

New behavior

The XML connector now supports jis and utf16 encodings.

Bugs fixed in Service Pack 1 FixPack 2

Bugs fixed in Data Federator Administrator

• Description

10088: Not all information was available about memory consumption of queries and subqueries when using Data Federator Administrator, and the estimated size of rows did not always appear.

New behavior

The Query History tab in Data Federator Administrator now shows the number of concurrent queries, the number of buffers used and the number of queries that used the disk. Also, the estimated size of rows is displayed correctly.

Bugs fixed in Data Federator connectors

• Description

40 Data Federator Release Notes

Fixed issues

Bugs fixed in Service Pack 1 FixPack 2

9429: The previous version of the connector for SAP NetWeaver BI had a problem detecting LIKE and NOT LIKE predicates that Data Federator could push to SAP NetWeaver BI.

New behavior

The predicates that SAP NetWeaver BI supports and those that it does not support are now correctly detected.

• Description

10036: Sybase throws the error Implicit conversion from datatype

'VARCHAR' to 'NUMERIC' is not allowed. Use the CONVERT function to run this query. This occurs when executing queries

through Data Federator with filters on decimal values.

Reason

Data Federator can execute parameterized queries on sources to optimize query execution. If a parameter of the query is of type decimal, the argument is passed as a varchar at the data access layer. As Sybase does not support implicit conversion, this throws an exception.

New behavior

You can configure Data Federator to avoid executing parameterized queries on the database. To do this, set the resource property useParam eterInlining to yes or true in the resource associated to the data source. The resource name starts with openclient.*.

When this option is activated, Data Federator will pass the parameter value inline in the query instead of using a parameterized query.

• Description

10077: not in predicates were sometimes pushed to the SAP NetWeaver BI connector, even though the connector cannot translate them to SAP-range predicates.

New behavior

not in predicates are no longer pushed to the SAP NetWeaver BI

connector.

Bugs fixed in Data Federator tools

• Description

Data Federator Release Notes 41

Fixed issues

Bugs fixed in Service Pack 1 FixPack 1

9465: The Backup and Restore tool would fail if the Windows service for the application's repository took long to stop.

New behavior

The Backup and Restore tool now allows time for the repository service to stop.

Bugs fixed in Service Pack 1 FixPack 1

Bugs fixed in Data Federator Designer

• Description

8763: The application froze when you selected operation output schemas on Internet Explorer 7.

New behavior

The application no longer freezes when you select operation output schemas for Web Services datasources.

• Description

8784: When you set an invalid post-filter, the status of the mapping was not updated.

New behavior

The status of the mapping is now updated whenever you set an invalid post-filter.

• Description

8787: The domain constraint check threw an error if the domain columns had spaces in their names.

New behavior

The domain constraint check for domain column names with spaces does not throw an error anymore.

• Description

8788: When you deleted and added a subsample for primary key constraints, the application threw a NullPointerException.

42 Data Federator Release Notes

Fixed issues

Bugs fixed in Service Pack 1 FixPack 1

New behavior

The application no longer throws an exception when you delete and add a subsample for primary key constraint.

• Description

8789: The application did not correctly handle table aliases with only numerals in their names, when these aliases were used in mapping rules.

New behavior

Table aliases with only numerals in their names are now handled correctly in mapping rules.

• Description

8796: For SAP NetWeaver BI datasources, Designer did not show REF ERENCE_DATE columns as input columns.

New behavior

The REFERENCE_DATE columns are shown as an input columns.

• Description

8838: The application allowed you to define input columns on SAP NetWeaver BI datasources, but they were not taken into account.

New behavior

You cannot define input columns for SAP NetWeaver BI. The checkboxes are now read-only to emphasize that.

• Description

9096: The application did not support the HTTPS protocol for retrieving data from web services.

New behavior

The HTTPS protocol is now supported for retrieving data from web services.

• Description

9162: It was not possible to make a datasource final if a column name had a slash ( /) in its name.

Data Federator Release Notes 43

Fixed issues

Bugs fixed in Service Pack 1 FixPack 1

New behavior

If a column in a datasource table contains the slash ( /) character, the datasource can be made final.

• Description

9244: It was possible to add a mapping rule with the same name as an existing one.

New behavior

The application no longer allows you to add mapping rules with the same names as existing ones.

• Description

9323: The application threw a NullPointerException when you tried to check constraints for a target table that had no primary key.

New behavior

When target table does not have a primary key, the global Check

constraint button works.

Bugs fixed in Data Federator connectors

• Description

9089: The web service connector was compliant only with the standards HTTP and SOAP, but not with the Web Service Interoperability basic profile.

New behavior

The web service connector is now compliant with the Web Service Interoperability Basic Profile according to a compatibility level specific to Data Federator. The only profile requirement implemented for the moment is 4.7.25. - SOAP Action.

• Description

9119: The web service connector could not retrieve data from a web service using the HTTPS protocol.

New behavior

44 Data Federator Release Notes

Fixed issues

Bugs fixed in Service Pack 1 FixPack 1

The web service connector can now retrieve data from a web service by using the HTTPS protocol.

• Description

9121: The web HTTPS protocol could not be used for retrieving a WSDL file.

New behavior

The HTTPS protocol can now be used for retrieving a WSDL file.

• Description

9318: Query Server translated SQL queries given to Informix XPS connectors to the dialect of Informix Dynamic Server.

New behavior

The queries to the Informix XPS connector are correctly translated.

• Description

9333: The URL used for calling a web service (for executing the POST operation) was generated with the port 80 if the port was not specified in the WSDL.

New behavior

If the port is not specified in the WSDL, no port number is added to the URL of the service.

Data Federator Release Notes 45

Fixed issues

Bugs fixed in Service Pack 1 FixPack 1

46 Data Federator Release Notes

More Information

LocationInformation Resource

SAP BusinessObjects product information

SAP Help Portal

SAP Service Marketplace

http://www.sap.com

Select http://help.sap.com > SAP BusinessObjects.

You can access the most up-to-date documentation covering all SAP BusinessObjects products and their deployment at the SAP Help Portal. You can download PDF versions or installable HTML libraries.

Certain guides are stored on the SAP Service Marketplace and are not available from the SAP Help Portal. These guides are listed on the Help Portal accompanied by a link to the SAP Service Marketplace. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative.

http://service.sap.com/bosap-support > Documentation

•

Installation guides: https://service.sap.com/bosap-inst

guides

•

Release notes: http://service.sap.com/releasenotes

The SAP Service Marketplace stores certain installation guides, upgrade and migration guides, deployment guides, release notes and Supported Platforms documents. Customers with a maintenance agreement have an authorized user ID to access this site. Contact your customer support representative to obtain an ID. If you are redirected to the SAP Service Marketplace from the SAP Help Portal, use the menu in the navigation pane on the left to locate the category containing the documentation you want to access.

Developer resources

48 Data Federator Release Notes

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary

More Information

LocationInformation Resource

SAP BusinessObjects articles on the SAP Community Network

Notes

Forums on the SAP Community Network

Training

Online customer support

https://www.sdn.sap.com/irj/boc/businessobjects-articles

These articles were formerly known as technical papers.

https://service.sap.com/notes

These notes were formerly known as Knowledge Base articles.

https://www.sdn.sap.com/irj/scn/forums

http://www.sap.com/services/education

From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style.

http://service.sap.com/bosap-support

The SAP Support Portal contains information about Customer Support programs and services. It also has links to a wide range of technical information and downloads. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative.

Consulting

http://www.sap.com/services/bysubject/businessobjectscon sulting

Consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in topics such as relational and multidimensional databases, connectivity, database design tools, and cus tomized embedding technology.

Data Federator Release Notes 49

More Information

50 Data Federator Release Notes

Index

previous installations

restoring data 12, 17

restoring data

previous installations 12, 17 XI 3.0 12

restoring data (continued)

XI Release 2 Accelerated 17 XI Release 2 Accelerated SP1 17

XI 3.0

restoring data 12

XI Release 2 Accelerated

restoring data 17

Data Federator Release Notes 51

Index

52 Data Federator Release Notes

Business objects DATA FEDERATOR XI 3.0 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Introduction

What's new in this release

Migrating data from previous versions

Restoring data from Data Federator XI 3.0 or XI 3.0 Service Pack 1

Restoring data from Data Federator XI Release 2 Accelerated or XI Release 2 Accelerated SP1

Known issues and limitations

Known issues

Known limitations

Known issues and workarounds when using Data Federator with other software

Fixed issues

BusinessObjects Data Federator XI 3.0

Bugs fixed in Service Pack 1 FixPack 2

Bugs fixed in Service Pack 1 FixPack 1

More Information

Index