DMM Studio Online Help › DMM Studio › Guidelines for Writing Scripts › Guidelines for Scripts to Migrate Application Settings

Guidelines for Scripts to Migrate Application Settings

The process for writing scripts to migrate application settings includes the following major phases:

Research

Follow these steps:

1. Start with a computer that does not have any application installed.
2. Run a difference tool.
3. (Optional) Install a monitoring program to detect the files and registry keys are associated with the application installation.
4. Run the application.
5. Determine whether any other keys are added or modified the first time the application is run.
6. Determine where all the settings are stored and how they are changed with each change in settings.

Design

After the research is complete, design how the script works. Consider the following factors:

• What are the versions of the application settings that can be migrated?
• What are the settings that can be moved between versions?
• How finely do you want to categorize the options?
• How can CA DMM detect the application settings?
• What registry keys indicate that the application settings are installed?
• What are the shortcuts that are on the desktop or on the Start menu program groups?

Writing

• Write the script using the help system.

  Note: If the settings option is the only selection, ensure that the application is installed in the destination computer and all the settings are migrated.

Consider the following conditions about the language functions:

Apply Functions

When you apply keys and values to any initialization files, specify that short names be used.

Debugging

Consider the following points:

• Ensure that CA DMM logging options are set to create a very detailed Debug log of information.
• Try the script with CA DMM on a single computer by saving to a DNA file.
• Review the Error log to determine whether all commands executed properly.
• Check the Debug log to determine what actions are complete.
• Use print statements to print values into the Debug Log so that you can watch variables at different points in the migration.

Testing

Run the script in all expected environments such as within DNA files and across the network.