Selecting the migration engine - BlueCat Integrity - 9.5.0

Address Manager Administration Guide
Locale
English
Product name
BlueCat Integrity
Version
9.5.0

New migration engine

As the new migration engine is the default engine, users can simply upload the XML migration file directly through the UI to process the file with the new engine. Uploading a zip package that includes an XML manifest file (as detailed in Optional engine tuning parameters) will also use the new migration engine by default, unless a meta tag is included indicating legacy, as detailed in the following section.

Legacy engine

To process migration XML using the legacy engine, a manifest file must be created and packaged with the migration XML. Set the engine value to legacy.

<?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="legacy"/>
    <file name="test-data.xml"/>
</manifest>
Attention: The manifest file must be named manifest.xml.
Attention: The migration file must be specified in the name attribute of the file element within the manifest.

Zip the manifest XML file with the migration XML file and upload through the UI to process using the legacy engine.