Improving OMNIbus Web GUI Client Performance using Dashboards instead of Multiple AELs
SteveHowell 2700029KG6 Visits (9681)
When Netcool OMNIbus Web GUI users wish to monitor events for several different scenarios, it is not uncommon for the user to open multiple AELs over many tab pages in TIP (or even combining many AELs onto a single page). If each AEL was configured to use a different filter then this would allow the user to monitor different sets of events without frequent opening and closing of TIP tab pages.
However, doing this can lead to poor performance on the client machine, primarily due to the amount of memory being consumed in total by all the Java applets running in the browser. A worst case is that the client's Java plugin will eventually run out of available heap memory, resulting in the client JVM being unable to continue processing.
A solution to this is to use a Web GUI event dashboard which updates a single AEL on the same page. This would mean that only 2 applets would be running at a time, vastly reducing the strain on system resources.
To start with, you would need to create a new TIP page, and add an Event Dashboard portlet and Active Event list portlet to it. You would configure the dashboard to contain one monitor box for each filter for which you wish to monitor the related events. Importantly, in the Single-Click Action setting for the dashboard, you should select "Update AEL on the Same Page":
Then, once the page is saved and opened, you can easily switch between scenarios to monitor by clicking on the appropriate monitor box. The AEL on the page will be refreshed, which avoids the wait for a new AEL to be opened: