User manual BUSINESS OBJECTS DATA INSIGHT XI 11.5.1.1 RELEASE NOTES 07-2007

[. . . ] in April 2006, email messages from us have come from a businessobjects. com email address. Make sure that your email system does not unintentionally filter these messages to a spam, trash, or quarantine area where you might miss them. We want all the important news about your product to reach you. Dqpv 'RFXPHQWDWLRQ *HW PRUH LQIRUPDWLRQ After installing Data Insight, you can find more information about it from the various pieces of documentation that are included with the software. Most of the Data Insight documentation is available in electronic format, both in a printable PDF file and an online help format. [. . . ] The BusinessObjects Data Insight XI Release 2 Installation Guide for UNIX provides detailed instructions regarding the following steps: 7vrPiwrp9hhDvtuYDSryrhrIr 1. If you are moving the engine from Windows to UNIX, verify that all scheduled tasks have completed on the Windows engine before transferring to the UNIX engine. This step does not update the Metadata Repository. Update any existing GUI installations to point to the UNIX engine Metadata Repository, or install the GUI. The GUI installation process will update the Metadata Repository. Install the report exporting engine on a Microsoft Windows workstation. If you are moving the engine from Windows to UNIX, after the Windows GUI and UNIX engine have been installed and started, use the GUI to open all of the projects currently included in that Metadata Repository to update the Metadata Repository connection string with information required by the UNIX engine. For Oracle and DB2 Metadata Repositories, if you are upgrading from a version older than 11. 5. 0. 1, you should be aware of changes that have been made to the Metadata Repository setup. For details, see the pre-installation checklist in the BusinessObjects Data Insight XI Release 2 Installation Guide for UNIX. 'LVSOD\ WKH VRIWZDUH YHUVLRQ QXPEHU The version number is displayed in the software as 11. 5. 1. 1. After you install the Data Insight software, to display the version number in the GUI, choose: Help > About Data Insight, or Help > About Metadata Repository To find the version number of the software in the Data Insight engine, access the iqieng. log file; the first line of this file contains the version number. By default, this file resides at c:\Firstlogic\IQInsight\eng for Windows, and install_location/Firstlogic/IQInsight/eng for UNIX. This file is created the first time you start the engine. Dhyyurshr :KDWV QHZ LQ WKLV YHUVLRQ %XLOG EXVLQHVV UXOHV You can specify standards and parsing rules in Data Insight that can be reused in Data Quality XI version 11. 7 or newer. For example, choose multiple firm names and specify a single standard in Data Insight by building a bulk load table and an XML file, and then load the table into the Data Cleanse dictionaries in Data Quality XI. Creating bulk load with Data Insight allows you to combine a large amount of data from various sources prior to loading it into the Data Cleanse dictionary. Use the results of a frequency (FRQ) or word frequency (WFRQ) to build new, or enhance existing dictionaries to export to Data Cleanse. When you analyze the results of the FRQ or WFRQ, you may find some standards that you want to implement in your data. For example, you may have many results using `large' and some that have `LG. ' Use the bulk load option to standardize and classify these options to become one standard output name of your choice. See the BusinessObjects Data Insight XI Release 2 User's Guide for details. , QVWDOO WKH $ULDO 8QLFRGH IRQW Because you can view Unicode data in the Bulk Load window, you must install the Arial Unicode font from the Windows installation CD. If the font is not installed, the data may not correctly appear in the preview pane. Contact your IT department for additional information. Administrative users can define business rule options so that users can classify the rules and then profile the data. Setting rule classifications is particularly helpful when calculating metrics or creating reports because you can use the resulting information stored in the repository to collect and summarize the profiling results. [. . . ] F101 F212 F213 F214 F216 F302 F412 F413 F420 7vrPiwrp9hhDvtuYDSryrhrIr Dspqr 9rpvv 3040 3050 3060 3070 3080 3090 3100 3110 4000 4010 5000 5010 5020 6000 Invalid primary range. Missing primary type and directional prefix or postfix. Invalid or missing directional prefix or postfix. An invalid locality is preventing a possible address match. [. . . ]