4 Oracle Database Companion CD Postinstallation Tasks

4.1.5.1 Copying and Editing the httpd.conf File

Copy the httpd.conf file used by the previous release to the current release configuration file directory.

Follow these steps:

1. Change directory to the configuration file directory for the current release of Oracle HTTP Server:

   cd ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf
   
   

2. Back up the httpd.conf file:

   copy httpd.conf httpd.conf.orig
   
   

3. Back up the configuration file directory for the current release of Oracle HTTP Server:

   copy ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf ORACLE_BASE\ORACLE_HOME
   
   

4. Change directory to the configuration file directory:

   cd ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf
   
   

5. Copy the httpd.conf file used by the previous release to the current directory, for example:

   copy \OLD_ORACLE_HOME\Apache\Apache\conf\httpd.conf
   
   

6. Open the httpd.conf file in any text editor.

4.1.5.2 Making Global Changes

To make the following global changes to the httpd.conf file, follow these steps:

1. Search for all occurrences of the old Oracle home directory path and replace them with the current Oracle home directory path.

2. Change all occurrences of mod_ssl.c to mod_ossl.c.

   
   

   Note: Oracle recommends that you change the SSL related directives in the httpd.conf file, even if SSL is not used.

4.1.5.3 Modifying the List of LoadModule Directives

To modify the list of LoadModule directives, follow these steps:

1. Remove the following directives:

   LoadModule oprocmgr_module    libexec\liboprocmgr.so
   LoadModule rewrite_module     libexec\mod_rewrite.so
   
   

   
   

   Note: You must add a LoadModule directive for the mod_rewrite module later in the file.

2. Add the following directive, which loads the onsint module, immediately before the <IfDefine SSL> section:

   LoadModule onsint_module      libexec\mod_onsint.so
   
   

3. In the LoadModule directive in the <IfDefine SSL> section, change ssl_module to ossl_module and change mod_ssl.so to mod_ossl.so, as follows:

   LoadModule ossl_module      libexec\mod_ossl.so
   
   

4.1.5.4 Removing Directives and Sections for Unsupported Features

To remove all directives and sections for unsupported features, follow these steps:

1. Remove the following directives from the <IfModule mod_alias.c> section:

   Alias /jservdocs/ "\ORACLE_BASE\ORACLE_HOME\Apache\Jserv\docs\"
   Alias /soapdocs/ "\ORACLE_BASE\ORACLE_HOME\soap\"
   
   

2. Remove the following directive from the <IfModule mod_fastcgi> section:

   FastCGIServer fcgi-bin/echo -initial-env ORACLE_HOME \
                                -initial-env NLS_LANG
   
   

3. Remove the following include directive:

   include "/ORACLE_BASE/ORACLE_HOME/Apache/Jserv/etc/jserv.conf"
   
   

4. Remove the <IfModule mod_oprocmgr.c> section.

4.1.5.5 Modifying Port Numbers

The httpd.conf file is used by previous releases of Oracle HTTP Server that were installed with Oracle HTTP Server or Oracle Database. This file specifies different ports for non-SSL (HTTP) requests depending on whether you started an SSL-enabled server. These ports are shown as port1 and port2 in the following example:

Port port1
Listen port1

<IfModule mod_ossl.c>
  Port port2
  Listen port2
  Listen SSL_port
</IfModule>

Oracle recommends that you change these directives as follows:

1. If you did not use SSL, remove the following directives:

   Port port2
   Listen port2
   
   

   Oracle HTTP Server listens for HTTP requests on port port1.

2. If you used only the ports defined for SSL, change the directives as shown in the following example:

   Port port2
   Listen port2
   
   <IfModule mod_ossl.c>
     Listen SSL_port
   </IfModule>
   
   

   Oracle HTTP Server listens for HTTP requests on port port2 and for HTTPS requests on port SSL_port.

3. If you intend to continue to use the previous version of Oracle HTTP Server concurrently with this release, change the ports specified by the Port and Listen directives to unused ports.

