jobExecution false shared engine

Camunda 7 Topics Discussion & Questions
1

Hello

I use shared engine with Camunda. Is it possible to turn off the job executor and start if my application was loaded?
I know that the embedded version I can use the setJobExecutorActivate(true) to activate. But the Camunda starts if I run the Tomcat and I am not able to start later.

The reason why I would like to start later that my beans should be loaded first and after if every custom bean were loaded I would like to start the job execution.

Thanks in advance: Gábor

2

Hi @Gabor_Sandor,

Normally the JobExecutor should only execute jobs, when there is a process application registered for the job. This is managed by the property jobExecutorDeploymentAware = true. The registration of the process application normally happens after all beans are initialized.

Did you set jobExecutorDeploymentAware to false?

Could you please elaborate how your application startup works?
Do you use Spring or CDI/EJB? What kind of process application do you use - ServletProcessApplication, SpringProcessApplication, SpringServletProcessApplication?

It is possible to disable the jobExecutor by setting the property jobExecutorActivate to false in the bpm-platform.xml inside the process-engine element, see the documentation.
To enable the JobExecutor, you could then call something along the lines of:

ProcessEngine engine = BpmPlatform.getDefaultProcessEngine();
ProcessEngineConfigurationImpl peci = (ProcessEngineConfigurationImpl) engine.getProcessEngineConfiguration();
JobExecutor jobExecutor = peci.getJobExecutor()
jobExecutor.start()

I wrote the code out of memory, so it could be that it won’t work :wink:

Cheers,
Christian