User manual BUSINESS OBJECTS DATA FEDERATOR XI RELEASE 2 ACCELERATED SP1

[. . . ] The image below shows a typical set-up of an XML file configuration: Data Federator Release Notes 13 2 What's new in this release BusinessObjects Data Federator XI Release 2 Accelerated SP1 You can display the XML tables you wish to add as datasource tables in a 'list' view, as shown in the example below: 14 Data Federator Release Notes What's new in this release BusinessObjects Data Federator XI Release 2 Accelerated SP1 2 You can also display them in an 'explorer' view, as shown below: Click Create tablesto create and display your XML datasource tables, as shown in the example below: Data Federator Release Notes 15 2 What's new in this release BusinessObjects Data Federator XI Release 2 Accelerated SP1 Improved user authentication When accessing relational datasources, you are no longer limited to using one database user account for all Data Federator users. You can: · · Use the Data Federator username and password as the credential when connecting to the database (credential pass-through). Define a mapping between a Data Federator user and a database credential. The image below shows the authentication modes available when defining your datasource connection parameters: 16 Data Federator Release Notes What's new in this release BusinessObjects Data Federator XI Release 2 Accelerated SP1 2 Automatic statistics management Using a new interface in Data Federator Administrator, you can now set Data Federator to record requests for statistics that are made during query optimization. The recording of statistics can be managed through Data Federator Administrator using a new Statistics tab, as shown in the example below: This tab also allows you to see statistics and override the values with your own. [. . . ] For details on the Data Federator Backup and Restore Tool, see "Backing up and restoring data" in the Data Federator User Guide or Data Federator Installation Guide. Restore the data from Data Federator Designer: In Data Federator Designer, click the Projects tab, then in the tree list, click Projects, then click Import projects. In Data Federator XI Release 2 Accelerated SP1, if you use Oracle datasources, set the following properties in your Oracle resource definitions. Set the property. . . 1 61000 For details on setting properties in resource definition, see the documentation on managing resources and properties of connectors in the Data Federator User Guide. Data Federator Release Notes 27 3 Migrating data from previous versions Restoring data from Data Federator XI Release 2 28 Data Federator Release Notes Known issues and limitations 4 4 Known issues and limitations Important changes This section lists known issues and limitations in BusinessObjects Data Federator, as well as issues fixed in this release. Important changes This section lists important changes made to BusinessObjects Data Federator since the last release. BusinessObjects Data Federator XI Release 2 Accelerated This section lists important changes made to BusinessObjects Data Federator XI Release 2 Accelerated. 3259 If connecting to a public SMB directory on UNIX, you must log in with the username 'guest'. Known issues This section lists known issues in BusinessObjects Data Federator. BusinessObjects Data Federator XI Release 2 Accelerated SP1 This section lists known issues in BusinessObjects Data Federator XI Release 2 Accelerated SP1. 30 Data Federator Release Notes Known issues and limitations Known issues 4 267 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. 519 Problem: If you update a domain table to correct an error in which the constant returned by a mapping formula is not in the domain attached to the target column, the mapping rule's errors are not immediately removed, and statuses are not changed. Workaround: Enter the mapping rule and re-save it. 1193 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 Data Federator Release Notes 31 4 Known issues and limitations Known issues algorithm than Data Federator, then two expressions could have a different result. 1526 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 (YYYY-MM-DD), it is parsed and new date is created (for example, 2004-01-02). Workaround: Do not enter semantically-incorrect dates. 1695 Target table columns cannot contain other characters than alphanumeric characters and "_". Therefore, if the datasource contains special characters, you cannot create a target table by copying its schema. 1760 Problem: When using the TIME format code 'hh', which represents a 12-hour 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. 32 Data Federator Release Notes Known issues and limitations Known issues 4 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. 1798 The "\tab" sequence (backslash, literally followed by the string "tab") in the separator of a text file is interpreted by Data Federator as the tab character. Therefore, files containing this exact character sequence as a separator are not supported. 1848 Problem: When you delete a deployment in Data Federator Designer, the tables in Data Federator Query Server are not deleted. If, for example, you delete the deployment "/OP", only the archive file is deleted in Data Federator Designer but tables on the Data Federator Query Server are not undeployed. Workaround: If you want to delete tables from Data Federator Query Server after deleting a deployment in Data Federator Designer, delete the tables by using Data Federator Administrator. Alternatively, you can deploy an empty project with the same name as the one you want to delete. 1856 Problem: You cannot add domain and lookup rows from an imported text file if Data Federator Query Server and Data Federator Designer are on different machines. Workarounds: Data Federator Release Notes 33 4 Known issues and limitations Known issues · · Populate the lookup or domain table by hand. Copy the uploaded file to the Data Federator Query Server machine by hand to a specific location (this does not work if Data Federator Query Server and Data Federator Designer are on different operating systems). 1896 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\DataFederator\LeSelect\ bin\startup. bat The connection to the MS Access database proceeds. 1944 Problem: After uninstalling DF on UNIX platforms (AIX, Solaris), some directories remain undeleted in the Data Federator installation directory. [. . . ] Current behavior: The property driverProperties is now taken into account for all JDBC datasources. 4577 Previous behavior: On Solaris, it was not possible to add a datasource for a DB2 zSeries database because the driver location was set incorrectly. It is possible to add a datasource for a DB2 zSeries database. 4585 Previous behavior: In some cases, Data Federator did not recognize primary keys in datasources. This happened when there were wildcard characters (_ or %) in the names of your catalogs, schemas or tables. Current behavior: Data Federator Release Notes 39 4 Known issues and limitations Fixed issues Data Federator correctly recognizes primary keys in datasources, even when wildcard characters are used. 4598 Previous behavior: When adding a datasource and viewing the list of tables that were available, it was not possible to see certain tables, for example materialized views on DB2. [. . . ]