|
<< Click to Display Table of Contents >> Raynet One Data Hub > 14.0 u1 > Connectors > Alphabetic Connector List > HP Universal CMDB > Connector Parameters Configuration |
This parameter defines the user repository for authentication in newer versions.
Technical Name |
user_repository |
Category |
Functional |
Type |
String |
Default Value |
UCMDB |
Example Values |
UCMDB |
The library will require this parameter for authentication in newer versions. Its purpose is unclear. Probably one of the following values is meaningful: 'UCMDB', 'LDAP'. Take a look at the official documentation.
This parameter contains the name of the UCMDB topology query to run and extract results from (topology queries can be created within UCMDB's Modeling Studio).
Technical Name |
query_name |
Category |
Functional |
Type |
String |
Default Value |
n/a |
Example Values |
|
This parameter contains regular expressions matching CI types.
Technical Name |
base_ci_type_pattern |
Category |
Functional |
Type |
String |
Default Value |
n/a |
Example Values |
(?i)cpu |
Topology query results are hierarchical graphs that need to be transformed to flat/tabular CSV files. The processor will generate one CSV record for all CIs in the query result whose CI type matches the regular expression specified 'base_ci_type_regex'. Properties of related Cis in the query result might be joined to each record (see parameter traverse).
This parameter can be used to activate the traversal of incoming or outgoing relations in the topology query result.
Technical Name |
traverse |
Category |
Functional |
Type |
String |
Default Value |
false |
Example Values |
false, incoming, outgoing |
Properties of related CIs that are found during traversal are joined to each base CI's CSV record. In case multiple CIs of the same type are joined for a CSV record, properties of these CIs are separated with the string sequence specified by parameter 'join_separator' in each CSV record and field. Default join separator is a comma followed by a space character, see documentation for parameter 'join_separator' below. In case single records should be exploded into multiple records during join, use IPP PCRE explode with 'pcre_expression = (\\[^[', \\]]+)' to transform comma-separated properties into multiple records.
This parameter contains a comma-separated list of the mappings for CI types.
Technical Name |
ci_type_mapping |
Category |
Functional |
Type |
String |
Default Value |
n/a |
Example Values |
nt:node,unix:node,vmware_esx_server:node,ip_address:ip |
This can be used to combine properties of different CI types into single fields. This parameter can also be used to rename the name for certain CI types in order to achieve shorter CSV headline fields. In this example the CI types 'nt', 'unix', and 'vmware_esx_server' are merged into the CI type node while 'ip_address' CIs are renamed/prefixed with 'ip'.
This parameter can be used to remove duplicate properties during a join.
Technical Name |
deduplicate_properties |
Category |
Functional |
Type |
Boolean (true or false) |
Default Value |
n/a |
Example Values |
|
'192.168.0.1, 192.168.0.2, 192.168.0.1' would be deduplicated to '192.168.0.1, 192.168.0.2'.
This parameter defines the string separator for properties during a join of related CIs.
Technical Name |
join_separator |
Category |
Functional |
Type |
String |
Default Value |
, |
Example Values |
, |
String sequence to use as a separator for properties during the join of related CIs.