Question on websphere portal CacheManagerService : Are there any tools/portlet to monitor these caching activities (PUMA, PAC activities) ?. I used CacheMonitor.ear. But looks like it doesn't monitor this (looks like it just monitors the portlet fragments caches).
This topic has been locked.
5 replies Latest Post - 2012-11-18T07:02:47Z by SystemAdmin
Pinned topic Monitoring Cache (CacheManagerService) in Portal
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-18T07:02:47Z at 2012-11-18T07:02:47Z by SystemAdmin
fang 1000005W3W769 PostsACCEPTED ANSWER
Re: Monitoring Cache (CacheManagerService) in Portal2009-06-14T03:24:12Z in response to vin.appAs far as I know, there is not a public tool to look into portal caches. CacheMonitor app only can monitor those in the Application servers.
The postings on this site are my own and do not necessarily represent the positions, strategies or opinions of IBM.
SystemAdmin 110000D4XK30897 PostsACCEPTED ANSWER
Re: Monitoring Cache (CacheManagerService) in Portal2009-06-15T15:34:38Z in response to fangHello,
If you send me email, then I can send you a Portal Cache Viewer portlet.
There is no official support for the Portal Cache Viewer portlet; it is currently a work in progress and provided "as-is".
CacheMonitor.ear will show detailed information on one cache on one page.
The Portal Cache Viewer portlet will show generic information on all WebSphere Portal caches on one page.
WebSphere Portal support
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.
PeterK2 1000003DR020 PostsACCEPTED ANSWER
Re: Monitoring Cache (CacheManagerService) in Portal2009-09-23T14:38:58Z in response to vin.appCacheMonitor, Exteneded Cache Monoitor does not work on Websphere 22.214.171.124 unless you install a fix
Servlet caching (via cachespec.xml) is not enabled by default.
<components xmi:type="applicationserver.webcontainer:WebContainer" xmi:id="WebContainer_1226808168345" sessionAffinityTimeout="0" defaultVirtualHostName="default_host" enableServletCaching="true">
Need this fix: