Hi,

Ideally, every custom view will have the auto refresh to work in a Application Client, Can you let me know , how you created the custom view and also on how the above code snippet is used. You can provide the complete working sample, procedure you followed for noticing this issue, and any conf file modification you have done and the details of incoming alerts that should have triggered the auto refresh.

Thanks
nms-support

Below is the source code of the CustomClassInterface implementation.
Since I'm just doing bugfixing of what was made by someone else who I cannot contact, I'm not aware of any conf file modification related to this.
If there's a conf file that I should verify, please let me know which one is it.
Is there a filter or config file where I can specify which alarams should trigger auto refresh?

1. public class CustomAlarmViewer
2.        implements CustomClassInterface
3. {
4.    /**
5.      * The setProperties method intercepts calls from the client and
6.      * grabs any properties that are passed in.
7.      * These properties are then parsed and the alert applet is shown
8.      * for the given props.
9.      * @param p Array of Properties objects - typically just 1 element in
10.      *          the array.
11.      *
12.      **/
13.     @Override
14.     public void setProperties(Properties p[])
15.     {
16.         if (p == null)
17.             return;
18.         hnLog.debug("(" + Arrays.toString(p) + ")");
19.         for(int count=0;count < p.length;count ++)
20.         {
21.             // Look for the obj name in 'objName'
22.             // and if it is not found there, look in 'NAME'
23.             // 'objName' is for map symbols and 'NAME' is for tree nodes.
24.             String objName=(String)p[count].get("objName");
25.             if(((objName != null) && (objName.indexOf( "objName") >= 0)) ||
26.                 (objName == null) || objName.equals("null"))
27.             {
28.                 objName = (String)p[count].get("NAME");
29.                 String objName2 = hnDomain.stripMapName(objName);
30.                 // If there's no map name in it,
31.                 // we just use the objName directly.
32.                 if (objName2 != null)
33.                     objName = objName2;
34.             }
35.  
36.             showAlerts(objName);
37.         }
38.     }
39.     private void showAlerts(String objName)
40.     {
41.         TopoAPI tApi = null;
42.         String displayName = "";
43.         ManagedObject mo = null;
44.         try
45.         {
46.             tApi = (TopoAPI)emsServices.lookup("TopoAPI");
47.             if (tApi != null)
48.             {
49.                 mo = tApi.getByName(objName);
50.                 displayName = mo.getDisplayName();
51.             } else {
52.                 hnLog.error("Error looking up TopoAPI");
53.                 return;
54.             }
55.         }
56.         catch (Exception ex)
57.         {
58.             hnLog.error("Error looking up TopoAPI, " + ex);
59.             return;
60.         }
61.         Properties prop = new Properties();
62.         prop.put("PANEL_NAME","AlertApplet");
63.         prop.put("GROUPNAME",mo.getName());
64.         Event event = new Event(this, NmsPanel.CHANGE_PANEL_EVENT, prop);
65.         // forms NmsEvent object.
66.         NmsPanelEvent nmsevt = new NmsPanelEvent(event);
67.         //fires the NmsEvent
68.         NmsClientUtil.getMainPanel().handleNmsPanelEvent(nmsevt);
69.     }
70. }

WebNMS/mapdata/menus/ovnSystem.xml:

1. ...
2. <MENU name = "System" shortcut_key = "S">
3.   <DOUBLECLICK>
4.   </DOUBLECLICK>
5.   <MENU-ITEM name="Alarm Management">
6.   <OPERATION name="Alarm Management"/>
7.     <JAVA-UI
8.       action_type="INVOKE_CLASS"
9.       action_value="com.hatteras.ems.client.alarms.CustomAlarmViewer?objName=${objName}&amp;NAME=${name}">
10.     </JAVA-UI>
11.   </MENU-ITEM>
12. </MENU>

Hi,

Why the "event firing mechanism" described here:
http://www.webnms.com/webnms/help/developer_guide/java_client_framework/all_about_nms_panels/java_developer_tips_nmspanels.html#Invoking_nmspanel_programmetically
does not work same like I invoke it from the GUI?

What I specifically need is to invoke alarm panel from right-click menu of the selected network object (switch) and list only those alarms that belong to the selected switch. But I also expect that the list of alarms is updated whenever an alarm update happens for this selected object.

Correct me if I'm wrong, but in the code above I only send the event to the already existing panel that has extended the AlertApplet, right?

Tree.xml:

