X hits on this document





43 / 131


Daemon’s workspace (default is “Navigator”)


This parameter specifies that a schema shows a 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.


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.

For more information on the JDBC URL connection details, refer to the Attunity Stream documentation.

JDBC 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. JDBC Password: Master password for the user profile.

  • 4.

    Create a physical schema under this data server corresponding to 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 (“public” if none exist), provided that the data server is correctly configured.

  • 5.

    Create a logical schema for this physical schema in the appropriate context.

Creating and Reverse-Engineering an Attunity Stream Model

To create an Attunity Stream model, use the ODI standard procedure for model creation. 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, context, etc. Refer to the Attunity Stream documentation for more information on the header columns content.

Setting up the Project

Import the LKM Attunity to SQL into your ODI project, if it is not already in your project. For more information about importing a KM, please refer to the Oracle Data Integrator User’s Guide.

Designing an Interface Using the LKM Attunity to SQL

To create an integration interface, which loads Attunity Stream data into your Oracle Data Integrator integration project, run the following steps:

  • 1.

    Create an integration interface with Attunity Stream source datastores and SQL compliant target datastores.

  • 2.

    Create joins, filters and mappings as usual. Note that joins between change tables are not allowed on the source. They should be performed on the interface’s staging area.

  • 3.

    In the Flow tab of the interface, select the source set containing the source change table(s) and select the LKM Attunity to SQL.

  • 4.

    Set the KM options as follows:

DELETE_TEMPORARY_OBJECTS - Set this option to No, if you wish to retain temporary objects (files and scripts) after integration.

Knowledge Modules Reference Guide


Document info
Document views565
Page views568
Page last viewedTue Jan 24 15:32:42 UTC 2017