# tRouteOutput

Sends messages from a Data Integration Job to a Mediation Route.

## tRouteOutput Standard properties

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

The Standard tRouteOutput component belongs to the ESB family.

*This component is relevant only when used with one of the Talend solutions with ESB, as it should be used with the Service Repository node and the Data Service creation related wizard(s).*

## Basic settings

| Properties | Description |
| --- | --- |
| Output Schema | <ul> <li> <p>A schema is a row description. It defines the number of fields            (columns) to be processed and passed on to the next component. When you create a Spark            Job, avoid the reserved word <kbd>line</kbd> when naming the            fields.</p> <p>Click <span>Edit        schema</span> to make changes to the schema. If the current schema is of the <span>Repository</span> type, three options are available:</p> <ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion.</p> <p>If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> <p>Click <span>Sync columns</span> to retrieve								the schema from the previous component connected in the Job.</p> </li> <li> <p> <span>Built-in</span>: No property data stored								centrally. </p> </li> <li> <p> <span>Repository</span>: Select the Repository								file where Properties are stored. </p> </li> </ul> |
| Camel | Enter the message parameters corresponding to the columns you<br>defined in the schema dialog box via the Edit<br>schema button. |
| Type | Select between:<br><br><br>Body: Used to set the body of a<br>Route, equals the code<br>exchange.getOut().setBody(...).<br><br><br>Property: Used to set the<br>property of a Route, equals the code<br>exchange.setProperty(name, value).<br><br><br>System: Used to set the system<br>property, equals the code System.setProperty(name,<br>value).<br><br><br>Header: Used the set the output<br>header, equals the code exchange.getOut().setHeader(name,<br>value). |
| Name | This column is used to set the name for the parameter when its<br>type is either Property, System or Header. This column is ignored when the type is<br>Body. |

## Advanced settings

| Properties | Description |
| --- | --- |
| tStatCatcher Statistics | Select this check box to gather the Job processing metadata at a<br>Job level as well as at each component level. |

## Global Variables

| Variables | Description |
| --- | --- |
| Global Variables | ERROR\_MESSAGE: the error message generated by the<br>component when an error occurs. This is an After variable and it returns a string. This<br>variable functions only if the Die on error checkbox is<br>cleared, if the component has this checkbox.<br><br>A Flow variable functions during the execution of a component<br>while an After variable functions after the execution of the component.<br><br>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<br>it.<br><br>For more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component can be used as the end component and thus<br>requires an input component. It is mandatory that a tRouteInput component is used in the Data Integration Job to be<br>called by a Route using the cTalendJob<br>component. The reason for it is that this will prevent the referenced Job from<br>starting automatically when deployed in *Talend Runtime*. Instead it will only start when it gets called by the Route.<br><br>For more information about how to use the cTalendJob component, see [cTalendJob](https://help.qlik.com/talend/r/en-US/8.0/route). |
| Limitation | The Job using a tRouteOutput<br>must be launched only within a Route using the cTalendJob component. |

**Related concepts**

* [Exchanging messages between a Job and a Route](https://help.qlik.com/talend/en-US/components/8.0/route/trouteoutput-trouteinput-tlogrow-treplace-exchanging-messages-between-job-and-route-standard-component-esb-this)