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 |
|
Get started
Operations Connector (OpsCx) is a component of Operations Manager i (OMi) that enables you to integrate data from third-party systems (typically enterprise management systems) in OMi. You can integrate events, metrics, topology, and generic output data in OMi.
Operations Connector uses policies to access the data sources. If the data matches the conditions defined in the policies, the data is forwarded in the form of events or metrics to OMi. Policies can also report topology data to OMi in order to create CIs and CI relationships in OMi's Run-time Service Model (RTSM).
Integration Types
Depending on the third-party data source and what type of data you need to collect, you choose one of the following integration types:
-
Remote integration. In remote integrations, installation of software on the third-party system is not required. Operations Connector can be installed on any system in your environment, provided the system meets the installation prerequisites.
-
Local integration. You install Operations Connector directly on the third-party system.
Integration Data
Operations Connector can access the following data sources:
Data Source | Integration Type | Integration Data | Description |
---|---|---|---|
Structured log files |
Local only |
Events Metrics Generic output |
Structured log file policies watch for specific entries added to a log file that is provided by a third-party system. These entries are then matched against the log file structure fields defined in policies by using the OM pattern-matching language . |
Database tables | Local or remote |
Events Metrics Generic output |
Database policies enable you to collect event, metric, and generic output data from a database used by third-party systems by performing a query through a JDBC connection. |
Perl scripts | Local |
Events Metrics Generic output |
Perl script policies enable you to collect event, metric, and generic output data using Perl scripts. |
Web service requests | Local or remote |
Events Metrics Topology Generic output |
REST Web service listener policies process the data received by the Operations Connector REST Web service listener. |
SNMP traps | Local or remote | Events |
SNMP trap policies process SNMP traps received by Operations Connector from third-party systems. |
XML files | Local only |
Events Metrics Topology Generic output |
XML file policies watch for specific entries added to an XML file provided by a third-party system by trying to match against a regular expression. The log file must be a local file. |
Open message interface messages | Local only | Events |
Open message interface policies process messages sent by the Operations Connector opcmsg command-line tool. |
Scheduled tasks | Local only | Events |
Scheduled task policies enable you to schedule commands to run on the Operations Connector system. Scheduled task policies send an event to OMi to indicate the start, success, or failure of the command. |
Operations Connector Data Consumers
The following applications consume the data:
-
Operations Manager i (Events, Operations Connector Topology)
-
Performance Graphing (Metrics)
If you have a CI monitoring five minutes of data and there are multiple data points within the duration, the graph shows only the last data received within the duration.
-
Run-time Service Model (Topology)
Available out-of-the-box Integrations
You can use one of the out-of-the box integrations that are available for Operations Connector. Alternately, you can also develop your own custom integration that suits your requirements.
See the Integrate topic for more information about these out of the box integrations.
Each of these Operation Connectors integrates with the third-party products and Operations Manager i (OMi) so that the gathered systems-management data about the events, topology, and metrics in a third-party product environment is made available to the OMi solution.
Such data can then be monitored and processed properly within OMi. Operation Connectors integrations therefore enables you to establish a link between a third-party environment and operations management in OMi.
The list of integrations with third-party products is updated continuously. For details and for download information, see the Integration Catalog.
Related topics
Structured Log File Policies (Events, Metrics, and Generic Output)
Database Policies (Events, Metrics, and Generic Output)
REST Web Service Listener Policies
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: