Version 10 for Microsoft Windows® First Edition, Lund, Sweden, October 2010 Authored by QlikTech International AB
Copyright © 1994-2010 Qlik®Tech International AB, Sweden. Under international copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced, translated or reduced to any electronic medium or machine-readable form, in whole or inpart, without the prior written permission of QlikTech International AB, except in the manner described in the software agreement. Qlik®, QlikTech® and QlikView® are trademarks and registered trademarks of QlikTech International AB. Other trademarks are the property of their respective owners and are hereby acknowledged.
Content 1 What's New in Version 10 2 Version Compatibility 3Installing QlikView Web Parts Requirements Installation Post Installation Manual Setup Using Proxy 4 Creating a Web Part Page 5 QlikView Web Parts for SharePoint and the QvAjaxZfc Virtual Directory Scenario 1: Scenario 2: Scenario 3: Scenario 4: Other Notes: 6 QlikView Web Parts for SharePoint and Multi-hop Authentication 7 Troubleshooting 8 Appendix A Inline Styles Logging 3 4 5 6 6 6 7 7 9 1414 14 14 15 15 16 17 18 18 18
1 What's New in Version 10
The following list outlines changes and improvements in QlikView Web Parts for SharePoint version 10:
The new installer simplifies the process of installing and configuring QlikView Web Parts for SharePoint. Manual steps have been eliminated. The Datasource Web Part is no longer needed making page layout more intuitive. TheQlikView document to use is defined as just another property of any QlikView Web Part. A single unified Web Part for all objects makes adding QlikView Web Parts even easier and prevents clutter the Web Part Gallery. Simplified properties for QlikView Web Parts makes configuring each QlikView Web Part easier. The back end architecture has been altered to take advantage of the services traditionallysupplied by the QlikView AccessPoint. This means that: o QlikView Web Parts for SharePoint can take advantage of QlikView load balancing when operating against clustered QlikView Servers.
QlikView Web Parts for SharePoint can more easily avoid the multi-hop authentication problem inherent in NTLM when the QlikView Server is on a different machine from SharePoint.
Due to the architectural changes needed to support the new features in version 10 and to allow us to extend the QlikView Web Parts for SharePoint product into the future beyond version 10, QlikView Web Part for SharePoint version 10 is not compatible with any earlier release of QlikView Server (i.e. QlikView Server version 9, 8.5, etc.). Likewise, SharePoint websites thatcontain version 9 or earlier QlikView Web Parts are not compatible with QlikView Server version 10.
3 Installing QlikView Web Parts
1. QlikView Server 10. The Server does not need to be installed on the same machine, but must be reachable over the network. 1. The QlikView Server must be configured to serve QlikView Ajax content via either the QlikView WebServeror Microsoft IIS (see the QlikView Server Reference manual for more information, also see the QvAjaxZfcPath setting below). 2. The QlikView Server must be licensed to allow QlikView Web Parts for SharePoint. To verify if a given QlikView server is licensed for QlikView Web Parts for SharePoint usage, verify that the License Enabler File for the QlikView Server has a line that states WebParts;YES;; - for more information, contact you QlikView Account Executive. 2. Because QlikView Web Parts for SharePoint acts as a fully featured client to a QlikView Server and exposes full QlikView functionality to the end user, each SharePoint user that will consume QlikView content via the QlikView Web Parts for SharePoint must have the appropriate licensing on the QlikView Server (see your QlikView...
Leer documento completo
Regístrate para leer el documento completo.