4. If you changed SSL_port in the previous step, complete the following steps:

   1. Locate the <VirtualHost _default_:SSL_port directive and ensure that the value of SSL_port matches the value specified by the Listen directive in the <IfModule mod_ossl.c section.

   2. In the <VirtualHost _default_:SSL_port section, ensure that the port number specified by the Port directive is the same as SSL_port.

4.1.5.6 Modifying Existing Sections and Directives

To modify the following sections and directives in httpd.conf, follow these steps:

1. In the default directory section, <Directory />, add the MultiViews option to the Options directive. For example:

   <Directory />
       Options FollowSymLinks MultiViews
       AllowOverride None
   </Directory>
   
   

2. In the <IfModule mod_alias.c> section, create a new <IfModule mod_perl.c> section and move the Alias directive that defines the /perl/ alias into this section. For example:

   <IfModule mod_alias.c>
   ...
       <IfModule mod_perl.c>
           Alias /perl/ "\ORACLE_BASE\ORACLE_HOME\Apache\Apache\cgi-bin\"
       </IfModule>
   ...
   </IfModule>
   
   

3. Modify the <IfModule mod_dms.c> section as shown in the following example, substituting the appropriate values for the hostname and domain variables:

   <IfModule mod_dms.c>
     <Location /dms0>
       SetHandler dms-handler
       Order deny,allow
       Deny from all
       Allow from localhost hostname.domain hostname
     </Location>
   </IfModule>
   
   

4. In the directive that sets the PERL5LIB environment variable, edit the Perl directory location and version, as shown in the following example:

   SetEnv PERL5LIB "\ORACLE_BASE\ORACLE_HOME\perl\5.6.1\lib:\ORACLE_BASE\ORACLE_HOME\perl\site\5.6.1\lib"
   
   

   Enter this setting on one line.

4.1.5.7 Adding New Sections and Directives

To add the following new sections and directives to the http.conf file, follow these steps:

1. Add the following section to protect the WEB-INF directories:

   #Protect WEB-INF directory
   
   <DirectoryMatch /WEB-INF/>
    Order deny,allow
    Deny from all
   </DirectoryMatch>
   
   

2. Add the following lines before the line that includes the oracle_apache.conf file:

   # Include the configuration files needed for mod_oc4j
   include "\ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\mod_oc4j.conf"
   
   # Loading mod_rewrite module here as it loads before mod_oc4j
   LoadModule rewrite_module     modules/ApacheModuleRewrite.dll
   

4.1.5.8 Migrating Your Server Certificate and Private Key

If you use SSL and have an existing server certificate and private key, you must migrate them to the format required by mod_ossl before using them with this release of Oracle HTTP Server.

To migrate an existing server certificate and private key, follow these steps:

