Selecting the migration engine - BlueCat Integrity - 9.5.0

New migration engine

As the new migration engine is the default engine, users can upload the XML file directly through the UI to process the file with the new engine. Users can also upload a zip package with a manifest file that declares new for the engine value:

<?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"/>
    <file name="test-data.xml"/>
</manifest>

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

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>

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