Start JobExecuter ourselves
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-23-2011 06:41 PM
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 application (maybe after we start the engine - buildProcessEngine()). Is there any way to do this and any sample?
thanks,
Rue
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 application (maybe after we start the engine - buildProcessEngine()). Is there any way to do this and any sample?
thanks,
Rue
Labels:
- Labels:
-
Archive
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2011 12:26 AM
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
thanks,
Rue

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2011 02:52 AM
Hi,
Just add the following line to the activiti.cfg.xml or Spring configuration you are using:
<property name="jobExecutorActivate" value="true" />
Best regards,
Just add the following line to the activiti.cfg.xml or Spring configuration you are using:
<property name="jobExecutorActivate" value="true" />
Best regards,
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2011 03:33 AM
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();
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2011 09:21 AM
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
<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
