Archiver is a Java applet for transferring and reorganizing Content Server Files and information. Archiver, used in conjunction with the Configuration Migration Utility (CMU) can be used to migrate a complete content server instance, including content from one system to another.
Note: Archiver supports contribution folders for moving content, but only supports moving tables for folders.
Understanding Archiver—
Archiver consists of 3 elements overall, archive structure, collections, and batch files.
Archive Structure:
An archive is a set of content files and their associated batch files. Each archive has its own subdirectory in the collection it belongs to.
An Archiver subdirectory includes the following:
Batch File Directories – Each batch file has a subdirectory in the archive. Default format is yy-MMM-dd_HH.mm.ss_SSS
Temp Directory –Contains transferred zip files.
archive.hda – Specifies information about the archive, such as export and import settings, the export query, field and value import maps, archiving history, and so forth.
doctypes.hda – Lists the content types (DocTypes database table) in the source Content Server instance. This file is present only if content types were exported.
exports.hda – Specifies the batch files that are included in the archive.
users.hda –
Lists the user attributes (Users database table) in the source Content Server instance. This file is present only if user attributes were exported.
Collections:
A collection is a set of archives on a particular content server instance.
collection.hda – Specifies the archives that are included in the collection.
collection.mrk – Internal file used by Archiver.
Archive directories – Each archive has a subdirectory in the collection.
Batch Files:
A batch file is a text file that contains the file records for archived content items. Batch files describe the metadata for each exported revision.
- A new batch file subdirectory is created each time an archive is exported.
- Each batch file contains up to 1000 file records. If an export contains more than 1000 revisions, a new batch file is created.
Content files -A subdirectory named ‘1’ in the batch file directory contains a vault structure that is copied from the source Content Server instance. If web-viewable files are being archived, this subdirectory also contains a weblayout structure.
Batch File – Specifies the metadata for each revision that was exported. Batch files are HDA files that are named with a unique number generated by Archiver. For example, 0335150414~1.hda.
docmetadefinition.hda – Lists the custom metadata fields in the source Content Server instance (DocMetaDefinition database table). This file is used by Archiver to create import maps.
Need assistance with WebCenter Content Archiver or anything else related to WebCenter? Contact us for migration assistance, including how to speed up Stellent and WCC migartions by up to 30% using Inspired ECM’s content migration accelerator.
This article was written from Oracle’s guide on Administering 12.2.1.3.0 WebCenter Content: https://docs.oracle.com/middleware/12213/wcc/webcenter-content-admin/GUID-D6CDC8D3-28E7-42B5-99F9-096D0BFCAC82.htm#WCCSA913
