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  

7 Upgrading to OracleAS Discoverer

This chapter contains step-by-step instructions for upgrading Oracle9iAS Discoverer to OracleAS Discoverer. The instructions were excerpted from the Oracle Application Server Discoverer Configuration Guide and the Oracle Discoverer Administrator Administration Guide. This chapter contains the following sections:

7.1 OracleAS Discoverer 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 Discoverer upgrade items are described in Table 7-1.

Table 7-1 OracleAS Discoverer Upgrade Items

Upgrade Item Location in Release 1 (1.0.2.2.x) Oracle home Location in 10g (9.0.4) Oracle home Notes
pref.txt

Default user preferences

discwb4/util/pref.txt discoverer/util/pref.txt In 10g (9.0.4), there are additions to the pref.txt file
.reg_key.dc

User-level preferences

discwb4 directory (UNIX)

Registry (Windows)

.reg_key.dc file

(the location is specified in the DC9_REG environment variable) (UNIX)

discoverer/.reg_key.dc (Windows)

In 10g (9.0.4), there are additions to the .reg_key.dc file.
End User Layer (EUL) Not applicable; database schema Not applicable; database schema To upgrade the Oracle Application Server Discoverer End User Layer schema, you use Oracle Discoverer Administrator, shipped with the Oracle Developer Suite 10g (9.0.4).

For more information, see: Oracle Discoverer Administrator Administration Guide in the Oracle Developer Suite documentation library.

URL references http://hostname/Discwb4/html/ english/ms_ie/start_ie.htm

OR

http://hostname/Discwb4/html/english/netscape/start_nn.htm

AND

http://hostname/Discoverer4i/Viewer

http://hostname/discoverer/plus

http://hostname/discoverer/ viewer

There are multiple changes in URL names.
Session timeout configuration Apache/JServ/servlets/disco4iviewer.properties j2ee/OC4J_BI_Forms/applications/discoverer/web/WEB-INF/web.xml The file in the Release 1 (1.0.2.2.x) installation is a text file, plugged into Oracle HTTP Server. The file in 10g (9.0.4) is an xml file that contains many more configuration entities, and is plugged into the OC4J stack.
Discoverer Viewer customizations Apache\Apache\htdocs\disco4iv\html\disco4iv.xml

Apache\Apache\htdocs\disco4iv\html\ viewer_config.xml

Apache\Apache\htdocs\disco4iv\html\ errors.xsl

Apache\Apache\htdocs\disco4iv\html\ functions.xsl

Apache\Apache\htdocs\disco4iv\html\gui_components.xsl

Apache\Apache\htdocs\disco4iv\html\render_table.xsl

Apache\Apache\htdocs\disco4iv\html\scripts.xsl

Apache\Apache\htdocs\disco4iv\html\style.xsl

j2ee/OC4J_BI_Forms/applications/ discoverer/web/WEB-INF/configuration.xml

j2ee/OC4J_BI_Forms/applications/ discoverer/web/common/xsl/ui/ui_config.xml

