Publishing Reports to the Web - Downloads - Oracle

Configuring Reports Server with the Oracle Process Manager and Notification Server and Oracle Enterprise Manager 10g
This tag specifies the name of Reports Server. It must match the Reports Server
internal name from targets.xml.
See Also: Chapter 19, "Managing and Monitoring OracleAS
Reports Services"
For more information about targets.xml.
This tag defines the process for the named Reports Server and associates it with the
OracleAS Reports Services process module.
This tag defines the process characteristics for the named Reports Server. It indicates
whether Reports Server should be restarted when it crashes. It also specifies the
number of Reports Servers started for this process set, which has to be 1 because the
process-set id identifies a single Reports Server name.
The first tag specifies the value for the PATH environment variable for the process. This
variable must be set for the start script to find uname. This environment element is not
needed on the Microsoft Windows platform.
This group of tags gathers together all of the data (parameters) common to the process.
In this particular example, it provides a way to specify that the BATCH parameter be
sent to Reports Server. batch=yes|no is an option to the start and stop commands of
Reports Server. If it is not configured, this option is not passed in to Reports Server.
This group of tags indicates the restart parameters category, which defines parameters
to be used in detecting whether the process has failed and needs to be restarted. If a
notification is not received within the specified reverseping-timeout period, then
the process is considered failed and will be restarted.
This tag delimits the list of components upon which Reports Server depends. For
example, Reports Server typically depends upon, among other things, the Oracle
HTTP Server and Oracle Application Server Containers for J2EE.
OPMN uses dependencies to determine whether to start a process. Like module-data
and environment blocks, dependencies blocks can be defined for multiple
elements within opmn.xml. OPMN creates an aggregate dependency list at the
process set level that contains all of the dependencies defined at or above it. If
duplicate dependencies are defined at different levels, then duplicate checks on that
dependency are made before starting a process.
OPMN has two primary types of dependencies: external and internal. External
dependencies are resources not managed by OPMN (the database, Oracle Internet
Configuring OracleAS Reports Services 3-43