ETL integration process
To move data from the source to destination tables, you run the ETL transform files that you developed in either Tivoli® Directory Integrator Configuration Editor or Pentaho Spoon through the API.
There must be a transform for each fact table. Fact tables are populated only through ETL transforms and not through the TRIRIGA® application.
The TRIRIGA Application Platform includes a workflow that runs on a schedule to load the fact tables. The workflow calls a platform Custom workflow task, which retrieves the latest transform XML from the Content Manager and uses either the Tivoli Directory Integrator or the Kettle API to run the transform.
- Setup, which involves creating the Transform business object/form/navigation item and the workflow itself.
- Creating/Maintaining the Transform XML using an ETL development environment.
- Runtime, which is a scheduled workflow that executes a Custom workflow task to periodically run through the transforms to update the fact tables.
The following diagram summarizes these processes for Pentaho Spoon ETL transforms:
The following diagram summarizes these processes for Tivoli Directory Integrator Configuration Editor ETL transforms:
Data is pulled by ETL scripts from business objects, including the Financial Summary business object, into which financial summary records are imported from spreadsheets or by customer-designed interfaces with a financial system.