This chapter contains the following sections:
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 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 registered them to a Oracle 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.
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 Release 12.2.1.1, 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.In Oracle Fusion Middleware 12c Release 12.2.1, 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 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.
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 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.
Upgrading a standalone Oracle HTTP Server from 11g to 12c is an out-of-place upgrade. You must install the Oracle HTTP Server 11g software in a new Oracle home and then use the Upgrade Assistant to upgrade the 11g domain.
Perform the following tasks to complete the standalone Oracle HTTP Server 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:
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.