Execute Talend
Infoveave Data Automation — Script Execution
Your Talend jobs work. Execute Talend runs them inside any Infoveave workflow.
Teams that built their data integration layer on Talend Open Studio or Talend Data Integration have investments in tested, production-grade ETL jobs. Migrating these jobs to a new platform takes time and introduces risk. Execute Talend preserves these investments by running compiled Talend JARs or scripts as native steps in Infoveave workflows — letting you orchestrate Talend alongside modern API calls, file ingestion, database operations, and email delivery in a single unified pipeline. Pass runtime arguments to make one Talend job handle multiple scenarios.
What Execute Talend does
Run Talend ETL jobs (JAR or script) as a step inside your Infoveave workflow. Integrate existing Talend pipelines into a modern orchestration platform without rebuilding them — pass arguments at runtime and capture Talend output for downstream activities.
When to use Execute Talend
- You have existing Talend ETL jobs (compiled as JAR files or shell scripts) that you want to incorporate into Infoveave workflows
- Your data integration pipeline uses Talend and you want to orchestrate it alongside other workflow activities
- You need to pass runtime arguments to a Talend job — such as source file paths, date parameters, or environment flags
- You are migrating from Talend as the primary orchestrator but want to preserve existing jobs during the transition period
When to avoid it
- You need to execute SQL queries — use Execute Query
- You need to run Node.js scripts — use Execute NodeJs
- You need to execute SSIS packages — use Execute SSIS
- You are building a new pipeline from scratch — use the native Infoveave transformation and ingestion activity library
Where it fits in your Infoveave automation
Execute Talend is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Execute Talend
Real scenarios where this transformation saves hours of manual work.
ERP Data Synchronization
A manufacturing team has a Talend job that synchronizes bill-of-materials data from the ERP system to the production planning database. Execute Talend runs this job as part of an Infoveave workflow triggered by a file arrival event, passing the source file path as a runtime argument. Downstream activities validate the loaded record counts and notify the planning team.
Multi-Source Data Consolidation
A Talend job reads from three different database sources, applies GAAP mapping, and loads consolidated entries into the financial data warehouse. Execute Talend runs this job nightly in an Infoveave workflow that also triggers post-load data quality checks and sends an audit summary to the finance controller.
Shipment Status Integration
A logistics team uses a Talend job to pull shipment status updates from a carrier API and update the internal order management system. Execute Talend runs the job hourly in an Infoveave workflow, with the carrier code passed as a runtime argument — the same workflow handles five different carriers using the same Talend job.
See Execute Talend in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
TalendJob_BOM_Sync.jar/home/infoveave/talend-jobs/home/infoveave/talend-jobsjava -jar TalendJob_BOM_Sync.jar--sourceFile "/data/bom_input.csv" --targetDB "prod-mssql"10 (seconds)Input Data
| (Talend JAR file or script in the configured Base Folder) |
Output Data
| (files or database state produced by the Talend job) |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
File
The Talend job file — typically a compiled JAR file (Talend Open Studio or Talend Data Integration export) or an executable shell script. Must be present in the configured Base Folder.
Base Folder
The root directory on the Infoveave server where the Talend job is installed. All file paths used by the Talend job are resolved relative to this directory.
Working Path
The directory from which the execution command is run. Typically matches Base Folder, but can be a subdirectory if the Talend job is structured with multiple modules or dependencies.
Command
The shell command to execute the Talend job — typically 'java -jar TalendJobName.jar'. Ensure Java is installed and accessible on the Infoveave server path.
Arguments
Optional command-line arguments passed to the Talend job at runtime. Used to inject dynamic values such as source file paths, target database connections, or date range parameters from the workflow context.
Refresh Interval
How frequently (in seconds) the activity checks the Talend job's progress while it is running. A shorter interval provides faster detection of completion or failure at the cost of slightly higher polling overhead.
Frequently asked questions
Everything you need to know about Execute Talend in Infoveave.
Also in Script Execution — and what runs before & after
Transformations in the same family as Execute Talend, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Execute Talend is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
