|
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 Oracle HTTP Server.
Oracle9iAS, Release 2 (9.0.2.0.1) for Windows does not support SSO wallet. You should use the SSLWalletPassword directive in httpd.conf instead.
Although SSO wallet is not supported, if you choose to use it, you have to change the owner of Oracle Process Manager service. Use the account that you enabled the SSO wallet with, instead of the default SYSTEM owner.
This section describes configuration issues and their workarounds for Oracle HTTP Server.
Use a Full or Partial Host Name in Oc4jMount Syntax in mod_oc4j.conf File
Configuring a Virtual Host Improperly Can Cause DADs to Break
Oracle HTTP Server (1.0.2.2.x) Cannot Be Used with Oracle9iAS (9.0.2.x)
While using the following Oc4jMount syntax in mod_oc4j.conf file:
Oc4jMount /path/* instance://[hostname]:<ias_instance>:<oc4j_instance>
Be aware that the host name is optional. It is only necessary to specify it when there are some standalone Oracle9iAS instances installed on different hosts that have identical Oracle9iAS instance names, which is rare.
When host name is specified, be sure to test with both a partially qualified host name as well as a fully qualified host name to see which one works. The host name that works matches the host name stored in the OC4J registration event.
After installation, if you wish to configure virtual hosts in the httpd.conf file, or by using the 'advanced' section of the EMD console, or by using a text editor on the httpd.conf file, use the following guidelines:
Ensure that the server definitions for VirtualHosts are provided after the Port, Listen and ServerName directives. A simple example of a correctly set virtual host section might be as follows:
#
# these are set at the end of the httpd.conf file after the IAS installation
occurs
#
Port 7778
ServerName someServer.mycompany.com
Listen 7779
#
# these lines were added manually to create a virtualHost
#
NameVirtualHost 1.2.3.4
<VirtualHost 1.2.3.4>
DocumentRoot /u01/app/oracle/product/iAS9020_portal/Vhost1.htdocs
ServerName Vhost1.mycompany.com
</VirtualHost>
Ensure that if you use a regular text editor to make changes to the file, you use the following dcmctl utility to update your changes.
<ORACLE_HOME>/dcm/bin/dcmctl updateConfig
This is automatically done for you if you edit the file through the EMD console.
Oracle Corporation does not support using the Oracle HTTP Server component that is supplied with Oracle9iAS Release 1 (1.0.2.2.x) as a front end to the Containers for J2EE (OC4J) component supplied with Oracle9iAS Release 2 (9.0.2.x), that is, you must not use the mod_Proxy module to route data between these two components.
Always use the mod_oc4j module to route data to and from the OC4J component supplied with Oracle9iAS Release 2 (9.0.2.x). Use the mod_proxy module to route data between the HTTP Server component supplied with Oracle9iAS Release 1 (1.0.2.2.x) and the OC4J component supplied with Oracle9iAS Release 1 (1.0.2.2.x).
This section describes administration issues and their workarounds for Oracle HTTP Server.
In Oracle9iAS, Release 2 (9.0.2.0.1), when you add a ssl-enabled virtual host to Oracle HTTP Server, you must stop and then start Oracle HTTP Server for this virtual host to function. Simply restarting Oracle HTTP Server will not enable the virtual host and may cause Oracle HTTP Server to crash, depending on your configuration. Virtual hosts that specify a wallet file but no wallet password will cause Oracle HTTP Server to crash on restart.
This section describes documentation issues and their workarounds for Oracle HTTP Server.
Incorrect Information in the "Configuring the IIS Listener for Single Sign-On" Section
Incorrect Information in Release Notes for iASOBF and SSO Wallet Support
Step 6 in the "Configuring the IIS Listener for Single Sign-On" section of the "Using Oracle9iAS Proxy Plug-in" appendix of the Oracle HTTP Server Administration Guide incorrectly states the following:
Restart IIS (stop and then start the IIS Server), ensuring that the oproxy filter is marked with a green up-pointing arrow.
It should say:
Restart IIS (stop and then start the IIS Server), ensuring that the osso filter is marked with a green up-pointing arrow.
In the "Using Single Sign-On with the Plug-in" section of appendix A of the Oracle HTTP Server Administration Guide, the "OSSO Configuration File Examples" incorrectly presents the syntax for the LoginServerFile directive with double quotes around the value.
The correct syntax is:
LoginServerFile = /path/config/sso_conf
Oracle HTTP Server Release Notes state the following:
IASOBF and SSO Wallet Support is User-dependent
To run the Oracle HTTP Server with SSL server correctly after installation, you should create a wallet and have the certificates contained within it signed by the proper Certificate Authorities. Make sure that the SSLWallet directive in httpd.conf points to this new wallet rather than the default wallet provided by the installation. Oracle HTTP Server will not start if you fail to do one of the following:
Obfuscate this new wallet's password by running:
osslpassword -p password LocalSystem
and place this obfuscated password in httpd.conf file using the Wallet Password directive (for example "WalletPassword obfuscatedPassword"). You can always choose to put the wallet password in httpd.conf in clear text but this is not recommended by Oracle.
Make this new wallet an SSO wallet as the root user.
|
See Also: Oracle9i Application Server Security Guide |
In the above issue, the command to obfuscate the new wallet's password should be changed to the following:
osslpassword -p password System
The Oracle9i Application Server mod_plsql User's Guide contains the following documentation errata:
In Section 2.6.8, "Direct BLOB Download", Step 2, the example:
procedure download_blob(varchar2 name) is
should be:
create or replace procedure download_blob(name in varchar2) is
In Section 2.6.8, "Direct BLOB Download", Step 2b, the example:
htp.p('Content-Length: ' || dbms_lob.get_length(myblob))
should be:
htp.p('Content-Length: ' || dbms_lob.getlength(myblob));
