Return-Path: X-Original-To: apmail-manifoldcf-commits-archive@www.apache.org Delivered-To: apmail-manifoldcf-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 33CFA9FFA for ; Fri, 15 Jun 2012 02:20:52 +0000 (UTC) Received: (qmail 20419 invoked by uid 500); 15 Jun 2012 02:20:51 -0000 Delivered-To: apmail-manifoldcf-commits-archive@manifoldcf.apache.org Received: (qmail 20373 invoked by uid 500); 15 Jun 2012 02:20:51 -0000 Mailing-List: contact commits-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list commits@manifoldcf.apache.org Received: (qmail 20366 invoked by uid 99); 15 Jun 2012 02:20:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2012 02:20:51 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2012 02:20:48 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 278492388865; Fri, 15 Jun 2012 02:20:27 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1350449 - in /manifoldcf/branches/CONNECTORS-474: connectors/sharepoint/lib-proprietary/ site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml Date: Fri, 15 Jun 2012 02:20:26 -0000 To: commits@manifoldcf.apache.org From: kwright@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120615022027.278492388865@eris.apache.org> Author: kwright Date: Fri Jun 15 02:20:26 2012 New Revision: 1350449 URL: http://svn.apache.org/viewvc?rev=1350449&view=rev Log: Finish revising SharePoint doc Removed: manifoldcf/branches/CONNECTORS-474/connectors/sharepoint/lib-proprietary/ Modified: manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml Modified: manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml URL: http://svn.apache.org/viewvc/manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml?rev=1350449&r1=1350448&r2=1350449&view=diff ============================================================================== --- manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml (original) +++ manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml Fri Jun 15 02:20:26 2012 @@ -60,6 +60,7 @@
  • LiveLink connector, built against a LiveLink API stub
  • Meridio connector, built against modified Meridio API WSDLs and XSDs
  • RSS connector
  • +
  • SharePoint connector, built against SharePoint API WSDLs
  • Webcrawler connector
  • Wiki connector
  • @@ -231,18 +232,10 @@
    Building the SharePoint connector

    -

    In order to build this connector, you need to download wsdls from an installed SharePoint instance. The wsdls in question are:

    -

    -
      -
    • Permissions.wsdl
    • -
    • Lists.wsdl
    • -
    • Dspsts.wsdl
    • -
    • usergroup.wsdl
    • -
    • versions.wsdl
    • -
    • webs.wsdl
    • -
    -

    -

    To download a wsdl, use Microsoft's disco.exe tool, which is part of Microsoft's Visual Studio, typically under c:\Program Files\Microsoft SDKs\Windows\V6.x\bin. You'd want to interrogate the following urls:

    +

    The SharePoint connector generates interface classes using checked-in wsdls originally obtained + from an installed Microsoft SharePoint instance using disco.exe. The disco.exe utility is installed as part of + Microsoft Visual Studio, and is typically found under "c:\Program Files\Microsoft SDKs\Windows\V6.x\bin". + If desired, you can obtain unmodified wsdls by interrogating the following SharePoint web services:

    • http[s]://<server_name>/_vti_bin/Permissions.asmx
    • @@ -253,14 +246,9 @@
    • http[s]://<server_name>/_vti_bin/webs.asmx

    -

    When the wsdl files have been downloaded, copy them to the directory connectors/sharepoint/lib-proprietary before building.

    -

    -

    The wsdl files download will be done automatically if you type "ant make-deps" from the root directory.

    -

    Note well: For SharePoint instances version 3.0 or higher, in order to support file and folder level security, you also must deploy a custom SharePoint web service on the SharePoint instance you intend to connect to. This is because Microsoft apparently overlooked support for web-service-based access to such security information when SharePoint 3.0 was released. This service can be found in the directory dist/sharepoint-integration after ManifoldCF is built. To install it on your SharePoint 3.0 machine, follow the directions in the file Installation Readme.txt, found in that directory.

    -

    Modified: manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml URL: http://svn.apache.org/viewvc/manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml?rev=1350449&r1=1350448&r2=1350449&view=diff ============================================================================== --- manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml (original) +++ manifoldcf/branches/CONNECTORS-474/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml Fri Jun 15 02:20:26 2012 @@ -60,6 +60,7 @@
  • LiveLink connector, built against a LiveLink API stub
  • Meridio connector, built against modified Meridio API WSDLs and XSDs
  • RSS connector
  • +
  • SharePoint connector, built against SharePoint API WSDLs
  • Webcrawler connector
  • Wiki connector
  • @@ -231,18 +232,10 @@
    Building the SharePoint connector

    -

    In order to build this connector, you need to download wsdls from an installed SharePoint instance. The wsdls in question are:

    -

    -
      -
    • Permissions.wsdl
    • -
    • Lists.wsdl
    • -
    • Dspsts.wsdl
    • -
    • usergroup.wsdl
    • -
    • versions.wsdl
    • -
    • webs.wsdl
    • -
    -

    -

    To download a wsdl, use Microsoft's disco.exe tool, which is part of Microsoft's Visual Studio, typically under c:\Program Files\Microsoft SDKs\Windows\V6.x\bin. You'd want to interrogate the following urls:

    +

    The SharePoint connector generates interface classes using checked-in wsdls originally obtained + from an installed Microsoft SharePoint instance using disco.exe. The disco.exe utility is installed as part of + Microsoft Visual Studio, and is typically found under "c:\Program Files\Microsoft SDKs\Windows\V6.x\bin". + If desired, you can obtain unmodified wsdls by interrogating the following SharePoint web services:

    • http[s]://<server_name>/_vti_bin/Permissions.asmx
    • @@ -253,14 +246,9 @@
    • http[s]://<server_name>/_vti_bin/webs.asmx

    -

    When the wsdl files have been downloaded, copy them to the directory connectors/sharepoint/lib-proprietary before building.

    -

    -

    The wsdl files download will be done automatically if you type "ant make-deps" from the root directory.

    -

    Note well: For SharePoint instances version 3.0 or higher, in order to support file and folder level security, you also must deploy a custom SharePoint web service on the SharePoint instance you intend to connect to. This is because Microsoft apparently overlooked support for web-service-based access to such security information when SharePoint 3.0 was released. This service can be found in the directory dist/sharepoint-integration after ManifoldCF is built. To install it on your SharePoint 3.0 machine, follow the directions in the file Installation Readme.txt, found in that directory.

    -