Configuration Options

Time period (in seconds) that defines the intervals at which the accumulated events (alerts) are acquired from the integrated Microsoft SCOM instance.

Default value: 40

The option that, when set to true, causes Operations Connector for Microsoft SCOM to obtain the health state of a monitored Microsoft SCOM object by querying the object directly, rather than deriving it from the alert data.

Default value: false

You may alter this option only to locally generate an event output file in the XML format for troubleshooting purposes. Follow the instructions in Troubleshooting the Collection of Events and Metrics topic. Afterward, adjust the options in the sink (eventxmlsink) section to fine‑tune the output file generation.

Default value: 0

To store the alerts in an XML format for debugging or troubleshooting purposes, you can use the copy splitter functionality available in the connector configuration file.

Default value: 0

String that specifies the web address to use in the REST Web Service communication between Operations Connector for Microsoft SCOM and Operations Connector. Specify a valid URL string without the scheme name (protocol), hostname, and port.

Default value: /bsmc/rest/events/HPBsmInt<InstanceID>

Fully qualified domain name (FQDN) of your Operations Connector host.

Default value: localhost

Default port of Operations Connector policies of the REST Web Service Listener type. As long as you do not reconfigure Operations Connector, you may not alter this option.

Default value: 30005

This option enables or disables secure communication using the SSL protocol.

Default value: true

You may not alter this option.

Value: scom_event_message

This option enables or disables a local file-based message buffering mechanism. When the mechanism is enabled, messages are delivered in any circumstance.

Default value: true

Path of the directory for persistency data files: an internal buffer for the not-yet-dispatched messages. You must create the directory in advance with the read and write access enabled.

Default value: ${OvDataDir}/tmp/HPBsmIntSCOM

You may not alter this option.

Value: <InstanceID>_events

Name of the root element in the event output XML file.

Default value: scom_event_message

Path of the event output file to which Operations Connector for Microsoft SCOM writes data. You do not have to create this file in advance.

Default value: ${OvDataDir} \
\datafiles\HPBsmIntSCOM\<InstanceID>\output\scom_events.xml

Size (in kilobytes) that an output XML file must exceed to initiate an output file rollover (that is, creating a new file and redirecting output into it).

Default value: 1024

Maximum number of output XML files the rollover mechanism may maintain.

Default value: 5

Time period (in seconds) that Operations Connector for Microsoft SCOM waits before retrying the rollover.

Default value: 30

You may not alter this option.

Value: <BacksyncPort>

The option that, when set to false, disables resolution state backward synchronization for all Microsoft SCOM events (alerts).

Default value: true

The option that, when set to true, causes resolution state backward synchronization to include also the events (alerts) that originate from Microsoft SCOM monitors. This option is ignored if the enable-backsync basic option is set to false.

Default value: false

This option defines how many concurrent connections Operations Connector for Microsoft SCOM should use for transferring event data to Operations Connector.

Default value: 5

Maximum number of messages that Operations Connector for Microsoft SCOM should put into a single REST Web Service request.

Default value: 10

Path of the file that stores a valid CA certificate in the PEM format and which is used to verify the identity of the remote server. The certificate must contain the private key and the public key.

This option must be set when the use-ssl option is set to true.

Default value: (empty)

The option that, when set to true, causes Operations Connector for Microsoft SCOM to use the credentials specified for the auth‑username and auth‑password options to authenticate against the remote REST Web Service endpoint.

Enable secure communication by using the SSL protocol to prevent the authentication credentials from being sent unencrypted to the Operations Connector host.

Default value: false

The option that, when set to true, causes Operations Connector for Microsoft SCOM to obtain the authentication credentials from the GenInt keystore rather than from the integration configuration file. In this case, the values of the auth‑username and auth‑password options are used as the credential string IDs inside the keystore.

Enable secure communication by using the SSL protocol to prevent the authentication credentials from being sent unencrypted to the Operations Connector host.

Default value: false

User name used for authenticating against the REST Web Service endpoint on the Operations Connector host.

Default value: (empty)

Password used for authenticating against the REST Web Service endpoint on the Operations Connector host.

Default value: (empty)

Size (in bytes) that a persistency data file must exceed to initiate the creation of a new data file.

Default value: 10240

Maximum number of persistency data files the message buffering mechanism maintains.

Default value: 10

Time period (in seconds) that Operations Connector for Microsoft SCOM waits before retrying to send the REST Web Service request. This option is ignored if the use-persistency basic option is set to false.

Default value: 30

Time period (in seconds) that defines the intervals at which the topology data is acquired from the integrated Microsoft SCOM instance.

Default value: 3600

You may not alter this option directly. To define the set of Microsoft SCOM groups from which the monitoring objects are collected to create topology data in OMi, use the Configuration Utility of Operations Connector for Microsoft SCOM.

Default value: HP Topology Infrastructure Group

The option that, when set to false, disables general enrichment of the topology data acquired from Microsoft SCOM. The enrichment (topology transformation) takes place before the data is relayed to Operations Connector.

