|
Traverse provides a rich set of APIs and open extensibility for integrating with existing systems or technology that Traverse needs to co-exist with. The API and external feeds provide interface points to either import or export data throughout the IT environment. The configuration database API can be used with Perl, Java, C or any similar language, and allows provisioning and updating users, devices and tests.
The standard Traverse authentication methods can be overridden by creating plug-in Java classes or scripts. This allows the use of custom authentication databases or other site-specific authentication methods to control access to Traverse. Additionally, Traverse provides the facility for integrating with a Web portal and using the Web portal's authentication mechanism.
External Data Feed
Traverse provides an External Data Feed (EDF) mechanism that allows external data to be sent to and processed by Traverse as though it had been collected by Traverse itself. Any external tool can send results and events for any existing test, and the result/event will be processed as if a Traverse monitor had polled the result. The EDF can handle external data feeds for pre-tested structured data or raw ASCII text data.
Plug-in Actions
The standard action framework in Traverse can be extended easily using the Plug-in Framework to run any external program. The device name and test information can be passed to the external program to build very flexible actions (which can then use the API to query the state of another device and test before executing a corrective action).
Plug-in Monitors
Traverse supports custom plug-in monitors (Java, C, Perl, shell), which are treated as integrated components of Traverse. The plug-in monitors provide a multi-threaded framework used by Traverse’s own monitors. They have an associated XML configuration file describing the test type, default thresholds and various display parameters.
| 
