Click the Create Reports Server Access link in the Reports Server Access portlet. On the resulting page, the Name internal name and the Portal DB Provider Click Next.

Deploying Reports in Oracle Portal 16-9 2. Navigate to the Builder page.

3. Click the Administer tab.

4. Click the Oracle Reports Security Settings link in the Oracle Reports Security

portlet.

5. Click the Create Reports Definition File Access link in the Reports Definition

File Access portlet.

6. On the resulting page, the Name internal name and the Portal DB Provider

fields contain default values. To include custom values: ■ Enter a unique name in the Name field that will identify the report internally in Oracle Portal, for example, MY_REPORT. This name must follow the Oracle Portal rules for a valid component name; that is: It must be no more than 30 characters It must contain only alphanumeric characters no spaces or special characters allowed. The first character must be a letter not a number. ■ Enter the name that you want to display for this report in the Display Name field. The Display Name is the name that is exposed to your users through Oracle Portal. ■ Select the Portal DB Provider that will own the Reports Server from the Portal DB Provider list of values. The Portal DB Providers displayed are those in which you have privileges to build components.

7. Click Next.

8. Enter or select information as follows: ■ Select the Reports Servers to be available to run this report from the Reports Servers list of values. Use control-click Windows or click UNIX to select multiple servers. ■ Enter the report file name, including its extension in the Oracle Reports File Name field. The report definition file can be an .rdf, .jsp, or .xml file. If the path to this file is included in your REPORTS_PATH environment variable, do not enter it here. If the path is not included in REPORTS_PATH, include it here along with the filename. Do this for all report definition files except those you will run as standalone JSPs. For JSPs, you must define the name as virtual_ pathreportname.jsp. Note: The Display Name, unlike the internal Name, can have spaces in it. Note: All the components you add to or create in Oracle Portal must belong to a Portal DB Provider. Refer to the OracleAS Portal online Help, for more information on how to create a Portal DB Provider. 16-10 Publishing Reports to the Web with Oracle Reports Services ■ Optional Enter a description for this report in the Description field. ■ In the Execute field, select either through servlet or as JSP. The selection you make here will affect the choices that are available on the next wizard page. through servlet: If you plan to run the report through Oracle Reports Servlet rwservlet. as JSP: If you will run a deployed JSP report.

9. Click Next.

10. Select the Destination settings on the Required Parameters page.These settings are only applicable if you run your report through Oracle Reports Servlet rwservlet. At runtime, anywhere you have indicated multiple selections using control-click, a list of values will be offered to your users from which they can set their own runtime information: ■ Types specifies the destination types acceptable for this report. Select the destination types from among Cache, File, Mail, OraclePortal, OracleWireless, Printer, FTP, WebDAV, or custom destination types. If the server you associate with this report supports custom destination types, which you indicated when you registered the Reports Server in Oracle Portal, the types you indicated will display on this list. ■ Formats defines the acceptable output formats for this report. Choose from HTML, HTMLCSS, PDF, XML, RTF, Delimited, Spreadsheet, PostScript, and Character. ■ Printers specifies the registered printers to which this report can be sent. The printers that appear on this list are determined by those you chose when you set up access to the Reports Servers you are associating with this report. When users choose a Reports Server on the runtime parameter form, only those printers that are associated with the selected Reports Server and that are accessible to those users are listed.

11. Select the Parameter Form Template and click Preview Template to see what the

selected template looks like: ■ Parameter Form Template specifies the template that will define the look and feel of the Portal parameter form from which you will run the report. This value is used only when the report is exposed through the Portal. Choose a template from the list of values.

12. Click Next.

13. Define the limits for the reports existing parameters on the Optional Parameters

page: See Also: ■ Appendix B, Environment Variables for more information on Oracle Reports-related environment variables. ■ Chapter 8, Configuring Oracle Reports Services for more information on specifying the virtual path. Note: For information about adding your own templates to this list, see the OracleAS Portal online Help.