Integrating Data in TimesTen

Oracle Changed Data Capture Adapters 28-3

28.2.3 Connectivity Requirements

In order to use the Attunity Stream technology, you must first install the Attunity drivers in the drivers directory of your Oracle Data Integrator installation and restart ODI. See Add Additional Drivers and Open Tools in the Oracle Fusion Middleware Installation Guide for Oracle Data Integrator. The driver files include the following: nvjdbc2.jar, nvapispy2.jar, nvlog2.jar.

28.3 Setting up the Topology

Setting up the Topology consists in: 1. Creating an Attunity Stream Data Server 2. Creating an Attunity Stream Physical Schema

28.3.1 Creating an Attunity Stream Data Server

An Attunity Stream data server corresponds to the server and workspace storing the Attunity Stream datasources.

28.3.1.1 Creation of the Data Server

Create a data server for the Attunity Stream 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 an Oracle data server: 1. In the Definition tab: ■ User : User profile to connect the workspace. If you are using anonymous access or specifying the user and password on the URL, leave this field and the JDBC Password field empty. ■ Password : Master password for the user profile. 2. In the JDBC tab: ■ JDBC Driver : com.attunity.jdbc.NvDriver ■ JDBC URL: jdbc:attconnect:host_name:portworkspace [;AddDefaultSchema=1][;parameter=value] You can use in the URL the properties listed in: Table 28–1 JDBC Attunity Driver Properties Option Description host_name Name of the machine running the Attunity daemon port Port that the daemon listens to workspace Daemon’s workspace. Default is Navigator. AddDefaultSchema=1 This parameter specifies that a schema shows the default owner name public if the data source does not natively support owners. It may be needed in some cases as Oracle Data Integrator makes use of the owner value. 28-4 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator For more information on the JDBC URL connection details, see the Oracle Application Server CDC Adapters Installation Guide.

28.3.2 Creating an Attunity Stream Physical Schema

Create an Attunity Stream physical schema using the standard procedure, as described in Creating a Physical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. This physical schema represents the Attunity Stream datasource from which you want to read the changed data. While defining the physical schema, the list of datasources and owners available for your workspace is displayed, provided that the data server is correctly configured. Public is displayed if no datasources and owners exist. 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.

28.4 Setting Up an Integration Project

Setting up a project using the Attunity Stream 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 LKM Attunity to SQL into your project for getting started with Attunity Stream.

28.5 Creating and Reverse-Engineering an Attunity Stream Model

This section contains the following topics: ■ Create an Attunity Stream Model ■ Reverse-engineer an Attunity Stream Model

28.5.1 Create an Attunity Stream Model

Create an Attunity Stream Model using the standard procedure, as described in Creating a Model of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator.

28.5.2 Reverse-engineer an Attunity Stream Model

Attunity Stream supports standard reverse-engineering. Standard reverse-engineering returns the change tables stored in the datasource as datastores. The change tables contain some CDC header columns in addition to the data columns used for integration. These columns include timestamps, table_name, operation, transactionID, parameter=value Any parameter available for the JDBC driver. Note that it is not needed to specify the datasource using the DefTdpName driver parameter, as Oracle Data Integrator accesses the change tables using the full qualified syntax: DATASOURCE:OWNER.TABLE_ NAME Table 28–1 Cont. JDBC Attunity Driver Properties Option Description