The LoaderManagerImpl class implements the interface atg.repository.loader.LoaderManager. A LoaderManager component of type LoaderManagerImpl accepts Repository Loader jobs. Repository jobs can be initiated from two sources:
RLClient (Repository Loader RMI client)
In both cases, the LoaderManager component passes the files to a TypeMapper component, which determines how to process them. Alternatively, the TypeMapping can be specified directly or in a manifest file.
Setting the repository path separator on Windows
Before submitting an import job to the LoaderManager on Windows, the target repository’s pathSeparator property must be set to backslash (\). After the import completes, reset this property to forward slash (/).
Note: If you set this pathSeparator directly in a properties file rather than in the ACC, use this format:
pathSeparator=\\
LoaderManager Properties
A LoaderManager component has the following configurable properties:
Property | Description |
|---|---|
| The number of cancelled jobs that can be kept in the queue and are viewable in the Repository Loader Administration Default: |
| The number of completed jobs that should be kept in the queue Default: |
| The number of files to handle in a single transaction. This value can be overridden by a batch size argument provided in the Default: |
| The default TypeMapper that the LoaderManager uses if no TypeMapper is provided in the LoaderManager methods If a manifest file specifies its own TypeMappings, those have precedence. Type: Default: |
| An array of components that listen to Type: |
| An Type: Default: |
| A string to prepend to Default: |
| The name of the Default: |
| The number of threads used in the jobs queue Default: |
| An array of components that listen to error Type: Default: |
| An array of components that listen to add, update and remove Type: |
| The number of suspended jobs that should be kept in the queue Default: |
| A Boolean property, specifies whether to suspend or cancel failed jobs. Default: |
Error policies
The LoaderManager uses a configurable error handling policy, defined by the Repository Loader’s ErrorPolicy component. Each job processed by the LoaderManager might contain files that cause exceptions to be thrown. The LoaderManager consults the ErrorPolicy component to determine how to handle exceptions. All exceptions are logged. The Repository Loader sets a success state for each job and each batch. ErrorPolicy methods also determine how to proceed after encountering a problem while processing a job:
ErrorPolicy method | Returns |
|---|---|
|
|
|
|
|
|
