Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Configure
- Configuring Event Collection
- Configuring the Event Backward Synchronization
- Configuring Metric Data Collection
- Configuring Topology Collection
- Configuring Operations Connector for High Availability
- Backing up and Restoring the Configuration
- Managing the Integration Services
- Updating Existing Event Severity
- Activating the IBM Tivoli Policies
- Configuration Options
- Entity Mappings
- Creating Additional Metric Collection Filters
Configuration Options
This topic describes configurable options for integrating IBM Tivoli events and topology with Ops Connector for IBM Tivoli. All options are preconfigured with default values you can modify. While basic options have their default values specified in the configuration files, the default values of advanced options are implicitly defined. To modify the value of an advanced option, manually add the option and its chosen value to a configuration file.
You can find integration configuration files in the <OvDataDir>/conf/HPBsmIntTivoli
directory on the Operations Connector host. They are plain text files. In a configuration file, in the nodes
section, each option has a value that is assigned by using the following syntax:
'<OptionName>' : '<Value>'
If an appropriate option and its value are present but commented out, remove the comment delimiter //
and modify the value as needed.
When adding an advanced option to the configuration file, make sure to add it to the appropriate subsection of the nodes
section. Use the following syntax:
'<AdvancedOptionName>' : '<Value>',
After reconfiguring a Ops Connector for IBM Tivoli integration, restart the integration service as described in Restarting the Services.
Some option descriptions inside the configuration files might be incomplete or incorrect. Refer to this documentation for complete and correct information about configuration options.
Event Integration Options
The following tables list options in event_integration.conf
—the event integration configuration file.
Basic Options
Option Name | Description, (Default) Value |
---|---|
Subsection: source (eifserver ) |
|
|
Network port on which the Ops Connector for IBM Tivoli listens for incoming IBM Tivoli events. Default value: |
threads
|
Number of worker threads used to receive incoming events. Each worker thread is able to handle one incoming request at a time. Default value: |
server-socket-timeout
|
Timeout in milliseconds for I/O operations on the server socket of the EIF (Event Integration Facility) receiver. Default value: |
Subsection: sink (bsmcws ) |
|
use-ssl
|
This option enables or disables secure communication using the SSL protocol. Default value: |
uri
|
String that specifies the web address to use in the REST Web Service communication between Ops Connector for IBM Tivoli and Operations Connector. Specify a valid URL string without the scheme name (protocol), hostname, and port. Default value: |
port
|
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: |
server-name
|
Fully qualified domain name (FQDN) or IP address of your Operations Connector host. Default value: |
use-persistency
|
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: |
persistency-dir
|
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. Windows default value: Linux default value: |
persistency-max-size
|
Size (in kilobytes) that a persistency data file must exceed to initiate the creation of a new data file. Default value: |
persistency-max-files
|
Maximum number of persistency data files the message buffering mechanism maintains. Default value: |
persistency-prefix
|
You may not alter this option. Default value: |
retry-wait
|
Time period (in seconds) that Ops Connector for IBM Tivoli waits
before retrying to send the REST Web Service request. This option is
ignored if the Default value: |
root-element
|
You may not alter this option. Value: |
Subsection: processor (discovery ) |
|
discovery-field-hostname-itm
|
Attribute name of a received IBM Tivoli event that contains a hostname, from which topology data is constructed. This option is used events are received from an IBM Tivoli Monitoring system. Default value: |
discovery-field-hostname-netcool
|
Attribute name of a received IBM Tivoli event that contains a hostname, from which topology data is constructed. This option is used events are received from an IBM Tivoli Netcool/OMNIbus system. Default value: |
discovery-field-ip-itm
|
Attribute name of a received IBM Tivoli event that contains an IP addresses, from which topology data is constructed. Default value: |
discovery-field-ip-netcool
|
Attribute name of a received OpsCx for IBM Tivoli event that contains an IP addresses, from which topology data is constructed. Default value: |
discovery-store
|
Location of discovery store file which stores information about events to construct topology. Windows default value: Linux default value: |
filename
|
Path of the file with a valid Lua script that processes IBM Tivoli event data. Windows default value: Linux default value: |
package-path
|
Additional search paths where Ops Connector for IBM Tivoli searches for Lua modules. Separate the paths with semicolons and use wildcard characters if needed. This option is used to set the global Lua variable Windows default value: Linux default file: |
Subsection: processor (baroc ) |
|
baroc-dir
|
The directory of the BAROC (Basic Recorder of Objects in C) event definition files, which are used in IBM Tivoli environments and can be reused to determine default values of the event attributes. Windows default value: Linux default value: |
Subsection: processor (ncbulkdel ) |
|
netcool-bulk-delete-class
|
Event class name used to detect IBM Tivoli bulk deletion events. Default value: |
netcool-bulk-delete-id-list
|
Attribute name of the identifier list used in IBM Tivoli bulk deletion events. Default value: |
netcool-bulk-delete-id-attr
|
Attribute name for the single identifier in the generated event when IBM Tivoli bulk deletion event splitting is enabled. Default value: |
Subsection: sink (xmltrace ) |
|
filename
|
Path of the event output file to which Ops Connector for IBM Tivoli writes data. You do not have to create this file in advance. Windows default value: Linux default value: |
root-element
|
Name of the root element in the event output XML file Default value: |
Subsection: processor (copier ) |
|
copy-count
|
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 Topology. Afterward, adjust the options in the Default value: |
Advanced Options
Option Name | Description, (Default) Value |
---|---|
Subsection: sink (bsmcws ) |
|
connection-count
|
Number of concurrent connections Ops Connector for IBM Tivoli should use for transferring event data to Operations Connector. Default value: |
bulk-size
|
Maximum number of messages that Ops Connector for IBM Tivoli should put into a single REST Web Service request. Default value: |
ssl-cert
|
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. The private key may not use a password. Although you can use different ways to obtain such certificate, it is strongly recommended that you use a certificate issued by a certificate authority (CA). This option must be set when the Default value: (empty) |
use-auth
|
The option that, when set to true, causes Ops Connector for IBM Tivoli to use the credentials specified for the Enable secure communication by using the SSL protocol to prevent the authentication credentials from being sent unencrypted to the Operations Connector host. Default value: |
use-store
|
The option that, when set to true, causes Ops Connector for IBM Tivoli to obtain the authentication credentials from the GenInt keystore
rather than from the integration configuration file. In this case, the values of
the Enable secure communication by using the SSL protocol to prevent the authentication credentials from being sent unencrypted to the Operations Connector host. Default value: |
auth-username
|
User name used for authenticating against the REST Web Service endpoint on the Operations Connector host. Default value: (empty) |
auth-password
|
Password used for authenticating against the REST Web Service endpoint on the Operations Connector host. Default value: (empty) |
Subsection: processor (discovery ) |
|
interval
|
Time period (in seconds) that defines the intervals at which event data
is processed by using the Lua script. This option is ignored if the
Default value: |
error-timeout
|
Time period (in seconds) that Ops Connector for IBM Tivoli waits before invoking the Lua script again in case an error occurred during the previous script run. Default value: |
single-run
|
The option that, when set to
Default value: |
package-cpath
|
Additional search paths where Ops Connector for IBM Tivoli searches for C libraries. Separate the paths with semicolons and use wildcard characters if needed. Default value: (empty) |
Subsection: sink (xmltrace ) |
|
rollover-size
|
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: |
rollover-count
|
Maximum number of output XML files the rollover mechanism may maintain. Default value: |
rollover-wait
|
Time period (in seconds) that Ops Connector for IBM Tivoli waits before retrying the rollover. Default value: |
Metric Integration Options
The following tables list options in metric_integration.conf
—the metric integration configuration file.
Basic Options
Option Name | Description, (Default) Value |
---|---|
Subsection:source (tivoli ) |
|
tivoli-hostname
|
Fully qualified domain name or IP address of the Tivoli server. This option is required. |
tivoli-ws-port
|
Network port on which Tivoli Web Service listens. Default: |
tivoli-metric-filter-location
|
Location of Tivoli metric filter files. Windows default value: Linux default value: |
tivoli-hostname-cache-file
|
Location of the Tivoli resolved hostnames cache file Windows default value: Linux default value: |
tivoli-timestamp-file
|
Timestamp persistency filename. Windows default value: Linux default value: |
tivoli-timezone-offset
|
If your Operations Connector and IBM Tivoli server are not in the same timezone, use this option to set the timezone offset. This time (in hours) will be added or substracted to the timestamp received. Examples of possible values: +1,-3,+2.5,0,-2.75,... Default: |
tivoli-interval
|
The metric collection interval in seconds. Default: |
tivoli-max-connections
|
Maximum concurrent connections to the ITM server during the metric collection. Default: |
tivoli-init-age
|
Maximum "age" of metrics when the collector starts. When restarting the collector (timestamp file already exists), the integration will fetch metrics which are not older than the given age (in seconds). In case the timestamp file does not exist, maximum age of collected metrics is limited with the tivoli-interval Default: |
tivoli-topology-filtering |
Topology filtering. If set to true, only those CIs will be collected which have metric collection enabled. If set to false, all CIs found will be sent to the OMi server. Default: |
discovery-store
|
The topology discovery store file. Windows default value: Linux default value: |
timeout
|
The maximum amount of time (in seconds) to wait for writing of the topology file, before timeout happens Default: 60 |
single-run
|
The option that, when set to Default value: |
filename
|
Path of the file with a valid Lua script that processes IBM Tivoli metric data. Windows default value: Linux default value: |
package-path
|
Additional search paths where OpsCx for IBM Tivoli searches for Lua modules. Separate the paths with semicolons and use wildcard characters if needed. This option is used to set the global Lua variable Windows default value: Linux default file: |
Subsection:sink (wsmetricsink ) |
|
use-ssl
|
This option enables or disables secure communication using the SSL protocol. Default: |
uri
|
String that specifies the web address to use in the REST Web Service communication between Ops Connector for IBM Tivoli and Operations Connector. Specify a valid URL string without the scheme name (protocol), hostname, and port. Default: |
port
|
The service name or port to use for establishing the connection. Default: |
server-name
|
Fully qualified domain name (FQDN) or IP address of your remote host. As the integration daemon runs on the same host as Operations Connector, this can be set to localhost. Default: |
use-persistency
|
If set to true, all incoming messages will first be persisted into a file-based data store, before sending them to the remote host. It also enables the retry mechanism. Default: |
persistency-dir
|
Directory path, used for the persistence layer. Directory must exist. Windows default value: Linux default value: |
persistency-max-size
|
Size (in kilobytes) that a persistency data file must exceed to initiate the creation of a new data file. Default: |
persistency-max-files
|
Maximum number of persistency data files the message buffering mechanism maintains. Default: |
persistency-prefix
|
You may not alter this option. Default: |
retry-wait
|
Time period (in seconds) that OpsCx for IBM Tivoli waits before retrying to send the REST Web Service request. This option is ignored if the Default: |
root-element
|
You may not alter this option. Default: |
Subsection:sink (xmlmetricsink ) |
|
filename
|
Path of the event output file to which Ops Connector for IBM Tivoli writes data. You do not have to create this file in advance. Windows default value: Linux default value: |
root-element
|
Name of the root element in the event output XML file Default value: |
Subsection:processor (copier ) |
|
copy-count
|
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 Topology. Afterward, adjust the options in the Default value: |
Topology Integration Options
The following tables list options in topology_integration.conf
—the topology integration configuration file.
Basic Options
Option Name | Description, (Default) Value |
---|---|
Subsection: source (store ) |
|
discovery-store-event
|
File, which stores information about events from which the topology data is generated. Windows default value: Linux default value: |
discovery-store-metric
|
File, which stores information about metric data from which the topology data is generated. Windows default value: Linux default value: |
discovery-interval
|
Interval in minutes, in which the topology information is fetched from the specified discovery store. Default value: |
filename
|
Path of the file with a valid Lua script that processes IBM Tivoli topology data. Windows default value: Linux default value: |
package-path
|
See Event Integration Options. |
collect-agents
|
Set this parameter to Default: |
Subsection: sink (topoxml ) |
|
filename
|
Path of the topology output file to which Ops Connector for IBM Tivoli writes data. You do not have to create this file in advance. Windows default value: Linux default value: |
Subsection: source (selfsource ) |
|
tivoli-netcool-hostname
|
Fully qualified domain name of the IBM Tivoli Netcool/OMNIbus system. Default value: (empty) |
tivoli-itm-hostname
|
Fully qualified domain name of the IBM Tivoli Monitoring system. Default value: (empty) |
interval
|
Seconds to wait after rerunning the Lua scripts. Default value: |
filename
|
Path of the file with a valid Lua script that processes IBM Tivoli self-discovery topology data. Default Windows value: Default Linux value: |
package-path
|
Additional search paths where Ops Connector for IBM Tivoli searches for Lua modules. Separate the paths with semicolons and use wildcard characters if needed. This option is used to set the global Lua variable Default Windows value: Default Linux value: |
Subsection: sink (selfxml ) |
|
filename
|
Path of the output file to which Ops Connector for IBM Tivoli writes self-discovery topology data. Default Windows value: Default Linux value: |
Advanced Options
Option Name | Description, Default Value |
---|---|
Subsection: source |
|
interval
|
See Event Integration Options. |
error-timeout
|
See Event Integration Options. |
single-run
|
See Event Integration Options. |
package-cpath
|
See Event Integration Options. |
Subsection: sink (selfxml ) |
|
tmp-filename
|
Name of the temporary file used as a buffer while waiting for the next
topology data block. If the time period configured with the The Default value: |
message-timeout
|
Time period (in seconds) that Ops Connector for IBM Tivoli. Operations Connector 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: |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: