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 |
|
![]() |
![]() |
This chapter contains step-by-step instructions for upgrading Oracle9iAS Reports. It contains the following sections:
Section 9.2, "Components Related to OracleAS Reports Services"
Section 9.4, "Validating the OracleAS Reports Services Upgrade"
Section 9.5, "Configuring OracleAS Reports Services Security"
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
The Oracle Application Server components listed below are integral to OracleAS Reports Services functionality:
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.
Copy the cgicmd.dat
file from <
source_MT_OH
>/report60/admin/server
to <
destination_MT_OH
>/reports/conf
.
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.
(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 variableREPORTS_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.
|
(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.
(UNIX only) Change all references to spoolcmd.sh
to rwlpr.sh
. The executable's name has changed in 10g (9.0.4).
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).
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.
Register the installed in-process server with OracleAS Portal. See http://download.oracle.com/docs/html/B10314_01/pbr_portal.htm#1007992
.
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
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):
OracleAS Reports Services is secure by default
Application and data security is provided by Oracle Application Server Single Sign-On and Oracle Internet Directory, and resource security is provided by OracleAS Portal.
This section explains how to configure and use the security features of OracleAS Reports Services.
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:
Set SINGLESIGNON=NO
in <
destination_MT_OH
>/reports/conf/rwservlet.properties
.
Restart the OC4J_BI_FORMS OC4J instance.
Start the Reports server in secure mode.
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.
Validating the Infrastructure configuration involves testing the functioning of the database, OracleAS Single Sign-On, and Oracle Internet Directory. Follow these steps:
Test the database by following these steps:
Start the OC4J_BI_FORMS instance in the middle tier.
Configure the TNS entries for the database in the <
destination_MT_OH
>/network/admin/tnsnames.ora
file.
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.
Test the OracleAS Single Sign-On configuration by following these steps:
Start the Reports server in secure mode.
Submit a report request using the Reports servlet.
The OracleAS Single Sign-On authentication screen appears.
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.
Test the Oracle Internet Directory configuration by following these steps:
Create users and groups in the LDAP directory.
Start the Reports server in secure mode.
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.