I am new to this tool. I understand that the CloverGUI can be used to perform data transformations. I am working on an application that processes a bunch of flat files containing comma delimited records. The app would take one record at a time and transform it to an XML file and send it to a servlet for further processing. How can I accomplish this functionality without using the CloverETL GUI tool? Since this tool is java based, are there some jar files that I need to import into my classpath to start woking with my process? I just want to know how CloverETL can be integrated into my java application. I don’t want to use the standalone version. Any comments on this would be greatly appreciated
I have created an Eclipse project with my transformations set up and all working. Next step for me is to now create a Java project and integrate these graph files into the Java project. I have had a look around the Wiki and the mailing list, but the information appears a bit disjointed and out of date. Is there a decent explanation for all the classes and methods used somewhere?
The basic steps outlined in most of the text seem to be as shown below. The pieces that are missing in the explanations are:
EngineInitializer.initEngine does not line up with what the parameters are in JavaDocs?
Is there an example showing how to link all the work done in a CloverETL project in the code below? Stuff like workspace.prm paramaters, linked dB and MetaData, etc.
Is there a working example to show how this is done? The code below has no definition for “in”, pluginRootDir, configFileName, etc.
I know all the info is there, but just asking for a working example if anyone has one.
Thanks
Des
// engine customization
GraphRuntimeContext runtimeContext = new GraphRuntimeContext();
// engine initialization - should be called only once
EngineInitializer.initEngine(pluginsRootDirectory, configFileName, logHost);
Hello Des,
if you download examples, you can found there eclipse project called javaExamples. After adding some jars to the classpath examples are ready to run:
Thanks for the help. I downloaded the examples and I am testing with the Java examples. I have a few issues though and was wondering if you could clarify?
I ran the example and it works fine. I then incorporated the convention used in workspace.prm and moved these parameters into the params.txt file used in the example. This is shown below. The intention is to configure the example.grf graph with a generic input of the DataReader of the form ${DATAIN-DIR}/bonus.csv instead of the path as given before.
PROJECT= .
# (Please use slash ‘/’ character as a path delimiter in all path specifications, e.g. C:/Users/username/workspace/project) #Project properties #Fri May 15 08:30:33 EST 2009
CONN_DIR=${PROJECT}/conn
SEQ_DIR=${PROJECT}/seq
DATAOUT_DIR=${PROJECT}/data-out
GRAPH_DIR=${PROJECT}/graph
TRANS_DIR=${PROJECT}/trans
DATATMP_DIR=${PROJECT}/data-tmp
META_DIR=${PROJECT}/meta
LOOKUP_DIR=${PROJECT}/lookup
DATAIN_DIR=${PROJECT}/data-in
Thanks for the prompt reply. Not sure I understand how this works then? Do I add this to the Source of the graph as a separate line or is this the URL of the reader component.
Apologize for the silly questions, but still trying to get my head around the setup?
Hi Des,
if you define some graph parameters in external file (e.g. params.txt), you have to pass on the file to the graph. You can do it in CloverETL Designer (see External (Shared) Parameters), change manually graph source (see Property and property file) or pass the parameter’s file when running graph (-cfg swich - see Command line).
When the graph “knows” the parameters, you can use them, eg. in component’s properties: