SystemPackage - importSystemPackage
SystemPackage - importSystemPackage
Description :
Deprecated do not use! Instead use importObject
The command imports a a system package that you previously exported (using the exportSystemPackage command) into a BMC BladeLogic system.
It uses a mapping file (mapping.xml) to resolve any conflicts. A DTD for this mapping file is listed at ImportExport : importObject .
Return type : java.lang.Void
Command Input :
Variable Name | Variable Type | Description |
|---|---|---|
sourcePath | String | Name of the directory where the system package you want to import is located. |
mappingFile | String | Location of a mapping file used to resolve any conflicts that occur when importing. |
createGroup | Boolean | Boolean flag to indicate auto creation of parent group |
Examples :
Example
The following example shows a sample XML mapping file.
Script
<?xml version="1.0" encoding="UTF-8"??>
<!DOCTYPE mapping SYSTEM "file://bladelogic.com/dtds/Import-Mapping.dtd">
<mapping>
<system_package_type_mapping>
<source_system_package_type>Windows 2000 Advanced Server</source_system_package_type>
<!--This is the name of the system package type on the importing system to use-->
<target_system_package_type>Windows 2000 Advanced Server</target_system_package_type>
</system_package_type_mapping>
</mapping>
Example
This example shows how to import a system package into a BMC BladeLogic system.
Script
# Location of the import directory
LOCAL_IMPORT_PATH= /c/exports/pkg1
# Mapping file name
MAPPING_FILENAME = /c/exports/pkg1/mapping.xml
# Create directory flag. Set this to true if you want to automatically create a default parent group on the importing system, if one does not already exist.
IS_CREATE_GROUP = "true"
blcli SystemPackage importSystemPackage $LOCAL_IMPORT_PATH $MAPPING_FILENAME $IS_CREATE_GROUP