3 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; one that is not managed by or associated with an existing Oracle WebLogic Server (WLS) domain.

This chapter contains the following sections:

About the Standalone Oracle HTTP Server Upgrade Process from 11g to 12c
Review the flowchart and roadmap for an overview of the upgrade process for Oracle HTTP Server.
Important Pre-Upgrade Considerations
Before you begin the upgrade, it is important to make sure that your existing setup is not impacted during or after the upgrade. If you are using Oracle Web Cache or WebGate, or if you have Application-specific artifacts in your 11g domain, review the topics under this section carefully to prevent impact to your existing setup.
Installing the Standalone Oracle HTTP Server
Before beginning your upgrade, download the Oracle HTTP Server 12c (12.2.1.2) distribution on the target system and install it using the Oracle Universal Installer.
Stopping Servers and Processes
Before you run the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all processes and servers, including the Administration Server and any managed servers.
Upgrading Domain Component Configurations
After reconfiguring the domain, use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration.
Starting Servers and Processes
After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.
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.

Parent topic: Upgrading Oracle HTTP Server from 11g to 12c

3.1 About the Standalone Oracle HTTP Server Upgrade Process from 11g to 12c

Review the flowchart and roadmap for an overview of the upgrade process for Oracle HTTP Server.

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

Figure 3-1 Upgrade Process Flowchart for Standalone Oracle HTTP Server from 11g to 12c

Description of "Figure 3-1 Upgrade Process Flowchart for Standalone Oracle HTTP Server from 11g to 12c"

The following table describes the tasks that must be completed to upgrade a standalone Oracle HTTP Server from 11g to 12c.

Table 3-1 Tasks for Upgrading Standalone Oracle HTTP Server from 11g to 12c

Task	Description
Required Verify that you are upgrading a standalone Oracle HTTP Server.	To determine which Oracle HTTP Server you have in your existing environment, see Determining whether Oracle HTTP Server is Standalone or Managed (Collocated).
Required Complete the pre-upgrade tasks.	The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating non-SYSDBA user. For a complete list of pre-upgrade tasks, see Preparing to Upgrade Oracle HTTP Server. Additionally, also complete the following tasks: Important Pre-Upgrade Considerations.
Required Install the Standalone Oracle HTTP Server.	Run the installation program to install the software. Select the installation type Standalone Oracle HTTP Server (managed independently of WebLogic server). This transfers the software to your system and creates a new Oracle home directory. See Installing the Standalone Oracle HTTP Server.
Required Shut down the 11g environment.	See Stopping Servers and Processes.
Required Upgrade the 11g standalone system component configurations.	See Upgrading Domain Component Configurations.
Required Restart the servers and processes.	See Starting Servers and Processes.
Required Verify the upgrade.	Your Oracle HTTP Server should continue to function as expected. If you have post-upgrade issues, you will need to troubleshoot the installation and retry the upgrade. See Troubleshooting Oracle HTTP Server in Oracle Fusion Middleware Administering Oracle HTTP Server.

Task

Description

Required

Verify that you are upgrading a standalone Oracle HTTP Server.

To determine which Oracle HTTP Server you have in your existing environment, see Determining whether Oracle HTTP Server is Standalone or Managed (Collocated).

Required

Complete the pre-upgrade tasks.

The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating non-SYSDBA user.

For a complete list of pre-upgrade tasks, see Preparing to Upgrade Oracle HTTP Server.

Additionally, also complete the following tasks: Important Pre-Upgrade Considerations.

Required

Install the Standalone Oracle HTTP Server.

Run the installation program to install the software. Select the installation type Standalone Oracle HTTP Server (managed independently of WebLogic server). This transfers the software to your system and creates a new Oracle home directory.

See Installing the Standalone Oracle HTTP Server.

Required

Shut down the 11g environment.

See Stopping Servers and Processes.

Required

Upgrade the 11g standalone system component configurations.

See Upgrading Domain Component Configurations.

Required

Restart the servers and processes.

See Starting Servers and Processes.

Required

Verify the upgrade.

Your Oracle HTTP Server should continue to function as expected. If you have post-upgrade issues, you will need to troubleshoot the installation and retry the upgrade.

See Troubleshooting Oracle HTTP Server in Oracle Fusion Middleware Administering Oracle HTTP Server.

3.2 Important Pre-Upgrade Considerations

Before you begin the upgrade, it is important to make sure that your existing setup is not impacted during or after the upgrade. If you are using Oracle Web Cache or WebGate, or if you have Application-specific artifacts in your 11g domain, review the topics under this section carefully to prevent impact to your existing setup.

