tJasperOutputExec
Last updated: 9/30/2026Creates a report in rich formats using Jaspersoft's iReport and offers a performance gain as it functions as a combination of an input component and a tJasperOutput component.
This component is closely related to Jaspersoft's report designer -- iReport. It reads and processes data from a source file to create a report against a .jrxml report template defined via iReport. tJasperOutputExec is used as a combination of an input component and a tJasperOutput component. The advantage of using two separate components is that data can be transformed before being used to generate a report and the input sources can be various and rich.
Reads and processes data from a source file to create a report against a .jrxml report template defined via iReport.
tJasperOutputExec Standard properties
These properties are used to configure tJasperOutputExec running in the Standard Job framework.
The Standard tJasperOutputExec component belongs to the Business Intelligence family.
The component in this framework is available in all Talend products.
Basic settings
| Properties | Description |
|---|---|
| Version | Select the Jasper version. Note that Jasper v6 is deprecated. |
| Property type | Either Built-in or Repository.
|
| Jrxml file | Select or enter the path to the report template file created via iReport. |
| Report type |
Select the file type of the final report. |
| Source file | Enter the name of the source file. |
| Field delimiter |
Enter the delimiter of the report fields. |
| Record delimiter |
Enter the delimiter of the report records. |
| Destination folder |
Select or enter the path of the final report file. |
| Use default output name |
Select this checkbox to use the default name for the report generated, which takes the source file's name. |
| Output name |
Enter the name of the final report. Information noteNote: This field does not appear if the Use Default Output Name box has been
selected.
|
Advanced settings
| Properties | Description |
|---|---|
| tStatCatcher Statistics | Select this checkbox to collect log data at the component level. |
| Specify Locale | Select this checkbox to choose a locale from the Report Locale list. Information noteNote: The first line of the
Report Locale list is empty. You can
click it to customize a locale.
|
| Encoding | Select an encoding mode from this list. You can select Custom from the list to enter an encoding method in the field that appears. |
| Source date pattern | Enter the date pattern corresponding to the source file. When using dynamic schema, the date pattern needs to be the input date pattern, rather than the expected output date pattern. The expected output date pattern should be defined in the jrxml file. |
Global Variables
| Variables | Description |
|---|---|
|
Global Variables |
NB_LINE: the number of rows read by an input component or transferred to an output component. This is an After variable and it returns an integer. ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error checkbox is cleared, if the component has this checkbox. A Flow variable functions during the execution of a component while an After variable functions after the execution of the component. To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it. For more information about variables, see Using contexts and variables. |
Usage
| Usage guidance | Description |
|---|---|
|
Usage rule |
The source date pattern must match the format of the incoming date values. Define output date patterns in the JasperReports JRXML template. The columns in the source data and the JRXML template must match. Extra input columns are discarded, and missing input columns are filled with null values. In Metadata Drag and Drop, select the non-Base64 tJasperOutputExec component. The Base64 variant cannot inherit preset metadata values. The old Jasper component remains available but is deprecated. The new v7 unified components do not migrate existing Jobs automatically. An existing user-defined JRXML template may require migration: open and save it in Jaspersoft Studio 7 before using it with this component. |