Publishing Reports to the Web - Downloads - Oracle

Table 3–3 Attributes of the cache element
Attribute Valid values Description
class see the Description
column
Configuring Reports Server
You can also enter from zero to multiple properties under the cache element.
Properties are name/value pairs recognized and understood by the implementation
class you register under cache. For example, if you use the default cache Java class
that is provided with OracleAS Reports Services, your configuration entry might look
like this:
In the preceding example, cacheSize is measured in megabytes, and cacheDir,
which points to the location of the cache, is specified for a Windows platform. On
UNIX, use UNIX standards, for example:
The default cache Java class also provides the following properties:
■ maxCacheFileNumber is the maximum number of files allowed in the cache. For
example:
■ ignoreParameters lists any report parameters you want to be ignored when
Reports Server constructs the cache key. (The cache key is used by Reports Server
to determine if an incoming job request matches existing output in the cache.)
3.2.1.4 engine
Example
Default: oracle.reports.cache.RWCache
A fully qualified Java class that implements the
oracle.reports.cache.Cache interface.
Required/Optional
Required. You must have at least one engine element in your configuration file, and
you can have more than one.
Description
The engine element identifies the fully qualified Java class that starts an engine and
provides a number of attributes that set operational controls on the engine. You can
use the default engine provided with OracleAS Reports Services
(oracle.reports.engine.EngineImpl) or develop your own implementation
through the OracleAS Reports Services Engine API. As an example of a custom engine,
Configuring OracleAS Reports Services 3-9