1 Introduction to Upgrading Oracle HTTP Server to 14c (14.1.2.0.0)

Before you begin, review all introductory information to understand the standard upgrade topologies and upgrade paths for Oracle HTTP Server 14c (14.1.2.0.0)

About the Starting Points for an Oracle HTTP Server Upgrade

You can upgrade a managed (collocated) Oracle HTTP Server deployment from Oracle Fusion Middleware 12c (12.2.1.4.0) and a standalone Oracle HTTP Server 12c (12.2.1.4.0) and 14 c (14.1.1.0.0) to 14c (14.1.2.0.0)

Supported release starting points are:

  • Oracle HTTP Server 12c (12.2.1.4) and and 14 c (14.1.1.0.0) for standalone servers

  • Oracle HTTP Server 12c (12.2.1.4) for managed servers

About the Oracle HTTP Server Standard Topologies

The steps to upgrade Oracle HTTP Server to 14c (14.1.2.0.0) depend on the existing production topology.

As a result, it is difficult to provide exact upgrade instructions for every possible Oracle HTTP Server installation. Therefore, this upgrade documentation provides instructions for upgrading several typical Oracle HTTP Server topologies. These typical topologies are referred to as standard upgrade topologies.

Your actual topology may vary, but the topologies described here provide an example that can be used as a guide to upgrade other similar Oracle HTTP Server topologies.

About Upgrade Restrictions

If you are using two or more Oracle Fusion Middleware products of the same or different versions in a single, supported, Oracle Fusion Middleware configuration, you must consider the interoperability and compatibility factors before planning the upgrade.

For a list of products and features available in Oracle Fusion Middleware Release 14.1.2.0.0, see Products and Features Available in Oracle Fusion Middleware in Understanding Interoperability and Compatibility.

When performing the upgrade of your hardware or software, verify that your Oracle Fusion Middleware software is certified to support the new operating system or computer hardware. For more information, refer to the following resources:

Determining whether Oracle HTTP Server is Standalone or Managed (Collocated)

Oracle HTTP Server is the web server component for Oracle Fusion Middleware. It provides a listener for Oracle WebLogic Server and the framework for hosting static pages, dynamic pages, and applications over the Web. If you configure Oracle HTTP Server in a WebLogic Server domain, it is considered a managed Oracle HTTP Server because you can manage the Oracle HTTP Server instances like any other elements of the WebLogic Server domain using Enterprise Manager Fusion Middleware Control, the WLST command-line interface, or the Node Manager. If you install the Oracle HTTP software in a separate Oracle home, without installing the Oracle Fusion Middleware Infrastructure, it is considered a standalone deployment.

To determine whether you are upgrading a managed or a standalone Oracle HTTP Server:

Check the element extention-template-ref and its attribute name in the file DOMAIN_HOME/init-info/domain-info.xml. If you find an element with the name Oracle HTTP Server (Standalone), then it is a standalone Oracle HTTP Server. And if you find an element with name Oracle HTTP Server (Collocated), then it is collocated.

Note:

This guide covers the procedures for upgrading both managed and standalone OHS deployments. Perform only those tasks that apply to your environment.