BMC Atrium CMDB Adapter For HP UCMDB Installation Guide

UCMDB Adapter TQL Documentation
For HP UCMDB 9.x

Table of Contents
CI - BMC_COMPUTERSYSTEM............................................................................................................3
CI - BMC_OPERATINGSYSTEM...........................................................................................................4
CI - BMC_IPENDPOINT..........................................................................................................................5
CI - BMC_LANENDPOINT......................................................................................................................6
CI - BMC_PRODUCT...............................................................................................................................7
CI - BMC_HARDWARESYSTEMCOMPONENT..................................................................................8
CI – BMC_NETWORKPORT................................................................................................................10
CI – BMC_CLUSTER.............................................................................................................................12
CI – BMC_ PROCESSOR.....................................................................................................................13
CI – BMC_VIRTUALSYSTEMENABLER............................................................................................14
CI – BMC_MEMORY..............................................................................................................................16
CI – BMC_DATABASESTORAGE........................................................................................................17
CI – BMC_DATABASE...........................................................................................................................18
CI – BMC_SOFTWARESERVER.........................................................................................................19
CI – BMC_LOGICALDISK.....................................................................................................................20
CI – BMC_REMOTEFILESYSTEM......................................................................................................21
CI - BMC_RESOURCEPOOL...............................................................................................................22
CI - BMC_APPLICATION......................................................................................................................23
CI - BMC_BUSINESSSERVICE...........................................................................................................24
CI - BMC_ORGANIZATION...................................................................................................................25
CI - BMC_IPCONNECTIVITYSUBNET...............................................................................................26
Relationship CI – VirtualHostRelation BMC_DEPENDENCY Relation...........................................27
Relationship CI – SoftwareServer BMC_COMPONENT Relation...................................................28
Relationship CI – NETDEVICE_HOST Relation................................................................................29
CI - BMC_MAINFRAME.........................................................................................................................30
CI - BMC_COMPUTERSYSTEM
Transformation - ComputerSystem9 and Delete_ComputerSystem9.ktr
TQL’s used. - node_bmccomputersystem
CI Elements in TQL - NODE
QUERY Node Properties
a. NODE
Attributes with Search Criteria present on Query node.
Parameterize
Criteria
d
Y LastModifiedTime Greater than or Equal <last_modified_time>
Y LastModifiedTime Less than or Equal <last_modified_time>
Use of TQL.
This TQL is used to fetch data from UCMDB from NODE and its sub types CLASS to populate data in
BMC_ComputerSystem. When calling the TQL for data pull we pass the parameterized date parameters
to get the CI data records for Initial Load/ Delta Load based on the last execution time of the
Transformation Job.
CI - BMC_OPERATINGSYSTEM
Transformation - OperatingSystemRelation9.ktr and Delete_OperatingSystem9.ktr
TQL’s used. - node_bmcoperatingsystem
CI Elements in TQL - NODE
a. NODE
Parameterize
Criteria
d
N DiscoveredOSName Not equal “NULL”
Use of TQL.
This TQL is used to fetch data from UCMDB from NODE and its sub types CLASS to populate data in
BMC_OperatingSystem. When calling the TQL for data pull we pass the parameterized date parameters
Transformation Job. The DiscoveredOSName attribute is checked so as to get the records which are
complete and contain Operating System information.
CI - BMC_IPENDPOINT
Transformation - BMC_IPEndPointRelation9.ktr and Delete_IPEndPoint9.ktr
TQL’s used. - ip_address_bmcipendpoint
CI Elements in TQL – IpAddress, IpSubnet and Node
a. IpAddress
Parameterize
Criteria
d
b. IpSubnet
No search criteria.
c. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from IpAddress and its sub types CLASS to populate data in
BMC_IpEndPoint. When calling the TQL for data pull we pass the parameterized date parameters to get
the CI data records for Initial Load/ Delta Load based on the last execution time of the Transformation
Job.
CI - BMC_LANENDPOINT
Transformation - LANEndPointRelation9.ktr and Delete_LANEndPoint9.ktr
TQL’s used. - physical_port_bmclanendpoint
CI Elements in TQL – PhysicalPort, Node and RunningSoftware
a. PhysicalPort
Parameterize
Criteria
d
b. RunningSoftware
No search criteria.
c. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from PhysicalPort and its sub types CLASS to populate data
in BMC_LanEndPoint. When calling the TQL for data pull we pass the parameterized date parameters to
get the CI data records for Initial Load/ Delta Load based on the last execution time of the Transformation
Job.
CI - BMC_PRODUCT
Transformation - ProductRelation9.ktr and Delete_Product9.ktr
TQL’s used. - installed_software_bmcproduct
CI Elements in TQL – InstalledSoftware, RunningSoftware and Node.
a. InstalledSoftware
Parameterize
Criteria
d
N NOT (Display Label Like “HotFix%”)
N NOT (Display Label Like “Security Update%”)
b. RunningSoftware
No search criteria.
c. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from InstalledSoftware to populate data in BMC_Product.
When calling the TQL for data pull we pass the parameterized date parameters to get the CI data records
for Initial Load/ Delta Load based on the last execution time of the Transformation Job. The fixed
condition on Display Label attribute is applied as Security Updates and Hotfix should not be loaded “by
default” into the BMC_Product.
CI - BMC_HARDWARESYSTEMCOMPONENT
Transformation - HardwareSystemComponentRelation9.ktr and

