2
Oracle HTTP Server Migration

This chapter explains the process of migrating the Oracle HTTP Server version 1.3.9 to version 1.3.12. Each section includes information for JDK migration, servlet migration, and mod_ssl migration, where applicable.

Contents

• Pre-migration

• Environment

• Configuration

• Application Logic

• Tools

Pre-migration

No pre-migration tasks are necessary.

Environment

No environment migration tasks are necessary.

Configuration

The following sections explain changes you must make to your configuration files so that the Oracle HTTP Server version 1.3.12 continues to work as it did with Oracle Internet Application Server Release 1.0.0.

The installation process creates backup copies of the configuration files, so if a configuration file is corrupted during the migration process, you can restore the original version by copying the default version over the corrupted version.

The files listed in Table 2-1 may be affected by the migration from version 1.0.0 to version 1.0.2.

Table 2-1 Configuration Files Used by Oracle HTTP Server

Configuration File	Description
NEW_HOME/Apache/Apache/conf/httpd.conf	The main HTTP server configuration file.
NEW_HOME/Apache/Jserv/etc/jserv.conf	Java servlet engine configuration file.
NEW_HOME/Apache/Jserv/etc/jserv.properties	Java servlet engine configuration file.
NEW_HOME/Apache/Jserv/etc/zone.properties	Java servlet zone configuration file.
NEW_HOME/Apache/Apache/conf/oracle_apache.conf	Oracle configuration file.

HTTP Server, JDK, and servlets

The configuration files supplied with the Oracle9i Application Server Release 1.0.2 installation will support all of the applications deployed in version 1.0.0 without modification, unless you have changed the version 1.0.0 configuration files. In that case, you must apply those changes to the version 1.0.2 files.

Oracle has made a number of changes to these files in version 1.0.2. The changes are listed below. To migrate your files, use the diff command, ignoring the listed Oracle changes, and manually migrate any remaining changes into the configuration files.

httpd.conf

The Oracle changes to this file are listed below.

• The httpds.conf file name is changed to httpd.conf.

• The httpds prefix is removed from all log files. For example, httpds_error_log is changed to error_log.

• The httpds file name prefix has been changed to httpd. For example, httpds.pid is changed to httpd.pid.

• AddModule mod_jserv.c is removed so mod_jserv now loads dynamically.

• A Port 7777 directive is added.

• The ExtendedStatus directive is set to on.

• A server-status directive is added or uncommented.

• The SSLLogLevel directive is changed from INFO to WARN.

• A perl-status directive is added, but commented out.

jserv.conf

• The LoadModule jserv_module is added.

• The IfModule container for mod_jserv.c is removed.

• The jserv-status handler directives are commented out.

jserv.properties

• A wrapper.classpath directive is added for:
  • tools.jar

  • aurora_client.jar

  • vbjorb.jar

  • vbjapp.jar

• A wrapper.env directive is added for $ORACLE_HOME/bin.

• A wrapper.classpath directive is removed for jbojdbcpatch.zip

Additional appended lines or directives may have been added by other Oracle9i Application Server components and are contained within comment fields identifying the component. See the chapter for a given component to determine the necessary migration tasks.

oracle_apache.conf

Oracle made no changes to this file. If you have changed it, you must apply the changes to this file in the new version installation.

zone.properties

Oracle made no changes to this file. If you have changed it, you must apply the changes to this file in the new version installation.

mod_ssl

Oracle Internet Application Server 1.0.0 uses open_ssl 0.9.4. Oracle9i Application Server 1.0.2 uses open_ssl 0.9.5.a. There are no known migration issues for Oracle9i Application Server associated with this version change.

To migrate the mod_ssl configuration, you must copy the configuration files listed in Table 2-2 from the version 1.0.0 $ORACLE_HOME directory to the version 1.0.2 $ORACLE_HOME directory.

Table 2-2 Migration of mod_ssl configuration files

