5 Post-installation Tasks

5.1.1 Back Up the root.sh Script

Oracle recommends that you back up the root.sh script after you complete an installation. If you install other products in the same Oracle home directory, then the Oracle Universal Installer updates the contents of the existing root.sh script during the installation. If you require information contained in the original root.sh script, then you can recover it from the backed up root.sh file.

5.1.2 Download and Install Patches

Check the OracleMetalink Web site for required patches for this product. To download required patches:

1. Use a Web browser to view the OracleMetalink Web site:

   http://metalink.oracle.com
   
   

2. Log in to OracleMetalink.

   
   

   Note: If you are not an OracleMetalink registered user, click Register for MetaLink! and follow the registration instructions.

   
   

3. On the main OracleMetalink page, click Patches.

4. Use the Search feature to search for patches, specifying Oracle HTTP Server(OHS) and mods in the Product or Family field.

5. If patches are available, click the number of the patch that you want to download.

6. On the Patch Set page, click View README, then read the page that appears.

   The README page contains information about the patch set and how to apply the patches to the installation.

7. Return to the Patch Set page, click Download, and save the file on the system.

8. Use an unzip utility to uncompress the Oracle patches that you downloaded from OracleMetalink.

5.1.3 Migrating From a Previous Release of Oracle HTTP Server

If you are using Oracle HTTP Server installed with a previous release of Oracle Server on this system, you can migrate the configuration of that HTTP server to the current release.

There are two parts to the migration, as described in the following sections:

• Migrate the httpd.conf File

• Migrate Database Access Descriptors Used by mod_plsql

5.1.4 Migrate the httpd.conf File

To migrate the configuration of an earlier release of Oracle HTTP Server to the current release, you must copy and modify the httpd.conf file used by that release. The following sections describe how to complete this task.

Copy and Edit the httpd.conf File

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

1. Switch user to the Oracle software owner user (typically oracle):

   $ su - oracle
   
   

2. Set the ORACLE_HOME environment variable to specify the path to the Oracle home directory for the current release:

   • Bourne, Bash, or Korn shell:

     $ ORACLE_HOME=new_oracle_home_path ; export ORACLE_HOME
     
     

   • C or tcsh shell:

     % setenv ORACLE_HOME new_oracle_home_path 
     
     

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

   $ cp $ORACLE_HOME/Apache/Apache/conf $ORACLE_HOME/Apache/Apache/conf.orig
   
   

4. Change directory to the configuration file directory:

   $ cd $ORACLE_HOME/Apache/Apache/conf
   
   

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

   $ cp /old_oracle_home/Apache/Apache/conf/httpd.conf .
   
   

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

Make Global Changes

Make the following global changes to the httpd.conf file:

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 you do not currently use SSL.

   
   

Modify the List of LoadModule Directives

Modify the list of LoadModule directives:

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 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
   
   

Remove Directives and Sections for Unsupported Features

To remove all directives and sections for unsupported features:

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

   Alias /jservdocs/ "oracle_home/Apache/Jserv/docs/"
   Alias /soapdocs/ "/oracle_home/soap/"
   
   

2. Remove the following include directive:

   include "/oracle_home/Apache/Jserv/etc/jserv.conf"
   
   

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

Modify Port Numbers

The httpd.conf file used by previous releases of Oracle HTTP Server that were installed with Oracle Server specified 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 will listen 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 will listen 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.

Verify the Values of the User and Group Directives

If necessary, change the values specified by the User and Group directives, as follows:

• The User directive should specify the user name of the Oracle Software Owner user that you used to install Oracle HTTP Server. The default value is oracle.

• The Group directive should specify the name of the Oracle Inventory group on this system. The default value is oinstall.

Modify Existing Sections and Directives

Modify the following sections and directives:

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_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_home/perl/lib/5.6.1:/oracle_home/perl/lib/site_perl/5.6.1"
   
   

Add New Sections and Directives

Add the following new sections and directives to the file:

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. Include the following lines before the line that includes the oracle_apache.conf file:

   # Include the configuration files needed for mod_oc4j
   include "/oracle_home/Apache/Apache/conf/mod_oc4j.conf"
   
   # Loading mod_rewrite module here as it has to load before mod_oc4j
   LoadModule rewrite_module     libexec/mod_rewrite.so
   
   

