5 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:

Installing the Standalone Oracle HTTP Server
Reconfiguring the Existing Domain with the Reconfiguration Wizard
The Reconfiguration Wizard reconfigures the domain while retaining the location of the domain. Use the Reconfiguration Wizard to upgrade your domain to the latest version.
Upgrading the 12c Domain using Upgrade Assistant
Verifying the Upgrade

Parent topic: Upgrading a Standalone Oracle HTTP Server

5.1 Installing the Standalone Oracle HTTP Server

To install the standalone Oracle HTTP Server:

Sign in to the target system where you want to install the 12.2.1.1 product distribution.
Download the Oracle HTTP Server distribution (fmw_12.2.1.1.0_ohs_linux64.bin for UNIX and setup_fmw_12.2.1.1.0_ohs_win64.exe for Windows) from Oracle Technology Network or Oracle Software Delivery Cloud on your target system.
Change to the directory where you downloaded the Oracle HTTP Server distribution.
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
Start the installation program by entering the following command:
On UNIX operating system:

./ohs_linux64.bin

On Windows operating system:

setup_ohs_win64.exe
On UNIX operating system, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location and click Next.

Note:
Installation Inventory Setup screen does not appear on Windows operating system.
On the Welcome screen, review the information to make sure that you have met all the prerequisites and click Next.
On the Auto Updates screen, select Skip Auto Updates 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.
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.
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.
The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again.

To ignore the error or the warning message and continue with the installation, click Skip, however this approach is not recommended.
On the Security Updates screen, indicate how you would like to receive security updates if you already have an Oracle Support account.
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.
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.
On the Installation Progress screen, click Next when the progress bar displays 100%.
The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information on this screen and click Finish to close the installer.

You have installed the Oracle HTTP Server in a standalone mode.

5.2 Reconfiguring the Existing Domain with the Reconfiguration Wizard

The Reconfiguration Wizard reconfigures the domain while retaining the location of the domain. Use the Reconfiguration Wizard to upgrade your domain to the latest version.

To reconfigure the domain:

Sign in to the system on which the domain resides.
Edition Based Database Users Only: If you have configured your schemas with Edition-Based Reassociation, you must manually supply a default edition name before running the Reconfiguration Wizard.
To set the default edition, enter the following SQL command:

ALTER DATABASE DEFAULT EDITION = edition_name;
Where, edition_name is the name of the default database edition.
Run the Reconfiguration Wizard by entering the following command:
On UNIX operating system:

$ORACLE_HOME/oracle_common/common/bin/reconfig.sh

On Windows operating system:

%ORACLE_HOME%\oracle_common\common\bin\reconfig.cmd

Note:
When you run the reconfig.cmd or reconfig.sh command, you can get the following error message to indicate that the default cache directory is not valid:
*sys-package-mgr*: can't create package cache dir

You can change the cache directory by including the -Dpython.cachedir=valid_directory parameter in the command.

Oracle recommends that you specify the "log" option while starting the Reconfiguration Wizard as shown in the following example:

./reconfig.sh -log=/$ORACLE_HOME/logs/reconfig.log -log_priority=ALL

You can set the log_priority as per your requirements.
On the Select Domain screen, specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
The Reconfiguration Setup Progress screen shows the progress of the setup process. When complete, click Next.
During this process:
- The 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.
On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. Click Next.

Note:
You cannot change the Domain Mode at this stage.

For a list of JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations.
A JDBC data source contains a pool of database connections that are created when the data source instance is created, deployed or targeted, or at server startup.
Applications look up a data source on the JNDI tree, and then request a connection. When the applications no longer need the connections, they return the connections to the connection pool in the data source.

You can configure the JDBC data sources defined in your domain source on the JDBC Data Sources screen. The JDBC data sources associated with the products for which you are creating the domain are listed in the lower half of the screen.

Select the data source(s) from the Data Source Name drop-down list for which you want to specify the settings. The values that you specify are displayed in the appropriate columns in the data source list, for the selected data source.
For Oracle RAC Configuration for data sources, you can select one of the three options:
- Convert to GridLink
- Convert to RAC multi data source
- Don’t convert
For more information about each option, click Help.
After specifying the details, click Next.

If you do not select any data sources on the JDBC Data Sources screen, you get a pop-up with the following warning:

Missing Driver

Click Ok to proceed without verification, click Cancel to return to the JDBC Data Sources page.

In this case, if you click Ok, the data sources are not verified.
On the JDBC Data Sources Test screen, select the check box for the data source connection you configured on the JDBC Data Sources screen and click Test Selected Connections to test the data source connection.

Note:
In order to test the database connections, the database to which you are connecting must be running. If you do not want to test the connections at this time, do not select any data sources. Click Next to continue.
On the Database Configuration Type screen, select RCU Data .
Enter the database connection details using the RCU service table (STB) schema credentials and click Get RCU Configuration.

The Reconfiguration Wizard uses this connection to automatically configure the data sources required for components in your domain.

If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.
On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema.
When the check is complete, click Next.

The Node Manager screen is only displayed if the domain you are reconfiguring is currently using a per host Node Manager.

On the Node Manager screen, select the Node Manager configuration to use for the reconfigured domain. The resulting configuration depends on the combination of options you select for Node Manager Type and Node Manager Configuration.

Table 5-1 Field Descriptions for Node Manager Screen

