Table of Contents
- Title and Copyright Information
- Preface
- What's New in This Guide
- 1 Introduction to Upgrading Oracle HTTP Server to 12c (12.2.1.4.0)
-
2
Preparing to Upgrade Oracle HTTP Server
- Oracle Fusion Middleware Pre-Upgrade Checklist
- Creating a Complete Backup
- Cloning Your Production Environment for Testing
-
Verifying Certification and System Requirements
- Verify Your Environment Meets Certification Requirements
-
Verify System Requirements and Specifications
-
Migrating from a 32-Bit to a 64-Bit Operating System
- Procure the Hardware That Supports the Upgrade's 64-bit Software Requirement
- Stop All Processes
- Back Up All Files from the 32-bit Host Machine
- Set Up the Target 64-bit Machine with the 12c (12.2.1.3.0) Host Name and IP Address
- Restore the 12c (12.2.1.3.0) Backup from 32-bit Host to 64-bit Host
- Install the 12c (12.2.1.4.0) Product Distributions on the Target Machine
- Upgrade the Target 64-bit Environment Using the Standard Upgrade Procedure
-
Migrating from a 32-Bit to a 64-Bit Operating System
- Verify That the Database Hosting Oracle Fusion Middleware is Supported
- Verify That the JDK Is Certified for This Release of Oracle Fusion Middleware
- Updating Policy Files when Using Enhanced Encryption (AES 256)
- Purging Unused Data
- Creating an Edition on the Server for Edition-Based Redefinition
- Creating a Non-SYSDBA User to Run the Upgrade Assistant
-
Part I Upgrading Oracle HTTP Server from 11g to 12c
- 3 Upgrading a Standalone Oracle HTTP Server from 11g to 12c
-
4
Upgrading a Managed Oracle HTTP Server from 11g to 12c
- About the Managed Oracle HTTP Server Upgrade Process from 11g to 12c
- Installing the Product Distributions
- Running a Pre-Upgrade Readiness Check
- Stopping Servers and Processes
- Creating the Required 12c Schemas with the RCU
- About Reconfiguring the Domain
- Upgrading Domain Component Configurations
- Starting Servers and Processes
- Verifying the Upgrade
- Importing Wallets to the KSS Database after an Upgrade Using WLST
- Post-Upgrade Task
-
Part II Upgrading Oracle HTTP Server from a Previous 12c Release
-
5
Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release
- About the Standalone Oracle HTTP Server Upgrade Process from a Previous 12c Release
- Installing the Standalone Oracle HTTP Server
- Stopping Servers and Processes
- About Reconfiguring the Domain
- Upgrading Standalone System Component Configurations
- Verifying the Upgrade
- Starting Servers and Processes
- Post-Upgrade Task
-
6
Upgrading a Managed Oracle HTTP Server from a Previous 12c Release
- About the Managed Oracle HTTP Server Upgrade Process from a Previous 12c Release
- Installing the Product Distributions
- Running a Pre-Upgrade Readiness Check
- Stopping Servers and Processes
- Upgrading Product Schemas (Applicable for Full-JRF Only)
- About Reconfiguring the Domain
- Upgrading Domain Component Configurations
- Starting Servers and Processes
- Verifying the Upgrade
- Post-Upgrade Task
-
5
Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release
-
A
Replacing Certificate Signed Using MD5 Algorithm with Certificate Signed Using SHA-2 Algorithm
- How to Check whether Certificate Signed with MD5 Algorithm is Present in the Wallet?
- Removing Certificate Signed with MD5 Algorithm from the Wallet
- Adding Certificate Signed with SHA-2 Algorithm to the Wallet
- Enabling Support for Certificate Signed with MD5 Algorithm in your 12.2.1.4.0 Oracle HTTP Server Deployment
- B About Updating the JDK Location After Installing an Oracle Fusion Middleware Product
- C About the Reduced Downtime Upgrade Process