The following optional meta
elements can be added to the manifest file
to determine engine behavior. The elements are added within the
manifest
element in the following format:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE manifest PUBLIC "-//BlueCat Networks/Proteus Migration Manifest 1.0//EN" "http://www.bluecatnetworks.com/proteus-migration-manifest-1.0.dtd">
<manifest>
<meta name="engine" value="new"/>
<meta name="{name}" value="{value}"/>
<file name="test-data.xml"/>
</manifest>
For example, the on-exception
flag is declared as follows:
<meta name="on-exception" value="stop"/>
Supported migration engine tuning parameters (optional):
Name | Supported value(s) | Default value | Description |
---|---|---|---|
on-exception | stop, continue | continue | Continue migrating when an exception occurs, or stop. |
max-batch-size | [integer] | 5000 | The maximum number of records to process in each batch. |
failed-batch-retry-segments | [integer] | 10 | When a batch fails, retry in segments. The value specifies how many sub-batches the failing batch will be divided into. |
verbose-logging | [boolean] | true | Display migration table. |
brief-stats-logging | [boolean] | false | Display full migration statistics in the log file. |
clear-sessions-on-success | [boolean] | true | Clear Hibernate session after each successfully processed batch. |
lock-parent-when-child-added-or-removed | [boolean] | true | Notify the parent entity of a bulk children deletion. |