Delete_HardwareSystemComponent9.ktr
TQL’s used. - node_element_bmchardwaresystemcomponent, node_bmchardwaresystemcomponent
CI Elements in TQL – NodeElement and Node.
1. node_element_bmchardwaresystemcomponent
a. NodeElement
Parameterize
Criteria
d
N CI Type Equal "DiskDevice"
N OR (CI Type Equal "Fan")
N OR (CI Type Equal "HardwareBoard")
N OR (CI Type Equal "MemoryUnit")
N OR (CI Type Equal "PowerSupply")
N OR (CI Type Equal "Storage Processor)
b. Node
No search criteria.
2. node_element_bmchardwaresystemcomponent
a. Node
Parameterize
Criteria
d
b. NodeElement
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from NodeElement ("DiskDevice", "Fan", "HardwareBoard",
"MemoryUnit", "PowerSupply" and "Storage Processor") to populate data in BMC_HardwareSystem.
for Initial Load/ Delta Load based on the last execution time of the Transformation Job. The condition on
CI Type attribute is applied so as to get data only for selected CI Class.
CI – BMC_NETWORKPORT
Transformation – NetworkPortRelation9.ktr and Delete_NetworkPort9.ktr
TQL’s used. – Physical_port_bmcnetworkport and interface_bmcnetworkport
CI Elements in TQL:
1. physical_port_bmcnetworkport – PhysicalPort, Node & RunningSoftware

2. interface_bmcnetworkport – Interface, Node & PhysicalPort
1. physical_port_bmcnetworkport
a. PhysicalPort
Parameterize
Criteria
d
b. Node
No search criteria.
c. RunningSoftware
No search criteria.
2. interface_bmcnetworkport
a. Interface
Parameterize
Criteria
d
b. Node
No search criteria.
c. PhysicalPort
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from PhysicalPort, Node, RunningSoftware and Interface to
populate data in BMC_NetworkPort. When calling the TQL for data pull we pass the parameterized date
parameters to get the CI data records for Initial Load/ Delta Load based on the last execution time of the
Transformation Job.
CI – BMC_CLUSTER
Transformation – ClusterRelation9.ktr and Delete_Cluster9.ktr
TQL’s used. – cluster_bmccluster
CI Elements in TQL – Cluster & Node.
a. Cluster
Parameterize
Criteria
d
b. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Cluster and Node to populate data in BMC_Cluster.
for Initial Load/ Delta Load based on the last execution time of the Transformation Job.
CI – BMC_ PROCESSOR
Transformation – Processor9.ktr and Delete_Processor9.ktr
TQL’s used. – cpu_bmcprocessor
CI Elements in TQL – CPU & Node.
a. Cpu
Parameterize
Criteria
d
b. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Cpu and Node to populate data in BMC_Processor.
CI – BMC_VIRTUALSYSTEMENABLER
Transformation – VirtualSystemEnabler9.ktr and Delete_VirtualSystemEnabler9.ktr
TQL’s used. – Hypervisor_bmcvirtualsystemenabler and node_bmcvirtualsystemenabler
CI Elements in TQL:
1. hypervisor_bmcvirtualsystemenabler – Hypervisor & Node

2. node_bmcvirtualsystemenabler – Hypervisor & Node
1. hypervisor_bmcvirtualsystemenabler
a. Hypervisor
Parameterize
Criteria
d
b. Node
No search criteria.
2. node_bmcvirtualsystemenabler
a. Node
Parameterize
Criteria
d
b. Hypervisor
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Hypervisor and Node to populate data in
BMC_VirtualSystemEnabler. When calling the TQL for data pull we pass the parameterized date
Transformation Job.
CI – BMC_MEMORY
Transformation – Memory9.ktr and Delete_Memory9.ktr
TQL’s used. – memory_bmcmemory
CI Elements in TQL – Memory & Node.
a. Memory
Parameterize
Criteria
d
b. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Memory and Node to populate data in BMC_Memory.
CI – BMC_DATABASESTORAGE
Transformation – DatabaseStorageRelation9.ktr and Delete_DatabaseStorage9.ktr
TQL’s used. – dbdatafile_bmcdatabasestorage
CI Elements in TQL – DB Data File & Database.
a. DB Data File
Parameterize
Criteria
d
b. Database
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from DB Data File and Database to populate data in
BMC_DataBaseStorage. When calling the TQL for data pull we pass the parameterized date parameters
Transformation Job.
CI – BMC_DATABASE
Transformation – DataBaseRelation9.ktr and Delete_Database9.ktr
TQL’s used. – database_bmcdatabase
CI Elements in TQL – Database, Node and RunningSoftware.
a. Database
Parameterize
Criteria
d
b. Node
No search criteria.
c. RunningSoftware
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Database, Node and RunningSoftware to populate data
in BMC_DataBase. When calling the TQL for data pull we pass the parameterized date parameters to get
Job.
CI – BMC_SOFTWARESERVER
Transformation – SoftwareServerRelation9.ktr and Delete_SoftwareServer9.ktr
TQL’s used. – running_software_bmcsoftwareserver
CI Elements in TQL – RunningSoftware, Node and ApplicationSystem.
a. RunningSoftware
Parameterize
Criteria
d
b. Node
No search criteria.
c. ApplicationSystem
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from RunningSoftware, Node and ApplicationSystem to
populate data in BMC_SoftwareServer. When calling the TQL for data pull we pass the parameterized
date parameters to get the CI data records for Initial Load/ Delta Load based on the last execution time of
the Transformation Job.
CI – BMC_LOGICALDISK
Transformation – LogicalDiskRelation9.ktr and Delete_LogicalDisk9.ktr
TQL’s used. – logical_volume_bmclogicaldisk
CI Elements in TQL – LogicalVolume, Node, Storage Pool and FileSystem.
a. LogicalVolume
Parameterize
Criteria
d
b. Node
No search criteria.
c. Storage Pool
No search criteria.
d. FileSystem
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from LogicalVolume, Node, Storage Pool and FileSystem to
populate data in BMC_LogicalDisk. When calling the TQL for data pull we pass the parameterized date
Transformation Job.
CI – BMC_REMOTEFILESYSTEM
Transformation – RemoteFileSystemRelation9.ktr and Delete_RemoteFileSystem9.ktr
TQL’s used. – file_system_bmcremotefilesystem
CI Elements in TQL – FileSystem (file_system), FileSystem (localdisk) and Node.
a. FileSystem (file_system)
Parameterize
Criteria
d
N Storage Type Equal "NetworkDisk”
b. FileSystem (file_system)
Parameterize
Criteria
d
N Storage Type Not equal "NetworkDisk"
N Storage Type Is null
c. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from FileSystem (file_system), FileSystem (localdisk) and
Node to populate data in BMC_RemoteFileSystem. When calling the TQL for data pull we pass the
parameterized date parameters to get the CI data records for Initial Load/ Delta Load based on the last
execution time of the Transformation Job. The qualification on Storage Type attribute is used to identify
the remote/local filesystems.
CI - BMC_RESOURCEPOOL
Transformation - ResourcePoolRelation9.ktr and Delete_ ResourcePool9.ktr
TQL’s used. - storagepool_bmcresourcepool
CI Elements in TQL – Storage Pool and Node.
a. Storage Pool
Parameterize
Criteria
d
b. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Storage Pool to populate data in BMC_ResourcePool.
CI - BMC_APPLICATION
Transformation - ApplicationRelation9.ktr and Delete_ Application9.ktr
TQL’s used. - application_system_bmcapplication
CI Elements in TQL – ApplicationSystem and Service.
a. ApplicationSystem
Parameterize
Criteria
d
b. Service
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from ApplicationSystem to populate data in
BMC_Application. When calling the TQL for data pull we pass the parameterized date parameters to get
Job.
CI - BMC_BUSINESSSERVICE
Transformation - BusinessServiceRelation9.ktr and Delete_ BusinessService9.ktr
TQL’s used. - service_bmcbusinessservice
CI Elements in TQL – Service, Organization and ApplicationSystem.
a. Service
Parameterize
Criteria
d
b. Organization
No search criteria.
c. ApplicationSystem
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Service to populate data in BMC_ BusinessService.
CI - BMC_ORGANIZATION
Transformation - Organization9.ktr and Delete_ Organization9.ktr
TQL’s used. - organization_bmcorganization
CI Elements in TQL – Organization.
a. Organization
Parameterize
Criteria
d
Use of TQL.
This TQL is used to fetch data from UCMDB from Organization to populate data in BMC_ Organization.
CI - BMC_IPCONNECTIVITYSUBNET
Transformation - IPConnectivitySubnet9.ktr and Delete_ IPConnectivitySubnet9.ktr
TQL’s used. - ip_subnet_bmcipconnectivitysubnet
CI Elements in TQL – IpSubnet
a. IpSubnet
Parameterize
Criteria
d
Use of TQL.
This TQL is used to fetch data from UCMDB from IpSubnet to populate data in
BMC_IpConnectivitySubnet. When calling the TQL for data pull we pass the parameterized date
Transformation Job.
Relationship CI – VirtualHostRelation BMC_DEPENDENCY Relation.
Transformation - VirtualHostRelation9.ktr
TQL’s used. - nodevirtual_bmccomputersystemvirtual
CI Elements in TQL – Node, Node (physical) and Hypervisor.
a. Node (Virtual)
Parameterize
Criteria
d
N Host is Virtual Equal “True”
b. Node (physical)
Parameterize
Criteria
d
N Host is Virtual Is null
N OR Host is Virtual Equal “False”
c. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Node and Hypervisor to populate data for
BMC_Dependency (HOSTEDVIRTUALSYSTEM and VIRTUALSYSTEMOS) relation between
ComputerSystems and VirtualSystemEnablers. When calling the TQL for data pull we pass the
parameterized date parameters to get the CI data records for Initial Load/ Delta Load based on the last
execution time of the Transformation Job. Conditions on ‘Host is Virtual’ attribute help identify
Virtual/Physical Computers.
Relationship CI – SoftwareServer BMC_COMPONENT Relation.
Transformation - SoftwareServer_SoftwareServerRelation9.ktr
TQL’s used. - running_software_bmcsoftwareserverrelation
CI Elements in TQL – RunningSoftware.
a. RunningSoftware
Parameterize
Criteria
d
b. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from RunningSoftware to populate data for
BMC_Component (APPLICATIONSYSTEMHIERARCHY) relation between SoftwareServers. When
calling the TQL for data pull we pass the parameterized date parameters to get the CI data records for
Initial Load/ Delta Load based on the last execution time of the Transformation Job.
Relationship CI – NETDEVICE_HOST Relation
Transformation - NetDeviceHostRelation9.ktr
TQL’s used. - nodenetdevice_bmccomputersystemrelation
CI Elements in TQL – NetDevice and Node.
a. NetDevice
Parameterize
Criteria
d
b. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Mainframe to populate data for BMC_Dependency
(NetworkLink) relation between net device and computer systems. When calling the TQL for data pull we
pass the parameterized date parameters to get the CI data records for Initial Load/ Delta Load based on
the last execution time of the Transformation Job.
CI - BMC_MAINFRAME
Transformation - Mainframe9.ktr and Delete_ Mainframe9.ktr
TQL’s used. - mainframe_bmcmainframe
CI Elements in TQL – Mainframe and Node.
d. Mainframe
Parameterize
Criteria
d
e. Node
No search criteria.
Use of TQL.
This TQL is used to fetch data from UCMDB from Mainframe to populate data in BMC_Mainframe. When
calling the TQL for data pull we pass the parameterized date parameters to get the CI data records for
Initial Load/ Delta Load based on the last execution time of the Transformation Job.

BMC Atrium CMDB Adapter For HP UCMDB Installation Guide

Uploaded by

Copyright:

Available Formats

BMC Atrium CMDB Adapter For HP UCMDB Installation Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BMC Atrium CMDB Adapter For HP UCMDB Installation Guide

Uploaded by

Copyright:

Available Formats

UCMDB Adapter TQL Documentation

For HP UCMDB 9.x

Transformation - ComputerSystem9 and Delete_ComputerSystem9.ktr

TQL’s used. - node_bmccomputersystem

CI Elements in TQL - NODE

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Transformation - OperatingSystemRelation9.ktr and Delete_OperatingSystem9.ktr

TQL’s used. - node_bmcoperatingsystem

CI Elements in TQL - NODE

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Transformation - BMC_IPEndPointRelation9.ktr and Delete_IPEndPoint9.ktr

TQL’s used. - ip_address_bmcipendpoint

CI Elements in TQL – IpAddress, IpSubnet and Node

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Transformation - LANEndPointRelation9.ktr and Delete_LANEndPoint9.ktr

TQL’s used. - physical_port_bmclanendpoint

CI Elements in TQL – PhysicalPort, Node and RunningSoftware

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Transformation - ProductRelation9.ktr and Delete_Product9.ktr

TQL’s used. - installed_software_bmcproduct

CI Elements in TQL – InstalledSoftware, RunningSoftware and Node.

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Transformation - HardwareSystemComponentRelation9.ktr and

TQL’s used. - node_element_bmchardwaresystemcomponent, node_bmchardwaresystemcomponent

CI Elements in TQL – NodeElement and Node.

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Attributes with Search Criteria present on Query node.

Transformation – NetworkPortRelation9.ktr and Delete_NetworkPort9.ktr

TQL’s used. – Physical_port_bmcnetworkport and interface_bmcnetworkport

1. physical_port_bmcnetworkport – PhysicalPort, Node & RunningSoftware

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Attributes with Search Criteria present on Query node.

Transformation – ClusterRelation9.ktr and Delete_Cluster9.ktr

TQL’s used. – cluster_bmccluster

CI Elements in TQL – Cluster & Node.

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Transformation – Processor9.ktr and Delete_Processor9.ktr

TQL’s used. – cpu_bmcprocessor

CI Elements in TQL – CPU & Node.

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Transformation – VirtualSystemEnabler9.ktr and Delete_VirtualSystemEnabler9.ktr

TQL’s used. – Hypervisor_bmcvirtualsystemenabler and node_bmcvirtualsystemenabler

1. hypervisor_bmcvirtualsystemenabler – Hypervisor & Node

QUERY Node Properties

Attributes with Search Criteria present on Query node.

Attributes with Search Criteria present on Query node.

Transformation – Memory9.ktr and Delete_Memory9.ktr

TQL’s used. – memory_bmcmemory

CI Elements in TQL – Memory & Node.