Page History

...

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

• Version 3.X

Features Provided with 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.

• Site Collection discovery.

Installation Steps

...

• SPDocumentTraversalService - 12.dll is for SharePoint 2007
• SPDocumentTraversalService - 14.dll is for SharePoint 2010

...

SharePoint 2010

1. Run SharePoint Management Shell as Administrator.

2. Run the following command:

   Code Block
   language powershell theme RDark
   add-spsolution -LiteralPath <path to sp2010 wsp>

3. Now run:

   Code Block
   language powershell theme RDark
   install-spsolution -Identity <wsp name> -GACDeployment

4. Go to Central Administration -> System Settings -> Manage Farm Solutions
5. The wsp should be deployed now.
6. Test the service browsing to http://<sitecollectionurl>

...

1. /_vti_bin/DocumentTraversalService.asmx

...

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:

...

SharePoint 2007

1. Run Windows Powershell as Administrator.
2. cd to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN (or where your SharePoint installation folder is located).

3. Run:

   Code Block
   language powershell theme RDark
   STSADM.EXE -o addsolution -filename <path to sp2007 wsp>

4. Run:

   Code Block
   language powershell theme RDark
   STSADM.EXE -o deploysolution -name <wsp name> -immediate -allowGacDeployment

5. Go to Central Administration -> Operations -> Global Configuration -> Solution Management
6. The wsp should be deployed now.
7. Test the service browsing to http://<sitecollectionurl>/_vti_bin/DocumentTraversalService.asmx