4 Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release

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

Note:

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

This chapter contains the following sections:

Parent topic: Upgrading a Standalone Oracle HTTP Server

4.1 Installing the Standalone Oracle HTTP Server

To install the standalone Oracle HTTP Server:
  1. Log in to the target system.
  2. Download the Oracle HTTP Server distribution (ohs_linux64.bin|setup_ohs_win64.exe) from Oracle Technology Network or Oracle Software Delivery Cloud on your system.
  3. Change to the directory where you downloaded the Oracle HTTP Server distribution.
  4. Check that your machines meet the following requirements:
    • Ensure that the system, patch, kernel, and other requirements are met as specified in Installing and Configuring Oracle HTTP Server.
    • Because Oracle HTTP Server is installed by default on port 7777, you must ensure that port 7777 is not used by any service on the nodes. To check if this port is in use, run the following command before installing Oracle HTTP Server. You must free the port if it is in use.

      netstat -an | grep 7777

  5. Launch the installation program by entering the following command:
    On UNIX operating system:
    ./ohs_linux64.bin
    On Windows operating system:
    setup_ohs_win64.exe
  6. On the Installation Inventory Setup screen, specify the location where you want to create your central inventory in the Inventory Directory field.
    Make sure that the Operating System Group name that you selecte on this screen has write permissions to the central inventory location. Click OK.

    Note:

    This screen does not appear on Windows operating systems. For more information about the central inventory, see Understanding the Oracle Central Inventory in Installing Software with the Oracle Universal Installer.
  7. On the Welcome screen, review the information and click Next.
  8. On the Auto Updates screen, select one of the following and click Next:
    • Skip Auto Updates: If you do not want your system to check for software updates at this time.
    • Select patches from directory: To navigate to a local directory if you downloaded patch files.
    • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.
  9. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    Since you are installing the standard installation topology for Oracle HTTP Server in a standalone domain, you can specify an Oracle home directory of your choice. However, ensure that you install the software in a new Oracle home.
    For more information about Oracle Fusion Middleware directory structure, see Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.
  10. On the Installation Type screen, select Standalone HTTP Server (Managed independently of WebLogic server) and click Next.
    For more information about the installation types, see Introducing the Oracle HTTP Server Standard Installation Topologies in Installing and Configuring Oracle HTTP Server.
  11. On the Prerequisite Check screen, verify that your system meets the minimum necessary requirements and click Next. If you see a warning or error message, see Oracle Fusion Middleware System Requirements and Specifications.
    For more information about other options on this screen, click Help.
  12. The Specify Security Updates screen only appears when you select Standalone HTTP Server (Managed independently of WebLogic server) as the installation type.
    If you already have an Oracle Support account, use this screen to indicate how you would like to receive security updates.
    If you do not have an Oracle Support account and you are sure that you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.
  13. On the Installation Summary screen, verify the installation options you selected.
    To save these options to a response file, click Save Response File and enter the location and the name of the response file. You can use response files for silent installation. Click Install.
  14. On the Installation Progress screen, click Next when the progress bar displays 100%.
    If the installation is successful, the Installation Complete screen displays the message Oracle HTTP Server (OHS) installation completed successfully. Click Finish to dismiss the installer.
You have installed the Oracle HTTP Server in a standalone mode.

4.2 Upgrading the 12.1.2 Domain using the Re-Configuration Wizard

You need to upgrade the 12.1.2 Oracle HTTP Server domain using the 12c Re-Configuration Wizard. To upgrade the 12.1.2 domain, follow the procedure documented in Using the Reconfiguration Wizard to Upgrade Your 12c Domain.

4.3 Upgrading the 12c Domain using Upgrade Assistant

