This topic provides information for CDM mapping for Host nodes.
The CIs created are described in this topic.
Removal of duplicated relationships
After upgrade from Discovery 10.2 to 11.0, the direct relationship between a host and an application no longer exists in CMDB. Similarly, in the virtualization model, the direct relationship from virtual BMC_ComputerSystem to physical BMC_ComputerSystem no longer exists in CMDB.
In previous releases, the sync mappings created a denormalized model, in which there were two relationship paths between a BMC_Application CI and the BMC_ComputerSystem CIs that were involved. That created a duplicate relationship path that does not reflect the structure of the application.
For example, consider the simplest possible application model in BMC Discovery, containing just one single SoftwareInstance. There would be a relationship with HasImpact=Yes from the BMC_ComputerSystem to the BMC_SoftwareServer and another relationship with HasImpact=Yes from the BMC_SoftwareServer to the BMC_Application. Then, separately, there would also be a relationship with HasImpact=No from the BMC_ComputerSystem directly to the BMC_Application.
That non-impactful relationship was created so that CMDB sync could keep track of its own state. It is not a part of the impact model, and does not reflect the structure of the application. CMDB sync no longer creates the denormalized non-structural relationship from BMC_ComputerSystem to BMC_Application. The only relationships that are now created are the impactful, structural ones that include the path through software CIs.
In the old virtualization model, the impactful chain would be from virtual BMC_ComputerSystem through BMC_VirtualSystemEnabler, to the physical BMC_ComputerSystem. There would also be a non-impactful direct relationship between the two BMC_ComputerSystem CIs. That denormalized direct relationship is no longer created.
If there is a business requirement for these denormalized relationships, they can be added with sync mapping extensions.
Data models
CMDB version differences
The default mapping works with modern CMDB versions, from version 7.6.03 and later. Old, unsupported CMDB versions have slightly different data models.
- BMC_Impact relationships are not normally created. See the information about impact relationships for more details.
Differences from previous versions of BMC Discovery
Starting from version 10.0, in the model populated by BMC Discovery, the ram attribute is used for storing the physical memory volume and the logical_ram attribute is used for the reported logical memory volume. The BMC_ComputerSystem TotalPhysicalMemory attribute is only set if the ram attribute is populated in Discovery. There is no place in the Common Data Model to store the logical memory information.
BMC_ComputerSystem
A root Host node is mapped to a root BMC_ComputerSystem CI with the following attributes:
Attribute | Details |
|---|---|
Name | The fully qualified name of the host if available, otherwise the unqualified name; if no names are available, the IP address |
NameFormat | " |
ShortDescription | Host |
Description | The host name and the fully qualified domain name separated by a colon |
CapabilityList | A single value corresponding to Server, Desktop, Laptop, or Other |
Domain | Host |
HostName | Host |
isVirtual |
|
LastScanDate | Host |
ManufacturerName | Host |
Model | Host |
PrimaryCapability | Server, Desktop, Mainframe, or Laptop |
SerialNumber | Host |
PartitionId | Host |
TokenId | See TokenId rules below |
TotalPhysicalMemory | Host |
VirtualSystemType | Enumeration value corresponding to the type of virtual machine |
Workgroup | Host |
| ComponentAliases | Component aliases for the host. |
Category | " |
Type | " |
Item | " |
Relationship | Name | Source | Destination |
|---|---|---|---|
BMC_Dependency | STORAGEUSE | BMC_ComputerSystem (Storage system) |
|
TokenId rules
TokenId is an attribute that in some circumstances aids reconciliation of CIs populated by multiple data sources. The following describes how discovery sets TokenId for BMC_ComputerSystem.
For most hosts, TokenId is of the form hostname:DNS domain name.
For some virtual hosts, TokenId contains a UUID:
- For VMware,
TokenIdis of the form "VI-UUID:ABCD-EF-GH-IJ-KLMNOP". Where each letter represents a hexadecimal digit. - For Hyper-V,
TokenIdis of the form "HYPERV-ID:ABCD-EF-GH-IJ-KLMNOP". With Hyper-V, the UUID is only available on the physical machine, so TokenId is only set for virtual machines that have been successfully linked to their hosting physical machines. - For Xen (including Oracle VM),
TokenIdis of the form "XEN-ID:ABCD-EF-GH-IJ-KLMNOP". - For KVM (including RedHat Enterprise Virtualization),
TokenIdis of the form "KVM-ID:ABCD-EF-GH-IJ-KLMNOP".
BMC_OperatingSystem
The root Host is also mapped to a single BMC_OperatingSystem CI, with the following attributes:
Attribute | Details |
|---|---|
Name | Host |
NameFormat | " |
ShortDescription | " |
Description | Host |
ManufacturerName | Host |
MarketVersion | Host |
Model | Host |
OSType | Enumeration value for OS type |
OSProductSuite | Enumeration value for OS product suite |
ServicePack | Host |
VersionNumber | Host |
| Company | Host Company |
Category | " |
Type | " |
Item | " |
Operating system relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
BMC_Processor
The root Host is mapped to a number of BMC_Processor CIs.
- For physical machines, the number of CIs corresponds to the number of physical CPU packages present in the machine.
- For virtual machines, the number of CIs corresponds to the number of logical CPUs the OS is scheduling across.
In some circumstances, it is not possible to discover the number of physical CPU packages in a physical machine. In such cases, no BMC_Processor CIs are created for the machine.
All the BMC_Processor CIs for a host are normally identical to each other. New in BMC Discovery 8.3, they can be different in cases that a physical machine has more than one type of CPU.
Attribute | Details |
|---|---|
Name | " |
NameFormat | " |
ShortDescription | Host |
Description | Description of the processor, its index, and host |
isVirtual | True if the Host is virtual; not set if physical. (Not present in CMDB 7.5.) |
ManufacturerName | Manufacturer of the processor. |
MaxClockSpeed | Host |
Model | Host |
NumberOfCores | Host |
NumberOfLogicalProcessors | Host |
OtherProcessorFamilyDescription | Host |
ProcessorArchitecture | Enumeration representing the architecture |
ProcessorFamily | Enumeration representing the processor family |
ProcessorStatus | 1 — CPU enabled |
ProcessorType | 2 — Central processor |
UpgradeMethod | 1 — Unknown |
| Company | Host Company |
Category | " |
Type | " |
Item | " |
Processor relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
BMC_NetworkPort, BMC_IPEndpoint and BMC_LANEndpoint
Each Network Interface node connected to the root Host in the Discovery model is mapped to a BMC_NetworkPort CI, and its MAC address is mapped to a BMC_LANEndpoint CI. Each of its associated IP addresses are mapped to BMC_IPEndpoint CIs.
Where Discovery has been able to connect a Network Interface node to a Network Device node (via associated port nodes), a BMC_Dependency relationship is created between the two BMC_ComputerSystem CIs representing the host and the network device.
BMC_NetworkPort
Attribute | Details |
|---|---|
Name | NetworkInterface |
ShortDescription | NetworkInterface |
Description | NetworkInterface |
AutoSense | Yes (0) or No (1) or null if not known |
FullDuplex | Yes (0) or No (1) or null if not known |
LinkTechnology | Ethernet (2) |
ManufacturerName | NetworkInterface |
PermanentAddress | NetworkInterface |
PortType | Ethernet (2) |
Speed | NetworkInterface |
| Company | HostCompany |
Category | " |
Type | " |
Item | " |
Each Fibre Channel HBA card node is mapped to the BMC_NetworkPort CI with the following attributes:
| Attribute | Details |
|---|---|
| Name | FibreChannelHBA description and FibreChannelPort wwpn or just FibreChannelPort wwpn |
| ShortDescription | FibreChannelPort wwpn |
| Description | FibreChannelHBA description and FibreChannelPort wwpn or just FibreChannelPort wwpn |
| LinkTechnology | Fibre Channel (4) |
| ManufacturerName | FibreChannelHBA vendor |
| Model | FibreChannelHBA model |
| PermanentAddress | FibreChannelPort wwpn |
| PortType | Fibre Channel (6) |
| SerialNumber | FibreChannelHBA serial |
| Company | HostCompany |
| Category | “H |
| Type | “Card” |
| Item | “Fibre Channel HBA card” |
BMC_NetworkPort relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
BMC_LANEndpoint
MAC addresses in the Discovery data model are stored in the conventional form with colons separating each pair of hexadecimal digits; in the CDM, MAC addresses are stored as just the hexadecimal digits, with no separating colons.
Attribute | Details |
|---|---|
Name | NetworkInterface |
NameFormat | " |
ShortDescription | NetworkInterface |
Description | "MAC address |
Address | MAC address (no separating colons) |
MACAddress | MAC address (no separating colons) |
ProtocolType | Ethernet (14) |
| Company | HostCompany |
Category | " |
Type | " |
Item | " |
BMC_LANEndpoint relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
|
|
|
|
BMC_IPEndpoint
Attribute | Details |
|---|---|
Name | IP Address |
NameFormat | " |
ShortDescription | IP Address |
Description | IP Address |
AddressType | IPv4 (1) or IPv6 (2) |
| Address | IP Address ip_addr |
DNSHostName | IP Address |
| ManagementAddress | Yes (1) if the IP address was used to scan the host; No (0) if not. (Not in CMDB 7.5.) |
ProtocolType | IPv4 (2) or IPv6 (3) |
| PrefixLength | IP Address prefix_length |
SubnetMask | IP Address |
| Company | HostCompany |
Category | " |
Type | " |
Item | " |
BMC_IPEndpoint relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
|
|
|
|
BMC_Dependency | BINDSTO | BMC_LANEndpoint |
|
BMC_IPConnectivitySubnet
Discovery Subnet nodes are mapped to BMC_IPConnectivitySubnet:
Attribute | Details |
|---|---|
Name | Subnet |
ShortDescription | Subnet |
Description | Subnet |
SubnetNumber | Subnet |
AddressType | IPv4 (1) or IPv6 (2) |
PrefixLength | IP Address |
SubnetMask | IP Address |
| Company | HostCompany |
Category | " |
Type | " |
Item | " |
Subnet relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
BMC_Cluster
Host cluster
Host Cluster nodes are mapped to BMC_Cluster:
Attribute | Details |
|---|---|
TokenId | See TokenId rules. |
Name | Cluster |
NameFormat | " |
Description | Cluster |
ShortDescription | Cluster |
| ComponentAliases | Cluster cdm_component_aliases |
| Company | HostCompany |
Category | " |
Type | " |
Item | " |
Host Cluster relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
Software cluster
Software Cluster nodes are mapped to BMC_Cluster:
Attribute | Details |
|---|---|
TokenId | See TokenId rules. |
Name | Software Cluster |
ShortDescription | Cluster |
Description | Cluster |
| ManufacturerName | Publisher from the Pattern maintaining the Software Cluster |
| MarketVersion | Software Cluster |
| Model | Software Cluster |
| PatchNumber | Software Cluster |
| VersionNumber | Software Cluster |
| ComponentAliases | Software Cluster |
| Company | HostCompany |
Category | " |
Type | " |
Item | " |
Software Cluster relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
|
|
|
|
BMC_IPEndpoint (Cluster)
ClusterService node IP addresses are mapped to BMC_IPEndpoint CIs.
Attribute | Details |
|---|---|
Name | IP address |
NameFormat | "IP" |
ShortDescription | Cluster service name |
Description | "ClusterService name:IP address" |
| AddressType | IPv4 (1) or IPv6 (2) |
| Address | IP Address ip_addr |
| ProtocolType | IPv4 (2) or IPv6 (3) |
| Company | HostCompany |
Category |
|
Type | " |
Item | " |
IP address relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
BMC_HostedAccessPoint |
|
|
|
BMC_VirtualSystemEnabler and virtualization
When a physical machine hosts one or more virtual machines, the Discovery model represents it as a number of Software Instance nodes related to the physical Host, one Software Instance per virtual host. In the CDM, the BMC_ComputerSystem corresponding to the physical machine has a BMC_HostedSystemComponents relationship to a single BMC_VirtualSystemEnabler CI. (Strictly speaking, it is one per technology, so a physical machine running more than one virtualization technology could have more than one BMC_VirtualSystemEnabler CI.)
Attribute | Details |
|---|---|
Name | VM type on hostname |
ShortDescription | VM type on hostname |
Description | VM type on hostname |
BuildNumber | Software Instance |
EnablerType | Enumeration representing the type of virtualization technology |
ManufacturerName | Publisher from the Pattern maintaining the Software Instance |
MarketVersion | Software Instance |
Model | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
VersionNumber | Software Instance |
| ComponentAliases | VM cdm_component_aliases |
| Company | HostCompany |
Category | " |
Type | " |
Item | " |
Virtualization relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
The HOSTEDVIRTUALSYSTEM relationship was removed in BMC Discovery 11.0. The direct route from ComputerSystem to ComputerSystem was a duplication of the path through the VirtualSystemEnabler.
BMC_HardwareSystemComponent.
Any Management Controller node with a direct Management relationship to the root Host in the Discovery model is mapped to a BMC_HardwareSystemComponent CI.
Any ManagementController for a HostContainer containing the root Host in the Discovery model is mapped to BMC_HardwareSystemComponent.
There is no way to map the ManagementController's IP information to the CDM.
BMC_HardwareSystemComponent
Attribute | Details |
|---|---|
Name | Management controller name. |
ShortDescription | Management controller name. |
Description | Vendor name, controller model and type. With serial if known. |
| LastScanDate | Management controller last_update_success |
ManufacturerName | Management controller vendor name. |
Model | Management controller model. |
PowerManagementSupported | Yes (0) or null if not known. |
| SerialNumber | Management controller serial number. |
Company | Host Company. |
VersionNumber | Management controller version number. |
| ComponentAliases | Management controller cdm_component_aliases |
Category | "Hardware" |
Type | "Hardware" |
Item | "Management controller" |
Hardware system component relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
BMC_ComputerSystem (Host Container)
HostContainer nodes are mapped to BMC_ComputerSystem representing the partitioned container.
Attribute | Details |
|---|---|
TokenId | Attribute that aids reconciliation of CIs populated by multiple data sources. |
Name | Host Container |
ShortDescription | Host Container |
Description | Host Container |
CapabilityList | "Blade System" (48) or "Other" (2) |
LastScanDate | Host |
ManufacturerName | Host Container |
Model | Host Container |
OtherCapabilityDescription | Host Container |
PrimaryCapability | "Blade System" (48) or "Other" (2) |
SerialNumber | Host Container |
| ComponentAliases | VM cdm_component_aliases |
Company | Host Container Company. |
Category | " |
Type | " |
Item | Host Container |
Host containment relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
BMC_SoftwareServer and BMC_ApplicationSystem
Each SoftwareInstance in the Discovery model is mapped to either a BMC_SoftwareServer CI or a BMC_ApplicationSystem CI:
SoftwareInstancenodes with DDD triggers are directly running on a single host, and are mapped toBMC_SoftwareServerSoftwareInstancenodes composed of otherSoftwareInstancenodes are mapped toBMC_ApplicationSystem.
SoftwareInstance nodes are also mapped (in an indirect manner) to BMC_Product.
Except as noted, the attributes set are the same in BMC_SoftwareServer and BMC_ApplicationSystem.
Attribute | Details |
|---|---|
| TokenId | Attribute that aids reconciliation of CIs populated by multiple data sources.TokenId is of the form "ADDM:hashedkey", where hashedkey is a hash of Software Instance key |
Name | Software Instance |
ShortDescription | Software Instance |
Description | Software Instance |
BuildNumber | Software Instance |
ManufacturerName | Publisher specified in the maintaining Pattern or on the Software Instance |
MarketVersion | Software Instance |
Model | Software Instance |
OtherSoftwareServerType | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
SoftwareServerType | Enumeration representing the type of SoftwareServer. Often 0 meaning "Other". (Only in |
VersionNumber | Software Instance |
| ComponentAliases | Software Instance cdm_component_aliases |
Company | Software Instance Company. |
Category | " |
Type | " |
Item | Product category from the maintaining Pattern |
Item values
The Item attribute is populated from the Pattern that is maintaining the Software Instance. To obtain a list of all the possible Item values, perform the following query in the Discovery Generic Query page:
BMC_SoftwareServer and BMC_ApplicationSystem relationships
As shown in the table, BMC_SoftwareServer and BMC_ApplicationSystem CIs can be related to each other with a BMC_Dependency relationship. This is mapped from both Dependency and Communication relationships between the SoftwareInstance nodes in the Discovery model.
BMC_SoftwareServer and BMC_ApplicationSystem CIs also have relationships to BMC_Product, shown in the Product relationships table.
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
|
|
|
|
BMC_Component | APPLICATIONSYSTEMHIERARCHY | BMC_SoftwareServer (containing) | BMC_SoftwareServer (contained) |
|
|
|
|
| APPLICATIONSYSTEMDEPENDENCY | BMC_SoftwareServer (facet) | BMC_SoftwareServer (main facet)Impacted |
Communication relationships between nodes are mapped to a dependency between CIs.
Relationship | Name | Source | Destination |
|---|---|---|---|
|
| Server (depended upon)
| (dependant)
Impacted |
|
| Client (dependant)
Impacted | Server (depended upon)
|
Observed Communication relationship between nodes mapped to Dependency between CIs. Due to the very high volume of Observed Communication relationships, only those that are part of application models are synchronized.
Relationship | Name | Source | Destination |
|---|---|---|---|
|
| Listening
|
Impacted |
|
|
| Connecting
Impacted |
Management relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
BMC_Dependency | SYSTEMMANAGER | | |
BMC_Dependency | SOFTWAREMANAGER |
| BMC_SoftwareServer First-order SI.BMC_ApplicationSystem Second-order SI. |
Although the manager impacts the CI it is managing, we do not mark the relationship as impactful, to avoid impact cycles.
BMC_Product
BMC_Product represents the installed aspects of a product. BMC Discovery uses SoftwareInstance nodes and associated metadata to provide an accurate picture of the installed products, regardless of how the products are installed. The mapping groups the SoftwareInstance nodes according to the product information on the maintaining patterns, and maintains one BMC_Product CI for each unique product version on the Host. SoftwareInstance nodes with different types can belong to a single product. So, for example, a server running four Oracle database instances and one Oracle TNS Listener would have five SoftwareInstance nodes; those five SoftwareInstances would map to a single Oracle Database BMC_Product CI.
Attribute | Details |
|---|---|
Name | "Publisher product name |
NameFormat | " |
ShortDescription | "product name product version" |
Description | "product name product version on hostname" |
BuildNumber | Software Instance |
ManufacturerName | Publisher from Pattern or |
MarketVersion | Software Instance |
Model | Product name from Pattern or |
PatchNumber | Software Instance |
ServicePack | Software Instance |
VersionNumber | Software Instance |
Company | Host Company. |
Category | " |
Type | " |
Item | Product category from the maintaining Pattern |
Item values
The Item attribute is populated from the Pattern that is maintaining the Software Instance. To obtain a list of all the possible Item values, perform the following query in the Discovery Generic Query page:
Product relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
BMC_ApplicationService
SoftwareComponent is mapped to BMC_ApplicationService.
Attribute | Details |
|---|---|
| TokenId | Attribute that aids reconciliation of CIs populated by multiple data sources.TokenId is of the form "ADDM:hashedkey", where hashedkey is a hash of Software Component key |
Name | Software Component |
ShortDescription | Software Component |
Description | Software Component |
Model | Software Component |
VersionNumber | Software Component |
ApplicationServiceType | Enumeration value representing the service type. Either comes from the component or defaults to unknown. |
Company | Host Company. |
Category | " |
Type | " |
Item | " |
Application service relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
BMC_DataBase
DatabaseDetail nodes representing logical databases are mapped to BMC_DataBase:
Attribute | Details |
|---|---|
| TokenId | Attribute that aids reconciliation of CIs populated by multiple data sources.TokenId is of the form "hosting_ci.TokenId:database_node.type:softwareinstance.instance:database_node.instance" |
Name | DatabaseDetail |
ShortDescription | DatabaseDetail |
Description | Description is of the form |
Model | DatabaseDetail |
Company | Host Company. |
Category | " |
Type | " |
Item | " |
ManufacturerName | Software Instance |
MarketVersion | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
VersionNumber | Software Instance |
BMC_DataBase relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
BMC_Application
BusinessApplicationInstance is mapped to BMC_Application. Contained SoftwareInstance and BusinessApplicationInstance nodes are mapped to corresponding BMC_Component relationships.
Attribute | Details |
|---|---|
Name | Business Application Instance |
ShortDescription | Business Application Instance |
Description | Business Application Instance |
MarketVersion | Business Application Instance |
VersionNumber | Business Application Instance |
Model | Business Application Instance |
| ComponentAliases | Business Application Instance cdm_component_aliases |
Company | Business Application Instance Company. |
Category | " |
Type | " |
Item | " |
Application relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
| BMC_ApplicationImpacted |
|
|
| BMC_ApplicationImpacted | BMC_Cluster |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_SoftwareServer |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application |
|
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_ApplicationService |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_Cluster |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_DataBase |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | ) |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application | BMC_Printer |
BMC_Component | APPLICATIONSYSTEMCOMPONENT | BMC_Application |
|
BMC_ConcreteCollection
FunctionalComponent nodes representing CAM Functional Components are mapped to BMC_ConcreteCollection.
Attribute | Details |
|---|---|
Name | Functional Component |
ShortDescription | Functional Component |
Description | Functional Component |
Model | Functional Component |
Company | Host |
Category | " |
Type | " |
Item | " |
Functional Component relationships
Relationship | Name | Source | Destination |
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| BMC_Cluster |
|
|
|
|
|
|
|
|
|
|
|
|
The relationship between BMC_Application and BMC_ConcreteCollection is used for Functional Components reached from any of the following node kinds:
- SoftwareInstance (first or second order)
- SoftwareComponent
- SoftwareCluster
- DatabaseDetail
- BAI
Dependency relationships
Relationship | Name | Source (Depended) | Destination |
|---|---|---|---|
BMC_Dependency | APPLICATIONSYSTEMDEPENDENCY |
(Impacted) |
|
Relationship | Name | Source | Destination (Dependant) |
|---|---|---|---|
BMC_Dependency | APPLICATIONSYSTEMDEPENDENCY |
|
(Impacted) |
3 Comments
Arkadiusz Juszczak
What version of CDM includes BMC_VirtualSystem class?
Duncan Grisby
Only extremely old obsolete versions. It was mistakenly included on this page. I have removed it.
Arkadiusz Juszczak
A OK in version 2.0 or something afaik. Therefore I was wondering if this class is introduced again in CDM 9.1 or is scope in latter version. Thank you very much for quick reply.
Best regards
Arek