Oracle® Fusion Middleware

Upgrading a Standalone Oracle HTTP Server

12c (12.1.3)

E51318-01

May 2014

Oracle Fusion Middleware Upgrading a Standalone Oracle HTTP Server 12c (12.1.3)

E51318-01

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Primary Authors:  Lisa Jamen, Contributing Author: Sreetama Ghosh.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

What's New in This Guide

- New and Changed Features for 12c

- Other Significant Changes in this Document for 12c

1 Introduction to the Standalone HTTP Server Upgrade

- 1.1 Understanding the Standalone OHS Topology

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

- 1.3 Overview of the Standalone OHS Upgrade Process

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

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

- 1.3.3 Flow Chart of the Standalone OHS Upgrade Process 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

2 Upgrading a Standalone Oracle HTTP Server from 11g to 12c

- 2.1 Important Pre-Upgrade Considerations

- 2.1.1 WebCache 11g Users

- 2.1.2 WebGate 11g Users

- 2.1.3 Application Artifacts from 11g

- 2.2 Upgrading a Standalone Oracle HTTP Server (OHS)

- 2.3 Performing Post-Upgrade Tasks

- 2.3.1 Migrating 11g Application Artifacts

3 Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release to 12.1.3

- 3.1 Upgrading a Standalone Oracle HTTP Server (OHS)

Preface

This preface contains the following sections:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This manual is intended for Oracle Fusion Middleware system administrators who are responsible for upgrading Oracle Fusion Middleware. It is assumed that the readers of this manual have knowledge of the following:

- Oracle Fusion Middleware 11g or Oracle Fusion Middleware 12c system administration and configuration information for the existing deployment

- The configuration and expected behavior of the system or systems being upgraded

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following related documentation available in the Oracle Fusion Middleware 12c (12.1.3) documentation library:

- Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware

- Oracle Fusion Middleware Installing and Configuring Oracle HTTP Server

- Administering Oracle HTTP Server

- Oracle Fusion Middleware Administering Oracle Fusion Middleware

- Oracle Fusion Middleware Understanding Oracle Fusion Middleware

- Oracle Fusion Middleware Upgrading to the Oracle Fusion Middleware Infrastructure

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

What's New in This Guide

The following topics introduce the new and changed features of the standalone Oracle HTTP Server and provides pointers to additional information.

New and Changed Features for 12c

Before you begin the upgrade process, review the following list of changes for standalone Oracle HTTP Servers in 12.1.3:

- The installer will no longer create a separate instance directory for Oracle HTTP Server. Instance information for the standalone OHS will be stored in a new standalone domain home. For more information, see Section 1.1, "Understanding the Standalone OHS Topology".

- OPMN agent and opmnctl command line utility are no longer used in Oracle Fusion Middleware. Instead, system components are managed by NodeManager and WLST commands.

Other Significant Changes in this Document for 12c

This guide is new to the Fusion Middleware library in 12c.

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.

See Also:

- For more information on installing and configuring a standalone Oracle HTTP Server, see Oracle Fusion Middleware Installing and Configuring Oracle HTTP Server

- For more information on the new 12c standalone domain, see "What Is a Standalone Domain?" in Oracle Fusion Middleware Understanding Oracle Fusion Middleware

- For more information on the administration scenarios and key features of the OHS, see "Introduction to Oracle HTTP Server" Administering Oracle HTTP Server.

- For more information on upgrading a managed OHS, see "Performing the Infrastructure Upgrade" in Oracle Fusion Middleware Upgrading to the Oracle Fusion Middleware Infrastructure"

Figure 1-1 shows a standalone OHS topology.

Figure 1-1 Standalone OHS Upgrade Topology

Table 1-1 describe the elements of this topology

Table 1-1 Description of the Elements in the Oracle Fusion Middleware Standalone OHS Upgrade Topology

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

2 Upgrading a Standalone Oracle HTTP Server from 11g to 12c

This chapter describes the procedures for upgrading an 11g standalone Oracle HTTP Server to 12c (12.1.3); one that is not managed by, or registered to, an existing Oracle WebLogic Server (WLS) domain.

Caution:

If you are upgrading an Oracle WebLogic managed Oracle HTTP Server, see Oracle Fusion Middleware Upgrading to the Oracle Fusion Middleware Infrastructure. If you are unsure, see Determining if the OHS is Standalone or Managed (Colocated) to determine which OHS you are upgrading.

This chapter contains the following sections:

