|
Oracle9i Application Server Release Notes Addendum
Release 2 (9.0.2.0.1) for Microsoft Windows Part No. A90336-10 |
|
|
|
|
Oracle9i Application Server Release Notes Addendum
Release 2 (9.0.2.0.1) for Microsoft Windows Part No. A90336-10 |
|
|
|
|
This chapter discusses the following topics:
This section describes general issues and their workarounds for Oracle9iAS Discoverer.
The Oracle9iAS Discoverer Configuration Guide describes how to use Oracle Enterprise Manager (OEM) to specify the communication protocol that the Discoverer Plus applet and the Discoverer servlet use to communicate. The protocol you specify in OEM is saved in the plus_config.xml file.
However, in this release you cannot use OEM to specify the communication protocol. Instead, you must use a text editor (or an XML editor) to modify the plus_config.xml file directly, as follows:
Open plus_config.xml in a text editor.
The file is located in:
<ORACLE_HOME>\j2ee\OC4J_BI_Forms\applications\discoverer\web\plus_files\xsl
Locate the following line in the file:
<transport name = "protocol_option"/>
where "protocol_option" is one of the following:
"jrmp" (the default)
"http"
"https"
Note: Do not change the line <transport name = "codebase"/>
Change the value of "protocol_option" as required.
Save the changes you have made and close the file.
Use OEM to stop and restart the OC4J_BI_FORMS system component.
Notes
The above protocol options are referred to in the Oracle9iAS Discoverer Configuration Guide as follows:
jrmp is referred to as the 'Default' option
http is referred to as the 'Tunneling' option
https is referred to as the 'Secure Tunneling' option
The Oracle9iAS Discoverer Configuration Guide includes detailed descriptions of the different protocol options. For convenience, the following is a summary of the options:
If transport is set to "jrmp", Discoverer will first attempt to make a direct connection using RMI. A direct connection will only work within a firewall. If a direct connection cannot be established, Discoverer will automatically attempt to use HTTP or HTTPS.
If transport is set to "http", Discoverer will use the same protocol to communicate with the Discoverer servlet as was originally used to download the applet itself (i.e. either HTTP or HTTPS depending on the URL). This method supports access via firewalls.
If transport is set to "https", Discoverer will always use HTTPS tunneling. This method only supports secure access via firewalls.
The Oracle9iAS Migration Guide explains how to migrate Discoverer preferences from Discoverer 4i (installed as a component of Oracle9iAS 1.0.2.x) to Oracle9iAS Discoverer 9.0.2 when the two versions of Oracle9iAS are installed on the same machine. The additional information below explains how to migrate Discoverer preferences when the two versions of Oracle9iAS are installed on different machines:
On the machine where Oracle9iAS 1.0.2.x is installed:
Run the Windows Regedit program.
In Regedit, select the following registry key:
HKEY_LOCAL_MACHINE\Software\Oracle\WebDisco 4
Select Registry | Export Registry File to export the registry key to a file.
Specify a name for the registry export file (e.g. disco41prefs.reg).
Copy the registry export file from the machine where Oracle9iAS 1.0.2.x is installed to the machine where Oracle9iAS 9.0.2 is installed.
On the machine where Oracle9iAS 9.0.2 is installed:
Run the Windows Regedit program.
In Regedit, select Registry | Import Registry File.
Specify the name of the registry export file to import (e.g. disco41prefs.reg).
Migrate the preferences by issuing the following command:
<ORACLE_HOME>\Discoverer902\util\migrateprefs.bat
When you install Oracle9iAS, the Discoverer Windows service is created and called Oracle<ORACLE_HOME>Discoverer (e.g. if the name of the ORACLE_HOME directory is OraHome1, the name of the Discoverer Windows service is OracleOraHome1Discoverer).
During Oracle9iAS installation, you are given the option to configure and automatically start the Oracle9iAS components:
If you choose to configure and automatically start Discoverer at install time, the Discoverer Windows service is started and its Startup property is set to Automatic (i.e. the service will start automatically whenever the machine is started).
If you choose not to configure and automatically start Discoverer at install time, the Discoverer Windows service is not started. Before you can use Discoverer, follow the instructions below:
Configure Discoverer through Enterprise Manager (for more information, refer to Chapter 2 'Using Discoverer with Oracle Enterprise Manager' of the Oracle9iAS Discoverer Configuration Guide).
Use the Windows Control Panel to start the Discoverer service (for more information, refer to Section 4.2 'Starting and stopping the Discoverer Windows service' of the Oracle9iAS Discoverer Configuration Guide).
Hint: If you always want the Discoverer service to start automatically, set the service's Startup property to Automatic.
Use the Windows Control Panel to stop and start the Oracle<ORACLE_HOME>ProcessManager Windows service.
When installing Oracle9iAS Discoverer into multiple Oracle Homes on the same machine, you might see the following error:
O/S Error in starting service Oracle<ORACLE_HOME>Discoverer
This error is due to a conflict in the port number allocation for the OSAGENT component. The workaround is as follows:
Ignore the error message and continue with the installation.
The Discoverer service will not be started at the end of the install. The Discoverer Configuration Assistant will also fail.
Edit the Windows Registry as follows:
Run the Windows Regedit program.
Locate the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Home<n>\DC902_OSAGENT_PORT registry variable, where n is the instance number of the second Oracle Home.
Change the value of the DC902_OSAGENT_PORT registry variable to a value different to its current value but still within the range 16001 to 16020.
For example, if the value of DC902_OSAGENT_PORT under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Home0 (i.e. the first Oracle Home) is 16001, you might change the value of DC902_OSAGENT_PORT under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\Home1 (i.e. the second Oracle Home) to 16002.
Note: The value you specify for DC902_OSAGENT_PORT must be between 16001 to 16020.
Unregister the session of the second Discoverer install as follows:
At the command prompt, change directory to the <ORACLE_HOME>\discoverer902\util directory in the second Oracle Home.
At the command prompt, type the following:
unregistersession.bat -nopause
In the second Oracle Home, change the value of DC902_OSAGENT_PORT in the following files to the new value you specified for the registry variable:
OC4J_BI_FORMS.properties
oc4j.properties
registersession.bat
unregistersession.bat
Register the session of the second Discoverer install as follows:
At the command prompt, change directory to the <ORACLE_HOME>\discoverer902\util directory in the second Oracle Home.
At the command prompt, type the following:
registersession.bat -nopause
Connect to Oracle Enterprise Manager and choose to configure Oracle9iAS Discoverer.
Migration of scheduled workbooks from Discoverer 4.1.x to 9.0.2 happens automatically when you upgrade the End User Layer (EUL). There is no need to use the dis4sch.exe executable that was provided with Discoverer 4.1.x
Below is an overview of the migration process:
Using Discoverer Administrator, you upgrade your EUL from 4.1.x to 9.0.2. The metadata for scheduled workbooks is automatically migrated.
Note the following:
The scheduled workbook result sets will not be migrated. In other words, the details of the workbooks to be scheduled will be migrated, but the actual results will not be populated in the upgraded EUL. The results will only be available after the scheduled workbooks are next run.
Only scheduled workbooks that repeat will be migrated.
When the owner of a scheduled workbook next opens the Scheduled Workbook dialog in Discoverer Plus or Discoverer Desktop, a new scheduled job will be created.
After the previous step and after the next run of the scheduled workbook (depending on the time of execution specified in the Scheduled Workbook dialog), the scheduled workbook will be visible.
When you use Oracle Enterprise Manager to create Discoverer public connections, you specify connection details on the 'General Discoverer' configuration page.
Note that the field in which you enter the EUL name is case sensitive. In other words, the EUL name you specify must match the case of the name given to the EUL when it was created. Typically, EUL names are all uppercase, so you will usually use uppercase characters to specify the EUL name when creating a new public connection.
This section describes known errors in the documentation.
The location of the plus_config.xml file as documented in the Oracle9iAS Discoverer Configuration Guide should be:
<ORACLE_HOME>\j2ee\OC4J_BI_Forms\applications\discoverer\web\plus_files\xsl
The name of the Discoverer Windows service as documented in the Oracle9iAS Discoverer Configuration Guide should be:
Oracle<ORACLE_HOME_Name>Discoverer
For example, if the name of the ORACLE_HOME directory is OraHome1, the name of the Discoverer Windows service is OracleOraHome1Discoverer.
The Oracle9iAS Discoverer Configuration Guide incorrectly gives the name of the Discoverer Windows service as either Oracle<ORACLE_HOME_Name>Discoverer902 or as Disco9.0.2Service.
Please remove Excel2000 from the list of valid values for the ExcelVersion user preference given in section 7.7 of the Oracle9iAS Discoverer Configuration Guide.
Section 2.5 (step 3) and section 13.5.2 (step 4) of the Oracle9iAS Discoverer Configuration Guide instruct you to select the OC4J_BI_Forms link in Oracle Enterprise Manager (OEM) to display the Discoverer Services Configuration page.
However, the OC4J_BI_Forms link is not the correct link to use to display the Discoverer Services Configuration page. Instead, select the System Component name for Discoverer (e.g. myserver.hostname_Discoverer).
