Oracle International Corporation

John Westworth Leigh

Robert Costin Velisar

Chetan Kothari

David Allan

Kwok Hung Lau

Daniel A Gallagher

Ganesh Seetharaman

Kwok-hung (Thomas) Lau

Thomas Lau

Joseph F Klein

The present disclosure relates generally to a data integration system that integrate an object based data integration tool, such a GUI-based data integration tools, with version control systems using a relational database repository for persistence. Examples of distributed version control systems include Git, Mercurial, and Bazaar, and examples of centralized version control systems include Subversion, CVS etc. in centralized or distributed environments.

Integrating object-based data integration tool with a version control system in centralized and decentralized environments

The present disclosure relates generally to a data integration system that may provide techniques for capturing definitions from business entities and how the business entities are implemented in a set of tables. This enables the data integration system to transform a data flow defined using business entities into code that may be used to transform the underlying tables and columns. Additionally to generate tables, classes and APIs to provide persistence of and manipulation for the definitions of these business entities. Additionally to dynamically generate a GUI editor for an object model of arbitrary complexity while maintaining GUI usability. This reduces development time and supports editing of an arbitrary object model. A dynamically generated GUI may be generated from an object model definition that is received from a user and/or is derived from the user's code.

Object mapping using intrinsic persistence metadata and pattern-based rules for mapping transformation

The present disclosure relates generally to a data integration system that may dynamically generate a GUI for an object model of arbitrary complexity while maintaining GUI usability. In some embodiments, the dynamically generated GUI may be generated from an object model definition received from a user. In some embodiments, the object model may be derived from the user's code and then the GUI may be dynamically generated based on the derived object model.

Generic editor layout using intrinsic persistence metadata

In various embodiments, a data integration system is disclosed which enables users to create a logical design which is platform and technology independent. The user can create a logical design that defines, at a high level, how a user wants data to flow between sources and targets. The tool can analyze the logical design, in view of the user's infrastructure, and create a physical design. The logical design can include a plurality of components corresponding to each source and target in the design, as well as operations such as joins or filters, and access points. Each component when transferred to the physical design generates code to perform operations on the data. Depending on the underlying technology (e.g., SQL Server, Oracle, Hadoop, etc.) and the language used (SQL, pig, etc.) the code generated by each component may be different.

System and method for decomposition of code generation into separate physical units though execution units

A data integration system is disclosed that incorporates one or more techniques for simplifying the design and maintenance of a mapping. As components are added or removed to an existing design, the data integration system removes the need to specify all input and output attributes. In one aspect, components types are implemented that allow assignment expressions to reference all or part of upstream components. Therefore, attributes of certain types of components can be propagated to downstream components or otherwise inherited from upstream components with minimal effort on the part of a map designer. During code generation the attributes required to be projected by any component can be derived based on the needs of the downstream components.

Use of projector and selector component types for ETL map design

One embodiment of the present invention provides a system that supports cross-component references in an object-oriented programming system. During operation, the system makes a first attempt to obtain a name for a referenced object through a cross-component reference between a referencing object and the referenced object. This first attempt involves attempting to obtain the name for the referenced object from the referenced object, which involves attempting access the referenced object through an identifier for the referenced object within the cross-component reference. If this first attempt fails, the system makes a second attempt to obtain the name for the referenced object, which involves obtaining a pathname for the referenced object from the cross-component reference.

Growing community of inventors

Sonoma, CA, United States of America

John Westworth Leigh