- Section 2.2, "Upgrading a Standalone Oracle HTTP Server (OHS)"

- Section 2.3, "Performing Post-Upgrade Tasks"

Note:

The information in this chapter assumes that you have read and performed any required pre-upgrade tasks in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.

2.1 Important Pre-Upgrade Considerations

Before you begin the upgrade, carefully review the following sections to determine if upgrading your standalone 11g Oracle HTTP Server (OHS) to 12c (12.1.3) will cause any issues with your existing setup.

- WebCache 11g Users

- WebGate 11g Users

- Application Artifacts from 11g

2.1.1 WebCache 11g Users

Consider the following limitations if you are using WebCache in your 11g environment:

- There is no WebCache in 12c. Correspondingly, there is no upgrade for WebCache.

- WebCache 11g front-ending a 12c OHS is not a certified combination.

- If both WebCache and OHS are used in 11g, only the OHS can be upgraded to 12c. In that case, the 11g WebCache needs to be disabled and configuration changes have to be made to direct the traffic to OHS directly.

- If both WebCache and OHS are used in 11g, and they are registered to a Oracle WebLogic Server (WLS) domain for administering them through Fusion Middleware Control, then the WLS domain also needs to be upgraded to 12c. In that case, the associated OHS will also be upgraded to 12c. However, the WebCache will be removed from the 12c Fusion Middleware Control.

2.1.2 WebGate 11g Users

WebGate is included as part of OHS 12c (12.1.3) installation and will be upgraded as part of the OHS upgrade process through Upgrade Assistant.

2.1.3 Application Artifacts from 11g

If you have 11g application artifacts that you will continue to use in 12c (12.1.3), carefully review the following:

- As part of upgrading OHS from an 11g Oracle instance to a 12c domain, the OHS configuration directory layout is being migrated from an Oracle instance to a standalone domain.

- Oracle HTTP Server 11g configuration files that reside in the component configuration directory of the Oracle instance will be migrated automatically.

- Application artifacts that reside within the Oracle instance, including any combination of static files (such as HTML or images, CGI or FastCGI scripts or applications, or third-party modules), must be migrated manually after the upgrade to 12c (12.1.3).
For more information, see Section 2.3.1, "Migrating 11g Application Artifacts".

2.2 Upgrading a Standalone Oracle HTTP Server (OHS)

Perform the following tasks to complete the standalone OHS upgrade:

- Task 1, "Installing the Standalone OHS"

- Task 2, "Starting the Upgrade Assistant"

- Task 3, "Completing the Upgrade Assistant Screens"

- Task 4, "Performing Required Post-Upgrade Tasks"

- Task 5, "Verifying the Upgrade"

- Task 6, "Starting the Node Manager"

- Task 7, "Starting the Standalone OHS Server"

Task 1   Installing the Standalone OHS

To start the installation program, perform the following steps.

1. Log in to the target system.

2. Go to the directory in which you downloaded the installation program.

3. Launch the installation program by entering the following command:

- On Linux:
./ohs_linux64.bin

- On Windows:
setup_ohs_win64.exe

The installation program begins to install the software.

For a description of each installation program screen, see "Navigating the Installation Screens" in Oracle Fusion Middleware Installing and Configuring Oracle HTTP Server.

Table 2-1 shows the standalone-specific installation options you should select on the installer screens.

CAUTION:

After the installation is complete, stop. You will start the Upgrade Assistant to create and configure the standalone OHS domain. DO NOT configure your new Oracle HTTP Server domain with the Configuration Wizard.

Table 2-1 Standalone Oracle HTTP Server Installation Options

Screen

Description and Action

Installation Type

Select the first option Standalone HTTP Server (Managed independently of WebLogic server).

Click Next.

Installation Summary

Review the Standalone OHS installation location, disk space and feature sets that will be installed. Click Install only after you have reviewed the information.

Task 2   Starting the Upgrade Assistant

To start the Upgrade Assistant using the graphical user interface, navigate to the oracle_common directory of the Oracle home where your products are installed.

1. Change directory to ORACLE_HOME/oracle_common/upgrade/bin on Unix operating systems or ORACLE_HOME\oracle_common\upgrade\bin on Windows operating systems.

2. Enter the following command to start the Upgrade Assistant.
On UNIX operating systems:

./ua

On Windows operating systems:

ua.bat

Task 3   Completing the Upgrade Assistant Screens

Table 2-2 describes the screens that will appear when you are running the Upgrade Assistant from an Oracle home that contains a standalone Oracle HTTP Server installation.

