This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Extending Delta Data Migration to include customizations

This topic was edited by a BMC Contributor and has not been approved.  More information.

You can add custom forms to the Delta Data Migration package so that you can migrate the data in these custom forms. You can do this manually or with the Custom Form Instruction Generation tool.

You can also update a field mapping file to correct customer-defined fields in the BMC Remedy reserved range.

Manually adding custom forms to the package

  1. Open the Custom_Form_Instructions.xml instruction file in the <migratorInstallFolder>\DeltaDataMigration\Packages\Custom folder.
    The file will contain information that is similar to the instructions XML example.
  2. Provide your custom form name and the unique field IDs (unique index field IDs) in their respective tags.
    Follow the same process for all of the forms that you need to add.
  3. Open the Custom_Form_Package.xml package file in the <migratorInstallFolder>\DeltaDataMigration\Packages\Custom folder.
  4. Provide the instruction XML file names in the package XML file:

    <instructions file="Custom_Form_Instructions.xml type="all" command="migrate" enabled="true">
    <instruction name="Custom_Form_Instructions"> </instructions>

  5. Save the instruction and package XML files.
    Now, you are ready to run the migrate and compare scripts for the custom package. The new package will run in parallel in a separate command window in the same way as the Delta Data Migration out-of-the-box package files.

Adding custom forms to the package by using the Custom Form Instruction Generation tool

If you do not have the list of your custom (non-BMC) regular forms, run the following batch files as outlined in the following procedure:

  • The migratorFindCustomForms.bat utility — Finds all of your custom forms from the AR System server that are not recognized as BMC Software forms. The utility generates a CSV file that includes the list of all custom form names with their unique indexes.
  • The migratorCSV2Instructions.bat utility — Uses the generated CSV file as the input, and creates the Custom_Form_Instructions.xml file for the custom forms in the CSV file.

To add custom forms to the package by using the Custom Form Instruction Generation tool

  1. Navigate to the <MigratorInstallFolder>\Migrator\migrator\DeltaDataMigration\Utilities\migratorUtilities folder.
  2. Run the migratorFindCustomForms utility by using the following syntax:

    migratorFindCustomForms.bat -s <sourceARServerName> -u <adminUserID> -p <adminPassword> -P <ARServerPort>

    For example:

    migratorFindCustomForms.bat -s test.bmc.com -u Demo -p "" -P 2020

  3. Open the Customforms.csv output file in a text editor or spreadsheet application.
  4. If a form is included in the list but should not be migrated, remove the entire line.
    Forms that are used for testing or to keep temporary data should not be included. If you are not sure, it is better to include the form in the migration. Migrating a form multiple times is permitted.

    Note

    You can save the names of forms to be excluded in a separate file, then you can use that file the next time you run migratorFindCustomForms.

  5. Save the changes you made to the Customforms.csv file.
  6. Run the migratorCSV2Instructions utility by using the following syntax:

    migratorCSV2Instructions.bat -i Customforms.csv

    This utility generates an instruction file that BMC Remedy Migrator reads and uses for the migration.

  7. Verify that the output file is Custom_Form_Instructions.xml.
  8. Open Custom_Form_Instructions.xml file, and ensure that the name inside of the xml file has the same name "Custom_Form_Instructions."
  9. Copy the Custom_Form_Instructions.xml files to the Packages\Custom directory. (You can overwrite the same file in the directory.)
    Now, the custom package is ready to be used. On the DDM user interface, when you select Custom, this custom package is selected, and the migration for the custom forms is executed.

Updating a field mapping file if you ran ARCHGID utility before or during an upgrade

If you used the BMC Remedy AR System ARCHGID utility to to fix customer-defined fields in the BMC Remedy reserved range and a field ID was updated, you must add the source and destination field mapping information in a field mapping .arm file.

The ARCHGID utility is not supported. For information about this utility, see https://communities.bmc.com/communities/docs/DOC-19172.

To create or update an .arm file and update the reference in the instruction XML file

Warning

Perform these steps only if you used the ARCHGID utility.

  1. Under the packages folder, open the custom package folder.
  2. Open the instruction file that needs its form mapping information to be updated.
    For some reason, if you have more than one instruction file, open the file which contains the form for which the delta data mapping is available.
  3. Create a mapping (.arm) file and map the custom source field ID to the destination field ID (which has a new ID after running the ARCHGID utility).
    The following figure shows an example of a mapping file:
  4. Add the mapping file name to the form reference in the instruction file, as shown in the following example:

Where to go from here

Post-migration procedures

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. David Petter

    In Step 3, Consider adjusting the path
    from: <migratorInstallFolder>\DeltaDataMigration\Custom folder.,
    to: <migratorInstallFolder>\DeltaDataMigration\Packages\Custom folder.

    The Custom was not found under the DDM folder on a 10/1 product download/install.

    Oct 25, 2013 10:37
    1. Bruce Cane

      Thanks David, I fixed it, too, in Step 1.

      Oct 25, 2013 01:10