Log in to Oracle Enterprise Manager. Navigate to the desired component’s home page see

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