Rule Synopsis
These are the rule/s that determine the target CMDB CI Tables/Classes used by CI Sync for each VMware Asset Type.
The target CI Table/CI Class is used by CI Sync for two purposes:
-
To search for an existing CIs during a CI Update Operation.
-
To write new CIs during a CI Insert Operation.
Rule Details and Default
The default table mappings for Primary/Parent Resource Types are shown below.
|
Primary/Parent Resource Types |
Default Target Class/Classes |
|---|---|
|
VMware |
|
|
vCentre Instances |
cmdb_ci_vcenter |
|
ESX Servers |
cmdb_ci_esx_server |
The default table mappings for Secondary/Child Records are shown below.
|
Secondary/Child Records |
Default Target Class |
|---|---|
|
Datacenters (for vCenter Instances) |
cmdb_ci_vcenter_datacenter |
|
Clusters (for ESX Server Clusters on vCenter Instances) |
cmdb_ci_vcenter_cluster |
|
Resource Pools (for vCenter Instances) |
cmdb_ci_esx_resource_pool |
|
Datastores (for vCenter Instances) |
cmdb_ci_vcenter_datastore |
|
vCenter Networks (for vCenter Instances) |
cmdb_ci_vcenter_network |
|
Virtual Machine Templates (for vCenter Instances) |
cmdb_ci_vmware_template |
|
Virtual Machine Instances (for ESX Servers) |
cmdb_ci_vmware_instance |
|
Custom Fields (for ESX Servers) |
cmdb_key_value |
Override Options
Context
Customers may consider changing these mappings to target different CMDB CI Tables/Classes shown above. This can often be required when existing CIs are already present in the CMDB (in Classes different to those shown below) and CI Sync is expected to correlate to the existing CIs.
Options
-
The target CI Class can be amended per VMware Asset Type.
-
The target Related List/Child Record table can be amended per VMware Asset Type.
Overriding via Connection Settings
Not Available - Requires a Custom Data Sync Rule (and therefore a Syncfish Support Plan to modify the default behaviour)
Additional Information
N/A
Related Rules
N/A