<?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: Qlik Sense APIs capabilities in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1566912#M10308</link>
    <description>&lt;P&gt;It is a long debate when it comes to manage real-time data, and data coming from a MOM have to be considered real time some extent. In 20+ years experience across different areas, gave me the belief the word "Real time" is more related to the user's feeling that a strict scientific definition. I met people happy to call a 30 seconds delay system "real time or near real time".&lt;/P&gt;
&lt;P&gt;Qlik Sense is&amp;nbsp;definitely not a stream data analysis, meaning that there is a time to digest the incoming data different from zero. The less the time Qlik takes to read data, the more often it can be updated. I haven't see reload time under 30 seconds, so far.&lt;/P&gt;
&lt;P&gt;Said that, the best way I can advice to address your needs is:&lt;/P&gt;
&lt;P&gt;1) To buffer all messages to a persistent system (e.g. Database)&lt;/P&gt;
&lt;P&gt;2) Create a task to read these data from the persistent system&lt;/P&gt;
&lt;P&gt;3.a) You can trigger the reload task via API (e.g. BizTalk trigger the task each &amp;lt;n&amp;gt; messages)&lt;/P&gt;
&lt;P&gt;3.b) You can schedule the reload task to run each &amp;lt;n&amp;gt; seconds&lt;/P&gt;
&lt;P&gt;Hope this help&lt;/P&gt;</description>
    <pubDate>Tue, 09 Apr 2019 12:18:16 GMT</pubDate>
    <dc:creator>Vincenzo_Esposito</dc:creator>
    <dc:date>2019-04-09T12:18:16Z</dc:date>
    <item>
      <title>Qlik Sense APIs capabilities</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1566233#M10302</link>
      <description>&lt;P&gt;Use Case Example:&lt;/P&gt;&lt;P&gt;1) Messages in the form of XML/JSON originate from Microsoft BizTalk Server based on communication (B2B) with a Purchase Order system. The XML/JSON message contains the data passed by the PO system about a new or an existing PO. Messages are generated whenever a PO request comes in.&lt;/P&gt;&lt;P&gt;2) Qlik sense then needs to load the data in the XML/JSON messages into an existing Qlik Sense application.&lt;/P&gt;&lt;P&gt;PUSH from Biztalk: Is there a way for BizTalk hub to call a Qlik API&amp;nbsp; that can take the data in the XML message as an input and load the new data into a Qlik sense application thru an incremental process?&lt;/P&gt;&lt;P&gt;PULL from Qlik Sense: The XML messages are not being persisted in Biz Talk so I am not sure if a rest API connector mechanism can help in this case where reload tasks from QMC can be triggered via QRS API.&lt;/P&gt;&lt;P&gt;Any thoughts around this is much appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2019 08:00:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1566233#M10302</guid>
      <dc:creator>swudali4786</dc:creator>
      <dc:date>2019-04-08T08:00:51Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense APIs capabilities</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1566912#M10308</link>
      <description>&lt;P&gt;It is a long debate when it comes to manage real-time data, and data coming from a MOM have to be considered real time some extent. In 20+ years experience across different areas, gave me the belief the word "Real time" is more related to the user's feeling that a strict scientific definition. I met people happy to call a 30 seconds delay system "real time or near real time".&lt;/P&gt;
&lt;P&gt;Qlik Sense is&amp;nbsp;definitely not a stream data analysis, meaning that there is a time to digest the incoming data different from zero. The less the time Qlik takes to read data, the more often it can be updated. I haven't see reload time under 30 seconds, so far.&lt;/P&gt;
&lt;P&gt;Said that, the best way I can advice to address your needs is:&lt;/P&gt;
&lt;P&gt;1) To buffer all messages to a persistent system (e.g. Database)&lt;/P&gt;
&lt;P&gt;2) Create a task to read these data from the persistent system&lt;/P&gt;
&lt;P&gt;3.a) You can trigger the reload task via API (e.g. BizTalk trigger the task each &amp;lt;n&amp;gt; messages)&lt;/P&gt;
&lt;P&gt;3.b) You can schedule the reload task to run each &amp;lt;n&amp;gt; seconds&lt;/P&gt;
&lt;P&gt;Hope this help&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2019 12:18:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1566912#M10308</guid>
      <dc:creator>Vincenzo_Esposito</dc:creator>
      <dc:date>2019-04-09T12:18:16Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense APIs capabilities</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1567277#M10314</link>
      <description>&lt;P&gt;Hi Ves,&lt;/P&gt;&lt;P&gt;Thanks for your prompt response. This use case is for a "near real time" scenario.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Having BizTalk persist to a database is a great idea. Another option that I could think of was to&lt;/P&gt;&lt;P&gt;i) Have BizTalk&amp;nbsp; team write all outgoing messages (XML files) to a folder on some disk. (set up an archival strategy to make sure folder size doesn't increase to unmanageable sizes as time progresses).&lt;/P&gt;&lt;P&gt;ii) Set up a general web connector that connects to this folder structure and the XML files.&lt;/P&gt;&lt;P&gt;iii) In QMC set up reload data and app tasks.&lt;/P&gt;&lt;P&gt;iv) Have BizTalk trigger the reload thru Capability API&amp;nbsp; whenever a new XML file arrives into the folder(Or is there any other API to trigger a reload data and app that is more appropriate?)&lt;/P&gt;&lt;P&gt;for item ii) is there any other option apart from Qlik general web connector that can help connect to the folder containing XML files?&lt;/P&gt;&lt;P&gt;Also I believe volume of messages is a critical factor in the triggering mechanism -&amp;nbsp; if the first message arrives into the folder and BizTalk triggers a reload thru an API and the reload task is still running. Meanwhile if another message arrives will the reloads be queued in QMC? Sorry if this sounds like a dumb question but I have not run into a similar situation before and want to evaluate what options should i be considering to arrive at an optimal solution.&lt;/P&gt;&lt;P&gt;Thanks in advance for your help!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Srik&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2019 02:50:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1567277#M10314</guid>
      <dc:creator>swudali4786</dc:creator>
      <dc:date>2019-04-10T02:50:21Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense APIs capabilities</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1567439#M10318</link>
      <description>&lt;P&gt;That was my point when I wrote Qlik Sense is not a data stream analizer. You cannot trigger the reload task on the message incoming, because it fails if a reload is already in progress. Hence my suggestion to accumulate the messages on a persistent layer and consume each 30sec. or 1 min.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2019 08:51:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-APIs-capabilities/m-p/1567439#M10318</guid>
      <dc:creator>Vincenzo_Esposito</dc:creator>
      <dc:date>2019-04-10T08:51:36Z</dc:date>
    </item>
  </channel>
</rss>

