From MIKE2 Methodology
|
| This article is currently Under Construction. It is undergoing major changes as it is in the early stages of development. Users should help contribute to this article to get it to the point where is ready for a Peer Review.
|
ETL Integrator consists of 3 components. An ETL service engine that is a JBI compliant service engine implementation which can be deployed in a JBI container. An ETL Editor that is a design time netbeans module which allow users to design ETL process in a graphical way. An ETL Project that is a design time netbeans module which allows users to package ETL related artifacts in a jar file which could be deployed onto the ETL service engine.
Relationship to MIKE2.0
SAFE Architecture
- Used to deliver the ETL sub-component
Overall Implementation Guide
ETL Design and Implementation Activities of MIKE2.0, which are:
Alignment with Strategic Requirements for Infrastructure Development
Product Review
Key Features
- Standalone ETL Editor (NetBeans plug-in) that will produce artifacts for ETL SE and standalone eTL runtime.
- ETL Editor integrated with NetBeans Database Explorer.
- Expose Flat file database to NetBeans Database Explorer and custom action to create table from flat file (Tools->Flat file DB).
- Integrate ETL deployment with CAPS Release 6 deployment framework.
- Runtime Service Engine(SE) based on JBI framework
- Standalone ETL Engine – can be invoked from command line or any Java class
Pros
- Free
- Good graphical interface through ETL Editor
Cons
- Online help and support is limited
Desired Enhancements
Functonality that users of the MIKE2.0 Methodology would like to see added to this product are as follows:
User Valuation Enhancements
Voting scores from MIKE2.0 Contributors on the value of the asset in the context of the overall methodology
Usage
Product Access
ETL Integrator Download available from product website
Open Source Licensing
Comparable Open Source Products
Reference Implementations through MIKE2.0