FAQ

Our FAQ is designed to give you fast, self-serve answers to the most common questions—so you can keep moving without opening a ticket. Well-designed FAQs reduce friction and improve the overall experience, while also guiding you to the right in-depth resources when needed. If something isn’t covered here, refer to our documentation or contact us, our support team is ready to help.

Frequently asked questions about EAC

Yes. EAC supports most Talend editions (commercial and open-source), including Talend DI and ESB (and Talaxie in your stack).

Export the job from Talend Studio, then upload the generated archive in EAC. From there, configure the task and schedule its execution.

No. EAC does not host an ESB runtime (e.g., Karaf). Talend ESB services run on a Karaf-based runtime you manage separately; EAC focuses on deployment/scheduling/monitoring around jobs and tasks.

Absolutely. Define contexts per environment, then override them in EAC (per job, per task, or even per execution) as needed.

On failures you can receive email notifications and enable Acknowledgement (Ack). When Ack is on, a failed task will not relaunch—manually or by the scheduler—until it’s acknowledged, preventing error loops.

EAC requires a Linux server, a web engine (Apache or NGINX), PHP + php-fpm, a database (MySQL, MariaDB, PostGreSQL or MSSQL Server) Java Open JDK 11+ and sufficient resources (RAM, CPU