Default Reports-Related Groups Creating Reports Users and Named Groups

Deploying Reports in Oracle Portal 16-5

16.1.3 Portal Password in Credential Store

Oracle Reports 11g Release 1 11.1.1 uses credential store to store Portal password as a key. You can also use the credential store to configure database connection information for jobstatusrepository and jobRepository elements. Portal password is stored in the reports credential map with key in the following syntax: portalpasswd_DomainName_InstanceName

16.2 Registering Oracle Reports Components

Before you begin, you must have a sufficient level of privileges in Oracle Portal to access the portlets and complete the tasks required for setting access controls. In order to manage reports in Oracle Portal, you must belong to both the PORTAL_ ADMINISTRATORS and RW_ADMINISTRATOR groups. If you only belong to RW_ ADMINISTRATOR, you will encounter errors when you attempt to create report objects. For more information on joining privilege groups in Oracle Portal, refer to the Oracle Portal Administrators Guide. This section outlines the necessary steps to go about: ■ Registering a Reports Server ■ Registering a Report ■ Registering a Printer ■ Creating an Availability Calendar To perform actions on existing Oracle Portal portlets, refer to: ■ The Manage Portlet

16.2.1 Registering a Reports Server

Before you can define access controls for a Reports Server, you must register your server within Oracle Portal. Registration provides Oracle Portal with the information it needs to identify and locate all available Reports Servers. This becomes particularly important when you register individual reports; during this process you are required to choose from a list of Reports Servers, and servers must be registered to appear on this list. Note: If you modify the Portal password, you must update the value of the key in the Reports credential store. Table 16–1 Sample Values Property Sample Value Name internal name myrep_server Display Name My Reports Server Portal DB Provider PORTAL_APP Reports Server Name rep_machine_name, for example, rep_ myserver1 16-6 Publishing Reports to the Web with Oracle Reports Services To register a Reports Server: 1. Log in as an administrator to Oracle Portal. 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. The Oracle Reports Security portlet enables you to use the security features in Oracle Portal at the time of defining access to the server, printer, calendar, and reports definition file.

5. Click the Create Reports Server Access link in the Reports Server 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 Reports Server internally in Oracle Portal, for example, MY_REPORTS_SERVER. 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 you want to display for this server 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.

Oracle Reports Web Gateway URL for JSP reports http:myias.mycomp.com:7778 Oracle Reports Web Gateway URL for RDF reports http:myias.mycomp.com:7778report srwservlet Availability Calendar COMCAL 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. Table 16–1 Cont. Sample Values Property Sample Value Deploying Reports in Oracle Portal 16-7

8. On the Server Definition page:

■ Enter the name of the Reports Server in the Reports Server Name field. This is the unique name assigned to the server at the time of server creation through OPMN. ■ Optional Enter a description for the Reports Server in the Description field. ■ Enter the URL location of your JSP files in the Oracle Reports Web Gateway URL for JSP reports field. The URL should be in the following format: http:your_web_server.domain:port For example: http:myias.mycomp.com:7779 ■ Enter the URL location of Oracle Reports Servlet rwservlet in the Oracle Reports Web Gateway URL for RDF reports field. The URL should be in the following format: http:your_web_server.domain:portvirtual_path_to_rwservletrwservlet For example: http:myias.mycomp.com:7778reportsrwservlet ■ Optional Select the Run Only Registered Report Definition Files check box. This ensures that only the report definition files registered with Oracle Portal can be executed on this Reports Server. Leave this box unchecked if you want this Reports Server to accept any report definition file, including those not registered in Oracle Portal, as long as the user who submits the report request has access privileges to this Reports Server. ■ Select the printers that you want to make available to this Reports Server from the Printers list. Use control-click Windows or click UNIX to select multiple printers.

9. Click Next.

10. Optional Enter a Custom Destination Type, if you have defined a custom

destination type.

11. Click Next.

12. Optional Enter the Availability Calendar name or click the list button to select

the Availability Calendar that determines the days and times this Reports Server is and is not available to accept report requests.

13. Click Finish.

See Also: Chapter 8, Configuring Oracle Reports Services for more information on specifying the virtual path. See Also: Chapter 13, Configuring Destinations for Oracle Reports Services for more information on custom destination types. See Also: Section 16.2.4, Creating an Availability Calendar