6 Upgrading a Managed Oracle HTTP Server from a Previous 12c Release

This chapter describes the procedure for upgrading a managed Oracle HTTP Server from to a latest 12c release from a previous 12c release. The valid starting point for this upgrade are 12c releases 12.1.2 and above.

This procedure assumes that you have the 12.1.2 Fusion Middleware Infrastructure (JRF plus the WebLogic Server) installed and configured on your system.

Before installing the 12c software, shut down all the 12.1.2 server instances except the RDBMS.

Parent topic: Upgrading a Managed Oracle HTTP Server

6.1 Installing the Managed 12c (12.2.1) Oracle HTTP Server

Before you upgrade your existing Managed Oracle HTTP Server components, you must first install the Oracle HTTP Server Release 12.2.1.

To install the Oracle HTTP Server:
  1. Log in to the host where you want to install the Oracle HTTP Server.
  2. Download the Oracle HTTP Server product distribution (ohs_linux64.bin|setup_ohs_win64.exe) from Oracle Technology Network or Oracle Software Delivery Cloud on your host system.
  3. 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

  4. On UNIX platforms, if the /etc/oraInst.loc file exists, check that its contents are correct. Specifically, check that the inventory directory is correct and that you have write permissions for that directory.
    If the /etc/oraInst.loc file does not exist, you can skip this step.
  5. Run the installer 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 select 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 a collocated Oracle HTTP Server in a WebLogic Server domain, enter the path to an existing Oracle Fusion Middleware Infrastructure 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 Collocated HTTP Server (Managed through 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. 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.
  13. 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 collocated mode.
How to install Oracle HTTP Server?

6.2 Upgrading the 12c (12.1.2 or 12.1.3) Schema using Upgrade Assistant

You need to upgrade the 12c (12.1.2 or 12.1.3) OPSS and IAU (Audit Services) schema using the 12c Upgrade Assistant.

To upgrade the 12c (12.1.2 or 12.1.3) OPSS and IAU schema:
  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 Selected Schemas screen, select Individually Selected Schemas to upgrade selected schemas for your installed components and click Next.
    The Upgrade Assistant identifies the components that are available for a schema upgrade thus allowing you to select the schemas you want to include in the upgrade.

    Caution:

    Upgrade only those schemas that are used to support your 12.2.1 components. Do not upgrade schemas that are currently being used to support 11g or 12c components that are not included in the Oracle Fusion Middleware 12.2.1 release.
  4. The Available Components screen provides a list of installed Oracle Fusion Middleware components that have schemas that can be upgraded. When you select a component, the schemas and any dependencies are automatically selected.
    Select Oracle Platform Security Services. Selecting this automatically selects Oracle Audit Services. Click Next.
  5. On the Domain Directory screen, enter the 12c (12.1.2 or 12.1.3) WebLogic domain directory. Click Browse and use the navigation tree to select the 12c WebLogic domain directory.
    The Upgrade Assistant requires the 12c domain location to access the jps-config.xml file.
  6. 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.
  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.

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

6.4 Upgrading the Component Configuration

If you are running the Upgrade Assistant from an Oracle home that contains managed domain components, then the WebLogic Component Configuration upgrade option is available.

To upgrade the component configurations for Oracle HTTP Server:
  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 WebLogic Components screen, select the WebLogic Component Configurations option to upgrade component configurations for a managed WebLogic Server domain. Enter the connection details required to connect to the WebLogic Administration Server that is managing the domain and click Next.
  4. The Component List screen provides a list of components that are included in the WebLogic domain's component configuration upgrade. The name of the domain is provided along with the list of components located within the domain.
    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. 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.

  7. 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.
  8. 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.
  9. On the End of Upgrade, click Finish to complete the upgrade and dismiss the wizard.

6.5 Post-Upgrade Tasks

The post-upgrade tasks include starting the Node Manager, starting the Administration Server, starting the Oracle HTTP Server, and verifying whether the upgrade from 12.1.2 to 12.2.1 is successful.

  • 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 start, shut down, and restart Administration Server and Managed Server instances from a remote location.
  • Starting the Administration Server
    One instance of WebLogic Server in each domain acts as an Administration Server. The Administration Server provides a central point for managing a WebLogic Server domain. All other WebLogic Server instances in a domain are called Managed Servers. In a domain with only a single WebLogic Server instance, that server functions both as Administration Server and Managed Server.
  • Starting the Oracle HTTP Server
    You can use Enterprise Manager Fusion Middleware Control or the opmnctl command to start, stop, and restart Oracle HTTP Server.
  • Verifying that Oracle HTTP Server Installation is Successful
    If you can log in to the Administration Console and the Enterprise Manager Fusion Middleware Control, you have installed Oracle HTTP Server successfully.

6.5.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 start, shut down, and restart Administration Server and Managed Server instances from a remote location.

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:
    Oracle_home/wlserver/server/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).

