Administer > Content utilities > Policy on importing content

Policy on importing content

The following table shows the affect of the policy you specify on the command-line for each content type when duplicates are found.

The choices are:

  • overwrite - the default if no policy is specified. The effect of this option is different for each content type as described in the table.
  • duplicate - the effect of this option is different for each content type as described in the following table.
  • skip - for all content types, specifying “skip" means that if a duplicate is found, a message is entered in the session log and the import continues.

See cbt command reference for a complete list of all the available arguments and their meanings.

Policies Used By DET When importing each content type

Content Type

Associated content types

Import policy (Overwrite)

Import policy (Duplicate)

Application Configuration

Application Configuration Template

All attributes are updated in overwrite mode.

New Application Configuration is created and named “Oldname-cbt<random>"

Application Configuration Template

 

All attributes are updated in overwrite mode.

New Application Configuration template is created and named “Oldname-cbt
<random>"

Custom Attributes

NA

Creates and overrides existing keys. The result is the union of the imported key and existing keys.

Same as Install Order Relationship.

Custom Extension

NA

A new version of the script is created

Same as overwrite policy.

Custom Field Schema

NA

Display name is the only field that is updated.

Do nothing on duplication.

Customer

NA

Do nothing on duplication.

Do nothing on duplication.

Please see Synchronizing multimaster meshes with deltas for important information about importing customers.

Folder

  • Package
  • Software Policy
  • OS Sequence
  • Customer

Placeholders for all Folders along the path to this folder are created. All attributes of this folder are updated. Folder contents and associated customers are overlaid on existing data. If --folderacls is specified, folderACLs to any pre-existing user groups are created.

Skip: folders are not duplicated.

Install Hooks

NA

See Unit.

See Unit.

Install Order Relationship

NA

Creates the relationship regardless and override the existing relationship.

Since this is done in the context of the parent node, a new relationship is always created because a parent node is always created - albeit with a different name.

MRL

NA

Always create an MRL in the target mesh using the identical name as in the source mesh.

Same as overwrite.

OS

  • Custom attributes
  • Customer
  • InstallHooks
  • MRL

Content information overrides existing node in target SA mesh without changing its node ID. Content information is overlaid on the existing node.

Content information is renamed by applying a “cbt<random>" suffix to the application name.

OS Build Plan

  • Application Configuration Template
  • Custom attribute
  • Customer
  • Device Group
  • Script
  • Software Policy
  • ZIP Package

Custom attributes are overlaid. Application Configuration Templates, Scripts, Software Policies, Patch Policies and ZIP Packages are overwritten. OS Build Plan description is updated.

If the name of a Build Plan is changed or the Build Plan is moved to a different location after export, the exported OS Build Plan will be imported to the original location as a new OS Build Plan leaving the renamed/relocated OS Build Plan unchanged.

Skip: OS Build Plans are not duplicated.

OS Build Plan content is duplicated as follows:

Application Configuration Templates, Scripts and Server Groups are duplicated

Zip Packages are overwritten

Customers are skipped

New Software Policies are created with name <software_policy>_cbt<random>

Package

NA

Package is uploaded over the existing package and will overwrite the “container" package types: LPP, HPUX Depot, and Solaris Package. These package types will be overwritten with the new data if their new contents (contained packages) are a superset of the old contents. If not, DET will revert to the existing “rename" mode.

If the package already exists in a different folder, it is imported as a new package in the new folder -- the existing package is not moved to the new folder.

Same as overwrite.

Patch

NA

Physical patch package is uploaded and contained units are created in the Software Repository.

AIX LPPs and HPUX Depots, package types will be overwritten with the new data if their new contents (contained packages) are a superset of the old contents. If not, DET will revert to the existing “rename" mode.

Same as overwrite. This is because Server Automation cannot reliably and efficiently determine whether a package in the Software Repository is equivalent to the package being uploaded.

Patch Knowledge

(PATCH_META_DATA)

NA

The patch database is imported into Server Automation, overwriting the existing database, if there is one. The knowledge created by the import will depend on the patch preference settings in the target SA mesh.

Same as overwrite.

Patch Policy

Patch

Description and list of patches are updated.

New patch policy is created and named “Oldname-cbt<random>"

Scripts1Scripts can only be imported by importing the parent folder.

NA

Adds the current version of the imported script to the existing object.

Duplicates the existing object with a new name and adds the current version of the imported script to the duplicate.

Server Compliance Criteria

NA

All attributes are updated in overwrite mode.

New Server Compliance Criteria is created and named “Oldname-cbt<random>"

Server (Device) Group

  • Application
  • Software Policy
  • Custom Attribute
  • Custom Field Schema
  • Patch
  • Server Group
  • Service Level

Group description and type are updated. Dynamic group rules are overwritten. The match “if any rules are met" and “if all rules are met" setting will be updated to reflect what is defined in the export. Custom attributes are overlaid. Attachments to patches, applications and service levels are overwritten.

New server group is created and named “Oldname-cbt<random>".

Service Level

  • Custom attributes
  • Customer

Content information overrides existing node in target SA mesh without changing its node ID. Content information is overlaid on the existing node.

Content information is renamed by applying a “cbt<random>" suffix to the template name.

Template

  • Custom attributes
  • Customer
  • Application
  • Patch
  • OS
  • Service Level

Content information overrides existing node in target SA mesh without changing its node ID. Content information is overlaid on the existing node.

Content information is renamed by applying a “cbt<random>" suffix to the template name.

Unit

Unit script

Units are associated with a physical package, see Package content type above. Virtual units are always associated with existing units in the target SA mesh - this is presumably created as a side effect of uploading the physical package that is also part of the same import session.

Same as overwrite.

Unit Script

NA

Created and overrides existing unit scripts.

Same as overwrite.

User Group

Customer, Server (Device) Group

User group description is updated. In addition, the checked state of features (as seen in the Features and Other tabs) will be updated to reflect what is in the export. The Read, Read & Write, and None settings of customers, node stacks, and client features will be updated to reflect what is in the export. The Read and Read & Write settings of server groups are updated as well.

New user group is created and named “Oldname-cbt
<random>".