<?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 Running the same job conductor job multiple times simultaneously in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Running-the-same-job-conductor-job-multiple-times-simultaneously/m-p/2342854#M110673</link>
    <description>I've created a job that basically copies tables from one database to another, but set it up so I just pass in the source and target tables/databases dynamically via context variables.
&lt;BR /&gt;That part works great, and I can call the API to trigger the job run with the proper contexts. &amp;nbsp;However, the problem is that if I trigger that job via API call to TAC, I have to wait for it to end before I call it with a different table.
&lt;BR /&gt;Ideally, I would want the job to trigger, then detach from the TAC immediately so I can call the same job with different contexts variables and have it run simultaneously with the first call, instead of having to wait for the first call to finish.
&lt;BR /&gt;I tried setting up a wrapper job that calls the dynamic job via tRunJob with the child process option checked, but the wrapper will still wait for the subjob to complete before I am allowed to call it again.
&lt;BR /&gt;Is there any way I can accomplish this?</description>
    <pubDate>Fri, 15 Apr 2016 16:59:51 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2016-04-15T16:59:51Z</dc:date>
    <item>
      <title>Running the same job conductor job multiple times simultaneously</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Running-the-same-job-conductor-job-multiple-times-simultaneously/m-p/2342854#M110673</link>
      <description>I've created a job that basically copies tables from one database to another, but set it up so I just pass in the source and target tables/databases dynamically via context variables.
&lt;BR /&gt;That part works great, and I can call the API to trigger the job run with the proper contexts. &amp;nbsp;However, the problem is that if I trigger that job via API call to TAC, I have to wait for it to end before I call it with a different table.
&lt;BR /&gt;Ideally, I would want the job to trigger, then detach from the TAC immediately so I can call the same job with different contexts variables and have it run simultaneously with the first call, instead of having to wait for the first call to finish.
&lt;BR /&gt;I tried setting up a wrapper job that calls the dynamic job via tRunJob with the child process option checked, but the wrapper will still wait for the subjob to complete before I am allowed to call it again.
&lt;BR /&gt;Is there any way I can accomplish this?</description>
      <pubDate>Fri, 15 Apr 2016 16:59:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Running-the-same-job-conductor-job-multiple-times-simultaneously/m-p/2342854#M110673</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-04-15T16:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: Running the same job conductor job multiple times simultaneously</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Running-the-same-job-conductor-job-multiple-times-simultaneously/m-p/2342855#M110674</link>
      <description>Tasks in the TAC are generally singleton tasks. 
&lt;BR /&gt;If you want to let a job work out something in parallel you have to do this within the job itself. 
&lt;BR /&gt;For your use case you have to create a task which simply accepts the table name to transfer and starts independently another task which iterates through the table names and starts the actual transfers with a embedded job. This embedded job should be triggered with an iterate -&amp;gt; here you can activate parallel running.</description>
      <pubDate>Sun, 17 Apr 2016 21:09:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Running-the-same-job-conductor-job-multiple-times-simultaneously/m-p/2342855#M110674</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-04-17T21:09:17Z</dc:date>
    </item>
    <item>
      <title>Re: Running the same job conductor job multiple times simultaneously</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Running-the-same-job-conductor-job-multiple-times-simultaneously/m-p/2342856#M110675</link>
      <description>were you able to solve the puzzle?</description>
      <pubDate>Fri, 13 Apr 2018 04:00:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Running-the-same-job-conductor-job-multiple-times-simultaneously/m-p/2342856#M110675</guid>
      <dc:creator>KarthikGs</dc:creator>
      <dc:date>2018-04-13T04:00:49Z</dc:date>
    </item>
  </channel>
</rss>

