The Content Deployment Settings are configured via Central Administration under Operations
Note:
- The site you deploy content to should use a separate content database from the source site.
- The site you deploy to must be initially created as a blank site.
- You can deploy content to sites with all relationships - ie: within a farm, between 2 web apps or between separate farms.
To set up content deployment between farms:
- Configure content deployment settings
- Enable content deployment jobs in Central Administration by setting CDS to Accept incoming content deployment jobs.
- Set the import & export servers
- Set the connection security to Do not require encryption
- Create a new blank site in the destination farm.
- Create a new Content Deployment Path
- Assign a name & description
- Select the source web application & site collection.
- Assign the URL for the destination Central Administration Server eg: http://dev01w2k3:11111
- Click on the Connect button.
- Select the desitination web application & site collection.
- Select whether you want to deploy user names & security information.
- Create a test one time deployment job
- Assign a name & description
- Select the content deployment path
- Specify whether the job should be site specific or accross an entire site collection.
- Leave the frequency & options as their default values.
- Click Ok.
- Run the one time test deployment job
- Open the One time deployment job drop down list and select Run Job.
- Refresh the page so that Running is displayed in the status column. Click on running to view the deployment process report page.
- If successful the status will change to Successful on completion.
- Schedule the Quick Deploy job
- Assign the frequency of the schedule.
- Check the quick deploy users.
- Set up notifiaction if required.
- Assign Quick Deploy content in the source website
- Go to your source website and edit a page.
- Publish your changes.
- From the Tools drop down list select Quick Deploy.
- The changes will be updated at the next scheduled job.
No comments:
Post a Comment