tBRMS Standard properties - Cloud - 8.0

Property type

Either Built-in or Repository .

Built-in: No property data stored centrally.

Repository: Select the repository file where properties are stored. The fields that follow are completed automatically using the fetched data.

Schema and Edit Schema

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

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.

Built-in: You create and store the schema locally for only the current component. 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 in various projects and Job flowcharts. For more information about a component schema in its Basic settings tab, see Basic settings tab.

XML Field

Select the XML field for the data to be written to the output file.

Choose rule module

Select from the list:

- Use latest deployment from Drools workbench: Always choose this option when you run the Job for the first time. The Job uses the latest deployment of the rule on the Drools repository. If the rule has been changed meanwhile, the Job results will be different.

- Use local rules: with this option, you execute the Job with the local rule you imported previously from the repository to the root folder of Talend Studio, in /studio_path/Drools/<project_name>, that is the latest package you browse from the Drools workbench. This means, even if you have modified the rule and deployed it on the repository, the Job results will not be different.

Do not use this option when you run your Job for the first time.

The fields that follow will vary according to your choice.

Drools Workbench Connection

Drools Workbench URL

Enter the address of the business rule repository.

Enter the authentication information used to connect to the Drools Workbench of interest.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Module list

Click the [...] button next to the field to open a list of the Jars on the Drools Workbench.

You can select Jar files from all branches, main and other branches. In Deploy Package, click the [...] button and select the Master artifacts or Custom artifact tab. To select a Jar file that is not from the latest version or the main branch, select the Custom artifact tab and enter the artifact ID, the group ID and the version. You can find these parameters in the Drools workbench.

Snapshot versions are not supported.

Maven Deployment Path

After you select the Jar file from the Drools Workbench, this field is automatically populated.

Class Name

After you select the Jar file, this field is automatically populated with the name of the class in which the business rule is stored in a Jar file.

A Drools flow describes the order in which a series of business rules are executed. Its flow ID is defined manually when you are creating the Drools flow.

When you need to call a specific Drools flow via tBRMS to use the execution order it defines, enter the corresponding flow ID in this field.

For more information about Drools flow, see the relevant Drools manuals.

Configure XML Tree

Click [...] to map the source schema to the XML output schema.

Group by

Use the tool bar to modify the column order.

Advanced separator

Select this check box to modify the separators used for numbers.

Encoding

Select the encoding type from the list or select Custom and define it manually. This field is compulsory for DB data handling.

tStatCatcher Statistics

Select this check box to collect the 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.

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.

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 component handles data flows. Therefore it requires input and output components.

Limitation

When using the tBRMS component in subJobs with the same value in the Class name field, select the Use an independent process to run subJob check box in the tRunJob component settings to be able to run the Job correctly.

For further information about the tRunJob component, see tRunJob.