ETL integration process

To move data from the source to destination tables, you run the ETL transform files that you developed in 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 Maximo® Real Estate and Facilities application.

Maximo Real Estate and Facilities 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 the Kettle API to run the transform.

The scheduled ETL process is available with the appropriate Maximo Real Estate and Facilities license entitlement.

Draft comment: Paraic.ORaghallaigh@ibm.com
Find equivalent license information.
The scheduled ETL process is available with the following Maximo Real Estate and Facilities licenses:
  • Any Workplace Performance Management license
  • A Real Estate Environmental Sustainability Manager license
  • A Real Estate Environmental Sustainability Impact Manager license
  • A Workplace Reservation Manager license
  • A Workplace Reservation Manager for Small Installations license
Process Overview
There are three main processes:
  • 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.
Restriction: Additional entitlement might be required for the set up and maintenance processes, such as a license for the triJobItem Module. The licenses needed to create or edit the ETLs differ from the licenses needed for the runtime process.
Draft comment: Paraic.ORaghallaigh@ibm.com
check this info.

The following diagram summarizes these processes for Pentaho Spoon ETL transforms:

Process flow when using Pentaho Kettle Spoon

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.