Implementation

Recommendations

Info

BA/BI Developers P a g e | 39 The role of a business analyst or BI developer in a typical QlikView deployment primarily involves the use of QlikView Desktop. QlikView developers use this Windows desktop application to extract data from source systems, create data models, and transform the data. It is where they describe all metadata, create data storage layers (QVD layers), and lay out the user interface. The BA or BI developer can also reuse existing extracted and pre-modeled data from the QVD layer by pulling “off-the-shelf” data from the QVD, when relevant for their application. The BA or BI developer also wants to ensure that their QlikView business applications are using the most recent data and that QlikView apps are being distributed to the correct business user community. For this reason, BAs and BI developers typically work closely with IT pros who use QlikView Publisher on the back end to ensure data refresh rates and QlikView Server on the front end to ensure the applications are correctly distributed and meet the business’ needs. Business User Business users interact with QlikView applications exclusively via the front end of a deployment, most typically using a browser on their desktop, laptop, or mobile device (such as an iPad). Users simply open their AccessPoint portal (or, in the case of integrated solutions, their organization’s own enterprise portal) and select the QlikView application they wish to use. QlikView Server provides all client-server communication and is the engine that drives the in- memory associative experience. Once the user’s security credentials are verified, they then open and can begin working with the application, exploring and interacting with the data and asking and answering their own stream of questions in a self-service mode. Users can also collaborate with other users in the organization, sharing insights and exploring data together, in real time or asynchronously. 4.1.5 QLIKVIEW WORKING PROCEDURE When a QlikView document is published on a QlikView Server, the content it contains becomes available for consumption by any user with privileges to access it. QlikView works like this: Step 1:When a user first opens a QlikView document, data is loaded in memory. __________________________________________________________________________________ BI Reporting Tool <strong>Implementation</strong> Arpan Ganguly
P a g e | 40 The compressed and unaggregated dataset is loaded off the disk and into the QlikView Server’s RAM (random access memory). This in-memory repository serves as the base dataset for this initial user and all other users requesting the same document. This repository stays in memory until no user activity has occurred within a defined time-out period. Step 2: Users explore data via selections. Central to QlikView is the concept of a user-defined selection state. As users click around in a QlikView document, they indicate which subsets of data they are interested in analyzing and which subsets should be ignored. QlikView takes advantage of the highly indexed nature of the unaggregated dataset. QlikView dynamically presents a subset of all the data available to the QlikView document based on the selection state. This happens in real time as the user executes clicks. Step 3: Upon selection, aggregates render instantly. On the fly, QlikView renders aggregates as intuitive and interactive user interface objects: charts, graphs, tables, etc. Users interact with objects in QlikView documents through any supported client. Users can create their own objects using the collaboration features. For a more comprehensive understanding of how QlikView works, please visit: http://www.qlikview.com/us/explore/resources/technical-briefs?language=english 4.2 QLIKVIEW DEPLOYMENT 4.2.1 ARCHITECTURE OVERVIEW Figure 9.0 shows the architecture of the QlikView production environment. Three main infrastructure components are used in this deployment. QlikView Server (QVS) handles the communication between the clients and the QlikView applications. QlikView Server loads the QlikView applications into memory and calculates and presents user selections in real time. In this deployment, Apache web servers are used to provide the content tothe users. There are two servers used to host the QlikView Server. These servers are clustered and located in the demilitarized zone (DMZ). They are used to serve the QlikView applications to the external users. In addition to these, there are four other servers, which are located in the local area network (LAN). These servers are used to serve the QlikView applications to the internal users. These servers are also clustered. __________________________________________________________________________________ BI Reporting Tool <strong>Implementation</strong> Arpan Ganguly
Page 1 and 2: Business Intelligence Reporting Too
Page 3 and 4: BI Reporting Tool Implementation __
Page 9 and 10: corporate agents and brokers to dis
Page 11 and 12: ICICI Prudential Life Insurance Com
Page 13 and 14: 1.5.1.4 RETIREMENT SOLUTIONS P a g
Page 15 and 16: diverse set of needs that character
Page 17 and 18: and liabilities of the insurance po
Page 19 and 20: your policy. However, your existing
Page 21 and 22: loans. 1.6.8.6 Can I assign a polic
Page 23 and 24: 3.0 SYSTEM OVERVIEW FIG 1.0 : Syste
Page 25 and 26: P a g e | 18 the time at which the
Page 27 and 28: P a g e | 20 the intermediary data
Page 29 and 30: P a g e | 22 from new business prem
Page 31 and 32: P a g e | 24 The charts in this rep
Page 33 and 34: 4.1 BI TOOLS : QlikView P a g e | 2
Page 35 and 36: 4.1.2 QLIKVIEW EXPERIENCE 4.1.2.1 Q
Page 37 and 38: Fast to Deploy, IT Efficient. P a g
Page 39 and 40: Speedy time to value. FIG 6.0 : Sam
Page 41 and 42: 4.1.2.3 QLIKVIEW EXPERIENCE : MAY B
Page 43 and 44: P a g e | 36 possible but even with
Page 45: P a g e | 38 AJAX or Mobile) and th
Page 49 and 50: 4.2.2 DEMILITARIZED ZONE 3. After s
Page 51 and 52: P a g e | 44 the call uses an Activ
Page 53 and 54: FIG 13.0 : Qlikview Section Access
Page 55 and 56: 5.1.2 DATA SOURCES Tables Required
Page 57 and 58: Agent Wise P a g e | 50 A summary o
Page 59 and 60: Channel wise P a g e | 52 A summary
Page 61 and 62: 5.2.4 Final Reports on Qlikview : O
Page 63 and 64: Ops Region Summary Ops Region Campa
Page 65 and 66: 6.0 REFERENCES About ICICI Prudenti

Implementation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?