topic Re: section access in 3 tier architecture in QlikView

section access in 3 tier architecture

gauthamchilled — Wed, 25 Nov 2020 16:16:04 GMT

Hi,

I'm implementing 3 tier architecture in our dashboard. I have 3 layers now

1. abc QVD Maker.qvw

2.abc Script loader.qvw

3.abc dashboard.qvw

If i have to implement section access, in which layer i have to implement section access?

pls help

-Gautham

Re: section access in 3 tier architecture

Anil_Babu_Samineni — Fri, 04 Aug 2017 09:00:27 GMT

Re: section access in 3 tier architecture

arvind_patil — Fri, 04 Aug 2017 09:04:54 GMT

Hi,

Section access work on access point when user login at that time we restrict them to access data. So undoubtedly on dashboard.

Thanks,

Arvind Patil

Re: section access in 3 tier architecture

neha_shirsath — Fri, 04 Aug 2017 10:03:25 GMT

Go through attached document. It will give you details about where to add section access and how to add.

Re: section access in 3 tier architecture

Akina0929 — Fri, 04 Aug 2017 10:22:20 GMT

abc dashboard.qvw

Re: section access in 3 tier architecture

marcus_sommer — Fri, 04 Aug 2017 10:52:19 GMT

I think it's depending on how you defined each layer. Personally I use a 4-tier architecture and the dashboard-layer is only loading per binary - therefore I have the section access within the last two layers: dashboard + datamodel.

- Marcus

Re: section access in 3 tier architecture

gauthamchilled — Sat, 05 Aug 2017 05:28:47 GMT

Hi Marcus,

My 3 tier architecure is like below.

1st layer--> QVD extract --simple select * from

2nd layer-> Transformation layer

3rd layer--> dashboard with section access (binarly load of 2nd layer)

Can you let me know in which layer can i have section access?

Also, never heard about 4 layer architecture, can you share about that?

Gautham

Re: section access in 3 tier architecture

marcus_sommer — Sat, 05 Aug 2017 16:14:27 GMT

The fourth layer is created by a more granular splitting of the 3-tier architecture. In my case the first layer is splitted into two layers. The first layer loads the raw-data without much transformations (adding some fields for incremental approaches, some if-constructs to handle different formattings for the same source and few other things but not really changing the data itself). The second layer used the qvd's from the first layer to do all the transformations. My third layer then creates the real datamodels by combining various qvd's from the first/second layer and the fourth layer is just the binary loaded dashboard with the gui.

If I would consider the logic of using layers more strictly I would need even two or three layers more but I'm a bit pragmatically on this point because most of my data needs only 3 or 4 layers.

In my scenario I load the section access table within the third layer (datamodel) and the binary load transferred it like the other data into the dashboard (fourth layer). In both layers I enable the section access settings within the document properties in tab open.

I must admit that I use this since many years (without thinking much about it) and I'm not absolutely sure if it wouldn't be working to load the section access just after the binary statement and to keep the section access only within the last layer.

Section access is a very special feature and you will need in each case various testings if it worked for each user like expected. Therefore I suggest that you just makes some more testings in which layer it would suit best. But before applying any section section make sure that you have BACKUP's from all of your applications - otherwise could be a mistake very painful.

- Marcus

Re: section access in 3 tier architecture

maxgro — Sun, 06 Aug 2017 18:31:39 GMT

I think on your second layer; this is from Qlik help

Inherited Access Restrictions

A binary load will cause the access restrictions to be inherited by the new QlikView document. A person with ADMIN rights to this new document may change the access rights of this new document by adding a new access section. A person with USER rights can execute the script and change the script, thus adding own data to the binary loaded file. A person with USER rights cannot change the access rights. This makes it possible for a database administrator to control the user access also to binary loaded QlikView documents.