If the content root for your repository in the file system contains a large number of files, it can take a long time for the FileSystemMonitorService to identify which files and folders need to be loaded into the repository and for the LoaderManager and ContentHandlers to convert the files and folders into repository items. (What constitutes a “large number of files” will vary, depending on your hardware configuration and other factors. However, fewer than 1000 files is not a large number.) In many applications, it will be better to create a Repository Loader manifest file that identifies the files and folders to be loaded, avoiding the need for the Repository Loader to do so.
The following is an example Repository Loader manifest file that adds five files:
<manifest> <add>/main/Dynamo/RL/sample-data/user001.xml</add> <add>/main/Dynamo/RL/sample-data/user002.xml</add> <add>/main/Dynamo/RL/sample-data/user003.xml</add> <add>/main/Dynamo/RL/sample-data/user004.xml</add> <add>/main/Dynamo/RL/sample-data/user005.xml</add> </manifest>
The elements in a Repository Loader manifest file are handled in the order that they appear. As a result, you need to take care that an element does not depend on a subsequent element. For example, remember that a content repository requires a folder hierarchy; do not attempt to add a content item before you add the folder that is to contain it.
The next two sections, Repository Loader Manifest File Document Type Definition and Repository Loader Manifest File Tags, provide more details about the XML format used in creating a Repository Loader manifest file.