To upgrade the 12c domain using Upgrade Assistant:
  1. Run the Upgrade Assistant from the 12.2.1 Oracle home by entering the following command:
    On UNIX operating system:
    12c_Oracle_Home/oracle_common/upgrade/bin/.ua
    On Windows operating system:
    12c_Oracle_Home\oracle_common\upgrade\bin\ua.bat
  2. The Welcome screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. Click Next.
    For more information about using the Upgrade Assistant, see Upgrading with the Upgrade Assistant or click Help on the Upgrade Assistant screen.
  3. On the Standalone Components screen, select Standalone System Component Configurations.
    Select Update an Existing Domain and enter the 12.1.2 domain location in the Domain Directory field. You can also click Browse to select the 12.1.1 domain directory using the navigation tree. Click Next.

    Note:

    • Create a New Domain option should only be used if you are upgrading from version 11g.

    • If you have already created a new 12c standalone domain for your upgraded 11g system components, you can extend the standalone domain with the standalone Oracle HTTP Server using Update an Existing Domain option.

    • Update an Existing Domain option should only be used if you are upgrading from a previous 12c release (12.1.2 or 12.1.3) to the latest 12c release (12.2.1).

  4. The Component List screen displays the standalone system component infrastructure and the Oracle HTTP Server that are available for upgrade.
    Review the list to verify that the required components are displayed. If you do not see the components you want to upgrade, you may have selected the wrong domain. Click Back to go to the previous screen and specify a different domain.
  5. On the Prerequisites screen, acknowledge that the prerequisites have been met by checking all the three boxes. Click Next.

    WARNING:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  6. On the Instance Directories screen, select 12c Source and click Next.
    You do not need to enter the Oracle instance directories when upgrading to the latest 12c release from a previous 12c release.
  7. The Examine screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. If the status is “succeeded”, click Upgrade.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No on the Examination Failure dialog box. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes on the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the schemas or configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  8. On the Upgrade Summary screen, review the summary of the options you have selected by expanding the tree.
    Review the Source Version and the Target Version to make sure that both the versions are correct before proceeding with the upgrade.
    The response file collects and stores all the information that you have entered through the Upgrade Assistant's graphical user interface , and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant wizard performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save and provide the location and name of the response file.
    Click Upgrade to start the upgrade process.
  9. The Upgrade Progress screen shows the status of the upgrade process and the projected Target Version of the component after a successful upgrade. Click Next.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.
  10. On the End of Upgrade, click Finish to complete the upgrade and dismiss the wizard.

4.4 Verifying the Upgrade

You can verify that the upgrade is successful if you are able to start the Node Manager and the Standalone Oracle HTTP Server properly. If you experience post-upgrade issues, you need to troubleshoot the installation and retry the upgrade. For more information, see Troubleshooting Oracle HTTP Server in Administrator's Guide for Oracle HTTP Server.

To start the Node Manager and the Standalone Oracle HTTP Server, see the following topics:

  • Starting the Node Manager
    Server instances in a WebLogic Server production environment are often distributed across multiple domains, machines, and geographic locations. Node Manager is a WebLogic Server utility that enables you to manage (start, shut down, and restart) your Oracle HTTP Server instance.
  • Starting the Standalone Oracle HTTP Server
    You can use the startComponent.sh|cmd script to start the standalone Oracle HTTP Server.

4.4.1 Starting the Node Manager

Server instances in a WebLogic Server production environment are often distributed across multiple domains, machines, and geographic locations. Node Manager is a WebLogic Server utility that enables you to manage (start, shut down, and restart) your Oracle HTTP Server instance.

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.

Note:

On UNIX platform, do not run Node Manager as the root user.
To start the Node Manager:
  1. Change directory to the following:
    Domain_home/bin
  2. On the UNIX operating system, start the Node Manager by running the following command:
    nohup ./startNodeManager.sh > nm.out&
    Where, nohup and nm.out are sample output files.
    On the Windows operating system, start the Node Manager by running the following command:
    startNodeManager.cmd
    You can also use a shortcut on the Start menu to start the Node Manager (Tools > Node Manager).

4.4.2 Starting the Standalone Oracle HTTP Server

You can use the startComponent.sh|cmd script to start the standalone Oracle HTTP Server.

To start the standalone Oracle HTTP Server:
  1. Change directory to the following
    Domain_home/bin
  2. On UNIX operating system, enter the following command:
    ./startComponent.sh ohs_name
    On Windows operating system, enter the following command:
    startComponent.cmd ohs_name
    For more information, see Starting and Stopping System Components in Administering Oracle Fusion Middleware.