Connector Configuration

RapidOSS Admin UI is extended with an "OpenNms" tab to manage OpenNMS connector configuration.

http://localhost:12222/RapidSuite/admin.gsp

Same default administrative userid/password: rsadmin/changeme

Define OpenNMS Connection

In RapidOSS Admin UI http://server:12222/RapidSuite/admin.gsp OpenNms tab, click on "New Connection Data" and enter the connection information for the OpenNMS server.

Connection information include the http url for the OpenNMS server, jdbc url for the postgres database and username and password for OpenNMS server and the postgres database.
(i.e. http://localhost:8980/opennms/), username and password to connect to the server through the web interface.

Note that http url must have the / at the end

Inventory Connector

In the RapidOSS Admin UI OpenNms tab, click on "New Connector" and create a connector with Type "Inventory". Set the Log Level to DEBUG initially to be able to see activity in case of any problems.
Start the connector by clicking on the Start button.
Check the RS_HOME/RapidSuite/logs/<name of your connector>.log file to see the log statements written by the connector. If the connector is not able to connect to the database, there may be exception messages in the RapidServer.log file as well. Make sure you can connect to the postgres database via jdbc through the jdbc url you've specified in the connection definition.
If the connector is working you should be able to see objects in RapidOSS. Go to RapidOSS UI Inventory tab (http://server:12222/RapidSuite/inventory.gsp) to see whether objects are added to RapidOSS repository.

Inventory connector consists of a datasource and a periodic script.

Inventory Datasources

RapidOSS integrates with other systems via datasources. Datasources encapsulate the connection information and use the operations to work with the external systems. SingleTableDatabaseDatasource objects are used to work with various postres database tables that have device, interface, service data.

OpenNMS Available Graphs

RapidOSS OpenNMS plugin includes a JSP page (OpenNMS/jetty-webapps/opennms/rapidcmdb/graphresultsasxml.jsp) that is deployed on OpenNMS server and provides list of graphs for each object (device, interface, etc.) in XML format.

Inventory Script

<connectorname>.groovy script (RS_HOME/RapidSuite/scripts directory) is implemented as a periodic script in order to retrieve device (node), interface, service, and graph information from OpenNMS server and create/update/remove objects in RapidOSS.

Inventory script also calls the Available Graphs page to retrieve the list of graphs available for each object.

Alarm Connector

In the RapidOSS Admin UI OpenNms tab, click on "New Connector" and create a connector with Type "Alarm". Set the Log Level to DEBUG initially to be able to see activity in case of any problems.
Start the connector by clicking on the Start button.

Alarms Datasource

RapidOSS integrates with other systems via datasources. Datasources encapsulate the connection information and use the operations to work with the external systems. SingleTableDatabaseDatasource objects are used to work with postres alarm table.

Alarms Script

<connectorname>.groovy script (RS_HOME/RapidSuite/scripts directory) is implemented as a periodic script in order to retrieve alarms from OpenNMS server and create/update/remove event objects in RapidOSS.

Starting the Connectors

In the RapidOSS Admin UI OpenNms tab, click on the start button next to the connector to start the connector. When you click on the Start button for your connector in the connectors list, the Start button will change to a Stop button. If there is an error in connection information or connector configuration, or if the OpenNms server or database is not available, etc. an error messages is displayed in the Admin UI. The error message will also be printed to the RS_HOME/RapidSuite/logs/RapidServer.log file in more detail.

Once you start the connector successfully, you can go to the RapidOSS Operations Console (http://localhost:12222/RapidSuite) and see the events, devices, interfaces, etc..