Working with object definition files during migration

You can work with object definitions in the following ways:

• Export object definitions to AR System .def and .xml formats, which Migrator exports as server-independent.
• Convert .def and .xml files to the .migrator format, which can be launched independently. The files are displayed in their own server windows.
• Migrate objects from a server to a .migrator file, a .migrator file to a server, or between .migrator files.

When converting a .def or .xml file to a .migrator file, the original .def or .xml file remains intact. The newly converted .migrator file is stored within the same directory where the .def or .xml file is stored.

Exporting object definitions on a server

Use the following procedures to export objects on a server (including locked objects) to .def or .xml files. These procedures are useful if you want to generate AR System definition or XML files from within Migrator.

To export objects to .def or .xml files

1. In the left pane of the server window, under AR System Objects, click an object type.
2. In the right pane, select the objects you want to export.
3. Select Tools > Export Definitions.
4. In the Save As dialog box, enter a file name, including the .def or .xml extension, and click Save.
   If the definition file already exists, you can append the existing file.

To export locked object definitions

1. In the left pane of the server window, under AR System Objects, click an object type.
2. In the right pane, select the objects you want to export.
3. Select Tools > Export Locked Definitions.
4. In the Lock Key field of the Object Lock dialog box, enter a lock key of up to 27 characters.
   You must enter a valid lock key consisting of alphanumeric characters (for example, 123456 or abcxyz or abc789 ). You cannot use double-byte characters. Objects with the same lock key are encrypted as a group in the definition file.
5. In the Verify Lock Key field, enter the lock key again.
6. Select a lock type (Hidden or Read Only).
   Filters, filter guides, and escalations can be hidden. For more information about lock types, see Working-with-server-windows-when-performing-migration-tasks.
7. Click OK.
   During the export, locked objects can exist in the same definition file with unlocked objects. Because lock information is encrypted, no one can remove a lock or change the lock type in the definition file.
8. In the Save As dialog box, enter a file name, including the .def or .xml extension, and click Save.
   If the definition file already exists, you can append the existing file.

To export deployable applications

1. Select Tools > Export Application.
2. In the Select Application dialog box, select a deployable application from the list, and click OK.
3. In the Save As dialog box, enter a file name for the application.
   The default file type is .def. To export as an .xml file, select .xml from the File Type field.
4. Click OK.
   The application is exported to the .def or .xml format.

Converting definition files to .migrator format

You can convert object .def and .xml files to the .migrator format for viewing files in Migrator, or for exporting .def and .xml files within Migrator.

You can convert a .def or .xml file in two ways:

• Select Tools > Convert Definition Files. When the Open dialog box appears, select a .def or .xml file, and click Open. A progress bar appears as the file is being converted to the .migrator file format.
• Select File > Open, select a .def or .xml file, and click Open. Remedy Migrator converts the .def or .xml file to a .migrator file with the same name.