locked
Deploying SharePoint 2007 Site On Client-Side RRS feed

  • Question

  • I am developing a SharePoint 2007 project which needs to be deployed on the client-side of the customer. The place where the project is being developed and the place where it is to be deployed are at distant geographical locations. Hence,detailed technical support needs to be provided. I am new to SharePoint Deployment and this is my first real-world project which needs to be deployed.
    Please tell me the technical details such as how to package, deploy the project, etc.
    Thanks in advance.
    Saturday, April 11, 2009 6:11 PM

Answers

  • Download the WSP Builder from the follwing URL:

    http://wspbuilder.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=25962

    * Download the 1st one.

    Install it on the Production Server

    Open Visual Studio > Create Project > Visual C# > Click on WSP Builder Project > Create.

    You can see the '12' folder in the Solution Explorer. This is basically a 12 hive folder which is in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\

    Go to this Folder. Now, You need to know the Custom Files which your Production/Development Staff of the project developed for the particular project.

    If there are Custom Files > Create the folder which contains Custom Files under 12 hive in the VS WSP Builder Project at the same level with the same name and case.

    If your project contains dlls as well then create a folder in your VS WSP Builder Project with a name GAC on the same level of 12 folder. Add the dlls in this folder.

    All Files copied. Now, Right Click on WSP Builder Project and > WSP Builder > Build.


    Now, You need to take abc.wsp and import file to the Client's Location.

    On the Client's Server.

    Follow the Steps:

    Copy both files in C:\

    Open Command Prompt. Go to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin

    Write following commands.

    > stsadm.exe -o addsolution -filename C:\YourFile.wsp
    > stsadm.exe -o deploysolution -name YourFile.wsp -url http://servername -immediate -allowgacdeployment -force
    > iisreset
    > stsadm.exe -o createweb -url http://servername/YourSite
    > stsadm.exe -o import -url http://servername/YourSite -filename C:\Import.cmp
    > iisreset

    If there are Features in the WSP Project then add these lines after import and iisreset

    > stsadm -o installfeature -filename YourFeatureFolderl\\feature.xml -force
    > stsadm -o activatefeature -filename YourFeatureFolderl\\feature.xml -url http://servername/YourSite

    (Repeat the last 2 steps of Feature for every feature)

    > iisreset



    That's It

    --- Regards, Sohaib Khan | Software Engineer - MOSS 2007
    Thursday, April 16, 2009 11:13 AM

All replies

  • What do you mean by "on the client side of the customer"?

    If you mean on a system running a client operating system such as XPPro or Vista, then it is not recommended in production to use this but there is a workaround available at the Bamboo Solutions site that makes it possible to install v3 SharePoint on Vista (but not XPPor):

    If you have as I suspect in fact a general question about having two different SharePoint installations - one local, one remote - then please confirm this.

    addition to the above your question might just be that you are developing a system at location A for use at location B. In that case it seems to me that the different locations are irrelevant and all you ought to be asking is how to move a development system to production.


    Please re-phrase your question. Preferably cutting it down to the essential question or questions.




    WSS FAQ sites: WSS 2.0: http://wssv2faq.mindsharp.com WSS 3.0 and MOSS 2007: http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 and MOSS 2007 Books (including foreign language titles) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
    Sunday, April 12, 2009 7:19 AM
  • Deploying SharePoint 2007 Site To Production:

    I am developing a SharePoint 2007 project which needs to be deployed on the customer location for use by their users.
    I am new to SharePoint Deployment and this is my first real-world project which needs to be deployed.
    Please tell me the technical details such as how to create the cabinet file (with .wsp extension),package and deploy the project, etc.
    Thanks in advance.

    Sunday, April 12, 2009 12:43 PM
  • Hello,

     

    I think you could refer to the following articles in MSDN:

     

    Solutions and Web Part Packages

    http://msdn.microsoft.com/en-us/library/ms413687.aspx

     

    The document describes how to create, deploy and localize SharePoint solutions.

     

    For the second question on solution transferring, we need to know some more detailed information about the network and farm topology of the test and production environments. But generally, the article above is helpful for most scenarios.

     

    Thanks.

     

    Best Regards,

    Lionel

    Thursday, April 16, 2009 8:30 AM
  • Download the WSP Builder from the follwing URL:

    http://wspbuilder.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=25962

    * Download the 1st one.

    Install it on the Production Server

    Open Visual Studio > Create Project > Visual C# > Click on WSP Builder Project > Create.

    You can see the '12' folder in the Solution Explorer. This is basically a 12 hive folder which is in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\

    Go to this Folder. Now, You need to know the Custom Files which your Production/Development Staff of the project developed for the particular project.

    If there are Custom Files > Create the folder which contains Custom Files under 12 hive in the VS WSP Builder Project at the same level with the same name and case.

    If your project contains dlls as well then create a folder in your VS WSP Builder Project with a name GAC on the same level of 12 folder. Add the dlls in this folder.

    All Files copied. Now, Right Click on WSP Builder Project and > WSP Builder > Build.


    Now, You need to take abc.wsp and import file to the Client's Location.

    On the Client's Server.

    Follow the Steps:

    Copy both files in C:\

    Open Command Prompt. Go to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin

    Write following commands.

    > stsadm.exe -o addsolution -filename C:\YourFile.wsp
    > stsadm.exe -o deploysolution -name YourFile.wsp -url http://servername -immediate -allowgacdeployment -force
    > iisreset
    > stsadm.exe -o createweb -url http://servername/YourSite
    > stsadm.exe -o import -url http://servername/YourSite -filename C:\Import.cmp
    > iisreset

    If there are Features in the WSP Project then add these lines after import and iisreset

    > stsadm -o installfeature -filename YourFeatureFolderl\\feature.xml -force
    > stsadm -o activatefeature -filename YourFeatureFolderl\\feature.xml -url http://servername/YourSite

    (Repeat the last 2 steps of Feature for every feature)

    > iisreset



    That's It

    --- Regards, Sohaib Khan | Software Engineer - MOSS 2007
    Thursday, April 16, 2009 11:13 AM
  • Hi Khan

    Please guide me

    In our Site having  Sharepoint Designer Workflow,Master Pages, SiteThemes and EventHandlers.
    I deploy the dlls for EventHandler using WSP.

    For other items how will i Deploy it.

    Is I create a template and deploy it in Client production server?
    Is template imcluded Designer workflow and EventHandler registration?

    Please guide me


    Thanks & Regards Jenkins
    Friday, May 22, 2009 8:20 AM
  • Hi Jenkins,

    For deploying your SPD Workflows, Master Pages, Site Themes etc, you need to create folder in the VS 2005 - WSP Project under 12 hive. Folder name should be same and case Sensitive as it is in 12 hive.

    e.g: for Workflows, If you've any Feature named 'JenkinsWorkflow' then in the VS-2005 WSP Project, Under 12 folder, create TEMPLATE then create folder FEATURES under TEMPLATE then create folder JenkinsWorkflow under FEATURES and there files just like there are in FEATURES folder.

    All in All, as per my above thread, you need to create folders in the VS Project just like default folders in 12 hive with same tree.

    Best Regards,

    Sohaib Khan

    Monday, May 25, 2009 2:10 PM