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)`

Operations Connector10.11

Integrate > IBM Tivoli > Configure > Configuring Topology Collection

Configuring Topology Collection

Topology Collection Flow

OpsCx for IBM Tivoli makes the topology available to Operations Connector as follows:

The tivolie and tivolim services write the topology data into the discovery store file.

Discovery store file is defined by the value of the discovery-store-event and discovery-store-metric configuration option. By default, the discovery store files are discovery-event.json and discovery-metric.json.
- If you make changes to discovery-store option, make sure you do it in both the topology configuration file and the event and metric configuration files.
- Once a node is written to the discovery file, it remain there and is not updated. If an IP address changes for a node, you must manually modify the entry in the discovery files and manually remove an IP Address CI from the RTSM.

Only CIs which can be resolved with a DNS are discovered from events and metrics. CIs that cannot be resolved are not created.

From the discovery stores, the tivolit service reads the topology data.
The tivolit service writes topology into the tivoli_topology.xml file.

The location of the topology XML output file can be changed in the topology configuration file using the filename option in the Topology XML Output Options section.

If you change the filename option, make sure you change the location in the Source page of the Operations Connector policy for IBM Tivoli topology as well.
The topology policy in Operations Connector reads the tivoli_topology.xml.

Figure 3. Topology collection flow in OpsCx for IBM Tivoli

Topology Configuration

To integrate IBM Tivoli topology into OMi, perform the following steps on your Operations Connector host:

Change the current directory to <OvDataDir>/conf/HPBsmIntTivoli/genint and open the topology integration configuration file in a plain text editor.
In the topology configuration file, edit the following options:
- tivoli-netcool-hostname or tivoli-itm-hostname: Specify the FQDN or IP address of your IBM Tivoli system, depending on which one is used.
- discovery-interval: The interval by which the tivolie service writes data into the discovery store.
  
  The discovery-interval default value is 60 minutes. In the initial configuration, service provider recommends changing this interval to a few minutes, so the topology can be created as soon as possible. Changing this interval does not affect the performance of any system.
  
  However, changing the discovery-interval option only affects the time intervals in which the event data is written into the discovery store. To generate topology faster than in default 60 minutes, you must also change the Polling interval in the Source page of the Operations Connector policy for IBM Tivoli topology.
Optionally, in the event configuration file, edit the following options:
- discovery-field-hostname-itm or discovery-field-hostname-netcool: An attribute in the received IBM Tivoli event that contains a hostname. By default it is set to hostname for ITM and origin for Netcool, but it can be any other, depending on your configuration of IBM Tivoli.
- discovery-field-ip-itm or discovery-field-ip-netcool: An attribute in the received IBM Tivoli event that contains IP address. By default it is set to origin for ITM and node_alias for Netcool, but it can be any other, depending on your configuration of IBM Tivoli. In case you change this option, make sure to also change Related CI in Default Event Attributes.
Optionally, if you filter metrics, edit the following option the metric configuration file:
- tivoli-topology-filtering
  
  If set, only topology for targets set in the filter files is collected.
Review the preconfigured values of basic configuration options and adjust them as needed. Add and configure advanced options if necessary. For descriptions of basic and advanced options, see Configuration Options topic.
Save your changes.
Review the policies to ensure their settings are proper for your OpsCx for IBM Tivoli configuration.
From the Operations Connector web interface, activate the imported policies.
To start the collection service, run the following commands:

ovc -start tivolie

ovc -start tivolim

ovc -start tivolit

OpsCx for IBM Tivoli is able to collect topology only if the tivolie or/and tivolim services are running besides tivolit.

Startup of the services initiates topology collection from IBM Tivoli and forwarding of the topology to OMi.

Verify your connection settings by checking for the presence of the
tivoli_topology.xml file in the <OvDataDir>/datafiles/HPBsmIntTivoli directory on the Operations Connector host. If the file does not exist, check the corresponding OpsCx for IBM Tivoli log file. For details, see Product Log Files topic.

If you deactivate the policy for IBM Tivoli topology, topology changes continue to be collected while the policy remains inactive after the deactivation. The processing and forwarding of accumulated changes resumes when you reactivate the policy.

Configuring Topology Collection

Topology Collection Flow

Topology Configuration

Related topics