Configuring Proxy Information Oracle Fusion Middleware Online Documentation Library

7-22 Publishing Reports to the Web with Oracle Reports Services

7.17 Modifying Reports Configuration Settings Using the System MBean Browser

To modify Oracle Reports configuration settings using the System MBean Browser: 1. Start Oracle Enterprise Manager Fusion Middleware Control and display the Farm Home page.

2. Select Fusion Middleware ReportsDomain WLS_REPORTS. The WLS_

REPORTS page is displayed.

3. From the WebLogic Server menu, choose System MBean Browser. Fusion

Middleware Control displays the System MBean Browser page. 4. Click the plus + symbol in the left column to expand a node in the navigation tree and drill down to the MBean you wish to access. The navigation tree expands to display links for viewing or updating settings. Each node in the navigation tree represents settings in a configuration file.

5. Click a node in the navigation tree, and click the Attributes tab to display the

details for a group of attributes. Attribute details include name, description of each attribute, access details and its current value. 6. Update an attribute value in one of the following ways: ■ Using the current page: Enter a new attribute value into the Value field for the appropriate row. Click Apply to apply the changes. ■ Displaying a page to view or update the setting: Table 7–3 Reports Configuration MBeans Configuration MBeans Associated Configuration File ServerConfigMXBean rwserver.confrwbuilder.conf JDBCPDSConfigMXBean jdbcpds.conf DiscoveryServiceConfigMX Bean rwnetwork.conf TextPDSConfigMXBean textpds.conf XMLPDSConfigMXBean xmlpds.conf CgicmdConfigMXBean cgicmd.dat RWServletConfigMXBean rwservlet.properties BridgeConfigMXBean rwbridge.conf ScreenprinterConfigMXBea n screenprinter.ppd Note: All Reports environment variables that are set in the registry are not exposed using MBeans. However, if they are specified in the server configuration file ENVID, the environment variables are exposed by ReportsServerConfigMXBean. Similarly, all environment variables used in server startstop shell scripts are not exposed using MBeans. Administering Oracle Reports Services Using Oracle Enterprise Manager 7-23 Click the link in the Name column to display a new page. Enter a new attribute value in the Value field. Click Apply to apply the changes. Click Return to close the page and display the navigation tree. 7. Repeat the previous steps to view or update another attribute value.

7.18 Diagnosing Issues

To help diagnose issues, you can use the Oracle Enterprise Manager logging functionality: ■ Specifying Logging Information ■ Diagnosing Font Issues

7.18.1 Specifying Logging Information

To specify information to be saved in log files for Reports Server or Reports Application in-process Reports Server:

1. Log in to Oracle Enterprise Manager.

2. Navigate to the component Home page see

Section 7.3, Viewing the Component Topology .

3. From the Reports menu, select Logs Log Configuration.

Alternatively, from the Reports Menu, click Administration Advanced Configuration . From the Reports Application Diagnostics window, click the link to Advanced Log Configuration. The Log Configuration page is displayed.

4. Select the Log Levels tab.

5. In the Oracle Diagnostic Logging Level Java Level section, change the log levels

as desired see Table 24–4, 11g ODL Message Types vs 10.1.2 Trace Options .

6. Select the Log Files tab.

7. Select the log handler that you want to modify and click the Edit Configuration

tab

8. Enter a new path in the Log Path field to change the log file location, if necessary.

9. Change the Maximum Log File Size MB and Maximum Size of all Log Files

MB properties as desired. In Oracle Enterprise Manager, the rotation policy for log files can be set by specifying the Max Log size and Max number of files properties. For example, if Max Log size is set to 10MB and Max number of files is set to 10, log file rotation automatically takes place when the first log file diagnostics.log reaches 1 MB Max Log size Max number of files = 10MB10. ODL then renames this file to diagnostic1.log and starts logging to a new diagnostics.log. When it reaches a size of 1 MB, it is renamed to diagnostics2.log and logging Note: Only attribute values with write or read-write permissions can be modified.