locked
Create SharePoint Sites based on WSP Package that contains everything (Sites and List Definitions, Web Parts, Content Types....etc.), then filling this site with content, and how to move those sites with content from staging to production Environment? RRS feed

  • Question

  • Hi,

    Actually I'm confused somehow regarding which strategy or method to follow when moving SharePoint Solution with Content between Staging and Production Environments, here is my scenario below:

    First, we are developing the whole solution as one WSP package which contains: Site Definitions, List Definitions and Instances, Content Types, Master Pages and Page Layouts, Custom Fields, Custom Web Parts, ....etc. Then I'm Creating the whole site structure using WebManifest file under this directory "\14\TEMPLATE\XML" which points to our custom developed site definitions. Now we need to populate this portal with content prior to the go live process, the problem is that there is some content that need to be migrated from old SharePoint portal.

    Questions:

    1- On which environment shall I add this content, Staging or Production? (Remember there is content migration from old SharePoint portal need to be done).

    2- Which method to follow for moving this content from staging to Production, Content Deployment, Content Database Restore…etc.?

    3- Please - if possible - provide me with all options for moving content along with pros and cons.

    4- Does any option have any special effects on performance?

    5- Does any option have any special effects on my development and deployment strategy? (My development and deployment strategy detailed above).

    Kindly provide me with your inputs on those issues based on practical experience.

    Thanks in Advance,

    Hamza

    Saturday, January 28, 2012 11:30 AM

