System Requirements and Certifications Technology Specific Requirements

Files 3-3

3.2.3 Connectivity Requirements

This section lists the requirements for connecting to flat files. JDBC Driver Oracle Data Integrator includes a built-in driver for flat files. This driver is installed with Oracle Data Integrator and does not require additional configuration.

3.3 Setting up the Topology

Setting up the topology consists in: 1. Creating a File Data Server 2. Creating a File Physical Schema

3.3.1 Creating a File Data Server

A File data server is a container for a set of file folders each file folder corresponding to a physical schema. Oracle Data Integrator provides the default FILE_GENERIC data server. This data server suits most of the needs. In most cases, it is not required to create a File data server, and you only need to create a physical schema under the FILE_GENERIC data server.

3.3.1.1 Creation of the Data Server

Create a data server for the File technology using the standard procedure, as described in Creating a Data Server of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. This section details only the fields required or specific for defining a File data server: 1. In the Definition tab: ■ Name : Name of the data server that will appear in Oracle Data Integrator. ■ UserPassword : These fields are not used for File data servers. 2. In the JDBC tab, enter the following values: ■ JDBC Drive r: com.sunopsis.jdbc.driver.file.FileDriver ■ JDBC URL : jdbc:snps:dbfile?property=valueproperty=value... You can use in the URL the properties listed in Table 3–2 . Table 3–2 JDBC File Driver Properties Property Value Description ENCODING encoding_code File encoding. The list of supported encoding is available at http:java.sun.comj2se1.4.2d ocsguideintlencoding.doc.html . The default encoding value is ISO8859_ 1. TRUNC_FIXED_STRINGS TRUE|FALSE Truncates strings to the field size for fixed files. Default value is FALSE. TRUNC_DEL_STRINGS TRUE|FALSE Truncates strings to the field size for delimited files. Default value is FALSE. 3-4 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator JDBC URL example : jdbc:snps:dbfile?ENCODING=ISO8859_1TRUNC_FIXED_ STRINGS=FALSEOPT=TRUE

3.3.2 Creating a File Physical Schema

Create a File physical schema using the standard procedure, as described in Creating a physical schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. In your physical schema, you must set a pair of directories: ■ The Directory Schema, where Oracle Data Integrator will look for the source and target files and create error files for invalid records detected in the source files. ■ A Directory Work Schema, where Oracle Data Integrator may create temporary files associated to the sources and targets contained in the Data Schema. Create for this physical schema a logical schema using the standard procedure, as described in Creating a Logical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator and associate it in a given context.

3.4 Setting Up an Integration Project

Setting up a project using the File database follows the standard procedure. See Creating an Integration Project of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. It is recommended to import the following knowledge modules into your project for getting started: ■ LKM File to SQL OPT TRUE|FALSE Optimizes file access on multiprocessor machines for better performance. Using this option on single processor machines may actually decrease performance. Default value is FALSE. Notes: ■ Data and Work schemas each correspond to a directory. This directory must be accessible to the component that will access the files. The directory can be an absolute path m:publicdatafiles or relative to the runtime agent or Studio startup directory ..demofiles. It is strongly advised to use a path that is independent from the execution location. ■ In UNIX in particular, the agent must have readwrite permission on both these directories. ■ Keep in mind that file paths are different in Windows than they are in UNIX. Take the platform used by the agent into account when setting up this information. Table 3–2 Cont. JDBC File Driver Properties Property Value Description