You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The Aspire SharePoint Web Services extension is required for accessing full document-level security ACLs from SharePoint, as well as for some additional features. See Standard or Extended SharePoint Web Services for more information.

The required files for SharePoint 2010 can be found here using your Aspire credentials:

Features Provided with the Extended Web Service

The following features will be available if you install the extended web service:

  • Security ACLs will be available for folders and documents.

    Without the extension, security information will be retrieved for only for sites and lists, and their ACLs will be automatically propagated to all of the items they contain. Individual document-level security ACLs will not be available.

  • URL provided to the connector can be from any site or sub-site, list or folder.

    Without the extension, the URL must be a site collection URL.

  • The account used to run the connector will need fewer access rights.
  • Hierarchical information required for Aspire Corporate Wide Sitemap will be available.

    This is used to implement the Aspire Corporate-Wide Sitemap feature.

Installation Steps

  1. Copy web service files (asmx and aspx) to ISAPI folder on the server’s SharePoint installation folder (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI)
  2. Choose one of SPDocumentTraversalService - 12.dll or SPDocumentTraversalService - 14.dll and rename it SPDocumentTraversalService.dll
    • SPDocumentTraversalService - 12.dll is for SharePoint 2007
    • SPDocumentTraversalService - 14.dll is for SharePoint 2010
  3. Run "gacutil -if SPDocumentTraversalService.dll" on a Visual Studio command prompt.
  4. Run "iisreset" on a Windows command line.
  5. Accessing http://siteUrl/_vti_bin/DocumentTraversalService.asmx to verify that the service was deployed correctly.

The above steps need to be applied based on the next rules:

  • If there is a single SharePoint server, do it only on that server.
  • If there is a load-balanced farm configuration with multiple web front ends and there is a virtual host configured to route requests through the load balancer to communicate with the web front ends, repeat the installation steps on all of the front ends.
  • If there is a load-balanced farm configuration with multiple web front ends, but there is a dedicated web front end to handle requests, install on the dedicated web front end only.

The above guidelines are the suggested ones, but they may actually change on each SharePoint deployment.

Note: If don't have the "gacutil" command on your command prompt, you'll need to install .Net Framework SDK. Instead of Step 3, you'll need to run the command like this:

  • C:\Program Files (x86)\Microsoft.NET\SDK\<version_number>\bin>gacutil -if [FILEPATH]\SPDocumentTraversalService.dll
  • No labels