[
https://issues.apache.org/jira/browse/CONNECTORS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274809#comment-13274809
]
Karl Wright commented on CONNECTORS-470:
----------------------------------------
My colleague says the following:
"Yes, we have a customer that has updated to SharePoint 2010 so we've had to
update the connector. I went into this knowing nothing about SharePoint and
found ... I hate SharePoint. Here is what I know at this point:
- I never could get the DspSts.asmx service to work with 2010. Found a couple
forum posts from MS employees that say that the DspSts interfaces are
deprecated in 2010 and should not be used. Use the lists.amx service to get the
same information. In the crawler, I wrote another proxy class that inherits
from the original and uses the lists.asmx service to get the same information
for version 4.0 (2010).
- You still need the MCPermssions.asmx service as there still exists no way
through the web services to get permissions info at the file level.
- MS has added a feature in 2010 call the “List View Threshold” to help with
performance. This does not allow users to get the items in a list if the list
has more than a “threshold” amount of items, default being 5000. This means
that a crawing user cannot crawl a list having more than 5000 items without
getting a “List View Threshold” exception from the SharePoint server (even
using the lists.asmx web services). Unfortunately our clients have lists with
WAY more than this number (closer to a million items). Some ways around this:
-- Have the SharePoint admins turn off the list view threshold for the lists in
question, which most are NOT willing to do.
-- Crawl with a admin user (their threshold is defaulted at 20,000).
-- Have the SharePoint admins increase the Threshold of the crawling user
(again, they’re not crazy about that).
-- I have implemented a couple more custom web service methods that the crawler
uses to get list items that use the .NET SharePoint Server Object Model API.
There are ways to circumvent this threshold using this API, then page the
results back to the crawler. This allows us to crawl lists with an unlimited
number of items. We are still in a testing phase with a customer for this.
-- Here is a link the describes this:
http://blogs.technet.com/b/speschka/archive/2009/10/27/working-with-large-lists-in-sharepoint-2010-list-throttling.aspx
"
> SharePoint 2010 support
> -----------------------
>
> Key: CONNECTORS-470
> URL: https://issues.apache.org/jira/browse/CONNECTORS-470
> Project: ManifoldCF
> Issue Type: Improvement
> Components: SharePoint connector
> Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 0.6
>
>
> See here for list of the SharePoint web services for SharePoint 2010:
> http://msdn.microsoft.com/en-us/library/ee705814.aspx
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
