Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello folks,
Excited that i am developed my first QlikView Application and implemented section access at application leave. We maintained user information in database and taken it into application. It is working good.
Now my turn is to deploy it into production. Since i am new to QMC (i know how to deploy application without section access), what extra steps i need to take care while deploying the application which is section access implemented.
Thanks.
A reload under control of the QlikView Distribution Server (aka "the Publisher", whether you have a publisher license or not) is run by a QV Desktop-like process called QVB.exe. This process is run in the background using the service account of the QDS service (see the services control panel on your server to know which Windows account it is).
For QVB.exe to be able to open a QVW with section access for a reload, it must have access to that document. Since access is managed by Section Access, this particular account needs an entry in your Section Access table as well. Otherwise the publisher will not be able to open the document and therefor cannot reload it.
Your second option is also possible, but less flexible. And passwords for ordinary users may need to be changed whenever System Administrators decide that passwords expire. A service account password usually never expires.
Best,
Peter
To your section access details, server local user (thorugh which QV services are running) needs to be added. else it will fail to reload.
Hi Manoj,
Do you mean i need to add server local user information to my section access details in QVW?
I did get exactly what does it mean?
or
you mean i need to add user and password of QMC at data protection field in RELOAD tab while scheduling application?
The service account should have an entry with ACCESS = ADMIN.
If you are using "data reduction based on section access", make sure that the link fields for the service account stay empty.
Also, your soution is ideally suited to enable "Dynamic CAL assignment" for Document CALs. Since your document itself will decide on who's getting access, you won't need to manually maintain a CAL list.
Best,
Peter
A reload under control of the QlikView Distribution Server (aka "the Publisher", whether you have a publisher license or not) is run by a QV Desktop-like process called QVB.exe. This process is run in the background using the service account of the QDS service (see the services control panel on your server to know which Windows account it is).
For QVB.exe to be able to open a QVW with section access for a reload, it must have access to that document. Since access is managed by Section Access, this particular account needs an entry in your Section Access table as well. Otherwise the publisher will not be able to open the document and therefor cannot reload it.
Your second option is also possible, but less flexible. And passwords for ordinary users may need to be changed whenever System Administrators decide that passwords expire. A service account password usually never expires.
Best,
Peter