Build Data Integration workspace and task configurations with source, transform, and target data flows.
Last verified: May 2026
Build Data Integration workspace and task configurations with source, transform, and target data flow steps.
Required Fields
compartmentIdworkspaceIddisplayNametask.modelTypetask.dataFlow.sourcetask.dataFlow.targetOutput will appear here...Your team has 30 Excel files arriving in Object Storage daily that need ingestion into Autonomous Database for reporting. The builder generates a Data Integration task: connection to the Object Storage bucket, data flow with column mapping + type conversion + validation, target Autonomous DB table, scheduled hourly OR triggered by Object Storage events. End-to-end ingestion pipeline in 1 day vs the 1-week estimate writing custom Python ETL by hand.
Build Data Integration workspace and task configurations with source, transform, and target data flows. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
The builder constructs OCI Data Integration configurations: workspace resource (compartment, VCN/subnet for private networking), project (logical container for related tasks), connection assets (data sources: Autonomous DB, Object Storage, MySQL, etc.), data flow tasks (visual flow definitions with source → transforms → target), and execution schedule. Output is generated as oci data-integration commands and Terraform oci_dataintegration_workspace + oci_dataintegration_data_asset resources.
OCI Data Integration is the right answer for ETL/ELT between Oracle services (Object Storage → Autonomous Database, Object Storage → ADW). For non-Oracle data sources, consider Spark on Data Flow or third-party tools — Data Integration's connector ecosystem is strongest for Oracle databases.
Visual data flow designer accelerates ETL development dramatically vs writing SQL/Python by hand for typical transformations. Build the flow visually, generate the underlying SQL/PySpark, deploy. The trade-off: complex business logic still needs custom code, not visual flows.
Schedule integration tasks via the built-in scheduler OR via OCI Events for event-driven triggering (e.g., 'when a file lands in this Object Storage prefix, run the ingestion task'). Event-driven is dramatically more efficient than polling-based scheduling for irregular data arrivals.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.