j2ee/OC4J_BI_Forms/applications/ discoverer/web/common/xsl/*

j2ee/OC4J_BI_Forms/applications/discoverer/web/viewer_files/xsl/*

The file in the Release 1 (1.0.2.2.x) installation is a text file�, plugged into Oracle HTTP Server. The file in 10g (9.0.4) is an xml file that contains many more configuration entities, and is plugged into the OC4J stack.

7.2 Components Related to OracleAS Discoverer

In 10g (9.0.4), OracleAS Discoverer is integrated with OPMN, Oracle Enterprise Manager 10g, and the OC4J Business Intelligence and Forms stack.

7.3 OracleAS Discoverer Upgrade Tasks

This section explains how to upgrade Discoverer from version 4.1 (the version shipped in Oracle9iAS Release 1 (1.0.2.2.x)) to 10g (9.0.4).

Before you begin the upgrade process, ensure that Oracle Application Server 10g (9.0.4) was installed successfully. All of the instructions in this section assume that Oracle9iAS Oracle9iAS Release 1 (1.0.2.2.x) is installed in <source_MT_OH> and Oracle Application Server 10g (9.0.4) is installed in <destination_MT_OH>.

Upgrade tasks are described in the following subsections:

7.3.1 Upgrading Preferences

This section explains how to upgrade Discoverer preferences.

Hint: If Discoverer scripts do not execute on UNIX, run the script file discwb.sh to set the Discoverer environment.

7.3.1.1 Upgrading Default User Preferences

The pref.txt file specifies the default user preferences. To upgrade default user preferences, follow the steps below:

  1. Compare the Oracle9iAS Release 1 (1.0.2.2.x) pref.txt file with the 10g (9.0.4) pref.txt file, as follows:

    Compare <source_MT_OH>/discwb4/util/pref.txt with <destination_MT_OH>/discoverer/util/pref.txt.

  2. If changes have been made to the pref.txt file in the <source_MT_OH> directory, edit the pref.txt file in the <destination_MT_OH> directory and make the same changes.

  3. Apply the default preferences.

7.3.1.2 Upgrading User-Level Preferences on UNIX

If you are upgrading from one Oracle home to another on the same computer using UNIX, follow the instructions below to upgrade user level preferences:

  1. Copy the .reg_key.dc file from the location specified by the DC_REG environment variable to the location specified in the discwb.sh file in <destination_MT_OH>/<installation>/discwb4.

  2. Issue this command:

    <destination_MT_OH>/discoverer/util/migrateprefs.sh -from 102

If you are upgrading from one UNIX computer to another UNIX computer, follow the instructions below to upgrade user level preferences:

  1. Copy the .reg_key.dc file from the location specified by the DC_REG environment variable on the computer on which Oracle9iAS Release 1 (1.0.2.2.x) is installed to the location specified by the DC9_REG environment variable on the computer on which Oracle Application Server 10g (9.0.4) is installed.

  2. On the computer on which Oracle Application Server 10g (9.0.4) is installed, issue this command:

    <destination_MT_OH>/discoverer/util/migrateprefs.sh -from 102

7.3.1.3 Upgrading User-Level Preferences on Windows

If you are upgrading from one Oracle home to another on the same Windows computer, follow the instructions below to upgrade user level preferences:

  1. Issue this command:

    <destination_MT_OH>/discoverer/util/migrateprefs.bat -from 102

    User-level preferences are copied from the Windows registry to the reg_key.dc file.

If you are upgrading from one Windows computer to another Windows computer, follow the instructions below to upgrade user-level preferences from Discoverer Release 4.1 to Discoverer Version 9.0.4:

  1. On the machine on which Oracle9iAS Release 1 (1.0.2.2.x) is installed, from the Start menu, select Run.

    The Run dialog box appears.

  2. Type regedit and press Enter.

    The Registry Editor window opens.

  3. Open the HKEY_LOCAL_MACHINE\Software\Oracle\WebDisco4 registry key.

  4. Choose Registry ->Export Registry File to export the registry key to a file.

  5. Specify a name for the registry export file (e.g. disco41prefs.reg).

  6. Copy the registry export file from the computer on which Oracle9iAS Release 1 (1.0.2.2.x) is installed to the computer on which Oracle Application Server 10g (9.0.4) is installed.

  7. On the machine on which Oracle Application Server 10g (9.0.4) is installed, from the Windows Start menu, select Run.

    The Run dialog box appears.

  8. Type regedit and press Enter.

    The Registry Editor window opens.

  9. Choose Registry-> Import Registry File.

  10. Specify the name of the registry export file to import (e.g. disco41prefs.reg).

  11. Upgrade the preferences by issuing the following command:

    <destination_MT_OH>\discoverer\util\migrateprefs.bat -from 102

7.3.2 Upgrading the End User Layer (EUL)

The version of Discoverer that ships with Oracle Application Server 10g (9.0.4) requires an EUL created or upgraded by Discoverer Administrator Version 9.0.4 (which is shipped with Oracle Developer Suite 10g (9.0.4)). If you have an existing Discoverer Release 4.1 EUL, you must upgrade the EUL from Release 4.1 to Version 5.1 using Discoverer Administrator Version 9.0.4.For more information about upgrading the EUL, see the Oracle Discoverer Administrator Administration Guide in the Oracle Developer Suite Documentation Library.

Before you do anything else, you will create a back up of the Release 4.1 EUL as described in Section 7.3.2.1, "Backing Up the Release 4.1 End User Layer". To use Discoverer Version 9.0.4, Discoverer users must have access to a Discoverer Version 5 End User Layer (EUL). If users were using a Discoverer Release 4.1 EUL, that EUL must be upgraded before it can be accessed with Discoverer Version 9.0.4.The EUL upgrade process creates new Version 5 EUL tables, and then copies metadata from the Release 4.1 EUL tables into the new tables. Existing users can continue working with Discoverer Release 4.1 during the upgrade process because the upgrade process is non-destructive (i.e. the Release 4.1 EUL tables are not deleted).

The prerequisites for upgrading to 10g (9.0.4) are as follows:

  • EUL owners must have the following privileges:

    • CREATE PROCEDURE

    • CREATE SESSION

    • CREATE TABLE

    • CREATE VIEW

    • CREATE SEQUENCE

  • When upgrading to an Oracle 8.1.7 (or later) database, summaries are implemented as materialized views, so the EUL owners must have the following privileges:

    • CREATE ANY MATERIALIZED VIEW

    • DROP ANY MATERIALIZED VIEW

    • ALTER ANY MATERIALIZED VIEW

    • GLOBAL QUERY REWRITE


Note:

To maintain the consistency of data transferred to the upgraded URLs, it is very important that no Discoverer Administrator sessions are opened on the earlier version of the EUL while the upgrade is in progress.

7.3.2.1 Backing Up the Release 4.1 End User Layer

Before you can upgrade a Discoverer Release 4.1 EUL to a Discoverer Version 5 EUL, you must first back up the EUL tables by exporting the EUL owner using the standard database export utility.How to export the EUL owner will depend on:

  • the version of the Oracle client software installed on the computer

  • the version of the Oracle database on which the Release 4.1 EUL resides

The EUL upgrade process creates new Version 5 EUL tables, and then copies metadata from the Release 4.1 EUL tables into the new tables. During the upgrade process, existing users can continue working with Discoverer Release 4.1, because the Release 4.1 tables are not deleted during the upgrade process.

Oracle Corporation recommends that the version of the Oracle database and the version of the Oracle database client software installed on the computer are the same. If the versions are not the same (e.g. if the EUL is on an Oracle8i database and Oracle9i client software is installed on your machine), then you might not be able to follow the instructions below. If you are unable to export the EUL, ask your database administrator to export the EUL for you.To back up a Release 4.1 EUL that resides on an Oracle9i database, using a computer on which Oracle Developer Suite is installed, follow the steps below.

  1. Open a command shell.

  2. Navigate to the directory location to which the End User Layer will be exported.

  3. Issue this command:

    exp <eulowner>/<password>@<dbname> file=<filename>.dmp owner=<eulowner>

    where:

    • eulowner is the database user who owns the End User Layer

    • password is the password of the user who owns the End User Layer

    • filename is the name of the .dmp file that the command creates

    For example, to export an End User Layer owned by the database user hrmgr to a file named hreul.dmp, the command would be:

    exp hrmgr/hrpswrd@HRDB file=hreul.dmp owner=hrmgr

    The End User Layer tables, associated synonyms, views, and other definitions are exported to the specified file in the current directory. When the export is complete, the following message appears:

    Export terminated successfully without warnings.

  4. Close the command shell window.

7.3.2.2 Upgrading the Release 4.1 EUL

After the Release 4.1 EUL is backed up, you can upgrade to Version 5. To upgrade, you open the EUL in the latest version of Discoverer, as described below. The same database user that owned the Release 4.1 EUL will own the Version 5 EUL.


Note:

Release 4.1 end users are not affected by upgrade, and can continue using the Release 4.1 EUL. However, any modifications to workbooks that are made in the Release 4.1 EUL after the upgrade process has begun will not be present in the upgraded EUL.

To maintain the consistency of the data transferred to the Version 5 EUL, ensure that no Discoverer Administrator sessions are opened on the Release 4.1 EUl while the upgrade is in progress.


Follow these steps to upgrade a Release 4.1 EUL to Version 5:

  1. In Oracle Developer Suite, start the Discoverer Administrator and display the Connect to Oracle Discoverer Administrator dialog. In Windows, the navigation path is:

    Start->Programs->Oracle Developer Suite - <Oracle home name>-> Discoverer Administrator

    The Connect to Oracle Discoverer Administrator dialog opens.

  2. Provide the database user name and password of the owner of the Discoverer Release 4.1 EUL that you want to upgrade and click OK.

    The EUL Upgrade dialog appears.

  3. Select the Yes, I have completed a database export check box to confirm that you have exported the Discoverer Release 4.1 End User Layer.

  4. Click Upgrade to create a new Version 5 End User Layer using the data from the Release 4.1 End User Layer.

    The EUL Upgrade progress bar displays the status of the upgrade. During the upgrade process, messages are displayed in the End User Layer Upgrade Log dialog. For more information about messages that refer to invalid characters in identifiers, see Section 7.4.7, "Identifiers Containing Invalid Characters".

    If there are Summary folders in the upgraded End User Layer, a message dialog appears, stating that the summary folders are invalid and must be refreshed.

  5. If the above message dialog appears, click OK.

    �The Load Wizard appears.

  6. Click Cancel to close the Load Wizard.

    The End User Layer Upgrade is complete. You can now use this End User Layer to connect to the database using Discoverer Administrator 9.0.4.

7.3.2.3 Refreshing the Summary Folders

If there are summary folders in the EUL you have upgraded, you must refresh them.

The definitions of any Release 4.1 summary folders are copied into the new Version 5 EUL and the status of the upgraded summary folders is changed to Refresh Required. The database tables or materialized views on which the upgraded summary folders are based are not actually created until the summary folders are refreshed.

When you refresh upgraded summary folders, Discoverer changes the database as follows, depending on the version:

  • On Oracle Standard Edition databases, Discoverer creates summary tables

  • On Oracle 8.1.7 (or later) Enterprise Edition databases, Discoverer creates materialized views

When the summary tables or materialized views have been created, Discoverer can then use the summary folders to optimize queries.

Follow these steps to refresh the upgraded summary folders:

  1. Connect to Discoverer Administrator as the owner of the upgraded EUL.

  2. Open the business area containing the summary folders that you want to refresh.

  3. Go to the Summaries tab of the work area.

  4. Select the summary folders to refresh.


    Note:

    You will have to refresh all of the summary folders before Discoverer can use them. However, depending on the amount of data, you might not want to refresh all the summary folders at the same time.

  5. Select Tools->Refresh Summaries.

    For any summary folders not based on external summary tables, the Refresh Summaries dialog is displayed.

  6. Specify refresh options as required.


    Note:

    You can refresh summary folders immediately or specify a time for the refresh.� Depending on the amount of data, you might want to schedule the refresh for an off-peak time.

  7. Click OK to refresh the summary folders.


Note:

If an upgraded EUL contains summary folders based on external summary tables, you must also refresh those summary folders. During the refresh, Discoverer updates EUL metadata for summary folders based on external summary tables. If you are using an Oracle 8.1.7 database (or later), Discoverer creates a materialized view that references the external summary table.

7.3.2.4 Migrating Users to Discoverer Version 9.0.4

After the EULs are upgraded successfully, you can migrate Discoverer Plus and Discoverer Viewer users� to Discoverer Version 9.0.4.

While you are performing the migration across the organization, users can continue to work with Discoverer Release 4.1 (accessing the original EUL), or with Discoverer 10g (9.0.4) (accessing the upgraded EUL). However, any changes made using one version of Discoverer Administrator will not be available to users of the other version of Discoverer. The steps for migrating users depends on the Discoverer tools being used.

7.3.2.4.1 Migrating Discoverer Plus and Discoverer Viewer Users

To migrate Discoverer Plus and Discoverer Viewer users� to Discoverer Version 9.0.4, follow the instructions in:

7.3.2.4.2 Migrating Discoverer Desktop Users

To migrate Discoverer Desktop users:

Install Discoverer Desktop from the Discoverer Desktop CD (shipped with Oracle Developer Suite) to the client computers.

The Oracle Installer automatically installs Discoverer Desktop Version 9.0.4 in a separate directory from Discoverer Release 4.1.


Note:

When a user logs in to Discoverer for the first time, using Discoverer Plus, Discoverer Desktop, or Discoverer Viewer, Discoverer first searches for any Version 5 EULs to which the user has access.
  • If a valid EUL is found, then the user can connect and start work in Discoverer 10g (9.0.4).

  • If no valid EUL is found, Discoverer displays a message that the user cannot connect to the database. The user should contact the Discoverer administrator, because the likely cause is that an EUL has not been upgraded. The user can still use Discoverer Release 4.1 against an existing Release 4.1 EUL.


7.3.2.5 Removing the Release 4.1 EULs

When you have upgraded the Release 4.1 EULs and migrated all users to Discoverer 9.0.4, you can remove the Release 4.1 EULs.

Initially, you will probably want to prevent access to the original EULs and only allow users to access the upgraded EULs. When you are confident that all users are successfully accessing the upgraded EULs, you can remove the old EULs.

A SQL script, eul4del.sql, is shipped with Discoverer to enable you to ��remove Release 4.1 EULs and associated tables, including summary tables and materialized �views.


Note:

Consider the following before you use the eul4del.sql script:
  • When you run the eul4del.sql script, you are prompted for the password of the SYSTEM user. If you do not know the password of the SYSTEM user, contact your database administrator. Rather than give you the SYSTEM user's password, your database administrator might prefer to run the script for you.

  • The eul4del.sql script will not complete successfully if there are any summary folders owned by users other than the EUL owner. The script will list any such summary folders and their owners. The summary folder owners must delete their summary folders before you can remove the Release 4.1 EULs.

  • If you have access to Discoverer Administration Edition Release 4.1, you can delete End User Layers using the EUL Manager instead of using the eul4del.sql script.

  • If users have modified the Release 4.1 EUL since you upgraded it, their changes will not be in the Version 9.0.4 EUL. If you think significant changes might have been made, consider taking another backup of the Release 4.1 EUL before removing it (for more information, see Section 7.3.2.1, "Backing Up the Release 4.1 End User Layer".


Follow these steps to remove a Release 4.1 EUL with the eul4del.sql script:

  1. Start SQL*Plus. In Windows, the navigation path is:

    Start->ORACLE->Application Development ->SQL*Plus

    The SQL*Plus Log On dialog box appears.

  2. Enter the database user name, password and database for the owner of the Discoverer Release 4.1 EUL that you want to remove.

    The command prompt appears.

  3. Type the following:

    @<source_MT_OH>\discoverer\sql\eul4del.sql

    The deinstallation script removes a specified Release 4.1 EUL and any associated database objects, including summary tables and materialized views. A summary of the deinstallation script appears:

    Removing summary refresh jobs ...

    Discoverer End User Layer Database Tables (4.x Production)

    deinstallation

    This script will remove a version 4.x EUL and any associated database objects.

    It will:

    1. Ask you to enter the ORACLE SYSTEM password and connect string.

    2. Ask you to enter the name and password of the 4.x EUL owner.

    3. Confirm that you wish to drop the 4.x EUL.

    4. Check for database jobs for users other than the 4.x EUL owner.

    5. Confirm whether to drop 4.x tutorial tables (if any).

    6. Log in as the 4.x EUL owner and remove any database jobs for it.

    7. Remove all summary database objects for the 4.x EUL.

    8. Remove all scheduled workbook database objects for the 4.x EUL.

    9. Remove the 4.x EUL tables.

    10. Remove user and public synonyms (if any) for the 4.x EUL tables.

  4. Enter the password and database connect string for the SYSTEM� user. If you do not know the password of the SYSTEM user, contact your database administrator.

  5. Enter the name and password of the owner of the Release 4.1 EUL.

    The following text appears:

    Preparing to remove EUL 4.x owned by <username> at <today's date>

    If you continue, the specified 4.x End User Layer will be PERMANENTLY dropped. All End User Layer information and workbooks stored in the database will be deleted.

    Any 5.x End User Layer tables will NOT be affected by this process.

    THIS PROCESS IS NON-REVERSIBLE.

    Do you wish to continue [N]:

  6. Type Y to confirm that you want to drop the Release 4.1 End User Layer.

    If the script detects the Release 4.1 tutorial tables, you are prompted to confirm whether to delete the tables. During the process of dropping the Release 4.1 EUL, the script will check whether there are any summary folders owned by users other than the EUL owner. If there are no summary folders owned by other users, then the Release 4.1 EUL is dropped. Messages resembling the following appear:

    Removing summary refresh jobs ...

    Dropping internally managed summary data ...

    Removing scheduled workbook jobs ...

    Dropping scheduled workbook data ...�

    Dropping 4.x End User Layer Tables ...

    Removing public synonyms (if any) ...

    Connected.

    Finished removing 4.x End User Layer.

    If there are summary folders owned by users other than the EUL owner, the� script will halt and display messages similar to the following:

    The following users have managed summaries which must be dropped before this EUL can be deinstalled:

    User: SCOTT, Summary: <Scott's summary>

    User: FRED, Summary: <Fred's summary>

    Quitting - no changes made.

    If this message appears, the specified users must log into Discoverer� Administration Edition Release 4.1 and remove the specified summary folders (for more information, see Chapter 14 of the Oracle Discoverer Administrator Administration Guide in the Oracle Developer Suite documentation library). When these summary folders have been dropped, run the eul4del.sql script again to drop the Release 4.1 EUL.

7.3.2.6 Removing the Release 4.1 Products from Client Computers

When users have connected successfully to Discoverer Version 9.0.4 and you are confident that summary folders are working correctly, you can remove Discoverer Release 4.1 products (i.e. Discoverer Administration Edition, Discoverer� Desktop Edition) from client computers.

Follow these steps to remove Discoverer Release 4.1 products from client computers:

  1. Insert the CD-ROM from which you installed Discoverer Release 4.1 products into� your computer's CD-ROM drive.

    The Oracle Universal Installer starts automatically. If it does not start automatically, access the CD-ROM with Windows Explorer and run setup.exe from the CD root directory.

  2. Use the Oracle Universal Installer deinstall option to remove Discoverer Release 4.1 products.


    Note:

    Workbooks created in Discoverer Release 4.1 and saved in the <ORACLE_HOME>/discvr4 directory will not be deleted.

  3. (Optional) To retain workbooks from the <ORACLE_HOME>/discvr4 directory for future use:

    1. Move Discoverer Release 4.1 workbooks from the <ORACLE_HOME>/discvr4 directory to a new directory for use with Discoverer Version 9.0.4.

    2. Delete the <ORACLE_HOME>/discvr4 directory.

7.3.3 Updating URL References

All Discoverer Viewer and Discoverer Plus URL references have changed between Discoverer Release 4.1 and Discoverer Version 9.0.4. These changes include (but are not limited to) links within the Web site and client bookmarks. You must manually replace all occurrences of old URLs with the new URLs. Table 7-2 provides the syntax of the old and new URLs and an example of the required change.

Table 7-2 OracleAS Discoverer URL References

Oracle9iAS Release 1 (1.0.2.2.x) URL 10g (9.0.4) URL Example
http://<hostname>/Discwb4/html/english/ms_ie/start_ie.htm

or

http://<hostname>/Discwb4/html/english/netscape/start_nn.htm

http://<hostname>/discoverer/plus Change

http://<host>:<port>/Discwb4/english/...

to

http://<host>:<port>/discoverer/plus/...

http://hostname/Discoverer4i/Viewer http://hostname/discoverer/viewer Change

http://<host>:<port>/Discoverer4i/Viewer/...

to

http://<host>:<port>/discoverer/viewer/...


7.3.4 Configuring Session Time-out

The session timeout parameter controls the HTTP session timeout (i.e. the number of minutes the Discoverer servlet waits for a browser to make another HTTP or HTTPS request before terminating the user's HTTP session).

In Discoverer Release 4.1, the session timeout parameter is in the disco4iviewer.properties file in the following directory:

<source_MT_OH>/Apache/JServ/servlets

In Discoverer Version 9.0.4, the session timeout parameter is in the web.xml file in the following directory:

<destination_MT_OH>/j2ee/OC4J_BI_Forms/applications/discoverer/web/WEB-INF

To set the session timeout parameter, add it to the web.xml file immediately following the line that reads </servlet> and before the bottom of the <web-app> section of the file, as shown below:

<web-app>
    <servlet>
    ...�
    </servlet>
    <session-config>
       <session-timeout>15</session-timeout>
    </session-config>
</web-app>  

7.3.5 Upgrading Discoverer Viewer Customizations

A number of files control the appearance and behavior of OracleAS Discoverer Viewer. Those files might have been modified to customize Discoverer Viewer to meet certain customer-specific requirements. The installation of Oracle Application Server 10g (9.0.4) installs new files with different names. Specifically:

  • disco4iv.xml is renamed configuration.xml and viewer_config.xml is renamed ui_config.xml

  • The content of various *.xsl files is moved into new *.xsl files.

If the original configuration files and *.xsl files were modified, then you must edit the new 10g (9.0.4) files and reapply the changes from the Release 4.1 files. The configuration files do not correspond one-to-one by name in the old and new releases, so you will need to determine the file in which a modification should be placed. See Table 7-3 for file names.


Note:

Do not simply replace the new files with the Release 4.1 files (i.e. do not simply rename the new files). Follow the steps in this section to upgrade only the customizations, not all of the differences, from the original Release 4.1 files to the new files.

To upgrade Discoverer Viewer customizations:

  1. For each original Release 4.1 file in <source_MT_OH>/Apache/Apache/htdocs/disco4iv/html:

    1. Compare the original Release 4.1 file with the equivalent Version 9.0.4 file in the <destination_MT_OH>/J2EE/OC4J_BI_Forms/applications/discoverer/web/ subdirectories. Table 7-3 lists the Release 4.1 files and the equivalent 10g (9.0.4) files.

    2. Edit the equivalent 10g (9.0.4) file to incorporate any customizations found in the original Release 4.1 file.


Note:

If you modify the configuration.xml file, consider using Oracle Enterprise Manager Application Server Control to make the changes. The Oracle Enterprise Manager Application Server Control provides a user interface for editing settings in the configuration.xml file, and provides useful information about each setting.

Table 7-3 Equivalent Versions of Discoverer Files

Oracle9iAS Release 1 (1.0.2.2.x) Discoverer File Oracle Application Server 10g (9.0.4) Discoverer File
disco4iv.xml <destination_MT_OH>/j2ee/OC4J_BI_Forms/applications/discoverer/web/WEB-INF/configuration.xml
viewer_config.xml (UNIX) <destination_MT_OH>/j2ee/OC4J_BI_Forms/applications/discoverer/web/common/xsl/ui/ui_config.xml

(Windows) <destination_MT_OH>/j2ee/OC4J_BI_Forms/applications/discoverer/web/common/xsl/ui_config.xml

errors.xsl

functions.xsl

gui_components.xsl

page_layouts.xsl

render_table.xsl

scripts.xsl

style.xsl

Various new XSL files in the following directories:
  • <destination_MT_OH>/j2ee/OC4J_BI_Forms/applications/discoverer/web/common/xsl

  • <destination_MT_OH>/j2ee/OC4J_BI_Forms/applications/discoverer/web/viewer_files/xsl


7.4 Notes About Upgrading to OracleAS Discoverer

This section identifies characteristics of the upgraded OracleAS Discoverer component in Oracle Application Server 10g (9.0.4) of which you should be aware.

7.4.1 Oracle Applications EULs

When upgrading an Oracle Applications EUL, be aware that the MAXEXTENTS storage property of the EUL tables might have been increased to a value greater than the MAXEXTENTS storage property of the tablespace in which the EUL was created. If this situation exists, any attempt to upgrade the EUL will fail with an ORA01631 error, because:

  • The upgrade process uses the original EUL tablespace's MAXEXTENTS value when creating the new EUL tables

  • The new EUL tables are therefore not large enough to contain the data from the original EUL tables

If the MAXEXTENTS value of the EUL tables is greater than the MAXEXTENTS value of the EUL's tablespace, ask your database administrator to increase the MAXEXTENTS value of the original EUL's tablespace before attempting to upgrade the EUL. The new EUL tablespace and the new EUL tables will be created with the larger MAXEXTENTS value.

7.4.2 EULs Containing Analytic Functions

When you upgrade a Discoverer Release 4.1 EUL to a Discoverer Version 5 EUL, new Oracle9i analytic functions are added to EUL tables.

Where existing user-defined functions have the same name (or the same unique identifier) as the new functions, Discoverer does the following:

  • Renames the existing user-defined function

  • Displays a log message at the end of the upgrade process

  • Provides the option to save the messages to a log file


Note:

Discoverer's internal reference system ensures that end users can still open workbooks that contain renamed user-defined functions.

7.4.3 The Video Stores Tutorial

The Video Stores tutorials are specific to particular Discoverer releases.

When you upgrade to a new version of Discoverer, Oracle Corporation recommends that you re-install the Video Stores tutorial using the appropriate version of Discoverer Administrator instead of upgrading the tutorial.

7.4.4 Scheduled Workbooks

When you upgrade a Release 4.1 EUL to a Version 5 EUL, scheduled workbooks are automatically upgraded. However, scheduled workbook results are not copied to the Version 5 EUL. The results for an upgraded scheduled workbook will only be available after the scheduled workbook has next run.

7.4.5 Workbooks Saved in .dis Files

If Discoverer Desktop users save workbooks to the filesystem in .dis files, the .dis files must be upgraded before they can be used with the latest version of Discoverer.

To upgrade the .dis files, open the .dis files in the latest version of Discoverer and save the files back to the filesystem, or to the database (to open them in Discoverer Plus and Discoverer Viewer). Note that after a .dis file has been upgraded, it is not backward-compatible with earlier versions of Discoverer Desktop.

7.4.6 Discoverer systems that use the EUL Gateway

A Discoverer system might use the EUL Gateway to populate EULs with metadata from a source other than the database's on-line dictionary (e.g. from Oracle Designer).

If you upgrade such a system, you will have to re-install and re-configure the EUL Gateway after the upgrade process is complete. For more information about installing and configuring the EUL Gateway, see the eulgatew.doc document located in the <destination_MT_OH>\discoverer\kits directory.

7.4.7 Identifiers Containing Invalid Characters

In a future release of Discoverer, there will be a change to the valid characters that can be used in identifiers and some characters will be de-supported.

If you upgrade an EUL that has identifiers containing invalid characters, messages will be displayed indicating the affected identifiers. Modify any identifiers that use the invalid characters so that the identifiers can be used in future releases of Discoverer.

7.5 Validating the OracleAS Discoverer Upgrade

Follow the steps below to verify that OracleAS Discoverer is functioning correctly after the upgrade:

  1. Connect to the URLs in OracleAS Discoverer 10g (9.0.4) and enter TNS information. Verify that this works in Discoverer Plus and Discoverer Viewer.

  2. Ensure that any configuration changes or customizations that were made to Discoverer Plus and Discoverer Viewer in Release 1 (1.0.2.2.x) are present in the new URL connections.