Oracle Web Cache 11g Users
Oracle Web Cache is a secure reverse proxy cache and a compression engine deployed between a browser and the HTTP server or a browser and the Content Management server to improve the performance of the websites by caching frequently accessed content. Oracle has released the last version of Web Cache in 11g. Web Cache is not available in 12c.
WebGate 11g Users
A WebGate is a web-server plug-in for Oracle Access Manager (OAM) that intercepts HTTP requests and forwards them to the Access Server for authentication and authorization. WebGate is included as part of Oracle HTTP Server 12c installation and is upgraded as part of the Oracle HTTP Server upgrade process through Upgrade Assistant.
Updating the WebGate log file-name
In Oracle Fusion Middleware 12c, WebGate log file is renamed from oblog.log to webgate.log. After upgrading to the latest release of Oracle HTTP Server, you must manually update the oblog_config_wg.xml file and replace every occurrence of ‘oblog.log’ with ‘webgate.log’.
Application Artifacts from 11g
Application artifacts include all of your web resources: JSP files, images, stylesheets, Javascript, static HTML pages in addition to your Java classes and source files and web application configuration files. The integrated development environment (IDE) uses all of these resources, and refers to them as web application artifacts.
Migrating 11g Application Artifacts
You need 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.

3.2.1 Oracle Web Cache 11g Users

Oracle Web Cache is a secure reverse proxy cache and a compression engine deployed between a browser and the HTTP server or a browser and the Content Management server to improve the performance of the websites by caching frequently accessed content. Oracle has released the last version of Web Cache in 11g. Web Cache is not available in 12c.

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

Web Cache is not available in Fusion Middleware 12c. Correspondingly, there is no upgrade for Web Cache.
Web Cache 11g front-ending a 12c Oracle HTTP Server is not a certified combination.
If you are using both Web Cache and Oracle HTTP Server in your 11g setup, you can only upgrade the Oracle HTTP Server to 12c. In that case, you need to disable the 11g Web Cache and change the configuration settings to divert the traffic to Oracle HTTP Server directly.
If you are using both Web Cache and Oracle HTTP Server in your 11g setup, and you have associated them with a WebLogic Server (WLS) domain for administering them through the Enterprise Manager Fusion Middleware Control, then you must also upgrade the WLS domain to 12c. In that case, the associated Oracle HTTP Server is also upgraded to 12c. However, the Web Cache is removed from the 12c Fusion Middleware Control.

3.2.2 WebGate 11g Users

A WebGate is a web-server plug-in for Oracle Access Manager (OAM) that intercepts HTTP requests and forwards them to the Access Server for authentication and authorization. WebGate is included as part of Oracle HTTP Server 12c installation and is upgraded as part of the Oracle HTTP Server upgrade process through Upgrade Assistant.

Note:

In Oracle Fusion Middleware 12c (12.2.1.2), WebGate log file is renamed from oblog.log to webgate.log. After upgrading to the latest release of Oracle HTTP Server, you must manually update the oblog_config_wg.xml file and replace every ‘oblog.log’ occurrence with ‘webgate.log’. For a procedure to do this task, see Updating the WebGate log file-name.

3.2.3 Updating the WebGate log file-name

In Oracle Fusion Middleware 12c, WebGate log file is renamed from oblog.log to webgate.log. After upgrading to the latest release of Oracle HTTP Server, you must manually update the oblog_config_wg.xml file and replace every occurrence of ‘oblog.log’ with ‘webgate.log’.

To update the WebGate log file-name:

Change directory to the following path:
DOMAIN_HOME/config/fmwconfig/components/OHS/ohs_instance/webgate/config
Open the oblog_config_wg.xml file in edit mode.
Replace every occurrence of ‘oblog.log’ with ‘webgate.log’.

3.2.4 Application Artifacts from 11g

Application artifacts include all of your web resources: JSP files, images, stylesheets, Javascript, static HTML pages in addition to your Java classes and source files and web application configuration files. The integrated development environment (IDE) uses all of these resources, and refers to them as web application artifacts.

If you have 11g application artifacts that you want to continue using in 12c, carefully review the following:

As part of upgrading Oracle HTTP Server from an 11g Oracle instance to a 12c domain, the Oracle HTTP Server 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 are 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.

For more information, see Migrating 11g Application Artifacts.

3.2.5 Migrating 11g Application Artifacts

You need 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 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 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.3 Installing the Standalone Oracle HTTP Server

Before beginning your upgrade, download the Oracle HTTP Server 12c (12.2.1.2) distribution on the target system and install it using the Oracle Universal Installer.

To install the standalone Oracle HTTP Server:

Sign in to the target system where you want to install the 12c (12.2.1.2) product distribution.
Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
- Oracle HTTP Server (UNIX: fmw_12.2.1.2.0_ohs_linux64.bin), (Windows: setup_fmw_12.2.1.2.0_ohs_win64.exe)
Change to the directory where you downloaded the 12c (12.2.1.2) product distribution.
Check that your machines meet the following requirements:
- Ensure that the system, patch, kernel, and other requirements are met as specified in Roadmap for Verifying Your System Environment.
- 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:
(UNIX) ./fmw_12.2.1.2.0_ohs_linux64.bin

