By default, all Integration Manager jobs run in parallel, up to the concurrency, which is the number of engines or nodes that you have licensed. Most of the time, different kinds of jobs can run concurrently without issue.

Sometimes, however, the same job running concurrently may have undesirable outcome, meaning the integration may not be idempotent.

Some examples:

In these scenarios, you can protect your data without complex integration logic by using a job execution mutex.

Strictly speaking, a mutex is a locking mechanism used to synchronize access to a resource. Only one task (which can be a thread or process based on OS abstraction) can acquire the mutex. It means ownership is associated with a mutex, and only the owner can release the lock (mutex).

You may configure a job execution mutex in Integration Server for any configuration. In essence, this prevents running multiple jobs for the same configuration at the same time.

To enable the mutex for a job configuration, you simply set the “blocking” property to true (blocking is false by default).

You can accomplish this using a simple API PATCH method:

Your Integration Manager Server Admin must have the ZooKeeper configuration enabled and connected. For more information, see Install and Configure Apache ZooKeeper (Windows).