This time you will call the parameterized transformation from a new job.
hello_world.kjb
job you created in the first section and save it as hello_world_fixedvalues.kjb
. chapter10
string by the string fixedfolder
. ${Internal.Job.Filename.Directory}/transformations/hello_world_param.ktr
.C:pdi-ce>kitchen /file:c:/pdi_labs/ hello_world_param.kjb /norep
/home/yourself/pdi-ce/kitchen.sh /file:/home/yourself/ pdi_labs/hello_world_param.kjb /norep
fixedfolder
has been created. hello.txt
with the following content:Hello, reader!
You reused the transformation that expects an argument and a named parameter from the command line. This time you created a job that called the transformation and set both the parameter and the argument in the transformation job entry setting window.
Then you ran the job from a terminal window, without typing any arguments or parameters. It didn't make any difference for the transformation. Whether you provide parameters and arguments from the command line or you set constant values in a transformation job entry, the transformation does its job—creating a file with a custom message in the folder with the name given by the ${HELLOFOLDER}parameter.
Modify the hello_world_param.kjb
job so that it generates three files in the default ${HELLOFOLDER}
, each saying "hello" to a different person.
After the creation of the folder, use three transformation job entries. Provide different arguments for each.
Run the job to see that it works as expected.
In Chapter 6, you built a transformation that created the data for a time dimension. Then in Chapter 8, you finished the transformation loading the data into a time dimension table.
The transformation had several named parameters, one of them being START_DATE
. Create a job that loads a time dimension with dates starting at 01/01/2000
. In technical jargon, create a job that calls your transformation and passes it a value for the START_DATE
parameter.
13.58.44.229