tJasperOutput

• Built-in: No property data stored centrally.
• Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved.

Select the file type of the final report.

• A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

  Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

  • View schema: choose this option to view the schema only.

  • Change to built-in property: choose this option to change the schema to Built-in for local changes.

  • Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

    If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

  The component supports a dynamic schema. The columns in the Talend schema and the columns defined in the JasperReports JRXML template must match. Extra input columns are discarded, and missing input columns are filled with null values.

• Built-in: The schema is created and stored locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.

• Repository: The schema already exists and is stored in the Repository, hence can be reused. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Click to synchronize the output file schema with the input file schema. The Sync function only displays once the Row connection is linked with the output component.

Select or enter the path of the final report file.

Enter the name of the final report.

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.

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.

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 rule

The input date pattern in the Talend schema must match the format of the incoming date values. Define output date patterns in the JasperReports JRXML template.

The columns in the Talend schema 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 tJasperOutput 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.