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:DOMAIN_HOME/servers/WLS_REPORTS/tmp/_WL_user/reports_version/random_string
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 System MBean browser are not reflected in the files located under the configuration directory.
The correct location of Reports application configuration file is:
DOMAIN_HOME/config/fmwconfig/servers/WLS_REPORTS/applications/reports_version/configuration
The configuration files associated with Oracle Reports Services are listed and described in Table 7-1.
Note:
The paths specified in Table 7-1 are the same for both Windows and UNIX environments, though they are expressed here using the Windows backslash convention (\).Table 7-1 Oracle Reports Services Configuration Files
Component | Configuration File |
---|---|
For Standalone servers:
For In-process servers:
The The See Section 7.2, "Reports Server Configuration File". Reports Server network configuration file:
ORACLE_HOME\reports\dtd\rwnetworkconf.xsd
The |
|
ORACLE_HOME\reports\dtd\rwserverconf.xsd
${DOMAIN_HOME}/config/fmwconfig/components/ReportsToolsComponent/<reports_tools_name>/rwbuilder.conf
The The Reports Builder network configuration file:
ORACLE_HOME\reports\dtd\rwnetworkconf.xsd
The |
|
ORACLE_HOME\reports\dtd\rwservlet.xsd
$DOMAIN_HOME\config\fmwconfig\servers\<WLS_SERVER_NAME>\applications\reports_<version>\configuration\rwservlet.properties
The See Section 7.3, "Oracle Reports Servlet Configuration File". Reports Servlet network configuration file:
ORACLE_HOME\reports\dtd\rwnetworkconf.xsd
The |
|
ORACLE_HOME\reports\dtd\bridgeconfig.xsd
${DOMAIN_HOME}/config/fmwconfig/components/ReportsBridgeComponent/<reports_bridge_name>/rwbridge.conf
The See Section 7.4, "Oracle Reports Bridge Configuration File". Reports Bridge network configuration file: Note: The directory, ORACLE_INSTANCE\config\ReportsBridgeComponent is not created by default. Instead, it is created when a user creates a Reports Bridge through
ORACLE_HOME\reports\dtd\rwnetworkconf.xsd
The |
In 12c reports system component config files are centralized in AdminServer machine
${DOMAIN_HOME}/config/fmwconfig/components/<componentType>/<componentName>/rwserver.conf
System components mean - Reports Server, Reports Tools and Reports Bridge
They are replicated to remote machines if the component is targeted to remote machine. But the central copy will be the source of truth
In remote machine they are available in same location
When a change is made to central copy it is replicated to remote machine
If change is made via mbeans (recommended), then change is immediately replicated to remote machine when the NodeManager in remote machine is up.
If change is made manually, then change is replicated to remote machine when AdminServer is restarted and when the NodeManager in remote machine is up.
This means do not make any change to remote copy as they will be overwritten with central copy next time when AdminServer / remote NodeManager starts communicating
Reports application configuration is not centralized
${DOMAIN_HOME}/config/fmwconfig/servers/<managedServerName>/applications/reports_<version>/configuration/
They will be local to the machine where the corresponding WLS_REPORTS is targeted
However some config like logging.xml is a Server level config and is central in nature and replicated as explained above.
${DOMAIN_HOME}/config/fmwconfig/servers/<managedServerName>/logging.xml