Importing templates using a version-neutral mechanism
Use the version-neutral import process to import component templates along with their payloads and referenced objects. This import process works with any zipped export package created during a version-neutral export process or created manually outside of the BMC Server Automation environment.
The version-neutral export and import mechanism allows you to export objects from any BMC Server Automation version 8.x system and import the same objects to any other BMC Server Automation system of the same version or of any later version. During the import of a version-neutral export package, you can preserve any existing objects found on the target system.
For more information about the XML-based content format file contained within the zipped export package and used during the import process, see Format for XML-based content.
To import component templates
The Import wizard opens. In the Component Templates folder, right-click the component template group or folder to which you want to import the component templates and select Import.
- Import Mode Selection panel, choose between a standard import and a version-neutral import.
The remaining steps in this topic describe the version-neutral import process. For a description of the standard import process, see Importing BMC Server Automation objects. On the
- On the Import Source File Selection panel, enter the path to the zipped export package that you want to import (including the name of the .zip file) in the Import from field, or use the hierarchical tree to select the relevant .zip file. Then click Next.
Import Template Selection panel, set the following specifications of template import:On the
Select templates to import
In the hierarchical presentation of the folders and templates contained within the export package that you are importing, select the folders or individual templates to import.
Handling of existing dependencies
Choose one of the following options for handling objects that are referenced by the imported templates and already exist on the target system:
- Overwrite existing objects — Overwrite the objects that exist on the target system with the objects from the source system.
- Keep existing objects — Keep the objects that exist on the target system.
- Abort if there are conflicts with existing objects — Terminate the import process without importing any objects if conflicts are discovered.
Choose one of the following options for the hierarchical positioning of the imported templates under the Component Templates folder on the target system:
- Preserve source group path — Reconstruct the folder path and hierarchy exactly as they exist on the source system and store the imported templates in the same folders.
- Locate templates under selected group (flat) — Store all imported templates in the folder that you selected in step 1, with no hierarchical nesting.
- Locate templates under selected group (preserve path within node) — Reconstruct the folder hierarchy that exists on the source system under the folder that you selected in step 1, and store the imported templates in the same folders.
- Choose one of the following methods to start the import process:
- To continue with the additional steps before starting the import process, click Next.
- To start the import process, without first viewing the list of contents within the imported package or previewing and validating that the import will end successfully, click Finish.
- Import Contents panel, review the list of package contents to be imported.
This list includes templates, BLPackages in the Depot, grammars, configuration objects (configuration files or extended objects), and Property Dictionary objects. For each object, the name, type, and destination location are provided.
If necessary, click Back to return to the previous panels and modify the import settings. On the
To preview and validate the import before running the actual import process:
- Run a preview while you remain in the Import wizard by clicking Preview.
Run a preview in the background by selecting the Run preview in the background check box and then clicking Finish.
All import objects are analyzed (this may take time), and the results are displayed either on the Import Contents panel (if you ran the preview within the Import wizard) or through the Import Preview panel (which is displayed after a background preview).
The results are displayed for each object in the Status and Action columns. For a description of the possible values displayed in these columns, see Import object status and action.
To view more preview details in the log messages issued during the preview process, click Show Log.
If only one object fails, the entire import process will fail. In such a case, check the log for the reason that the object could not be imported. Address the issue by modifying the existing object on the target system, and then try running the import preview process again.
A local configuration object in the imported component template cannot coexist with a global configuration object defined in the Configuration Object Dictionary on the target system. If a configuration file with the same name and path or an extended object with the same name and operating system already exists in the Configuration Object Dictionary on the target system, the import of the conflicting local configuration object is skipped. The imported component template is associated with the global configuration object that already existed on the target system.
Similarly, a global configuration object associated with the imported component template cannot coexist with a local configuration object defined in any component template on the target system. The import process fails, and an error message prompts you to delete or rename the conflicting local configuration object on the target system before you run the import process again.