Importing BMC Server Automation objects
You can import system objects from a file system into BMC Server Automation by using the Import wizard. The behavior of the Import wizard depends on the type of object you plan to import.
When you import an object, the import process places imported objects into a default group. You must review those group assignments and, if necessary, assign the imported objects to their correct locations. Optionally, you can instruct the import process to create a group structure on the importing system that matches the group structure on the exporting system, and then assign the imported objects to those groups. In this way, the importing system can have a group structure identical to the exporting system. The import process cannot create smart groups.
If you import an object that includes any associated objects stored in the file server of the exporting system, those associated objects are stored in a directory in the file server of the importing system. The directory on the importing system's file server is called /imported. For example, if you import a component template that includes a BLPackage, and the file server on the importing system is a directory called /storage, the imported BLPackage is placed in the /storage/imported directory.
If you import an object that includes references to URL-based objects, those objects are not copied into the importing system.
You can only import system objects into the same version of BMC Server Automation from which the objects were exported.
When you export or import a Workflow Job, the targets, server groups, and child jobs that are associated with the job through input parameters are not included in the export or import. You must define these objects on the target system or import them to the target system before you import the Workflow Job.
To import an object
Select the import target by using one of the following methods:
- In the Component, Component Templates, Depot, Jobs, or Servers folder, select the folder or group to which you want to import an object. Right-click and select Import from the pop-up menu.
- Select Configuration > Config Object Dictionary. Then, click Import Configuration Object
The Import wizard opens. .
- If you selected a component template folder or group for import in step 1, choose between the standard import and the version-neutral import.
The rest of this section describes the standard import process. For a description of the version-neutral import process, see Importing templates using a version-neutral mechanism.
Use the Import wizard, as described in the following topics:
- Import - Select Import Source Directory
- Import - Import contents
- Import - Select destination grammars
- Import - Select destination group
- Import - Select remediation groups
- Import - Map Missing Servers and Server Groups
- Import - Map Missing Properties
- Import - Property Values Mapping
- Import - Map Existing System Package Types
- Import - Map Missing BLPackages
- Import - Map Missing Component Templates
- Import - Map Missing Depot Objects
- Import - Map Missing Component Discovery Jobs
- Import - Map Missing Compliance Jobs
- Import - Map Missing Deploy Jobs
- Import - Map Missing Network Shell Scripts
- In some situations, after you specify a source directory (through the Select Import Source Directory panel), a dialog box warns that the import process cannot automatically map all properties in the imported object to properties on the destination system. You can map these properties manually later in the import procedure.
Note that the properties from the imported object overwrite the values defined for those properties at the target. However, for any property that you need to keep the local value at the target server, you must restore the property value after the import. For example, the STAGING_DIR property in the built-in Server property class.
- After completing the last step of the wizard, click Finish.