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 |
|
Configuration Options
This topic describes configurable options for integrating Systems Insight Manager events and topology with OpsCx for SIM. 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/HPBsmIntSIM
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 OpsCx for SIM integration, restart the integration service as described in Restarting the Services topic.
Some option descriptions inside the configuration files might be incomplete or incorrect. Refer to this document for complete and correct information about configuration options.
Event Integration Options
The following tables list options in sim_events.conf
—the event integration configuration file.
Basic Options
Option Name | Description, (Default) Value |
---|---|
Subsection: source (eventsource ) |
|
filename
|
Path of the file with a valid Lua script that processes SIM event data. Windows default value: Linux default value: |
interval
|
Seconds to wait after collecting the data. Default value: |
package-path
|
Additional search paths where OpsCx for SIM 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: |
sim_event_timestamp_filename
|
A path to a file with a time stamp of a last collected event. Windows default value: Linux default file: |
already_cleared_events_file
|
File where already cleared event IDs are stored. Operations Connector always receives all cleared events from SIM, so it needs to compare the received events to the events listed in this file. This enables Operations Connector to distinguish between all and newly obtained cleared events. Windows default value: Linux default value:
|
cleared_events_query_name
|
The name of query for cleared events, which needs to be imported to the SIM system. Default value: |
separator
|
Separator between clear event IDs in Default value: |
sim_event_init_age
|
Maximum age of events for the initial run. On the initial run (without having a time stamp file), the integration will fetch alerts with modification time stamp not older than the given age (in minutes). Default value: |
Subsection: source (backsyncsource ) |
|
port
|
SIM server event backward synchronization port number. Default value: |
Subsection: sink (backsyncsink ) |
|
filename
|
Path of the file with a valid Lua script that processes SIM event backward synchronization data. Windows default value: Linux default file: |
package-path
|
Additional search paths where OpsCx for SIM searches for Lua modules for event backward synchronization. Separate the paths with semicolons and use wildcard characters if needed. Windows default value: Linux default file: |
Subsection: processor (eventcopysplitter ) |
|
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 topic. Default value: |
Subsection: sink (wseventsink ) |
|
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 OpsCx for SIM 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 bytes) 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 OpsCx for SIM waits
before retrying to send the REST Web Service request. This option is
ignored if the Default value: |
auth-username
|
User name used for authenticating against the REST Web Service endpoint on the Operations Connector host. Default value: |
auth-password
|
Password used for authenticating against the REST Web Service endpoint on the Operations Connector host. Default value: |
root-element
|
You may not alter this option. Value: |
Subsection: sink (xmleventsink ) |
|
filename
|
Path of the event output file to which OpsCx for SIM writes data. You do not have to create this file in advance. Windows default value: Linux default value: |
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: |
root-element
|
Name of the root element in the event output XML file Default value: |
Advanced Options
Option Name | Description, (Default) Value |
---|---|
Subsection: source (eventsource ) |
|
error-timeout
|
Seconds that OpsCx for SIM 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 OpsCx for IBM Tivoli searches for C libraries. Separate the paths with semicolons and use wildcard characters if needed. Default value: (empty) |
Subsection: sink (wseventsink ) |
|
connection-count
|
Number of concurrent connections OpsCx for SIM should use for transferring event data to Operations Connector. Default value: |
bulk-size
|
Maximum number of messages that OpsCx for SIM 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, Service provider strongly recommends 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 OpsCx for SIM 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 OpsCx for SIM 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: |
Subsection: sink (xmleventsink ) |
|
rollover-wait
|
Time period (in seconds) that OpsCx for SIM waits before retrying the rollover. Default value: |
Topology Integration Options
The following tables list options in sim_topology.conf
—the topology integration configuration file.
Basic Options
Option Name | Description, (Default) Value |
---|---|
Subsection: source (topologysource ) |
|
sim_server_hostname
|
Hostname of the SIM server. Default value: |
sim_server_port
|
Port number of the SIM Web Service. Default value: |
filename
|
Path of the file with a valid Lua script that processes the SIM topology data. Windows default value: Linux default value: |
interval
|
Seconds to wait after re-running the script. Default value: |
package-path
|
Additional search paths where OpsCx for SIM 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 value: |
Subsection: sink (sinktopo ) |
|
filename
|
Path of the topology output file to which OpsCx for SIM writes data. You do not have to create this file in advance. Windows default value: Linux default value: |
Subsection: processor (simselfdiscoveryprocess ) |
|
filename
|
Path of the file with a valid Lua script that processes the SIM self-discovery topology data. Windows default value: Linux default value: |
interval
|
Script running interval in seconds. Default value: |
Subsection: sink (simselfdiscoverysink ) |
|
filename
|
Path of the self-discovery topology output file to which OpsCx for SIM writes data. You do not have to create this file in advance. Windows default value: Linux default value: |
Advanced Options
Option Name | Description, Default Value |
---|---|
Subsection: source (topologysource ) |
|
error-timeout
|
See Event Integration Options topic. |
single-run
|
See Event Integration Options topic. |
package-cpath
|
See Event Integration Options topic. |
Subsection: sink (sinktopo ) |
|
interval
|
See Event Integration Options topic. |
error-timeout
|
See Event Integration Options topic. |
single-run
|
See Event Integration Options topic. |
package-path
|
See Event Integration Options topic. |
package-cpath
|
See Event Integration Options topic. |
Subsection: processor (simselfdiscoveryprocess ) |
|
error-timeout
|
See Event Integration Options topic. |
single-run
|
See Event Integration Options topic. |
package-path
|
See Event Integration Options topic. |
package-cpath
|
See Event Integration Options topic. |
Subsection: sink (selfdiscoverysink ) |
|
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 OpsCx for SIM BSM 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: