Note: Before reading this section or completing this step, review the Repository Loader chapter in the ATG Repository Guide.

The following procedure shows how to use the Repository Loader’s RMI client RLClient to import file asset metadata into the PublishingFileRepository, and write the file contents to the file system.

  1. If you are running on Windows, set this property:


    to backslash (\):


    Backslash is an escape character in Java properties files. Alternatively, you can set this property using a single backslash via the ACC.

  2. If you import any manually created targeters that store their rule sets in separate .rules files, modify each applicable RuleSetService configuration file to specify the virtual file system that stores the .rules file.

  3. On the asset management server, create a manifest file that identifies the production server directories and files to import into the PublishingFileRepository.

    Each <add> tag should include a type-mapping attribute that specifies the correct TypeMapping component to use for the given file or folder, and its body should specify the file or folder’s path.

    Because you are performing the import in manifest mode, the manifest must specify all folders to be imported. They are not automatically imported as folder content items.

    For example, to import a directory and two HTML files into the PublishingFileRepository, add three <add> tags to the manifest:

      <add type-mapping=

      <add type-mapping=

      <add type-mapping=

  4. On the asset management server, configure the /atg/epub/file/VersionedLoaderEventListener as appropriate for the import operation:

    • For initial import of file assets, do not specify a workspace name. Instead, let the system generate a workspace and workspace name. Using a system-generated workspace is appropriate for initial imports, because the workspace and files should be checked in immediately.

    • Set the property VersionedLoaderEventListener.checkinOnCompletion to true (the default) in order to check in the initial set of file assets. This is particularly important when using an system-generated workspace; if the files are imported into an system-generated workspace but not checked in, there is no way to access the assets via the Business Control Center, because they were not imported into a known workspace—that is, a workspace associated with an existing project.

    For more information about VersionedLoaderEventListener component properties, see the Repository Loader chapter in the ATG Repository Guide.

  5. Start an application that includes the Publishing.base module, or any module that requires Publishing.base. The Publishing.base module starts the RL (Repository Loader) module automatically.

  6. Check that the DYNAMO_HOME environment variable is set on the content development or production server; then change to the <ATG10dir>/RL/ directory and run the Repository Loader’s RLClient. Specify the manifest file you created in step 3 as an argument.

    For example:

    bin/RLClient –h localhost –m /users/joe/temp/initialFileImport.xml

    If the –h argument specifies a host other than localhost, the manifest file path supplied by the -m switch should be on the remote machine.

  7. Because the VersionManager requires a forward slash (/) path separator, on Windows reset the following property to forward slash: