Skip to main content Skip to complementary content

tSCPClose Standard properties

These properties are used to configure tSCPClose running in the Standard Job framework.

The Standard tSCPClose component belongs to the Internet family.

The component in this framework is available in all Talend products.

Basic settings

Component list

If there is more than one connection in the current Job, select tSCPConnection from the list.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a Job level as well as at each component level.

Global Variables

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

Usage rule

tSCPClose is generally used as a start component. It requires an output component.

Dynamic settings

Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your SCP connection dynamically from multiple connections planned in your Job.

Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Dynamic schema and Creating a context group and define context variables in it.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!