Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

Announcements
QlikWorld, June 24-25, 2020. Free virtual event for DI and DA gurus. Register Today
cancel
Showing results for 
Search instead for 
Did you mean: 
Specialist
Specialist

is Binary Load Applicable in Access Point?

I am trying to understand the purpose of Binary Load. Please help me. The qvw we have been working on is ready for production and we want to implement the security following best practice. So I was going to do a Binary load on the app to be published. But if the publisher takes care this for you by clearing the script so that users can not get access to script, what is the point of doing a binary load if you are publishing your document in access point for users. Because what I understand about binary load is it is a security feature that will prevent the USERS from getting access to the script. Please feel free to comment.

1 Solution

Accepted Solutions
Highlighted
MVP
MVP

Re: is Binary Load Applicable in Access Point?

Binary Load is a feature to be able to reuse the final data model of a QVW in another QVW without having to run the Load Script of the first QVW.

So yes a binary load does hide the load script of the first QVW. But no it is not really a security feature because it does give full access to the final data. But if hiding the source code and any sensitive information that might be in the load script it could be "part" of a security measure.

For the Access Point a binary load does not give you anything extra as the users of applications accessible on the Access Point does not have access to the QVW - unless download of QVWs is enabled via the QMC. But if you run the Publisher it will strip the load script when doing a reload anyway. If you run reload via the SBE-version of QlikView Server it will not stip the load script code away.

Binary Load:

- Is a very efficient way of loading a complete data model. Even more efficient than loading QVDs. So if you need a prefabricated data model which can be modified further for you analysts or you the Binary Load is a very nice feature.

- If you need to separate the data manipulation  / ETL from the UI/Application parts keeping the Load Script and ETL in one QVW and the UI/App specific in another QVW might be a good practice for you.

  So you could build and maintain one Load Script QVW and have several different front-end QVW maybe for different devices or different applications that share most of the data model.

There are also uses for binary load for other purposes like under development if you need to further refine or append to the data model you can perform a "self-binary-load" so you don't need to rerun your entire load script to make minor modifications to the data model.

View solution in original post

2 Replies
Highlighted
MVP
MVP

Re: is Binary Load Applicable in Access Point?

Binary Load is a feature to be able to reuse the final data model of a QVW in another QVW without having to run the Load Script of the first QVW.

So yes a binary load does hide the load script of the first QVW. But no it is not really a security feature because it does give full access to the final data. But if hiding the source code and any sensitive information that might be in the load script it could be "part" of a security measure.

For the Access Point a binary load does not give you anything extra as the users of applications accessible on the Access Point does not have access to the QVW - unless download of QVWs is enabled via the QMC. But if you run the Publisher it will strip the load script when doing a reload anyway. If you run reload via the SBE-version of QlikView Server it will not stip the load script code away.

Binary Load:

- Is a very efficient way of loading a complete data model. Even more efficient than loading QVDs. So if you need a prefabricated data model which can be modified further for you analysts or you the Binary Load is a very nice feature.

- If you need to separate the data manipulation  / ETL from the UI/Application parts keeping the Load Script and ETL in one QVW and the UI/App specific in another QVW might be a good practice for you.

  So you could build and maintain one Load Script QVW and have several different front-end QVW maybe for different devices or different applications that share most of the data model.

There are also uses for binary load for other purposes like under development if you need to further refine or append to the data model you can perform a "self-binary-load" so you don't need to rerun your entire load script to make minor modifications to the data model.

View solution in original post

Highlighted
Specialist
Specialist

Re: is Binary Load Applicable in Access Point?

petter.skjolden

Thank you for your well explained, comprehensive & meaningful reply. It has been of immense help.

Regards,