Skip to Content

Import and export concepts

Using the BLCLI, you can export an object from one BMC Server Automation system, then import it as a new object into another BMC Server Automation system. You can also update certain object types.

You can export and import the following objects:

Objects to export/import

Using BLCLI?

Using GUI?

BLPackages

yes

yes

Component templates

yes

yes

Jobs (except for the job types listed below)
You cannot export/import the following job types:

  • Upgrade Model Objects
  • Distribute Configuration Objects
  • Deregister Configuration Objects
  • Provision Job
  • Virtual Guest Job
  • Application Discovery Job
  • Patching Job (all types)

yes

yes

Depot objects (any type)

yes

yes

System packages

yes

yes

Smart groups (any type)

yes

yes

Extended objects

yes

yes

Config files

yes

yes

Grammars

yes

yes

You can update the following objects:

Objects to update

Using BLCLI?

Using GUI?

BLPackages

yes

no

Component templates

yes

no

Smart groups (any type)

yes

no

Warning

Note

A granular export and import mechanism is available if you want to reduce the risk of import failure due to existing objects on the destination system. For more information, see Granular-import-and-export-concepts.

Alternatively, for a component template you might be interested in the version-neutral export and import processes described in the online documentation for the ContentImportExport name space.

The following topics describe how to export, import, and update BMC Server Automation objects using the BLCLI:

 

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

BMC Server Automation 8.2