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 > Systems Insight Manager

Systems Insight Manager

Operations Connector integrates the supported Systems Insight Manager (SIM) applications and Operations Manager i (OMi) so that the gathered systems-management data about the events and topology in an SIM environment is made available to the OMi solution. Such data can then be monitored and processed properly within OMi. OpsCx for SIM therefore enables you to establish a link between an SIM environment and operations management in OMi.

For a list of the SIM release versions that OpsCx for SIM supports, see Supported Systems Management Applications topic.

Key concepts

OpsCx for SIM is a product complementary to Operations Connector. It enhances the Operations Connector to provide the following functionality:

Collection of SIM events and topology from SIM environment

OpsCx for SIM identifies hostnames and IP addresses from the received events and forwards topology data to OMi.
Mapping of the collected data to an OMi-compliant form
Customization of the data collection and data mapping
Closure of SIM events from OMi by using backward synchronization of the event resolution states

Deployment options for OpsCx for SIM are bound by Operations Connector. While both must be installed on the same system, remote monitoring capability of Operations Connector enables the applications to reside on a dedicated integration server. In such a setup, the processing, memory, and storage resources of the SIM host are burdened to a lesser degree.

The basic part of OpsCx for SIM is the Generic Integrator module (GenInt). It provides common functionality for integrating Operations Connector and other third-party systems, storage, or infrastructure management application.

The collection, processing, and mapping of events and topology data can be configured in detail as part of advanced configuration of OpsCx for SIM.

SIM Events in OMi Environment

OpsCx for SIM makes SIM events available to OMi as follows:

Events are collected from SIM through its web service interface using the HTTP/SOAP protocol. Two web service requests are used for event collection:
- A request to get all events created from the last collection time.
- A request to get events cleared since the last collection time, not older than one day. This time can be modified.
In OpsCx for SIM, the collected events are processed and sent to the REST Web Service endpoint of Operations Connector.
The collected events are mapped with a Operations Connector policy of the REST Web Service Listener type, and then forwarded to OMi.

Each event is tested if it matches some rule in the policy. If it does, the event is mapped accordingly.

The predefined generic rules in the policy serve as an example and can be changed.

Figure 1. Architectural overview of the SIM event integration with OMi

Operations Connector enables tracing which alert caused an OMi event. It also supports close-state propagation of events. Whenever an alert is closed in SIM, the corresponding event in OMi is also closed.

If backward synchronization of event resolution is enabled, for each event that you close in OMi, the corresponding Systems Insight Manager event is also closed. If an SIM event is closed in OMi, the SIM server must be informed and should also clear this event. Backward synchronization uses two Perl scripts to send an HTTP request to the connection, which clears the event on the SIM server using the SIM web service. If this succeeds, the event state is changed to cleared in SIM.

SIM Topology in OMi Environment

OpsCx for SIM makes SIM topology available to OMi as follows (The process is repeated regularly):

OpsCx for SIM collects topology data from SIM through its web service using the HTTP/SOAP protocol.
The topology collector forwards topology data to the Operations Connector for further processing.
The topology data is mapped by using a Operations Connector policy of the XML File type, and then forwarded to OMi.

Figure 2. Architectural overview of the SIM topology integration with OMi

SIM topology structure is mapped to an equivalent structure in OMi. The topology structure is constructed from three topology entity types:

Configuration items (CIs)
CI attributes
Relations between CIs

Topology objects are mapped to the Run-Time Service Model (RTSM) using the local topology synchronization component provided by the Operations Connector. The mapping rules map the following CI types:

failover_cluster
ip_address
node
nt
unix
management_processor
rack
enclosure
storagearray

Systems Insight Manager

Key concepts

SIM Events in OMi Environment

SIM Topology in OMi Environment

Related topics