Jobexecutor and its awareness of a jobs origin

[sazzadul]

Hi,

      Is it possible to make the JobExecutor be aware of where a job actually originates from ? Given the scenario I have described in my diagram, I would rather have a jobexecutor(webapp) for each module in that way I will gain a lot of freedom in terms of development, debugging, deployment etc etc. If the jobExecutor knew where a job came from it would simply skip the job and the second jobexecutor potetially would process the job which had the correct execution code.

      Its important for us to have a shared db so there you go.

      Please let me know if you would consider this feature in any future release.

      Thanks

/Sazzadul

[frederikherema1]

There is currently no way of knowing from which process-engine a job came, other than the process-instance and execution-id. There are no plans of introducing this kind of mechanism. You could alter the JobHandlers and add the module-name to the job-configuration for example, on top of the existing values that go in there.

[soaguy]

Hi,
   I wanted to followup on this to see if this is still the same. Can the jobExecutor be configured to process the jobs only on the process engine that created it?

Thanks
{Clement}

[jbarrez]

No, this has not changed since the last post. That would be a customization to the job executor.