Problem in Implementing CompanyTransactionsTutorial example

CloverDX Platform
1

Hi all,
I am new in CloverEtl. I am trying to implement CompanyTransactionsTutorial in CloverEtl Designer version.
Well, in that the first graph is about splitting transactions(A01_SplittingTransactions.grf).
When I am implementing it in CloverEtl Community, it is giving the expected result but when I am implementing it in CloverEtl Designer, its not giving the expected result.

the result it is giving is as follows:

INFO [main] - *** CloverETL framework/transformation graph, (c) 2002-2011 Javlin a.s, released under GNU Lesser General Public License ***
INFO [main] - Running with CloverETL library version 3.2.0 build#57 compiled 20/12/2011 01:02:50
INFO [main] - Running on 2 CPU(s), OS Linux, architecture i386, Java version 1.6.0_24, max available memory for JVM 241536 KB
INFO [main] - Loading default properties from: defaultProperties
INFO [main] - Graph definition file: graph/A01_SplittingTransactions.grf
INFO [main] - Graph revision: 1.32 Modified by: mgarg Modified: Wed Feb 08 15:56:01 IST 2012
INFO [main] - Checking graph configuration…
INFO [main] - Graph configuration is valid.
INFO [main] - Graph initialization (A01_SplittingTransactions)
INFO [main] - [Clover] Initializing phase: 0
INFO [main] - [Clover] phase: 0 initialized successfully.
INFO [main] - register MBean with name:org.jetel.graph.runtime:type=CLOVERJMX_1328616503664_0
INFO [WatchDog] - Starting up all nodes in phase [0]
INFO [WatchDog] - Successfully started all nodes in phase!
INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - ----------------------** Final tracking Log for phase [0] **---------------------
INFO [WatchDog] - Time: 08/02/12 15:56:13
INFO [WatchDog] - Node ID Port #Records #KB aRec/s aKB/s
INFO [WatchDog] - ---------------------------------------------------------------------------------
INFO [WatchDog] - TransactionsDelimited TRANSACTIONS_DELIMITED FINISHED_OK
INFO [WatchDog] - %cpu:… Out:0 100000 10991 20000 2198
INFO [WatchDog] - Splitting Data SPLITTING_DATA1 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 100000 10991 20000 2198
INFO [WatchDog] - Out:0 100000 2581 20000 516
INFO [WatchDog] - Out:1 0 0 0 0
INFO [WatchDog] - Out:2 0 0 0 0
INFO [WatchDog] - Out:3 0 0 0 0
INFO [WatchDog] - ExtSort EXT_SORT3 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - Out:0 0 0 0 0
INFO [WatchDog] - Dedup DEDUP3 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - Out:0 0 0 0 0
INFO [WatchDog] - EmployeesDelimited EMPLOYEES_DELIMITED FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - ExtSort EXT_SORT2 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - Out:0 0 0 0 0
INFO [WatchDog] - Dedup DEDUP2 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - Out:0 0 0 0 0
INFO [WatchDog] - CustomersDelimited CUSTOMERS_DELIMITED FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - ExtSort EXT_SORT1 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - Out:0 0 0 0 0
INFO [WatchDog] - Dedup DEDUP1 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - Out:0 0 0 0 0
INFO [WatchDog] - AmountsDelimited AMOUNTS_DELIMITED FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 0 0 0 0
INFO [WatchDog] - ExtSort EXT_SORT0 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 100000 2581 20000 516
INFO [WatchDog] - Out:0 100000 2581 20000 516
INFO [WatchDog] - Dedup DEDUP0 FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 100000 2581 20000 516
INFO [WatchDog] - Out:0 100000 2581 20000 516
INFO [WatchDog] - IDsDelimited IDS_DELIMITED FINISHED_OK
INFO [WatchDog] - %cpu:… In:0 100000 2581 20000 516
INFO [WatchDog] - ---------------------------------** End of Log **--------------------------------
INFO [WatchDog] - Execution of phase [0] successfully finished - elapsed time(sec): 5
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
INFO [WatchDog] - 0 FINISHED_OK 5 7992
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
INFO [WatchDog] - WatchDog thread finished - total execution time: 5 (sec)
INFO [main] - Freeing graph resources.
INFO [main] - Execution of graph successful !

Only one OUT:0 port is sending 100000 records whereas others(OUT:1, OUT:2, OUT:3) are sending 0 records.

I am not able to understand where I am going wrong. Can anyone help me to resolve this problem.

Thanks

2

Hi MGarg,

Do you use unaltered version of graph from examples? If you changed it (seems to me there are different names of components), or build your own version, can you please send me your graph?

Thank you

3

HI,
Thanx for your response.

This is my graph below:

<?xml version="1.0" encoding="UTF-8"?> <!\[CDATA\[//#CTL2

// Transforms input record into output record.
function integer transform() {
$0.AmountID = $0.AmountID;
$1.Amount = $0.Amount;
$0.CustomerID = $0.CustomerID;
$2.CustomerState = $0.CustomerState;
$2.CustomerSurname = $0.CustomerSurname;
$2.CustomerFirstname = $0.CustomerFirstname;
$0.EmployeeID = $0.EmployeeID;
$3.EmployeeSurname = $0.EmployeeSurname;
$3.EmployeeFirstname = $0.EmployeeFirstname;
$1.AmountID = $0.AmountID;
$2.CustomerID = $0.CustomerID;
$3.EmployeeID = $0.EmployeeID;

return ALL;
}

// Called during component initialization.
// function boolean init() {}

// Called during each graph run before the transform is executed. May be used to allocate and initialize resources
// required by the transform. All resources allocated within this method should be released
// by the postExecute() method.
// function void preExecute() {}

// Called only if transform() throws an exception.
// function integer transformOnError(string errorMessage, string stackTrace) {}

// Called during each graph run after the entire transform was executed. Should be used to free any resources
// allocated within the preExecute() method.
// function void postExecute() {}

// Called to return a user-defined error message when an error occurs.
// function string getMessage() {}
]]>















4

Hi MGarg,

graph you sent me, is not the one from which log was generated. Log contained in your first post contained names of components like “SPLITTING_DATA1”, but the graph you send not. I guess you sent me original graph from our sources (and it works for me).