topic Re: ProcessEngine configuration help. in Alfresco Archive

ProcessEngine configuration help.

fionn — Thu, 22 Jan 2015 14:24:04 GMT

Hi, I'm trying to setup the mail server for activiti explorer. The documentation seems to be lacking slightly in this area.But googling around I found out that spring beans need to be setup to configure the mail server in the processEngineConfiguration bean. So I found this bean, commented out, in t

Re: ProcessEngine configuration help.

fionn — Fri, 23 Jan 2015 15:01:34 GMT

Figured it out. It turns out that in the newer versions the process engine is setup using the ActivitiEngineConfiguraion.java file in the activiti explorer web app. In here you can set the mail server and any other process engine settings.

Re: ProcessEngine configuration help.

jbarrez — Mon, 09 Feb 2015 12:28:21 GMT

That is correct

Re: ProcessEngine configuration help.

wsalembi — Tue, 10 Feb 2015 13:14:10 GMT

It would be a lot easier if all mail properties were defined in engine.properties (or mail.properties) instead of overriding the processEngineConfiguration bean.

The new java config is cumbersome.
- Developers who want to wire their own configuration java class must package it in org.activiti.rest.conf or org.activiti.engine.conf to be detected by the component scan.
- Why does activity-explorer disable the job executor by default? (engine.activate.jobexecutor=false) If you override it in activiti-custom-context.xml, it is by default set to true.
- The registration of custom form types is a little heavy too. You must override the entire processEngineConfiguration bean to add a new custom type and additionally in explorer you need to customize the activiti-ui-context.xml too. It would be a lot easier if org.activiti.engine.form.AbstractFormType provides a handle method to retrieve the renderer instead.

Re: ProcessEngine configuration help.

jbarrez — Wed, 18 Feb 2015 12:00:09 GMT

> The new java config is cumbersome.

Thats why we introduced the xml fallback.

> Why does activity-explorer disable the job executor by default? (engine.activate.jobexecutor=false) If you override it in activiti-custom->
> context.xml, it is by default set to true.

Cause, if you search a bit on this forum, it confused a lot of starters.

> The registration of custom form types is a little heavy too.

I agree. I don't like it either, but it would mean a big refactoring to switch it out now.

Re: ProcessEngine configuration help.

filprayer — Mon, 22 Jun 2015 10:09:09 GMT

Hi,

I'm a new member of this forum and I've encountered the same problem, especially in adding a new custom form type.

I tried to follow the steps of this guide (http://www.jorambarrez.be/blog/2013/03/13/creating-a-new-form-property-in-activiti/) but I found out that when I add a new form type in the file "activiti-custom-context.xml" uncommenting it, explorer web app fails to run.

So my questions are: does this problem still exist or it has been fixed? Is it necessary to modify the ActivitiEngineConfiguraion.java file in order to add a new form type?

Thanks!

Re: ProcessEngine configuration help.

jbarrez — Tue, 30 Jun 2015 19:01:23 GMT

No, it should work as advertised, but i need more than 'explorer web app fails to run.'. Example xml and stacktraces are always helpful.

Re: ProcessEngine configuration help.

filprayer — Tue, 12 Jan 2016 14:11:18 GMT

Hi,

with the last version of Activiti (5.19), this problem has been resolved. Sorry if I didn't reply to previous messagges.

Thank you.

Regards,
Filippo.

Re: ProcessEngine configuration help.

javaman1 — Wed, 09 Mar 2016 05:24:39 GMT

Hi,

Got a question related to activiti-custom-context.xml in activiti-explorer.
I am using mysql for my db properties.
I am running a process with a User Task.

Scenario 1: I use the default activiti-custom-context.xml that came with activiti-explorer, which contains beans that are commented out
1. I populate the form and start the process in the processes tab
2. I go to the Tasks tab and immediately see the task in the Queued tasks under Management

Scenario 2: I uncomment the commented-out beans settings in activiti-custom-context.xml
1. I populate the form and start the process in the processes tab
2. I go to the Tasks tab but the task does not appear in the queue (even logging out and relogging-in doesn't work)
3. After I restarted tomcat, and re-logged in, only then did the task appeared in the queue

What configuration should I change in the default activiti-custom-context.xml to achieve a similar behavior as Scenario 1?

Re: ProcessEngine configuration help.

javaman1 — Wed, 09 Mar 2016 05:40:07 GMT

P.S.: I am using activiti-5.19.0.2