1 Introduction to the Standalone HTTP Server Upgrade

This chapter provides a general introduction to the Oracle Fusion Middleware Standalone Oracle HTTP Server and an overview of the steps you must perform to upgrade from an Oracle Fusion Middleware 11g or a previous 12c release of Oracle HTTP Server to Oracle HTTP Server 12c (12.1.3).

This chapter includes the following sections:

Section 1.1, "Understanding the Standalone OHS Topology"
Section 1.2, "Determining if the OHS is Standalone or Managed (Colocated)"
Section 1.3, "Overview of the Standalone OHS Upgrade Process"

Caution:

This guide should be used to upgrade an Oracle HTTP Server that is NOT managed through a WebLogic Server domain.

If your OHS is managed through Oracle WebLogic, then the OHS can be upgraded as part of the Fusion Middleware infrastructure and you should follow the upgrade procedures in "Performing the Infrastructure Upgrade" in Oracle Fusion Middleware Upgrading to the Oracle Fusion Middleware Infrastructure.

1.1 Understanding the Standalone OHS Topology

In 12c (12.1.3), a standalone Oracle HTTP Server (OHS) is not managed by or registered to an Oracle WebLogic Server domain. A standalone Oracle HTTP Server 12.1.3 topology is installed and configured without the Oracle Fusion Middleware Infrastructure. A managed Oracle HTTP Server (OHS), however, is associated with an existing Oracle WebLogic Server domain. For the standalone scenario, you install the Oracle HTTP Server software in its own Oracle home, and you configure the Oracle HTTP Server instance in its own standalone domain.

Element	Description and Links to Additional Documentation
WEBHOST	Standard term used in Oracle documentation referring to the machine that is hosting the Web tier.
Standalone Domain	A standalone domain is only created if you are upgrading from 11g to 12.1.3. If you are upgrading from 12.1.2 to 12.1.3, then the standalone domain will already exist and there is no need to create the standalone domain. This standalone domain has a directory structure similar to an Oracle WebLogic domain, but it does not contain an Administration Server or Managed Servers. The Oracle WebLogic Server Node Manager and other tools allow you to manage the standalone Oracle HTTP Server instance. For more information on standalone domains, see "What Is a Standalone Domain?" in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.

1.2 Determining if the OHS is Standalone or Managed (Colocated)

Do the following to determine if the OHS you are trying to upgrade is managed or standalone:

If you are an 11g user: Check for the registered property in the file $ORACLE_INSTANCE/config/OPMN/opmn/instance.properties. If it is set to true, then the instance is registered. A managed Oracle HTTP Server (OHS) will be registered, if it is not registered then it is Standalone OHS.

If you are a 12c user: 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 OHS. And if you find an element with name Oracle HTTP Server (Collocated), then it is collocated.

1.3 Overview of the Standalone OHS Upgrade Process

The following sections provide a high level overview of the procedures you will perform to upgrade your standalone OHS:

Flow Chart of the Standalone OHS Upgrade Process from 11g to 12.1.3
Roadmap for Upgrading a Standalone OHS from 11g to 12.1.3
Flow Chart of the Standalone OHS Upgrade Process from 12.1.2 to 12.1.3
Roadmap for Upgrading a Standalone OHS From 12.1.2 to 12.1.3

1.3.1 Flow Chart of the Standalone OHS Upgrade Process from 11g to 12.1.3

Figure 1-2 shows the high-level procedures associated with a standalone OHS upgrade when the starting point is 11g. The tools used for each step are also listed.

Detailed instructions for upgrading your standalone OHS are described in Chapter 2, "Upgrading a Standalone Oracle HTTP Server from 11g to 12c".

Figure 1-2 Standalone Oracle HTTP Server Upgrade from 11g to 12.1.3

1.3.2 Roadmap for Upgrading a Standalone OHS from 11g to 12.1.3

Table 1-2 describes the tasks that must be completed to upgrade a standalone OHS from 11g to 12.1.3.

Table 1-2 Overview of the Standalone OHS Upgrade Process

