14 Oracle9iAS Reports Services

This chapter discusses the following topics:

Section 14.1, "General Issues and Workarounds"

14.1 General Issues and Workarounds

This section describes general issues and their workarounds for Oracle9iAS Reports Services.

14.1.1 Reports Configuration Assistant Fails during Installation

During installation, if the Reports Configuration Assistant fails and gives the following message:

Process destroyed exception (in the installer configuration palette)

then perform the following procedures:

Remove Security Page:

Log on to Oracle9iAS Portal.
Click Builder.
Click Navigator.
Click Contents for the Portal Design-Time Pages page group.
Click Pages.
Click Delete for the Oracle Reports Security page.

Remove Security Provider:

Log on to Oracle9iAS Portal.
Click Builder.
Go to the Build tab by clicking Build.
In the Providers portlet, type ORACLE REPORTS SECURITY in the name field.
Click Delete.

Run rwaddpag.sql:

Log on to the Oracle Internet Directory and obtain the Oracle9iAS Portal user database password.
Log on to the metadata repository as the Oracle9iAS Portal user and run the following script:
```
ORACLE_HOME/portal/admin/plsql/wwd/rwaddpag.sql
```
This creates the Reports portlet in Oracle9iAS Portal.

Alternatively, you can create a tnsnames entry and execute the script as the Oracle9iAS Portal user with the user password obtained from the Oracle Internet Directory in Step 1.

14.1.2 Running JSP Reports from Oracle9iAS Portal

When you run JSP reports from Oracle9iAS Portal, you need to have a complete path for the CSS file because Oracle9iAS Reports Services and Oracle9iAS Portal have different virtual directories. For example, if you use css/my.css for a JSP report in Oracle9iAS Portal, the browser will construct the URL as follows:

http://<server>:<port>/<portal-path>/css/foo.css

This URL will not work. The URL needs to be as follows, which requires you to enter a fully qualified path in the JSP report:

http://<server>:<port>/reports/css/foo.css