| Wiki Markup |
|---|
{scrollbar} |
The Kettle actions allow for the execution ETL operations within your action sequence using the Kettle open source ETL tool. Supported operations include the execution of Kettle ETL transformation and Kettle jobs. For further information on Kettle refer to http://kettle.pentaho.org.
...
Execution Status Output - The execution status of the job or transformation (Success, Failure, etc...).
Execution Log Output - The execution log of the given job or transformation.
Transform Success Output - The name of the result set containing the successfully processed data from executing the Kettle transformation.
Transform Success Count Output - The number of rows in the Transform Success Output result set.
Transform Error Output - The name of the result set containing the data that failed processing from executing the Kettle transformation.
Transform Error Count Output - The number of rows in the Transform Error Output result set.
...
OPTIONAL
Job Inputs -- Allows for the inclusion of miscellaneous inputs miscellaneous inputs to the Kettle job.
directory -- specified if loading from the kettle repository, used in conjunction with the input "job"
Outputs:
Execution Status Output - The execution status of the job or transformation (Success, Failure, etc...).
Execution Log Output - The execution log of the given job or transformation.
Resources:
REQUIRED
Job File - The Kettle job file to be executed.
...
| Note | ||
|---|---|---|
| ||
The name you use for repository.name must match a connection defined in Kettle repository.xml file. This file is located by default in the user's home directory (~/.kettle/repositories.xml) It needs to be in the home directory of the effective user that the BI Server is running as. The easiest way to create the files and directories required is to run Spoon on the server machine and do the normal repository setup. This requirement will go away when the following JIRA case is completed: |
Support for Parameters, Variables and Arguments
Parameters, variables and arguments may be passed into PDI Jobs and Transformations by mapping KettleComponent inputs. All values to be sent to the PDI Job / Transformation MUST be included in the 'action-inputs' section of the KettleComponent's 'action-definition' element.
Once the desired values are in the 'action-inputs' section they may be mapped by adding either a 'set-parameter', 'set-variable', or 'set-argument' element into the 'component-definition' section of the KettleComponent's 'action-definition'.
Format for: 'set-parameter':
<set-parameter>
<name>parameterOne</name>
<mapping>inputOne</mapping>
</set-parameter>
Format for: 'set-variable':
<set-variable>
<name>variableOne</name>
<mapping>inputOne</mapping>
</set-variable>
Format for: 'set-argument':
<set-argument>
<name>1</name>
<mapping>inputOne</mapping>
</set-argument>
<set-argument>
<name>2</name>
<mapping>inputTwo</mapping>
</set-argument>
In the above three examples, the 'name' element maps to the name in the PDI Job / Transformation (Except in the case of argument it is, consecutively 1-10, mapping to the expected command line arguments). The 'mapping' element maps to the parameter in 'action-inputs'.
Please see: http://jira.pentaho.com/browse/BISERVER-257 for a more complete example.