<?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 How do we enable our SaaS application to be QV accessable in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/How-do-we-enable-our-SaaS-application-to-be-QV-accessable/m-p/296895#M110140</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hello - our application is a hosted SaaS application.&amp;nbsp; We have both transactional and OLAP storage in MS SQL.&amp;nbsp; QV can easily connect to our OLAP data connector but we can't allow access to the transactional DB via ODBC or OLEDB for security reasons.&amp;nbsp; Presently we support .Net Remoting connections to our server via a middle-tier service, that service is the only service permitted to connect to SQL. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a Server API product for QV that would allow us to open a QV data-port for QV customers that would allow us to make certain stored-procedures/views available for data-access?&amp;nbsp; We have a new customer prospect who loves the QV product, but we have had to say 'no' to their request to allow direct connect to the SQL database via OLEDB or ODBC.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Aug 2011 12:35:44 GMT</pubDate>
    <dc:creator />
    <dc:date>2011-08-24T12:35:44Z</dc:date>
    <item>
      <title>How do we enable our SaaS application to be QV accessable</title>
      <link>https://community.qlik.com/t5/QlikView/How-do-we-enable-our-SaaS-application-to-be-QV-accessable/m-p/296895#M110140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hello - our application is a hosted SaaS application.&amp;nbsp; We have both transactional and OLAP storage in MS SQL.&amp;nbsp; QV can easily connect to our OLAP data connector but we can't allow access to the transactional DB via ODBC or OLEDB for security reasons.&amp;nbsp; Presently we support .Net Remoting connections to our server via a middle-tier service, that service is the only service permitted to connect to SQL. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a Server API product for QV that would allow us to open a QV data-port for QV customers that would allow us to make certain stored-procedures/views available for data-access?&amp;nbsp; We have a new customer prospect who loves the QV product, but we have had to say 'no' to their request to allow direct connect to the SQL database via OLEDB or ODBC.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2011 12:35:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/How-do-we-enable-our-SaaS-application-to-be-QV-accessable/m-p/296895#M110140</guid>
      <dc:creator />
      <dc:date>2011-08-24T12:35:44Z</dc:date>
    </item>
  </channel>
</rss>