If you need additional help with any of the upgrade screens, click the screen name.

Table 2-2 Upgrade Assistant Screens: Upgrading Standalone OHS

Screen

Description

Welcome

This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks.

Schemas or Standalone System Component Configurations

Select Standalone System Component Configurations.

Select Create a New Domain.

Click Next.

NOTE: The Create a New Domain option should only be used if upgrading from version 11g. If you already created a new 12.1.3 standalone domain for your upgraded 11g system components, you can extend the standalone domain with the standalone OHS using the Update an Existing Domain option.

The Update an Existing Domain option should only be used if you had previously run the UA and chose the Create a New Domain option.

Component List

Displays the standalone system component infrastructure and the Oracle HTTP Server that is available to upgrade.

Prerequisites

This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade.

You must check all of the boxes before you can continue.

Instance Directories

When upgrading OHS, you must provide the directory location of the 11g instance that will be upgraded. This instance will be used as a basis for configuring the new 12c OHS instance. The 11g OHS installation will not be modified.

Click + to add additional 11g instance directories, if necessary.

Node Manager

Use this screen to create a new Node Manager for the standalone domain. If you select the Create new Domain option, choose a new username and password for the new Node Manager. You will need these credentials when you start the OHS instances that require the Node Manager for start-up.

NOTE: This screen displays only when the Create a New Domain option is selected. It does not appear when Update an Existing Domain is selected.

Examine

This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.

If the Examine phase fails, see "Troubleshooting Your Upgrade" for information on resolving common upgrade errors.

Upgrade Summary

Use this screen to verify the upgrade options you selected. If you want to save these options to a response file, click Save and provide the location and name of the response file. Response files can be used later in a silent upgrade situation.

For more information about silent or command line installation, see "Performing Silent Upgrades" in Oracle Fusion Middleware Upgrading with the Upgrade Assistant.

Upgrade Progress

This screen shows the status of the upgrade process.

Upgrade Success

Or

Upgrade Failure

The upgrade was successful. The Post-Upgrade Actions window describes the manual tasks you must perform to make the component function in the new installation.

Or:

The upgrade failed for the specified component(s) and Upgrade Assistant will have to be restarted.

If the upgrade fails, see "Troubleshooting Your Upgrade" for information on resolving common upgrade errors.

Task 4   Performing Required Post-Upgrade Tasks

Depending on your environment, you may be required to perform additional post-upgrade tasks after the upgrade. See Performing Post-Upgrade Tasks to determine if any additional tasks are required for your use case scenarios.

Task 5   Verifying the Upgrade

To verify that the OHS upgrade was successful, launch the server and verify that it is working as expected. Successfully completing Tasks 6 and 7 will be your first indication of a successful upgrade.

If you experience post-upgrade issues, you will need to troubleshoot the installation and retry the upgrade. For more information, see "Troubleshooting Oracle HTTP Server" in Administering Oracle HTTP Server.

Task 6   Starting the Node Manager

To start Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:

./startNodeManager.sh >

On Windows operating systems, run:

startNodeManager.cmd

Note:

On Windows operating systems, it is recommended that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.

For more information, see "Running Node Manager as a Startup Service" in Administering Node Manager for Oracle WebLogic Server.

Task 7   Starting the Standalone OHS Server

To start the standalone OHS server, go to the DOMAIN_HOME/bin directory and execute the following command:

On Unix operating systems:

DOMAIN_HOME/bin/startComponent.sh ohs_name

On Windows operating systems:

DOMAIN_HOME\bin\startComponent.cmd ohs_name

For more information, see "Starting and Stopping System Components" in Oracle Fusion Middleware Administering Oracle Fusion Middleware.

2.3 Performing Post-Upgrade Tasks

This section describes the post-upgrade tasks that are required for some upgrade scenarios. Not all tasks will apply to your upgrade scenario. Review the following sections and perform only those tasks that are applicable to your environment:

- Migrating 11g Application Artifacts

2.3.1 Migrating 11g Application Artifacts

You will have to manually migrate any 11g application artifacts that reside within the Oracle instance, including any combination of static files such as HTML or images, CGI or FastCGI scripts or applications, or third-party modules. Application artifacts that were referred to by the 11g configuration, but were stored in directories outside of the Oracle instance, will continue to be referenced by the migrated configuration used by Oracle HTTP Server 12c.