6.5.2 Starting the Administration Server

One instance of WebLogic Server in each domain acts as an Administration Server. The Administration Server provides a central point for managing a WebLogic Server domain. All other WebLogic Server instances in a domain are called Managed Servers. In a domain with only a single WebLogic Server instance, that server functions both as Administration Server and Managed Server.

In a development environment, it is usually sufficient to start an Administration Server and deploy your applications directly onto the Administration Server. However, in a production environment, it is recommended that you create Managed Servers to run your applications.

To start an Administration Server:
  1. Change directory to the following:
    Oracle_Home\user_projects\domains\DOMAIN_NAME
    Where, DOMAIN_NAME is the name of the directory in which you located the domain.
  2. On the Windows operating system, start the Administration Server by running the following command:
    startWebLogic.cmd
    On the Windows operating system, the Configuration Wizard creates a shortcut on the Start menu to start the Administration Server that you created.
    On the UNIX operating system, start the Administration Server by running the following command:
    ./startWebLogic.sh

    Note:

    If the server prompts you to enter a username and password, enter the name of a WebLogic Server user who has permission to start servers.

6.5.3 Starting the Oracle HTTP Server

You can use Enterprise Manager Fusion Middleware Control or the opmnctl command to start, stop, and restart Oracle HTTP Server.

6.5.3.1 Starting the Oracle HTTP Server using the Enterprise Manager Fusion Middleware Control

To start an Oracle HTTP Server using the Enterprise Manager Fusion Middleware Control:
  1. Go to the Oracle HTTP Server home page.
  2. From the Oracle HTTP Server menu:
    1. Select Control.
    2. Select Start Up from the Control menu.
    Or
  3. From the Target Navigation tree:
    1. Right-click the Oracle HTTP Server instance you want to start.
    2. Select Control.
    3. Select Start Up from the Control menu.
6.5.3.1.1 Starting the Oracle HTTP Server using opmnctl
To start Oracle HTTP Server components in an Oracle instance using opmnctl:
  1. Change directory to the following:
    ORACLE_INSTANCE/bin
  2. Run the following command to start all Oracle HTTP Server components in an Oracle instance
    opmnctl startproc process-type=OHS
6.5.3.1.2 Determining the Status of Oracle HTTP Server Components using opmnctl
To determine the status of the Oracle HTTP Server components:
  1. Change directory to the following:
    ORACLE_INSTANCE/bin
  2. Enter the following command:
    opmnctl status
    Following is a sample output:
    Processes in Instance: instance1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status  
---------------------------------+--------------------+---------+---------
webcache1                        | WebCache-admin     |   19556 | Alive   
webcache1                        | WebCache           |   19555 | Alive   
ohs1                             | OHS                |    7249 | Alive

6.5.4 Verifying that Oracle HTTP Server Installation is Successful

If you can log in to the Administration Console and the Enterprise Manager Fusion Middleware Control, you have installed Oracle HTTP Server successfully.

To verify whether the software patch is installed successfully:
  1. Log in to the following URL:
    http://MachineName.us.oracle.com:7777
  2. To access Enterprise Manager Fusion Middleware Control:
    http://MachineName.us.oracle.com:7001/em