Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

What's New in This Guide

• New and Changed Features for 12c
• Other Significant Changes in this Document for 12c

1 Introduction to Upgrading Oracle HTTP Server to 12c (12.2.1.2)

• 1.1 About the Starting Points for an Oracle HTTP Server Upgrade
• 1.2 About the Oracle HTTP Server Standard Topologies
  • 1.2.1 Fusion Middleware Infrastructure Upgrade Topology with Oracle HTTP Server
    • 1.2.1.1 Oracle HTTP Server Standard Upgrade Topology for Standalone Agents not Associated with a WebLogic Domain
• 1.3 Differences between Oracle HTTP Server 11g and 12c
• 1.4 About Upgrade Restrictions
• 1.5 How to Use this Guide
• 1.6 Determining whether Oracle HTTP Server is Standalone or Managed (Collocated)

2 Preparing to Upgrade Oracle HTTP Server

• 2.1 Oracle Fusion Middleware Pre-Upgrade Checklist
• 2.2 Creating a Complete Backup
  • 2.2.1 Backing Up the Schema Version Registry Table
  • 2.2.2 Maintaining Custom Domain Environment Settings
• 2.3 Cloning Your Production Environment for Testing
• 2.4 Verifying Certification and System Requirements
  • 2.4.1 Verify Your Environment Meets Certification Requirements
  • 2.4.2 Verify System Requirements and Specifications
    • 2.4.2.1 Migrating from a 32-Bit to a 64-Bit Operating System
      • 2.4.2.1.1 Procure the Hardware That Supports the Upgrade's 64-bit Software Requirement
      • 2.4.2.1.2 Stop All Processes
      • 2.4.2.1.3 Back Up All Files from the 32-bit Host Machine
      • 2.4.2.1.4 Set Up the Target 64-bit Machine with the 11g Host Name and IP Address
      • 2.4.2.1.5 Restore the 11g Backup from 32-bit Host to 64-bit Host
      • 2.4.2.1.6 Install the 12c Product Distributions on the Target Machine
      • 2.4.2.1.7 Upgrade the Target 64-bit Environment Using the Standard Upgrade Procedure
  • 2.4.3 Verify That the Database Hosting Oracle Fusion Middleware Is Supported
  • 2.4.4 Verify That the JDK Is Certified for This Release of Oracle Fusion Middleware
• 2.5 Updating Policy Files when Using Enhanced Encryption (AES 256)
• 2.6 Purging Unused Data
• 2.7 Creating an Edition on the Server for Edition-Based Redefinition
• 2.8 Creating a Non-SYSDBA User to Run the Upgrade Assistant
• 2.9 Identifying Existing Schemas Available for Upgrade

Part I Upgrading Oracle HTTP Server from 11g to 12c

3 Upgrading a Standalone Oracle HTTP Server from 11g to 12c

• 3.1 About the Standalone Oracle HTTP Server Upgrade Process from 11g to 12c
• 3.2 Important Pre-Upgrade Considerations
  • 3.2.1 Oracle Web Cache 11g Users
  • 3.2.2 WebGate 11g Users
  • 3.2.3 Updating the WebGate log file-name
  • 3.2.4 Application Artifacts from 11g
  • 3.2.5 Migrating 11g Application Artifacts
• 3.3 Installing the Standalone Oracle HTTP Server
• 3.4 Stopping Servers and Processes
• 3.5 Upgrading Domain Component Configurations
  • 3.5.1 Starting the Upgrade Assistant
    • 3.5.1.1 Upgrade Assistant Parameters
  • 3.5.2 Upgrading the 11g Domain Components Using the Upgrade Assistant
  • 3.5.3 Verifying the Domain-specific-Component Configurations Upgrade
• 3.6 Starting Servers and Processes
  • 3.6.1 Starting the Standalone Oracle HTTP Server
• 3.7 Verifying the Upgrade

4 Upgrading a Managed Oracle HTTP Server from 11g to 12c

• 4.1 About the Managed Oracle HTTP Server Upgrade Process from 11g to 12c
• 4.2 Installing the Product Distributions
• 4.3 Running a Pre-Upgrade Readiness Check
  • 4.3.1 About Running a Pre-Upgrade Readiness Check
  • 4.3.2 Starting the Upgrade Assistant in Readiness Mode
    • 4.3.2.1 Upgrade Assistant Parameters
  • 4.3.3 Performing a Readiness Check with the Upgrade Assistant
  • 4.3.4 Understanding the Readiness Report
