ETL maps
Your implementation of a DataConnect integration determines how you move your data into the staging tables, either through an ETL tool or direct SQL statements. Regardless of how you move your data from the external source into the staging tables, the data must be populated in the external source before you run the mapping.
If you use an ETL tool, the integration drives which ETL maps you must develop to move data from the external source to the staging tables. Use a tool to define an ETL mapping between the external source and the staging tables. One such tool is the Spoon tool from Pentaho Kettle. Otherwise, you can use another tool of your choice.
When the
mapping runs, it must accomplish the following tasks:
- Create a unique job number.
- Create an entry in the DataConnect Job Control table (DC_JOB), setting the state to New.
- Populate the staging tables for the business objects, including any child staging tables. The entries include the job number, one or more correlation numbers, and the action. The path is required on Update actions where no keys are defined and optional for Insert actions.
- Optional: Update the entry in the DataConnect Job Control table (DC_JOB), setting the state to Ready. This update can be set manually through the Administrator Console by selecting the DataConnect managed object, the DataConnect job, and then the Ready Job action.