Error with iFrame Portlet and DFM "Alerts and Activities"

Answered Question
Feb 27th, 2009
User Badges:

Hello,


we are using LMS 3.1, DFM 3.1.0.

We are trying to set up a view in the public LMS Portal for the 1st level support. Here we would like to include the "Alerts and Activities" dashboard in an iFrame portlet.


(Because the agents should also be able to see informational alerts instead of only critical ones.

The predefined portles from the DFM category don't provide this. Also the "DFM Summary Events" portlet is just a summary with no details and direct access to the alerts.)


We configured the iFrame portlet with the URL "https://<servername>/dfm/AFDAction.do". It works fine as long as the "Alerts and Activities" dashboard has already been opened in another browser window before. If I close the window again, the iFrame portlet continues to work fine.


However, the portlet does NOT work, when I close all browser windows and open a fresh session. After login, the error message pasted below is displayed in the portlet. It goes away and works fine again as soon as I manually open the "Alerts and Activities" page manually in a new window.

We tried the authentication settings but it didn't help. However, when activating the authentication and setting it to "basic" no error message is displayed. Instead the portlet stays blank.


Is there a way to get this working?


Regards,

Andreas



====================================

HTTP Status 500 -


--------------------------------------------------------------------------------


type Exception report


message


description The server encountered an internal error () that prevented it from fulfilling this request.


exception


java.lang.NullPointerException

com.cisco.nm.trx.afd.Action.AFDAction.perform(AFDAction.java:69)

org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1786)

org.apache.struts.action.ActionServlet.process(ActionServlet.java:1585)

org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491)

javax.servlet.http.HttpServlet.service(HttpServlet.java:689)

javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

com.cisco.nm.cmf.util.AccessLogFilter.doFilter(AccessLogFilter.java:100)



note The full stack trace of the root cause is available in the Apache Tomcat/5.5.17 logs.



--------------------------------------------------------------------------------


Apache Tomcat/5.5.17

====================================

Correct Answer by Joe Clarke about 8 years 2 months ago

Why not just add the DFM High Severity Alerts and/or Event Severity Summary portlets instead? These are much better fits in the portal UI.


That said, adding the following worked for me without needing to have AAD open in another window:


http://SERVER/dfm/AFDLaunchAction.do

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Joe Clarke Fri, 02/27/2009 - 08:22
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Why not just add the DFM High Severity Alerts and/or Event Severity Summary portlets instead? These are much better fits in the portal UI.


That said, adding the following worked for me without needing to have AAD open in another window:


http://SERVER/dfm/AFDLaunchAction.do

a.foerster Mon, 03/02/2009 - 02:09
User Badges:

Hello Joe,


thank you very much for your reply. As described above, we cannot use the predefined portlets since the 1st level support should be able to see also informational alerts ("High Severity Alerts" portlet not appropriate). The Event Severity Summary shows only the summary, which again is not enough information.


Anyway, the URL you provided is working perfectly. Thank you very much!


Best regards,

Andreas

Actions

This Discussion