Batch Files Archive Targets

8-18 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server necessary only in rare situations. For example, you could create a new collection if you want to save disk space by archiving to another system that does not have Oracle Content Server on it. ■ Collections can be created only through the standalone Archiver. For details about using the standalone Archiver, see Section 8.3.2.5, Running the Archiver as a Standalone Application. ■ A collection can be removed from an Oracle Content Server instance, but this only makes it unavailable from the Archiver application; the archive and batch files remain until you delete them from the file system. Structure An archive collection includes the following: Figure 8–8 Collection Structure

8.3.1.3 Batch Files

This section provides information about batch files. Summary 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. Tip: Archiver collections are normally compatible between different versions of Oracle Content Server instances. One possible exception would be User Configuration information that was archived from a pre-3.0 Oracle Content Server instance. The format of the Users database table changed in version 3.0, so this information might not be compatible between pre- and post-3.0 Oracle Content Server instances. File or Directory Description collection.hda file Specifies the archives that are included in the collection. collection.mrk file Internal file used by Archiver. Archive directories Each archive has a subdirectory in the collection. Note: Archiver batch files are not the same as the batch files that are used with the Batch Loader application. Managing System Migration and Archiving 8-19 Structure A batch file subdirectory includes the following: Figure 8–9 Batch File Structure

8.3.1.4 Archive Targets

You can use the archiver to archive the following content: ■ Native files with associated standard metadata values ■ Web-viewable files .pdf, .html, and so forth ■ Metadata fields and changes ■ User information fields ■ Security groups user attributes and settings ■ User updates ■ Subscription types ■ File formats ■ Document types ■ Content types ■ User attributes such as user login, full name, password, e-mail address, and so forth File or Directory Description Content files A subdirectory named 1 in the batch file directory contains a vault structure that is copied from the source Oracle 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 file Lists the custom metadata fields in the source Oracle Content Server instance DocMetaDefinition database table. This file is used by Archiver to create import maps. Note: Content types and user attributes can be exported and imported manually, but cannot be transferred or archived automatically through replication. Table replication can be used, though, to replicate user information. 8-20 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server

8.3.1.5 Using Archive Logs