After you upgrade to OracleAS Reports Services 11g, review the following sections, which provide information about typical post-upgrade tasks for OracleAS Reports Services users:
When you upgrade to Oracle Reports 11g, the security configuration is not upgraded. As a result, the security configuration of Oracle Reports 11g remains the same as it was before the upgrade.
For information about the security features available in Oracle Reports 11g and how to configure them, see Chapter 15, "Securing Oracle Reports Services".
The following sections describe some other common post-upgrade tasks to complete after upgrading to OracleAS Reports Services 11g:
Any shell scripts that are stored in the bin directory of the Oracle Reports 10g Oracle home, such as reports.sh, rwrun.sh, and rwserver.sh are not upgraded automatically during the upgrade process. Instead, you must change these scripts manually, as needed. After the upgrade, you can find these scripts in the following Oracle Fusion Middleware 11g directory:
ORACLE_INSTANCE/config/reports/bin
OracleAS Reports Services DAT files are upgraded during the upgrade process. However, if job command entries in the DAT files contain references to old Oracle Home path names or invalid path names, then those jobs will fail. Therefore, you must reschedule any such report jobs.
In OracleAS Reports Services 10g, the in-process server target appears in the Oracle Enterprise Manager Application Server Control as Reports Server.
However, after you upgrade to OracleAS Reports Services 11g, the in-process server does not appear as Reports server in Oracle Enterprise Manager Fusion Middleware Control. Instead, it appears as a Reports application, called reports, and you can manage the in-process server target and the Reports servlet on the Reports application page.
Cached Reports output files are not upgraded to Oracle Reports 11g.