• 4.4 Stopping Servers and Processes
• 4.5 Creating the Required 12c Schemas with the RCU
• 4.6 Reconfiguring the Domain
  • 4.6.1 Backing Up the Domain
  • 4.6.2 Starting the Reconfiguration Wizard
  • 4.6.3 Reconfiguring the Domain with the Reconfiguration Wizard
• 4.7 Upgrading Domain Component Configurations
  • 4.7.1 Starting the Upgrade Assistant
    • 4.7.1.1 Upgrade Assistant Parameters
  • 4.7.2 Upgrading Domain Components Using the Upgrade Assistant
  • 4.7.3 Verifying the Domain-specific-Component Configurations Upgrade
• 4.8 Starting Servers and Processes
  • 4.8.1 Starting the Oracle HTTP Server
• 4.9 Verifying the Upgrade
• 4.10 Importing Wallets to the KSS Database after an Upgrade Using WLST

Part II Upgrading Oracle HTTP Server from a Previous 12c Release

5 Upgrading a Standalone Oracle HTTP Server from a Previous 12c Release

• 5.1 About the Standalone Oracle HTTP Server Upgrade Process from a Previous 12c Release
• 5.2 Installing the Standalone Oracle HTTP Server
• 5.3 Stopping Servers and Processes
• 5.4 Reconfiguring the Domain
  • 5.4.1 Backing Up the Domain
  • 5.4.2 Starting the Reconfiguration Wizard
  • 5.4.3 Reconfiguring the Existing Domain with the Reconfiguration Wizard
• 5.5 Upgrading Standalone System Component Configurations
  • 5.5.1 Starting the Upgrade Assistant
    • 5.5.1.1 Upgrade Assistant Parameters
  • 5.5.2 Upgrading Standalone System Component Configurations Using the Upgrade Assistant
  • 5.5.3 Verifying the Domain-specific-Component Configurations Upgrade
• 5.6 Verifying the Upgrade
  • 5.6.1 Starting the Node Manager
  • 5.6.2 Starting the Standalone Oracle HTTP Server
• 5.7 Starting Servers and Processes

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

• 6.1 About the Managed Oracle HTTP Server Upgrade Process from a Previous 12c Release
• 6.2 Installing the Product Distributions
• 6.3 Running a Pre-Upgrade Readiness Check
  • 6.3.1 About Running a Pre-Upgrade Readiness Check
  • 6.3.2 Starting the Upgrade Assistant in Readiness Mode
    • 6.3.2.1 Upgrade Assistant Parameters
  • 6.3.3 Performing a Readiness Check with the Upgrade Assistant
  • 6.3.4 Understanding the Readiness Report
• 6.4 Stopping Servers and Processes
• 6.5 Upgrading Product Schemas
  • 6.5.1 Identifying Existing Schemas Available for Upgrade
  • 6.5.2 Starting the Upgrade Assistant
    • 6.5.2.1 Upgrade Assistant Parameters
  • 6.5.3 Upgrading the Product Schemas Using the Upgrade Assistant
  • 6.5.4 Verifying the Schema Upgrade
• 6.6 Reconfiguring the Domain
  • 6.6.1 Backing Up the Domain
  • 6.6.2 Starting the Reconfiguration Wizard
  • 6.6.3 Reconfiguring the Domain with the Reconfiguration Wizard
• 6.7 Upgrading Domain Component Configurations
  • 6.7.1 Starting the Upgrade Assistant
    • 6.7.1.1 Upgrade Assistant Parameters
  • 6.7.2 Upgrading Domain Components Using the Upgrade Assistant
  • 6.7.3 Verifying the Domain-specific-Component Configurations Upgrade
• 6.8 Starting Servers and Processes
  • 6.8.1 Starting the Oracle HTTP Server
• 6.9 Verifying the Upgrade
• 6.10 Importing Wallets to the KSS Database after an Upgrade Using WLST

A Replacing Certificate Signed Using MD5 Algorithm with Certificate Signed Using SHA-2 Algorithm

• A.1 How to Check whether Certificate Signed with MD5 Algorithm is Present in the Wallet?
• A.2 Removing Certificate Signed with MD5 Algorithm from the Wallet
• A.3 Adding Certificate Signed with SHA-2 Algorithm to the Wallet
• A.4 Enabling Support for Certificate Signed with MD5 Algorithm in your 12.2.1.2 Oracle HTTP Server Deployment