Option	Description
Per Domain Default Location	If you select this option, the Node Manager home is redefined to $domain_name/nodemanager and you cannot edit the Node Manager home.
Per Domain Custom Location	Select this option if you want the per domain Node Manager configuration files to be created in a specific location for this domain. Specify the directory in the Node Manager Home field, or click Browse to use the navigation tree to select the location. The specified directory must be empty. The nodemanager.properties and nodemanager.domains files are created in this directory.
Node Manager Home	If you selected the Per Domain Custom Location option, click Browse to navigate to the directory location that you want to use to store the per domain Node Manager configuration.
Manual Node Manager Setup	If you select this option, creation of the Node Manager configuration for the domain is skipped (all remaining fields cannot be modified), and if you want to use Node Manager in the domain, you must manually configure Node Manager as described in Completing the Node Manager Configuration. The reconfigured domain will still use a per host Node Manager configuration. You should also select this option if your existing domain is not configured to use Node Manager and you do not want to use Node Manager in the reconfigured domain. For more information about Node Manager configuration, see Administering Node Manager for Oracle WebLogic Server.
Node Manager Configuration	Select one of the following two options. These fields are not available if you selected Manual Node Manager Setup.
Create New Configuration	A per domain Node Manager configuration will be automatically created for the reconfigured domain using default settings in nodemanager.properties. If necessary, you can modify nodemanager.properties after the domain has been successfully reconfigured.
Migrate Existing Configuration	The existing per host Node Manager configuration will be migrated to a per domain configuration for the reconfigured domain. This does not include environment-specific settings for ListenAddress, ListenPort, StartScriptName, JavaHome, and LogFile.
Node Manager Home	If you selected the Migrate Existing Configuration option, enter or browse to the Node Manager home directory that you want to migrate to the reconfigured domain.
Apply Oracle Recommended Defaults	If you selected the Migrate Existing Configuration option, select this check box if you want to use Oracle-recommended defaults in the nodemanager.properties file. Deselect this check box if you want to continue using the settings in the nodemanager.properties file being migrated. Oracle-recommended properties with default values are as follows: LogLimit=0 AuthenticationEnabled=true LogLevel=INFO DomainsFileEnabled=true NativeVersionEnabled=true LogToStderr=true SecureListener=true LogCount=1 StopScriptEnabled=false QuitEnabled=false LogAppend=true StateCheckInterval=500 CrashRecoveryEnabled=false StartScriptEnabled=true LogFormatter=weblogic.nodemanager.server.LogFormatter ListenBacklog=50
Node Manager Credentials: Username, Password	Specify the username and password that you want to use to start Node Manager in the reconfigured domain.

On the Advanced Configuration screen, you can select all categories for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.

Note:
The categories that are listed on the Advanced Configuration screen depend on the resources defined in the templates you selected for the domain.

For this upgrade, select none of the options and click Next.
On the Configuration Summary screen, 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.

To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.

Note:
The location of the domain does not change when you reconfigure it.
The Reconfiguration Progress 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 progress bar shows 100%, click Next.
The End of Configuration 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). If the reconfiguration is successful, it displays “Oracle WebLogic Server Reconfiguration Succeeded”.
If the reconfiguration process did not complete successfully, an error message is displayed to indicate the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.

Note the Domain Location and the Admin Server URL for further operations.

5.3 Upgrading the 12c Domain using Upgrade Assistant

To upgrade the 12c domain using Upgrade Assistant:

Run the Upgrade Assistant from the 12.2.1.1 Oracle home by entering the following command:
On UNIX operating system:

$Oracle_Home/oracle_common/upgrade/bin/ua

On Windows operating system:

%Oracle_Home%\oracle_common\upgrade\bin\ua.bat
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, click Help on the Upgrade Assistant screen.
On the Standalone Components screen, select Standalone System Component Configurations.
Select Update an Existing Domain and enter the location of the existing 12c domain in the Domain Directory field. You can also click Browse to select the existing 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, 12.1.3 or 12.2.1.0) to the latest 12c release (12.2.1.1).
On the Component List screen, verify that all the components you want to upgrade within a domain are listed and click Next.
If you do not see the components you want to upgrade, click Back to go to the previous screen and specify a different domain.
On the Prerequisites screen, acknowledge that the prerequisites have been met by checking all the check boxes. Click Next.

Note:
The Upgrade Assistant does not verify whether the prerequisites have been met.
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.
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 “Examine finished.”, 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.
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.
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.
If the upgrade is successful, you see the Upgrade Success screen. Click Close to complete the upgrade and close the wizard.
The Post-Upgrade Actions window describes the manual tasks you must perform to make the component functional in the new installation. This is an optional window that only appears if a component has post-upgrade steps.
If the upgrade has failed, you see the Upgrade Failure screen. This indicates that the upgrade of one or more components has failed. The components cannot be upgraded this time.
Click View Log to view and troubleshoot the errors.

Fix the issues in the pre-upgrade environment before starting the Upgrade Assistant again. Restore your pre-upgrade environment from backup (making sure to keep the original backup files in a separate location), fix the issues, and restart the Upgrade Assistant.

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

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

Change directory to the following:
On UNIX operating system:

$DOMAIN_HOME/bin

On Windows operating system:

%DOMAIN_HOME%\bin
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. Click Tools and then click Node Manager.

5.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:

Change directory to the following
On UNIX operating system:

$DOMAIN_HOME/bin

On Windows operating system:

%DOMAIN_HOME%\bin
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.