ECC Integration Job

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

This section includes:

ECC Integration Mechanism

The following workflow explains how the ECC Integration by SQL job discovers the storage topology of ECC. The job:

Connects to the ECC Oracle database instance using credentials from the Generic DB Protocol (SQL). For details, see How to Run the ECC/UCMDB Integration Job.

Queries for fibre channel switches and ports on each switch and creates Fibre Channel Switch CIs:

SELECT switch.st_id, switch.st_sn, switch.st_alias, switch.st_model, switch.st_version, switch.st_vendor, switch.sw_managementurl, switch.sw_domain, switch.sw_portcount, switch.sw_portcount_free FROM stssys.sts_switch_list switch WHERE LOWER(switch.sw_principal) = 'true'

Queries for fibre channel adapters and ports on each Fibre Channel Switch and creates Fibre Channel HBA and Fibre Channel Port CIs:

SELECT port.port_id, port.port_number, port.port_type, port.adport_alias, port.port_wwn, port.port_status, port.conn_port_wwn FROM stssys.sts_switch_port port WHERE port.st_id = switch.st_id from above query

Queries for storage arrays and creates Storage Array CIs:

SELECT array.st_id, array.st_sn, array.st_alias, array.st_type, array.st_model, array.st_vendor, array.st_microcode, array.sy_microcode_patch, array.sy_microcode_patchdate FROM stssys.sts_array_list array

Queries for Fibre Channel ports, Fibre Channel host bus adapters (HBA), and logical volumes on each storage array, and creates Fibre Channel Port, Fibre Channel Port HBA, and Logical Volume CIs:

SELECT port.port_id, port.port_number, port.port_type, port.adport_alias, port.port_wwn, port.port_status FROM stssys.sts_array_port port WHERE port.st_id = array.st_id from above query
SELECT hba.port_id, hba.ad_id, hba.ad_name FROM stssys.sts_array_port hba WHERE hba.st_id = array.st_id from above query
SELECT logicalVolume.sd_id, logicalVolume.sd_name, logicalVolume.sd_alias, logicalVolume.sd_size, logicalVolume.sd_type FROM stssys.sts_array_device logicalVolume WHERE logicalVolume.st_id = array.st_id from above query

Queries for hosts/servers and creates appropriate Computer, Windows, or Unix CIs. Results of this query are used to create host resource CIs, such as CPU, if this information is available:

SELECT host.host_id, host.host_name, host.host_alias, host.host_domain, host.host_model, host.host_ip, host.host_vendorname, host.host_cpucount, host.host_installedmemory, host.host_os, host.host_osversion, host.host_oslevel, host.host_osclass FROM stssys.sts_host_list host

Queries for Fibre Channel ports, Fibre Channel host bus adapters (HBA), and logical volumes on each host/server and creates Fibre Channel Port, Fibre Channel Port HBA, and Logical Volume CIs:

SELECT port.port_id, port.port_number, port.adport_alias, port.port_wwn FROM stssys.sts_host_hba port WHERE port.host_id = host.host_id from above query
SELECT hba.ad_id, hba.ad_name, hba.fibread_nodewwn, hba.ad_vendor, hba.ad_revision, hba.ad_model, hba.port_id, hba.ad_driver_rev FROM stssys.sts_host_hba hba WHERE hba.host_id = host.host_id from above query
SELECT logicalVolume.hd_id, logicalVolume.hd_name, logicalVolume.hd_type, logicalVolume.hd_total FROM stssys.sts_host_device logicalVolume WHERE logicalVolume.hd_id IS NOT NULL AND logicalvolume.arrayjbod_type = 'Array' AND logicalVolume.host_id = host.host_id from above query

Queries for logical volume mapping between logical volumes on hosts/servers and logical volumes on storage arrays, and adds Dependency relationships between hosts/servers and storage arrays:
```
SELECT sd_id FROM stssys.sts_host_shareddevice WHERE hd_id = logicalvolume.hd_id from above query
```

Queries for paths between hosts/servers and storage arrays and adds Fibre Channel Connect relationships between respective hosts/servers, switches, and storage arrays:

SELECT port.port_wwn, port.conn_port_wwn FROM stssys.sts_array_port_connection port WHERE port.port_wwn IS NOT NULL AND port.conn_port_wwn IS NOT NULL
SELECT port.port_wwn, port.conn_port_wwn FROM stssys.sts_switch_port port WHERE port.port_wwn IS NOT NULL AND port.conn_port_wwn IS NOT NULL

Adapter

The following table gives details of the adapter parameters.

Parameter	Description
allowDNSLookup	If a node in the ECC database does not have an IP address but has a DNS name, it is possible to resolve the IP address by the DNS name. True: If a node does not have an IP address, an attempt is made to resolve the IP address by DNS name (if a DNS name is available). Default: False
ignoreNodesWithoutIP	Defines whether or not nodes in ECC without IP addresses should be pulled into UCMDB. True. Nodes without IPs are ignored. False. A Node CI is created with an ECC ID as the node key attribute. Note Setting this parameter to False may result in duplicate CIs in the CMDB. Default: True

Parameter

Description

allowDNSLookup

If a node in the ECC database does not have an IP address but has a DNS name, it is possible to resolve the IP address by the DNS name.