Archiver best practice?
I run a contribution/consumption environment. I am upgrading to 11g and am wondering what the best practice is for Archiver setup between contribution/consumption. Is it best to have 1 Archiver process setup to publish all content up to my consumption environment, or is it better to have one per website? I have a few active websites currently running on WCC. At this time the current process has multiple Archiver jobs that publish content depending on which website the content is assigned to, or type of content it is.
I am wondering how WCC runs Archiver jobs. Is it serial or single thread? Is there a better way?