Migrate 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:

1. Enter a command similar to the following in a separate terminal window:

   $ /new_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 this 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, if that directive is not preceded by the comment character (#). 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, if that directive is not preceded by the comment character (#). 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: /new_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:

   
   

   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.

   
   

   $ /oracle_home/Apache/Apache/bin/iasobf -p wallet_pwd
   
   

   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.

Modify 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_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_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.

Copy 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

5.1.5 Migrate Database Access Descriptors Used by mod_plsql

If you used mod_plsql to access a database with the previous release of Oracle HTTP Server, you must migrate the database access descriptors (DADs) to the format required by mod_plsql in the current release. You can use the dadTool.pl Perl script to complete this migration. To run this script, follow these steps:

1. If necessary, switch user to the Oracle software owner user (typically oracle):

   $ su - oracle
   
   

2. Set the ORACLE_HOME environment variable to specify the path to the Oracle home directory for the current release and set the PATH environment variable to include the directory containing the perl executable:

   • Bourne, Bash, or Korn shell:

     $ ORACLE_HOME=new_oracle_home_path 
     $ PATH=${ORACLE_HOME}/perl/bin:${PATH} 
     $ PATH=${ORACLE_HOME}/Apache/modplsql/conf:${PATH} 
     $ export ORACLE_HOME PATH
     
     

   • C or tcsh shell:

     % setenv ORACLE_HOME new_oracle_home_path
     % setenv PATH ${ORACLE_HOME}/perl/bin:${PATH}
     % setenv PATH ${ORACLE_HOME}/Apache/modplsql/conf:${PATH}
     
     

3. Set the appropriate shared library path environment variable for your platform to include the $ORACLE_HOME/lib directory. The following table shows the appropriate environment variable for each platform:

   Platform	Environment Variable
   AIX	LIBPATH
   HP-UX	SHLIB_PATH
   Linux, Solaris, and Tru64 UNIX	LD_LIBRARY_PATH

   
   

   For example, to set the SHLIB_PATH environment variable in the Bourne shell on HP-UX systems, enter the following command:

   $ SHLIB_PATH=$ORACLE_HOME/lib:${SHLIB_PATH}; export SHLIB_PATH
   
   

4. Change directory to the mod_plsql configuration directory for the current release of Oracle HTTP Server:

   $ cd $ORACLE_HOME/Apache/modplsql/conf
   
   

5. Copy the DAD configuration file (wdbsvr.app) used by the previous release to this directory:

   $ cp /old_oracle_home/Apache/modplsql/cfg/wdbsvr.app .
   
   

6. Enter the following command to run the script:

   $ perl dadTool.pl -m
   
   

   The script reads the DAD information from the wdbsvr.app file and creates new equivalent DADs in the dads.conf file.

5.1.6 Starting, Stopping, and Restarting Oracle HTTP Server

You must use Oracle Process Manager and Notification server (OPMN) with Oracle HTTP Server. To use OPMN, you must first start the OPMN daemon. To start the OPMN daemon and the Oracle HTTP Server processes together, enter the following command:

$ $ORACLE_HOME/opmn/bin/opmnctl startall

When the OPMN daemon is running, you can enter the following commands to start, stop, or restart Oracle HTTP Server:

• Start Oracle HTTP Server only:

  $ $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
  
  

• Stop Oracle HTTP Server only:

  $ $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
  
  

• Restart Oracle HTTP Server only:

  $ $ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=HTTP_Server
  
  

To stop the OPMN daemon and the Oracle HTTP Server processes, enter the following command:

$ $ORACLE_HOME/opmn/bin/opmnctl stopall

5.2.1 Restart Oracle HTTP Server

If you installed Oracle HTML DB in an existing Oracle home directory, you must restart Oracle HTTP Server. To restart Oracle HTTP Server, enter the following command:

$ $ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=HTTP_Server

5.2.2 Verify the Installation

To verify the installation, open the Oracle HTML DB administration page in a Web browser. To complete this task, follow these steps:

1. Open the following URL in a Web browser:

   http://>hostname:port/pls/htmldb/htmldb_admin
   
   

   In this example:

   • hostname is the Oracle HTTP Server host name

   • port is the Oracle HTTP Server port

2. Log in to Oracle HTML DB using the user name ADMIN and the password that you specified during the installation.