For example, if a third-party plug-in module was installed into the Oracle home with Oracle HTTP Server 11g, and the configuration referenced it by the Oracle home location using the configuration in the example below, the plug-in module must be installed manually into the Oracle home with 12c (12.1.3) Oracle HTTP Server or the upgraded configuration must be modified to reference it elsewhere.

LoadModule example_module "${ORACLE_HOME}/ohs/modules/mod_example.so"

Similarly, if static files were copied into the /htdocs directory within the 11g component configuration directory, then they too must be manually copied into the 12c (12.1.3) instance configuration directory or the upgraded configuration must be modified to reference it elsewhere. Other types of application artifacts must be manually migrated in a similar manner.

3 Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release to 12.1.3

This chapter describes the process of upgrading a Standalone Oracle HTTP Server to 12c (12.1.3) from a previous Standalone Oracle HTTP Server 12c release.

This chapter contains the following section:

- Section 3.1, "Upgrading a Standalone Oracle HTTP Server (OHS)"

Note:

The information in this chapter assumes that you have read and performed any required pre-upgrade tasks in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.

3.1 Upgrading a Standalone Oracle HTTP Server (OHS)

Perform the following tasks to complete the standalone OHS upgrade:

- Task 1, "Installing the Standalone OHS"

- Task 2, "Reconfiguring the Domain"

- Task 3, "Completing the Reconfiguration Wizard Screens"

- Task 4, "Starting the Upgrade Assistant"

- Task 5, "Completing the Upgrade Assistant Screens"

- Task 6, "Performing Required Post-Upgrade Tasks"

- Task 7, "Verifying the Upgrade"

- Task 8, "Starting the Node Manager"

- Task 9, "Starting the Standalone OHS Server"

Task 1   Installing the Standalone OHS

To start the installation program, perform the following steps.

1. Log in to the target system.

2. Go to the directory in which you downloaded the installation program.

3. Launch the installation program by entering the following command:

- On UNIX:
./ohs_linux64.bin

- On Windows:
setup_ohs_win64.exe

The installation program begins to install the software.

For a description of each installation program screen, see "Navigating the Installation Screens" in Oracle Fusion Middleware Installing and Configuring Oracle HTTP Server.

Table 3-1 shows the standalone-specific installation options you should select on the installer screens.

CAUTION:

After the installation is complete, stop. You will start the Upgrade Assistant to create and configure the standalone OHS domain. DO NOT configure your new Oracle HTTP Server domain with the Configuration Wizard.

Table 3-1 Standalone Oracle HTTP Server Installation Options

Screen

Description and Action

Installation Type

Select the first option Standalone HTTP Server (Managed independently of WebLogic server).

Click Next.

Installation Summary

Review the Standalone OHS installation location, disk space and feature sets that will be installed. Click Install only after you have reviewed the information.

Task 2   Reconfiguring the Domain

Start the Reconfiguration Wizard from the standalone 12.1.3 OHS installation, to upgrade the existing standalone OHS domain.

Note: Whether it's a standalone OHS or a collocated OHS, in each case an OHS instance resides in a domain, and in order to upgrade the domain to 12.1.3 run the Reconfiguration Wizard.

Enter the following command to start the Reconfiguration Wizard.

On UNIX:

ORACLE_HOME/oracle_common/common/bin/reconfig.sh

On Windows:

ORACLE_HOME\oracle_common\common\bin\reconfig.cmd

Task 3   Completing the Reconfiguration Wizard Screens

Table 3-2 describes the screens that will appear when you are running the Reconfiguration Wizard from an Oracle home that contains a standalone Oracle HTTP Server installation.

If you need additional help with any of the Reconfiguration Wizard, click the screen name.

Table 3-2 Reconfiguration Wizard Screens: Upgrading Standalone OHS

Screen

Description

Select Domain

On this screen, you specify the location of the domain that you want to upgrade.

Reconfiguration Setup Progress

This screen displays the progress of the setup process. During this process:

- WLS core infrastructure files are updated.

- The WebLogic domain configuration is read.

- Reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xml, config-groups.xml, and security.xml (among others).

- Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

- The domain upgrade is validated.

Click Next to continue.

JDK Selection

Use the JDK section to select the JDK for the domain. Select only a JDK that is supported on the platform you are using. For a list of the JDKs that are supported for a specific platform, see "Oracle Fusion Middleware Supported System Configurations" on Oracle Technology Network.

System Components

Use this screen to add or delete system components.

OHS Server

Use this screen to configure the OHS servers in your domain.

Configuration Summary

