nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Start JobExecuter ourselves

ruedesilva

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

Find more posts tagged with

Comments

ruedesilva

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

trademak

Hi,

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

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

Best regards,

frederikherema1

One thing you could do is setting the jobExecutorActive to false and, when needed, call this (warning, using impl classes at your own risk):
<br>((ProcessEngineImpl)processEngine).getProcessEngineConfiguration().getJobExecutor().start();<br>

ruedesilva

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