tDqReportRun Standard properties

Schema and Edit schema

A schema is a row description, it defines the number of fields to be processed and passed on to the next component. The schema is either Built-in or stored remotely in the Repository.

The schema of this component is read-only. It gives some information about the report such as report identification, report name, execution time and so on.

Built-in: You create and store the schema locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Repository: You have already created and stored the schema in the Repository. You can reuse it in other projects and Job designs. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Refresh Dependency

Click this button to update the jars needed by the report data mart before executing the report Job.

For further information about configuring databases to store report results, see Managing the report database.

Browse Reports

Click this button to open a dialog box where you can select one or more reports to be generated.

The reports you select overwrite the current Job contexts.

If the reports you select store analysis results in different data marts, generating the report will store these results in the different databases accordingly. However, one report file will be generated in the path defined in the component basic settings.

All reports created in the Profiling perspective are listed in this dialog box.

Report filenames

You can set several report paths separated by commas.

Output folder

Set the path to the folder where to store the generated report file.

Driver JAR

Jars are listed by default in this table if you generate the Job via the Generate report file menu item in the Profiling perspective.

You can still add Jar files by adding lines to the table. Then on each line, click the [...] button to open a wizard from which you can select a driver Jar relevant to the connection used by the analyses listed in the report. In the wizard, you can select Jars from either internal or external modules.

Select this check box when you use tParallelize to run tDqReportRun components in parallel.

tStat Catcher Statistics

Select this check box to collect log data at the component level.

Global Variables

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 check box is cleared, if the component has this check box.

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

This is a start component of a Job. It needs an output component to which it sends information about report execution.