DMM Director Online Help › DMM Director › DMM Director Migration File › Migration File Structure

Migration File Structure

The migration file contains the details of your automated migration. Each migration is completely specified in a migration section of the migration file. A migration section includes all elements between each set of <Migration> ….</Migration> tags.

Each option in the migration file has the following format:

<Option Name="DNAFile">
<Value>\\Server1\DirectorData\%DNA_USER_NAME%\DirectorDNA.dna</Value> 
<Type>STRING</Type> 
<DisplayName>How do you want to name and save; identify and apply, the DNA files?</DisplayName> 
<Dependency>Required when the Operation option is set to CreateDNAFile, CreateSEFile, or OpenDNAFile</Dependency> 
<ValidValues>Valid path and file name. May include variables.</ValidValues> 
<Comment>Defines the naming conventions for DNA files, any DMM variable, or AskUser Variable (defined by the AskUser options).</Comment> 
</Option>

The XML tags in the angle brackets are not case-sensitive; however, they must be consistent throughout the migration file. The migration file includes the following elements:

Name (attribute)

Defines the name that matches one of the following options:

• DMM Director options
• DMM option names

Value

Defines the value of the option that must match the type specified in the Type option.

This is a required element.

Type

Lets you define option types. Permissible option types are string, Boolean, or integer.

This is a required element.

DisplayName

Provides the name of the option for display or informational purposes.

Explanation

Provides a more detailed explanation. This is an optional element.

Valid Values

Includes a list of the values that the option can contain.

Comment

Provides a field for the administrator to add any additional information.

The following rules apply to migration files:

• Each migration section specifies one execution of CA DMM and any number of these migration sections can appear in the migration file.
• Each migration must be completely defined within its own migration section.
• All options must be contained within a subsection under the migration section – they cannot appear directly beneath the migration tag.
• There is no restriction on the names or number of subsections or which options appear within them. <FilePath>, <Network>, and all the tags defined are convenient tags, but you can use any tags you want to define.