1. QlikView Integration Overview June 2011

2. Agenda Data Source Integration Web & Application Integration Security Integration Integration with 3rd party systems and processes

3. Agenda Data Source Integration Web & Application Integration Security Integration Integration with3rd party systems and processes

4. Data Source Integration Easily integrating with many diverse data sources is a key tenet of QlikView SQL Server Oracle Any ODBC/OLE source Salesforce.com SAP Netweaver xls/xlsx csv text XML Web Services

5. Data Source Integration Accessing ‘non-standard’ data sources Salesforce.com Connector –‘Native’ connectivity to SFDC data, similar in appearance to the ODBC/OLE connector –Can access all common fields in SFDC, as well as custom fields

6. Data Source integration Accessing ‘non-standard’ data sources SAP Connector –Simple query builder to SAP data –Uses metadata and field descriptions from SAP to allow QlikView developers ‘make sense’ of SAP field and data names –Supports extraction from SAP R/3, mySAP and existing SAP BW and BEX information

7. Data Source integration Accessing ‘non-standard’ data sources Accessing OLAP sources or Informatica sources using QlikView Data Exchange (QVX) –QVX as a file format. Data is ‘pushed’ to QVX files (using API’s) and consumed by QlikView –QVX as a connector. Data is ‘pulled’ from QVX files.

8. Agenda Data Source Integration Web & Application Integration Security Integration Integration with3rd party systems and processes

9. Web Integration Integrating with Microsoft SharePoint QlikView supports and promotes ‘Web Part’ technology –Every object (e.g. chart, listbox) in a QlikView application can be used as a web part. Each web part can be used as a live object within SharePoint –All data, client-server communication and the in-memory processing still occurs in the QlikView Server –QlikView embedded within SharePoint allows for a single intranet portal to show KPI’s and dashboard information

10. Web Integration Integrating with websites QlikView AJAX client is open and extensible: API’s exist to embed QlikView into websites QlikView WorkBench is a product that allows developers using MS Visual Studio to embed QlikView objects into websites An entire QlikView application can be embedded into a website using standard iFrame technology

11. Application Integration QlikView uses an ActiveX OCX (OLE Control Extension) component for integration with 3 rd party desktop and web applications Provided on an OEM basis for ‘white labeled’ versions of QlikView Allows for QlikView to be hosted and controlled by the 3 rd party application via API’s

12. Agenda Data Source Integration Web & Application Integration Security Integration Integration with3rd party systems and processes

13. Security Integration QlikView integrates with a series of standard security systems for authentication and authorization purposes –MS Active Directory –Single Sign-On systems (SSO) (e.g. Novell, IBM Websphere) –Non-AD LDAP’s QlikView can use a combination of Integrated Windows Authentication, HTTP headers, ticketing, Directory Service Connectors (DSC’s)

14. Security Integration Single Sign-On Integration QlikView can work with existing SSO providers for user authentication Method used is HTTP Header injection Example deployments include –IBM Tivoli Access Manager –MS ISA/TMG –CA SiteMinder

15. Security Integration The topic of QlikView Security is covered extensively in the following content: –QlikView Security Overview White Paper –QlikView Security Video Series –QlikView Development and Deployment Technical Brief

16. Agenda Data Source Integration Web & Application Integration Security Integration Integration with 3rd party systems and processes

17. This topic covers the following areas: Management Integration Automation and Scheduling Managing Documents/Version Control Deployment Control

18. Integration with 3rd party systems and processes Management Integration QlikView provides a web-based Management Console out of the box Extensive management API’s exist to allow automation of tasks on a larger scale, or to allow integration with existing centralized application management software Example: integrating an HR system for employee on-boarding with the QlikView admin tasks to allocate QlikView licenses

19. Integration with 3rd party systems and processes Automation and Scheduling QlikView provides a native scheduling solution for automating data reloads However: often before data is reloaded, a number of activities need to take place: e.g. cleansing or data retrieval checks QlikView reloads can be triggered (using Event Driven Execution – EDX) by any external dedicated schedulers such as –BMC Software Control-M –IBM Tivoli

20. Integration with 3rd party systems and processes Managing Documents/Version Control QlikView works with any standard Source Control system (such as MS TFS, Visual Source Safe etc.) for version control Single.qvw files can be ‘exploded’ into multiple files: each XML file containing the definition of each object in the.qvw file (such as a chart of list box) –This ‘Project File’ collection can be used with a source control system for more granular control –Data is not exported to the source control system, minimizing storage needs

21. Integration with 3rd party systems and processes Managing Documents/Version Control QlikTech partners with NOAD for a fully integrated versioning and deployment control system Product is called EQM4 Version Control Full ‘knowledge’ of QlikView applications Source data locations Scripts UI objects Extension objects

22. Integration with 3rd party systems and processes Deployment Control NOAD EQM4 Deployment Control manages the rollout of QlikView applications from a central source –Dev –Test –UAT –Production Approval workflow built-in to the solution Test manager can see reports on difference analysis of checked-in applications, allowing them to focus on just the changed parts

23. Integration Materials NEW: Integration Overview White Paper NEW: Integration Overview Video Series

24. Thank You