Hi Tony,
I had somewhat similar situation at a client where we could not export the whole site, as some parts of the site were to be updated by users on the destination, so job was failing as updates were happening on both ends. I went with moving those lists to a sub-site and excluded the sub-site from the Job, ( this required some change of code and links but luckily was not too much in our case.) OOTB gives things like email notification and good error info (Install Nov 09 hotfix for this), reports job history etc which is quite useful. Doing something custom will take time and testing as we will have to export content than move content file to destination and run import when content arrives and own logging, etc. For custom code I will * Export content * Keep change token * Move content to destination server * Once content is copied, notify the import job and start importing * Email errors or success On Tue, Jun 1, 2010 at 6:41 PM, Tommy Segoro <tommy.seg...@l7.com.au> wrote: > Peter, > > > > It is possible. You can either use the Content Deployment Wizard as > suggested by Ajay, I think the only downside to this is it can’t be > scheduled but it has worked very well for me. > > > > Another way is to write a simple batch command that uses SPImport and > SPExport class (of the object model) to selectively deploy content from > source to destination server. > > > > I will personally use the two approaches above because you can select what > content you want to export down to a single list item. The OOTB 2007 CDT > (Content Deployment Tool) and stsadm commands only support site-level export > and not item level. > > > > > > Cheers, > > Tommy > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *Peter Milliner > *Sent:* Tuesday, 1 June 2010 1:20 PM > > *To:* ozMOSS > *Subject:* RE: SharePoint 2010 Web publishing > > > > Thanks for that. Just need clarification. I have had a look at content > deployment and understand the process of publishing from authoring to > production via content deployment. > > > > We will be having an authoring site (maybe a staging site) and a production > website. > > > > Can we publish content (some not all) from our intranet site to the > authoring site without 3rd Party tools – just need to know if this is > possible with OOB functionality. > > > > I.e. we are considering having course information etc stored on intranet > and managed on the intranet but require it be published to our authoring > site and then to our website. > > > > Cheers > > Peter Milliner > > Bendigo TAFE > > SharePoint Administrator. > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *Jeremy Thake > *Sent:* Tuesday, 1 June 2010 2:02 PM > *To:* ozMOSS > *Subject:* RE: SharePoint 2010 Web publishing > > > > Take a look at Content Deployment Jobs and Content Deployment Paths. This > can handle this to a certain degree OOTB. > > > > 3rd Party tools are available such as RepliWeb to handle this also. > > > > Cheers, > > > > *Jeremy Thake* > > *SharePoint Evangelist* > > *Microsoft Virtual Technology Specialist* > > m: +61 400 767 022 – b: wss.made4the.net – t: @jthake > > Founder of SharePointDevWiki.com > > > > [image: Description: Beschreibung: Beschreibung: Beschreibung: > Beschreibung: Beschreibung: cid:image002.png@01CA1CD1.CC0D80A0] > > [image: Description: Description: cid:image001.jpg@01CA848B.2108B5E0] > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *Peter Milliner > *Sent:* Tuesday, 1 June 2010 7:45 AM > *To:* ozMOSS > *Subject:* SharePoint 2010 Web publishing > > > > Hello all, > > > > Just need some advice. We are at the moment in the planning stage for > SharePoint 2010 implementation. > > > > We will be using it for our intranet/extranet and website. > > > > The question that has been asked is can we publish from intranet to staging > site then to website with out of the box functionality and workflows (and > maybe a bit of custom workflow using SharePoint designer). > > > > The marketing department want to keep all their assets on their intranet > site i.e. articles, pictures, pages but when ready to publish are sent to > staging website and then eventually to website etc. > > We will also have certain policy pages that are stored on intranet and that > will need to be published to web > > > > From what I have researched and read I thought this could be achieved by > content types and web publishing features of SharePoint 2010 but my manager > has received conflicting advice – advising that more in depth > *custom*solution would need to be implemented for this to occur OR all > content and > assets for website would need to be on the staging site and edited and > stored on the staging site. > > > > Any advice appreciated > > > > *Peter Milliner* > > _______________________________________________ > ozmoss mailing list > ozmoss@ozmoss.com > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss > >
<<image002.jpg>>
<<image001.png>>
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
