How to integrate with SharePoint will depend on the version of SharePoint you have installed.
MOSS 2007 and SharePoint 2010 - QlikView Webparts/
SharePoint 2012+ you require Workbench and create an integration using "div tags" method.
Incidentally, workbench "div tag" method is backward compatible (supporting MOSS 2007 & SharePoint 2010)
My advice is progress with Workbench solution, rather than use QlikView Webparts.
Hope this is useful? If this is useful please mark the question as answered.
Just checking you have Enterprise Edition and not Small Business Edition Server, as the later doesn't support SharePoint integration?
I would recommend looking at the Workbench solution instead of the Webparts approach. I would say each solution should take no more than 1/2 a day to configure correctly, you may complete the configuration quicker than 1/2 day it is not that complicated to set-up. The integration to SharePoint Sites or Pages vary in the time they take 5 minutes - 1 hour (depending on what you are trying to do). An entire QlikView application/document can be embedded within Webparts within SharePoint. Individual objects or collections of objects can be quickly and easier embedded within SharePoint and work in the usual way displaying selected data, associated data and unrelated data based upon the users selection.
I have a price list, however the price may vary based upon where you are located. The best option maybe to contact your QlikView Account Manager, who will be able to provide pricing information to you. Based upon my price list, both QlikView Webparts and Workbench are identically priced.
Hope this helps?
I would suggest not to use WebParts because it only alows you to deploy QlikView objects in Share Point.
If you would like to open the QlikView accespoint in Sharepoint just create an new iframe and use the accesspoints url to display the accesspoint in SharePoint.
You would probably like a single-sign-on solution which can be achieved with certificates.
The only restriction would be external availability. If you placed the QV server on an internal server.
But this issue is fixable by placing a second webserver in DMZ or something like that.
Hope this points you in the right direction.