tEXARollback Standard properties
These properties are used to configure tEXARollback running in the Standard Job framework.
The Standard tEXARollback component belongs to the Databases family.
The component in this framework is available in all Talend products.
Basic settings
Database |
Select a type of database from the list and click Apply. |
Component List |
Select the tEXAConnection component for which you want the rollback action to be performed. |
Close Connection |
This check box is selected by default and it allows you to close the database connection once the rollback is done. Clear this check box to continue to use the selected connection after the component has performed its task. |
Advanced settings
tStatCatcher Statistics |
Select this check box to gather the Job processing metadata at the 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 |
This component is more commonly used with other Exasol components, especially with the tEXAConnection and tEXACommit components. |
Dynamic settings |
Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your database connection dynamically from multiple connections planned in your Job. This feature is useful when you need to access database tables having the same data structure but in different databases, especially when you are working in an environment where you cannot change your Job settings, for example, when your Job has to be deployed and executed independent of Talend Studio. Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable. For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Talend Studio User Guide. |