1. <LEVEL-1 ICON-FILE="images/alarm.png"
2.              TARGET="center"
3.              MENU-FILE-NAME="alertsmenu.xml"
4.              MODULE-NAME="Alerts"
5.              TABLE-COLUMNS="Severity=severity=55;Failure Object=entity=135;System Name=groupName=100;Category=category=100;Alarm Message=message=275;Date/Time=modTime=155;"
6.              ID="Alerts"
7.              TABLE-POPUP-MENU="View"
8.              TREE-POPUP-MENU="Custom Views,frameoptions.xml,TreeOperations.xml"
9.              URL="jsp/GetAlerts.jsp"
10.              PANEL-KEY="AlertApplet"
11.              Client="All"
12.              TREE-NAME="Alarms"/>

NmsPanels.conf:

1. <PANEL SHOW-TREENODE-PROPERTIES="true"
2.         className="com.adventnet.nms.alertui.AlertApplet"
3.         TABLE-SELECTION-BGCOLOR="180-180-180"
4.         PANEL-KEY="AlertApplet"
5. />

So I see the only difference in that if the alarms panel is invoked programmatically, the listed alarms are not updated when e.g. their severity changes.

Hi,

The refresh on a temporary custom view works for me without any issues and I would want you to check on the same once. I just selected the AlarmApplet, used the search to select only the "failure object" starting with s. This action showed a Temporary Custom View with no Objects. Immediately, I raised an alarm for an object starting with letter s, and the same got displayed for me in the Temporary Custom View. This works fine in a permanent customview as well. Please attempt the above step from UI and let me know how it works.

Also, I wanted you to mail me the source, the conf file changes etc, to me and also on the step to reproduce if you continue to face the problem. You can mail these to nms-support@webnms.com by quoting the support ID as 3102887.

Please note, the AlertApplet will get the refresh triggered and Since you have the AlertApplet being invoked from your filter, this should also get the required updates too.

Thanks
Swami

Hi Swami,

I did some further investigation.

I have extended explicitly the AlertApplet and updated the NmsPanel.conf

1. <PANEL SHOW-TREENODE-PROPERTIES="true"
2.         className="com.overture.oms.client.alert.CustomAlertApplet"
3.         TABLE-SELECTION-BGCOLOR="180-180-180"
4.         PANEL-KEY="AlertApplet"
5. />

1. public class CustomAlertApplet extends AlertApplet
2. {
3.     @Override
4.     public void setProperties(Properties props)
5.     {
6.         super.setProperties(props);
7.     }
8. }

I compared the following three scenarios for which I got the following properties in the props parameter of the setProperties() method:

1. Alarms displayed without any filter
   props: {Type=All, REFRESH_EACH_TIME=false}
   
   
2. user defined and saved filter (properties stored in db - CustomViewProps table)
   props: {Type=Alerts.431652489, REFRESH_EACH_TIME=false}
   db dump:
   MODULE;VIEWID;USERNAME;CRITERIAID;PROPKEY;OPERATOR;PROPVALUE1;PROPVALUE2
   Alerts;Alerts.431652489;admin;4;groupViewMode;=;none;NULL
   Alerts;Alerts.431652489;admin;5;groupName;=;overture-1400-b.sde;NULL
   
   
3. custom temporary
   props: {tempSelected=All, Arg=temporary, GROUPNAME=overture-1400-b.sde}
   in this case the alarm summary view (graph) is updated properly, but the rows in the Alarms panel remains unchanged until user presses F5.
   

1 and 2 works fine, but 3 does not.

I have tried to play with the properties passed to the setProperties() method, but no clue how to make the temporary alerts panel updating itself when an alarm changes.

From what I know we use the WebNMS version 5.2. So if you tested it on a newer version, we may find a clue.

I have also noticed that in case 1 and 2 the following methods are called when an alarm change event appears:

• NmsCustomPanel.correctTotalNumbers(NmsTableModelEvent arg0)
• AlertApplet.doTheUpdate(NmsTableModelEvent tabEvt)
  

but they are not called in case 3.

From the stack I saw that AlertApplet.doTheUpdate() is called from CustomClient.run() - line 1282

1. (public abstract class com.adventnet.nms.startclient.CustomClient implements com.adventnet.nms.startclient.SocketConnection, com.adventnet.nms.failover.FailOverListener)

as well as the NmsCustomPanel.correctTotalNumbers() - line 1281

1. (public abstract class com.adventnet.nms.startclient.NmsCustomPanel extends com.adventnet.nms.startclient.AbstractBaseNmsPanel implements java.lang.Runnable, java.awt.event.ItemListener, java.awt.event.KeyListener, java.awt.event.MouseListener, java.awt.event.FocusListener)

So there must be a condition in the CustomClient.run() when those methods are being called and when not.

Thanks,
Milan