Information Technology Reference
In-Depth Information
5.3
System Scalability
Regarding scalability, and the pervasiveness requirements of ubiquity, this solution
was designed with both the DW and front-end horizontal scalability in mind. At the
DW level, it is achieved by using database clusters. At the Front-End it is achieved
dividing the front-end by different business areas. This division is done at the
compute level of the front-end and presentation is kept unified, making this division
of compute resources invisible to the end user, who continues to perceive the
front-end as a whole [20].
6
Implementation
6.1
ETL
To achieve real-time requisites and pervasiveness of data access, as well as capacity
for automation, all of the ETL layer was developed recurring to SQL statements. This
also allows for maximum compatibility with other database management system that
use the same language, with minor adjustments in the code. In the figure below,
Figure 4, a diagram illustrating the ETL process is presented. The main data sources
are: the requests made by citizens and the workflow moves from the requests.
Fig. 4.
- ETL Process Diagram
6.2
Access Control Layer
One of the requirements for a pervasive BI is universal access to data, and with a web
enabled front-end, access control to the platform is done in three levels. The first step
is access to the organization Active Directory Domain. This authentication step can be
bypass if the user has already logged on the Active Directory Domain, by means of
the operating system log on. The second level of authentication pertains to the
platform access, and identifies to witch applications in the platform, the user has
access to. Each organizational unit can have one or more applications. The third
access level is to information within each application. This might be needed to
enforce privacy data law compliance. This level will also control access to (tabs /
dashboards) that the user can view and can change.
Search WWH ::
Custom Search