Configuring the XML/A Cache¶

When JasperReports Server connects to an XML/A provider to retrieve data that populate views and reports, it relies on a cache to improve performance. When data is first requested from the XML/A provider, it is retrieved and cached. Subsequent requests for the data are then fulfilled from the cache until it is refreshed. You can configure the frequency and behavior of the cache’s refresh mechanism by editing a properties file, as shown in the following table.

XML/A Cache Configuration
Configuration File
`…\WEB-INF\applicationContext-olap-connection.xml`
Property	Value	Description
`OLAP4J_CACHE`	`org.olap4j.driver.xmla.cache. XmlaOlap4jNamedMemoryCache`	Do not change this value.
`OLAP4J_CACHE_NAME`	`org.olap4j.driver.xmla.cache. XmlaOlap4jNamedMemoryCache`	Do not change this value.
`OLAP4J_CACHE_MODE`	`LFU`	Specifies the eviction policy to use when determining what data to evict from the cache. Valid values are: `LIFO`: Last In First Out `FIFO`: First In First Out `LFU`: Least Frequently Used `MFU`: Most Frequently Used
`OLAP4J_CACHE_SIZE`	Commercial Editions: `10000` Community Project: `1000`	The number of cache entries to maintain. The number of entries generated is determined by the number of queries sent to the XML/A provider via SOAP.
`OLAP4J_CACHE_TIMEOUT`	Commercial Editions: `3600` Community Project: `600`	The length of time, expressed in seconds, to keep an entry in the cache. The default is one hour in commercial editions and ten minutes in the community project.