Review the detailed configuration settings of the domain before continuing.You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list. If you need to change the configuration, click Back to return to the appropriate screen.When done, click Reconfig to reconfigure the domain. The location of the domain does not change.

Reconfiguration Progress

This screen displays the progress of the reconfiguration process. During this process:

- Domain information is extracted, saved, and updated.

- Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

- When the process completes, click Finish.

Configuration Success

This screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured as well as the Administration Server URL (including the listen port).

Task 4   Starting the Upgrade Assistant

To start the Upgrade Assistant using the graphical user interface, navigate to the oracle_common directory of the Oracle home where your products are installed.

1. Change directory to ORACLE_HOME/oracle_common/upgrade/bin on Unix operating systems or ORACLE_HOME\oracle_common\upgrade\bin on Windows operating systems.

2. Enter the following command to start the Upgrade Assistant.
On UNIX operating systems:

./ua

On Windows operating systems:

ua.bat

Task 5   Completing the Upgrade Assistant Screens

Table 3-3 describes the screens that will appear when you are running the Upgrade Assistant from an Oracle home that contains a standalone Oracle HTTP Server installation.

If you need additional help with any of the upgrade screens, click the screen name.

Table 3-3 Upgrade Assistant Screens: Upgrading Standalone OHS

Screen

Description

Welcome

This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks.

Standalone Components

Select Standalone System Component Configurations.

Select Update an Existing Domain. Enter the 12.1.2 domain.

Click Next.

NOTE: The Create a New Domain option should not be used when upgrading Standalone OHS from 12.1.2 to 12.1.3. This option is valid only when upgrading from 11g to 12c.

Component List

Displays the standalone system component infrastructure and the Oracle HTTP Server that is available to upgrade.

Prerequisites

This screen requires you to acknowledge that all prerequisites have been met before you continue with the upgrade.

You must check all of the boxes before you can continue.

Instance Directories

When upgrading from a previous release of 12c, select 12c Source and click Next. You do not need to enter directories when upgrading from a previous release of 12c.

Examine

This screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.

If the Examine phase fails, see "Troubleshooting Your Upgrade" for information on resolving common upgrade errors.

Upgrade Summary

Use this screen to verify the upgrade options you selected. If you want to save these options to a response file, click Save and provide the location and name of the response file. Response files can be used later in a silent upgrade situation.

For more information about silent or command line installation, see "Performing Silent Upgrades" in Oracle Fusion Middleware Upgrading with the Upgrade Assistant.

Upgrade Progress

This screen shows the status of the upgrade process.

Upgrade Success

Or

Upgrade Failure

The upgrade was successful. The Post-Upgrade Actions window describes the manual tasks you must perform to make the component function in the new installation.

Or:

The upgrade failed for the specified component(s) and Upgrade Assistant will have to be restarted.

If the upgrade fails, see "Troubleshooting Your Upgrade" for information on resolving common upgrade errors.

Task 6   Performing Required Post-Upgrade Tasks

Depending on your environment, you may be required to perform additional post-upgrade tasks after the upgrade.

Task 7   Verifying the Upgrade

To verify that the OHS upgrade was successful, launch the server and verify that it is working as expected. Successfully completing Tasks 6 and 7 will be your first indication of a successful upgrade.

If you experience post-upgrade issues, you will need to troubleshoot the installation and retry the upgrade. For more information, see "Troubleshooting Oracle HTTP Server" in Administering Oracle HTTP Server.

Task 8   Starting the Node Manager

To start Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > nm.out&

On Windows operating systems, run:

startNodeManager.cmd

Note:

To use a per-host Node Manager configuration, ensure that –Dohs.product.home=<MW_HOME> is set for JAVA_OPTIONS in the appropriate Node Manager script. Run the command NodeManager.cmd/sh if you are not using the Node Manager service. Run the command installNodeMgrSvc.cmd if you are using the Node Manager service.

The Host and Port used, should match those used with your Upgraded setup. For more information on how to edit the Host/Port values in the file to install the Node Manager Service with the correct details, see "Configuring Java Node Manager" in Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server

Task 9   Starting the Standalone OHS Server

To start the standalone OHS server, go to the DOMAIN_HOME/bin directory and execute the following command:

On Unix operating systems:

DOMAIN_HOME/bin/startComponent.sh ohs_name

On Windows operating systems:

DOMAIN_HOME\bin\startComponent.cmd ohs_name

For more information, see "Starting and Stopping System Components" in Oracle Fusion Middleware Administering Oracle Fusion Middleware.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.