Page Comparison

h2. Kettle Transformation

Executes a Kettle transformation and saves the resulting data into an output result set

.

h4. *Component Name:

* KettleComponent


h4. *Inputs:*

_REQUIRED_
*Monitor Step* \- The step in the transformation from which to retrieve success and error rows.

_OPTIONAL_
*Transformation Inputs* \__-\- Allows for the inclusion of miscellaneous inputs to the Kettle transformation.
*directory* \-\- specified if loading from the kettle repository, used in conjunction with the input "transformation"

h4. *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.

*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.

h4. *Resources:

*

_REQUIRED_
*Transformation File* _\-\-_ The kettle transformation file that is be executed.

h2. *Kettle Job*

Executes a Kettle Job.

h4. *Component Name:* KettleComponent


h4. *Inputs:*

_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"

h4. *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.

h2. Kettle Repository Configuration

To configure the kettle repository, modify the pentaho-solutions/system/kettle/settings.xml file:

*repository.type* \-\- files or rdbms

*repository.name* \-\- the name of the repository

*repository.userid* \--the username to access the repository

*repository.password* \-\- the password to access the repository

{note

:title

=Kettle setup for BI Server

}
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:

[http://jira.pentaho.com/browse/BISERVER-2858

]
{note}

h2. 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>

&nbsp;&nbsp;<name>parameterOne</name>
&nbsp;&nbsp;<mapping>inputOne</mapping>
</set-parameter>

Format for: 'set-variable':

<set-variable>

&nbsp;&nbsp;<name>variableOne</name>
&nbsp;&nbsp;<mapping>inputOne</mapping>
</set-variable>

Format for: 'set-argument':

<set-argument>

&nbsp;&nbsp;<name>1</name>
&nbsp;&nbsp;<mapping>inputOne</mapping>
</set-argument>

<set-argument>

&nbsp;&nbsp;<name>2</name>
&nbsp;&nbsp;<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.