Home » Support » Community Server Evolution » SharePoint Integration

Forums

Open Support Ticket

Call Support:
Direct: (214) 420-1337
Toll Free: (877) 522-6334

Monday through Friday
8 a.m. to 6 p.m. Central (GMT-6)

Join our Community
Details
  • 4 Replies
  • 0 Subscribers
  • Postedover 3 years ago
Options

Sharepoint Integration

This question is answered
cas.mendes
Posted by
on Thu, Mar 5 2009 5:47 PM

Hi all,

can someone explain me the difference between the properties that we need to change when performing Sharepoint and Evolution integration?

What should we use in siteCollection and targetWeb properties and what is the difference between them?

Thanks in advance

 
Verified Answer
  • Brendon Schwartz (Telligent)
    Posted by
    on Thu, Jun 4 2009 1:56 PM
    Verified Answer
    Verified by

    The two urls can be the same and they refer to the actual SharePoint web application that you have created. 

    The new documentation does not use the automated bat files, but instead just takes you through the steps to manually deploy them.  I would suggest just using central admin to deploy the files from the Solution Management after you do an stsadm -o -addsolution -file <filename>
All Replies
  • Brendon Schwartz (Telligent)
    Posted by
    on Thu, May 21 2009 5:40 PM

    I am not sure I follow your questions, where are the configuration options you are refering to?

    Thanks,

    Brendon
  • cas.mendes
    Posted by
    on Thu, May 21 2009 6:05 PM

    Hi Brendon,

    in the "Read.me" file included in the Sharepoint Integration Package it's said:

    "Initial Steps: 

    1. Edit the "Install.bat" file. 

    2. Ensure the url points to your site collection url and that the path to STS is correct for your installation of WSS v3."

    In the Install.bat file you have some fields: 

    @echo off

    @SET SPDIR="c:\program files\common files\microsoft shared\web server extensions\12\bin"

    @SET siteCollection=http://moss2007:4950

    @SET targetWeb=http://moss2007:4950

    @SET wsp=CommunityServerSPDeploy

    @SET features=(CSGlobalInit,CSWebParts,CSFeatureResources,CSSearchStapler,CSDocLibSync,CommunityServerFeatures, CSWebServiceInstaller)

    @SET featuresOut=(CSSearchStapler,CSFeatureResources,CSDocLibSync,CSWebParts,CSGlobalInit,CommunityServerFeatures, CSWebServiceInstaller)

    I'm referring to both fields in bold (siteCollection and targetWeb). I can't understand what should go into each one of them.
    Thanks for your reply,
    Carlos

     

     

     

     
  • Brendon Schwartz (Telligent)
    Posted by
    on Thu, Jun 4 2009 1:56 PM
    Verified Answer
    Verified by

    The two urls can be the same and they refer to the actual SharePoint web application that you have created. 

    The new documentation does not use the automated bat files, but instead just takes you through the steps to manually deploy them.  I would suggest just using central admin to deploy the files from the Solution Management after you do an stsadm -o -addsolution -file <filename>
  • cas.mendes
    Posted by
    on Thu, Jun 4 2009 2:07 PM

    Hi Brendon,

    thanks for the info!

    I'm not sure we have the latest Sharepoint Integration Pack.

    We are using version CS_For_Sharepoint_4.1.31106.3070. 

    Should we get a new version to be able to proceed with the centralized deploy?

    If there is a new version can you please provide the link?

    I've been looking for the new Sharepoint installation documentation and I can't find it. On the instructions link the process is still described using installer.bat.

    Thanks,

    Carlos