topic Start JobExecuter ourselves in Alfresco Archive

Start JobExecuter ourselves

ruedesilva — Tue, 23 Aug 2011 22:41:36 GMT

Hi,We have Activiti running inside our ear (enterprise application) deployed within Weblogic. And it is working very smoothly. However we do not intend to deploy the Activiti rest or Explorer applications (not allowed by network security). So we need to start the JobExecutor ourselves within our app

Re: Start JobExecuter ourselves

ruedesilva — Wed, 24 Aug 2011 04:26:05 GMT

This works with setting in activiti.cfg.xml. I had Tomcat also running so the Job executor there picked it up instead of the one in Weblogic.

thanks,
Rue

Re: Start JobExecuter ourselves

trademak — Wed, 24 Aug 2011 06:52:41 GMT

Hi,

Just add the following line to the activiti.cfg.xml or Spring configuration you are using:

<property name="jobExecutorActivate" value="true" />

Best regards,

Re: Start JobExecuter ourselves

frederikherema1 — Wed, 24 Aug 2011 07:33:00 GMT

One thing you could do is setting the jobExecutorActive to false and, when needed, call this (warning, using impl classes at your own risk):


((ProcessEngineImpl)processEngine).getProcessEngineConfiguration().getJobExecutor().start();

Re: Start JobExecuter ourselves

ruedesilva — Wed, 24 Aug 2011 13:21:44 GMT

Yes I was using

<property name="jobExecutorActivate" value="true" />

The problem was I had Tomcat also running with Weblogic and the JobExecutor in Tomcat fired first, so I was thinking the one in Weblogic was not working. Once I stopped Tomcat (which I do not need) the Weblogic JobExecutor worked.

But thanks for the tip on ((ProcessEngineImpl)processEngine).getProcessEngineConfiguration().getJobExecutor().start(); - This is really good to know.

- Rue