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. This component offers a performance gain as it functions
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.
Component family |
Business Intelligence/Jasper |
|
Function |
Reads and processes data from a source file to create a report |
|
Purpose |
This component allows you to use Jaspersoft’s iReport to create a |
|
Basic settings |
Jrxml file |
Report template file created via iReport. |
|
Source file |
Name of the source file. |
|
Record delimiter |
Delimiter of the records. |
|
Destination path |
Path of the final report file. |
Use Default Output Name |
Select this check box to use the default name for the report |
|
|
Output Name |
Name of the final report. NoteThis field does not appear if the Use Default Output Name box has been |
|
Report type |
File type of the final report. |
|
iReport |
Edit the command to provide the path of iReport’s execution file, |
|
Launch |
Click to run iReport. |
Advanced settings |
tStatCatcher Statistics |
Select this check box to collect log data at the component |
Specify Locale |
Select this check box to choose a locale from the Report Locale list. NoteThe first line of the Report |
|
Encoding |
Select an encoding mode from this list. You can select Custom from the list to enter an encoding |
|
Global Variables |
NB_LINE: the number of rows read by an input component or ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see Talend Studio |
|
Usage |
This component is closely related to Jaspersoft’s report designer |
|
Limitation |
n/a |
For related scenarios, see Scenario: Generating a report against a .jrxml template.