Note: Before reading this section or completing this step, you should be familiar with the concepts described in the following documentation:

The discussion on the Repository Loader in the ATG Repository Guide provides general information on using the Repository Loader, which is supplied with the Adaptive Scenario Engine. This manual supplements that chapter with information specific to using the Repository Loader with ATG Content Administration.

The Repository Loader imports file assets into the ATG Content Administration system, as follows:

  1. Imports file asset metadata into the PublishingFileRepository.

  2. Writes the file contents to the file system.

Because importing the initial set of file assets is a one-time setup process, this section describes how to do so in manifest mode: the files to import are specified in a manifest file that you create and manually submit to the RLClient that performs the import. This manual method of file import is faster than automatic mode.

To import the initial set of file assets into the PublishingFileRepository:

  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.

    For more information about this step, see the Repository Loader section in the Tools chapter.

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

    Each <add> tag should include a typemapping 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, you add three tags like these:

    <add typemapping="/atg/epub/file/typemappers/FileFolderTypeMap

    <add typemapping="/atg/epub/file/typemappers/WWWTextFileAsset

    <add typemapping="/atg/epub/file/typemappers/WWWTextFileAssetType

    For information on the TypeMapping components provided with ATG Content Administration for the default content item descriptors in the PublishingFileRepository, see the Repository Loader section in the Tools chapter.

    For general information on using <add> tags in manifests, see the Repository Loader chapter in the ATG Repository Guide.

  4. On the ATG Content Administration 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 automatically. Using a system-generated workspace is appropriate for this initial import 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 ATG 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 and its properties, see Configuring the VersionedLoaderEventListener later in this manual.

  5. If desired, create on the ATG Content Administration server a .properties file that specifies additional parameters or hints—for example, a batch size for transactions—to be used by the LoaderManager.

    For additional information about this step, see the discussion on RLClient hints in the Repository Loader chapter in the ATG Repository Guide.

  6. 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.

    For information on application assembly and ATG modules, see the ATG Installation and Configuration Guide.

  7. On the content development or production server, make sure your DYNAMO_HOME environment variable is set; then change to the <ATG2007.3dir>/RL/ directory and run the RLClient, the Repository Loader’s RMI client. Be sure to specify the manifest file you created in step 3 as an argument.

    For example:

    bin/RLClient –h localhost
                 –m /users/joe/temp/initialFileImport.xml
                 –p /users/joe/temp/
                 –auth admin:admin

    If the –h argument specifies a host other than localhost, the paths you supply in the –m and –p arguments should exist on the remote machine and not on the machine where the script is executed.

    For more information on all RLClient arguments and how to invoke it remotely, see the section Repository Loader RMI Client in the ATG Repository Guide.

  8. If you are running on Windows, reset this property:


    to forward slash (/). The VersionManager requires a / path separator.

loading table of contents...