User manual BUSINESS OBJECTS DATA FEDERATOR XI 3.0

[. . . ] Data Federator User Guide BusinessObjects Data Federator XI 3. 0 Copyright © 2008 Business Objects, an SAP company. patents, which may cover products that are offered and licensed by Business Objects: 5, 295, 243; 5, 339, 390; 5, 555, 403; 5, 590, 250; 5, 619, 632; 5, 632, 009; 5, 857, 205; 5, 880, 742; 5, 883, 635; 6, 085, 202; 6, 108, 698; 6, 247, 008; 6, 289, 352; 6, 300, 957; 6, 377, 259; 6, 490, 593; 6, 578, 027; 6, 581, 068; 6, 628, 312; 6, 654, 761; 6, 768, 986; 6, 772, 409; 6, 831, 668; 6, 882, 998; 6, 892, 189; 6, 901, 555; 7, 089, 238; 7, 107, 266; 7, 139, 766; 7, 178, 099; 7, 181, 435; 7, 181, 440; 7, 194, 465; 7, 222, 130; 7, 299, 419; 7, 320, 122 and 7, 356, 779. Business Objects and its logos, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight and its logos , LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. [. . . ] This allows the query engine and virtual target tables to provide additional functionality and higher performance. Data Federator Query Server architecture The illustration below shows an overview of the main components of Data Federator. They are, Data Federator Query Server, Data Federator Designer and Data Federator Administrator. 344 Data Federator User Guide Introduction to Data Federator Query Server Data Federator Query Server architecture 9 How Data Federator Query Server accesses sources of data Real-time access to sources of data is divided into two steps: the connector and the driver. Element Description The connector expands the functionality of the database driver to work with Data Federator Query Server. Connector The connector is an XML file (. wd file) that defines the parameters by type of database and contains metadata about the data managed by Data Federator Query Server. Driver The driver is a file that defines the access parameters to query the database it supports. Data Federator Query Server supports many sources of data, for example: Oracle, SQL Server, MySQL, CSV files, XML files or web services. Database (source) Data Federator User Guide 345 9 Introduction to Data Federator Query Server Data Federator Query Server architecture The illustration below shows an example of how the Data Federator Query Server relates to the sources of data. 346 Data Federator User Guide Introduction to Data Federator Query Server Data Federator Query Server architecture 9 Data experts and data administrators The database administrator is the person who sets up the connection and allows others to connect to the data base. This person is not necessarily the data expert who controls the Data Federator Designer. For this reason, a system of aliases facilitates access to the often highly-customized database resources. Once the connections are made, Data Federator provides an end-to-end view via Data Federator Administrator and Data Federator Designer, from the database resources to the target tables. These two web-based tools respectively provide functionality for the data administrator and the data expert. Related Topics · The Data Federator application on page 26 Key functions of Data Federator Administrator The main functions performed by Data Federator Administrator on Data Federator Query Server are as follows: · Setting up and managing users and their roles · · Managing resources and database connections Monitoring query execution Related Topics · · · · About user accounts, roles, and privileges on page 504 Managing resources using Data Federator Administrator on page 483 Data Federator Query Server overview on page 344 Query execution overview on page 530 Data Federator User Guide 347 9 Introduction to Data Federator Query Server Security recommendations Security recommendations Business Objects recommends that you use a firewall and use a standard http protocol to protect and access the Data Federator Query Server. 348 Data Federator User Guide Connecting to Data Federator Query Server using JDBC/ODBC drivers 10 10 Connecting to Data Federator Query Server using JDBC/ODBC drivers Connecting to Data Federator Query Server using JDBC Connecting to Data Federator Query Server using JDBC This section describes how to connect your applications using JDBC so that they can retrieve data from Data Federator Query Server. Installing the JDBC driver with the Data Federator installer This procedure shows you what you need to install in order to use the JDBC driver for Data Federator Query Server in your client application. This procedure applies when you have the Data Federator or Data Federator Drivers installer. Use the Data Federator or Data Federator Drivers installer on the Data Federator CD-ROM to install the JDBC driver. Add data-federator-installation-dir/JdbcDriver/lib/thindriv er. jar to the classpath that your client application must search when loading the Data Federator Query Server JDBC driver. Use this as the class name of the JDBC driver that your client application loads: com. businessobjects. datafederator. jdbc. DataFederatorDriver Note: Data Federator remains compatible with previous versions. You can still use the class name LeSelect. ThinDriver. ThinDriver, but it is recommended that you update to the new name above. For certain applications, you may need to launch the JVM with the following option: -Djava. endorsed. dirs=data-federator-installation-dir/Jdbc Driver/lib 350 Data Federator User Guide Connecting to Data Federator Query Server using JDBC/ODBC drivers Connecting to Data Federator Query Server using JDBC 10 If your application does not allow you to set the java. endorsed. dirs option, set a system CLASSPATH variable that includes all the . jar files from the directory: data-federator-installation-dir/JdbcDriver/lib Installing the JDBC driver without the Data Federator installer If you do not have the Data Federator installer, but you can access the JDBC files that come with Data Federator, then you can make a JDBC connection as follows. Retrieve thindriver. jar from the machine where Data Federator is installed, from the directory data-federator-installation-dir/Jdbc Driver/lib. If: · the parameter commProtocol=jacORB is used, you will also need avalon-framework-4. 1. 5. jar, jacorb. jar and logkit-1. 2. jar · your client application uses JDK1. 4, you will also needicu4j. jar 2. Copy these files to a directory of your choice (your-jdbc-driver-direc tory). 3. Add your-jdbc-driver-directory/thindriver. jar to the classpath that your client application must search when loading the Data Federator Query Server JDBC driver. For certain applications, you may need to launch the JVM with the following option: -Djava. endorsed. dirs=your-jdbc-driver-directory If your application does not allow you to set the java. endorsed. dirs option, set a system CLASSPATH variable that includes all the above . jar files. Data Federator User Guide 351 10 Connecting to Data Federator Query Server using JDBC/ODBC drivers Connecting to Data Federator Query Server using JDBC Connecting to the server using JDBC This procedure shows how to establish a connection between your application and Data Federator Query Server. In the client application that you are using to connect, enter the connection URL: jdbc:datafederator://host[:port][/[catalog]][[;paramname=value]*] Note: Data Federator remains compatible with previous versions. You can still use the url prefix jdbc:leselect:, but it is recommended that you update to the new prefix above. [. . . ] That is, only one IP address on which the server can be contacted by clients. Configurations with multiple clients in multiple independent sub-networks are not supported. If you have a multi-interface configuration on your server, you should explicitly specify the public IP to be used by the server. All clients that can contact this IP can create connections to the server. [. . . ]