3 Introduction to the Standalone Oracle 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 (12.1.2 and above) of Oracle HTTP Server to this Oracle HTTP Server 12c Release (12.2.1.1).

Caution:

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

If your Oracle HTTP Server is managed through Oracle WebLogic, then follow the procedure in Upgrading a Managed Oracle HTTP Server.

This chapter includes the following sections:

Understanding the Standalone Oracle HTTP Server Topology
In 12c, a standalone Oracle HTTP Server is not managed by or registered to an Oracle WebLogic Server domain. A standalone Oracle HTTP Server 12c topology is installed and configured without the Oracle Fusion Middleware Infrastructure. A managed Oracle HTTP Server, 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.
Overview of the Standalone Oracle HTTP Server Upgrade Process
The valid starting points for upgrading the Oracle HTTP Server are 11g Release 11.1.1.7 and above and 12c Release 12.1.2 and above.

Parent topic: Upgrading a Standalone Oracle HTTP Server

3.1 Understanding the Standalone Oracle HTTP Server Topology

In 12c, a standalone Oracle HTTP Server is not managed by or registered to an Oracle WebLogic Server domain. A standalone Oracle HTTP Server 12c topology is installed and configured without the Oracle Fusion Middleware Infrastructure. A managed Oracle HTTP Server, 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.

Note:

For more information on installing and configuring a standalone Oracle HTTP Server, see Installing and Configuring Oracle HTTP Server.
For more information on the latest 12c standalone domain, see What Is a Standalone Domain? in Understanding Oracle Fusion Middleware.
For more information on the administration scenarios and key features of the Oracle HTTP Server, see Introduction to Oracle HTTP Server Administrator's Guide for Oracle HTTP Server.
For more information on upgrading a managed Oracle HTTP Server, see Performing the Infrastructure Upgrade in Upgrading to the Oracle Fusion Middleware Infrastructure.

Figure 3-1 shows a standalone Oracle HTTP Server topology.

Figure 3-1 Standalone Oracle HTTP Server Upgrade Topology

Description of "Figure 3-1 Standalone Oracle HTTP Server Upgrade Topology "

Table 3-1 describe the elements of this topology

Table 3-1 Description of the Elements in the Oracle Fusion Middleware Standalone Oracle HTTP Server Upgrade Topology

Element	Description and Links to Additional Documentation
WEBHOST	Standard term used in Oracle documentation referring to the machine that hosts the Web tier.
Standalone Domain	A standalone domain is only created if you are upgrading from 11g to 12c. If you are upgrading from 12.1.2 or 12.1.3, then the standalone domain already exists and there is no need to create the standalone domain. The 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 Understanding Oracle Fusion Middleware.

Element

Description and Links to Additional Documentation

WEBHOST

Standard term used in Oracle documentation referring to the machine that hosts the Web tier.

Standalone Domain

A standalone domain is only created if you are upgrading from 11g to 12c. If you are upgrading from 12.1.2 or 12.1.3, then the standalone domain already exists and there is no need to create the standalone domain.

The 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 Understanding Oracle Fusion Middleware.

3.2 Overview of the Standalone Oracle HTTP Server Upgrade Process

The valid starting points for upgrading the Oracle HTTP Server are 11g Release 11.1.1.7 and above and 12c Release 12.1.2 and above.

The following sections provide a high level overview of the procedures you need to perform to upgrade your standalone Oracle HTTP Server:

3.2.1 Flow Chart of the Standalone Upgrade Process from 11g to 12c

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

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

Note:

Before starting the upgrade, you must shutdown the 11g instance.

Figure 3-2 Standalone Oracle HTTP Server Upgrade from 11g to 12c

Description of "Figure 3-2 Standalone Oracle HTTP Server Upgrade from 11g to 12c"

3.2.2 Roadmap for Upgrading a Standalone Oracle HTTP Server from 11g to 12c

Table 3-2 describes the tasks that must be completed to upgrade a standalone Oracle HTTP Server from 11g to 12c.

Table 3-2 Roadmap for Standalone Oracle HTTP Server Upgrade Process