Default value: true

Path of the file with the custom definition of topology transformation that Operations Connector for Microsoft SCOM uses to enrich topology data. When the value is left empty, the default topology transformation is used.

You can find a template of the custom transformation definition at the location <OvDataDir>\installation\HPBsmIntSCOM\templates\ in the recommended_transformations.xml file.

Default value: (empty)

This option enables or disables creation of Operations Manager i-conforming host keys based on the systems' MAC or IP addresses. If set to true, Operations Connector for Microsoft SCOM scans all network interface adapters of each discovered system to acquire their MAC addresses and IP addresses.

Default value: true

The option that, when set to false, disables reverse DNS lookup of the IP addresses of hostnames collected from the integrated Microsoft SCOM instance.

Default value: true

This option specifies the IP format that Operations Connector for Microsoft SCOM uses when artificially creating IP addresses. The allowed values are ipv4, ipv6, and both.

Default value: both

This option defines how discovery of network interface controllers (NICs) is conducted. If the option is set to nic, Operations Connector for Microsoft SCOM discovers all NICs of a discovered system (Microsoft SCOM object) and adds them to it. If the option is set to computer, NICs are not discovered.

Default value: nic

This option enables or disables enrichment of IP addresses with the data from the network interface controllers (NICs). The option is ignored if the ip-create-mode basic option is set to computer.

Default value: true

Domain in which Microsoft SCOM object discovery is run.

Default value: DefaultDomain

The option that, when set to false, disables reverse DNS lookup of the IP addresses of hostnames collected from the integrated Microsoft SCOM instance. Reverse DNS lookup requires the Operations Connector host and the Microsoft SCOM host to be members of the same domain.

Default value: true

Path of the topology output file to which Operations Connector for Microsoft SCOM writes data. You do not have to create this file in advance. This value must match the value of the Topology XML File option of the Operations Connector policy for Microsoft SCOM topology. In the Operations Connector web interface, you can find it in the Source page of the policy.

Default value: ${OvDataDir}\datafiles\HPBsmIntSCOM \
\<InstanceID>\output\scom_topology.xml

Path of the self-discovery topology output file to which Operations Connector for Microsoft SCOM writes data. You do not have to create this file in advance. This value must match the value of the Topology XML File option of the Operations Connector policy for Microsoft SCOM self-discovery topology. In the Operations Connector web interface, you can find it in the Source page of the policy.

Default value: ${OvDataDir}\datafiles\HPBsmIntSCOM \
\<InstanceID>\output\scom_topology_discovery.xml

Name of the temporary file used as a buffer while waiting for the next topology data block. If the time period configured with the message‑timeout option expires before the next data block arrives, the buffered data overwrites the topology output file, and the buffer is flushed.

The <filename> variable is automatically replaced with the value of the filename option.

Default value: <filename>.tmp

Time period (in seconds) that Operations Connector for Microsoft SCOM waits for the next topology data block before overwriting the topology output file with the received data that is already in the buffer.

Default value: 10

Name of the temporary file used as a buffer while waiting for the next self-discovery topology data block. If the time period configured with the message‑timeout option expires before the next data block arrives, the buffered data overwrites the self-discovery topology output file, and the buffer is flushed.

The <filename> variable is automatically replaced with the value of the filename option.

Default value: <filename>.tmp

Time period (in seconds) that Operations Connector for Microsoft SCOM waits for the next self-discovery topology data block before overwriting the self-discovery topology output file with the received data that is already in the buffer.

Default value: 10

Time period (in seconds) that defines the intervals at which the metrics are acquired from the integrated Microsoft SCOM instance.

Default value: 300

Path of the file that contains settings for filtering the Microsoft SCOM metric data.

Default value: ${OvDataDir}\datafiles\HPBsmIntSCOM \
\<InstanceID>\MetricFilterConfig.xml

You may alter this option only to locally generate a metric output file in the XML format for troubleshooting purposes. Follow the instructions in Troubleshooting the Collection of Events and Metrics topic. Afterward, adjust the options in the sink (metricxmlsink) section to fine‑tune the output file generation.

Default value: 0

String that specifies the web address to use in the REST Web Service communication between Operations Connector for Microsoft SCOM and Operations Connector. Specify a valid URL string without the scheme name (protocol), hostname, and port.

Default value: /bsmc/rest/metrics/HPBsmInt<InstanceID>

See Event Integration Options.

See Event Integration Options.

See Event Integration Options.

You may not alter this option.

Value: scom_metric_message

See Event Integration Options.

See Event Integration Options.

You may not alter this option.

Value: <InstanceID>_metrics

Name of the root element in the metric output XML file.

Default value: scom_metric_message

Path of the metric output file to which Operations Connector for Microsoft SCOM writes data. You do not have to create this file in advance.

Default value: ${OvDataDir}\datafiles\HPBsmIntSCOM \
\<InstanceID>\output\scom_metrics.xml

See Event Integration Options.