Batch migration is the best method for mass upgrades, deployments and migrations, because it lets you integrate CA DMM with some other processes you may need as part of your migration. In some cases you may need more control or may require dynamically changing settings as part of the migration. You can do that by modifying any options file manually using a text editor, or programmatically using the ATL COM interface.
All settings can be set programmatically by a wrapper application, including all logs locations and levels.
Wrapper or batch files may be used to find the last template, DNA file, and IP connection for a migration. To do this and retain a unique record of each migration for processing or applying the DNA file, you need to copy the default options file for each migration.
DMM settings can be stored statically in the DMM Options file (DNAOptions.xml). The options file is an XML file that defines the CA DMM default behavior.
You can customize the default options file using a text, or XML editor and can place it in a location accessible by the wrapper. The wrapper should copy the file to a folder that is unique for the migration. The wrapper then calls CA DMM with the /O switch along with the name and path for the unique batch file for the migration. To do this, use the following command line option:
/OPTIONSFILE [/O] D:\XML file path\XMLfileName.xml
CA DMM uses this XML file for all operations. Any items that get written back to the XML file (last template file, last DNA file, last IP address) are saved after the migration is completed. When CA DMM has finished, the wrapper may get any information that is needed from the XML file using the same mechanism that was used to populate the file (ATL COM object).
Using the ATL COM object for accessing an XML file, the wrapper can push or pull any necessary information to or from the XML file.
|
Copyright © 2013 CA.
All rights reserved.
|
|