Hi, It's pretty normal to see the status of a publication job as finished in CMS but not see the pages appear in the log until much later. The gap in between gets larger as the size of the publication job gets larger. The reason for the delay is often due to the way that pages are released on LiveServer.
The default is that a page gets published to the LiveServer, but remains in draft status until all the pages in the job have been published. Then CMS publishes special XML files that release all the previously published pages. The goal is to ensure that pages are not made available to users until all other pages, which they may link to or rely on, have also been published. It is possible to disable this two-step process via a RDServer.ini configuration. I believe the line is releasefileatonce=true, but you may want to check with RedDot (Open Text Web Solutions) Support to double check. Best, - Eric On Aug 28, 4:13 pm, rwagner <[email protected]> wrote: > Thanks guy, you've each given me a little more information that I > already had. > > To help further: > - We do not appear to have any network issues > - We do have "always replace media files" checked, but we may need to > keep that on in the long term for other reasons (in the meantime we > may experiement with that) > > Keep the suggestions coming! > -rw > > On Aug 28, 3:08 pm, Dave Bellous <[email protected]> wrote: > > > > > I had a similar situation after checking "always replace media files" > > in the Publications Settings dialog. > > > Publication works like this (roughly): > > > 1. RedDot writes everything out to /RedDotTemp directory > > (the job moves from an 'active' job - to completed in the publication > > log section at this point) > > 2. Directory or FTP transfer takes place > > > The publication report gets 'drafted' and then rewritten as the FTP > > process occurs. > > > It sounds like the FTP process is hogging the connection - and it's a > > linear process - so while your publishing is multi-threaded, your FTP > > process will queue up like a soup line. > > > If you're republishing all your media files - that can produce a much > > longer publish. I'd have a look at that particular setting in the > > Administer Publication > Project > (action menu) Edit General Settings > > > 6th item in that list (Always replace media files). Uncheck that > > if you're trying to reduce the publish time of your project. > > > You may need to check that box to ensure everything is flushed out > > once a week, but if you're getting great delays - have a look at that > > section. > > > Wayne's suggestion below is a good workaround for the long term - and > > a better setup in general. > > > Luck, > > > .dave > > > On 28-Aug-09, at 9:26 AM , Wayne Bouwmeester wrote: > > > > I guess this may seem like an obvious question, but have your network > > > folks changed anything that may be slowing down the connection to the > > > FTP server around the same time you noticed the significant slowdown? > > > > Something to think about: > > > As a test, I'd create a publishing target to the file server, try a > > > full publish to it, then again the next night (the times may differ > > > depending on your settings) > > > If you get way better response publishing to the file server (I'm > > > guessing you will), I'd look into implementing a product that can push > > > the files out from the file server to ftp server. We always see faster > > > publishing to a file server target, and then you can use best of breed > > > software to move the files after the publish / keep them in sync > > > during the day. One of my clients used winscp and it worked fairly > > > well. I haven't done a lot of research into other tools. > > > > NB - I'm not sure how much better CMS 10 is for FTP vs file server - > > > it may have made great gains. > > > > Wayne. > > > > On Aug 28, 7:47 am, rwagner <[email protected]> wrote: > > >> I want to throw this out to the big brains out there. > > > >> We have a CMS nightly publication that is 6000+ pages and we expect > > >> to > > >> take about three hours to publish to LiveServer. Lately, it's been > > >> taking in excess of 12 hours, and sometimes we have to shut the job > > >> down because it prevents publications from taking place the next day. > > > >> The publication report in the CMS says "finished" but only displays > > >> the media files published, no pages. After that it takes hours and > > >> hours before an email gets send and the rest of the pub report fills > > >> out. During this interval there is an async process called "FTP- > > >> Transfer for PROJECT NAME" that sits in the async queue and does not > > >> permit any other publication jobs to pass through. > > > >> Has anyone out there seen something like this? If so, any ideas on > > >> what might be causing it or how to approach fixing it? > > > >> Much thanks for any help. > > > >> -rw > > > -- > > daveb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
