<?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 Re: dynamic config tMomOutput component in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/dynamic-config-tMomOutput-component/m-p/2275000#M51512</link>
    <description>Hi Xiaodong, 
&lt;BR /&gt;If you have access to the ESB components, the best way to do this is with cJMS and by manipulating the header CamelJMSDestinationName header (see doc link below). 
&lt;BR /&gt;If you must use a DI job, I think you could spawn a new job (tRunJob?) and configure the context property as needed so it's effective on initialization of that job. Of course, this is not efficient. So Mediation is a much better solution. If you still want to see dynamic queue/topic resolution in tMomOutput, I suggest creating a new JIRA and mark it as a work item (link below). 
&lt;BR /&gt; 
&lt;A href="http://camel.apache.org/jms.html" rel="nofollow noopener noreferrer"&gt;http://camel.apache.org/jms.html&lt;/A&gt; 
&lt;BR /&gt; 
&lt;A href="https://jira.talendforge.org/secure/Dashboard.jspa" rel="nofollow noopener noreferrer"&gt;https://jira.talendforge.org/secure/Dashboard.jspa&lt;/A&gt; 
&lt;BR /&gt;Best Regards, 
&lt;BR /&gt;Ben</description>
    <pubDate>Fri, 27 Dec 2013 18:53:48 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2013-12-27T18:53:48Z</dc:date>
    <item>
      <title>dynamic config tMomOutput component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/dynamic-config-tMomOutput-component/m-p/2274999#M51511</link>
      <description>How to dynamically configure the tMomOutput for ActiveMQ with the "To" queue name passed in from the request. 
&lt;BR /&gt;More specifically, I have a job listen to a request using the tMomInput component. the response queue name is embedded in the request. My job will decode the response queue name, save it to a context variable "replyQueueName", then use it to configure the tMomOutput component (the value for the field "To" of the tMomOutput component is: context.replyQueueName). 
&lt;BR /&gt;This is not working, it seems the tMomOutput component is configured before the job actually starts, so it takes whatever the initial value of the context variable, not the dynamic value I assigned after decoding the request message. 
&lt;BR /&gt;Could someone tell me how to get around this? 
&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 26 Dec 2013 14:07:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/dynamic-config-tMomOutput-component/m-p/2274999#M51511</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-12-26T14:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: dynamic config tMomOutput component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/dynamic-config-tMomOutput-component/m-p/2275000#M51512</link>
      <description>Hi Xiaodong, 
&lt;BR /&gt;If you have access to the ESB components, the best way to do this is with cJMS and by manipulating the header CamelJMSDestinationName header (see doc link below). 
&lt;BR /&gt;If you must use a DI job, I think you could spawn a new job (tRunJob?) and configure the context property as needed so it's effective on initialization of that job. Of course, this is not efficient. So Mediation is a much better solution. If you still want to see dynamic queue/topic resolution in tMomOutput, I suggest creating a new JIRA and mark it as a work item (link below). 
&lt;BR /&gt; 
&lt;A href="http://camel.apache.org/jms.html" rel="nofollow noopener noreferrer"&gt;http://camel.apache.org/jms.html&lt;/A&gt; 
&lt;BR /&gt; 
&lt;A href="https://jira.talendforge.org/secure/Dashboard.jspa" rel="nofollow noopener noreferrer"&gt;https://jira.talendforge.org/secure/Dashboard.jspa&lt;/A&gt; 
&lt;BR /&gt;Best Regards, 
&lt;BR /&gt;Ben</description>
      <pubDate>Fri, 27 Dec 2013 18:53:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/dynamic-config-tMomOutput-component/m-p/2275000#M51512</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-12-27T18:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: dynamic config tMomOutput component</title>
      <link>https://community.qlik.com/t5/Talend-Studio/dynamic-config-tMomOutput-component/m-p/2275001#M51513</link>
      <description>&lt;P&gt;As the queue initialization is done before tMomOutput we have to explicitly add the following line to update the queue in case if we need to pass the message the dynamic queues. The following line has to be added one step before the to&amp;nbsp;tMomOutput. The tMomOutput&amp;nbsp; To field can be set with the dummy queue name.&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;BR /&gt;javax.jms.Destination des_tMomOutput_1;&lt;BR /&gt;des_tMomOutput_1 = session_tMomOutput_1.createQueue("DestinationQueueName");&lt;/P&gt; 
&lt;P&gt;producer_tMomOutput_1 = session_tMomOutput_1.createProducer(des_tMomOutput_1);&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&lt;A href="https://community.qlik.com/s/feed/0D73p000004kiybCAA#M115395" target="_blank"&gt;https://community.talend.com/t5/Design-and-Development/Dynamic-destination-in-tMomOutput/m-p/210154#M115395&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2019 17:12:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/dynamic-config-tMomOutput-component/m-p/2275001#M51513</guid>
      <dc:creator>Jeeva</dc:creator>
      <dc:date>2019-12-19T17:12:10Z</dc:date>
    </item>
  </channel>
</rss>

