Skip Headers

Oracle® Application Server 10g Upgrading from Release 1 (1.0.2.2.x) to 10g (9.0.4)
10g (9.0.4)
Part No. B13674-02
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

9 Upgrading to OracleAS Reports Services

This chapter contains step-by-step instructions for upgrading Oracle9iAS Reports. It contains the following sections:

9.1 OracleAS Reports Services Upgrade Items

An upgrade item is an aspect of configuration that is acted upon during upgrade: a file, executable, or a setting that you must add, change, or delete/replace in the 10g (9.0.4) installation. OracleAS Reports Services upgrade items are described in Table 9-1.

Table 9-1 OracleAS Reports Services Upgrade Items

Upgrade Item Location in Release 1 (1.0.2.2.x) Oracle home Location in 10g (9.0.4) Oracle home Notes
cgicmd.dat reports60/admin /server reports/conf File contents are the same, only the location has changed.
uifont.ali 6iserver/guicommon6/tk60/admin guicommon9/tk90 /admin Cannot be directly overwritten. The 10g (9.0.4) file contains new entries, such as PDF subsetting and embedding.
uiprint.txt 6iserver/guicommon6/tk60/admin guicommon9/tk90 /admin File contents are the same, only the location has changed.
reports60.sh/reports.sh 6iserver/reports60.sh bin/reports.sh You must set REPORTS_PATH to specify the default location of RDF & PLLs.
proxyinfo.xml Not present reports/conf /proxyinfo.xml New configuration file.
cache folder 6iserver/reports60/server/cache reports/cache Folder location change.
printer folder 6iserver/reports60/admin/printer reports/printers Folder location change.
resource folder 6iserver/reports60/admin/resource reports/res Folder location change.
mesg folder 6iserver/reports60/mesg reports/mesg Folder location change.
templates folder 6iserver/reports60/admin/templates reports/templates Folder location change.
spoolcmd.sh spoolcmd.sh rwlpr.sh Executable name change
rwgenkey.sh Not present rwgenkey.sh Executable name change
Default .PPD and other .ppd files 6iserver/guicommon6/tk60/admin/ppd guicommon9/tk90/admin/ppd UNIX platforms only. Printer definition files, contents are the same.

9.2 Components Related to OracleAS Reports Services

The Oracle Application Server components listed below are integral to OracleAS Reports Services functionality:

9.3 OracleAS Reports Services Upgrade Tasks

This section explains how to perform the OracleAS Reports Services upgrade. "Related Documents" provides references to documents that may be helpful as you perform the steps.

  1. Copy the cgicmd.dat file from <source_MT_OH>/report60/admin/server to <destination_MT_OH>/reports/conf.

  2. Copy the customizations (any additions to, or changes from, the original configuration) from the <source_MT_OH>/6iserver/guicommon6/tk60/admin/uifont.ali file to the <destination_MT_OH>/guicommon9/tk90/admin/uifont.ali file. Do not copy the entire file; the base configuration differs between releases.

  3. (UNIX only) Copy the uiprint.txt file from <source_MT_OH>/6iserver/guicommon6/tk60/admin to <destination_MT_OH>guicommon9/tk90/admin.


    Note:

    The contents of this file are the same between releases. In 10g (9.0.4), the variable REPORTS_DEFAULT_DISPLAY=YES is set by default in the reports.sh file during installation. Internally, the display surface is created using the screenprinter.ppd file. This setting makes the DISPLAY environment variable and valid printer unnecessary in UNIX. You need not edit this file unless you want to set REPORTS_DEFAULT_DISPLAY=NO in the reports.sh file.

  4. (UNIX only) Copy the custom environment settings from <source_MT_OH>/6iserver/reports60.sh to <destination_MT_OH>bin/reports.sh. If the Reports ENV variable is in use, refer to the Oracle9i Reports Obsolescense Plan: Oracle9i Reports Statement of Direction at http://otn.oracle.com/products/reports/pdf/movingto9i.pdf for obsolescence and 10g (9.0.4) naming conventions.

  5. (UNIX only) Change all references to spoolcmd.sh to rwlpr.sh. The executable's name has changed in 10g (9.0.4).

  6. Register the Reports server in opmn.xml and targets.xml by executing the script <destination_MT_OH>/bin/addNewServerTarget.sh (UNIX) or addNewServerTarget.bat (Windows).

  7. Set the default printer for the in-process server. See http://download.oracle.com/docs/html/B10314_01/pbr_conf.htm, Section 3.8, for instructions.

  8. Register the installed in-process server with OracleAS Portal. See http://download.oracle.com/docs/html/B10314_01/pbr_portal.htm#1007992.

9.4 Validating the OracleAS Reports Services Upgrade

To ensure that the upgrade was successful, run the test report from the Oracle Application Server Reports Services demonstration CD, or known reports from the previous release with the same reports clients or new reports clients. Follow the steps in Running Reports Requests in http://download.oracle.com/docs/html/B10314_01/toc.htm

9.5 Configuring OracleAS Reports Services Security

In Oracle9iAS Release 1 (1.0.2.2.x), the security for OracleAS Reports Services was Portal-based, and the Reports server was not secure by default (security had to be enabled). In Oracle Application Server 10g (9.0.4):

This section explains how to configure and use the security features of OracleAS Reports Services.

9.5.1 Configuring Oracle Internet Directory

OracleAS Reports Services uses Oracle Internet Directory in the Infrastructure installation for the directory services portion of its security implementation. Follow these steps to configure Oracle Internet Directory for OracleAS Reports Services:

  1. Set SINGLESIGNON=NO in <destination_MT_OH>/reports/conf/rwservlet.properties.

  2. Restart the OC4J_BI_FORMS OC4J instance.

  3. Start the Reports server in secure mode.

9.5.2 Using Oracle Application Server Single Sign-On

OracleAS Reports Services uses OracleAS Single Sign-On in the Infrastructure installation for the authentication portion of its security implementation. It is configured by default, so no configuration steps are required. However, note the following guidelines for its use:

  • The Reports server must be started in secure mode.

  • Optionally, you can set SINGLESIGNON=YES in <destination_MT_OH>/reports/conf/rwservlet.properties and then restart the OC4J_BI_FORMS OC4J instance.

9.6 Validating the Infrastructure Configuration

Validating the Infrastructure configuration involves testing the functioning of the database, OracleAS Single Sign-On, and Oracle Internet Directory. Follow these steps:

  1. Test the database by following these steps:

    1. Start the OC4J_BI_FORMS instance in the middle tier.

    2. Configure the TNS entries for the database in the <destination_MT_OH>/network/admin/tnsnames.ora file.

    3. Run a sample report using the Reports servlet and in-process server deployed in the OC4J_BI_FORMS instance.

      If the report executes, the database was accessed successfully and the database connection to OracleAS Reports Services is functioning as it should.

  2. Test the OracleAS Single Sign-On configuration by following these steps:

    1. Start the Reports server in secure mode.

    2. Submit a report request using the Reports servlet.

      The OracleAS Single Sign-On authentication screen appears.

    3. Enter a valid OracleAS Single Sign-On user ID and password.

      If the report executes, the report request was serviced and the OracleAS Single Sign-On configuration is functioning as it should.

  3. Test the Oracle Internet Directory configuration by following these steps:

    1. Create users and groups in the LDAP directory.

    2. Start the Reports server in secure mode.

    3. Submit a request using the Reports servlet, specifying the authid=user/password on the command line (where the user and password is one created in Step a.).

      If the report executes, the report request was serviced and the Oracle Internet Directory is functioning as it should.