Skip to main content Skip to complementary content

tSetProxy Standard properties

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

The Standard tSetProxy component belongs to the Internet family.

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

Basic settings

Proxy type

List of proxy protocols.

Proxy host

Address of the proxy server.

Proxy port

Number of the proxy port.

Proxy user

Username for proxy authentication.

Proxy password

Password for proxy authentication.

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

No Proxy Hosts

The hosts which should be connected to directly and not through the proxy server. The value can be a list of hosts, each separated by a |, and in addition a wildcard character (*) can be used for matching, e.g. "192.168.0.* | localhost".

This option is available when you select HTTP Proxy or FTP Proxy from the Proxy type drop-down 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 further information about variables, see Talend Studio User Guide.

Usage

Usage rule

Typically used as a subJob by itself, tSetProxy is deployed along with other Internet components.

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!