Archive Manager Pipelines
Archiving functionality is implemented using Pipelines. Pipelines facilitate the running of simple linear workflows as part of the deployment process.
The Archive Manager consists of the following pipelines for the publish (deploy) and unpublish (undeploy) actions:
| Pipeline | Responsible for... |
|---|---|
| Archiving-Pipeline-Initial | comparing existing URLs and new URLs to find out which resources have remained unchanged (these do not need to be archived again) |
| Archiving-Pipeline | resolving, capturing, and storing URLs published to one or more Web sites |
| Undeployment-Archiving-Pipeline-Initial | resolving and collecting URLs that have been unpublished from one or more Web sites |
| Undeployment-Archiving-Pipeline-Final | capturing and storing URLs unpublished from one or more Web sites (this pipeline picks up where the Undeployment-Archiving-Pipeline-Initial pipeline finishes) |
The reason that the undeployment pipeline is split into an initial and final part is because the archiving action occurs after the deployment action. As a result, undeployment archiving functionality requires that the URLs are collected in a ”pre-undeploy” (initial) pipeline, and then captured and stored in a ”post-undeploy” (final) pipeline.
Pipeline steps
cd_archivemanager_conf.xml configuration file contain different <Step> elements:
<Step> | Archiving-Pipeline-Initial | Archiving-Pipeline | Undeployment-Archiving-Pipeline-Initial | Undeployment-Archiving-Pipeline-Final |
|---|---|---|---|---|
MetaKeyCollectionStep | yes | yes | yes | no |
UrlResolverStep | yes | yes | yes | no |
UrlChangesProcessingStep | no | yes | no | no |
UrlCaptureStep | no | yes | no | yes |
ComponentResolverStep | no | yes | no | yes |
StorageAdaptorStep | no | yes | no | yes |
MetaKeyCollectionStep- This step loops through all items being published or unpublished and collects the MetaKeys for each used to determine which URLs need to be archived based on the changes being published.
UrlResolverStep- This step resolves URLs for the specified Publications.
UrlChangesProcessingStep- This step detects changes in URLs; if the URL of a page changes, it ensures that the new URL is archived and the old one marked as undeployed.
UrlCaptureStep- This step captures all URLs it receives.
ComponentResolverStep- This step inspects all of the fetched responses and resolve the TCM URIs (Content Manager identifiers) for the content items (Components, Component Templates) that were used to create them.
StorageAdaptorStep- This step specifies the storage adapter used and the database where your archived Web site is stored