Locking a Publication
To prevent Content Delivery from publishing after the Archive Manager has failed to archive content from a previous publish action, you need to add a <Processor> element to the cd_deployer_conf.xml file. You can specify on a per-Publication basis whether you want to lock a Publication when archiving fails.
To lock a publication, open the Content Deployer configuration file cd_deployer_conf.xml and add the following code as the first Processor in the <Processors> section:
<Processor Action="Deploy" Class="com.tridion.deployer.Processor">
<Module Class="com.tridion.archiving.modules.GuardingModule">
<Locks FileName="webapps\tcds\log\ArchiveLock.log" Method="ignore">
<Lock Publication="42" Method="fail"/>
<Lock Publication="41" Method="ignore"/>
</Locks>
</Module>
</Processor>
Where:
- The
Lockselement is a container in which you can specify locking per publication. It contains the following attributes:FileNameindicates the directory path where archiving errors are logged and the name of the log file. (If no directory is specified, the file is generated in the current directory.)Methodif an error occurs that does not relate to a specific publication, such as an Archive Manager configuration errors, you can configure the module to lock all publications by setting the method to fail. Specify ignore to not lock the publication. On failure, a generic log file is generated.
- A
Lockelement is used to specify locking for a publication. It contains the following attributes:Publicationindicates the ID of an archived publicationLock Method=""indicates whether the publication is locked (fail) or not (ignore) when archiving fails. On failure, specific log files are generated for each publication.