Skip to main content Skip to complementary content
Close announcements banner

Connecting the components

Use the procedure below to create connections to link the components and finalize the Job script creation.

Procedure

  1. Next to the tLogRow Job script definitions, enter the following script code to define a Merge connection between the first tFileInputDelimited component to the tUnite component.
    addConnection {
    	TYPE: "FLOW",
    	NAME: "row1",
    	LINESTYLE: 10,
    	SOURCE: "tFileInputDelimited_1",
    	TARGET: "tUnite_1"
    }
  2. Enter the following script code to define a Merge connection between the second tFileInputDelimited component and the tUnite component.
    addConnection {
    	TYPE: "FLOW",
    	NAME: "row2",
    	LINESTYLE: 10,
    	SOURCE: "tFileInputDelimited_2",
    	TARGET: "tUnite_1"
    }
  3. Enter the following script code to define a Merge connection between the third tFileInputDelimited component and the tUnite component.
    addConnection {
    	TYPE: "FLOW",
    	NAME: "row3",
    	LINESTYLE: 10,
    	SOURCE: "tFileInputDelimited_3",
    	TARGET: "tUnite_1"
    }
  4. Enter the following script code to define a Main row connection between the tUnite component and the tAggregateRow component.
    addConnection {
    	TYPE: "FLOW",
    	NAME: "row4",
    	LINESTYLE: 0,
    	SOURCE: "tUnite_1",
    	TARGET: "tAggregateRow_1"
    }
  5. Enter the following script code to define a Main row connection between the tAggregateRow component and the tSortRow component.
    addConnection {
    	TYPE: "FLOW",
    	NAME: "row5",
    	LINESTYLE: 0,
    	SOURCE: "tAggregateRow_1",
    	TARGET: "tSortRow_1"
    }
  6. Enter the following script code to define a Main row connection between the tSortRow component and the tLogRow component.
    addConnection {
    	TYPE: "FLOW",
    	NAME: "row6",
    	LINESTYLE: 0,
    	SOURCE: "tSortRow_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!