Copy all files from:	To:
OLD_HOME/Apache/Apache/conf/ssl.crl/	NEW_HOME/Apache/Apache/conf/ssl.crl/
OLD_HOME/Apache/Apache/conf/ssl.crt/	NEW_HOME/Apache/Apache/conf/ssl.crt/
OLD_HOME/Apache/Apache/conf/ssl.csr/	NEW_HOME/Apache/Apache/conf/ssl.csr/
OLD_HOME/Apache/Apache/conf/ssl.key/	NEW_HOME/Apache/Apache/conf/ssl.key/
OLD_HOME/Apache/Apache/conf/ssl.prm/	NEW_HOME/Apache/Apache/conf/ssl.prm/

Changing httpd.conf for mod_ssl migration

To migrate mod_ssl, you must replace the path of the version 1.0.0 Oracle home with the path of the version 1.0.2 Oracle home in the httpd.conf file, which is shown as NEW_HOME in the example below. You can safely replace the old file with the new file.

#SSLSessionCache shm:<NEW_HOME>/Apache/Apache/logs/httpd _ssl_scache(512000)
SSLSessionCache dbm:<NEW_HOME>/Apache/Apache/logs/httpd _ssl_scache

SSLMutex  file:<NEW_HOME>/Apache/Apache/logs/httpd _ssl_mutex
SSLLog <NEW_HOME>/Apache/Apache/logs/httpd _ssl_engine_log
SSLCertificateFile <NEW_HOME>/Apache/Apache/conf/ssl.crt/server.crt
SSLCertificateKeyFile <NEW_HOME>/Apache/Apache/conf/ssl.key/server.key
#SSLCertificateChainFile <NEW_HOME>/Apache/Apache/conf/ssl.crt/ca.crt
#SSLCACertificatePath <NEW_HOME>/Apache/Apache/conf/ssl.crt
#SSLCACertificateFile <NEW_HOME>/Apache/Apache/conf/ssl.crt/ca-bundle.crt
#SSLCARevocationPath <NEW_HOME>/Apache/Apache/conf/ssl.crl
#SSLCARevocationFile <NEW_HOME>/Apache/Apache/conf/ssl.crl/ca-bundle.crl
#SSLOptions +FakeBasicAuth +ExportCertData +CompatEnvVars +StrictRequire
<Files ~ "\.(cgi|shtml)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "<NEW_HOME>/Apache/Apache/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>
CustomLog <NEW_HOME>/Apache/Apache/logs/httpd _ssl_request_log \
       			   "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

Application Logic

This section describes the migration tasks related to application logic when migrating the HTTP Server and its components.

HTTP Server

There are no differences in the Oracle HTTP Server shipped with Oracle9i Application Server Release 1.0.2 that affect deployment of applications from Oracle Internet Application Server 1.0.0.

JDK

Java applications compiled in JDK 1.1.8 and deployed in Oracle Internet Application Server 1.0.0 should function in the same manner when deployed in Oracle9i Application Server 1.0.2 with the JDK version 1.2.2.

However, be aware that the use of any Java feature that was deprecated in version 1.2.2 might require code changes and recompilation. Become familiar with JDK version 1.2.2, and review all code written for JDK 1.1.8, if necessary.

Servlets

The Apache JServ version is unchanged between Oracle Internet Application Server Release 1.0.0 and Oracle9i Application Server Release 1.0.2. Servlets written to the JServ version 2.0 API and deployed in Oracle Internet Application Server 1.0.0 should function in the same manner when deployed in Oracle9i Application Server 1.0.2.

mod_ssl

Copy all certificates, requests, and files to the locations shown in "Changing httpd.conf for mod_ssl migration" and restart Oracle9i Application Server.

mod_perl

Modify the Perl path (typically, the first line of the Perl script) to reflect the location of the Oracle9i Application Server version 1.0.2 installation.

If any new third-party modules have been added to Perl, they need to be added to the Oracle9i Application Server version 1.0.2 installation.

Tools

No tools migration tasks are necessary for the HTTP Server, JDK, servlets, or mod_ssl.