tInformixCommit Standard properties
These properties are used to configure tInformixCommit running in the Standard Job framework.
The Standard tInformixCommit component belongs to the Databases family.
The component in this framework is available in all Talend products.
Basic settings
Database |
Select the desired database type from the list and click Apply. |
Component list |
If there is more than one connection in the Job, select tInformixConnection from the list. |
Close connection |
This check box is selected by default. It means that the database conenction will be closed once the commit has been made. Clear the check box to continue using the connection once the component has completed its task. Information noteWarning:
If you are using a Row > Main type connection to link tInformixCommit to your Job, your data will be committed row by row. If this is the case, do not select this check bx otherwise the conenction will be closed before the commit of your first row is finalized. |
Advanced settings
tStatCatcher Statistics |
Select this check box to collect the log data at a component level. |
Usage
Usage rule |
This component is generally used along with Informix components, particularly tInformixConnection and tInformixRollback. |
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 Dynamic schema and Creating a context group and define context variables in it. |