8.1 Oracle Reports Services Configuration Files

This section identifies the configuration files associated with Oracle Reports Services. In most cases, you can leave these files untouched. Because they control many aspects of your server environment, you could put that environment at risk if you change a file in some unsupported way. Always keep a back-up of the current version of any configuration file you plan to change.

Note:

Reports application is deployed in no-stage mode in following location:

You might see Reports application configuration files in the configuration directory in the above specified location, but they are stale files; do not edit them. Any modifications done to the Reports application configuration files through Oracle Enterprise Manager or System MBean browser are not reflected in the files located under the configuration directory.

The rwserver.conf file defines initial values for the Reports Server Cache, the Oracle Reports engine, and security; registers valid destination types; and sets other server-related values. This file is automatically created when you start up the server.

The rwbuilder.conf file configures the Reports Server that is embedded in Oracle Reports Builder and Oracle Reports Runtime. All run requests must go through Reports Server, meaning that Oracle Reports Builder requires a server to run reports. Oracle Reports Builder automatically starts a Reports Server to handle its requests. When you run a report from Oracle Reports Builder, this file provides the configuration for the in-process Reports Server instance that is invoked. Like the rwserver.conf file, this file relies on the rwserverconf.xsd file for its data type definitions, though the following elements do not apply: persistFile and security.