Working with Fact Table Loader Wizard

Right after the Next button, in the new wizard selection window, is pressed a new FTL wizard is launched. This case covers the wizard launched with an associated project.

New Graph Name Page

Figure 32.5. New Graph Name Page


In this page the user has to enter the graph name and can check or uncheck the checkbox which determines whether the wizard is able to use the project parameters.

Output Page

Figure 32.6. Output Page


After clicking on the Next button the wizard displays the Output Page. In this page the user can choose the directory in which the created graph will be saved.

File Selection Page

Figure 32.7. File Selection Page


In this window the user has to enter paths to the needed files.

  1. The first row contains the path to the file with the input data.

  2. The second row contains the path to the file with the metadata definition for the input file (.fmt file)

  3. The third row contains the path to the directory where the reject file with the data rejected by the reader will be stored. This is optional - if this row is empty no reject file will be created.

  4. The forth row contains the path to the directory where the reject file with the data rejected by the database writer will be stored, this also optional.

If the user clicks on the Browse button they can browse the project using the special dialog.

URL Dialog

Figure 32.8. URL Dialog


In this dialog the user can browse the project or the whole filesystem. The dialog returns the path to the file in parameter form, after the user clicks the OK button (if the project is associated).

Database Connection Page

Figure 32.9. Database Connection Page


The database connection page is displayed, after the user clicks on the Next button in the File selection page. In this page, the user provides the requested information needed to establish a connection to a database. Only one connection is created, so the fact table and the dimension tables of the data warehouse have to be in the same database.

Fact Table Selection Page

Figure 32.10. Fact Table Selection Page


The user has to select one table from the database which will be used as the fact table. Only one table can be selected. The created fact will be inserted into this table.

Dimension Table Selection Page

Figure 32.11. Dimension Table Selection Page


The user has to select one or more tables from the database in this window. These tables will be considered the dimension tables of the data warehouse.

Order Table Page

Figure 32.12. Order Table Page


In this window the user is able to see selected dimension tables and databes, select joiner which will be used for mapping and change the order of the dimension tables shown in this window. This is useful if the dimension key of one of the dimension tables is needed for searching within another dimension table.

Mapping Page

Figure 32.13. Mapping Page


The user maps the available fields onto fields of the dimension table using drag-and-drop. The user can also choose which field of the dimension table will be considered the dimension key and will be added to the fact. This can be done by setting the boolean value of the column Is dimension key to true. In this window the SQL condition can be also created. The user can create a where condition from which are the other DBJoin attributes generated. If the user creates where condition for the dimension table and he selected the ExtHashJoin or ExtMergeJoin, DBJoin will be used in a graph instead. A Mapping Page is shown for every dimension table.

Fact Mapping Page

Figure 32.14. Fact Mapping Page


The user maps the created fact to the fact table in this window. The editor uses an auto-rule which matches fields by name if the names are equal.

Summary Page

Figure 32.15. Summary Page


The last page of the wizard gives the user the information from the wizard. It also informs the user about new parameters which will be created in the CloverETL graph. The last three parameters are not created if the user did not enter a path for an output directory for rejected files. The user is also warned if DBJoin is used insted of user selected joiner.