jBPM 4 reminders

[gleenders]

Hi,

If I want to implement reminders in jBPM 4 what do have to set up to get this working?

It is not clear to me when the jBPM engine poll's the tasks to see if it has to send a reminder. So for the moment nothing happens with the reminders attached to my tasks (no reminders mails are send automatically).

How do I have to design my web application to achieve the best jBPM integration?

Regards,
Gert

[kukeltje]

I would think reminders are jobs, so if timers etc work task-reminders should to.

Designing your webapp is a totally different thing and not answered easily. Not that it is difficult to incorporate jBPM, but there are so many ways, also depending on frameworks you use (spring/seam, jsf/gwt, etc..etc...) So a more specific question would be handy

[gleenders]

Ronald,

Timers etc also don't work. My environment is a JSF (ADF Faces) Application who runs on a WebLogic 11g. Until now my app is more a 'quick and dirty' approach to see if I get everything working under this new environment. For the moment my process engine is in a singleton and is only called if needed.

But to get the jobs working I suppose I have to get the process engine running as service (According the dev guide chapter 15.4) and bound to JNDI. Since I have little experience in this area and since the dev guide explanation is very brief I could use some help here.

I remember from my jBPM 3 experience that the process engine was polling the DB all the time (on JBoss). My current jBPM 4 WebLogic app's process engine is not polling at all. So my first concern is to set it up as a service.

Regards,
Gert

[jbarrez]

Gert,

It is not necessary to run on a JEE server. You just need to enhance your configuration to include the job executor to make timers and reminders work:

http://docs.jboss.com/jbpm/v4.0/devguide/html_single/#jobexecutor

[kukeltje]

@Joram,

I would have expected having a job executor in your config to be the default.

[jbarrez]

@Ronald

The examples don't have a job executor since there the jobs are executed programmatically for readability. So we can't add it straight away to the default config since it will make the examples do unexpected things ...

But I do agree that the configuration needs some documentation, seeing how many people forget to include the job executor....

[gleenders]

That would saved (a lot of) time for me :-)

[kukeltje]

I agree that it should not be included for the examples. But the default deployment of the engine should (the one deployed when deploying the console) Or does that have it (did not check, sorry)

[jbarrez]

Yep, the console installation does have the job executor installed.

[kukeltje]

Gert,

If you get reminders to work I'd like you to test if the template for the mail that is used is really the reminder template. I suspect a bug, looking at the source of the jPDL parser that the task-notification template is used. At least if you do not configure the template attribute and xsd workaround that I suggested in the task-notification issue.

If you 'hurry' with this, fixes might make it into 4.1 (although there officially already is a jira freeze)

[rujimethut]

I have been using jbpm4.1-Snapshot which was built from the source, It is still a problem that the task reminder is using task-notification email template, I have to set the template attribute to point to the task-reminder template and I have to turn-off xml validation to get it works

[gleenders]

@Ronald: Indeed as Rujimethut already said, the bug is still there.

[kukeltje]

Thanks for reporting. I think I can get this fixed in 4.1 IF you guys file a jira issue for the task-notification template thing on the reminder.

[kukeltje]

https://jira.jboss.org/jira/browse/JBPM-2466

[kukeltje]

<duplicate post>Can someone other then me check if it works now against svn-trunk. So removing of the xsd should not be needed as is specifying of a template on reminder to get the right template being used.</duplicate post>