Selecting the migration engine - BlueCat Integrity - 26.1.0

Address Manager Administration Guide
ft:locale
en-US
Product name
BlueCat Integrity
Version
26.1.0
Attention:

Change in behaviour - Address Manager v25.1

Address Manager v9.5.0 introduced a different migration engine that was set as the default engine for the migration service. In Address Manager v25.1, the legacy engine has been returned as the default engine for the Address Manager migration service.

Legacy migration engine

The legacy migration engine is the default engine in Address Manager v25.1, so users can simply upload the XML migration file directly through the UI to process the file with the legacy engine.

New migration engine

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

<?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>
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 new engine.

For more information on using the new migration engine introduced in v9.5.0, refer to the Engine behavior and legacy compatibility chapter in the v9.5.x or v9.6.x Address Manager Administration Guide.

Note: For Mac users: Errors can result with the migration package when the built-in zip utility includes __MACOSX folders (UI compress option), as well as if hidden .DS_Store files are included in the package when compressing. The following CLI zip utility command is recommended to ensure no extra files are included in the package: zip -r dir.zip . -x '.*' -x '__MACOSX'