Appboard/2.4/builder/data sources/third party/hp nnmi: Difference between revisions
imported>Jason.nicholls No edit summary |
imported>Jason.nicholls No edit summary |
||
Line 28: | Line 28: | ||
== Entities == | === Entities === | ||
A successful connection will return two data source entities, ''Nodes'' and ''Incidents''. | |||
{|class='wikitable' | {|class='wikitable' | ||
Line 40: | Line 42: | ||
|The Incidents entity contains all incidents from NNM. This is consistent with All Incidents from the Incident Browsing Workspace of the NNM web interface. | |The Incidents entity contains all incidents from NNM. This is consistent with All Incidents from the Incident Browsing Workspace of the NNM web interface. | ||
|} | |} | ||
[[File:HP-NNM-NodesPreview.png|thumb|750px|Example data preview of ''Nodes'']] |
Revision as of 08:00, 4 November 2013
The HP NNMi adapter retrieves information about nodes and incidents from the HP Network Node Manager (NNMi) application.
Data Source Configuration
Configure Connection Settings
The table below details the settings you can configure for a HP NNMi Data Source:
Name | Description |
---|---|
url | The base URL of NNM, which should be in the form of "<protocol>://<host>[:port]/" (http://nnm.test.com:8080/ in this example). The base URL can be tested by entering it in a browser and appending "/IncidentBeanService/IncidentBean?wsdl", which should return an XML file describing the Incident web service. |
cacheTimeout | How long the cache manager will keep a response before re-querying the data source. |
httpAuthUsername | User name credential used to connect to HP NNMi. |
httpAuthPassword | User password credential used to connect to HP NNMi. |
Entities
A successful connection will return two data source entities, Nodes and Incidents.
Entity | Description |
---|---|
Nodes | The Nodes entity contains a list of nodes from NNM. This is consistent with the nodes from the Inventory Workspace of the NNM web interface. |
Incidents | The Incidents entity contains all incidents from NNM. This is consistent with All Incidents from the Incident Browsing Workspace of the NNM web interface. |