The Repository Loader includes an RMI client you can use to submit manifests that identify the files you want to be loaded into the repository. This client is named RLClient. To use the RLClient, use one of the scripts found in <ATG2007.3dir>/RL/bin:

RLClient.bat
RLClient.sh

together with the following arguments:

-m [manifestFilePath] -p [propertiesFilePath] -h [hostname] {-r [RMIPort]}
 -auth [username:password] {-s servicename]}

Make sure you have set your DYNAMO_HOME variable before you run the script. The RLClient arguments are as follows:

Argument

Description

-m <manifestFilePath>

The server-side path to the manifest containing the desired load commands. See Using a Repository Loader Manifest for information about the manifest file format.

-mp “<manifestFilePath>“

The server-side path to the manifest containing the desired load commands. Use this argument, rather than the -m argument, if your RLClient and host are running on different operating systems. The manifest path should be enclosed in double quotes. See Using a Repository Loader Manifest for information about the manifest file format.

-p <propertiesFilePath>

Path to a properties file containing additional parameters and hints to the LoaderManager. See RLClient Hints for more information. Optional.

-h <hostname>

Name of the host where the RemoteManifestProcessor is running.

-r <RMIPort>

RMI port of the host where the RemoteManifestProcessor is running. Optional. The port defaults to 8860.

-auth <username:password>

A colon-separated username:password pair. By default, the username and password is tested against the /atg/dynamo/security/AdminUserAuthority. You can specify a different user authority by setting the userAuthority property of /atg/dynamo/repository/loader/RemoteManifestProcessorService.

-s <servicename>

Nucleus address of the atg.repository.loader.RemoteManifestProcessorService component. Optional, defaults to /atg/dynamo/repository/loader/
RemoteManifestProcessorService
.

 
loading table of contents...