All replies

  • <<the problem is that there is some content that need to be migrated from old SharePoint portal.>>

    just to clarify : do you mean MOSS (SharePoint 2007) or SharePoint 2003 ?


    Serge Luca; SharePoint MVP ; blog: http://sergeluca.wordpress.com/ Devoteam Belgium. http://twitter.com/sergeluca
    Saturday, January 28, 2012 12:45 PM
  • Hi Serge,

    Its from MOSS 2007. Also there is some content that will be added manually on the new portal directly (new content).

    Thanks,

    Hamza AlSughier

    Saturday, January 28, 2012 1:33 PM
  • Migrate your MOSS content db to your SharePoint Server 2010  staging system; then everything will be in SharePoint 2010; use content deployment to move the content from legacy site coll  to your new staging site collection and use content deployment to deploy everything to your production farm.

    Of course deploy your wsp to the staging & production farms before


    Serge Luca; SharePoint MVP ; blog: http://sergeluca.wordpress.com/ Devoteam Belgium. http://twitter.com/sergeluca
    Saturday, January 28, 2012 1:41 PM
  • Hi,

         Content deployment will be the best option to migrate the content as suggested by Serge. Deploy your wsp on the production and staging but do not activate the feature in the production as it is being done by the content deployment.


    Ajeet
    Saturday, January 28, 2012 2:09 PM
  • Answer :1

    Place all your newly developed contents in Production Server . If its list,document library,CSS,script files,master files and site pages and images were about to migrate to new server,then you can user content deployment later.If your old server still had custom controls,webParts and custom workflow then you need to use the backup/restore.

    Answer : 2

    Please avoid the Content database attaching method as you said your WSP package contains custom WebParts.Backup and restore always fine.

     

    Answer : 3
    If you have information policy setting on old server,then you need to maintain the version.So please be remind on IncludeVersion parameter on backup time.You need to maintain the unified look and feel for the old site also.So you might have to update the master page for your migrated sites.

     

    Answer : 4

    If your document library/List were needed to open in datasheet view,you need to manually configure them.
    If you have custom workflow is on,You need to double check them in your migrated site.Some time workflow stopped thats depending upon backup methods.

     

    Answer : 5

    How you placed the custom webpart in a page ? What types of pages you created ? If it is SitePage,You must have permission for each page.If you have application page you need handle the permission on each page as it is available for all sites and users.


    Murugesa Pandian,MCTS
    Saturday, January 28, 2012 2:38 PM
  • Just to make sure we fully understand the context :

     

    do you have 3 servers :

    server 1 : MOSS & content <no code customization?>

    then you did create a SharePoint 2010 solution package

    server 2 : SharePoint Server 2010 staging : what do you do here ? authoring ? or just Quality Assurance ?

    server 3 : SharePoint Server 2010 production here you want old content & new content (same lists ?)

     


    Serge Luca; SharePoint MVP ; blog: http://sergeluca.wordpress.com/ Devoteam Belgium. http://twitter.com/sergeluca
    Saturday, January 28, 2012 2:53 PM
  • Thanks All,

    Actually I'm not going to use the Content Deployment Feature in SharePoint; I have used it before and then it causes too many issues most of them are non-expected.

    So I decided not to use it again. So I'm looking for something much more practical and trustworthy.


    Hamza AlSughier
    Saturday, January 28, 2012 3:13 PM
  • <<I have used it before and then it causes too many issues most of them are non-expected.>>

    "before", do you mean in MOSS ? content deployment has been improved in SharePoint Server 2010, it was let's say....unreliable in MOSS ; much better now...


    Serge Luca; SharePoint MVP ; blog: http://sergeluca.wordpress.com/ Devoteam Belgium. http://twitter.com/sergeluca
    Saturday, January 28, 2012 3:18 PM
  • My context is as below:

    1- I have on old server which have MOSS 2007 installed, I'm just going to migrate some content from this server (pages, documents, list items...etc.), I'm not going to migrate any customizations, sites, libraries or lists. Also I’m not going to rely on this migration only to fill the site with content; there is new content that need to be added to the new SharePoint 2010 portal directly.

    2- We have started our development, and we are relying on SharePoint 2010 solution packages for development and deployment, so all of my development components (Site Definitions, List Instances and Definitions, Custom Fields, Content Types, Modules, Custom Web Parts….etc.) are included in the solution package, even the portal site structure is built using this solution package, this package assembles the infrastructure for my new developed portal solution. Once I deploy this package I just go to the central administration and create new site collection based on my custom site template, which will provision all sites with all above mentioned components.

    3- For the staging server it’s on SharePoint 2010, its purpose supposed to be for Quality Assurance and content authoring in the future, but our client has changed his mind and decided that they are going to do content authoring directly on production farm and use the publishing and approval workflows.

    4- On production farm, which built on SharePoint 2010, we are going to deploy the new developed solution package along with some data needed from old portal (MOSS 2007), plus new authored content. Again I’m going to migrate just pages, documents and list items. I'm not going to migrate any customizations, sites, libraries or lists.

    5- I want to remind you that I’m very concerned in benefiting from my strategy in the development and deployment; All my files are ghosted (not customized), and as long as they are ghosted, so I’m benefiting from the caching techniques of IIS very effectively; as those files are on disk not inside a database.

    Thanks


    Hamza AlSughier
    Saturday, January 28, 2012 3:37 PM
  • so the staging server will only be used for QA (Acceptance Tests) ?
    Serge Luca; SharePoint MVP ; blog: http://sergeluca.wordpress.com/ Devoteam Belgium. http://twitter.com/sergeluca
    Saturday, January 28, 2012 3:51 PM
  • Thanks All,

    Actually I'm not going to use the Content Deployment Feature in SharePoint; I have used it before and then it causes too many issues most of them are non-expected.

    So I decided not to use it again. So I'm looking for something much more practical and trustworthy.


    Hamza AlSughier

    Hi,

         Content deployment has an advantage above other options as it provides:

    1) Content to be deployed with the granular permission (Item level permission) associated with the content.

    2) Activate the custom feature (deployed in the destination site collection) and restore the configuration of the custom web part if involved

    3) Migrate the users with the permission as assigned in the source site collection.

    The Content deployment depends on the infrastructure (any hotfix or update is required) and the correct way of deploying and retracting custom wsp. If the environment follows the two mention path content deployment will work fine.


    Ajeet
    Saturday, January 28, 2012 3:56 PM
  • Hi,

         Since you are not going to migrate the whole content from the site and custom solution will be deployed on the production server, you can save the list/library which you want in the staging/production server as a template. Download the template of list/library change the extension from .stp to .wsp upload the list/library template to SharePoint 2010 site and then you can create the list/library in the site you want.

     

    Please let me know if it helps!!!


    Ajeet
    Saturday, January 28, 2012 4:03 PM
  • if you really don't want to use content deployment and now that you mentioned that authoring will be done in the production farm, indeed saving as a template on MOSS and reimporting could be an option, but is not straightforward; read this post : http://markviky.blogspot.com/2011/01/migrating-list-or-library-from.html

     


    Serge Luca; SharePoint MVP ; blog: http://sergeluca.wordpress.com/ Devoteam Belgium. http://twitter.com/sergeluca
    Saturday, January 28, 2012 4:15 PM
  • Thanks all,

    That’s right, “Save as Template” may help in some cases, but I doubt it will work for pages and pages libraries. Also I already created new list definitions and instances for my lists and libraries in my new developed solution, with new fields and content types. So I’m confused how “Save as Template” will work in such case.

    I think the best option is to create a small tool that maps lists and libraries from the old site to the new site (export old content along with fields, and map that content to the new lists and libraries).

    Let us say that I have moved content from MOSS 2007 portal to the staging environment, which strategy shall I follow to move from staging to production? Shall I use content database backup and restore? Does this have any effects on performance, development and deployment approaches which I’m using? (Please review point #5 in my last reply).

    Thanks Again,


    Hamza AlSughier
    Sunday, January 29, 2012 8:57 AM
  • Hi Hamza,

    If we do deep analysis on this, I would say "Save as Template" is equal to "Database Backup/restore". None of your configuration settings in Web Parts in Site Pages or Custom code implementation in an application is going to be reflected.

    Using Power shell command or through Central Administration is best always for the site which had full of custom developments.

    But your initial question says that you have site and its contents like master pages,css,images and webParts were packaged as WSP.

    So rethink or do get some more insights before using the "Content database migration approach".

     


    Murugesa Pandian,MCTS

    Sunday, January 29, 2012 4:02 PM