Relational Extraction, Transformation and Loading

Enhydra Octopus is a Java-based Extraction, Transformation, and Loading (ETL) tool. It may connect to any JDBC data sources and perform transformations defined in an XML file.

DODS data models are supported by generating oid's for new objects. Natural keys can be used to insert/update existing data and create relationships with oid's.

A loadjob-generator is provided to generate Octopus loadjob skeletons (and even DODS DOML files !) from an existing database. Many different types of databases can be mixed (MSSQL, Oracle, DB2, QED, JDBC-ODBC with Excel and Access, MySQL, CSV-files, XML-files,...) Four special JDBC drivers come with Octopus to support JDBC access to CSV-files (CSV-JDBC), MS-SQL (FreeTDS), XML (XML-JDBC) and property files (i18n-JDBC).

Octopus supports Ant and JUnit to create a database / tables and extract /load data during a build or test process. Loadjobs can be executed during execution of an application installation (e.g. NSIS, Installshield,...)

Octopus gives you a very generic way to transform data. You can define transformations by implementing Transformer interface or using JavaScript code (directly in the load job XML file).

Enhydra Octopus is included in Enhydra Server and Enhydra Enterprise distributions !

The ObjectWeb GForge project

The ObjectWeb GForge project for Enhydra Octopus contains all the needed links for mailing lists, News, CVS access and Downloads.

What you can do with Enhydra Octopus

Did you ever want to transfer data from one JDBC source, CSV-file, Excel,... to another and do some kind of transformation during copy, like:

normalize unnormalized data
create artificial keys (oid's)
calculate counters and subcounters
insert and/or update data and relations based on natural keys
execute SQL statements during / before / after transfer
make big loadjobs restartable with configurable commitcounts
replace variables in the data / sql-statements with values just known at runtime
migrate data from one database vendor into another
structure your jobs with nested included files ?

Did you ever want to create a database like the following in one step:

create the tables
load data from another source (CSV, Excel, XML, another database)
create indexes
create primary keys
create foreign keys ?

Do you need to maintain such jobs independent from a database vendor ? Maybe during build / test deployment or execution of a setup ?

Check this out...!