1. Enter a command using the following syntax in a separate terminal window:

   \ORACLE_BASE\ORACLE_HOME\Apache\Apache\bin\ssl2ossl -cert cert_file \
                                                       -key key_file \
                                                    {[ -chain chain_file] |
                                                     [ -cafile CA_file] |
                                                     [ -capath CA_path] }\
                                                       -wallet wallet_path \
                                                     [ -certpass key_file_pwd] 
                                                     [ -wltpass wallet_pwd] \
                                                     [ -ssowallet yes] \
                                                     [ -validate yes]
   
   

   The following table lists the recommended value for each option available with the ssl2ossl command:

   
   

   Note: You must specify at least one of the following options: -chain, -cafile, or -capath.

   Option	Recommended Value
   -cert	Use the value specified by the SSLCertificateFile directive in the httpd.conf file for the previous release.
   -key	Use the value specified by the SSLCertificateKeyFile directive in the httpd.conf file for the previous release.
   -chain	Use the value specified by the SSLCertificateChainFile directive in the httpd.conf file for the previous release, if that directive is not preceded by the comment character (#). Note: If the SSLCertificateChainFile directive is not specified or is preceded by a comment character, do not specify the -chain option.
   -cafile	Use the value specified by the SSLCACertificateFile directive in the httpd.conf file for the previous release. Note: If the SSLCACertificateFile directive is not specified or is preceded by a comment character, do not specify the -cafile option.
   -capath	Use the value specified by the SSLCACertificatePath directive in the httpd.conf file for the previous release. Note: If the SSLCACertificatePath directive is not specified or is preceded by a comment character, do not specify the -capath option.
   -wallet	Specify the path to the directory in which you want to create the wallet. The default value is: \ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\ssl.wlt\default
   -certpass	Specify the password for your private key file, if it is encrypted.
   -wltpass	Specify a password for your new wallet. If you do not specify this option, the ssl2ossl utility prompts you to enter and verify the wallet password.
   -ssowallet	Specify the value yes to create a wallet that is compatible with Oracle Single Sign-On.
   -validate	Specify the value yes to verify that the wallet will be converted successfully. If you specify this option with the value yes, the wallet is not created.

2. Optionally, enter a command similar to the following to generate an encrypted version of the wallet password you specified in the ssl2ossl command:

   ORACLE_BASE\ORACLE_HOME\Apache\Apache\bin\iasobf -p wallet_pwd
   
   

   
   

   Note: If you specify the -ssowallet option in the ssl2ossl command, you do not need to complete this step. Otherwise, because the password must be specified in the httpd.conf file, Oracle recommends that you encrypt it.

   The output from this command is the encrypted version of the password specified by the -p option. In the following section, you must specify this value for the SSLWalletPassword directive.

4.1.5.9 Modifying the SSL Sections and Directives

Make the following changes to the directives contained in the <IfModule mod_ossl.c> sections:

1. Change the setting for the SSLSessionCache directive as follows:

   SSLSessionCache shmcb:/ORACLE_BASE/ORACLE_HOME/Apache/Apache/logs/ssl_scache(512000)
   
   

2. Change the setting for the SSLCipherSuite directive as follows:

   SSLCipherSuite SSL_RSA_WITH_RC4_128_MD5:SSL_RSA_WITH_RC4_128_SHA:
   SSL_RSA_WITH_3DES_EDE_CBC_SHA:SSL_RSA_WITH_DES_CBC_SHA:
   SSL_RSA_EXPORT_WITH_RC4_40_MD5:SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
   
   

3. Remove the following directives and their associated comments:

   SSLRandomSeed
   SSLCertificateFile
   SSLCertificateKeyFile
   SSLCertificateChainFile
   SSLCACertificateFile
   SSLCACertificatePath
   SSLVerifyDepth
   
   

4. In the <VirtualHost _default_:SSL_port section, add the following lines:

   #   Server Wallet:
   #   The server wallet contains the server's certificate, private key
   #   and trusted certificates. Set SSLWallet at the wallet directory
   #   using the syntax:  file:<path-to-wallet-directory>
   SSLWallet file:\ORACLE_BASE\ORACLE_HOME\Apache\Apache\conf\ssl.wlt\default
   
   #   Server Wallet Password:
   #   Both clear text wallet password and obfuscated password are allowed
   #   here. An obfuscated one is recommended.
   #   Examples:
   #   SSLWalletPassword <clear_pass>
   #   SSLWalletPassword <obfuscated_pass>
   #SSLWalletPassword ...
   
   

5. If you migrated a server certificate and private key, complete the following steps:

   1. Change the value specified by the SSLWallet directive to specify the wallet path, if it is different from the default value.

   2. If you did not create a wallet that is compatible with Oracle Single Sign-On (using the -ssowallet yes option in the previous section), remove the comment from the SSLWalletPassword directive and specify the clear-text or encrypted wallet password as its value.

4.1.5.10 Copying Required Files to New Directories

Copy (or move) any scripts for files from the document root and script directories to the equivalent directories for the new release. Copy the following files, as appropriate:

• Files and subdirectories in directories specified by a DocumentRoot or Alias directive

• CGI, Perl, and FastCGI programs and scripts and their associated files in directories specified by a ScriptAlias directive

4.2.3.1 Copying the Oracle Database 10g images Directory to an Oracle9i images Directory

From the Oracle Database 10g installation, recursively copy the images directory located in ORACLE_BASE\ORACLE_HOME\marvel\images to a new images directory in your Oracle9i installation. In the following example, the Oracle9i home is referred to as ORACLE_BASE\ORACLE_HOME_9 and the Oracle Database 10g home is ORACLE_BASE\ORACLE_HOME_10g. For example:

c:\>xcopy /E /I ORACLE_BASE\ORACLE_HOME_10g\marvel\images ORACLE_BASE\ORACLE_HOME_9\images

Enter this command on one line.

4.2.3.2 Modifying the Oracle9i httpd.conf File

Next, modify the Oracle9i httpd.conf file to point to the Oracle9i file system path of the images directory that you created in the previous step.

Follow these steps:

1. Use a text editor to open the httpd.conf file, located in ORACLE_BASE\ORACLE_HOME_9\Apache\Apache\conf.

2. Add an alias called /i/ to point to the file system path of the Oracle9i images directory. For example:

   Alias /i/ "E:\oracle\ora92\images/"
   
   

3. Save and exit httpd.conf.

4.2.3.3 Modifying the Oracle9i websvr.app File

The wdbsvr.app file contains information about Database Access Descriptors (DADs). A DAD is a set of values that specify how Oracle HTTP Server connects to the database server to fulfill an HTTP request. You need to create a DAD to specify how to connect to the Oracle HTML DB instance.

Follow these steps:

1. Use a text editor to open the wdbsvr.app file, located in ORACLE_BASE\ORACLE_HOME_9\Apache\modplsql\cfg.

2. Add an entry for Oracle HTML DB using the following syntax. Only change the settings indicated in italics below.

   [DAD_htmldb]
   connect_string = hostID:port_number:databaseSID 
   password = password
   username = htmldb_public_user
   default_page = htmldb
   document_table = wwv_flow_file_objects$
   document_path = docs
   document_proc = wwv_flow_file_mgr.process_download
   reuse = No
   enablesso = No
   stateful = STATELESS_RESET
   nls_lang = database_nls_lang
   
   

   where:

   • connect_string refers to the host ID, port number, and Oracle9i database to which Oracle HTML DB will connect. For example:

     138.2.84.182:1521:orcl
     
     

     If the Oracle9i version of Oracle HTTP Server you want to use is installed in the same Oracle home as the database you specified for use with Oracle HTML DB, you can leave this setting blank.

   • password is the same password that you entered when you installed Oracle HTML DB.

   • nls_lang refers to the language setting. It must match the NLS_LANG of the database. For example:

     American_America.AL32UTF8
     
     

     You can find information about your database's NLS_LANG setting by querying the view NSL_DATABASE_PARAMETERS.

   Oracle recommends that you leave the remaining settings, including the username setting, as they are.

3. Save and exit wdbsvr.app.

4.2.3.4 Stopping and Restarting Oracle HTTP Server

In order for your changes to httpdb.conf and wdbsvr.app to take effect, stop and restart Oracle HTTP Server. See "Starting, Stopping, or Restarting Oracle HTTP Server" for more information.

4.2.3.5 Removing the Oracle HTTP Server 10g Home

After you complete these steps, you no longer need the Oracle HTTP Server 10g home. All the Oracle HTML DB code is now compiled as PL/SQL inside the database server that you specified at installation time, and you have copied the Oracle Database 10g images directory to your Oracle9i home.

If you are not going to use Oracle HTTP Server 10g, follow these steps:

1. From the Oracle Database 10g home, run the Oracle Universal Installer.

2. Select Deinstall Products and follow the instructions to remove the Oracle HTTP Server 10g home.