<?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 Custom job executor for Task Migration in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/custom-job-executor-for-task-migration/m-p/161435#M115366</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello Guys,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There has been some discussion going on to customize job executor to handle clusterability on more flexibility level. I have a similar requirement to be used in my project. I am working on task migration in a distributed workflow system based on ceratin predefined conditions. I am using asynchronous continuation as a way to migrate tasks from one machine to another. Since the job executor is designed the clusterabilty in mind, there isn't a way to tell which job to run on what machine.I have done a some digging into the job executor source code and might have come up with a solution which suits my use case.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The job executor checks the database periodically for new jobs and allocates a thread from the pool, but I was thinking instead of accessing the database why not have dedicated queue for each job executor and jobs which are in that queue are picked up by corresponding job executor. In this way only certain type of jobs run on that machine. I was also thinking of a controller at&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;the manager level which validates the conditions and schedule jobs on these queues.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would appreciate any suggestions on this approach.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Nov 2013 16:44:28 GMT</pubDate>
    <dc:creator>asshetye</dc:creator>
    <dc:date>2013-11-18T16:44:28Z</dc:date>
    <item>
      <title>Custom job executor for Task Migration</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/custom-job-executor-for-task-migration/m-p/161435#M115366</link>
      <description>Hello Guys,There has been some discussion going on to customize job executor to handle clusterability on more flexibility level. I have a similar requirement to be used in my project. I am working on task migration in a distributed workflow system based on ceratin predefined conditions. I am using a</description>
      <pubDate>Mon, 18 Nov 2013 16:44:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/custom-job-executor-for-task-migration/m-p/161435#M115366</guid>
      <dc:creator>asshetye</dc:creator>
      <dc:date>2013-11-18T16:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: Custom job executor for Task Migration</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/custom-job-executor-for-task-migration/m-p/161436#M115367</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;I am in the process of looking into different queues but its a good step to think about existing db queue and what do you mean by adding "column to store the jobExecutor's address" adding a Table in the database ? or column in execution or job table ? . This mean we might add chnges to schema. I am trying to come up with an approach without modifing the db .&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Nov 2013 19:20:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/custom-job-executor-for-task-migration/m-p/161436#M115367</guid>
      <dc:creator>asshetye</dc:creator>
      <dc:date>2013-11-19T19:20:41Z</dc:date>
    </item>
  </channel>
</rss>

