Enter parameter values in the Parameter tab and, if desired, schedule the job to

16-26 Publishing Reports to the Web with Oracle Reports Services ■ The header of the rwlang.sql script contains the complete list of all language abbreviations. Edit the script file using any text editor to find out the various abbreviations.

16.3.5 Distributing Report Output to Oracle Portal

To distribute to the ORACLEPORTAL destination from Reports Server: 1. Create a distribution file for example, distribution.xml to distribute report output to Oracle Portal. For example: destinations destype id=customforPortal name=oraclePortal property name=outputpage value=Test_Reports property name=statuspage value=result property name=pagegroup value=test_reports property name=itemtitle value=TestReport include src=report destype destinations

2. Run a report with the following URL:

http:host:portreportsrwservlet?server=reports_server report=report_namedestination=distribution_file distribute=yesuserid=userpassworddb

3. In Oracle Portal, go to the page specified in the URL and make sure the report is

visible.

16.4 Connecting to Oracle Portal

By default, Reports Server can only use Oracle Portal users to connect to Oracle Portal. It cannot use an ordinary userid, such as scotttiger, unless you first assign appropriate privileges to its schema. To assign the appropriate privileges to a schema other than the Oracle Portal schema, you must run the following script from SQLPlus as an Oracle Portal user: ORACLE_HOMEportaladminplsqlworrwgrant.sql Once the script is loaded, it prompts you to enter the connection string for the new schema for example, repapprepapporcl. The script then assigns the appropriate privileges to this new schema. You can then specify this connection string in the destination element in the Reports Server configuration file to connect to Oracle Portal.

16.5 Troubleshooting Information

This section contains information on the various steps that you can take to rectify issues that occur. Note: In this example, you must ensure that pagegroup test_ reports exists in Oracle Portal or specify an existing pagegroup name. Deploying Reports in Oracle Portal 16-27

16.5.1 Resolving Reports-Portal Integration Error When Attempting Create Resource

In Oracle Portal, when configuring Oracle Reports Security settings for Reports Definition File Access, you may encounter an error when editing a report definition file, when you click Run or Run as Portlet. 500 Internal Server Error Unexpected Error. Please contact Administrator This error occurs when all of the following conditions are true: ■ Running in an Interop deployment which allows for a mixed 9.0.29.0.4 environment, with 9.0.4 MT mid-tier, 9.0.4 IM Identity Management, and 9.0.2 MR metadata repository configured to run together. ■ Running Oracle Reports within Oracle Portal, using the SSOCONN parameter. ■ The connection resource specified in the SSOCONN parameter has not been created in the Oracle Internet Directory server. To implement the workaround, perform the following steps:

1. In the 9.0.4 IM ORACLE_HOME, open the following file in a text editor:

ORACLE_HOMEApacheApacheconfmod_osso.conf 2. Add the following flag: OssoRedirectByForm on For example: IfModule mod_osso.c OssoIpCheck off OssoIdleTimeout off OssoConfigFile private1iasinstinstall_set1904infraApacheApacheconfossoosso.conf OssoRedirectByForm on IfModule