In the Certificate Manager Export wizard, select Base64 encoded X.509 .CER

7-18 Publishing Reports to the Web with Oracle Reports Services .opmnctl stopproc ias-component=emagent_name .opmnctl startproc ias-component=emagent_name 7. Restart Enterprise Manager. After you restart Oracle Enterprise Manager, it detects your addition to the list of Certificate Authorities, and you can successfully monitor the Oracle Reports metrics using the secure Oracle Enterprise Manager Console. Example 7–2 Example Content of an Exported Certificate -----BEGIN CERTIFICATE----- MIIDBzCCAnCgAwIBAgIQTs4NcImNY3JAs5edi5RkTANBgk ... base64 certificate content ... ------END CERTIFICATE------

7.11 Managing Log Files

Oracle Reports 11g Release 1 11.1.1 provides improved diagnosability through logging and tracing enhancements. All Oracle Reports log files follow Oracle Diagnostic Logging ODL format, the standard across Oracle Fusion Middleware, for log format, message types, and log management directives. The log file entries are in Text format default or XML format. For detailed information, refer to Oracle Fusion Middleware Administrators Guide. For information about log file enhancements, see Section 24.3.2, Log Files

7.11.1 Viewing and Searching Log Files

To view and search log files in Oracle Enterprise Manager:

1. Log in to Oracle Enterprise Manager.

2. Navigate to the desired component’s home page see

Section 7.3, Viewing the Component Topology : Reports Server, Reports Application, Reports Bridge, or Reports Tools.

3. From the Reports menu, select Logs View Log Messages.

The Oracle Enterprise Manager Log Messages page is displayed.

4. View the trend metrics; that is, how many errors of each type Incident Error,

Error, Warning, Notification, Trace have been logged in the log files for the component.

5. Use the search options available in the page to search inside log files with various

parameters, such as specific message type or time duration. To modify the information logged in log files to diagnose issues, see Section 7.18.1, Specifying Logging Information . Note: If you change the log path for the in-process server engine that is, oracle.reports.engine logger, ensure that you make similar changes in the logmetadata.xml file. This file resides in the same directory as logging.xml. Administering Oracle Reports Services Using Oracle Enterprise Manager 7-19

7.11.2 Configuring Log Levels

To configure Log Levels in Oracle Enterprise Manager:

1. Log in to Oracle Enterprise Manager.

2. Navigate to the component’s home page see

Section 7.3, Viewing the Component Topology .

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

The Log Configuration page is displayed. 4. Select the Log Levels tab 5. Select the appropriate log level for each Logger Name from the ODL Level drop-down list.

6. Click Apply

7.11.3 Editing Log Files

To edit the log files in Oracle Enterprise Manager: 1. Log in to Oracle Enterprise Manager. 2. Navigate to the component’s home page

3. From the Reports menu, select Logs Log Configuration

The Log Configuration page is displayed 4. Select the Log Files tab 5. From the list of log files that is displayed, select the file which you want to edit 6. Click Edit Configuration... The Edit Log File pop-up window is displayed 7. Edit the required parameters.

8. Click OK

7.12 Modifying Reports Server Audit Configuration

To modify Reports Server Audit Configuration in Oracle Enterprise Manager: 1. Log in to Oracle Enterprise Manager. 2. Navigate to Domain Home page

3. From the WebLogic Domain menu, click Security Audit Policy.

4. From the Audit Level drop-down list, select Custom.

5. Select ReportsServer and click the plus + symbol to expand the User Sessions and Authorization node to edit the corresponding configuration settings. Note: If you change the Log File Format in the Edit Log File window, you must change the file extension in the Log Path field, or manually delete the existing content from the log file. Therefore, the same diagnostic log file does not contain messages of different formats. 7-20 Publishing Reports to the Web with Oracle Reports Services

7.13 Registering Pluggable Destinations with Reports Server

To register a pluggable destination with Reports Server: 1. Log in to Oracle Enterprise Manager. 2. Navigate to the Reports Server Home page see Section 7.3, Viewing the Component Topology .

3. From the Reports menu, select Administration Advanced Configuration.

The Reports Server Advanced Configuration page displays.

4. In the Reports Pluggable Destinations section, enter appropriate Name and Class

values for the new pluggable destination. For example, to register the SecurePDF pluggable destination: Name : SecurePDF Class : oracle.reports.plugin.destination.securepdf.SecurePdfDestinat ion

5. Click Add Destination, then click Apply.

This adds the new destination element to the Reports Server configuration file rwserver.conf, which adds the specified destination to the Report Server’s list of valid destinations for report output.

6. You can also click Add to add the properties for the destination in the Registered

properties.

7.14 Configuring Proxy Information

Some features of Oracle Reports Services support retrieving or sending information through a firewall. For example, the URL engine, the XML data source, the Text data source, and the mail destination features all retrieve or send information through the firewall. For these features to function properly, Reports Server requires certain proxy information. To specify proxy information: 1. Log in to Oracle Enterprise Manager. 2. Navigate to the Reports Server or Reports Application Home page see Section 7.3, Viewing the Component Topology .

3. From the Reports menu, select Administration Advanced Configuration.

The Advanced Configuration page displays. 4. On the Advanced Configuration page, set proxy hosts and ports available for various protocols, such as http, https, ftp, or file. You can also specify the addresses for which proxies can be bypassed. Note: The jars where pluggable destination classes are available must be available in the REPORTS_CLASSPATH environment variable, or in the WebLogic Server classpath in case of in-process servers