The User Defined Java Class Step

info_steps

Today I would like to talk about the “User Defined Java Class” a.k.a. UDJC step introduced in Kettle 4.0. This step is incredibly versatile. It allows you to put arbitrary processing code into the ETL without the penalty of a performance hit. This article shows how to use the step in different scenarios, explaining each of . . . → Read More: The User Defined Java Class Step

Developing a Custom Kettle Plugin: Triggering a Report on JasperServer

screenshot-job

The previous posts on Kettle plugin development focus on transformation steps. It is also possible to extend Kettle with custom job entries. This post introduces a plugin that provides a job entry which can trigger a report on JasperServer 3.7 Community Edition. Scheduling reports can be a tricky thing. If you keep your reports on JasperServer, . . . → Read More: Developing a Custom Kettle Plugin: Triggering a Report on JasperServer

Run Kettle Job for each Row

run for each row

Sometimes it would be nice to execute a Kettle job or transformation multiple times, each time with different parameters passed in. Suppose for example you are doing migration work and need to import legacy data one day at a time. You already have a Job in place that imports data for a particular date. The date must be specified as a parameter. Suppose you need to import all data since a fixed start date up to yesterday. Running the import for every day manually is a pain and it is error prone. Would it not be nice to let Kettle figure out the proper dates and run the import job for each date? . . . → Read More: Run Kettle Job for each Row

Date calculation in iReport

Screen Shot Date Calculations

When working with JasperServer, JasperReports, and iReport it is a common problem to perform date calculations. You would usually want to calculate dates to fill parameters when calling sub reports for example. iReport expressions offer a way to do calculations in Java or Groovy. But each calculation, like the definition of a parameter value, must consist of exactly one expression. When trying to define a complex date object, describing the last day of the last month for example, most people find it very difficult, if not impossible, to do this in a single expression. . . . → Read More: Date calculation in iReport