Added by tugrul kinikoglu, last edited by Berkay Mollamustafaoglu on Jan 27, 2010  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Downloads

Documentation

RapidOSS and Netcool Screencast

RapidOSS Primer for Netcool Users

RapidOSS Netcool Plugin Overview

IBM Tivoli/Netcool Omnibus is an event management solution widely used by service providers and large enterprises. RapidOSS integrates with Netcool Omnibus and makes events from Netcool Omnibus server available through standard interfaces.

The latest reincarnation of RapidOSS Netcool plugin is a complete rewrite. Some of the design principles guiding the development of this release include:

  • user requirements vary significantly. There is no one "perfect design", hence the solution has to be flexible and open to accommodate different needs.
  • client side plugins are painful. Java applets and activex are strictly out. Flash is easier to maintain but not ideal as it still requires a plugin.
  • scalability and performance are crucial and challenging. Many Netcool implementations have tens of thousands active events. The solution should be able to handle high number of events both on the server and client. Scalability and performance on the client side (browser) is particularly challenging.
  • No new/proprietary languages. Don't create new languages or frameworks (done this before). There are number of available open source options out there for pretty much everything. They may not do exactly what we want but often come close enough. A developer who is familiar with common web technologies (application servers, databases, search, javascript, etc.) should be able to learn how to use/enhance the solution with ease.
  • Search is the killer feature. users need to be able to find the events they are interested in easily.
  • Implementation should be straight forward with ideally no external dependencies. Despite the required flexibility and hence toolkit like capabilities, the solution should also have smarts defaults to get it up and running easily.
  • The UI should go beyond replicating desktop client and also take advantage of the native capabilities of the browser instead.

Live Demo

Issue Tracker for enhancement requests and bug reports