(Windows) setup_fmw_12.2.1.2.0_ohs_win64.exe
On UNIX operating systems, 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:
The Installation Inventory Setup screen does not appear on Windows operating systems.
On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
On the Auto Updates screen, select Skip Auto Updates. Options are:
- 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.
Click Next.
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 Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
On the Installation Type screen, select Standalone HTTP Server (Managed independently of WebLogic server) and click Next.
The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
To view the list of tasks that gets verified, select View Successful Tasks. To view log details, select View Log. 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 (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.
If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.
Click Install to begin the installation.
On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.

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

3.4 Stopping Servers and Processes

Before you run the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all processes and servers, including the Administration Server and any managed servers.

An Oracle Fusion Middleware environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple managed servers, Java components, system components such as Identity Management components, and a database used as a repository for metadata. The components may be dependent on each other, so they must be stopped in the correct order.

Note:

The procedures in this section describe how to stop servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Oracle Fusion Middleware Administering Oracle Fusion Middleware.

To stop your Fusion Middleware environment, follow the steps below.

Step 1: Stop System Components

To stop system components, such as Oracle HTTP Server, use the stopComponent script:

(UNIX) DOMAIN_HOME/bin/stopComponent.sh component_name
(Windows) DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 2: Stop the Managed Servers

To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:

(UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url
(Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Step 3: Stop Oracle Identity Management Components

Stop any Oracle Identity Management components, such as Oracle Internet Directory:

(UNIX) DOMAIN_HOME/bin/stopComponent.sh component_name
(Windows) DOMAIN_HOME\bin\stopComponent.cmd component_name

Step 4: Stop the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To stop the Administration Server, use the stopWebLogic script:

(UNIX) DOMAIN_HOME/bin/stopWebLogic.sh
(Windows) DOMAIN_HOME\bin\stopWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 5: Stop Node Manager

To stop Node Manager, close the command shell in which it is running.

Alternatively, after having set the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. For more information, see stopNodeManager in Oracle Fusion Middleware WLST Command Reference for WebLogic Server.

3.5 Upgrading Domain Component Configurations

After reconfiguring the domain, use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration.

Starting the Upgrade Assistant
Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
Upgrading the 11g Domain Components Using the Upgrade Assistant
Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.
Verifying the Domain-specific-Component Configurations Upgrade
To verify that the domain-specific-component configurations upgrade was successful, log in to the Administration console and the Fusion Middleware Control and verify that the version numbers for each component is 12.2.1.2.

3.5.1 Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.

To start the Upgrade Assistant:

Go to the oracle_common/upgrade/bin directory:
- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
- (Windows) ORACLE_HOME\oracle_common\upgrade\bin
Start the Upgrade Assistant:
- (UNIX) ./ua
- (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see:

Upgrade Assistant Parameters

3.5.1.1 Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 3-2 Upgrade Assistant Command-Line Parameters

Parameter	Required or Optional	Description
`-readiness`	Required for readiness checks Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).	Performs the upgrade readiness check without performing an actual upgrade. Schemas and configurations are checked. Do not use this parameter if you have specified the `-examine` parameter.
`-threads`	Optional	Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas. The value must be a positive integer in the range 1 to 8. The default is 4.
`-response`	Required for silent upgrades or silent readiness checks	Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).
`-examine`	Optional	Performs the examine phase but does not perform an actual upgrade. Do not specify this parameter if you have specified the `-readiness` parameter.
`-logLevel attribute`	Optional	Sets the logging level, specifying one of the following attributes: `TRACE` `NOTIFICATION` `WARNING` `ERROR` `INCIDENT_ERROR` The default logging level is `NOTIFICATION`. Consider setting the `-logLevel TRACE` attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if `-logLevel TRACE` is used.
`-logDir location`	Optional	Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant will create log files and temporary files. The default locations are: UNIX: `ORACLE_HOME/oracle_common/upgrade/logs` `ORACLE_HOME/oracle_common/upgrade/temp` Windows: `ORACLE_HOME\oracle_common\upgrade\logs` `ORACLE_HOME\oracle_common\upgrade\temp`
`-help`	Optional	Displays all of the command-line options.

3.5.2 Upgrading the 11g Domain Components Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.

To upgrade the 11g domain using Upgrade Assistant:

On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

Note:
For more information about any Upgrade Assistant screen, click Help on the screen.
On the Domain Directory screen, select Create a New Domain (choose when upgrading from 11g).
On the Standalone Components screen, select Standalone System Component Configurations.
Select Create a New Domain and 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.0, 12.1.3.0, 12.2.1.0, and 12.2.1.1) to the latest 12c release (12.2.1.2).
On the Component List screen, verify that the list includes all the components for which you want to upgrade configurations 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 selecting 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 11g Source and provide the directory location of the 11g instance that you want to upgrade.
This instance is used as a basis for configuring the 12c Oracle HTTP Server instance. The 11g Oracle HTTP Server installation is not altered.

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

Note:
You cannot use the Upgrade Assistant to upgrade Oracle 10g instances to Oracle 12c. You must first upgrade Oracle 10g instances to 11g. For more information on migrating 10g to 11g, see the 11g upgrade documentation for your components.

On the Node Manager screen, specify the following to create a new Node Manager to administer your standalone domain.

Table 3-3 Field Descriptions for the Node Manager Screen

Option	Description
User Name	To specify the user name used to access Node Manager.
Password	To specify the password used to access Node Manager. Re-enter the password for confirmation.
Listen Address	To enter the DNS name or IP address upon which Node Manager listens.
Listen Port	To enter the listening port number of Node Manager.

Note:

The user name and password are only used to authenticate connections between Node Manager and clients. They are independent of the server Administrator credentials.

On the Examine screen, review the status of the Upgrade Assistant as it examines each standalone component, verifying that the standalone component configuration is ready for upgrade. If the status is Examine finished, click Next.
If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Oracle Fusion Middleware Upgrading with the Upgrade Assistant Upgrade Guidefor 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 in 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 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 for component configuration upgrade.
The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant 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 Response File and provide the location and name of the response file.
Click Upgrade to start the upgrade process.
On the Upgrade Progress screen, monitor the status of the upgrade.

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.

Note:
The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

Click Next.
If the upgrade is successful: On 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 components functional in the new installation. This window appears only if a component has post-upgrade steps.

If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at ORACLE_HOME/oracle_common/upgrade/logs. Note If the upgrade fails you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

3.5.3 Verifying the Domain-specific-Component Configurations Upgrade

To verify that the domain-specific-component configurations upgrade was successful, log in to the Administration console and the Fusion Middleware Control and verify that the version numbers for each component is 12.2.1.2.

To log into the Administration Console, go to: http://administration_server_host:administration_server_port/console

To log into the Fusion Middleware Control, go to: http://administration_server_host:administration_server_port/em

Note:

After upgrade, make sure you run the administration tools from the new 12c Oracle home and not from the previous Oracle home.

During the upgrade process, some OWSM documents, including policy sets and predefined documents such as policies and assertion templates, may need to be upgraded. If a policy set or a predefined document is upgraded, its version number is incremented by 1.

3.6 Starting Servers and Processes

After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.

The components may be dependent on each other so they must be started in the correct order.

Note:

The procedures in this section describe how to start servers and process using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.

To start your Fusion Middleware environment, follow the steps below.

Step 1: Start the Administration Server

When you start the Administration Server, you also start the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To start the Administration Server, use the startWebLogic script:

(UNIX) DOMAIN_HOME/bin/startWebLogic.sh
(Windows) DOMAIN_HOME\bin\startWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 2: Start Node Manager

To start Node Manager, use the startNodeManager script:

(UNIX) DOMAIN_HOME/bin/startNodeManager.sh
(Windows) DOMAIN_HOME\bin\startNodeManager.cmd

Step 3: Start Oracle Identity Management Components

Start any Oracle Identity Management components, such as Oracle Internet Directory, that form part of your environment:

(UNIX) DOMAIN_HOME/bin/startComponent.sh component_name
(Windows) DOMAIN_HOME\bin\startComponent.cmd component_name

Step 4: Start the Managed Servers

To start a WebLogic Server Managed Server, use the startManagedWebLogic script:

(UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url
(Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Note:

The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.

Step 5: Start System Components

To start system components, such as Oracle HTTP Server, use the startComponent script:

(UNIX) DOMAIN_HOME/bin/startComponent.sh component_name
(Windows) DOMAIN_HOME\bin\startComponent.cmd component_name

You can start system components in any order.

Starting the Standalone Oracle HTTP Server
After upgrade, start the standalone Oracle HTTP Server.

3.6.1 Starting the Standalone Oracle HTTP Server

After upgrade, start the standalone Oracle HTTP Server.

To start the standalone Oracle HTTP Server:

Go to the oracle_common/upgrade/bin directory:
- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
- (Windows) ORACLE_HOME\oracle_common\upgrade\bin
Enter the command to start the standalone server.
On UNIX operating systems:e

./startComponent.sh ohs_name

On Windows operating systems:

startComponent.cmd ohs_name

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

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

If you are not able to start the newly upgraded environment, a possible cause could be the use of MD5 certificates in your Oracle wallet. See Replacing Certificate Signed Using MD5 Algorithm with Certificate Signed Using SHA-2 Algorithm for a procedure to check whether you are using MD5 signatures and a procedure to replace them with SHA-2 certificates.