Skip to main content Skip to complementary content
Close announcements banner

Defining connections between components in a Job script

To add a connection in a Job script, type in the addConnection{} function and define its properties between the brackets.

addConnection{} properties

Function Description Mandatory?

TYPE

Type in the type of connection used in the component, for example: FLOW, REJECT, and so on.

Yes

NAME

Give a name to the connection.

Yes

LINESTYLE

Define the style of the connection. Commonly used values:

  • 0 (default): row connection, which can be:

    • FLOW (Row > Main) for most flow handling components
    • FILTER (Row > Filter) or REJECT (Row > Reject) for tFilterRow
  • 1: SUBJOB_OK (Trigger > On Subjob OK)
  • 3: COMPONENT_OK (Trigger > On Component OK)
  • 4: SUBJOB_ERROR (Trigger > On Subjob Error)
  • 5: COMPONENT_ERROR (Trigger > On Component Error)
  • 6: RUN_IF (Trigger > Run If):
  • 7: Iterate
  • 8: LOOKUP (Row > Lookup)
  • 9: TABLE (for ELT components)
  • 10: Merge (for tUnite)
  • 12: SYNCHRONIZE (Trigger > Synchronize, for tParallelize)
  • 13: PARALLELIZE (Trigger > Parallelize, for tParallelize)

No

SOURCE

Type in the name of the source component.

Yes

TARGET

Type in the name of the target component.

Yes

MONITOR_CONNECTION

Set this parameter to true to monitor the data flow over the connection. The measured information will be interpreted and displayed in a monitoring tool such as Talend Activity Monitoring Console. For information about Talend Activity Monitoring Console, see Talend Activity Monitoring Console User Guide.

By default, this parameter is set to false.

No

Example

The following Job script example shows how to define a Row > Main connection between tFileInputDelimited_1 and tLogRow_1.

addConnection {
	TYPE: "FLOW",
	NAME: "row1",
	LINESTYLE: 0,
	METANAME: "tFileInputDelimited_1",
	SOURCE: "tFileInputDelimited_1",
	TARGET: "tLogRow_1"
	}
}

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!