Skip to Content
Information
This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Exporting and importing with a command utility

This section contains information about using the import/export command-line utility to import and export definitions. Topics include:

Use the following guidelines to run commands from the import/export command-line utility:

  • On a computer with Developer Studio installed locally, set the current directory to the directory that contains the Developer Studio executable (by default, C:\Program Files\BMC Software\ARSystem\developerstudio). The commands must be run in this directory. File arguments without a directory path are created in the current directory.
  • Command-line import and export are provided by the DefinitionImport and DefinitionExport commands. These commands are implemented as Windows batch (.bat ) files.
  • Every command executed opens a separate AR System session, executes the command, and logs out.
  • DefinitionImport and DefinitionExport parse options in the order they are listed in DefinitionExport-and-DefinitionImport-options. Options are interpreted in a predictable order and might not be executed in the order you enter them.
  • You cannot perform an action against two servers with one command. For example, you must issue two commands to export object definitions from one server and import them into another server.
  • Enclose arguments that contain blank spaces or symbols in quotation marks.
Error
Warning

If the AR System server has Record Object Relationships enabled, the relationships are recorded as the objects are created during import. If you import a large application or many object definitions, the server might become highly loaded and unresponsive for a period of time.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

AR System 21.3