As clover ETL is a 3rd party technology, you are required to purchase at an independent license, probably the GUI desktop version for 1 system, costing a whopping $4000.

As an alterative, I have stewed more toward the concept of java pre-processors (JPPs) to accommodate the code modification and conformance checking. I find Individuals also prefer the scalability of java as a technology to clover.

The image presents the concept of a JPPs becoming the intermediate from converting any data feeds into the acceptable OIA format, which can then be dropped into the OIA staging repository in preparation to importing them into OIA.

With this in mind, I have been suggesting this alternative to companies though I only recently came across the idea of java classes as java beans and allowing OIA’s spring framework to schedule the alteration.

For scheduling purposes, the java file should extend the TimerTask package which will make the manipulations required to then populate this into the OIA staging as a new file.

I have created a new file called jpp-etl.xml, which resides within the WEB-INF directory and altered the web.xml (to reference the jpp-etl.xml file). Once configured, OIA can then take the responsibility on the ETL effort without the dependency of OOTB clover graphs.

About the author