<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Jobexecutor and its awareness of a jobs origin in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114494#M80676</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 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. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Its important for us to have a shared db so there you go.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Please let me know if you would consider this feature in any future release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;/Sazzadul&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jul 2012 14:55:25 GMT</pubDate>
    <dc:creator>sazzadul</dc:creator>
    <dc:date>2012-07-05T14:55:25Z</dc:date>
    <item>
      <title>Jobexecutor and its awareness of a jobs origin</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114494#M80676</link>
      <description>Hi,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 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</description>
      <pubDate>Thu, 05 Jul 2012 14:55:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114494#M80676</guid>
      <dc:creator>sazzadul</dc:creator>
      <dc:date>2012-07-05T14:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: Jobexecutor and its awareness of a jobs origin</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114495#M80677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2012 06:35:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114495#M80677</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2012-07-06T06:35:11Z</dc:date>
    </item>
    <item>
      <title>Re: Jobexecutor and its awareness of a jobs origin</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114496#M80678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; 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? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;{Clement}&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Apr 2016 13:40:34 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114496#M80678</guid>
      <dc:creator>soaguy</dc:creator>
      <dc:date>2016-04-26T13:40:34Z</dc:date>
    </item>
    <item>
      <title>Re: Jobexecutor and its awareness of a jobs origin</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114497#M80679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;No, this has not changed since the last post. That would be a customization to the job executor.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 11:30:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/jobexecutor-and-its-awareness-of-a-jobs-origin/m-p/114497#M80679</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-05-03T11:30:17Z</dc:date>
    </item>
  </channel>
</rss>

