Home > Share Point 2010 > Content Deployement with Share Point 2010

Content Deployement with Share Point 2010

  • Introduction
  • Procedure
  • References

Introduction

I have recently gone through the prevailing requirement of updating public site contents, although this feature is provided by all content management systems. But with Share Point we can, not only, change the contents but also allowed to manage the content controls as well as whole site-collections.

Procedure

This post will help you in publishing your site contents from one web application to another web application through SPS 2010,

There will be 2 web applications in your server farm:

  1. Source Site Web Application
  2. Destination site Web Application.

Steps to create Source Web Application:

After Logging in Central Administration as an admin user, Click on “Administration Management > Manage Web Application and then select on “New Application” from top navigation and follow the steps as:

1. Create a new Source Web Application & specify port no and appropriate path as you like and since it is a source application (Admin Web Application) so select “No” for “Allow Anonymous” in Security configuration.

Create a new Source Web Application2. Define the public URL with earlier port and zone as default. And define new Application Pool for e.g. SourceWebApps with appropriate security account user configurable as Administrator role.

Create a new Source Web Application

3. Give the Database Server & its Authentication details & Fail over server if needed.

Create a new Source Web Application4.      Keep other things default or as per your requirement. Now select groups from Service Application Collections.

5.     Choose Customer Experience Improvement Program, if required, for your Source site & click on OK. Then wait

Create a new Source Web Application 6.   Now you have created one Source Application “SourceWebApps” with Url like:http://XXXXXX:3030/

Steps for creating Site Collections under source web application

You need to make a collection site for creating the source site, again under Application Management > Site Collections > click on Create Site collection as below you should be assured that you are creating this top site collection under your Source Web Application from Web application drop down list.

Create a new Source site

1.      Write the text “sourcesite” under sites URL. Choose Template as you like eg. Team Site. Give Primary & Secondary Site Administrators.

Create a new Source site

2.      Select “Quota Template”: Personal site if you require size limitations & then click OK. You can create site, document libraries, etc as per your requirement under top site e.g. http://aiXXX024:3030/sites/sourcesite.

Now after successfully creation of Source site collections you need to make one Destination Web Application” go to steps 1- 6 for creations of “DestinationSiteApps”. You can give this application “Yes” -Allow Anonymous in Security configuration as it will be treated as Public site and you are required to create one top site collection for it with custom template e.g. http://aiXXX024:3030/sites/destinationsite.

site

Now you have to define content deployment path & job for activating this feature, go to CA>General Application Settings >Content Deployment & click on Configure content deployment

content deployement

& then choose “Accept incoming content deployment jobs” & appropriate servers for Import & Export and select “Don’t require encryption” for connection security.

content deployementGive path for Temporary files & No. of reports for Reporting, if required, & Click OK.

After that click on Configure Content Deployment paths and jobs under content deployment > New Path >give Source & destination site credentials with proper Authentication Information &then click OK.

After creating content deployment path successfully create New Job.

Then either schedule job for run or run directly that job & wait until status completes.

Now check your destination site URL.

Please note that content deployment is a one-way process: content is copied from a source site collection to a destination site collection only this content deployment feature does not support round-trip synchronization from source to destination and back again. So, any changes that are made to the destination site collection will remain on the destination site collection only until they are deleted on the destination site collection, or are overwritten by a content deployment job that is set to deploy all content, including content that was previously deployed. Because of this, you should consider restricting permissions on the destination site collection so that users can only view content stored within that site collection.

One limitation in creating content deployment paths is that the source and destination path must exist in different content databases. This is because all of the GUIDs that are used to define sites, Web pages, list, and items will be transferred with the site when it is deployed. For this reason, you cannot deploy a site to the same database as the source site.

If you create a sub site in the destination collection without using the content publishing feature, it will NOT get wiped out by the deployment.  If you happen to have a sub site in the authoring farm with the same path name, your deployment will fail.

As per best practice don’t create sub site directly in the production site.

References:

1.       http://technet.microsoft.com/en-us/library/cc850698.aspx

2.       http://technet.microsoft.com/en-us/library/ee721058.aspx

3.       http://technet.microsoft.com/en-us/library/cc261995.aspx

4.     Hanz blog

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: