Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have a lot of data in a database which I want different qlikview implementations to be able to consume.
The data in the MS-SQL database is for several customers and I do not want to let them in directly in the db. I want to have an API where the customer can get their data over SSL and with password protection.
At the same time I want it to be as easy as it can be for the customer to consume the data within their qlikview program.
What would be the best solution for us to build so that the custoemr easily can consume our data from our database and where the data is encrypted and protected?
/Andreas
Hi,
Have a look at the security in QlikView document in below link.
http://community.qlik.com/docs/DOC-1853
Hope this will help.
Regards,
Kaushik Solanki
Ok
But what sort of datasource should we build for qlikview to consume. I am no qlikviewdeveloper I have only been asked to provide som data for a customer.e
What can qlikview consume easly? REST API, SOAP?
Andreas
Hi,
QlikView can consume data from any kind of datasource.
Like Excel, Txt file, Databases like Oracle, mysql Also SAP.
Regards,
Kaushik Solanki
Hello Andreas, The terms REST, API, and SOAP looks good with Java and Dot Net Application, As you said that you are not familiar with QlikView. Then QlikView is Business intelliegence tool, and here we talk about Cubes, Meta Data, Schemas. As you told you have SQL Server and contains all data which you dont want to show, then Create Schema and give Read permission onTable and Views which you can populate for QliView data. In QLikView share the credentials and Make connection string to connect with SQL Server using ODBC, and Load the data. Again in QlikView you can implement security using section access and restrict the users.
Hope I am able to answer you as per your knowledge.
Thanks
Regards
QlikView Bug
The problem with using a database and setting that up is to time consuming for us as each customer needs to have it's on view. Alla the data is in the same tables and separetad by customerID's we also don't want to open up our database outside our firewall. Database connections with odbc then the data is not encrypted.