IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
  • 1.  Atom feed exception

    Posted 03/07/14 07:49 AM

    Hi,

    I’m getting the following exception while opening any portlet from inside Folders > System > Portlets.
    Any clues?

    Thanks,
    Bruno

    2014-03-07 11:43:45 WET (Framework:FATAL) [RID:1580] - [POP.001.0002] A “java.lang.NullPointerException” occurred with the Message “at com.webMethods.caf.faces.data.export.AtomFeedExportProvider.getAutogeneratedValues(AtomFeedExportProvider.java:161)”
    java.lang.NullPointerException
    at com.webMethods.caf.faces.data.export.AtomFeedExportProvider.getAutogeneratedValues(AtomFeedExportProvider.java:161)
    at com.webMethods.caf.faces.data.export.AtomFeedExportProvider.getPropertyKeys(AtomFeedExportProvider.java:85)
    at com.webMethods.caf.faces.data.export.atom.Element.initialize(Element.java:108)
    at com.webMethods.caf.faces.data.export.atom.Element.(Element.java:42)
    at com.webMethods.caf.faces.data.export.atom.Source.(Source.java:34)
    at com.webMethods.caf.faces.data.export.atom.Feed.(Feed.java:31)
    at com.webMethods.caf.faces.data.export.AtomExportBean.writeExportText(AtomExportBean.java:103)
    at com.webMethods.portal.portlet.wm_atomrenderer.AtomRenderer.export(AtomRenderer.java:226)
    at com.webMethods.portal.portlet.wm_atomrenderer.AtomRenderer.render(AtomRenderer.java:160)
    at com.webMethods.portal.framework.presentation.PresentationManager.handlePres(PresentationManager.java:431)
    at com.webMethods.portal.framework.dispatch.DispatchManager.pres(DispatchManager.java:692)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:522)
    at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:424)
    at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:309)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:770)
    at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1448)
    at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82)
    at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:294)
    at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:48)
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419)
    at com.webMethods.portal.framework.impl.NTLMV1Filter.doFilter(NTLMV1Filter.java:67)


    #MWS-CAF-Task-Engine
    #webMethods
    #webMethods-BPMS


  • 2.  RE: Atom feed exception

    Posted 03/07/14 12:46 PM

    If the atom renderer feature is not needed, it can be disabled as a workaround for this problem.

    To disable the atom renderer, login to MWS as sysadmin and go to
    Folders > System > Managers > presManager > renderers > atom

    There, you can disable the atom renderer.

    To re-enable the renderer in Linux, you can “touch” the “wm_atomrenderer.cdp” in the “deploy” folder.


    #webMethods-BPMS
    #MWS-CAF-Task-Engine
    #webMethods


  • 3.  RE: Atom feed exception

    Posted 03/07/14 12:55 PM

    I suspect that someone has created or modified a renderer rule that is now trying to render anything under that folder as an ATOM feed which doesn’t seem right.

    Please review your renderer rules by logging in as sysadmin and checking the list @
    Administrative Folders > Administration Dashboard > User Interface > Manage Rendering Rules


    #webMethods-BPMS
    #MWS-CAF-Task-Engine
    #webMethods