Skip to main content Skip to complementary content

Configuring the components


  1. In the tFileInputDelimited component Basic settings panel, fill the File name/Stream field with the relevant context variable we just defined: context.filename.
  2. Define the file schema manually (Built-in). It contains two columns defined as: key and value.
  3. Accept the defined schema to be propagated to the next component (tContextLoad).
  4. In the Dynamic settings view of the tContextLoad component, click the [+] button to add a row in the table, and fill the Code field with context.printOperations to use context variable printOperations we just defined. Note that the Print operations check box in the Basic settings view now becomes highlighted and unusable.
  5. Then double-click to open the tMysqlInput component Basic settings view.
  6. Fill the Host, Port, Database, Username, and Password fields with the relevant variables stored in the delimited files and defined in the Context view:, context.port, context.database, context.username, and context.password respectively in this example, and fill the Table Name field with the actual database table name to read data from, customers for both databases in this example.
  7. Then fill in the Schema information. If you stored the schema in the Repository Metadata, then you can retrieve it by selecting Repository and the relevant entry in the list.
    In this example, the schema of both database tables is made of four columns: id (INT, 2 characters long), firstName (VARCHAR, 15 characters long), lastName (VARCHAR, 15 characters long), and city (VARCHAR, 15 characters long).
  8. In the Query field, type in the SQL query to be executed on the DB table specified. In this example, simply click Guess Query to retrieve all the columns of the table, which will be displayed on the Run tab, through the tLogRow component.
  9. In the Basic settings view of the tLogRow component, select the Table option to display data records in the form of a table.

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!