Camunda BPM Platform without process engine components

Camunda 7 Topics Discussion & Questions
,
1

Hi,

We have several process applications deployed which share the same Camunda database. We are looking to spin up an additional deployment which offers the REST API and webapps for the shared context without participating in the process execution.

The docker-camunda-bpm-platform project looks promising. The problem is that the process engine automatically tries to pick up jobs from the database, and there doesn’t seem to be a good way to decouple the process engine components from the REST API and webapps. The camunda-engine jars cannot be removed from the container without classloader issues.

We were able to successfully prevent the process engine from picking up jobs by mounting a custom default.yml file in the container with camunda.bpm.job-execution.deployment-aware: true. However, we’re curious if we are overlooking a more elegant solution that disables/removes the process engine component entirely.

Any ideas?

Thanks in advance!

2

Hi @jmcmaha1

There is indeed a much better way of doing this to ensure the engine doesn’t pick up any jobs you can use

camunda.bpm.job-execution.enabled = false
1 Like
3

Hi,

With deployment aware, the job executor is still running, it just wont pickup any jobs…

A more elegant solution could be to disable the job executor altogether - see here for more detail.

regards

Rob

2 Likes
4

Thanks @Niall and @Webcyberrob! That’s exactly what we are looking for.

What threw me off is that camunda.bpm.job-execution.enabled = false is the default per the starter docs. It makes more sense with the context @Webcyberrob provided.