Step No.	Importance (Mandatory, Conditional, or Optional)	Task	Description
1	Recommended.	Verify that you are upgrading a standalone Oracle HTTP Server.	To determine which Oracle HTTP Server you have in your existing environment, see Determining whether Oracle HTTP Server is Standalone or Managed (Collocated).
2	Optional.	Learn about the interoperability and compatibility factors that could affect how you upgrade to BI 12.2.1.1.	It is important to understand how two or more Oracle Fusion Middleware products of the same version or different versions work together (interoperate) in a supported Oracle Fusion Middleware configuration. You can learn more about interoperability and compatibility in Understanding Interoperability and Compatibility.
3	Mandatory.	Back up your existing environment.	It is important to back up your existing environment before the upgrade because the domain configurations are upgraded in-place. The back-up allows you to restore your pre-upgrade environment in case the upgrade fails or if the upgrade results are unsatisfactory.
4	Mandatory.	Complete the pre-upgrade tasks.	The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating non-SYSDBA user. For a complete list of pre-upgrade tasks, see Preparing to Upgrade Oracle HTTP Server.
5	Mandatory.	Install the Standalone Oracle HTTP Server.	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 Oracle HTTP Server.
6	Mandatory.	Upgrade the 11g domain configurations with the Upgrade Assistant.	After the installation, you need to use the Upgrade Assistant to upgrade the Oracle HTTP Server and system component infrastructure. See Upgrading the 11g Domain using Upgrade Assistant.
7	Mandatory.	Complete the post-upgrade tasks and verify the upgrade.	Your Oracle HTTP Server should continue to function as expected. If you have post-upgrade issues, you will need to troubleshoot the installation and retry the upgrade. See Troubleshooting Oracle HTTP Server in Administering Oracle HTTP Server.

3.2.3 Flow Chart of the Standalone Oracle HTTP Server Upgrade Process from a Previous 12c Release

Figure 3-3 shows the high-level procedures associated with a standalone Oracle HTTP Server upgrade when the starting point is another 12c release. The tools used for each step are also listed.

Detailed instructions for upgrading your standalone Oracle HTTP Server are described in Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release.

Note:

Before starting the upgrade, you must shutdown the 12c instance.

Figure 3-3 Standalone Oracle HTTP Server Upgrade from a Previous 12c release

Description of "Figure 3-3 Standalone Oracle HTTP Server Upgrade from a Previous 12c release"

3.2.4 Roadmap for Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release

Table 3-3 describes the tasks that must be completed to upgrade a standalone Oracle HTTP Server from a previous release of 12c to the latest version.

Table 3-3 Roadmap for Standalone Oracle HTTP Server Upgrade Process

Step No.	Importance (Mandatory, Conditional, or Optional)	Task	Description
1	Recommended.	Verify that you are upgrading a standalone Oracle HTTP Server.	To determine which Oracle HTTP Server you have in your existing environment, see Determining whether Oracle HTTP Server is Standalone or Managed (Collocated).
2	Optional.	Learn about the interoperability and compatibility factors that could affect how you upgrade to BI 12.2.1.1.	It is important to understand how two or more Oracle Fusion Middleware products of the same version or different versions work together (interoperate) in a supported Oracle Fusion Middleware configuration. You can learn more about interoperability and compatibility in Understanding Interoperability and Compatibility.
3	Mandatory.	Back up your existing environment.	It is important to back up your existing environment before the upgrade because the domain configurations are upgraded in-place. The back-up allows you to restore your pre-upgrade environment in case the upgrade fails or if the upgrade results are unsatisfactory.
4	Mandatory.	Complete the pre-upgrade tasks.	The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating non-SYSDBA user. For a complete list of pre-upgrade tasks, see Preparing to Upgrade Oracle HTTP Server.
5	Mandatory.	Install the Standalone Oracle HTTP Server.	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 Oracle HTTP Server.
6	Mandatory.	Reconfigure your existing domain.	Run the Reconfiguration Wizard from 12c Oracle HTTP Server installation to reconfigure the existing domain. See Reconfiguring the Existing Domain with the Reconfiguration Wizard.
7	Mandatory.	Upgrade the domain configurations with the Upgrade Assistant.	After the installation, you need to use the Upgrade Assistant to upgrade the Oracle HTTP Server and system component infrastructure. See Upgrading the 12c Domain using Upgrade Assistant.
8	Mandatory.	Complete the post-upgrade tasks and verify the upgrade.	Your Oracle HTTP Server should continue to function as expected. If you have post-upgrade issues, you need to troubleshoot the installation and retry the upgrade. Troubleshooting Oracle HTTP Server in Administering Oracle HTTP Server.