Publishing Reports to the Web - Downloads - Oracle

Configuring Reports Server
you may have developed an engine to execute an operating system command should
an event occur in your database.
Note: Look for upcoming information about Oracle Reports APIs
on the Oracle Technology Network, (http://otn.oracle.com)
The engine element has several attributes, described in Table 3–4.
Table 3–4 Attributes of the engine element
Attribute Valid values Description
id string A keyword, unique within a given configuration
XML file, that identifies a particular engine
element. This can be a text string or a number, for
example:
id="rwEng"
class see the
Description
column
3-10 Oracle Application Server Reports Services Publishing Reports to the Web
Default:
oracle.reports.engine.EngineImpl
A fully qualified Java class that implements two
interfaces: oracle.reports.engine.Engine
and
oracle.reports.engine.EngineInterfac
e.
classPath string The directory path to the Java class specified in
the class attribute. To specify the directory, use
the conventions required by the server platform,
for example:
Windows:
classPath="%ORACLE_
HOME%\myEngine.jar"
UNIX:
classPath="$ORACLE_
HOME/myEngine.jar"
initEngine number Default: 1
The number of engines you want Reports Server
to start at initialization.
maxEngine number Default: 1
The maximum number of this type of engine that
can run on the server.
minEngine number Default: 0
The minimum number of this type of engine that
is maintained by the server.
engLife number Default: 50
The number of jobs the engine can run before the
engine is terminated, and, if necessary, a new
engine is started. This feature is available to
thwart memory leaks.