Why you should consider using WebSphere Dynacache to improve performance and save money with WebSphere Application Server for z/OS.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Hard copy of this document is for temporary reference only. The official version of the document is stored and maintained on-line in the Lotus Notes database titled, “WAS Project Central.” The responsibility of using the official version of this document, and of verifying that any copies are complete and official, lies completely with the user of the document. Please visit the Lotus Notes database on-line for the official version of the document.
Requests served from the FRCA cache are about 8% the cost of requests served from the Dynamic Cache Reduction in CP and ZAAP CPU% leading to cost savingsDisplay FRCA cache statistics
o From MVS console: f <serverName>,display,frca o From MVS console: display tcpip,,netstat,cach o From TSO: netstat cach
– CacheMonitor application shipped with WAS install in the installableApps dir.o Provides
Real-time view of the current state of dynamic cache Verify the configuration of dynamic cache Verify the cache policies Monitor cache statistics Monitor the data flowing through the cache Monitor the data in the edge cache View the data offloaded to the disk Manage the data in the cache
– Provides two functions that are not available with the cache monitor Display the contents of object cache i.e. distributedmap i.e. POJO cache instances. Display the Dynamic Cache mbean statistics for cache instances across all members of the cluster. Installed as an update to the existing CacheMonitor application. All Dynacache customers that use the DistributedMap API leverage the ECM in development and production.
XML cache policy file that contains configuration entries for caching
definitions and rules for Servlet/JSP/ JSTL/ Portlet caching
Allows application developers to specify: What is going to be cached (Servlets, JSP, Java
commands, web services etc.) Where it is going to be cached (memory or disk) When cache items are to be evicted (invalidation) How cache entries are related (invalidation