Task	Description	Documentation
Verify that you are upgrading a standalone OHS.	The steps in this document describe the process for upgrading a standalone Oracle HTTP Server. If you are upgrading an OHS that is managed by a WebLogic server domain, the upgrade steps will be different.	To determine which OHS you have in your existing environment, see For information on upgrading a managed Oracle HTTP Server, see "Performing the Infrastructure Upgrade" in Oracle Fusion Middleware Upgrading to the Oracle Fusion Middleware Infrastructure.
Verify your system environment.	Before beginning the upgrade, verify that the minimum system and network requirements are met.	See "Verifying Certification and System Requirements" in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
Obtain the Oracle HTTP Server distribution.	To create the topology described in this guide, obtain the Oracle Fusion Middleware Oracle HTTP Server distribution.	See "Understanding and Obtaining Product Distributions" in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
Install the software.	Run the installation program to install the software. Select the installation type Standalone Oracle HTTP Server (managed independently of WebLogic server). This transfers the software to your system and creates a new Oracle home directory.	See "Installing the Standalone OHS".
Run the Upgrade Assistant.	After the installation, you will use the Upgrade Assistant to upgrade the OHS and system component infrastructure.	See "Starting the Upgrade Assistant".
Perform any required post-upgrade steps.	You may be required to perform additional steps after the upgrade.	See Performing Required Post-Upgrade Tasks.
Start Node Manager and OHS.	After the upgrade, start the Node Manager and OHS.	See "Starting the Node Manager" and "Starting the Standalone OHS Server".
Verify the upgrade was successful.	Your OHS should continue to function as expected. If you have post-upgrade issues, you will need to troubleshoot the installation and retry the upgrade.	"Troubleshooting Oracle HTTP Server" in Administering Oracle HTTP Server.

1.3.3 Flow Chart of the Standalone OHS Upgrade Process from 12.1.2 to 12.1.3

Figure 1-2 shows the high-level procedures associated with a standalone OHS upgrade when the starting point is 12.1.2. The tools used for each step are also listed.

Detailed instructions for upgrading your standalone OHS are described in Chapter 3, "Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release to 12.1.3".

Figure 1-3 Standalone Oracle HTTP Server Upgrade from 12.1.2 to 12.1.3

1.3.4 Roadmap for Upgrading a Standalone OHS From 12.1.2 to 12.1.3

Table 1-3 describes the tasks that must be completed to upgrade a standalone OHS from a previous release of 12c to 12.1.3.

Table 1-3 Overview of the Standalone OHS Upgrade Process

Task	Description	Documentation
Verify that you are upgrading a standalone 12.1.2 OHS.	The steps in this document describe the process for upgrading a standalone Oracle HTTP Server. If you are upgrading an OHS that is managed by a WebLogic server domain, the upgrade steps will be different.	For information on upgrading a managed Oracle HTTP Server, see "Performing the Infrastructure Upgrade" in Oracle Fusion Middleware Upgrading to the Oracle Fusion Middleware Infrastructure.
Verify your system environment.	Before beginning the upgrade, verify that the minimum system and network requirements are met.	See "Verifying Certification and System Requirements" in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
Obtain the Oracle HTTP Server distribution.	To create the topology described in this guide, obtain the Oracle Fusion Middleware Oracle HTTP Server distribution.	See "Understanding and Obtaining Product Distributions" in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
Install the software.	Run the installation program to install the software. This transfers the software to your system and creates a new Oracle home directory.	See "Installing the Standalone OHS".
Reconfiguring the domain.	To start the Reconfiguration Wizard from 12.1.3 OHS installation to perform domain-related upgrades, run the following command: On UNIX: `ORACLE_HOME/oracle_common/common/bin/reconfig.sh` On Windows: `ORACLE_HOME\oracle_common\common\bin\reconfig.cmd`	See "Reconfiguring the Domain".
Run the Upgrade Assistant.	After the installation, you will use the Upgrade Assistant to upgrade the OHS and system component infrastructure.	See "Starting the Upgrade Assistant".
Perform any required post-upgrade steps.	You may be required to perform additional steps after the upgrade.	See Performing Required Post-Upgrade Tasks.
Verify the upgrade was successful.	Your OHS should continue to function as expected. If you have post-upgrade issues, you will need to troubleshoot the installation and retry the upgrade.	"Troubleshooting Oracle HTTP Server" in Administering Oracle HTTP Server.
Start Node Manager and OHS.	After the upgrade, start the Node Manager and OHS.	See "Starting the Node Manager" and "Starting the Standalone OHS Server".