Skip to main content Skip to complementary content

tWaitForSocket Standard properties

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

The Standard tWaitForSocket component belongs to the Orchestration family.

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

Basic settings


DB server listening port.

Send to client

Enter a string to send to the client. The default is to client:$_.


Select the action to be carried out: keep on listening or close socket.

Print client/server data

Select this check box to display the client or server data.

Advanced settings

tStatCatcher Statistics

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

INPUT_DATA: the data transmitted by the client. This is a Flow variable and it returns a string.

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 an input, trigger component for the subJob executed depending on the condition set. Hence, it needs to be connected to a subJob via an Iterate link.


Outgoing links (from this component to another):

Row: Iterate.

Trigger: On Subjob Ok; On Subjob Error; Run if; On Component Ok; On Component Error.

Incoming links (from one component to this one):


Trigger: On Subjob Ok; On Subjob Error; Run if; On Component Ok; On Component Error; Synchronize; Parallelize.

For further information regarding connections, see Using connections in a Job.

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 – let us know how we can improve!